CHTQ Axis detection issue

[ZK-CAV]

Hi Peter

Wondering if you can help me please. I downloaded, installed and registered FSUIPC4.2 yesterday and have found an issue with it. So found 4208 and installed that too but made no change to my problem. Have searched and haven't found anything similar after on this BBS and have I have RTFM.

I can calibrate all but 1 of the axis on my CH Throttle Quadrant. I'm running FSX SP2 (Acceleration) under Vista 32 bit OS.

What happens with the axis action and set to direct for "mixture 1" and see movement on the axis under axis assignment tab so it can be assigned from the drop down munu, but when I go to the next tab to calibrate it no movement is detected hence I can't calibrate it. I've assigned another lever to this action and the same thing happens hence I believe the issue is with the assignment from the drop down menu to select axis for mixture 1.

Any ideas please?

Thanks Paul

[Pete Dowson]

What happens with the axis action and set to direct for "mixture 1" and see movement on the axis under axis assignment tab so it can be assigned from the drop down munu, but when I go to the next tab to calibrate it no movement is detected hence I can't calibrate it. I've assigned another lever to this action and the same thing happens hence I believe the issue is with the assignment from the drop down menu to select axis for mixture 1.

I'm afraid I cannot reproduce any such problem here, so I think the issue must be more complex than you say. I am assuming that you definitely have got "Direct to FSUIPC" selected, because the symptom does sound very much like the usual problem with FS assignments of the Mixture axis being defaulted with zero sensitivity. Just to cross check, when you press the top left "Set" button in the Mixture1 calibration section, it does say "(direct!)" against "Mixture1" doesn't it?

To start with, as well as trying other axes on Mixture1 have you tried the same axes on other functions? Perhaps you could list the assignments you've made -- or, better, show me the [Axes] and [JoystickCalibration] sections from the FSUIPC4.INI file (which you'll find in the FSX Modules folder).

Regards

Pete

[ZK-CAV]

Hi Pete

Thanks for the reply.

I am assuming that you definitely have got "Direct to FSUIPC" selected, because the symptom does sound very much like the usual problem with FS assignments of the Mixture axis being defaulted with zero sensitivity. Just to cross check, when you press the top left "Set" button in the Mixture1 calibration section, it does say "(direct!)" against "Mixture1" doesn't it?

Correct

To start with, as well as trying other axes on Mixture1 have you tried the same axes on other functions?

Again Correct - I've tried each of the levers/axis on the TQ to each of the functions and so far the only issue is mixture1 regardless of which axis is assigned.

because the symptom does sound very much like the usual problem with FS assignments of the Mixture axis being defaulted with zero sensitivity.

Never had that problem before so here is the ##.ini file in which I note mixture1 one does not appear. which for some reason I can't attach so have to put it here sorry.

[General]

History=5YMD5BHJ0PKKUL1P9NF0V

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

WeatherReadFactor=2

WeatherRewriteDelay=10

ProcessGlobalWeather=No

SimConnectStallTime=1

GraduatedVisibility=No

LowerVisAltitude=0

UpperVisAltitude=0

UpperVisibility=0

MinimumVisibility=0

MaximumVisibilityFewClouds=0

MaximumVisibility=0

MaximumVisibilityOvercast=0

MaximumVisibilityRainy=0

SetVisUpperAlt=No

VisUpperAltLimit=0

ExtendMetarMaxVis=No

OneCloudLayer=No

CloudTurbulence=No

CloudIcing=Yes

GenerateCirrus=Yes

SuppressCloudTurbulence=No

MaxIce=-4

MinIce=-4

UpperWindGusts=No

SuppressWindTurbulence=No

WindTurbulence=Yes

SuppressAllGusts=No

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

WindSmoothing=No

WindSmoothness=2

WindSmoothAirborneOnly=Yes

DisconnTrimForAP=No

ZeroElevForAPAlt=No

ThrottleSyncAll=No

WhiteMessages=No

ShowPMcontrols=No

SpoilerIncrement=512

MagicBattery=No

RudderSpikeRemoval=Yes

ElevatorSpikeRemoval=Yes

AileronSpikeRemoval=Yes

ReversedElevatorTrim=No

ClockSync=No

ClockSyncMins=5

ClearWeatherDynamics=No

FixWindows=No

OwnWeatherChanges=No

TimeForSelect=4

LoadFlightMenu=No

LoadPlanMenu=No

PauseAfterCrash=No

ZapSound=firework

ShortAircraftNameOk=No

FixControlAccel=No

LogAxes=Yes

[WideServer]

WideFSenabled=Yes

[GPSout]

Port=

Speed=4800

Interval=1000

PosTo6Decimal=Yes

Sentences=

GPSoutEnabled=No

[AutoSave]

AutoSaveEnabled=No

[JoystickCalibration]

ExclThrottleSet=No

SepRevsJetsOnly=No

ApplyHeloTrim=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=-16380,16380

LeftBrake=-14563,14592/16

RightBrake=-14693,14592/16

Throttle1=-16384,-15733,-15473,16383

Throttle2=-16384,-15473,-15213,16380

Reverser1=-16380,16380

ElevatorTrim=-16380,-512,512,16380

SlopeElevatorTrim=2

Spoilers=-16380,16380

Mixture2=-16384,-15993,-15733,16383

PropPitch1=-16384,-15733,-14173,16383

PropPitch2=-16384,-15733,-14173,16383

Aileron=-16253,-910,1152,16256

Elevator=-16384,-1040,1536,16256

Rudder=-16384,-390,256,16383

[Axes]

0=0X,256,D,3,0,0,0

1=1X,256,D,9,0,0,0

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

3=1Z,256,D,17,0,0,0

4=1R,256,D,18,0,0,0

5=1U,256,D,14,0,0,0

6=1V,256,D,13,0,0,0

[Axes.Beech Baron 58 Paint1]

0=0X,256,D,3,0,0,0

1=1X,256,D,9,0,0,0

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

3=1Z,256,D,17,0,0,0

4=1R,256,D,18,0,0,0

5=1U,256,D,14,0,0,0

6=1V,1,D,13,0,0,0

[Axes.Beech Baron 58]

0=0X,256,D,7,0,0,0

1=0Y,256,D,8,0,0,0

2=0Z,256,D,3,0,0,0

3=1X,256,D,13,0,0,0

4=1Y,256,D,14,0,0,0

5=1Z,256,D,9,0,0,0

6=1R,256,D,10,0,0,0

7=1U,256,D,18,0,0,0

8=1V,256,D,17,0,0,0

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

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

Regards Paul

[Pete Dowson]

.... here is the ##.ini file in which I note mixture1 one does not appear. which for some reason I can't attach so have to put it here sorry.

In the Axes assignments you have some slight oddities, though I've tested with identical ones here and found no problem.

[Axes]

0=0X,256,D,3,0,0,0

1=1X,256,D,9,0,0,0

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

3=1Z,256,D,17,0,0,0

4=1R,256,D,18,0,0,0

5=1U,256,D,14,0,0,0

6=1V,256,D,13,0,0,0

[Axes.Beech Baron 58 Paint1]

0=0X,256,D,3,0,0,0

1=1X,256,D,9,0,0,0

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

3=1Z,256,D,17,0,0,0

4=1R,256,D,18,0,0,0

5=1U,256,D,14,0,0,0

6=1V,1,D,13,0,0,0

[Axes.Beech Baron 58]

0=0X,256,D,7,0,0,0

1=0Y,256,D,8,0,0,0

2=0Z,256,D,3,0,0,0

3=1X,256,D,13,0,0,0

4=1Y,256,D,14,0,0,0

5=1Z,256,D,9,0,0,0

6=1R,256,D,10,0,0,0

7=1U,256,D,18,0,0,0

8=1V,256,D,17,0,0,0

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

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

The Delta of only 1 for the Mixture1 on the "Beech Baron 58 Paint1" may give some problems if there is any jitter at all on the axis, as it means every single change has to be read. I don't have any jitter on any axes I have so I couldn't test it, but it may be that the changes are causing FSUIPC to stick in a tight loop reading the values and never allowing Windows to redraw the displayed ones.

This is pure speculation, and assumes that the only aircraft you've tested with is that Baron with the white/blue paint scheme.

Your other Baron entry, highlighted above too, has the X/Y axes assigned to the Mixt1 and 2 instead of U/V, but it will never be used because the name is a short name and you still have this:

ShortAircraftNameOk=No

If you want that entry to be used for all the other Barons you'd need to change the option to "Yes" (or you could use the "Substring" option there and just use "Baron" as the name).

The other entry, [Axes] looks okay, so with other aircraft loaded I cannot see why there would be a problem at all. There certainly isn't here with exactly the same settings.

Regards

Pete

[ZK-CAV]

Hi Pete

Problem solved - thanks very much.

Changed the value highlighted in the .ini file to 256 and changed ShortAircraftNameOk=No to Yes end result is everything now works fine (only tested in the Barron so far).

The file was a bit odd due to the testing I've been doing I guess.

Thanks again - another satisfied customer.

Kind Regards Paul