Filter
Top Products
Serial Interface Specifications
62 Apollo GX50/60/65 Installation Manual
NAVCOMM DATA OUTPUT
When MapCom output is selected additional NavComm data is provided along with Moving
Map data. The format of the MapCom data output is as follows. This data output is
compatible with the SL30 or SL40 for sending frequency data to the comm or nav unit.
Baud rate: ..........................................9600
Data bits: ...........................................8
Stop bits: ...........................................1
Parity: ................................................none
Output rate: .......................................approx. 1 second
Message length: ................................variable, approx. 83 to 750 characters
The comm data is output using the following format.
$PMRRC<msg_id><msg_data><chksum><cr>
$PMRRV<msg_id><msg_data><chksum><cr>
The checksum is computed by an 8 bit addition of the msg_id and msg_data characters,
ignoring carry if any. The resulting 8 bit checksum is converted to two ASCII characters by
taking the upper and lower nibbles, adding 30h to each, and placing the most significant
character first in the data message.
Example Moving Map Data Output (Extended Data Enabled)
AN 34 1570 34°15.70’ latitude
BW 118 4390 118°43.90’ longitude
C306 306° track angle
D210 210 knots
E02682 268.2nm to waypoint
GR0006 0.6nm right of course
I3059 305.9° desired track
KSFO SFO waypoint ident
L3058 305.8° bearing to waypoint
QE140 14.0° east magnetic variation
T--------- No alarms, data not flagged
<binary data> From Table 7
a—O--F Approach Enabled Off, Active Off, Message On, Parallel Track
Off, Hold Off, and From/To is FROM
cvR001 CDI Valid, Needle Right, Deflection 001°
p+0008 Pressure Altitude, +80 ft
vC000 VDI Valid, Needle Centered, Deflection is 000°
<binary data> From Table 7
tda Flight Plan Waypoint Type data, direct-to, airport type
Figure 18 Moving Map Data Output (Extended Data Enabled)