Pecifications; B.2.1 Mapcom Output - Garmin GNS 480 Installation Manual

B.2 S O
ERIAL UTPUT
Available settings for the serial outputs are listed in Table B- 5. Not all settings are available on each
serial 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) Selections
TX Comment
N No input connected.
ONE
MAPMX Proprietary interface between GNS 480 and MX20 v5.0 or
later. 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 SAME
INPUT PORT)
GNS 480 Proprietary interface to second GNS 480 for cross-talking data
(MUST BE USED WITH GNS 480 SELECTED ON SAME
INPUT PORT)
M Moving map output data, nearest waypoint data, annunciator
APCOM
data, flight plan waypoints and nav/com data.
SL70 SL70/SL70R mode control and altitude data.
Refer to SL70 installation manual.
I DA Not currently supported.
R
GTX32 Proprietary interface between GNS 480 and GTX 32/327
transponder for mode control.
GTX33 / Proprietary interface between GNS 480 and GTX 33/330
GTX33+TIS transponder for mode control (and optional TIS traffic).

B.2.1 Mapcom Output

When M is selected, the GNS 480 will transmit moving map data, nearest waypoint data, flight
APCOM
plan waypoints, and nav/com data on this output. The format of the MapCom output is as follows:
Baud rate: ............................................... 9600
Data bits: ................................................ 8
Stop bits: ................................................ 1
Parity: ..................................................... none
Output rate: ............................................ approx. 1 sec.
Message length: ..................................... variable, approx. 164 to 958 bytes
Moving map data, nearest waypoint data, and flight plan waypoints are embedded within a packet of
data, enveloped by <STX> and <ETX> characters. NavComm data uses a different packet protocol,
which does not use the <STX> and <ETX> characters.
As an example, a snapshot representation of 1 second worth of messages would look like the following:
<STX>
<id><data><it>
<id><data><it>...
<id><data><it><ETX>
$PMRRC<msg_id><msg_data><chksum><it>
$PMRRC<msg_id><msg_data><chksum><it>...(no ETX character).
And, the sequence begins again.
GNS 480 (CNX80) Installation Manual 560-0982-01 Rev A
S

PECIFICATIONS

Appendix B - Serial Interface Specifications
Reference
N/A
N/A
N/A
B.2.1
560-0402-xx
N/A
N/A
N/A
B-7