Saitek Cessna Trim Wheel - Not initially recognised

[Scotfleiger]

Pete

I have recently acquired a Saitek Cessna Trim Wheel (VID 06A3, PID 0C2D) and assigned it to the Elevator Trim axis. FSUIPC5 logs it as but does not initially action any input. After the trim wheel has been operated the device reload and then FSUIPC recognises the trim input.  The FSUIPC5.log shows the device reconnecting at this point. The attached load also includes LINDA logging.

If this a known problem?

 

FSUIPC5.log

FSUIPC5.ini

[Thomas Richter]

Hi,

as the log shows it connects in the first place and reconnects later, as you say after use it. Maybe the Hub where it is connected to is overloaded?

Quote

       94 Product= Pro Flight Cessna Trim Wheel
       94    Manufacturer= Saitek
       94    Serial Number= RD001289
       94    Vendor=06A3, Product=0BD4 (Version 1.6)
       94    GUIDs returned for product: VID_06A3&PID_0BD4:
       94       GUID= {627C8510-4FB6-11E8-8001-444553540000}
       94       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X1023,Y0,Z0

. . .

      110 Device acquired for use:
      110    Joystick ID = 4 (Registry okay)
      110    4=Pro Flight Cessna Trim Wheel
      110    4.GUID={627C8510-4FB6-11E8-8001-444553540000}

. . .

   132641 ***** HID USB device reconnected: re-initialising FSUIPC connections
   132641 HID: Vendor=06A3, Product=0BD4 (Version 1.6)
   132641 Manufacturer= Saitek
   132657 Product= Pro Flight Cessna Trim Wheel
   132657 Serial Number= RD001289

. . .

   132672 Device acquired for use:
   132672    Joystick ID = 4 (Registry okay)
   132672    4=Pro Flight Cessna Trim Wheel
   132672    4.GUID={627C8510-4FB6-11E8-8001-444553540000}

As you know FSUIPC can only see what Windows sees and when it reconnects in FSUIPC that means FSUIPC gets a callback from Windows that a device has been connected.

Also please start FS and close it fully without moving the TrimWheel and keep a copy of the FSUIPC5.JoyScan.csv file (Modules folder). Then start again FS and move the TrimWheel to get devices reloaded and it is correct seen and then close FS. Copy of the FSUIPC5.JoyScan.csv file and send both of them.

Thomas

[Pete Dowson]

5 minutes ago, Thomas Richter said:

Maybe the Hub where it is connected to is overloaded?

Or possibly the USB port still has power management turned on in Windows Device Manager. This option is defaulted on, and the option can cause a seldom used input to power off ("go to sleep"). Always turn off the feature in the properties of all listed USB devices/hubs in device Manager.

Pete

 

[Scotfleiger]

I had great hopes for setting the 'damned' power management. However, no luck. I just have to remember to function the trim wheel before flight.

Attached are the before and after joy files.

FSUIPC5.JoyScanTrimMoved.csv

FSUIPC5.JoyScanOnStart.csv

[Pete Dowson]

17 minutes ago, Scotfleiger said:

I just have to remember to function the trim wheel before flight.

Attached are the before and after joy files.

Well, the scan returns the same results for the Trim Wheel in both cases:

Y, x1E, x06A3, x0BD4, Pro Flight Cessna Trim Wheel, 4, 4, 0, {627C8510-4FB6-11E8-8001-444553540000},
{627C8510-4FB6-11E8-8001-444553540000}, {627C8510-4FB6-11E8-8001-444553540000}, Y, Y

so I really don't understand why it isn't functioning correctly like any other joystick connection. Weird.

Pete

 

[Scotfleiger]

No problems. Thank you for looking. 

[Quaxman]

I bought my SAITEK trim wheel long time ago - it's an old story and not FSUIPC related:
After starting/restarting Windows, one has to turn the wheel until the Windows USB device detection sound comes up.

It's a problem in the USB controller of the wheel.