MXT on TCP 5087: stuffed 0x01...0x04 binary, type 0x31 plots, ACK 0x02, not MTX #MTX text.
On Traxelio
Hardware that speaks this protocol
Point this protocol at Traxelio
Confirm a binary shell that opens 0x01 and closes 0x04. Reject a #MTX, ASCII line as the MTX neighbor.
Configure only MXT to TCP 5087. MXT on 5087 is not MTX on 5083 or NVS on 5101.
Traxelio answers type 0x02 inside the 0x01...0x04 shell. That reply is not proof of a map point.
Send one type 0x31 with non-zero lat/lon on 5087 and verify a map point.
Still offline after GPS lock
MXT on 5087 is not MTX #MTX, ASCII on 5083 or NVS on 5101.
Only type 0x31 plots. A bind on another type will not draw a point. Lat/lon of 0,0 also will not help.
The ACK only proves a 0x31 body was parsed. Check the map for non-zero lat/lon.
FAQ
No. MXT is a binary 0x01...0x04 shell. MTX on 5083 is the #MTX, text dialect.
Type 0x31. Other types can bind the unit id and will not plot.
Traxelio answers type 0x02 inside a stuffed 0x01...0x04 shell. Type 0x03 is NACK and is not sent on a parsed 0x31.
Latitude and longitude are little-endian integers divided by 1 000 000. Course is 45-degree steps.
This dialect is positions only. G-100, MX-100, MXT-100, MTC-700, and IDP-780 class units are listed.