Garmin 480 Wiring

From DynonDocs

Jump to: navigation, search

Edit 11 Feb 2009 by Breister - We have three confirmations from people including myself that all functionality is working as expected with v2.3 of the Garmin software.

NOTE!!! Version 2.3 of the Garmin software is the latest (and probably final) version, and you should GET THE UPGRADE!!! It is FREE - you just need to arrange with your local Garmin rep to get it done. Takes about 2-3 hours, and they provide you a new antenna which, together with the software, finally provides full WAAS / GPSS functionality. Version 2.1 would NOT successfully communicate GPS data via ARINC (although there were reports that v2.0 worked fine). Bottom line - there is no good reason NOT to get the upgrade and your full WAAS capability!

On the GNS 480 side, only Input #2 accepts EFIS command. The HS34 has two sets of pins which will output ARINC, but that is only for convenience because both pairs output the exact same thing so you can use HS34 ARINC output #1 or #2. The only output setting is "Enable."


CNX-80 / GNS 480 PLUS D100/D180 WITHOUT HS34 (Serial Only; GPS Only)
Garmin GNS 480 Dynon D100/D180
Plug PIN Description Setting Plug Pin Description Setting Notes
P5 (78 Pin)30Serial #8 Alt Enc / 1200Vertical Fem D2513Serial OutputAlt Encoder / Format 1Provides Baro info to 480
P1 (Main)5RS232 TxD1 (Output)MAPCOM 9600Vertical DB2522 (Yellow)Serial 1 RxAviation 9600Provides GPS Course - no vertical steering. It does not appear possible to output Nav data via Serial connection on the GNS480 - a pity, because a simple switch would allow you to toggle between Nav & GPS. Also stupid, because the inner workings of the 480 are known to be the same as the SL30.
P1 (Main)4RS232 RxD1 (Input)SL 30Vertical DB25 10 (Orange)Serial 1 TxSL 30 Command(?)Pass Nav Course to 480? Unconfirmed what this does, if anything


CNX-80 / GNS 480 WITH HS34 (ARINC - Allows GPSS Vertical Guidance as well as VOR/ILS/LOC)
Garmin GNS 480 Dynon HS34
Plug PIN Description Setting Plug Pin Description Setting Notes
P5 (78 Pin)4ARINC 429 Tx Channel 1AGamma 429 / *HighFem D2523ARINC 429 RX 1AGama GPS / *HighProvides course & vertical GPS steering
P5 (78 Pin)24ARINC 429 Tx Channel 1BGamma 429 / *HighFem D2511ARINC 429 RX 1BGama GPS / *HighProvides course & vertical GPS steering
P5 (78 Pin)5ARINC 429 Tx Channel 2AVOR/ILS / *HighFem D2522ARINC 429 Rx 2AGama Nav / *HighProvides VOR/LOC/ILS steering
P5 (78 Pin)25ARINC 429 Tx Channel 2BVOR/ILS / *HighFem D2510ARINC 429 Rx 2BGama Nav / *HighProvides VOR/LOC/ILS steering
P5 (78 Pin)8ARINC 429 Rx 2AEFIS (Sys 1) / *HighFem D2524 or 25ARINC 429 TxOutput "On" / *HighAlt Encoder and Nav course back to 480
P5 (78 Pin)28ARINC 429 Rx 2BEFIS (Sys 1) / *HighFem D2512 or 13ARINC 429 Tx Output "On" / *HighAlt Encoder and Nav course back to 480
P1 (Main)5RS232 TxD1 (Output)MAPCOM 9600Male D251Serial 1 RxAviation 9600Not Required (ARINC is better)
P1 (Main)4RS232 RxD1 (Input)SL 30Male D2514Serial 1 TxSL 30 CommandShould pass freq. info from x86 or SL30 - Unconfirmed

- * Note: Apparently either "Low" or "High" will work - just be sure that Tx and Rx speeds match on both units. "Low" may be necessary in cases where other equipment is also receiving the same data in parallel - example, TruTrack specifies speed "Low." - Supplemental note: It appears that ARINC "Low" and "High" do not really matter, but that "High" may drop some info from the data stream. Too, TruTrack autopilots will only accept "Low." For these reasons, it may be preferable to set everything to "Low."

Final thought: May wish to keep the serial connection for GPS even if the ARINC proves to work with v2.3, as this would provide a backup connection in the unlikely event that the wires somehow failed in flight. This can be enabled / disabled in the HSI setup so that it does / does not appear on the list of GPS sources.

Personal tools