Topflytech on TCP 5047: (IMEI then yymmddhhmmss A or V, lat/lon with N/S E/W, speed, course, closed by ).
On Traxelio
Hardware that speaks this protocol
Point this protocol at Traxelio
Confirm a line that opens with ( IMEI and closes with ). Reject a 0x2323 binary capture as T800 X.
Configure only Topflytech to TCP 5047. Topflytech on 5047 is not T800 X on 5094 or Meitrack on 5020.
Topflytech has no reply byte. A parsed A-status sentence is enough.
Send one sentence whose status is A on 5047 and verify a map point.
Replace {password} with the tracker PIN or password.
Guided setup available
Set upload interval
TIMER,{password},10:600:0:0#Set heartbeat
HBT,{password},10#Set timezone UTC
GMT,{password},0#APN commands depend on the carrier SIM in your tracker, so they are not shown here.
Still offline after GPS lock
Topflytech on 5047 is not T800 X binary 0x2323 on 5094 or Meitrack $$ on 5020.
Status must be A. A V status binds the IMEI and will not plot. A missing closing ) never plots.
This dialect has no reply byte. Check the map, not the socket for an ACK.
FAQ
No. Topflytech wraps IMEI in parentheses ASCII with A or V status. Concox families use 0x7878 binary login.
A plots. V is void and will not plot.
No. There is no reply byte. A parsed closing parenthesis is the whole handshake.
Topflytech is ASCII that opens with ( and closes with ). T800 X is binary 0x2323 with type 0x01 login and 0x02 GPS.
This dialect is positions only. A remote cut-relay is not offered on this row.