Ch Throttle Quadrant

[craigy 20]

I have a problem with the CH Thrrottle Quadrant. I follow the steps to calibrate the throttles and when you move the throttles a small foward movement, power increases to 50% and retarding the throttles has no effect. Idle has to be restored using F1.

My CH joystick and rudder pedals work fine.

Any suggestions?

Craig

[Jonas S. 466]

Hey Craig,

So you are absolutely sure that your hardware works fine? This does only happen with the airbus? Do you have any configurations left in FSUIPC or something misleading in the FSX settings?

[Aerosoft Team [Inactive Account] 51558]

And have you read Vol 7 of the manuals?

[msagner 21]

Here's what I found out with my CH throttle quadrant, in combination with axis assignment via FSUIPC:

The two throttle levers on the left side of the throttle quadrant have a range from 0 .... +16383 (as displayed in the FSUIPC axis assignment dialog).

The Airbus needs a range of -16282 .... +16383, though.

The resulting behaviour is what is described above in post #1.

Solution:

Edit your FSUIPC.ini file (can be found in the FSX "modules" folder):

[Axes]
0=0X,256,F,66420,0,0,0,*2,-16383
1=0Y,256,F,66423,0,0,0,*2,-16383

The "0X" and "0Y" part may be different in your file, depending on what other USB control devices are installed on your machine.

The important thing is appending the parts printed in bold above.

What this does is, it scales the throttle output from 0 .... +16383 to the desired -16383 .... +16383.

Hope that helps (it did for me)

[Aerosoft Team [Inactive Account] 51558]

But that is exactly what calibration of the hardware does. It matches the movement to the +16383 <> -18383 values.

[craigy 20]

hi guys

Thanks for your responses. msagner, the throttles aren't managed by FSUIPC.

I have recently added a new ssd for windows and also have done a clean install of fsx but windows has misbehaving so I the computer is being checked. After Scholli4 comment I checked throttle behaviour using the PMDG 737 and throttle behaviour is the same so I suspect hardware issues. I will come back when I have more information

Cheers

Craig