FutureWay on TCP 5213: hex type 0x20 binds IMEI: then 0xA0 GPS: A/V lines plus optional WIFI and LBS.
On Traxelio
Hardware that speaks this protocol
Point this protocol at Traxelio
Confirm a 16-hex prefix and either IMEI: on type 0x20 or a GPS: line on type 0xA0.
Configure only FutureWay to TCP 5213. FutureWay on 5213 is not GoSafe on 5078 or GNX on 5106.
FutureWay has no reply byte. A parsed GPS:A line is enough.
Send one 0xA0 frame whose GPS: status is A on 5213 and verify a map point.
Still offline after GPS lock
FutureWay on 5213 is not GoSafe on 5078 or GNX on 5106.
Type 0x20 binds the IMEI: field and will not plot. Send a 0xA0 GPS:A line.
This dialect has no reply byte. Check the map, not the socket for an ACK.
FAQ
No. FutureWay opens with a hex type byte, then GPS:, WIFI:, or LBS: lines. Concox families use 0x7878 binary login.
A plots. V is void and will not plot.
No. There is no reply byte. A parsed GPS:A line is the whole handshake.
It binds the digits after IMEI: and does not plot. A map point needs type 0xA0.
This dialect is positions only. Futureway, Smart Crutches, and FP03 are listed. There is no SMS family on this row.