Problem with throttle (collective) in Dodo helicopter

[Griphos]

I'm a new user of the registered version of FSUIPC. I've set up my throttles (and only my two throttle levers on my CH quadrant) through FSUIPC, deleting the assignments in FSX for those two levers. I did so in order to use the wonderful lua script by pilotjohn for reverse thrust provided here on the forum in user contributions. That works like a charm.

I calibrated my two throttle axes as per the instructions in the user guide. Throttles work fine in all aircraft I have used so far, with the exception of the Dodo helicopter. In helicopters, throttle control in the aircraft is usually assigned to prop pitch, and the actual throttle axis controls the "collective." This works fine in my Aerosoft Huey, just as it should, but in the Dodo, trying to control the collective with the throttle axis produces very strange behavior. The power needle jumps around as I move the axis and the helicopter tries to lift off, but as I stop moving the throttle axis, the power drops to zero. This never happened when throttle axes were assigned in FSX.

It appears that there is something being recognized when I move the throttle (collective), but something is not right. I can make the helicopter take off by constantly moving the throttle axis up near the top of its range, and I can make the helicopter descend again by constantly moving the throttle axis near the bottom of its range. In other words, by constantly jiggling the axis, I appear to be sending signals to the sim that the Dodo recognizes. But as soon as I stop moving the axis at any point in its range, the signals seem to stop and the power returns to idle.

I'm really hoping there is a way to resolve this issue with the Dodo. I've searched and can't find any info on others having this problem. I would hate to have to revert to FSX control, since the lua script for reverse thrust is a god-send for my turbo-props. But I can't give up flying the Dodo!

Edited October 9, 2012 by Griphos

[Pete Dowson]

It appears that there is something being recognized when I move the throttle (collective), but something is not right. I can make the helicopter take off by constantly moving the throttle axis up near the top of its range, and I can make the helicopter descend again by constantly moving the throttle axis near the bottom of its range. In other words, by constantly jiggling the axis, I appear to be sending signals to the sim that the Dodo recognizes. But as soon as I stop moving the axis at any point in its range, the signals seem to stop and the power returns to idle.

FSUIPC only sends axis controls when the input changes. And as far as I know, so does FS. However, FSUIPC only acts on changes greater than the "Delta" value -- you can see this in the Axis assignments tab. This makes it much more efficient and smoother since changes smaller than a certain amount have little or no actual effect in FS in any case, and it removes unwanted jitter which some hardware inputs are prone to.

You could edit the INI file Axis assignment and change the Delta from its default (256) to 1, say, but I would really doubt that your helicopter is reliant so much on using a jittering control. I think something else must be going wrong with it. Maybe it requires a different control. How are you assigning the Axis -- in FSUIPC? If in FSUIPC, using which method? Direct to FSUIPC calibration, or to an FS control. If to an FS control, which one? And how are you calibrating? In the single throttle part or the 4 throttle part, and with Reverse Zone or not?

Oh, and which exact version number of FSUIPC? If it is earlier than 4.853 please update first.

I'm really hoping there is a way to resolve this issue with the Dodo. I've searched and can't find any info on others having this problem. I would hate to have to revert to FSX control, since the lua script for reverse thrust is a god-send for my turbo-props. But I can't give up flying the Dodo!

Two points there:

First, you should know that you can do different things for different aircraft -- via Profiles (or the older aircraft-specific facilities if preferred). So you can assign differently as well as calibrate differently for different aircraft or different aircraft types. It would be quite normal to use an entirely different set of controls for a helicopter as opposed to a turbo-prop.

Second, since this peculiarity is specific to that one make of helicopter, I think you should be seeking advice on their support forum. They will know better what might be going on than I. There is no way i can obtain, test, and support all the possible add-ons to which folks apply FSUIPC.

Regards

Pete

[Griphos]

What appears to be happening is that a signal is sent when the axis is moved to set the power corresponding to the amount of movement but then when the axis stops moving, a signal is sent to set the power to 0. This results in the power jumping around while moving the axis (which it shouldn't, since moving the axis should result in a smooth application of power) and then down to 0 again (actually 30 % on the gauge, which is zero power input) when I stop moving the axis, always ending with the power at 0.

I'm assigning the axis in FSUIPC as I said, and I have deleted that axis in FSX. I have "Send direct to FSUIPC" option checked. Here's my settings:

I'm using 4.853. I just bought it a few weeks ago.

I've tried different settings in FSUIPC. The response is always the same. So far, it is specific to this helicopter, but I haven't been able to find the problem occurring for anyone else using FSUIPC and the Dodosim, and I have found info on the internet where people are using FSUIPC and this aircraft and not having any problems, so I think this is a problem with my specific install, and since the Dodosim works perfectly (and always has) with FSX controlling the throttle axis, I think it must be something I'm doing wrong in FSUIPC.

And there is a weirdness that I'll explain now, but the thing is that all my other aircraft work perfectly fine, including the Huey helicopter (I don't have a lot of helicopters).

The weirdness is that when I open up FSUIPC and click on the Axis Assignment, it's usually not blank. Instead it usually says this:

I've not assigned this axis, and don't know what Axis# R even is. If I close it and open again, it sometimes says the same thing except Axis# V or Z. This may simply indicate that FSUIPC is registering one of my other axes as having moved.

The really weird part is that if I open FSUIPC and the Joy# and Axis# fields are blank, and I move Axis X (Throttle 1), then it puts Axis#Y in the fields and registers the movement of that axis (Throttle 2). If I move Axis Y, it puts Axis# X in the fields and registers the movement of Axis X. If I move any other axis on my 6 axis CH quadrant (none of which I've assigned in FSUIPC) when the fields are blank, then it registers Axis# X, usually, but sometimes axis# Y. If I hit rescan, it then registers whichever axis (X or Y I move correctly, although sometimes I have to hit rescan several times as it cycles through Axis# R or U or Z or whatever first.

So, I think something is not right here, but I followed the steps from both the User Guide and PilotJohn's instructions for his Lua script exactly.

Edited October 10, 2012 by Griphos

[Pete Dowson]

What appears to be happening is that a signal is sent when the axis is moved to set the power corresponding to the amount of movement but then when the axis stops moving, a signal is sent to set the power to 0.

SUIPC most certainly won't be doing such things of its own volition!

I'm assigning the axis in FSUIPC as I said, and I have deleted that axis in FSX. I have "Send direct to FSUIPC" option checked. Here's my settings:

That's fine.

I'm using 4.853. I just bought it a few weeks ago.

You buy FSUIPC4. The purchase covers all versions 4.xxx.

I've tried different settings in FSUIPC. The response is always the same. So far, it is specific to this helicopter, but I haven't been able to find the problem occurring for anyone else using FSUIPC and the Dodosim, and I have found info on the internet where people are using FSUIPC and this aircraft and not having any problems, so I think this is a problem with my specific install, and since the Dodosim works perfectly (and always has) with FSX controlling the throttle axis, I think it must be something I'm doing wrong in FSUIPC.

Well, it doesn't appear to be related to the assignment you've shown. Why not show me the INI file where all the settings are stored? That would be far for informative and definitive than a set of pictures!

The weirdness is that when I open up FSUIPC and click on the Axis Assignment, it's usually not blank. Instead it usually says this:

...

I've not assigned this axis, and don't know what Axis# R even is. If I close it and open again, it sometimes says the same thing except Axis# V or Z. This may simply indicate that FSUIPC is registering one of my other axes as having moved.

Yes, it means there's jitter on those other axes and this is being detected. You'd need to press the "rescan" button to clear it and make FSUIPC look for another. If the same one keeps cropping up you'd need to use the "ignore axis" button to tell it to (temporarily) not scan that axis. (All this is covered in the documentation).

The really weird part is that if I open FSUIPC and the Joy# and Axis# fields are blank, and I move Axis X (Throttle 1), then it puts Axis#Y in the fields and registers the movement of that axis (Throttle 2). If I move Axis Y, it puts Axis# X in the fields and registers the movement of Axis X. If I move any other axis on my 6 axis CH quadrant (none of which I've assigned in FSUIPC) when the fields are blank, then it registers Axis# X, usually, but sometimes axis# Y. If I hit rescan, it then registers whichever axis (X or Y I move correctly, although sometimes I have to hit rescan several times as it cycles through Axis# R or U or Z or whatever first.

Either you are confusing yourself about which is X and which is Y, or your device is subject to interference between the assorted axes (I've seen this happen), and probably one or more has a tendency to jitter. It is not "weird", and you can deal with it using the ignore and rescan buttons as documented and mentioned above.

So, I think something is not right here, but I followed the steps from both the User Guide and PilotJohn's instructions for his Lua script exactly.

Show me your FSUIPC4.INI file, from the FS Modules folder.

You can also use FSUIPC's axis and event logging to see what is hhappening. Check the Logging tab -- you'll see the options there. If you (temporarily) run FSX in Windowed mode you can enable FSUIPC's Console Log too, and see what is happening in real time on screen. Don't mess with any other options there, though. Don't press "new log". If you want help understanding what the log is showing, paste a relevant section into a message here.

Note that after tomorrow (Thursday) I am away on holiday for over three weeks (back November 5th).

Regards

Pete

[Griphos]

I'm happy to paste in the .ini (below) but I figured pictures of my settings would be more informative than me trying to describe them and you could see what they are easily.

No, I'm not confusing myself. And it's completely regular. I've tried quite a number of times, and there is never a departure. Moving Axis#X always triggers Axis#Y and moving Axis#Y always triggers Axis#X. If I open up FSUIPC and move axis #X, axis#Y appears in the windows and moving axis#Y changes the values. Moving axis#Y always makes axis#X appear in the windows and moving axis#X after that changes the values. The changes are smooth, without any appearance of jitter (in other words, the values change smoothly and do not change after I stop moving the axis....it's a fairly new quadrant).

This seems to have no effect on operation in the sim except for possibly the Dodo.

Here's the .ini. I'll try the other things you suggest when I get home from work. I am reading the manual, but don't always understand its instructions. The interface is not always intuitive, but I'm working at it.

----------

[General]

UpdatedByVersion=4853

History=YAM4VJNVSVU9HAIOXG9UB

AxesWrongRange=No

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

InitDelay=0

GetNearestAirports=Yes

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

LuaRerunDelay=66

Console=No

OOMcheck=Yes

InitDelayDevicesToo=No

MouseWheelMove=No

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

FixControlAccel=No

FixMachSpeedBug=No

DeleteVehiclesForAES=Yes

AutoScanDevices=Yes

VisibilityOptions=No

OneCloudLayer=No

CloudTurbulence=No

CloudIcing=No

GenerateCirrus=No

SuppressCloudTurbulence=No

MaxIce=-4

MinIce=-4

UpperWindGusts=No

SuppressWindTurbulence=No

SuppressWindVariance=No

WindTurbulence=No

TurbulenceRate=1.0,5.0

TurbulenceDivisor=20,20,40,40

SuppressAllGusts=No

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

SmoothBySimTime=No

WindSmoothing=No

WindSmoothness=2

WindSmoothAirborneOnly=Yes

PressureSmoothness=0

TemperatureSmoothness=0

DisconnTrimForAP=No

ZeroElevForAPAlt=No

ThrottleSyncAll=No

WhiteMessages=No

ShowPMcontrols=No

SpoilerIncrement=512

MagicBattery=No

RudderSpikeRemoval=No

ElevatorSpikeRemoval=No

AileronSpikeRemoval=No

ReversedElevatorTrim=No

ClockSync=No

ClockSyncMins=5

ClearWeatherDynamics=No

OwnWeatherChanges=No

TimeForSelect=4

LoadFlightMenu=No

LoadPlanMenu=No

PauseAfterCrash=No

BrakeReleaseThreshold=75

SaveDataWithFlights=No

ZapSound=firework

ShortAircraftNameOk=No

UseProfiles=Yes

EnableMouseLook=No

FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0

SimConnectUsed=10.0.61259.0

[JoyNames]

AutoAssignLetters=No

1=CH Pro Pedals USB

1.GUID={3F04E780-F054-11E0-8005-444553540000}

2=CH Throttle Quadrant USB

2.GUID={42699650-F054-11E0-8008-444553540000}

3=Pro Flight Cessna Trim Wheel

3.GUID={A2BCFFB0-624B-11E1-8001-444553540000}

0=T.16000M

0.GUID={4A54B3D0-31DE-11DF-8001-444553540000}

[WideServer]

WideFSenabled=Yes

[sounds]

Path=D:\MyGames\FSX\Sound\

Device1=Primary Sound Driver

Device2=Headphones (High Definition Audio Device)

Device3=Digital Audio (S/PDIF) (High Definition Audio Device)

Device4=Speakers (High Definition Audio Device)

Device5=Digital Audio (HDMI) (High Definition Audio Device)

[Window.VAFS Message:]

Docked=405, 3449, 3514, 2428

[buttons]

ButtonRepeat=20,10

1=P2,14,CL2:T,2

2=P2,12,CL2:T,1

3=H2,3,K45,8

[MacroFiles]

1=4X_DA20-100

2=Meggitt2100

[AutoSave]

Next=1

Interval=60

Files=10

SaveOnGround=No

AutoSaveEnabled=No

[GPSout]

GPSoutEnabled=No

[GPSout2]

GPSoutEnabled=No

[LuaFiles]

1=PMDG_J41_CP

2=ThrottleManager

[Profile.J41]

1=PMDG Jetstream 41 Origin Pacific

[Keys.J41]

1=74,11,L1:R,0

[JoystickCalibration]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=No

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

Throttle1=-16384,-512,512,16383/32

Throttle2=-16384,-512,512,16383/32

SyncSlopeThrottle2=20/21,41/41,63/63,71/71,92/91,101/100,117/115

MapThr12to34=Yes

[Auto]

2=Lua ThrottleManager

[Axes]

0=2X,256,D,9,0,0,0

1=2Y,256,D,10,0,0,0

[Pete Dowson]

No, I'm not confusing myself. And it's completely regular. I've tried quite a number of times, and there is never a departure. Moving Axis#X always triggers Axis#Y and moving Axis#Y always triggers Axis#X. If I open up FSUIPC and move axis #X, axis#Y appears in the windows and moving axis#Y changes the values. Moving axis#Y always makes axis#X appear in the windows and moving axis#X after that changes the values. The changes are smooth, without any appearance of jitter (in other words, the values change smoothly and do not change after I stop moving the axis....it's a fairly new quadrant).

It is definitely behaving strangely, though. There's no way FSUIPC can do that. It judst gets the named axes from DirectInput.

Your INI looks innocent enough. Hardly much use of FSUIPC at all at present, and certainly nothing which will produce the symptoms you describe -- unless it is something in the Lua files executed by these lines

1=P2,14,CL2:T,2

2=P2,12,CL2:T,1

and one or other of those buttons is getting pressed or acting flakily. I see they are on the throttle quadrant. Try placing a ';' in front of both lines to stop them doing anything, just as a test. I see it is called "ThrottleManager" and it is certainly the most likely candidate.

Just one other observation. This line in [JoystickCalibration]

SyncSlopeThrottle2=20/21,41/41,63/63,71/71,92/91,101/100,117/115

is very unlikely to have anything to do with it, but it might be worth eliminating that too (; in front of the line).

If neither of these changes makes any difference then the logging details are needed, bt it would then point strongly at a faulty device or driver.

Regards

Pete

[Griphos]

I remarked those lines, although I think the SyncSlope settings were done after I first noticed this issue. There was no change in behavior. I enabled logging and then advanced and retarded the throttle four times, and then moved it and stopped it a bit. I think this is the log that was made. Hope there's something in here that is helpful :

********* FSUIPC4, Version 4.853 by Pete Dowson *********

User Name="Phil Hopkins"

User Addr="hopkinsp@southwestern.edu"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

1681113 System time = 10/10/2012 09:23:35, Simulator time = 09:19:41 (17:19Z)

[Continuation log requested by user]

Running inside FSX on Windows 7

Module base=635C0000

1681113 LogOptions changed, now 50000000 00000001

1681363 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

1681363 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET

1681363 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

1681363 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET

1681363 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

1681535 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

1681535 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -165 (0xffffff5b) AXIS_ELEVATOR_SET

1681535 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

1681535 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET

1681535 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

1681691 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

1681691 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -165 (0xffffff5b) AXIS_ELEVATOR_SET

1681691 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

1681691 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET

1681691 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

1681878 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

1681878 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET

1681878 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

1681878 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET

1681878 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

1681878 *** AXIS: Cntrl= 65820 (0x0001011c), Param= 130 (0x00000082) THROTTLE1_SET

[Griphos]

EDIT: long necessary log deleted

[Pete Dowson]

I remarked those lines, although I think the SyncSlope settings were done after I first noticed this issue. There was no change in behavior. I enabled logging and then advanced and retarded the throttle four times, and then moved it and stopped it a bit. I think this is the log that was made. Hope there's something in here that is helpful :

[Continuation log requested by user]

First off, you pressed the "New Log" button. I expressly asked you not to do that. It means that some of the initialisation information is missing!

Second, you did not need to send a complete log. Each part is much like the other. That is why I just asked for an extract, a "relevant section" -- ie. one place where you got the problem

Third, it certainly looks like toy have all your axes alsp defined in FSX, not only in FSUIPC:

1681363 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

1681363 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET

1681363 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

1681363 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET

1681363 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

All those events are from FSX assignments! In particular the AXIS THROTTLE SET controls will conflict with your two separate throttle assignments in FSUIPC!

Disable controllers in FSX! You must NEVER have dual assignments for the same axis to the same action. It is asking for trouble! The documentation tells you this, and I note even the instructions for using that Throttle Lua add-on tells you to at least unassign them. You can do this, but be aware that FSX does re-assign automatically if it ever sees the controls as newly connected. Best therefore to only use FSX or FSUIPC for assignments, not both.

Pete

[Griphos]

Yes, you did say that, but you also said to check the logging tab and I wasn't sure whether logging was happening unless I clicked something.

I did disable my two throttle axes in FSX. I've seen plenty of information both here and in the lua script itself that makes this clear. As I said, I'm am reading the instructions and trying my best to follow them. I have a Ph.D. and am not unfamiliar with reading technical instructions. I clearly understand that FSX and FSUIPC cannot be controlling the same axis or button at the same time. I also believe I understand I don't have to fully disable a controller in FSX in order to assign some of its axes in FSUIPC. Perhaps I am mistaken about that.

But I checked in FSX yet again to triple check that the two throttle axes are not being controlled by the sim:

As you'll see here, there is no setting on this controller or any other for Throttle 1 or Throttle 2 (X and Y axis). There is for X and Y rotation, which are two different axes on the controller. So, I do not see how FSX is trying to control those two axes. I'll trust you that the log says they are. Or perhaps the log says that other axes on the same controller are being controlled by FSX and I need to disable that whole controller in FSX. I would prefer not to do that, but will, I suppose, if I have to.

I realize that you've been doing this a long time, and that you are intimately familiar with this program. I am not. I am trying to read everything provided by you to figure out what the problem is, but have not been able to do so, and that is why I am writing here.

[Pete Dowson]

Yes, you did say that, but you also said to check the logging tab and I wasn't sure whether logging was happening unless I clicked something.

The logging "tab" is the tab selecting the Logging options, like Axis tab and Buttons tab, etc. In Windows tabbed dialogues the tabs are the selection bits at the top, as in a filing system with tabs.

I did disable my two throttle axes in FSX.

...

But I checked in FSX yet again to triple check that the two throttle axes are not being controlled by the sim:

Those are the two separate throttle axes, which, yes, are unassigned in FSX (as I could see from the log)! But you've not bothered to scroll down to the single throttle axis,That's the one which is doing the damage! "AXIS_THROTTLE_SET" is the single throttle axis which is obviously assigned in your FSX -- as I can see in the Log along with those other axes I listed. If it isn't assigned on this controller, it most certainly is on another.

I also believe I understand I don't have to fully disable a controller in FSX in order to assign some of its axes in FSUIPC. Perhaps I am mistaken about that.

Provided that you don't have conflicts, which you do, that is true. But be aware, as I already stated, that FSX will automatically reassign axes if it ever sees your device as "newly connected". So whenever you get something odd happening, as you have, always check.

On the whole it is best to do all or none at all. Keeps things clean and tidy.

To check assignments on a device you need to scroll through the entire list, not just stop at the start!

I realize that you've been doing this a long time, and that you are intimately familiar with this program. I am not. I am trying to read everything provided by you to figure out what the problem is, but have not been able to do so, and that is why I am writing here.

I understand that, but I am asking you to do things and you are not, or you are doing different things. And you certainly aren't ensuring that you have no conflicting assignments in FSX!

Pete

[Griphos]

I did in fact ensure I had no conflicting assignments. And I haven't "newly connected" anything, although I will be sure to keep that issue in mind. And I'm doing what you are asking as I understand what you are asking, and will continue to do so. There is no single throttle axis assigned on this controller, but I checked all other controllers as well (a joystick, pedals, and trim wheel). There were no assignments to any axis on any controller for the single Throttle axis or any throttle axis. I can take pictures of all of them if you would like. But, with what you said in mind, I looked at buttons as well, and found that there were settings for throttle (increase quickly and decrease quickly) for "mouse look" on the scroll wheel. Lord knows how those got there, as I certainly didn't do that. Perhaps they are default. There was also a throttle decrease quickly (default=F2) assigned to a button on the CH quadrant. I deleted those assignments, restarted FSX and checked to make sure they were still not assigned, and then tried the helicopter again.

That didn't make any difference.

I trust you that something in FSX is controlling the single throttle axis, and that this is causing the problem, however only for this one aircraft so far, but I can't for the life of me see what it is since nothing is assigned to it in FSX. Would it be helpful to look at my controls.ini?

I copied the log from when I restarted FSX to check, but it doesn't seem to have logged any control inputs, although I was making them. If you could tell me how to ensure I get the kind of log you need, I will try to get it:

********* FSUIPC4, Version 4.853 by Pete Dowson *********

Running inside FSX on Windows 7

Module base=62FC0000

User Name="Phil Hopkins"

User Addr="hopkinsp@southwestern.edu"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

406 System time = 10/10/2012 12:02:03

406 FLT path = "C:\Users\Phil\Documents\Flight Simulator X Files\"

437 Trying to connect to SimConnect Acc/SP2 Oct07 ...

437 FS path = "D:\MyGames\FSX\"

702 LogOptions=00000000 00000001

702 Wind smoothing fix is fully installed

702 G3D.DLL fix attempt installed ok

702 SimConnect_Open succeeded: waiting to check version okay

702 Trying to use SimConnect Acc/SP2 Oct07

4321 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

4321 Initialising SimConnect data requests now

4321 FSUIPC Menu entry added

4352 D:\MyGames\FSX\FLIGHTS\OTHER\FLTSIM.FLT

4352 D:\MyGames\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

54413 D:\MyGames\FSX\SimObjects\Rotorcraft\DodoSim_206_FSX_LowSkid\DodoSim206FSX_lowskid.AIR

117375 System time = 10/10/2012 12:04:00, Simulator time = 12:02:07 (20:02Z)

117437 Aircraft="Dodosim 206 FSX RAN N17-025"

118904 Starting everything now ...

118919 LUA.0: Starting...

118951 LUA.0: Done.

120011 Advanced Weather Interface Enabled

314404 Sim stopped: average frame rate for last 196 secs = 69.2 fps

405540 Sim stopped: average frame rate for last 63 secs = 72.4 fps

408582 Weather Mode now = Theme

408582 C:\Users\Phil\AppData\Roaming\Microsoft\FSX\Previous flight.FLT

[Pete Dowson]

I did in fact ensure I had no conflicting assignments. And I haven't "newly connected" anything, although I will be sure to keep that issue in mind.

Well, take care. Sometimes just a USB glitch or a slower than normal initilalisation of a USB device can make it happen. Just check when you get problems.

I trust you that something in FSX is controlling the single throttle axis, and that this is causing the problem, however only for this one aircraft so far, but I can't for the life of me see what it is since nothing is assigned to it in FSX. Would it be helpful to look at my controls.ini?

No. Just disable the controllers and re-test. That will prove it to you. I am running out of time here. You really do need to test this yourself. There is nothing in FSUIPC which is doing this to you!

I copied the log from when I restarted FSX to check, but it doesn't seem to have logged any control inputs

You haven't got any log options selected this time, that's why! I don't know why you turned them off.

Anyway, it won't tell me anything else now. Those "AXIS_ ..." controls it logged last time were certainly all from FSX -- unless the FSUIPC4.INI file you showed me isn't the one you are actually using.

Pete

[Pete Dowson]

Further to my previous reply, there is one important thing I just noticed. when you had Axis logging enabled, as in the ealrier logs, the main 5 "generic" control axes were being set at rregualr intervals: Here's a section without the confusion of your own throttle movements:

1683204 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

1683204 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -205 (0xffffff33) AXIS_ELEVATOR_SET

1683204 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

1683204 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET

1683204 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

1683375 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

1683375 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -215 (0xffffff29) AXIS_ELEVATOR_SET

1683375 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

1683375 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET

1683375 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

1683547 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

1683547 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -225 (0xffffff1f) AXIS_ELEVATOR_SET

1683547 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

1683547 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET

1683547 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

1683703 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

1683703 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -235 (0xffffff15) AXIS_ELEVATOR_SET

1683703 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

1683703 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET

1683703 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

1683875 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

1683875 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -245 (0xffffff0b) AXIS_ELEVATOR_SET

1683875 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

1683875 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET

1683875 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

1684031 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

1684031 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -255 (0xffffff01) AXIS_ELEVATOR_SET

1684031 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

1684031 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET

1684031 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

The fact is that these are NOT sent by FSUIPC. But it perhaps isn't actually FSX either, because it doesn't appear that the all values are changing -- only the Elevator (which oddly is decreasing by exactly 10 each time!?).

The interval of 160-170 mSecs (the number on the left is time in mSecs) is suspiciously like FSX though -- it scans devices at 6Hz (much less frequently, in fact, than the default in FSUIPC4, which is 100 Hz!). So I am unclear on this. See if the logging is the same with that other helicopter -- maybe it is that aircraft you have loaded which is doing this.

I'm sorry, but I have reached the limit of my ability to help you. All I can say is that the problem is NOT to do with FSUIPC, It is either something set in FSX or the aircraft or some other add-on you are using. Now it is time for you to do some elimination. You have the tools -- the logging with Axis events logged will show you, as i have explained.

One experiment you CAN try in FSUIPC4 is to set the [JoystickCalibration] option

UseAxisControlsForNRZ=No

in the INI file to Yes. Maybe this add-on expects the "AXIS_ ..." controls only and if it doesn't see them does this crazy reset action. Being a helicopter with only one "throttle" (actually treated as collective I think), it may not even like the separate throttle 1 and 2 controls in any case.

I suspect you may have to start using Profiles properly so that different things apply to different aircraft according to their needs.

Regards

Pete

[Griphos]

No. Just disable the controllers and re-test. That will prove it to you.

You haven't got any log options selected this time, that's why! I don't know why you turned them off.

I didn't turn them off. They weren't ever on. The first time I logged, I had to check some of them, which is why I thought I needed to push new log. I will try it with the controller disabled in FSX and see if that makes a difference.

I will try the joystick calibration option you suggested as well.

I've not ever said that FSUIPC is causing the problem. However, it is FSUIPC that isn't working. The helicopter works just fine when the axis is controlled by FSX.

I'm sure your program is excellent. Many people like it. I've certainly had wonderful advantage from it with all the other payware I've used that utilizes it. However, the tone of your support is making me regret my purchase. I suppose I'm just not used to being treated as if I am stupid, and accused of doing things I have not done and ignoring things I have not ignored.

[Pete Dowson]

I didn't turn them off. They weren't ever on. The first time I logged, I had to check some of them, which is why I thought I needed to push new log.

When they are turned on, they stay on for all further sessions until you turn them off. You had them on in the first log you posted. Then you posted a log with them off. Not sure where "new log" comes into it. I actually explicitly told you not to press it in the message asking you to enable the axis logging.

I've not ever said that FSUIPC is causing the problem. However, it is FSUIPC that isn't working. The helicopter works just fine when the axis is controlled by FSX.

FSUIPC is simply doing what you ask of it. It isn't doing the other stuff which is what is messing things up. You cannot say "FSUIPC isn't working". It's a tool, it does what you tell it to do.

However, the tone of your support is making me regret my purchase. I suppose I'm just not used to being treated as if I am stupid, and accused of doing things I have not done and ignoring things I have not ignored.

The "tone"? I am absolutely trying my best, under pressure as I am trying to get ready to leave on Friday for three weeks. I am honestly frustrated by the lack of success, but I am doing my damnest. It's just that each time I suggest something the response comes back with something done differently to my suggestion. If only you'd take just a little more care. I quite understand if you are completely unfamiliar with computers, but you must realise they don't really understand anything, they just do what they are told.

if you scan throughg this Forum you will see I try to, and normally achieve, the best and fastest support you are likely to see anywhere, and I am deeply hurt by your accusations.

I am afraid we have reached an impasse with virtually no time now for me to help further until after 5th November. I respectfully suggest there is something very odd about that "Dodo" and perhaps you will get more help from other users?

Sad Regards

Pete

[Griphos]

I am not completely unfamiliar with computers. I'm actually quite computer literate for a lay person. I'm completely unfamiliar with FSUPIC, having just bought it. I'm not a software engineer. I'm not thick. Again, I haven't been suggesting there is a problem with FSUIPC, merely that I don't appear to have things set up correctly, despite having followed the guide and instructions to the best of my ability. I am also genuinely disappointed that this isn't a problem that has a clear and readily known solution. And that it appears to be limited to one aircraft that no one else, as far as I can tell, has experienced trouble with.

The key bit for me is that when I open FSUIPC and move throttle axis#X, throttle axis#Y is detected and vice versa. That doesn't seem to be correct behavior to me.

Perhaps the fault is partially my own as I'm trying to work with you today before you leave even though I'm needing to work at the same time. So both of us are rushed. I do appreciate the speed of your support. I do still think the tone could use some work.

I realize you may not be able to respond, but I disabled the controller and tried again and I have the exact same behavior. So, I'm not sure what was "proved" by that. I've posted some of the log below. The elevator still appears to be doing weird things, even with the controller disabled in FSX. I tried changing the .ini file as suggested as well. No luck. I will continue to work ont his while you are gone, obviously, but since the problem continues even with the controller disabled in FSX, it seems clearly to be an issue either with this particular aircraft (which I've not been able to find generally) or with my setup of FSUIPC.

----------------

790926 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

790926 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -220 (0xffffff24) AXIS_ELEVATOR_SET

790926 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

790926 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET

790926 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

791082 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

791082 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET

791082 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

791082 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET

791082 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

791253 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

791253 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET

791253 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

791253 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET

791253 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

791409 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

791409 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET

791409 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

791409 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET

791409 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

791581 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

791581 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET

791581 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

791581 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET

791581 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

791752 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

791752 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET

791752 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

791752 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET

791752 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

791908 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

791908 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -207 (0xffffff31) AXIS_ELEVATOR_SET

791908 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

791908 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET

791908 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

792080 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

792080 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET

792080 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

792080 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET

792080 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

792252 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

792252 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET

792252 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

792252 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET

792252 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

792423 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

792423 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -202 (0xffffff36) AXIS_ELEVATOR_SET

792423 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

792423 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET

792423 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

792595 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

792595 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -200 (0xffffff38) AXIS_ELEVATOR_SET

792595 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

792595 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET

792595 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

792751 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

792751 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET

792751 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

792751 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET

792751 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

792922 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

792922 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET

792922 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

792922 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET

792922 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

793094 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

793094 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -196 (0xffffff3c) AXIS_ELEVATOR_SET

793094 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

793094 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET

793094 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

793266 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

793266 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -195 (0xffffff3d) AXIS_ELEVATOR_SET

793266 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET

793266 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16202 (0x00003f4a) AXIS_PROPELLER_SET

793266 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET

793437 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET

793437 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET

[Pete Dowson]

Briefly:

Try leaving the logging as you have it, and load a different aircraft -- maybe that other help you have. If you then don't get those 6 hz repeating batch of 5axis controls, you know it MUST be the Dodo. The try their support.

Sent on my phone

PS i try not to inject any tone into my replies, they are purely technical. I'm sorry you read them otherwise and even accuse me of accusing you of things which,if you read more carefully you'll find is not so.

Bye, and good luck!

Regards

Pete (no Ph.D I'm afraid

[Pete Dowson]

Also try removing that throttle Lu's file, temporarily

Pete

Sorry about typos -- horrible keyed on phone

[Griphos]

That is helpful. I loaded the Aerosoft Huey, and only got logging for Throttle1 and it logged smooth and appropriate operation. So, even though there is still something odd about moving one axis when in the Axis Assignment page and having its neighbor always pop up, it does appear that there is something fishy in Dodoland. I have posted on their support forum.

And, yes, I thought about removing the throttle lua to test, and will do that now as well.

PS:

But you've not bothered to scroll down to the single throttle axis,That's the one which is doing the damage! "AXIS_THROTTLE_SET" is the single throttle axis which is obviously assigned in your FSX -- as I can see in the Log along with those other axes I listed. If it isn't assigned on this controller, it most certainly is on another...And you certainly aren't ensuring that you have no conflicting assignments in FSX!

[Pete Dowson]

PS:

Not sure why you posted that Ps. I was referring to your "proof", i.e the picture you posted, which didn't show the single throttle axis at all.

I've finished for now. i'll have a little time tomorrow and I'll check back, but I don't think there's anything else I can do from here. Maybe the Dodo people can get in touch with me after I get back if there's some conflict with their product. Or maybe other users know the answers.

Pete

[Griphos]

Sorry, I was going to say something and then decided against it and thought I'd deleted it, but obviously left the quote. I'm a bit stressed today as well and could be reading more "tone" than is there.

Anyway, since the general throttle axis was sending signals even though it wasn't assigned, I created a profile for the Dodo and mapped Axis#X to general throttle instead of throttle 1. It works. It's still logging those five inputs at regular intervals, but that doesn't seem to be interfering with correct operation. It's clearly something the Dodo is doing. I'm just glad to be able to use the Dodo again and continue to use FSUIPC to map those axes so I can use the excellent throttle script by PilotJohn for my turboprops.

Thanks for your attention and help.

[Andydigital]

The DODO uses some very sophisticated FBW techniques and flight model tricks to enhance the very poor helicopter flight dynamics in FS, this is probably why you are seeing strange outputs in the FSUIPC logs that Pete asked for. I've been using the DODO since 2009 in FSX with the axes assigned through FSUIPC with no problems at all.

Here is my AXIS section for the DODO, you will see that it uses all the standard "AXIS Elevator Set" etc, control surface commands.

[Axes.Dodosim B206]
0=BX,256,F,65763,0,0,0
1=BY,256,F,65762,0,0,0
2=RR,256,F,65764,0,0,0
3=PX,256,D,4,0,0,0
4=PY,256,D,5,0,0,0
5=AZ,256,F,65765,0,0,0
6=AR,256,F,66291,0,0,0[/CODE]

[i]EDIT: Deleted last paragraph and replaced with this.[/i] You should have always assigned to the general throttle command, Throttle 1 is not used by the DODO, you should only ever assign to the throttle 1 command in a single engined craft when specifically told to so. Otherwise you should always use the general throttle command as a preference in single engined aircraft.

[Griphos]

Thanks for the reply Andy and for the info from your .ini.

As I said, I'm new to the full version of FSUIPC, so am not used to being able to set up different controls for different aircraft, which is certainly a very nice feature (and one I'm sure to start taking more advantage of). So, I had to assign throttle1 as my main throttle for all aircraft since I needed it for some aircraft, and it was not possible to assign it to only those aircraft using FSX controls short of creating several standard.cfg files and a batch file for swapping them, as far as I know. That was too big a pain to contemplate. Since I have never had a problem as a result in all my many years of simming, it didn't occur to me that might be the issue. In fact, it always worked fine with the DODO when FSX was controlling the axis, and fine with all my other helos even with FSUIPC controlling.

Don't know if I would have ever thought of it if Pete hadn't deciphered the log for me and shown that the sim or the DODO was sending inputs from the main throttle axis even though it wasn't assigned.

But that's the point and the value of these forums.