XT2400 Protocol (tag-length binary 0x07/0x08 lat/lon)
XT2400 on UDP 5138: PCR format map, then tag 0x03 id, 0x06 unix time, 0x07 lat, 0x08 lon scaled by 1e6.
On Traxelio
What XT2400 trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak XT2400
Point this protocol at Traxelio
Point XT2400 at Traxelio
-
1
Capture an XT2400 fingerprint
Confirm packed tag bytes, not a TK, text line. Tag 0x07 is latitude and 0x08 is longitude.
-
2
Point XT2400 at 5138
Configure only XT2400 to UDP 5138. XT2400 on 5138 is not XT013 on 5076 or Xexun on 5006.
-
3
Load a PCR format first
Without a :wycfg pcr format map the datagram is ignored. Do not wait for an ACK.
-
4
Prove one XT2400 fix
Send one datagram whose 0x07 and 0x08 values are non-zero on 5138 and verify a map point.
Still offline after GPS lock
XT2400 still not landing
- XT2400 aimed at the wrong port
XT2400 on 5138 is not XT013 TK, CSV on 5076 or Xexun on 5006.
- Datagram arrives, empty map
Load a PCR format first. Then 0x07 and 0x08 must be non-zero. A 0,0 pair reuses the last point.
- Walk aborts on an unknown tag
An unmapped tag stops the parse. Restrict the format map to known tags.
FAQ
XT2400 leftover questions
Does XT2400 send TK, CSV like XT013?
No. XT2400 is packed tag/length binary. Latitude is tag 0x07 and longitude is tag 0x08, each divided by 1e6.
Which tags plot an XT2400 fix?
Non-zero 0x07 and 0x08. A 0,0 pair reuses the last known point and will not invent a new one.
Does XT2400 send an ACK?
No. There is no reply byte. A parsed tag walk is the whole handshake.
Why does a valid-looking XT2400 blob miss the map?
Traxelio only walks tags after a PCR format map is configured. With no format, the datagram is dropped.
Can an XT2400 unit run SMS setup or a controlled-action flow?
This dialect is positions only. Catalogue devices include Xirgo XT2400 Series and XT6300 Series. There is no SMS family on this row.