XT013 Protocol (TK, IMEI CSV)
XT013 on TCP 5076: optional HI then TK, IMEI, yymmddhhmmss, signed lat/lon, speed, course, altitude, and F or L fix.
On Traxelio
What XT013 trackers do once they are on Traxelio
Point this protocol at Traxelio
Point XT013 at Traxelio
-
1
Capture an XT013 fingerprint
Confirm a line that reaches TK, then an IMEI. Optional HI digits may precede the verb.
-
2
Point XT013 at 5076
Configure only XT013 to TCP 5076. XT013 on 5076 is not XT2400 on 5138 or Xexun on 5006.
-
3
Do not wait for an ACK
XT013 has no reply byte. A parsed TK, sentence is enough.
-
4
Prove one XT013 fix
Send one TK, sentence whose fix letter is F on 5076 and verify a map point.
Still offline after GPS lock
XT013 still not landing
- XT013 aimed at the wrong port
XT013 on 5076 is not XT2400 tag binary on 5138 or Xexun on 5006.
- Session up, empty map
Fix letter must be F. Letter L binds the IMEI and will not plot.
- No ACK, assumed dead
This dialect has no reply byte. Check the map, not the socket for an ACK.
FAQ
XT013 leftover questions
Does XT013 send Concox 0x7878 frames?
No. XT013 is ASCII. A line reaches TK, then an IMEI and signed lat/lon. Concox families use 0x7878 binary login.
Which letter plots an XT013 fix?
F plots. L is no-fix and will not plot.
Does XT013 send an ACK?
No. There is no reply byte. A parsed TK, sentence is the whole handshake.
Where is the XT013 unit id?
The IMEI sits immediately after TK, before the compact yymmddhhmmss stamp.
Can an XT013 unit run SMS setup or a controlled-action flow?
This dialect is positions only. One catalogue device is listed (XT013). There is no SMS family on this row.