Most of the commonly reported issues and questions are answered in the Frequently Asked Questions (FAQ) option under the Support menu of this website.
*** PLEASE NOTE ***
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
1st December: A new version of the GoFlight Interface Tool for MSFS is now available.
12th November: A new version of the GoFlight Interface Tool for X-Plane is now available.
6th June: A new version of Virtual Flight Sim Hardware is now available (huge update)
21st November: A new version of the GoFlight Interface Tool for FSX/FSXSE/P3D is now available.

46'S still keeping locking up even with SLEEP

Hi Steve,

This problem seems to be specific to the 46's, the 48's work well.

I've tried many different sleep values and "Run event in background" but my 46's dial action always ends up locking up the 46 so it becomes completely none functional until a "reboot" ... these seems more like a buffering problem at the driver level?

Any other suggestions?

Cheers, Rob.

Comments

  • oops "keep locking..."
  • My theory on the GF166 and GF46 lock up issue is that unlike the MCP PRO, GoFlight have not updated the firmware. The MCP PRO before the A25 firmware used to lock up just the same as these devices. I noticed in the GoFlight driver readme, they refer to a rollout of firmware upgrades across the range, but not sure if this ever happened.

    The GoFlight SDK only offers the option to read and write to the device, GIT has very little control. The only thing you can change is the sliders in the Settings tab which delay writing to the GF166 and GF46 devices to help avoid lockups. Also like the GF166, separate out onto different hubs sometimes helps.

    Is it happening in all versions of GIT with all aircraft?

    Best wishes
    Steve
  • I haven't tried using the read/write device delay values, I'll give that a try tonight or tomorrow and see if that helps. Are these values saved per aircraft or global?

    Is there anything in the USB device descriptions that might provide a clue as to what version of firmware they have? For reference my 166s are relatively new (purchased last month) and they have NOT locked up. One of my 46's is also relatively new (last month) and my other 46's is older (year or so) ... both 46's HAVE locked up.

    I can't say if this is aircraft specific, I've really only started doing "custom" configurations of the 46's recently using the JF PA28R for XP11. I have the JF PA28R for P3D V4 also, so I can test it out in that environment.

    Cheers, Rob.
  • Hi Steve,

    I tried several values for the write delay this evening and even other settings to see if there was any change, unfortunately nothing seems to work, the 46 would lock up on any rapid forward and then backward rotary movement. If I rotate slowly, everything works fine.

    The most annoying part of this problem is that it requires a reboot to unlock the 46.

    Cheers Rob.
  • Does it lock up using Goflight driver software?
  • I haven't notice them locking up in P3D V4 side of things using either GIT or just going with GFConfig native ... so far it seems to be XP11 only for lockups and ONLY with the 46's ... the 166's, 48's, MPCPRO, EFIS all working well in XP11.
  • That's strange as the code to write to the device is the same in all versions. I'll take a look and see if I can spot anything.

    Thx
    Steve
Sign In or Register to comment.