DMT Protocol (0x02 0x55 binary)
DMT on TCP 5137: 0x02 0x55 binary, hello 0x00, data 0x04 or 64-byte 0x10, commit 0x05.
On Traxelio
What DMT trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak DMT
Point this protocol at Traxelio
Point DMT at Traxelio
-
1
Capture a DMT fingerprint
Confirm a binary frame that opens with 0x02 0x55 and a hello type 0x00.
-
2
Point DMT at 5137
Configure only DMT to TCP 5137. DMT on 5137 is not DMT HTTP on 5139.
-
3
Wait for the hello reply
A hello 0x00 is answered with type 0x01. A commit 0x05 is answered with 0x06.
-
4
Prove one DMT fix
Send one 0x04 or 0x10 record with a valid fix on 5137 and verify a map point.
Still offline after GPS lock
DMT still not landing
- DMT aimed at the wrong port
DMT on 5137 is not DMT HTTP on 5139.
- Hello ok, empty map
A hello binds the id. A map point needs a 0x04 or 0x10 data record.
- JSON posted at 5137
JSON Records belong on DMT HTTP 5139. This listen is 0x02 0x55 binary.
FAQ
DMT leftover questions
Does DMT send Concox 0x7878 frames?
No. DMT opens with 0x02 0x55 and a type byte. Concox families use 0x7878 binary login.
What does a DMT hello look like?
Type 0x00 carries a serial then a 15-character unit id. Traxelio answers type 0x01.
Why does a DMT hello bind without a map fix?
Hello only binds the unit. A later 0x04 or 0x10 record must carry a valid fix.
How are DMT coordinates stored?
Latitude and longitude are signed little-endian integers divided by 10 million. Standard record time counts seconds from 2013-01-01.
Can a DMT unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.