T622 Iridium on TCP 5248: binary envelope, 15-digit IMEI, then hex tags for lat, lon, Y2K time, valid, and speed.
On Traxelio
Point this protocol at Traxelio
Confirm a binary envelope with a 15-digit IMEI after the header, then hex-tagged lat/lon. Reject @@ CSV and $$ Meitrack lines as the wrong neighbor.
Configure only T622 Iridium to TCP 5248. T622 Iridium on 5248 is not Swiftech on 5217 or Meitrack on 5020.
T622 Iridium has no reply byte. A parsed payload with lat/lon is enough.
Send one payload whose tags include 02 lat, 03 lon, and 05 valid, then verify a map point.
Still offline after GPS lock
T622 Iridium on 5248 is not Swiftech on 5217 or Meitrack on 5020.
The payload must carry tags 02 and 03. Session status alone will not plot.
This dialect has no reply byte. Check the map, not the socket for an ACK.
FAQ
No. T622 Iridium uses a binary envelope with a 15-digit IMEI and hex-tagged lat/lon. Concox families use 0x7878 binary login.
Tag 04 is seconds since 2000-01-01 00:00:00 UTC, stored little-endian.
No. There is no reply byte. A parsed payload is the whole handshake.
Tag 02 is latitude, tag 03 is longitude, tag 04 is time, and tag 05 must be greater than zero. Speed is tag 08.
This dialect is positions only. There is no SMS family on this row.