Profile axis and Joystick Calibration

[bobbjoh]

Hi Pete, have a simple question. My LDS 767 has a profile setup in FSUIPC using my CHProducts yoke and pedals. Everything is working fine with the profile axis assignments, but the joystick calibration menu is not responding to any yoke or pedal movements. The plane is working just fine with control movements. The calibration menu was working but stopped last week. I have included the FSUIPC log: ********* FSUIPC4, Version 4.859m by Pete Dowson *********

Running inside FSX on Windows Vista

Module base=55D10000

User Name="Robert Johnson"

User Addr="bobbyjoh1@verizon.net"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

93 System time = 10/01/2013 11:51:59

93 FLT path = "C:\Users\Owner\Documents\Flight Simulator X Files\"

2667 Trying to connect to SimConnect Acc/SP2 Oct07 ...

2917 FS path = "F:\FSX\"

5506 LogOptions=00000000 00000001

5506 ### SIM1 base=20B70000, friction=20B71670

5506 SIM1 Frictions access gained and basic values patched

5756 Wind smoothing fix is fully installed

5756 G3D.DLL fix attempt installed ok

5756 SimConnect_Open succeeded: waiting to check version okay

5756 Trying to use SimConnect Acc/SP2 Oct07

5928 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

5928 Initialising SimConnect data requests now

5928 FSUIPC Menu entry added

5990 C:\Users\Owner\Documents\Flight Simulator X Files\EDDF.FLT

5990 C:\Users\Owner\Documents\Flight Simulator X Files\KJFK-EGLL.PLN

5990 F:\FSX\SimObjects\Airplanes\LVLD_B763_Winglet\B767-300.AIR

5990 C:\Users\Owner\Documents\Flight Simulator X Files\KJFK-EGLL.PLN

12885 Weather Mode now = Global

25303 ASE with WX requester detected

154425 Weather Mode now = Theme

154456 Weather Mode now = Global

154815 System time = 10/01/2013 11:54:33, Simulator time = 12:58:26 (11:58Z)

155345 Aircraft="Level D Simulations B767-300ER Winglet - Delta airlines NC (GE)"

156047 Starting everything now ...

156157 AES Link established

156703 Advanced Weather Interface Enabled

164269 Weather Mode now = Theme

164425 Weather Mode now = Global

186858 Sim stopped: average frame rate for last 35 secs = 6.1 fps

249820 **** No SimConnect events or states being received! Re-connecting now ... ****

249929 SimConnect_Open succeeded: waiting to check version okay

249960 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

249960 Initialising SimConnect data requests now

249960 FSUIPC Menu entry added

250022 C:\Users\Owner\AppData\Roaming\Microsoft\FSX\Previous flight.FLT

250022 C:\Users\Owner\Documents\Flight Simulator X Files\KJFK-EGLL.PLN

250381 C:\Users\Owner\Documents\Flight Simulator X Files\KJFK-EGLL.PLN

252035 System time = 10/01/2013 11:56:11, Simulator time = 12:59:15 (11:59Z)

8204810 Sim stopped: average frame rate for last 7953 secs = 15.7 fps

27649788 Sim stopped: average frame rate for last 19442 secs = 27.4 fps

35567650 Sim stopped: average frame rate for last 7917 secs = 20.8 fps

36035638 Sim stopped: average frame rate for last 449 secs = 6.2 fps

36180532 Sim stopped: average frame rate for last 101 secs = 6.9 fps

36210031 System time = 10/01/2013 21:55:29, Simulator time = 16:54:42 (21:54Z)

36210031 *** FSUIPC log file being closed

Average frame rate for running time of 35910 secs = 23.0 fps

G3D fix: Passes 275937, Null pointers 0, Bad pointers 0, Separate instances 0

Memory managed: 40419 Allocs, 40419 Freed

********* FSUIPC Log file closed ***********

What do you think would cause the celebration menu to stop working.

Bob Johnson

DTW

[Pete Dowson]

Hi Pete, have a simple question. My LDS 767 has a profile setup in FSUIPC using my CHProducts yoke and pedals. Everything is working fine with the profile axis assignments, but the joystick calibration menu is not responding to any yoke or pedal movements. The plane is working just fine with control movements. The calibration menu was working but stopped last week. I have included the FSUIPC log:

The log really tells me nothing about how you've assigned things, so I have no idea. The INI file is more relevant. The calibration tab merely receives values either direct from FSUIPC assignments or from FSX itself. In either case, if the axes are calibrated and it never sees them it wouldn't pass them on, so nothing would work.

BTW this doesn't look good:

249820 **** No SimConnect events or states being received! Re-connecting now ... ****

249929 SimConnect_Open succeeded: waiting to check version okay

249960 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

249960 Initialising SimConnect data requests now

249960 FSUIPC Menu entry added

250022 C:\Users\Owner\AppData\Roaming\Microsoft\FSX\Previous flight.FLT

250022 C:\Users\Owner\Documents\Flight Simulator X Files\KJFK-EGLL.PLN

250381 C:\Users\Owner\Documents\Flight Simulator X Files\KJFK-EGLL.PLN

Something is stalling FSX so much that SimConnect can't send data to FSUIPC for a significant period. Maybe this is related? where, in the timeframe of the log, were you trying to use the Calibration tab? What about the next load of FS?

What do you think would cause the celebration menu to stop working.

Nothing speciifcally I know of, expecially if the axes are assigned in FSUIPC "direct to calibration". If assigned to FS controls, in FS or in FSUIPC, then the calibration depends upong intercepting controls via Simconnect, and if you are getting SimConnect stalling i suppose all sorts of weird things might result.

Regards

Pete

[bobbjoh]

Hi Pete,

Here is the .ini file:

[General]

UpdatedByVersion=4859m

History=9OVKOY248A4WU7XMPRL68

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

FixControlAccel=No

FixMachSpeedBug=No

VisibilityOptions=No

OneCloudLayer=No

CloudTurbulence=No

CloudIcing=No

GenerateCirrus=No

SuppressCloudTurbulence=No

MaxIce=-4

MinIce=-4

UpperWindGusts=No

SuppressWindTurbulence=No

SuppressWindVariance=No

WindTurbulence=No

TurbulenceRate=1.0,5.0

TurbulenceDivisor=20,20,40,40

SuppressAllGusts=No

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

SmoothBySimTime=No

WindSmoothing=No

WindSmoothness=2

WindSmoothAirborneOnly=Yes

PressureSmoothness=0

TemperatureSmoothness=0

DisconnTrimForAP=No

ZeroElevForAPAlt=No

ThrottleSyncAll=No

WhiteMessages=No

ShowPMcontrols=No

SpoilerIncrement=512

MagicBattery=No

RudderSpikeRemoval=No

ElevatorSpikeRemoval=No

AileronSpikeRemoval=No

ReversedElevatorTrim=No

ClockSync=No

ClockSyncMins=5

ClearWeatherDynamics=No

OwnWeatherChanges=No

TimeForSelect=4

LoadFlightMenu=No

LoadPlanMenu=No

PauseAfterCrash=No

BrakeReleaseThreshold=75

SaveDataWithFlights=Yes

ZapSound=firework

ShortAircraftNameOk=No

UseProfiles=Yes

EnableMouseLook=No

AxesWrongRange=No

TCASid=Flight

TCASrange=80

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

InitDelay=0

GetNearestAirports=Yes

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=4

LuaRerunDelay=66

Console=No

DeleteVehiclesForAES=Yes

MouseWheelMove=No

AutoScanDevices=Yes

OOMcheck=Yes

!1=DeleteVehiclesForAES

InitDelayDevices=Yes

InitDelayDevicesToo=No

PatchSIM1friction=Yes

MapSIM1Coefficients=Yes

!1=Wheel values: 25 sets of 8 FLOAT32 values starting at offset 0xA000

!2=Braking values: 25 sets of 4 FLOAT32 values starting at offset 0xA400

AdvDisplayHotKey=65,8

FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0

SimConnectUsed=10.0.61259.0

[JoyNames]

AutoAssignLetters=No

0=CH Pro Pedals USB

0.GUID={C89E3F00-2687-11E1-8003-444553540000}

1=CH Flight Sim Yoke LE

1.GUID={C8A0B000-2687-11E1-8004-444553540000}

[buttons]

Buttonrepeat=20,10

1=P1,3,C1008,30

0=P1,9,C65615,0

[AutoSave]

Next=1

Interval=60

Files=10

SaveOnGround=No

AutoSaveEnabled=No

[GPSout]

GPSoutEnabled=No

[GPSout2]

GPSoutEnabled=No

[WideServer]

WideFSenabled=Yes

[sounds]

Path=F:\FSX\Sound\

Device1=Primary Sound Driver

Device2=Speakers (High Definition Audio Device)

[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

Aileron=-16380,0,0,16380

Elevator=-16380,0,0,16380

Rudder=-16380,0,0,16380

Throttle=-16380,16380/16

[Profile.Level D 767]

1=Level D Simulations B767-300ER Winglet - Delta airlines NC (GE)

2=

[Axes.Level D 767]

0=0X,256,F,66387,0,0,0

1=0Y,256,F,66388,0,0,0

2=0Z,256,F,65764,0,0,0

3=1X,256,F,65763,0,0,0

4=1Y,256,F,65762,0,0,0

5=1Z,256,F,65765,0,0,0

[JoystickCalibration.Level D 767]

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

Aileron=-16380,-512,512,16380

Elevator=-16380,-512,512,16380

Rudder=-16380,-512,512,16380

Throttle=-16380,16380

RightBrake=-16384,15488/16

LeftBrake=-16380,16380/16

[buttons.Level D 767]

0=P1,34,C65606,0

1=P1,2,C1008,0

[window.Radar Contact]

Docked=1826, 6993, 3575, 1759

[Pete Dowson]

Here is the .ini file:

I don't see anything there which would cause such a problem, though it is perhaps a little worrying, presuming that you have Controllers disabled in FS, that you only have axes assigned for the one aircraft only in the one livery. You have no default assignments, which is very ununsual. If you load a different aircraft you'd have no controls until you assigned them. This is even odder when you see that you do have default calibrations even though there are no assignments which could be calibrated that way.

I would strongly recommend some tidy up and a little more flexibility adding, as follows:

In

[General]

change

ShortAircraftNameOk=No

to

ShortAircraftNameOk=Substring

and delete these strange lines -- I don't know how they arose at all!

!1=DeleteVehiclesForAES

!1=Wheel values: 25 sets of 8 FLOAT32 values starting at offset 0xA000

!2=Braking values: 25 sets of 4 FLOAT32 values starting at offset 0xA400

Then change the Profile definition so it applies to all the Level D 767s:

[Profile.Level D 767]

1=Level D Simulations B767

Add a copy of the 767 axes section with the title [Axes] so that you have some default axis assignments, thus:

[Axes]

0=0X,256,F,66387,0,0,0

1=0Y,256,F,66388,0,0,0

2=0Z,256,F,65764,0,0,0

3=1X,256,F,65763,0,0,0

4=1Y,256,F,65762,0,0,0

5=1Z,256,F,65765,0,0,0

Regards

Pete

[bobbjoh]

Thanks Pete for your suggestions, made them to clean up those items you mentioned. However the joystick calibration menu is still inactive. I checked that there are no controls set in FS. I am somewhat hesitant to make further changes since FSUIPC is working great on the LDS 767. Do you have any other suggestions? Thanks for any help

Bob

[Pete Dowson]

Thanks Pete for your suggestions, made them to clean up those items you mentioned. However the joystick calibration menu is still inactive. I checked that there are no controls set in FS. I am somewhat hesitant to make further changes since FSUIPC is working great on the LDS 767. Do you have any other suggestions?

The only way there will be no "IN" values changing in the Calibration tab is if no axis values are arriving there to be calibrated. To test this simply enable the controllers again in FS and see.

I suggest you show me the current state of your INI file and explain, step by step,what you are doing and where, exactly, you think you should see activity yet are not.

Regards

Pete

[bobbjoh]

Hi Pete, I did enable one axis in the FS controls and the (ailerons) and they did start of work in the FSUIPC joystick calibration.

Here is my current ini file:

[General]

UpdatedByVersion=4859n

History=SAHKBKOQ8W0J43J9CE8T7

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

FixControlAccel=No

FixMachSpeedBug=No

VisibilityOptions=No

OneCloudLayer=No

CloudTurbulence=No

CloudIcing=No

GenerateCirrus=No

SuppressCloudTurbulence=No

MaxIce=-4

MinIce=-4

UpperWindGusts=No

SuppressWindTurbulence=No

SuppressWindVariance=No

WindTurbulence=No

TurbulenceRate=1.0,5.0

TurbulenceDivisor=20,20,40,40

SuppressAllGusts=No

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

SmoothBySimTime=No

WindSmoothing=No

WindSmoothness=2

WindSmoothAirborneOnly=Yes

PressureSmoothness=0

TemperatureSmoothness=0

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

OwnWeatherChanges=No

TimeForSelect=4

LoadFlightMenu=No

LoadPlanMenu=No

PauseAfterCrash=No

BrakeReleaseThreshold=75

SaveDataWithFlights=Yes

ZapSound=firework

ShortAircraftNameOk=Substring

UseProfiles=Yes

EnableMouseLook=No

AxesWrongRange=No

TCASid=Flight

TCASrange=80

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

InitDelay=0

GetNearestAirports=Yes

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=4

LuaRerunDelay=66

Console=No

MouseWheelMove=No

AutoScanDevices=Yes

OOMcheck=Yes

InitDelayDevices=Yes

InitDelayDevicesToo=No

PatchSIM1friction=Yes

MapSIM1Coefficients=Yes

AdvDisplayHotKey=65,8

DeleteVehiclesForAES=Yes

FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0

SimConnectUsed=10.0.61259.0

[JoyNames]

AutoAssignLetters=No

0=CH Pro Pedals USB

0.GUID={C89E3F00-2687-11E1-8003-444553540000}

1=CH Flight Sim Yoke LE

1.GUID={C8A0B000-2687-11E1-8004-444553540000}

[buttons]

Buttonrepeat=20,10

1=P1,3,C1008,30

0=P1,9,C65615,0

[AutoSave]

Next=1

Interval=60

Files=10

SaveOnGround=No

AutoSaveEnabled=No

[GPSout]

GPSoutEnabled=No

Port=COM1

Speed=4800

Interval=2000

PosTo6Decimal=No

SimModeIndicator=No

Sentences=

[GPSout2]

GPSoutEnabled=No

Port=<none set>

Speed=4800

Interval=2000

PosTo6Decimal=No

SimModeIndicator=No

Sentences=

[WideServer]

WideFSenabled=Yes

[sounds]

Path=F:\FSX\Sound\

Device1=Primary Sound Driver

Device2=Speakers (High Definition Audio Device)

[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

Aileron=-16380,0,0,16380

Elevator=-16380,0,0,16380

Rudder=-16380,0,0,16380

Throttle=-16380,16380/16

[Profile.Level D 767]

1=Level D Simulations B767-300ER Winglet - Delta airlines NC (GE)

2=Level D Simulations B767

[Axes.Level D 767]

0=0X,256,F,66387,0,0,0

1=0Y,256,F,66388,0,0,0

2=0Z,256,F,65764,0,0,0

3=1X,256,F,65763,0,0,0

4=1Y,256,F,65762,0,0,0

5=1Z,256,F,65765,0,0,0

[Axes]

0=0X,256,F,66387,0,0,0

1=0Y,256,F,66388,0,0,0

2=0Z,256,F,65764,0,0,0

3=1X,256,F,65763,0,0,0

4=1Y,256,F,65762,0,0,0

5=1Z,256,F,65765,0,0,0

[JoystickCalibration.Level D 767]

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

Aileron=-16380,-512,512,16380

Elevator=-16380,-512,512,16380

Rudder=-16380,-512,512,16380

Throttle=-16380,16380

RightBrake=-16380,16380

LeftBrake=-16380,16380/16

[buttons.Level D 767]

0=P1,34,C65606,0

1=P1,2,C1008,0

[window.Radar Contact]

Docked=1826, 6993, 3575, 1759

After I start FSX which is in the LDS 767 last saved postilion at the gate where I landed last, I go to the FSUIPC tab. When I open FSUIPC I first look at the axis settings which are in the LDS profile. They all work as programmed, then I click on the joystick calibration tab and when I move my yoke or pedals nothing moves. Now a week ago or a little more the calibration items would move and could be set. BTW I only fly the LDS 767, with AS2012 and Radar Contact.

Hope this gives you a little more info, as I said the plane flies great, but just this new strange behavior in the FSUIPC tab.

Thanks

Bob

[Pete Dowson]

Hi Pete, I did enable one axis in the FS controls and the (ailerons) and they did start of work in the FSUIPC joystick calibration.

Okay. So the normal Axis controls are being intercepted okay, and processed. So, let's look at your assignments:

[Axes.Level D 767]

0=0X,256,F,66387,0,0,0 Axis left brake set

1=0Y,256,F,66388,0,0,0 Axis right brake set

2=0Z,256,F,65764,0,0,0 Axis rudder set

3=1X,256,F,65763,0,0,0 Axis ailerons set

4=1Y,256,F,65762,0,0,0 Axis elevator set

5=1Z,256,F,65765,0,0,0 Axis throttle set

Now all those are the exact same ones which assignment in FS provides. No difference at all. The calibration routines should receive them identically no matter which way you assign them.

This raises another question, though. Why ARE you assigning axes in FSUIPC? You might as well assign in FS, as it would be more efficient in any case rather than have FSUIPC send these controls to FS and for FSUIPC thern to intercept them for calibration. Really assignment of axes to FS controls is either intended for those who want different assignments for different aircraft, or who prefer the greater efficiency of the "direct to calibration" assignments, which involves no messages going back and forth to FS nor interceptions.

I'm afraid I'm still at a loss to understand how your system is somehow working whilst the calibration cannot intercept the axis controls only whilst originating in FSUIPC. It relies on a function of SimConnect to make this happen and I'm now wondering if there's been some small corruption somewhere in that area. However, rather than try any reinstalling in your setup with which you are otherwise quite happy, I'd suggest one of two things:

Either reassign those controls to the direct equivalents, which involves unticking the current assignments, selecting "direct to calibration" mode just above, then reselecting in the drop downs.

Or deassign all axes in FSUIPC and assign in FS instead. Calibration is still valid. You could do this quickly by simply deleting the [Axes ...] sections in the INI.

Now a week ago or a little more the calibration items would move and could be set.

Hmm. I wonder what happened a week ago or so?

Pete

[bobbjoh]

Hi Pete and thanks for all the help inputs. The reason I moved from FS Controls to FSUIPC I was getting "line spikes" with the FS Controls and I never get them with FSUIPC. Other than is minor issue with the calibration menu everything is working GREAT. Tomorrow I am flying KDTW to KLAX after the flight I may do some testing. This sounds terrible but when something is NOT broke don't try to fix it. I have no clue why this just started but FSUIPC is doing what you designed it to do which is to control the controls on my AC, which it does perfect.

Cheers

Bob

[bobbjoh]

Hi Pete,

Did an update on my FSUIPC axis settings and changed from "send to FS" to "send to FSUIPC config" now everything is working as it was before, axis change and so do the joystick configurations which allows me to adjust sensitivity.

Cheers

Bob