The byte values of the following examples are shown in hexadecimal. Make sure your application has the ability to communicate in hexadecimal format. In MT Manager, use the Device Data Viewer to see the low level communication. This example is for the MTi-G-710, so not all commands can be used on other MTi products.
The low-level communication emulator (Device Data Viewer) in MT Manager
Before you can change any settings, make sure Config mode is active:
TX: FA FF 30 00 D1
Continue receiving data until the following bytes are received:
RX: FA FF 31 00 D0
Set the configuration
TX: FA FF C0 28 10 20 FF FF 10 60 FF FF 20 10 00 64 40 20 01 90 80 20 01 90 C0 20 00 64 E0 20 FF FF 50 42 00 64 50 22 00 64 D0 12 00 64 73
The list of settings is:
Note the mask: e.g. LatLon, in this example, fixed point 16.32, is also available as fixed point 12.20. That part would then have been 50 41 00 64.
The MT acknowledges with
RX: FA FF C1 28 10 20 FF FF 10 60 FF FF 20 10 00 64 40 20 01 90 80 20 01 90 C0 20 00 64 E0 20 FF FF 50 42 00 64 50 22 00 64 D0 12 00 64 72
Set the baud rate (serial communication only)
TX: FA FF 18 01 80 68
The MT acknowledges with
RX: FA FF 19 00 E8
Set the filter profile (in this case GeneralNoBaro for an MTi-G-710)
TX: FA FF 64 02 00 02 99
The MT acknowledges with
RX: FA FF 65 00 9C
Goto measurement state to start logging data:
TX: FA FF 10 00 F1
Start logging data:
The MT sends the MTData2 message which has the following format:
RX: FA FF 36 31 10 20 02 DF C5 10 60 04 00 45 9D A0 40 20 0C BE DC 9A FA 3F 54 9F 37 41 1C BB 70 80 20 0C BB AA 5C 80 3B 8C 55 01 BB 81 33 00 E0 20 04 00 00 00 81 45
The message is composed as follows:
| FA FF 36 | Preamble, Bus ID and Message ID (0x36 is MTDATA2) |
| 31 | Length of all data |
|
10 20 02 DF C5 ... |
In this case, the highlighted part is the Packet counter (0x1020) with length 0x02 and these 2 bytes are DF C5 (decimal: 57285). Double-clicking a message in the data viewer will show the decimal value in a pop-up screen. All data messages are following with a total of 0x31 bytes (49 bytes). The last data packet is E0 20 04 00 00 00 81 |
| 45 | Checksum for this Xbus message (see Message Structure for a definition of the checksum) |