Jump to content
The simFlight Network Forums

Throttle calibration problem


Recommended Posts

I have 2 Saitek TQs in my simpit. The first 2 axes on the first TQ are behaving strangely in FSX(FSUIPC 4.859d).

The Windows calibration tool(Win7-64 bit) shows them behaving normally, a 50% movement of the axis produces a 50% movement in the game controller window, 75% gives 75% and so on.

However in FSUIPC the calibration does not follow this profile. A 99% movement of the axis stick causes the calibration in FSUIP to move fromm-16384 to 0, the last 1% movement of the axis causes FSUIPC caplibration togo from0 to+16384. The 3rd axis on that TQ behaves normally, as do other 3 on the 2nd TQ. This applies to any profile I try to use.

I think this is caused by me calibrating wrongly somewhere so I deleted the axis calibrations in the .ini file and redid them today. There is no change in the response.

Cleary I have overlooked something or done somthing wrong but cannot find it. Below is the (I hope!) relevant sections of the ini file for single engine profile but thebehavoir also occurs in the twin ingine profile as well.

Can you please tell me what I have done wrong!!

Thanks


[JoyNames]
AutoAssignLetters=Yes

A=CH PRO PEDALS USB

B=CH FLIGHT SIM YOKE USB
C=Saitek Pro Flight Throttle Quadrant
D=Saitek Pro Flight Throttle Quadrant
E=BU0836X Interface
0=Saitek Pro Flight Throttle Quadrant
0.GUID={EB167160-31F5-11E0-8005-444553540000}
2=CH PRO PEDALS USB
2.GUID={EB164A50-31F5-11E0-8003-444553540000}
4=BU0836X Interface
4.GUID={EB16E690-31F5-11E0-800C-444553540000}
1=CH FLIGHT SIM YOKE USB
1.GUID={EB164A50-31F5-11E0-8004-444553540000}
3=Saitek Pro Flight Throttle Quadrant
3.GUID={EB167160-31F5-11E0-8006-444553540000}
F=<< MISSING JOYSTICK >>
[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=No
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=Both
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
UseAxisControlsForNRZ=No
ElevatorTrim=-16380,-64,-64,16380/8
Aileron Trim=-16380,-488,230,16380
Rudder=-16380,0,0,16380
Rudder Trim=-16380,-262,0,16380
LeftBrake=-16380,16380/16
RightBrake=-16380,16380/16
SlopeAileron Trim=-6
SlopeRudder Trim=-6
Aileron=-16380,-1430,3200,16380
Elevator=-16380,-1944,4543,15695
Throttle=-16380,16380

[Axes]
1=BX,256,D,1,0,0,0
2=BY,256,D,2,0,0,0
3=AX,256,F,66387,0,0,0
4=AY,256,F,66388,0,0,0
5=AZ,256,D,3,0,0,0
9=EX,256,D,28,0,0,0
10=EY,256,D,27,0,0,0
11=EZ,256,D,21,0,0,0
12=EU,256,D,4,0,0,0

[Profile.Single engine piston]
1=Cessna Skyhawk 172SP Paint2
2=Cessna Skyhawk 172SP Paint3
3=Cessna Skyhawk 172SP Paint1
4=SIAI-Marchetti SF.260 Left G-AERO
5=SIAI-Marchetti SF.260 Left White
6=Commercial Level Simulations -- Piper PA-28R-200 Arrow II black
7=Cessna Grand Caravan Paint2
8=Commercial Level Simulations -- Piper PA-28R-200 Arrow II Red
9=Chipmunk
10=Commercial Level Simulations -- Piper PA-28R-200 Arrow II grey
11=Mooney Bravo Retro
12=Auster J1 Autocrat G-AGTO
13=Hurricaneiv
14=Commercial Level Simulations -- Piper PA-28R-200 Arrow II Light Blue
15=Beech_p35
16=PT-19
17=CIX Chipmunk CHIP4
18=DH82A Cix VFR Club G-BRSJ
19=CIX Chipmunk CHIP6
20=CIX Chipmunk CHIP1
21=Beech_p35b
22=Cessna Skyhawk 172SP Paint4
23=Auster J1 Autocrat G-JAYI
24=Beech_p35b
25=CIX Chipmunk CHIP4
26=AeropraktFoxbat.1
[Axes.Single engine piston]
0=CX,256,D,4,0,0,0
1=CY,256,D,5,0,0,0
2=CZ,256,D,6,0,0,0
3=BX,256,D,1,0,0,0
4=BY,256,D,2,0,0,0
5=AX,256,F,66387,0,0,0
6=AY,256,F,66388,0,0,0
7=AZ,256,D,3,0,0,0
8=EX,256,F,66732,0,0,0
9=EY,256,D,27,0,0,0
10=EZ,256,D,21,0,0,0
[JoystickCalibration.Single engine piston]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=No
ExcludeMixtureSet=No
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=Both
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
Aileron Trim=-16380,-512,512,16380
Rudder Trim=-16380,-2123,1281,16380/8
ElevatorTrim=-16380,-512,512,16380
Rudder=-16380,-774,774,16380/8
LeftBrake=-16380,16380/16
RightBrake=-16380,16380/16
SlopeLeftBrake=15
SlopeRightBrake=15
Aileron=-16380,-3901,4992,16380/8
Elevator=-16380,-1666,4406,16380/8
SlopeRudder Trim=6
Throttle=-16380,-258
PropPitch1=-16384,0,0,0/32
PropPitch=-16380,-323
Mixture=-16380,16380
[/CODE]

Link to comment
Share on other sites

I have 2 Saitek TQs in my simpit. The first 2 axes on the first TQ are behaving strangely in FSX(FSUIPC 4.859d).

The Windows calibration tool(Win7-64 bit) shows them behaving normally, a 50% movement of the axis produces a 50% movement in the game controller window, 75% gives 75% and so on.

However in FSUIPC the calibration does not follow this profile. A 99% movement of the axis stick causes the calibration in FSUIP to move fromm-16384 to 0, the last 1% movement of the axis causes FSUIPC caplibration togo from0 to+16384. The 3rd axis on that TQ behaves normally, as do other 3 on the 2nd TQ. This applies to any profile I try to use.

I think this is caused by me calibrating wrongly somewhere so I deleted the axis calibrations in the .ini file and redid them today. There is no change in the response.

It is not related to fSUIPC at all. It is a really well-known bug in the Saitek installation and is fixed by a Registry change. Please check the Saitek support site. I really cannot support their products.

Regards

Pete

Link to comment
Share on other sites

Pete

thanks for that, I have tried the fix on their website, tried unplugging the TQ and deleting all entries in the .xml file and allowing fsx to rebuild it. All to no avail.

I have contacted them for a solution.

Thanks for your help.

Den

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.