Communication with the MTi is done via the binary Xbus communication protocol, except for data coming from the MTi device in ASCII format (NMEA). The communication protocol is extensively documented in the MT Low Level Communication Protocol Document.
For many applications, it is crucial to know exactly the various delays and latencies in a system. A discussion on this can be found on BASE.
In case multiple systems are used during a measurement, it is important to have the measurement data synchronized between the systems. Processing synchronised data is much easier because there is no need to resample the data to compensate for timing inaccuracies like clock drift and clock deviations. Synchronization using multiple systems involves two important issues: starting the measurement at the same time and having a fixed time relationship of the sampling instances. Refer to BASE for more information on triggering and synchronization options: Synchronization with the MTi
The internal clock jitter of the MTi is less than 25 ns.
The internal clock of the MTi which generates the sample timing based on the set sample period is accurate to ±10 ppm with a maximum of ±15 ppm (this differs per MTi) over the temperature operating range. Using a typical MT (with an accuracy of 10 ppm), this means that the worst case deviation after a 1 hour log is ± 0.036 seconds (= 3600 s ∙ 10 ppm) or 15 sample counts in 1,440,000 at 400 Hz sample rate (± 25 ns/data packet @ 400 Hz).
In the event that the MTi-G-710 has a GNSS fix, the bias of the clock will be estimated and in the long term there will be no deviation from GPS time. On the short time scale, the clock jitter is the determining factor. Note that only GNSS time pulses (not other GNSS reference times) are used to determine the time reference. This clock bias estimation will improve the accuracy of the crystal used in the MTi-G-710, under normal operating conditions to <1 ppm.
The time pulse used to correct the clock of the MTi-G has minor inaccuracies, caused by the following:
Delay caused by the antenna cable length is compensated for in the GNSS receiver, but will vary with cable length.
The internal clock jitter of the MTi is less than 25 ns. The internal clock of the MTi which generates the sample timing based on the set sample period is accurate to ±10 ppm with a maximum of ±15 ppm (this differs per MTi) over the temperature operating range, if there is no availability of GNSS. Using a typical MT (with an accuracy of 10 ppm), this means that the worst case deviation after a 1 hour log is ± 0.036 seconds (= 3600 s ∙ 10 ppm) or 4 sample counts in 360,000 at 100 Hz sample rate (± 0.1 μs/sample @ 100 Hz).
The MTi has a parallel serial (RS232/RS422/RS485 or alternative UART) and USB interface. However, it is not possible to have communication on both the serial and USB interfaces simultaneously. Therefore, the MTi wakes up as a serial device, unless USB is detected. When a USB interface is detected, the communication will be done via that USB interface.
Default settings for serial connection can be found in the MT Low Level Communication Protocol Document.
The MTi’s RS232 transceiver has RS232 compliant output levels and is compatible with TIA/EIA-232-F specifications. The MTi's RS485/RS422 transceiver has RS485 compliant output levels and is compatible with TIA/EIA-485-A specifications. The differential lines of the RS422/RS485 communication are terminated with a 120Ω resistor.
For completeness, the input and output voltage levels are listed below:
|
|
Low value (binary 1) |
High value (binary 0) |
|
RS232 RX (sensor) [1] |
< 0.8 V |
> 2.5 V |
|
RS232 TX (sensor) |
< -5.0 V[2] |
> 5.0 V[3] |
|
RS422/RS485 RX (sensor) [4] Differential |
< -0.2 V |
> 0.2 V |
|
RS422/RS485 TX (sensor)[5] Differential |
< -2 V |
> 2 V |
[1] typical hysteresis is 0.4V
[2] typical value @ 25ºC and load of 3kΩ is -5.7 V
[3] typical value @ 25ºC and load of 3kΩ is 6.2 V
[4] typical hysteresis is 25mV
[5] with a total differential load resistance of 50Ω (MTi already has 120Ω termination resistance)