What's new
Van's Air Force

The definitive Van's Aircraft support community! Buying, building or flying an RV? Join our exclusive family of mentors and enthusiasts!

G3X Touch SW v9.52 Available Now (3/24/2025)

Up loaded the system update and went flying. I have just the single screen and have it configured with 2 insets. The one bottom left was configured to normally be a map representation of the flight plan and the one on the right is configured to normally be traffic. After the system update the left inset became a text list of the fight plan waypoints. I tried selecting that page and using menu to change it back to the map but it will not change back. Is this a known problem?
 
I noticed my AP disconnected by itself twice on my first flight after the update, but otherwise no other glitches yet.
 
Draker said:
I noticed my AP disconnected by itself twice on my first flight after the update, but otherwise no other glitches yet.
Click to expand...
This just occurred for me yesterday! First time that has ever happened for me. Just once for me and it was shortly (about 5 minutes) after engaging.
 
Updated to 9.52 yesterday and flew about 2.5hrs. No problems noted and autopilot worked like normal. The only super minor issue was the label on the EIS display for "AUX FUEL" changed to "A FUEL".
 
I usually export my existing configuration to an SD card prior to running a new system software update. That is done in configuration mode.
Export Config.jpg

Then if the system options change or even all customization options disappear I can just restore the prior backup configuration file off the SD card. That restores the options and settings back to values prior to the update. See section 30 of the G3X installation manual.
Inport Config.jpg
 
First flight after 9.52. I had A/P disconnect once and also had a message appear. "SFD network communications error - check wiring" I was able to reboot the G5 and message disappeared. Never had either of these to issues prior.
 
I have three flights completed after installing 9.52 - no issues to report (no A/P disconnect issue for me). One change, I now get a "Traffic" unavailable warning on my G3X at start up which clears within a few minutes. I'm guessing the system in initializing and in the past no message was displayed.
 
Strikhedonia said:
I have three flights completed after installing 9.52 - no issues to report (no A/P disconnect issue for me). One change, I now get a "Traffic" unavailable warning on my G3X at start up which clears within a few minutes. I'm guessing the system in initializing and in the past no message was displayed.
Click to expand...
I'm not sure if this is your case, but a TRFC FAIL msg came along with the 9.41 update
  • Along with these inputs, 3 new CAS Messages were added to the system:
    • TERR INHIBIT – Terrain Alerts Inhibited
    • TA INHIBIT – Traffic Alerts Inhibited
    • TRFC FAIL – Traffic device or traffic input failed
 
supik said:
I'm not sure if this is your case, but a TRFC FAIL msg came along with the 9.41 update
  • Along with these inputs, 3 new CAS Messages were added to the system:
    • TERR INHIBIT – Terrain Alerts Inhibited
    • TA INHIBIT – Traffic Alerts Inhibited
    • TRFC FAIL – Traffic device or traffic input failed
Click to expand...
I upgraded from 9.32 so that makes sense, thank you!
 
bjdecker said:
Check the diagnostics logs; any events in there?
Click to expand...
Thanks for the suggestion. In both cases of failure, the log did output "Fail / Airdata timeout / 00000024 00000000" in the "Autopilot State" column. Sounds like I'll want to start with an E-mail to g3xpert at Garmin.
 
I updated to the 9.52 and still having ADSB drop outs. I have a GDL39R. If I’m flying with some of my friends the two planes with Garmin gear will drop off but my buddy with a UAvonics sky beacon always remains. I can pull my breaker for the gdl39r and push it right back in. Once it reboots all traffic will show back up. After a little while I’ll loose traffic here and there until I pull the breaker again. Seems like it’s happening with my buddies that are running Garmin transponders/adsb equipment.
I had a call in with g3x team and one tech said they were aware of the issue. Months later still have the issue but can’t get any type of reply if there is a fix for this.
Pretty frustrating when you spend the amount of money we do and have these issues. I’m starting to think Garmin will not be my choice for my future build.
 
torquen said:
I updated to the 9.52 and still having ADSB drop outs. I have a GDL39R. If I’m flying with some of my friends the two planes with Garmin gear will drop off but my buddy with a UAvonics sky beacon always remains. I can pull my breaker for the gdl39r and push it right back in. Once it reboots all traffic will show back up. After a little while I’ll loose traffic here and there until I pull the breaker again. Seems like it’s happening with my buddies that are running Garmin transponders/adsb equipment.
I had a call in with g3x team and one tech said they were aware of the issue. Months later still have the issue but can’t get any type of reply if there is a fix for this.
Pretty frustrating when you spend the amount of money we do and have these issues. I’m starting to think Garmin will not be my choice for my future build.
Click to expand...
I was the one who put this on engineerings radar years ago, but still no resolution. However, i was able to make it 80% better. On your ipad, use the forget device function under blue tooth connections for the gdl39. Then add it back via pairing. Also ,be sure you don’t have two different devices connected to the gdl blue tooth connection.
 
lr172 said:
I was the one who put this on engineerings radar years ago, but still no resolution. However, i was able to make it 80% better. On your ipad, use the forget device function under blue tooth connections for the gdl39. Then add it back via pairing. Also ,be sure you don’t have two different devices connected to the gdl blue tooth connection.
Click to expand...
This is directly to my g3x screen. Not using an iPad. Wired in.
 
Okay, I updated a few weeks ago to the latest version, from 9.32, I believe. We now experience at least once a flight where the MFD(PFD2) goes dark and reboots. There is an occasional message on PFD1 saying that the signal to the VP-X has been lost, which probably makes sense given the system architecture if screen 2 loses power. Having checked all the wires and following Occam's razor, I can only assume that this is occurring because it doesn't like the most recent software update. I don't see the previous software version posted to the Garmin website... Do I just need to reach out to Garmin? Has anyone else experienced this issue?
 
543TB said:
Okay, I updated a few weeks ago to the latest version, from 9.32, I believe. We now experience at least once a flight where the MFD(PFD2) goes dark and reboots. There is an occasional message on PFD1 saying that the signal to the VP-X has been lost, which probably makes sense given the system architecture if screen 2 loses power. Having checked all the wires and following Occam's razor, I can only assume that this is occurring because it doesn't like the most recent software update. I don't see the previous software version posted to the Garmin website... Do I just need to reach out to Garmin? Has anyone else experienced this issue?
Click to expand...
While not something we have seen very many times, there is the possibility that the system reset itself. We have tools to determine if that is the case. If there is a problem with the display that results in the display resetting, we log that info.

To export that log, press Menu twice, Tools, Diagnostics and finally Shutdowns. Press the Menu button and select Copy to SD Card. If a shutdown log exists in this page, please email it to us at [email protected].

Thanks,

Justin
 
You must log in or register to reply here.
Back
Top