Esky Protocol (R; semicolon TCP/UDP)
Esky on TCP and UDP 5147: E-header then IMEI, R; satellites, packed time, signed lat/lon, optional 0x inputs.
On Traxelio
What Esky trackers do once they are on Traxelio
Point this protocol at Traxelio
Point Esky at Traxelio
-
1
Capture an Esky fingerprint
Confirm a line that starts with E, carries the IMEI, and has literal R; before lat/lon.
-
2
Point Esky at 5147
Configure only Esky to 5147 as TCP or UDP. Esky on 5147 is not Dway on 5150 or EasyTrack on 5056.
-
3
Expect ACK only on UDP
UDP is answered ACK, plus the text after the last + and #. TCP has no reply.
-
4
Prove one Esky fix
Send one R; line whose lat/lon parse on 5147 and verify a map point.
Still offline after GPS lock
Esky still not landing
- Esky aimed at the wrong port
Esky on 5147 is not Dway AA55 on 5150 or EasyTrack on 5056.
- TCP session up, no ACK, assumed dead
ACK, is UDP only. On TCP, check the map. A parsed R; line is enough.
- IMEI bound, empty map
The line must reach R; plus a lat/lon pair. A header without R; will not plot.
FAQ
Esky leftover questions
Does Esky send Concox 0x7878 frames?
No. Esky is ASCII with R; after the IMEI. Concox families use 0x7878 binary login.
When does Esky answer ACK?
On datagram only: ACK, then the text after the last + then #. A stream session has no reply.
Which marker starts Esky location data?
Literal R; after the IMEI, then satellites and packed date and time.
Do ES610 and MT821 share this dialect?
Yes. Both catalogue rows use this wire. Mictrack ES821 and ES825 do not.
Can an Esky unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.