Garmin GNS 480 Installation Manual

Also see for Apollo CNX80: User Newsletter User Newsletter Supplemental Flight manual Pilot's guide Data list

Appendix B - Serial Interface SpecificationsGNS 480 (CNX80) Installation Manual 560-0982-01 Rev A B-7B.2 SERIAL OUTPUT SPECIFICATIONSAvailable settings for the serial outputs are listed in Table B- 5. Not all settings are available on eachserial output port – refer to section 3.2.1.1 to determine which settings are available on a given port.Table B- 5 - RS-232 Serial Output (TX) SelectionsTX Comment ReferenceNONE No input connected. N/AMAPMX Proprietary interface between GNS 480 and MX20 v5.0 orlater. This interface will support auto chart selection,flightplans with the new flight legs, zoom scale matching,altimeter correction, and ILS and VOR navigation information.(MUST BE USED WITH MAPMX SELECTED ON SAMEINPUT PORT)N/AGNS 480 Proprietary interface to second GNS 480 for cross-talking data(MUST BE USED WITH GNS 480 SELECTED ON SAMEINPUT PORT)N/AMAPCOM Moving map output data, nearest waypoint data, annunciatordata, flight plan waypoints and nav/com data.B.2.1SL70 SL70/SL70R mode control and altitude data.Refer to SL70 installation manual.560-0402-xxIRDA Not currently supported. N/AGTX32 Proprietary interface between GNS 480 and GTX 32/327transponder for mode control.N/AGTX33 /GTX33+TISProprietary interface between GNS 480 and GTX 33/330transponder for mode control (and optional TIS traffic).N/AB.2.1 Mapcom OutputWhen MAPCOM is selected, the GNS 480 will transmit moving map data, nearest waypoint data, flightplan waypoints, and nav/com data on this output. The format of the MapCom output is as follows:Baud rate: ............................................... 9600Data bits: ................................................ 8Stop bits: ................................................ 1Parity: ..................................................... noneOutput rate: ............................................ approx. 1 sec.Message length: ..................................... variable, approx. 164 to 958 bytesMoving map data, nearest waypoint data, and flight plan waypoints are embedded within a packet ofdata, enveloped by and characters. NavComm data uses a different packet protocol,which does not use the and characters.As an example, a snapshot representation of 1 second worth of messages would look like the following:…$PMRRC$PMRRC…(no ETX character).And, the sequence begins again.