Elevator axis becoming "invisible"

[northcape]

Hello Peter

I have been using the CH yoke, pedals and throttle quadrant calibrated with FSUIPC since 2004 without problems but over the last week or so I am experiencing problems with the Elevator axis that manifests in some payware aircraft but not in others.

In the Axis Assignment page I see in the "set minimum change here" boxes about 50% of the range of the numerical values - approx -16384 to approx 8448 but in the the Axis Calibration page in the boxes under the Reset button page I see no numerical change at all: throughout the full back and forth movement of the yoke the numbers shown are static and completely out of whack; for example 5721 to 5371

In the aircraft visual model (this appears in quality payware jets but not in other A/C) the Elevator movement is severely limited - lots of up but no down - and as I said - no movement in the numerical values in the "Set" section on the left.

This problem is new and all other axes (Aileron and Gear up/down on the yoke and all pedal and quadrant) work correctly.

I am completely at a loss as to why this is happening; all my configs are the same as ever (I backup and reinstall the FSUIPC .ini file after any OS or FS installs) and have no idea whether this is an A/C, FSUIPC or human problem.

Regards

Nicholas

[Pete Dowson]

In the Axis Assignment page I see in the "set minimum change here" boxes about 50% of the range of the numerical values - approx -16384 to approx 8448

There's only one "minimum change" box which should contain a small value, the "Delta" value, which tells FSUIPC to ignore changes smaller than that. You are confusing the Delta value with the simply input value monitoring.

... but in the the Axis Calibration page in the boxes under the Reset button page I see no numerical change at all: throughout the full back and forth movement of the yoke the numbers shown are static and completely out of whack; for example 5721 to 5371

If they are static, how can they change? Or am I misunderstanding something? If the axis is assigned correctly, the IN value will normally match the actual axis value shown in the axis assignments Tab. But if, for instance, you assign to the FS controls, it depends what controls you are assigning to and whether you have some add-on which is intercepting them. Therefore you need to state what exact option you are selecting for assignment, and which actual control (by name) you assign to.

In the aircraft visual model (this appears in quality payware jets but not in other A/C) the Elevator movement is severely limited - lots of up but no down - and as I said - no movement in the numerical values in the "Set" section on the left.

What if you press the "Reset" button in the calibration so the axis is no longer being calibrated by FSUIPC?

I am completely at a loss as to why this is happening; all my configs are the same as ever (I backup and reinstall the FSUIPC .ini file after any OS or FS installs) and have no idea whether this is an A/C, FSUIPC or human problem.

You said that it "manifests in some payware aircraft but not in others", so it must be related to the aircraft, mustn't it? Always test with default aircraft. If you are assigning to the the FS controls instead of "direct to FSUIPC calibration" then aircraft code can conceivably intercept and change them before they get to FSUIPC calibration.

Please, next time, state which version of FS and which version number of FSUIPC you are talking about. It always helps to know these things.

Regards

Pete

[ClaudeMan]

Hello Pete,

First time post, but have been using FSUIPC for years. Currently --- FSX (SP2 without Acceleration), FSUIPC Ver 4.664, and WIN7 (Service Pack 1) (x64).

My CH Flight Sim Yoke USB Aileron and Elevator Axes are calibrated with FSUIPC and I recently encountered similiar issues as reported by Nicholas. I suspect it has something to do with WIN7, Service Pack 1 and not FSUIPC.

Two days ago, I was unable to pitch up the LevelD 767 for take-off. The CH Flight SIM Yoke USB was essentially unresponsive. Sitting on the ground, in spot view, I could see the actual Elevator and Aileron deflections were only approximately 50% of full. In FSUIPC, the reported values for Aileron and Elevator were also approximately 50% of previous values. (Reverting to version 4.657, just to check, made no difference.) Re-calibrating in FSUIPC Ver 4.664 to these newer values restored full Aileron and Elevator deflection. BTW, observed similiar behavior with the FSX default Cessna 172's.

Here are the FSUIPC value differences (For now I did not attempt to change the middle values):

Before installing WIN7 Service Pack 1: Aileron=-16383,-512,512,16383

Elevator=-16383,-512,512,13472

After installing Win Service Pack1: Aileron=-7040,-512,512,6784

Elevator=-7040,-512,512,5056

Again, I think FSUIPC is functioning as intended, but Win7( SP1) and FSX are now reporting different values for the joystick axes.

Claude

[Pete Dowson]

Here are the FSUIPC value differences (For now I did not attempt to change the middle values):

Before installing WIN7 Service Pack 1: Aileron=-16383,-512,512,16383

Elevator=-16383,-512,512,13472

Well, the first shows pretty much uncalibrated default values. I'm surprised you've not calibrated properly and allowed some dead space at either extreme. And the default centre values are seldom correct for any axis.

After installing Win Service Pack1: Aileron=-7040,-512,512,6784

Elevator=-7040,-512,512,5056

I assume you've merely set the extremes again? not allowed a little dead space to account for variations as recommended?

Again, I think FSUIPC is functioning as intended, but Win7( SP1) and FSX are now reporting different values for the joystick axes.

You don't say where you've assigned these. If in FSX then its "sensitivity" slider will change the range FSUIPC sees. It needs to be on max. If it is, or you are assigning via FSUIPC, then all I think is happening is that you didn't re-calibrate in Windows "game controllers" after updating windows. It probably reset them, maybe even changed the drivers being used. Are they CH ones or Windows defaults?

Regards

Pete

[ClaudeMan]

Many thanks for your comments and suggestions. Went back and re-read the Joystick Calibration section of the doumentation. I'd advise others to do this from time to time.

The axes are assigned in FSX, however the Sensitivity/Null settings were incorrect. Re-calibrated both the Yoke and Rudder pedals in the Windows Game Controllers (outside FSX). Within FSX Set Sensitivity to Max and Null to Min, and then calibrated in FSUIPC.

Here are my results: (Will experiment a bit with the dead space settings.)

Aileron=-16061,-854,720,15814/8

Elevator=-16192,1550,2934,15962/8

Rudder=-15802,-2017,2130,15934

The CH Flightsim Yoke and Pedals are a Plug and Play driverless USB installation, so the drivers are Windows 7 defaults.

Claude

[Pete Dowson]

Here are my results: (Will experiment a bit with the dead space settings.)

Aileron=-16061,-854,720,15814/8

Elevator=-16192,1550,2934,15962/8

Rudder=-15802,-2017,2130,15934

That looks better. The elevator is a bit off-center -- maybe the pot has turned in its mounting -- but if it works smoothly enough both ways that shouldn't matter.

Regards

Pete

[ClaudeMan]

That looks better. The elevator is a bit off-center -- maybe the pot has turned in its mounting -- but if it works smoothly enough both ways that shouldn't matter.

Regards

Pete

I'm fairly certain the elevator pot is mis-aligned a bit along with possibly weakened springs, but it is smooth both ways so we're okay.

Thanks

Claude