MTX Protocol (#MTX, CSV)
MTX on TCP 5083: #MTX, IMEI CSV, yyyymmdd hhmmss, decimal lat/lon, and a #ACK reply.
On Traxelio
What MTX trackers do once they are on Traxelio
Point this protocol at Traxelio
Point MTX at Traxelio
-
1
Capture an MTX fingerprint
Confirm a line that opens with #MTX, and a 15-digit IMEI.
-
2
Point MTX at 5083
Configure only MTX to TCP 5083. MTX on 5083 is not Maestro on 5129 or NTO on 5250.
-
3
Wait for #ACK
Traxelio answers #ACK. That reply is not proof of a map point.
-
4
Prove one MTX fix
Send one #MTX line with lat/lon on 5083 and verify a map point.
Still offline after GPS lock
MTX still not landing
- MTX aimed at the wrong port
MTX on 5083 is not Maestro on 5129 or NTO on 5250.
- Got #ACK, empty map
ACK can fire before the CSV parses. Check the date and the lat/lon pair.
- X in the spare columns
X is allowed in the spare slots. It does not drop a parsed fix.
FAQ
MTX leftover questions
Does MTX send Concox 0x7878 frames?
No. MTX is #MTX, ASCII CSV. Concox families use 0x7878 binary login.
What does an MTX reply look like?
Traxelio answers #ACK. That string is not a map point by itself.
Why does an MTX line bind without a map fix?
The date stamp or the lat/lon pair failed to parse. The IMEI field alone is not a fix.
Is every MTX line treated as valid?
Yes. There is no A/V letter. A parsed coordinate pair plots.
Can an MTX unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.