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!

I can't get support from Garmin -- can you help?

kirkbauer

Well Known Member
I've been struggling with a GSU 73 problem for over a year now and Garmin has gone silent on me. I'm hoping people here can either (1) help me figure out how to get real help from Garmin or (2) help me track down this problem on my own. Here is email I sent to Garmin support back in January but I haven't heard anything back from them yet.

We are still having issues with our GSU 73 that started Feb 2025 after 12 years and 1300 flight hours with no issues. We have gone through the RMA process three times now. We need to figure out how to properly diagnose the problem and get this resolved. I need guidance on how to proceed.

Here is the history, starting from right now and going backwards in time. Long story short:
  • We think the problem from back in Mar 2025 was actually the config card the whole time and our original GSU 73 was just fine. We replaced the config module in Jun 2025.
  • The RMA units we received in April and again in October seem to be having issues not related to the config module.
  • We are out of any theories as to what is causing our current issues and we need guidance on next steps.
February 2026

The problem continued on my most recent two flights. In the first flight, the altitude, airspeed, VS, and OAT were all X'd out until about 20 minutes into the flight. For the next 10 minutes, it was intermittently working, slowly working more and more often. By about 30 minutes it stopped having an issue and worked fine for the rest of the 2hr flight.

On the next flight I was departing from a Class C so by the time I got into the air the plane had already been running for about 15 minutes. By about 5min into the flight it started working partially. About ten minutes later it stopped failing.

Note that in both cases it was fully broken for about 20 minutes, then about 10 minutes of intermittently working. But in one case we spent most of that 20 minutes on the ground. Note that we have also seen the same pattern in the hangar without the engine running or the plane moving.

Here is a video of the most recent issue:
https://www.dropbox.com/scl/fi/elyd...6.39.mp4?rlkey=kx6cohmxdife8n32s78fdxwx6&dl=0

Also note:
  • No issues with engine indication, so that part of the GSU 73 remained working the entire time
  • No ADAHRS align came up during flight
  • This tells me this is not a power problem. If it was, we'd see everything go offline when it rebooted.
January 2026

The GSU73 intermittently fails on the ground and in flight. At first, it almost constantly fails, spending more time in a failed state than in a working state. But over time it gradually fails less often failed and spends more time working. After about 20 minutes, it works almost 100% of the time, but will still fail occasionally.

Important: this happens in the air but also in the hangar on the ground with the engine shut off.

When I say fail, this is what I mean:
What we have done to troubleshoot:
  • We have replaced the OAT sensor since it was being called out specifically as failed at times. That did not change anything.
  • We have inspected the connectors and everything looks to be in great shape
  • We have inspected the config card and it doesn't seem to be causing the problem (see below -- we previously had a problem with the config card and replaced it)
  • We can't identify how this can be an electrical issue. The unit has multiple power and ground pins and is connected through a VPX. Per the config mode screen it doesn't seem that the device actually powers off, just toggles between failure/working states.
  • As I mentioned, we have gone through the RMA process three times
October 2025

After the GSU 73 had been working for a while (since June 2025) we started seeing the air data failures during flight (airspeed, altitude, VS, TAS, OAT). We replaced the unit through the RMA program. Since that replacement (from October until today) we have had the exact same issues with the air data but additionally after the replacement we started intermittently losing all data from the unit as previously described.

June 2025

Ever since we replaced the unit April 2025 we had occasional complete losses of all data from the GSU 73. Most of the time it would come back online but on at least one occasion it remained offline for the duration of the flight. We were able to reproduce the issue on the ground with the top connector clamshell open. When the config card was slightly pushed it would cause the GSU 73 to fail. When the pressure was released the GSU 73 would work again. We were able to completely and reliably cause the GSU 73 to work and not work just by gently touching the config module.

So we replaced the config module and the wiring harness with a new one. All problems went away for the next few months.

March 2025

Here is the email I sent back in March that led to us replacing the GSU 73 in April.

Since replacing the GSU 73 through this RMA, we have made several flights with the aircraft. We had no issues on two short test flights, but the new GSU 73 has rebooted during two of the three longer flights since it was replaced. When the reboot happened, we temporarily lost all ADAHRS and engine indication data, and then the display showed an "ADAHRS Align" screen (again, during flight).

I was flying during the last reboot which occurred yesterday, Mar 23, at about 2PM EDT. Here is a timeline for that flight:
For about the first 30min of the flight, there were no issues at all
For about the next 60min of the flight, oil pressure readings were inconsistent, varying between a normal pressure and a low pressure. I have several videos showing this behavior.
Then the GSU 73 rebooted. For the final 30min of the flight there were no issues at all
Although it is possible it is an issue with the oil pressure sensor, that doesn't explain the GSU 73 reboots. It also wouldn't explain why the reboot instantly caused the oil pressure to start reading correctly again. I think there may be something wrong with the new GSU 73 causing the reboots and possibly it also affected the oil pressure. Note that we never had any reboots with the original GSU 73.

I also wanted to mention that during the ~60 minutes of mostly inaccurate oil pressure readings, where it swung from low to normal, the lows trended downwards.


February 2025

Here is the email that the builder sent in February that led to our original RMA replacement.

I have a older G3X non-touch with GSU 73
Have been flying 12 years and 1300 hours with no real issues.
3 flights ago for 1/2 of one flight got erroneous oil pressure indications. (Steady in the 70s, then 0, red X, then in 20’s for a bit, then back into the 70’s for rest of flight (15 min of erroneous indications, then 10 min of normal).
next several flights (~10 hr of flight time) all normal indications.

Today during ground run all was normal, but soon after takeoff in IMC All EGT and CHT temps were bouncing all over the place (synchronized at first, all 6 cyld together). Going to red-line , then normal, then to 0, then back to normal. Most aberrations were for 1-3 seconds at a time. (Oil pressure and all other instruments at this time were steady and correct). I opted to continue flight as with engine sound, power was sure it was an instrument issue and not something actually happening. At this time I assumed I had a ground fault of some sort.

Later in the flight, it got weirder, with fuel indications (1 tank at a time) going to 0, then back up, oil pressure going all over the place, single or 2 cylinders showing erratic temperatures, and also sometimes all 6 cylinders temp readings bouncing together.
Also some jumps in RPM which were not happening.
 
I ran into a similar issue once with an RV7/ GSU73, worked good for while then randomly fail, exchanged boxes, checked wiring all the normal stuff. This went on for a few years with random failures. I finally bit the bullet and completely rewired the entire CAN bus, that fixed it. In the process of rewiring, I discovered bundles of coiled up CAN bus wire. Obviously, someone had purchased a "panel in a box" and didn't want to mess with all the excess wire so just coiled it up and stuffed it wherever there was room. 5+ years later no more problems with the system.
 
I'm not sure this is something you will be able to fix yourself, since the GSU 73 is telling you that it has an internal fault:

1773844205780.png
 
I'd call Garmin Experimental Tech support and ask for Randy. I found Randy patient, helpful and very knowledgeable when I was doing a complete panel upgrade last year that involved replacing every wire in my 8.
 
Inspect all the CAN Bus wires for chafing.
Check grounds (fixed two plane's autopilot issues that way)
Open all the connectors and look for stray wire strands (whiskers) that can be possibly shorting things.
 
Last edited:
I had the same issue. Ended up finding that the solder sleeves were allowing the wire to just barely move. Even though when pulled the wire felt secure. I cut all the solder sleeves out and hard soldered. Never a problem again.
The funny part is I would only have this issue in the warm days. Only think I can think of is once my plane warmed up all the wiring either relaxed or slightly moved and would then move the wire in the solder sleeve.
I have done a lot of testing on solder sleeves and honestly can’t believe they are allowed in aviation. They do not provide enough solder to run the wire and create a good fusion. Also the low temp solder used is junk.
 
Agree! Solder sleeves were designed for termination of shields, not for splicing wires.
I know some folks will disagree, but I don't care so please don't try to convince me otherwise!
 
Last edited:
I ran into a similar issue once with an RV7/ GSU73, worked good for while then randomly fail, exchanged boxes, checked wiring all the normal stuff. This went on for a few years with random failures. I finally bit the bullet and completely rewired the entire CAN bus, that fixed it. In the process of rewiring, I discovered bundles of coiled up CAN bus wire. Obviously, someone had purchased a "panel in a box" and didn't want to mess with all the excess wire so just coiled it up and stuffed it wherever there was room. 5+ years later no more problems with the system.

I should mention that we aren't seeing any CAN Bus errors being reported. Do you still think it may be the source of the issue?

I'm not sure this is something you will be able to fix yourself, since the GSU 73 is telling you that it has an internal fault:

View attachment 112722

Yes, I agree with you. But it's our fourth unit in about a year. Is it possible the fault is a side-effect of something external? Is there any way for Garmin to figure that out through a data dump or something?

Inspect all the CAN Bus wires for chafing.
Check grounds (fixed two plane's autopilot issues that way)
Open all the connectors and look for stray wire strands (whiskers) that can be possibly shorting things.

This has all been done, but of course it's still possible we missed something. The unit does have multiple ground pins and that makes me think it is unlikely to be an intermittent grounding issue since it seems not every ground pin could be having connectivity issues, right? Or am I thinking about it wrong?

I had the same issue. Ended up finding that the solder sleeves were allowing the wire to just barely move. Even though when pulled the wire felt secure. I cut all the solder sleeves out and hard soldered. Never a problem again.
The funny part is I would only have this issue in the warm days. Only think I can think of is once my plane warmed up all the wiring either relaxed or slightly moved and would then move the wire in the solder sleeve.
I have done a lot of testing on solder sleeves and honestly can’t believe they are allowed in aviation. They do not provide enough solder to run the wire and create a good fusion. Also the low temp solder used is junk.

Good information, thank you. I'm not the original builder (just a partner in the plane with him) so I'll find out if solder sleeves may be something we could look to replace at least for this device.
 
This has all been done, but of course it's still possible we missed something. The unit does have multiple ground pins and that makes me think it is unlikely to be an intermittent grounding issue since it seems not every ground pin could be having connectivity issues, right? Or am I thinking about it wrong?
Problems I've found were the grounding to the airframe. In one case it was grounded to some bare metal (servo body), which was attached to a primer coated part of the airframe. Second case was a very hard to find bad crimp on a ring terminal. It passed tug tests. Only when I decided that I didn't like the ground location and removed the wire... tugged it again and it came apart.
 
Is Garmin in the business of over the phone troubleshooting endlessly?

I'd go find someone that is in that business and pay them.
 
Is Garmin in the business of over the phone troubleshooting endlessly?

I'd go find someone that is in that business and pay them.

With all the things he’s tried and checked, going to “someone in the business” is going to be nothing more than throwing money away…

The garmin experimental people are the best resource available and it has been my experience that they will work through the problem…
 
First, from my experience with Garmin support I agree whole heartedly with other, get on the phone with them.
2nd, you're not done with Canbus. I scanned quickly but didn't see anything about the 120 ohm resistor.
3rd, you're still not done with Canbus wiring. If you've inspected the wire and the connector ends and still having weird problems you have 2 choices (because there may be a source of excess noise). Either stick an oscilloscope on the wires to see if there is noise, or start replacing wires.
And good luck.
 
With all the things he’s tried and checked, going to “someone in the business” is going to be nothing more than throwing money away…

The garmin experimental people are the best resource available and it has been my experience that they will work through the problem…
Not everyone has the time/ability to effectively troubleshoot /repar electrical gremlins, and Garmin can’t fix everything over the phone (nor should they have to).
Maybe Rocketbob will volunteer to come help you fix it !
 
Last edited:
Is Garmin in the business of over the phone troubleshooting endlessly?

I'd go find someone that is in that business and pay them.
Excellent point. Garmin experimental support is set up for someone who knows what they are doing. They can and are helpful but the main horsepower to get the job done is supplied by the caller. There are too many debug decision trees to list for the OP if he hasn't tackled a sophisticated avionics system before. That being said it can be hard to find a qualified person to do the job, for example Stein only will fix things on systems they have wired.
 
Last edited:
I hate to say it, but this system is over 12 years old and was discontinued many years ago.
I’m a little surprised Garmin is even trying to support it.
Maybe now would be a good time for an upgrade?
 
I've been struggling with a GSU 73 problem for over a year now and Garmin has gone silent on me. I'm hoping people here can either (1) help me figure out how to get real help from Garmin or (2) help me track down this problem on my own. Here is email I sent to Garmin support back in January but I haven't heard anything back from them yet.

We are still having issues with our GSU 73 that started Feb 2025 after 12 years and 1300 flight hours with no issues. We have gone through the RMA process three times now. We need to figure out how to properly diagnose the problem and get this resolved. I need guidance on how to proceed.

Here is the history, starting from right now and going backwards in time. Long story short:
  • We think the problem from back in Mar 2025 was actually the config card the whole time and our original GSU 73 was just fine. We replaced the config module in Jun 2025.
  • The RMA units we received in April and again in October seem to be having issues not related to the config module.
  • We are out of any theories as to what is causing our current issues and we need guidance on next steps.
February 2026

The problem continued on my most recent two flights. In the first flight, the altitude, airspeed, VS, and OAT were all X'd out until about 20 minutes into the flight. For the next 10 minutes, it was intermittently working, slowly working more and more often. By about 30 minutes it stopped having an issue and worked fine for the rest of the 2hr flight.

On the next flight I was departing from a Class C so by the time I got into the air the plane had already been running for about 15 minutes. By about 5min into the flight it started working partially. About ten minutes later it stopped failing.

Note that in both cases it was fully broken for about 20 minutes, then about 10 minutes of intermittently working. But in one case we spent most of that 20 minutes on the ground. Note that we have also seen the same pattern in the hangar without the engine running or the plane moving.

Here is a video of the most recent issue:
https://www.dropbox.com/scl/fi/elyd...6.39.mp4?rlkey=kx6cohmxdife8n32s78fdxwx6&dl=0

Also note:
  • No issues with engine indication, so that part of the GSU 73 remained working the entire time
  • No ADAHRS align came up during flight
  • This tells me this is not a power problem. If it was, we'd see everything go offline when it rebooted.
January 2026

The GSU73 intermittently fails on the ground and in flight. At first, it almost constantly fails, spending more time in a failed state than in a working state. But over time it gradually fails less often failed and spends more time working. After about 20 minutes, it works almost 100% of the time, but will still fail occasionally.

Important: this happens in the air but also in the hangar on the ground with the engine shut off.

When I say fail, this is what I mean:
What we have done to troubleshoot:
  • We have replaced the OAT sensor since it was being called out specifically as failed at times. That did not change anything.
  • We have inspected the connectors and everything looks to be in great shape
  • We have inspected the config card and it doesn't seem to be causing the problem (see below -- we previously had a problem with the config card and replaced it)
  • We can't identify how this can be an electrical issue. The unit has multiple power and ground pins and is connected through a VPX. Per the config mode screen it doesn't seem that the device actually powers off, just toggles between failure/working states.
  • As I mentioned, we have gone through the RMA process three times
October 2025

After the GSU 73 had been working for a while (since June 2025) we started seeing the air data failures during flight (airspeed, altitude, VS, TAS, OAT). We replaced the unit through the RMA program. Since that replacement (from October until today) we have had the exact same issues with the air data but additionally after the replacement we started intermittently losing all data from the unit as previously described.

June 2025

Ever since we replaced the unit April 2025 we had occasional complete losses of all data from the GSU 73. Most of the time it would come back online but on at least one occasion it remained offline for the duration of the flight. We were able to reproduce the issue on the ground with the top connector clamshell open. When the config card was slightly pushed it would cause the GSU 73 to fail. When the pressure was released the GSU 73 would work again. We were able to completely and reliably cause the GSU 73 to work and not work just by gently touching the config module.

So we replaced the config module and the wiring harness with a new one. All problems went away for the next few months.

March 2025

Here is the email I sent back in March that led to us replacing the GSU 73 in April.

Since replacing the GSU 73 through this RMA, we have made several flights with the aircraft. We had no issues on two short test flights, but the new GSU 73 has rebooted during two of the three longer flights since it was replaced. When the reboot happened, we temporarily lost all ADAHRS and engine indication data, and then the display showed an "ADAHRS Align" screen (again, during flight).

I was flying during the last reboot which occurred yesterday, Mar 23, at about 2PM EDT. Here is a timeline for that flight:
For about the first 30min of the flight, there were no issues at all
For about the next 60min of the flight, oil pressure readings were inconsistent, varying between a normal pressure and a low pressure. I have several videos showing this behavior.
Then the GSU 73 rebooted. For the final 30min of the flight there were no issues at all
Although it is possible it is an issue with the oil pressure sensor, that doesn't explain the GSU 73 reboots. It also wouldn't explain why the reboot instantly caused the oil pressure to start reading correctly again. I think there may be something wrong with the new GSU 73 causing the reboots and possibly it also affected the oil pressure. Note that we never had any reboots with the original GSU 73.

I also wanted to mention that during the ~60 minutes of mostly inaccurate oil pressure readings, where it swung from low to normal, the lows trended downwards.


February 2025

Here is the email that the builder sent in February that led to our original RMA replacement.

I have a older G3X non-touch with GSU 73
Have been flying 12 years and 1300 hours with no real issues.
3 flights ago for 1/2 of one flight got erroneous oil pressure indications. (Steady in the 70s, then 0, red X, then in 20’s for a bit, then back into the 70’s for rest of flight (15 min of erroneous indications, then 10 min of normal).
next several flights (~10 hr of flight time) all normal indications.

Today during ground run all was normal, but soon after takeoff in IMC All EGT and CHT temps were bouncing all over the place (synchronized at first, all 6 cyld together). Going to red-line , then normal, then to 0, then back to normal. Most aberrations were for 1-3 seconds at a time. (Oil pressure and all other instruments at this time were steady and correct). I opted to continue flight as with engine sound, power was sure it was an instrument issue and not something actually happening. At this time I assumed I had a ground fault of some sort.

Later in the flight, it got weirder, with fuel indications (1 tank at a time) going to 0, then back up, oil pressure going all over the place, single or 2 cylinders showing erratic temperatures, and also sometimes all 6 cylinders temp readings bouncing together.
Also some jumps in RPM which were not happening.
Ok, I re-read above a bit more closely and don’t see any mention of the termination. Most likely the G3X itself or the GSU25 has its own internal terminator but there would also likely be a separate 120ohm resistor at the far end of the CANBUS. If the connection to this terminator has come loose or opened it will wreak havoc on the entire bus. It will generate reflections. Get hold of a G3X installaton manual and look for 2 things. Which devices have a built in termination AND where is the end node termination ( literally at the other end of the bus). You’ll find a separate 120ohm resistor there.
If you disconnect that bus (remove the connectors) completely and measure for resistance on the CANBUS pair you should have either 120 or 240 ohms, depending on if one of the terminations is internal to a device.

Hope that makes sense.

Great to know Garmin has been willing to try to work this. Given that even the G3X Touch is now 12 year old technology, and given I bought my kit years before I flew my 9A, it’s nice to know I’d still have support.

Good luck.
 
LRU's on the CAN buss can sometimes misbehave and cause problems on the buss, so you might try turning off/removing power from LRU's one at a time and see if that helps.
The system has been working fine this long so unlikely a termination issue but that's easy to check (should be 60 ohms, 2 120 ohm in parallel).
 
LRU's on the CAN buss can sometimes misbehave and cause problems on the buss, so you might try turning off/removing power from LRU's one at a time and see if that helps.
The system has been working fine this long so unlikely a termination issue but that's easy to check (should be 60 ohms, 2 120 ohm in parallel).
Crap. Can’t believe I made that mistake. Thanks for correcting.
 
Back
Top