ASPEN and Garmin GTX345 software glitch

[RNC]

SUMMARY: You cannot use a GTX345 transponder unless you have an ARINC429 heading source to override the broken serial interface between your non-GTN GPS and the GTX345.

I am posting a summary of my findings of this with the correct information to avoid others having to sort through it all.

The reason there are multiple conflicting posts in this thread describing the issue is that Garmin's rep has been misleading us on the Beechtalk forums about this issue, and they also misled the first person and his installation shop about this issue.

http://newsroom.garmin.com/press-re...ls-next-generation-all-one-ads-b-transponders

http://i.imgur.com/NWEyM2Z.png

The above clearly states that the CX80/GNS480 is a valid position source for ADS-B on the GTX 345 transponder. This is false, that interface is broken.

http://i.imgur.com/z2rIKLn.png

The above is Garmin's rep telling another GTX345 owner in that thread that the issue is Aspen's fault (that person has a GTN GPS and solved the problem by using a proprietary ethernet interface on his GTN 750 to drive the transponder's input). That post by the Garmin rep is a lie.

http://i.imgur.com/fYEuzve.png

The above is the same Garmin rep in the same thread replying to me saying that this is Aspen's fault. That is still a lie. The fact is that the RS232 interface to the GTX345 is broken, that's how mine is wired up. It is a proprietary interface that does not have the ability to selectively enable or disable heading inputs.

http://i.imgur.com/gfXDBtO.png

The above is the heading input priority page from the GTX345 installation manual. As you can see, ARINC429 trumps RS232 (the proprietary serial interface that mine is using from the newly updated CX80/GNS480). That fixes the problem, by priority override.

http://www.beechtalk.com/forums/viewtopic.php?f=21&t=124608

 

[Canuck]

 

[killrocks]

 

[RNC]

 

[Canuck]

 

[RNC]

 

[Canuck]

 

[sanjiv]

 

[RNC]

 

[rrc1962]