FSUIPC disconnecting controllers (CH YOKE/THROTTLE)

[bjratchf]

I'm having a relatively small problem that just recently has cropped up...

Some time during the flight- my joystick controllers stop working- CH YOKE, Throttle, - this disconnection is accompanied by a small "static" sound, and then I realize I'm not getting any more control response.

The only thing I can think of at this point is that I've been monkeying around with my DRAM settings in the bios- I just realized that the timings were not stock, and my DRAM voltage was showing 1.65 (they are only rated for 1.6) so I corrected the timings, speed, and voltage manually in the bios. Could this be what's causing the disconnecting of my controllers? In each case, going back into FSUIPC and my axes settings, and having FSUIPC "re-recognize" my controllers by moving them back and fourth corrects the problem each time. Not a big deal problem, however going into FSUIPC settings during my flight causes FSX to crash, since I'm in fullscreen mode (ENBseries limitation).

Thanks!

Some info about my system:

Asus P8P67 Pro

i7 2600k overclocked to 4.8 (stable)

Windows 7 64bit

CH Pro Yoke, Throttle Quadrant

Saitek Fighter-Pro Pedals

8Gb GSkill Ripjaws CL7 Rated at 1600Mhz 7-8-7-24, defaults to 1600Mhz 8-8-8-24 timings on the over clock. 1.6v rated.

[Pete Dowson]

Some time during the flight- my joystick controllers stop working- CH YOKE, Throttle, - this disconnection is accompanied by a small "static" sound, and then I realize I'm not getting any more control response.

Sounds like a connection problem. Normally such problems are due to Windows removing power from the USB port when there's been no action on it for a while. You can stop that by turning power management off for each USB hub, in the Device Manager. But I've never heard of it making a sound when it does it.

The only thing I can think of at this point is that I've been monkeying around with my DRAM settings in the bios- I just realized that the timings were not stock, and my DRAM voltage was showing 1.65 (they are only rated for 1.6) so I corrected the timings, speed, and voltage manually in the bios. Could this be what's causing the disconnecting of my controllers?

Sorry, I've no idea about all that.

In each case, going back into FSUIPC and my axes settings, and having FSUIPC "re-recognize" my controllers by moving them back and fourth corrects the problem each time. Not a big deal problem, however going into FSUIPC settings during my flight causes FSX to crash, since I'm in fullscreen mode (ENBseries limitation).

If the joysticks are disconnecting, then simply going into FSUIPC's dialogues and exiting again causes FSUIPC to re-scan for new connections. FS itself doesn't do this -- you'd need to close FS down and restart it to get them back.

Regards

Pete

[bjratchf]

I see where you talking about- in the device manager for the specific USB root hub that my CH components are attached to, there is a checkbox that says "Allow the computer to control the power to this unit." I unchecked it- and will give it a go!

[bursco]

Quote - "I'm having a relatively small problem that just recently has cropped up...

Some time during the flight- my joystick controllers stop working- CH YOKE, Throttle, - this disconnection is accompanied by a small "static" sound, and then I realize I'm not getting any more control response. "

I have the same problem with saitek X52 Pro rudders - they switch off and I hear the system noise - I just go in and out of FSUIPC and after scanning like you said Peter the rudders work. Have taken off power control but still same - only started recently. Only the rudder switches off - joystick stays on - weird. :cry:

Will try and time it :idea:

Denis Brown

Asus P8Z68-V Pro, WIN7 64, 560TI, i5-2500K 3.30, 8gig mem.

[Pete Dowson]

I have the same problem with saitek X52 Pro rudders - they switch off and I hear the system noise - I just go in and out of FSUIPC and after scanning like you said Peter the rudders work. Have taken off power control but still same - only started recently. Only the rudder switches off - joystick stays on - weird. :cry:

It certainly sounds like there's some sort of disconnection glitch which is causing this -- maybe wiring or maybe something in the unit itself. The symptoms you describe are exactly what you'd get if you pulled the USB plug out and plugged it in again. FS wouldn't recover from that without reloading. FSUIPC does rescan for new connections when you go into its options.

Regards

Pete

[bursco]

It certainly sounds like there's some sort of disconnection glitch which is causing this -- maybe wiring or maybe something in the unit itself. The symptoms you describe are exactly what you'd get if you pulled the USB plug out and plugged it in again. FS wouldn't recover from that without reloading. FSUIPC does rescan for new connections when you go into its options.

Regards

Pete

Have timed the disconnects for rudders (Saitek) - it seems to happen around every 11 mins- even if I have used them for taxi etc ?? Been in bios and set legacy usb and usb 3 to enabled and EHCH to off.

I fly the dodo helo and they seem to disconnect randomly when flying it - strange again.

Thanks for quick reply - will keep on "experimenting" - my X52 pro is 100% better in FSUIPC than FSX or Saitek software (which has been uninstalled).

The next thing I will try is another usb port. :razz:

:razz:

DMB

[mldavis2]

I'm having a similar issue that may be related to FSUIPC and FSX. I'm running SP2 but not Acceleration. It has been a stable platform for well over a year. I have a registered copy of FSUIPC 4.751 and I'm using CH Pro Throttle, CH Pro Pedals and a CH Eclipse yoke all running from a powered USB hub.

I was flying a default Lear 45 and turned the autopilot off on an approach. My ailerons would not work. I restarted FSX and reset the approach without the autopilot on with the same results. Thinking my yoke was going bad, I removed it and replaced it with a spare CH Yoke LE I had that I know works. Same result. I then loaded X-Plane and had full aileron control. Back to FSX and into FSUIPC. In the Axis Assignment tab I can see the full range of the potentiometer =/- 16,000 for "joystick #1 X-axis". When I go to the Axis Calibration the aileron (X-axis) value is stuck around 400 and does not deflect with the yoke handle. I rebooted the computer with the same result. I then plugged the CH Yoke LE directly into the USB port on the back of the mobo with the same results. Is FSUIPC blocking this potentiometer signal for some strange reason? And if so, why now after a year and no changes other than installing the new version 4.751 a week or so ago? Why does FSUIPC show full axis range in assignment but not in calibration?

[Pete Dowson]

When I go to the Axis Calibration the aileron (X-axis) value is stuck around 400 and does not deflect with the yoke handle. I rebooted the computer with the same result. I then plugged the CH Yoke LE directly into the USB port on the back of the mobo with the same results. Is FSUIPC blocking this potentiometer signal for some strange reason? And if so, why now after a year and no changes other than installing the new version 4.751 a week or so ago? Why does FSUIPC show full axis range in assignment but not in calibration?

FSUIPC does not (cannot) treat any one axis different from any other except by user options. There's no way "aileron" assignment will get singled out for special unwanted treatment on FSUIPC's own initiative. Furthermore there's been no changes in how all this works for a long long time, and it is the same in FSUIPC3 and FSUIPC4.

Before doing anything else, please update to the latest version -- 4.758 -- so we are both using the same one. No need to download the installer, just get the updated DLL and copy it in. Download Links subforum.

It sounds as if you have something screwed up in your settings. Please, first, make sure controllers are all switched off in FSX (because any dual assignments can give the oddest results), Then paste your FSUIPC4.INI file here. You could also enable Axis logging in FSUIPC's logging tab, operate the ailerons and check the results. Again, paste the Log here if you want me to take a look.

Regards

Pete

[mldavis2]

Thanks, Pete. I'm not blaming FSUIPC, just trying to make sense of this sudden failure. FYI, I opened X-Plane 10 and my ailerons (X-axis) works fine in that program, so it's not a controller hardware or connection issue I don't think. I hope I'm doing this correctly from what you asked above:

For the record, I'm running Win7 64 on a stable Q9450 Intel chip, 8GB RAM and an nVidia 570 card with 1280MB RAM. I'm using Active Sky 2012 for weather which is a couple of weeks old. The nVidia 570 card is a week old, a replacement for an older nVidia 9800GTX+, but has been used during that time. The ailerons were being "controlled" during turns when the autopilot was ON during the flight in which they failed sometime after disconnection of the autopilot. What puzzles me is that I have been flying this setup for several days with no changes. It was sometime after I disabled the autopilot on the last approach that my aileron controls were gone. There was no ILS on the approach airport, just a manual landing. Other default aircraft have been checked since then and shown to have no aileron control, so it's a universal FSX issue.

I installed FSUIPC 4.758 (although I had to use the .exe installer because I didn't find the single FSUIPC file). I am not using WIDEFS7. I turned controllers off (checkbox) in FSX, then went to FSUIPC, turned axis logging on, ran yoke through axis ranges. Here are the .INI and .LOG files. I hope you can shed some light on this and offer some suggestions. I'm at my wits end - and flying X-Plane until I get it sorted out ...

********* FSUIPC4, Version 4.758 by Pete Dowson *********

User Name="Mike Davis"

User Addr="mldavis2@sbcglobal.net"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

Running inside FSX on Windows 7

Module base=61000000

359 System time = 16/01/2012 08:03:20

359 FLT path = "C:\Users\Mike\Documents\Flight Simulator X Files\"

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

421 FS path = "C:\Flight Simulator X\"

1154 LogOptions=00000000 00000001

1170 Wind smoothing fix is fully installed

1170 G3D.DLL fix attempt installed ok

1170 SimConnect_Open succeeded: waiting to check version okay

1170 Trying to use SimConnect Acc/SP2 Oct07

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

4165 Initialising SimConnect data requests now

4165 FSUIPC Menu entry added

4259 C:\Users\Mike\Documents\Flight Simulator X Files\NextFlightSet.FLT

4259 C:\Users\Mike\Documents\Flight Simulator X Files\FIMP-FMNV.PLN

4259 C:\Flight Simulator X\SimObjects\Airplanes\Lear45\Lear45.AIR

4259 C:\Users\Mike\Documents\Flight Simulator X Files\FIMP-FMNV.PLN

109559 System time = 16/01/2012 08:05:09, Simulator time = 08:03:24 (05:03Z)

109824 Aircraft="Learjet 45 Limited Edition"

110480 Starting everything now ...

111572 Advanced Weather Interface Enabled

245577 Sim stopped: average frame rate for last 60 secs = 59.0 fps

582352 Sim stopped: average frame rate for last 230 secs = 23.4 fps

922746 Sim stopped: average frame rate for last 306 secs = 59.1 fps

1022462 LogOptions changed, now 10000000 00000001

1043787 Sim stopped: average frame rate for last 21 secs = 44.3 fps

1147855 LogOptions changed, now 00000000 00000001

[General]

History=5V3QU4P5EXSY7634MMF0T

MouseWheelTrim=No

MouseWheelTrimSpeed=1

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

WindSmoothing=Yes

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

ZapSound=firework

ShortAircraftNameOk=No

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=Yes

SuppressMultilineFS=No

AxisIntercepts=No

WeatherReadFactor=2

WeatherRewriteSeconds=1

SimConnectStallTime=1

CustomWeatherModify=No

Console=No

UpdatedByVersion=4758

SaveDataWithFlights=No

UseProfiles=No

SmoothBySimTime=No

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

DeleteVehiclesForAES=Yes

BrakeReleaseThreshold=75

EnableMouseLook=No

AxesWrongRange=No

DontResetAxes=No

InitDelay=0

GetNearestAirports=Yes

LuaRerunDelay=66

FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0

SimConnectUsed=10.0.61259.0

[AutoSave]

AutoSaveEnabled=Yes

Interval=300

Files=5

SaveOnGround=No

AlsoSave=Save

AlsoInterval=60

Next=2

1=Sun 213152

2=Sun 210655

3=Sun 211154

4=Sun 211654

5=Sun 212153

[GPSout]

GPSoutEnabled=No

Port=COM0

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[WideServer]

WideFSenabled=Yes

[JoystickCalibration]

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

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

LeftBrake=829,16380/16

RightBrake=-397,16380/16

Flaps=0,16380/16

Rudder=-16380,0,0,16380

Mixture=-7770,6859

Throttle=-13316,16380

AllowSuppressForPFCquad=Yes

UseAxisControlsForNRZ=No

[JoystickCalibration.Maule M7 260C paint1]

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

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

Rudder=-16383,0,512,16383/8

SlopeRudder=9

Mixture=-7770,6859

LeftBrake=-16380,16380/16

RightBrake=-16380,16380/24

Flaps=0,16380/16

[JoystickCalibration.Cessna Skyhawk 172SP Paint1]

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

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

Rudder=-16380,0,0,16380

SlopeRudder=1

Mixture=-7770,6859

LeftBrake=3104,8249/16

RightBrake=-482,16380/16

Flaps=0,16380/16

Aileron=-16375,80,80,16383/8

Elevator=-16380,-203,-203,16380/8

[JoystickCalibration.Airbus A321 Paint2]

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

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

Rudder=-16380,0,0,16380

SlopeRudder=-5

Mixture=-7770,6859

LeftBrake=-687,16380/16

RightBrake=-397,16380/16

Flaps=0,16380/16

Elevator=-16380,-512,512,16380/16

Aileron=-16380,-512,512,16380/16

[JoystickCalibration.Beech King Air 350 Paint1]

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

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

Aileron=-16375,80,80,16383

Rudder=-16380,0,0,16380

SlopeRudder=-5

Mixture=-7770,6859

LeftBrake=-687,16380/16

RightBrake=-397,16380/16

Flaps=0,16380/16

Elevator=-16380,-203,-203,16380

[MacroFiles]

1=747 OHD

2=APchart

[JoystickCalibration.Mooney Bravo]

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

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

Rudder=-16380,0,0,16380

Throttle=-13316,16380

Mixture=-7770,6859

LeftBrake=-2362,16380/16

SlopeLeftBrake=2

RightBrake=-779,16380/16

Flaps=0,16380/16

[JoyNames]

AutoAssignLetters=No

0=CH Pro Pedals USB

0.GUID={EA85F7F0-CB64-11DE-8005-444553540000}

1=CH Pro Throttle USB

1.GUID={EA85F7F0-CB64-11DE-8004-444553540000}

2=CH Eclipse Yoke USB

2.GUID={EA85F7F0-CB64-11DE-8003-444553540000}

[buttons]

ButtonRepeat=20,10

1=R1,1,K113,8

2=U1,1,K112,8

[JoystickCalibration.Boeing 737-800 Paint1]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

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

Mixture=-4973,4972

LeftBrake=829,16380/16

RightBrake=-397,16380/16

Flaps=0,16380/16

[GPSout2]

GPSoutEnabled=No

Port=<none set>

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[JoystickCalibration.Cessna 177RG]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

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

Rudder=-16380,0,0,16380

Throttle=-13316,16380

Mixture=-7770,6859

LeftBrake=829,16380/16

RightBrake=-397,16380/16

Flaps=0,16380/16

[sounds]

Path=C:\Flight Simulator X\Sound\

Device1=Primary Sound Driver

Device2=Speakers (SoundMAX Integrated Digital HD Audio)

Device3=SPDIF Interface (SoundMAX Integrated Digital HD Audio)

[Window.Radar Contact]

Docked=67, 714, 3537, 1549

[Monitor]

Display=1

[bursco]

Have timed the disconnects for rudders (Saitek) - it seems to happen around every 11 mins- even if I have used them for taxi etc ?? Been in bios and set legacy usb and usb 3 to enabled and EHCH to off.

I fly the dodo helo and they seem to disconnect randomly when flying it - strange again.

Thanks for quick reply - will keep on "experimenting" - my X52 pro is 100% better in FSUIPC than FSX or Saitek software (which has been uninstalled).

The next thing I will try is another usb port. :razz:

:razz:

DMB

Have tried another usb port for rudders and "touch wood" - they have been OK all day - with NGX and Dodo - Thanks for all your help Peter and A Happy New Year.

Denis Brown

[Pete Dowson]

I installed FSUIPC 4.758 (although I had to use the .exe installer because I didn't find the single FSUIPC file).

I don't know how you could miss it. The Download Links subforum certainly contains both. The entries for FSUIPC read as follows:

FSUIPC4 update 4.758 FSUIPC 4.758

----If you haven't already installed 4.70 or later, instead get the full installer for 4.758 here:

Install complete FSUIPC version 4.758 Install FSUIPC4.758

Note: This new installer fixes a termination problem when only Prepar3D is installed (ie. no FSX or ESP)

Details of changes in FSUIPC4 since the last full release (4.70) are included in a PDF in the ZIP.

The first link is just the DLL and a changes document. The second is the full works. This arrangement is always provided in that thread.

I turned controllers off (checkbox) in FSX, then went to FSUIPC, turned axis logging on, ran yoke through axis ranges. Here are the .INI and .LOG files.

I'm afraid that you didn't get any useful logging:

922746 Sim stopped: average frame rate for last 306 secs = 59.1 fps

1022462 LogOptions changed, now 10000000 00000001

1043787 Sim stopped: average frame rate for last 21 secs = 44.3 fps

1147855 LogOptions changed, now 00000000 00000001

It looks like you turned axis logging off but either never actually went back into FS flight mode to waggle the axes, or did go back but didn't waggle any connected axes. Natually, whilst in the options, such logging doesn't occur because the axes are not being put through the normal paths, they are only recognised for assignment and calibration purposes.

Looking at the INI file, you have NO AXIS ASSIGNMENTS WHATSOEVER in FSUIPC. therefore if they aren't assigned in FSX, they cannot be used at all!

That may explain the lack of logging -- FSUIPC cannot log axes which aren't doing anything.

Secondly, look at the following, where I've simply removed everything but the calibrations. You have different calibrations, for the same devices, for loads of different aircrafgt. But some incvlude some axes, not others. All in all it is a mess. Can you tell me what you've been trying to do here?

[JoystickCalibration]

LeftBrake=829,16380/16

RightBrake=-397,16380/16

Flaps=0,16380/16

Rudder=-16380,0,0,16380

Mixture=-7770,6859

Throttle=-13316,16380

[JoystickCalibration.Maule M7 260C paint1]

Rudder=-16383,0,512,16383/8

SlopeRudder=9

Mixture=-7770,6859

LeftBrake=-16380,16380/16

RightBrake=-16380,16380/24

Flaps=0,16380/16

[JoystickCalibration.Cessna Skyhawk 172SP Paint1]

Rudder=-16380,0,0,16380

SlopeRudder=1

Mixture=-7770,6859

LeftBrake=3104,8249/16

RightBrake=-482,16380/16

Flaps=0,16380/16

Aileron=-16375,80,80,16383/8

Elevator=-16380,-203,-203,16380/8

[JoystickCalibration.Airbus A321 Paint2]

Rudder=-16380,0,0,16380

SlopeRudder=-5

Mixture=-7770,6859

LeftBrake=-687,16380/16

RightBrake=-397,16380/16

Flaps=0,16380/16

Elevator=-16380,-512,512,16380/16

Aileron=-16380,-512,512,16380/16

[JoystickCalibration.Beech King Air 350 Paint1]

Aileron=-16375,80,80,16383

Rudder=-16380,0,0,16380

SlopeRudder=-5

Mixture=-7770,6859

LeftBrake=-687,16380/16

RightBrake=-397,16380/16

Flaps=0,16380/16

Elevator=-16380,-203,-203,16380

[JoystickCalibration.Mooney Bravo]

Rudder=-16380,0,0,16380

Throttle=-13316,16380

Mixture=-7770,6859

LeftBrake=-2362,16380/16

SlopeLeftBrake=2

RightBrake=-779,16380/16

Flaps=0,16380/16

[JoystickCalibration.Boeing 737-800 Paint1]

Mixture=-4973,4972

LeftBrake=829,16380/16

RightBrake=-397,16380/16

Flaps=0,16380/16

[JoystickCalibration.Cessna 177RG]

Rudder=-16380,0,0,16380

Throttle=-13316,16380

Mixture=-7770,6859

LeftBrake=829,16380/16

RightBrake=-397,16380/16

Flaps=0,16380/16

Additionally, in some places you enabled Filtering, others not. Why? Generally filtering is NOT a good idea unless you have really bad, dirty controls or a poor power supply.

the only aircraft for which you have ailerons calibrated are:

[JoystickCalibration.Cessna Skyhawk 172SP Paint1]

Aileron=-16375,80,80,16383/8

-- Filtering enabled. Why?

[JoystickCalibration.Airbus A321 Paint2]

Aileron=-16380,-512,512,16380/16

Reverse enabled, but numbers show no calibration -- those are default numbers!

[JoystickCalibration.Beech King Air 350 Paint1]

Aileron=-16375,80,80,16383

Same calibration as the Cessna above, without filtering.

Why have different calibrations for the same controls for different aircraft? I could understand some sorts of separate needs, like helicopters v aircraft, and fighters or stunt aircraft v airliners and GA. But not for these ordinary aircraft. you just confuse yoursel.

If I were you I'd delete the FSUIPC4.INI file altogether and start again. But please do read a little more of the User Guide. And please think about assignments. Unless you assign your axes they cannot be used.

Regards

Pete

[mldavis2]

Thanks, Pete. Recognize that those calibrations are the accumulation of YEARS of flying with FSX, they weren't all performed recently. The use of filtering also dates way back with a previous CH Yoke LE that was getting old that has since been replaced. Note that there are no dates on those calibrations logs.

I'll go back and delete the FSUIPC.INI file and report back. Just completed a flight in X-Plane 10 with no problems, by the way, with the CH Eclipse Yoke.

Thanks for your patience. I have no idea why I haven't been having any problem for years ... ??

[mldavis2]

Sorry for the late reply, Pete, but the forum was down for several hours when I tried to log on.

You are, of course, right. I deleted the FSUIPC.INI file and eliminated the problem.

Two questions remain of only passing interest since the main goal was getting FSX back flying. First, I do not recall going into FSUIPC any time recently and resetting anything, so why the sudden problem of lost aileron control. Second, why did it occur AFTER I had a successful take-off under manual control, the autopilot handled turn banks correctly enroute, and the ailerons only seemed to fail when the autopilot was disengaged on approach. I think it was these irrational factors that caused so much confusion, even to the point of disassembly of my yoke. No matter.

I did learn a few things, and I will go back and read the manual. I was not aware that you could simply delete the .INI file and it would be rebuilt.

Anyway, no response needed. Your product support is greatly appreciated and I thank you for your time. I hope more simmers will be encouraged to register FSUIPC rather than using the free version. Thanks for a great product!!

[Pete Dowson]

I do not recall going into FSUIPC any time recently and resetting anything, so why the sudden problem of lost aileron control. Second, why did it occur AFTER I had a successful take-off under manual control, the autopilot handled turn banks correctly enroute, and the ailerons only seemed to fail when the autopilot was disengaged on approach. I think it was these irrational factors that caused so much confusion, even to the point of disassembly of my yoke.

Sorry, I've really no idea. Obviously something got corrupted at some stage. But with your axes evidently only ever assigned in FSX, the stuff in FSUIPC for calibration was only able to work with whatever came through from FSX. FSUIPC4 only reads the joysticks directly when you assign in FSUIPC, otherwise all the calibrations are trying to do is modify the control values once FSX has received them and messed with them.

I did learn a few things, and I will go back and read the manual. I was not aware that you could simply delete the .INI file and it would be rebuilt.

It only rebuilds with everything reverting to default, with no assignments, no calibrations, no unusual settings. But in your case that was a good thing. In general one would only delete the troublesome area -- but your settings showed you only ever used FSUIPC for calibration, and then a little bit wonkily with assorted options applied rather haphazardly to different aircraft. Best to just start over, as you've now done.

Regards

Pete

[mldavis2]

One quick follow-up here, Pete, in case anyone else is fighting an illogical controller problem. After "fixing" the problem by deleting the FSUIPC.INI file and letting FSX rebuild it, I encountered exactly the same problem again on the very next flight. I tried deleting it again but no luck. I deleted the FSX.CFG file and let that rebuild, no luck. Finally after surfing the net I ran across a situation in which there was an axis conflict between a CH Pro Throttle and the CH Eclipse yoke. So I went back into FSX and looked at axis assignments. What I found was that, for some reason, the X-axis for ailerons had been assigned to the X-axis of the CH Pro throttle, of which there is none, of course, the throttle being a Z-axis. So by deleting the axis conflict in the Pro Throttle, I was able to regain control of the x-axis ailerons with the yoke. The real question now is why did those assignments appear for the Pro Throttle, and why was it able to assign functions to a non-existent axis? I have no idea, but now I sure know what to look for !!!

[Pete Dowson]

So I went back into FSX and looked at axis assignments. What I found was that, for some reason, the X-axis for ailerons had been assigned to the X-axis of the CH Pro throttle, of which there is none, of course, the throttle being a Z-axis. So by deleting the axis conflict in the Pro Throttle, I was able to regain control of the x-axis ailerons with the yoke. The real question now is why did those assignments appear for the Pro Throttle, and why was it able to assign functions to a non-existent axis? I have no idea, but now I sure know what to look for !!!

FSX does do auto-assignments according to details it holds about devices. I think they are all in files called something like Devices.CFG. It matches devices by the name which appears on the USB connection. Maybe the device name is ambiguous or it got the wrong one, and did its auto-assignments based on the details it has in those CFG files.

I always have all controllers disabled in FSX and assign everything in FSUIPC. I don't like auto-assignment at all I'm afraid. It can be very annoying.

Regards

Pete

[mldavis2]

I always have all controllers disabled in FSX and assign everything in FSUIPC. I don't like auto-assignment at all I'm afraid. It can be very annoying.

Regards

Pete

I think that is an excellent idea. I much prefer using FSUIPC for setting calibrations. I'll give it a try. Thanks again, Pete, for your advice and effort!

[Oliver Branaschky]

Dear Mr. Dawson,

I have started using FSUIPC for axis and button assignment only a couple of days ago. Everything works fine, except that I'm experiencing the same issue with a stuck rudder.

I'm using a Saitek Pro Flight Yoke System with Throttle Quadrant in combination with a pair of rather old CH pedals. Controllers are deactivated in FSX, axis assigned through FSUIPC.

Regardless of whether I connect the pedals directly to a free USB port or through the Saitek yoke functioning as a USB hub, after a certain time (I figure around 30 to 45 minutes), the rudder will suddenly cease to work. Only after accessing FSUIPC via the Add-Ons menu and immediately leaving it again, will they reverse to functioning. Power management for all USB ports is turned off.

I would be glad if you have any more ideas as to what might be wrong here...

Regards,

Oliver

[Pete Dowson]

Dear Mr. Dawson,

It's "Dowson", actually, but call me Pete.

Everything works fine, except that I'm experiencing the same issue with a stuck rudder.

Same issue as what, exactly? I've read through the other two, different, problems in this thread and neither were concerned with any "stuck rudder" --one was a definite USB port problem and fixed using another port, the other was one of dual assignments because controllers had not been disabled in FSX when assigning in FSUIPC.

Regardless of whether I connect the pedals directly to a free USB port or through the Saitek yoke functioning as a USB hub, after a certain time (I figure around 30 to 45 minutes), the rudder will suddenly cease to work. Only after accessing FSUIPC via the Add-Ons menu and immediately leaving it again, will they reverse to functioning. Power management for all USB ports is turned off.

Well, all visiting the FSUIPC menu does is cause the USB connections to be rescanned, which sends a re-initialisation code to the joysticks, so it certainly seems as if the specific USB connection to the rudder is going to sleep and/or stalling in some way. Since it is the same through the Saitek hub it would certainly argue against being a USB port problem, and instead suggest a power probem in the unit itself, or the connecting wires to the unit, or the actual circuitry inside it. I really can't advise how that could be fixed.

Regards

Pete

[masterk]

Hi Pete,

i have nearly the same problem. I have all Sticks connected to my computer. No Hub.

Suddelny during flight the rudder starts to work without touching it. Or suddenly no axis work. After entering the FSUIPC and press OK everything seem to work again. It seem like the FSUIPC stops work for a time. Sometimes for thrust i must go to the axis menu and only move it there an press OK. Then it works again. It all startet with the new Version. I have installed 3.999f. Or only one throttle works. After entering FSUIPC and press OK it works again.

Have you an idea what i can do?

Br and have an nice evening

Christian

[Pete Dowson]

i have nearly the same problem. I have all Sticks connected to my computer. No Hub.

Suddelny during flight the rudder starts to work without touching it. Or suddenly no axis work. After entering the FSUIPC and press OK everything seem to work again. It seem like the FSUIPC stops work for a time. Sometimes for thrust i must go to the axis menu and only move it there an press OK. Then it works again. It all startet with the new Version. I have installed 3.999f. Or only one throttle works. After entering FSUIPC and press OK it works again.

All this must surely be down to poor connections or failing hardware. There's no way FSUIPC has of infliuencing USB connections or making phantom values. The fact that reiniitialising the USB devices revitalises them certainly indicates something is wrong in the hardware or its settings.Mmake sure that Windows has its USB power management turned off on every hub listed. If it is already off on them all, then I certainly think you have a faulty motherboard on your hands if it affects all devices (otherwise just a faulty device).

Regard

Pete

[gert57]

Hi Pete,

I stumbled on this forum because I have the same problem as Masterk. I have tried a lot to amend the problem but nothing goes. HOWEVER, I observed the problem only exists if I run FSX with Aivlasoft EFB in conjunction with IVAP fro IVAO.

And it came up when I installed the latest cersion from FSUIPC, viz. 4.8.0.0. In the enclosed logfile I saw something starnge happening with the weather. Maybe that points to a cause?? I did not change the weather in any way..

I hopeyou can shed light in this fog...Sincerely yours, Gert

Logfile:

********* FSUIPC4, Version 4.80 by Pete Dowson *********

User Name="G.D. Visser"

User Addr="gdvisserede@filternet.nl"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

Running inside FSX on Windows 7

Module base=61000000

78 System time = 11/03/2012 16:43:09

78 FLT path = "C:\Users\Beheer\Documents\Flight Simulator X Files\"

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

125 FS path = "G:\FSX\"

1437 LogOptions=00000000 00000001

1437 Wind smoothing fix is fully installed

1437 G3D.DLL fix attempt installed ok

1437 SimConnect_Open succeeded: waiting to check version okay

1437 Trying to use SimConnect Acc/SP2 Oct07

3281 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

3281 Initialising SimConnect data requests now

3281 FSUIPC Menu entry added

3359 G:\FSX\FLIGHTS\OTHER\FLTSIM.FLT

3359 G:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

40609 G:\FSX\SimObjects\Airplanes\feelThere pic 737-300\B737-3A00A.AIR

100140 C:\Users\Beheer\Documents\Flight Simulator X Files\EFB Edinburgh (EGPH) to Belfast - Aldergrove (EGAA).PLN

246531 System time = 11/03/2012 16:47:15, Simulator time = 15:44:06 (15:44Z)

246531 Aircraft="feelThere Boeing 737-300 KLM"

307593 Starting everything now ...

310734 Advanced Weather Interface Enabled

350859 Sim stopped: average frame rate for last 44 secs = 57.4 fps

970984 Sim stopped: average frame rate for last 575 secs = 60.8 fps

970984 Weather Mode now = Theme

982281 Weather Mode now = Custom

3103296 Sim stopped: average frame rate for last 2132 secs = 39.5 fps

4040046 Sim stopped: average frame rate for last 927 secs = 34.2 fps

4076046 C:\Users\Beheer\Documents\Flight Simulator X Files\EFB Edinburgh (EGPH) to Belfast - Aldergrove (EGAA).PLN

4076046 Weather Mode now = Theme

4076046 C:\Users\Beheer\AppData\Roaming\Microsoft\FSX\Previous flight.FLT

4087578 System time = 11/03/2012 17:51:16, Simulator time = 16:50:28 (16:50Z)

4087578 *** FSUIPC log file being closed

Average frame rate for running time of 3696 secs = 41.8 fps

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

Memory managed: 2125 Allocs, 2125 Freed

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

[masterk]

All this must surely be down to poor connections or failing hardware. There's no way FSUIPC has of infliuencing USB connections or making phantom values. The fact that reiniitialising the USB devices revitalises them certainly indicates something is wrong in the hardware or its settings.Mmake sure that Windows has its USB power management turned off on every hub listed. If it is already off on them all, then I certainly think you have a faulty motherboard on your hands if it affects all devices (otherwise just a faulty device).

Regard

Pete

Hi Pete,

i will check it with the power. Thanks for your answer.

Br

Christian

[masterk]

Hi Pete.

The same problem. The Axis stops to work after a time. The Buttons on the yokes where all working. So it seem the FSUIPC forgett the Axis. After entering the fsuipc and press OK all axis are working again.

BR

Christian

[Pete Dowson]

The same problem. The Axis stops to work after a time. The Buttons on the yokes where all working. So it seem the FSUIPC forgett the Axis. After entering the fsuipc and press OK all axis are working again.

FSUIPC cannot "forget" axes. They simply send signals when they want to. FSUIPC has no control over that. If they stop responding -- i.e. stop sending messages -- then it is down to the hardware, the USB driver, or Windows turning off the power. All that visiting the options does is make FSUIPC rescan the USB devices for new connections. That makes the Windows USB drivers send out re-initialisation signals to the devices, which must be waking them up again.

If your devices are going to sleep you either need better power for them or you must turn off Windows USB power management. If none of that helps you have faulty drivers or faulty hardware.

The same would most certainly also occur with FS assigning, except in FS's case you've no option for re-scanning but have to reload FS!

Regards

Pete