Yoke & Rudder - strange behavior

[agusti747]

Hi,

I have two yokes and two rudders and last registered version of FSUIPC & WIDEFS.

From a week, I'm having some strange behavior with my yokes and rudders.

I try to explain it with an example:

Plane in runway with external view. Ailerons and elevator are in center position.

When I begins takeoff, suddenly, one of ailerons comes up suddenly, causing the aircraft off the runway. Of course without any entry on yokes or rudders.

I can see left aireron completely UP in external view.

This situation occurs repeatedly at random times, making flight impossible. Not only in soil, also happens in the air.

In FSUIPC i have some problems.

I assign an axis for elevator, ailerons and rudders as usually and then I proceed to Joystick calibration. I'm not a newbie, I've done this process dozens of times.

In joystick calibration tab (Main flight control sections) I observe a curious thing: When I move one rudder, I can see the complete range 16384 to -16384 in Rudder Direct sections, but what happens here is that the numbers of the ailerons moves too. I'm not moving yokes here! (Are significant numbers, not sporadic movements)

This succed with ruders and elevator axis.

I have checked this on other computers and does not happen.

Also I've tried to change the USB connection can not resolve the problem.

The most intriguing is that the yokes and rudders works fine unders windows.

I can calibrate it and I only move the axis that I'm calibrating, not another ones.

I tried too to delete FSUIPC and reinstall it, with no results. I used my FSUIPC.INI file, due I have a hard configuratios. Perhaps I must to create a new one?

I must to add that I have not any axis or key configured in FSX (Only "S" for external view) and "ESC" for exit.

Any idea Pete? I'm lost here?

Thanks!

Regards,

Agustí

Edited June 14, 2013 by agusti747

[Pete Dowson]

last registered version of FSUIPC & WIDEFS.

What does 'last registered' mean? Please always quote version numbers.

Plane in runway with external view. Ailerons and elevator are in center position.

When I begins takeoff, suddenly, one of ailerons comes up suddenly, causing the aircraft off the runway. Of course without any entry on yokes or rudders.

I can see left aireron completely UP in external view.

This situation occurs repeatedly at random times, making flight impossible. Not only in soil, also happens in the air.

That sounds very much like either dual assignment, or even more likely a connection problem. When an axis device becomes disconnected the input spike looks exactly like a maximum deflection.

You could try enabling the spike detection in FSUIPC -- see bottom of left-hand side of the Miscellaneous tab. The facility was originally introduced because of a software bug in one of the add-ons in FS9. It ignores exact maximum and minimum values.

In joystick calibration tab (Main flight control sections) I observe a curious thing: When I move one rudder, I can see the complete range 16384 to -16384 in Rudder Direct sections, but what happens here is that the numbers of the ailerons moves too. I'm not moving yokes here! (Are significant numbers, not sporadic movements)

That can only be either conflicting / dual assignments, or hardware interference.

I tried too to delete FSUIPC and reinstall it, with no results.

I never understand why people thing replacing a DLL with the same DLL can make any difference. There's nothing else installation does except also replace the documentation in the FSUIPC Documents folder.

I used my FSUIPC.INI file, due I have a hard configuratios. Perhaps I must to create a new one?

Well if there are dual assignments in the INI, certainly deleting it will cure that because you then won't have any! But let me take a look first. Paste it into a message.

And disable controllers completely in FSX. If you don't, FSX will tend to automatically reassign them, and you will certainly get conflicts then. You only want things assigned in one place or the other.

I must to add that I have not any axis or key configured in FSX (Only "S" for external view) and "ESC" for exit.

Keys don't matter -- if you assign a key in FSUIPC it overrides the FSX assignment in any case. But merely not assigning axes and buttons in FSX isn't really any good. Either do ALL assignments in FSX and none in FSUIPC, or disable controllers in FSX. It's the only safe way.

Pete

[agusti747]

Peter,

Thans for your fast answer.

"Last versions" means, at present day, 4.90 and 6.995.

The first thing I was think it's in a dual assignement, but I revised a lot of times my FSX config and I can't find it.

Perhaps I need to disable joystick in FSX. I've joystick activated because I need to use the hat switch. but I check axis assignements in FSX and there is none. FSX certainly has a strange "ghost" behavior here, I know.

I will try to enable spike button, thanks.

Hardware interference: It's possible. There are a lot of hardware in this system. I'll try more tests here.

I'm not in my house now. I wil send you the FSUIPC.INI later.

Thanks Peter!

Regards,

Agustí

[Pete Dowson]

The first thing I was think it's in a dual assignement, but I revised a lot of times my FSX config and I can't find it.

To eliminate possible conflicts with FSX simply disable controllers. No need to check any "configs".

But I was also meaning possible dual assignments in FSUIPC. That's why I suggested showing me your INI file.

Perhaps I need to disable joystick in FSX. I've joystick activated because I need to use the hat switch.

If you use FSUIPC for assignments, do so with the hat as well. Axis assignments, "pan view".

Pete

[agusti747]

Hi Pete,

Ok, deactivate joystick an assign Pan view. Thanks!

This is my FSUIPC.INI: (I overwrites yesterday 4.90 version with my old 4.860)

[General]

UpdatedByVersion=4860

History=AS8RD3YIF6YHNX2AL4XIA

InitDelayDevicesToo=No

MouseWheelMove=No

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

FixControlAccel=No

FixMachSpeedBug=No

DeleteVehiclesForAES=Yes

AutoScanDevices=Yes

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=No

ZapSound=firework

ShortAircraftNameOk=Substring

UseProfiles=Yes

EnableMouseLook=No

AxesWrongRange=No

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

InitDelay=0

GetNearestAirports=Yes

OOMcheck=Yes

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

LuaRerunDelay=66

Console=No

UseMidMouseBtn=Yes

FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0

SimConnectUsed=10.0.61259.0

[JoyNames]

AutoAssignLetters=No

1=PFC USB Yoke

1.GUID={39A30D90-716C-11E2-8002-444553540000}

2=PFC USB Pedals

2.GUID={39A30D90-716C-11E2-8001-444553540000}

4=BU0836X Interface

4.GUID={60CF4030-75E2-11E2-8008-444553540000}

5=PFC USB Yoke

5.GUID={39A30D90-716C-11E2-8003-444553540000}

6=BU0836X Interface

6.GUID={60CF4030-75E2-11E2-800A-444553540000}

7=Virtual Joystick

7.GUID={0626C430-8002-11E2-8001-444553540000}

0=BU0836X Interface

0.GUID={60CF4030-75E2-11E2-8009-444553540000}

[buttons]

Buttonrepeat=20,10

1=R2,2,Cx32000BC0,x3FFF000F

2=R2,3,Cx42000BC0,xC001000F

3=R1,2,Cx32000BC0,x3FFF000F

4=R1,3,Cx42000BC0,xC001000F

15=P1,0,C65791,1

16=U1,0,C65791,2

17=P1,6,C1006,1

18=U1,6,C1006,2

21=P0,7,C1006,1

22=U0,7,C1006,2

24=P1,7,C1006,1

25=U1,7,C1006,2

28=P1,1,C1006,3

29=U1,1,C1006,4

32=P5,6,C1006,1

33=U5,6,C1006,2

34=P5,0,C1006,3

35=U5,0,C1006,4

36=R5,3,Cx42000BC0,xC001000F

37=R5,2,Cx32000BC0,x3FFF000F

[AutoSave]

Next=1

Interval=60

Files=10

SaveOnGround=No

AutoSaveEnabled=No

[GPSout]

GPSoutEnabled=No

[GPSout2]

GPSoutEnabled=No

[WideServer]

WideFSenabled=Yes

AdvertiseService=1

Port=8002

Port2=9002

[sounds]

Path=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Sound\

Device1=Controlador primario de sonido

Device2=Altavoces (Dispositivo de High Definition Audio)

Device3=Audio digital (S/PDIF) (Dispositivo de High Definition Audio)

Device4=Audio digital (S/PDIF) (Dispositivo de High Definition Audio)

[Axes]

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

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

2=0R,256,D,3,0,0,0

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

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

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

6=2Y,256,D,7,0,0,0

7=2R,256,D,3,0,0,0

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

9=3Y,256,D,7,0,0,0

10=3R,256,D,3,0,0,0

11=5X,256,D,1,0,0,0

12=5Y,256,F,65694,0,0,0

[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

LeftBrake=0,16383

RightBrake=0,15753

Aileron=-16384,-512,0,16383

Elevator=-16380,-512,512,16380

Rudder=-16384,-1587,512,16383

[Programs]

Run1=READY,CLOSE,KILL,C:\ProSim737\ProSim737\Prosim737.exe

Run2=READY,CLOSE,KILL,C:\ProSim737\ProSimMCP\ProsimMCP.exe

Run3=READY,CLOSE,KILL,C:\ProSim737\ProSimCDU\ProsimCDU.exe

Run4=READY,CLOSE,KILL,C:\ProSim737\ProSimPanel\ProsimPanel.exe

Run5=READY,CLOSE,KILL,C:\ProSim737\ProSimAudio\ProsimAudio.exe

1=COCKPIT

[Keys]

17=52,10,x010066C4,x01,x010066C4,x00

18=53,10,x010066C0,x01,x010066C0,x00

19=49,10,x010066C1,x01,x010066C1,x00

22=50,10,x010066C2,x01,x010066C2,x00

24=54,10,x010066C5,x01,x010066C5,x00

26=55,10,x010066C6,x01,x010066C6,x00

[ClientNames]

1=INSTRUCTOR

Regards,

Agustí

[Pete Dowson]

This is my FSUIPC.INI: (I overwrites yesterday 4.90 version with my old 4.860)

The only relvant parts to axis assignments are these:

[JoyNames]

AutoAssignLetters=No

1=PFC USB Yoke

1.GUID={39A30D90-716C-11E2-8002-444553540000}

2=PFC USB Pedals

2.GUID={39A30D90-716C-11E2-8001-444553540000}

4=BU0836X Interface

4.GUID={60CF4030-75E2-11E2-8008-444553540000}

5=PFC USB Yoke

5.GUID={39A30D90-716C-11E2-8003-444553540000}

6=BU0836X Interface

6.GUID={60CF4030-75E2-11E2-800A-444553540000}

7=Virtual Joystick

7.GUID={0626C430-8002-11E2-8001-444553540000}

0=BU0836X Interface

0.GUID={60CF4030-75E2-11E2-8009-444553540000}

[Axes]

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

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

2=0R,256,D,3,0,0,0

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

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

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

6=2Y,256,D,7,0,0,0

7=2R,256,D,3,0,0,0

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

9=3Y,256,D,7,0,0,0

10=3R,256,D,3,0,0,0

11=5X,256,D,1,0,0,0

12=5Y,256,F,65694,0,0,0

You have 4 assignments to ailerons. I can understand 2 assignments for your two yokes, but 4?

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

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

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

11=5X,256,D,1,0,0,0

As you can see, there's one on each PFC yoke, but also one on a Bodnar board and even one on your PFC pedals (device 2 axis X)!

For elevators, you've got three assignments:

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

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

12=5Y,256,F,65694,0,0,0

one "direct to FSUIPC" on a Bodnar board, and the other two using FS controls instead (why, when all the others are direct?) on the two yokes.

You have three rudder assignments:

2=0R,256,D,3,0,0,0

7=2R,256,D,3,0,0,0

10=3R,256,D,3,0,0,0

One to the pedals, one to a Bodnar board, and the other to a non-existent device 3.

And you have three toe brake assignments, one (left only) to the pedals, and both left and right on the non-existent device 3.

6=2Y,256,D,7,0,0,0

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

9=3Y,256,D,7,0,0,0

Oddly, you have no throttles assigned at all. So how do you fly? I can only assume you assign throttles in FSX?

Altogether, it adds up to a real mess. I think you must have been disconnecting and reconnecting your many devices into different USB ports on different occasions. This will make Windows assign different IDs to them, and consequently the FSUIPC assignments to one device now become applied to another.

If i were you I'd do these steps:

1. Delete the entire [Axes] section in your INI

2. Set the AutoAssignLetters=No parameter in the [JoyNames] section to 'Yes', as advised in the User Guide for those with several devices and who might swap them around (please read that chapter too!).

3. Load up FSX and reassign everything from scratch. No need to recalibrate if you are happy, but looking at your calibrations i also see most values have been left at defaults, so I would still recommend recalibrating everything properly following the numbered steps in the User guide.

Don't forget throttles somewhere, especially since you are going to disable controllers in FSX.

Pete

[agusti747]

If i were you I'd do these steps:

1. Delete the entire [Axes] section in your INI

2. Set the AutoAssignLetters=No parameter in the [JoyNames] section to 'Yes', as advised in the User Guide for those with several devices and who might swap them around (please read that chapter too!).

3. Load up FSX and reassign everything from scratch. No need to recalibrate if you are happy, but looking at your calibrations i also see most values have been left at defaults, so I would still recommend recalibrating everything properly following the numbered steps in the User guide.

Don't forget throttles somewhere, especially since you are going to disable controllers in FSX.

Hi Pete,

First of all thank you fast answer.

I erased the entire axis section and all works fine now!

I think someone probably changed some USB connectors from his original place.

Certainly, I haven't configured my throttle throught FSUIPC. I can't do it! it's impossible with this throttle!

I've a FSC TQ non motorized throttle wich only works with his F SCnative driver. I can only configure some buttons throght FSUIPC, via key assignement, like TOGA, AT/Disarm and parquing brake. All axis only works via FSC driver. (Prosim737 incorporates this driver too in the last release).

Some people are changing original electronic board of this throttle to a Leo Bodnar joystick card, and then yes, it's possible to configure all axis throught FSUIPC. But it's not possible with his original board.

The reason for only left brake assignement is that my rudders are broken. Only works left toe in F/O side and none in Captain side! I hope to repair it in a few days.

Regards,

Agustí

[Pete Dowson]

The reason for only left brake assignement is that my rudders are broken. Only works left toe in F/O side and none in Captain side! I hope to repair it in a few days.

Well, until then you might want to assign the left toe brake to both left and right brake axes so you get symmetric braking!

Regards

Pete