I have an RV9A with a Garmin GNS430 WAAS GPS and a GTX 330 transponder. The plan being executed with my avionics dealer was to have my GTX 330 sent to Garmin for the ES upgrade (done) and then the avionics dealer would send the upgraded transponder back to me, I would re-install it in my plane, and the guidance was that the transponder would again operate in mode-C until I could get the plane into the avionics shop where they would perform the final steps of building the harness to connect the GTX transponder to the GNS430 GPS, install said harness, test, do the paperwork, and I would be ADSB Out compliant.
Well, today I slid my GTX 330 back into its rack and went for a flight. I was a little skeptical that the transponder would operate in Mode C again, and, unfortunately, I was right. (The older I get, the more skeptical I am and unfortunately, the skepticism is usually right.) No mode C reporting. The local approach control said they were getting my squawk code, but, no mode C altitude. I tried pushing all sorts of buttons on the GTX transponder, including turning altitude reporting on, but, no luck.
It is the weekend of course, so, Garmin and my avionics guy are closed.
Any thoughts on what needs to be done to get my transponder mode C operational?
Thanks,
Curt
Well, today I slid my GTX 330 back into its rack and went for a flight. I was a little skeptical that the transponder would operate in Mode C again, and, unfortunately, I was right. (The older I get, the more skeptical I am and unfortunately, the skepticism is usually right.) No mode C reporting. The local approach control said they were getting my squawk code, but, no mode C altitude. I tried pushing all sorts of buttons on the GTX transponder, including turning altitude reporting on, but, no luck.
It is the weekend of course, so, Garmin and my avionics guy are closed.
Any thoughts on what needs to be done to get my transponder mode C operational?
Thanks,
Curt