GFC-500 Disconnecting

[Rick Junkin]

1 hour ago, PT20J said:

g3xpert mainly deals with the non-certified customers and the latest experimental version is 9.41 so perhaps this is something already addressed that hasn't made it to a certified release yet. 

...which begs the question again, can I load the release that has experimental v9.41 and select certified in the config and still get the correct certified v9.17, but perhaps with some bugs worked out? I know it wouldn't be legal, but would it work? 

[BlueSky247]

You fellas are way more patient than I am. I’d be livid had I coined for a gfc-500 install and Garmin was not actively troubleshooting the problem. 

[PT20J]

2 hours ago, Rick Junkin said:

...which begs the question again, can I load the release that has experimental v9.41 and select certified in the config and still get the correct certified v9.17, but perhaps with some bugs worked out? I know it wouldn't be legal, but would it work? 

Hard to say. From what I understand, there is one G3X Touch code base. So, the 9.XX versions would be sequential from 9.00 (9.01, 9.02... 9.41). Since Garmin skips version numbers in its releases, some are likely versions cut for internal testing but not released to the field. Also, some versions in the sequence are released for certified and some for noncertified. The most current certified version is 9.17. There is no noncertified 9.17. The closest noncertified released versions were 9.14 and 9.22. Garmin's release notes are not very detailed and often say something like "General improvements to system operation" which likely means minor bug fixes. So, it's unclear what you would get with 9.41 running in certified mode. The biggest problem I see is that I don't know how Garmin does it's updates. It could be a complete reload or more likely it is a patch. Sometimes it can be problematic to back out a patch to get back to an earlier version, especially if several versions were skipped.

[Pinecone]

17 hours ago, PT20J said:

Did the D99 happen coincident with the AP Fail? If so, perhaps the GSU 25D is the problem rather than the autopilot. Without understanding the design, it's not possible to know, but maybe the "system" referred to in the failure message is the ADAHRS and not the autopilot. I could see the autopilot perhaps wanting to disengage if the ADAHRS was degrading but perhaps not degraded enough to cause a MISCOMP with the standby. Or maybe it is something external that affects both ADAHRS.

Were the disconnects in different locations to rule out GPS interference in some location?

Nope, N100 N100 at the time of AP Fail.