robertb
Pre-takeoff checklist
Hey there gang,
I have a Skylane with a GNS530W and a GTX330ES transponder. The transponder is misbehaving.
Short version of my question:
What should I do with a bad GTX330ES that I do not need? Send it to Garmin and sell it as a freshly repaired unit? Sell it as it is?
Long version:
The transponder started acting up by giving intermittent "FAIL" messages once the GNS530W initialized and got stable GPS position on fire-up. I could power down the avionics and it would go away. Sometimes it would not give the error message at all and worked fine.
Then it failed and I could not get it to work. If I left the GNS530W turned off, I could not get the transponder to fail. But as I live in a Mode C area, I needed the 530W to feed position data to the 330ES to be ADS-B compliant.
I had an avionics shop spend a couple of hours digging through everything and update the firmware in the 330ES. It worked when I left the avionics shop but failed again a few days later.
So, I purchased another 330ES on my favorite avionics store (eBay). The new one arrived, I installed and configured it. It has been working fine since.
I find it an odd failure mode that if the 530W is off the transponder will work fine. But if the 530W and the 330ES are chatting with each other, the transponder goes into fail mode and will not function at all. (There was no way to clear the fail message that I could find aside from a power-cycle.)
I am as curious about the odd failure mode as I am about what to do with the unit. Any thoughts, contemplations, or feedback is welcome and appreciated!
I have a Skylane with a GNS530W and a GTX330ES transponder. The transponder is misbehaving.
Short version of my question:
What should I do with a bad GTX330ES that I do not need? Send it to Garmin and sell it as a freshly repaired unit? Sell it as it is?
Long version:
The transponder started acting up by giving intermittent "FAIL" messages once the GNS530W initialized and got stable GPS position on fire-up. I could power down the avionics and it would go away. Sometimes it would not give the error message at all and worked fine.
Then it failed and I could not get it to work. If I left the GNS530W turned off, I could not get the transponder to fail. But as I live in a Mode C area, I needed the 530W to feed position data to the 330ES to be ADS-B compliant.
I had an avionics shop spend a couple of hours digging through everything and update the firmware in the 330ES. It worked when I left the avionics shop but failed again a few days later.
So, I purchased another 330ES on my favorite avionics store (eBay). The new one arrived, I installed and configured it. It has been working fine since.
I find it an odd failure mode that if the 530W is off the transponder will work fine. But if the 530W and the 330ES are chatting with each other, the transponder goes into fail mode and will not function at all. (There was no way to clear the fail message that I could find aside from a power-cycle.)
I am as curious about the odd failure mode as I am about what to do with the unit. Any thoughts, contemplations, or feedback is welcome and appreciated!