Constantly Needing to Calibrate Pedals

[amnz]

Dear Pete,

 

I have to keep on re-calibrating my PFC Cirrus GA pedals every 3 minutes to get them to function normally. Even when I am not touching the pedals, the rudder will automatically jar to one side in the sim and then re-centre (but it doesn't re-centre all the time) This obviously is a very frustrating problem.

 

In FSUIPC (4.907 with PFCHID 1.32) I have set my delta value in the axis assignment tab up to 256 and I still get the same issue. Furthermore, in the joystick calibration section the 'in' and 'out' values constantly fluctuate.

 

I really hope it isn't the potentiometer on the pedals that is wearing out- i've barely had time to use them!

 

Please help if you can :)

[Pete Dowson]

I have to keep on re-calibrating my PFC Cirrus GA pedals every 3 minutes to get them to function normally. Even when I am not touching the pedals, the rudder will automatically jar to one side in the sim and then re-centre (but it doesn't re-centre all the time) This obviously is a very frustrating problem.

 

 

 

Re-calibrating to the same values does nothing whatsopever. The values are stored both in memory and in the INI file. They are not lost!

The symptoms you mention are always either due to conflicting assignments (i.e. another axis assigned to the same function, maybe in FSUIPC or maybe in FS), or to a bad connection either withing the device or in its USB connections.

 

In FSUIPC (4.907 with PFCHID 1.32) I have set my delta value in the axis assignment tab up to 256 and I still get the same issue. Furthermore, in the joystick calibration section the 'in' and 'out' values constantly fluctuate.

 

 

That confirms my assessment above.

 

FSUIPC does have "spike" elimination options (see Miscellaneous options tab), but these only eliminate the very extreme values, due often to sudden temporary loss of power or connection. However, your symptoms do sound much more like conflicting assignments.

 

If you have disabled controllers in FSX completely and still get this, show me your FSUIPC4.INI file. You may have some previous assignments you have not removed.

 

Pete

[amnz]

[Axes]

0=1R,256,D,3,0,0,0

1=1U,1,D,7,0,0,0

2=1V,1,D,8,0,0,0

3=17X,1

4=17X,B,13545,16383,66030,0

5=17X,B,-14578,-11998,66029,0

6=17Y,256,D,10,0,0,0

7=17Z,1,D,4,0,0,0

8=17R,256,D,18,0,0,0

9=17U,1,D,26,0,0,0

10=17V,256,D,14,0,0,0

 

[MacroFiles]

1=PFCCUB

 

[Profile.cub]

1=A2A Piper Cub

 

[JoystickCalibration.cub]

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

Throttle=-16384,16383

LeftBrake=-16384,15609

SlopeLeftBrake=-5

RightBrake=-16384,15222

SlopeRightBrake=-5

Aileron=-16384,0,0,16383

Elevator=-16384,0,0,16383

Rudder=-2024,1248,1280,2144

 

[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

Rudder=-1960,2304,2496,3904

 

[Keys]

1=32,8,66734,0

[Pete Dowson]

Only odd thing there is

 

6=17Y,256,D,10,0,0,0

7=17Z,1,D,4,0,0,0

 

 

17Z is assigned to the generic all-engine throttle, and 17Y to Throttle 2. I would think they'd conflict.

 

There's only one assignment here ot rudder, so either you also have assignments in FSX 9you don't mention whether you've disabled controllers in FSX), or it is a connection problem.

 

Pete

 

[amnz]

I have disabled controllers in FSX. So its a mechanical problem to do with the pedals in this case?

 

 

NOTE: Is it normal for the max value in joystick calibration tab to have a value of over 4000??? Almost everything else, the max value is around 1683...

[Pete Dowson]

I have disabled controllers in FSX. So its a mechanical problem to do with the pedals in this case?

 

 

Maybe, or just wiring. But first check that you have no other drivers trying to process the device before it gets to FS.

 

NOTE: Is it normal for the max value in joystick calibration tab to have a value of over 4000??? Almost everything else, the max value is around 1683...

 

 

The INPUT values for nearly all modern devices range from -16380 or so to +16380 or so. They have digital or optical readers, not so much old fashioned resistance based pots. The latter may have large or small ranges, varying quite a lot according to quality, wiring and things like temperature and actual voltage levels.

 

Pete

[amnz]

Well I think I found the golden solution for anyone who may have a similar problem!

 

There are 2 holes on top of the casing that houses all the circuitry- just blast some air in them et voilà, problem solved!!! Who knew dust would be able to screw up some rudder pedals.