DMT HTTP Protocol (JSON Records / Edge)
DMT HTTP on HTTP 5139: JSON IMEI plus Records with FType 0, or a device-edge lat/lng body; HTTP 200 or 400.
On Traxelio
What Dmthttp trackers do once they are on Traxelio
Point this protocol at Traxelio
Point Dmthttp at Traxelio
-
1
Capture a DMT HTTP fingerprint
Confirm a JSON POST with IMEI plus Records, or device.imei plus lat/lng. This is not 0x02 0x55 binary.
-
2
Point DMT HTTP at 5139
Configure only DMT HTTP to HTTP 5139. DMT HTTP on 5139 is not DMT on 5137 or Dragino on 5253.
-
3
Read HTTP 200 as bind, not as a plot
Traxelio answers 200 when the body binds, or 400 when it does not. A 200 is not a map point.
-
4
Prove one DMT HTTP fix
Send one FType 0 record with GpsStat greater than 0, or one edge body with lat/lng, and verify a map point.
Still offline after GPS lock
Dmthttp still not landing
- Binary DMT aimed at 5139
DMT HTTP on 5139 is not DMT 0x02 0x55 binary on 5137.
- HTTP 200, empty map
A 200 means the body bound. A plot needs FType 0 with GpsStat greater than 0, or edge lat/lng.
- HTTP 400 on every POST
The IMEI did not bind, or the JSON is not Records/edge. Fix the unit key before chasing coordinates.
FAQ
Dmthttp leftover questions
Does DMT HTTP send Concox 0x7878 frames?
No. DMT HTTP POSTs JSON with IMEI plus Records, or a device.imei edge object. Concox families use 0x7878 binary login.
Which FType carries the DMT HTTP fix?
FType 0. GpsStat greater than 0 marks it valid. FType 2 is IO. FType 6 is analogue values.
What JSON keys mark a traditional DMT HTTP body?
IMEI plus a Records array. Each record has SeqNo, Reason, DateUTC, and Fields.
Why can HTTP 200 leave the map empty?
200 means the body bound. A traditional record without FType 0, or an edge body without lat/lng, will not plot a new fix.
Can a DMT HTTP unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.