![](/html/dc/dce7/dce76d7d4b1e19b1f8a6bddd1f28a1efe4e1dbc2b90fed31352c4f8172698666/bg1.png)
MGL Avionics
V16 Aviation band transceiver
ICD V1
![](/html/dc/dce7/dce76d7d4b1e19b1f8a6bddd1f28a1efe4e1dbc2b90fed31352c4f8172698666/bg2.png)
Table of Contents
MGL Avionics V16 transceiver communications protocols.........................................................3
Version....................................................................................................................................3
The legal stuff..........................................................................................................................3
General........................................................................................................................................3
Frequencies.................................................................................................................................4
RS232 protocol...................................................................................................................5
General message format:...................................................................................................5
Commands:........................................................................................................................5
Format of Acknowledge message (sent by transceiver)....................................................8
Format of status message (sent by transceiver every 100mS unless setup menu is
active).................................................................................................................................8
Format of the Setup menu message (sent every 200mS if setup menu active)................9
Technical string.................................................................................................................10
CAN bus protocol......................................................................................................................10
Messages from the V16........................................................................................................10
Status message................................................................................................................10
Menu item message..........................................................................................................11
Technical string.....................................................................................................................12
Messages to the V16........................................................................................................12
![](/html/dc/dce7/dce76d7d4b1e19b1f8a6bddd1f28a1efe4e1dbc2b90fed31352c4f8172698666/bg3.png)
MGL Avionics V16 transceiver communications protocols
Version
This document contains preliminary information on the binary communications protocol used
by MGL Avionics VHF airband V16 transceivers.
MGL Avionics does not guarantee correctness of this document. MGL Avionics reserves the
right to change any part of the specification at any time without notice.
The legal stuff
The text in this document is provided in good faith and not subject to written and signed NDA
agreements.
A legal entity implementing this protocol or parts of this protocol agrees to hold MGL Avionics
CC free of liability for any and all consequent liability or claims arising out of use of any and all
information made available in this document.
Any entity making use of this information does so at their own risk and liability.
These conditions are not negotiable and will not be waived. Should the entity not accept these
conditions MGL Avionics does not grant the right to use any of this information in any way.
Usage of this information constitutes acceptance of a legally binding contract in the spirit of
information placed in the public domain for the common good. It follows that any action
against MGL Avionics CC in this context is considered a breach of contract immediately
negating the right to use this information.
General
Communications takes place via RS232 or via CAN bus or both
RS232 settings
9600 Baud
8 Data bits
1 Stop bit
No parity
CAN bus settings
11 bit identifiers
250KBaud
The transceiver transmits regular status messages containing sufficient information to build a
typical display image. The status message is transmitted every 100mS. During special
conditions the status message is sent every 200mS inter spaced with a setup information or
technical information message every 200mS (so the overall message rate remains at
100mS).
![](/html/dc/dce7/dce76d7d4b1e19b1f8a6bddd1f28a1efe4e1dbc2b90fed31352c4f8172698666/bg4.png)
Messages to the transceiver consist of commands. Most commands result in transmission of
an acknowledgment when the command has been received with a matching checksum.
Exceptions to this are the PTT command (no response).
PTT command has to be sent every 100 mS to keep PTT active.
Command messages containing frequency request that are not within the permitted airband
or illegal channel frequencies are ignored and not acknowledged.
The V16 provides two RS232 ports and one CAN bus. Only RS232 port 1 supports this
protocol. RS232 port 2 is reserved for special functions.
Frequencies
Frequencies are transmitted as 4 byte unsigned integer values in the RS232 protocol and 3
byte integer values in the CAN bus protocol,
Frequency values consist of MHZ and 100's of Khz plus a channel number within the 100Khz
band.
Values N=0-15 give the channel where channels 1,2,3,5,6,7,9,10,11,13,14,15 are 8.33Khz
channels and 0,4,8,12 are the 25Khz spaced channels.
Using published frequencies 8.33Khz channels from 0 to 15 correspond:
N ICAO KHZ
0 0 0 25Khz bandwidth
1 5 0
2 10 8.333
3 15 16.666
4 25 25.000 25Khz bandwidth
5 30 25.000
6 35 33.333
7 40 41.666
8 50 50.000 25Khz bandwidth
9 55 50.000
10 60 58.333
11 65 66.666
12 75 75.000 25Khz bandwidth
13 80 75.000
14 85 83.333
15 90 91.666
Examples:
25Khz channel 127.175MHZ = 127112
8.33Khz channel 120.235Mhz = 120206 (actual frequency 120.233333 MHZ)