![EverMore GM-X205 Скачать руководство пользователя страница 19](http://html.mh-extra.com/html/evermore/gm-x205/gm-x205_user-manual_2444189019.webp)
EverMore Technology Inc.
2F, No.7, R&D Road 1, Science-Based Industrial Park, Hsinchu, Taiwan, 310, R.O.C.
http://www.emt.com.tw
19
4.2 EVERMORE BINARY MESSAGE SPECIFICATION
The EverMore binary message protocol consists of 3 parts: message header, message body,
and message footer.
Message Header
Message Body
Message Footer
Start Sequence Length of Message Body
Message Checksum
End Sequence
0x10 0x02
1 or 2 bytes
Up to 253 bytes
1 or 2 bytes
0x10 0x03
Message Header
The Message Header consists of 3 or 4 bytes:
Byte #1 - DLE = 0x10
Byte #2 - STX = 0x02
Byte #3 - Length of Message Body + 2
Byte #4 - when Byte #3 equals DLE (0x10), DLE (0x10) is sent out as the 4th byte of the
message header; otherwise it is not sent.
Message Body
When DLE (0x10) is encountered in the message body, it is repeated. The EverMore Binary
Message supports following message types for receiver configuration and status monitoring:
Message Type 0x80: Initialization Command Input
Message Type 0x02: Navigation Data Output
Message Type 0x04: DOP Data Output
Message Type 0x06: Channel Status Output
Message Type 0x08: Measurement Data Output
Message Footer:
The Message Footer consists of 3 or 4 bytes:
Byte #1 - checksum of the Message Body (it is calculated by summing all bytes in the
Message Body and taking the sum modulo 256)
Byte #2 - when Byte #1 equals DLE (0x10), DLE (0x10) is sent out as the 2nd byte of the
message footer; otherwise it is not sent.
Byte #3 - DLE (0x10). If checksum is not 0x10, this DLE character becomes Byte #2
Byte #4 - ETX (0x03). If checksum is not 0x10, this ETX character becomes Byte #3