Robo Track Protocol (0x00 login / 0x03 GPS)
Robo Track on TCP 5163: 0x00 IMEI login with 0x80 0x01 0x66 ACK, then 0x03 GPS or 0x04 GSM.
On Traxelio
What Robotrack trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Robotrack
Point this protocol at Traxelio
Point Robotrack at Traxelio
-
1
Capture a Robo Track fingerprint
Confirm a 69-byte 0x00 login: 16-byte name then a 15-byte ASCII IMEI.
-
2
Point Robo Track at 5163
Configure only Robo Track to TCP 5163. Robo Track on 5163 is not Riti on 5071 or RST on 5196.
-
3
Wait for the three-byte login ACK
Login is answered 0x80 0x01 0x66. GPS records have no reply.
-
4
Prove one Robo Track fix
Send one 0x03 GPS record on 5163 and verify a map point.
Still offline after GPS lock
Robotrack still not landing
- Robo Track aimed at the wrong port
Robo Track on 5163 is not Riti on 5071 or RST on 5196.
- Login ACK, empty map
0x80 0x01 0x66 only binds the IMEI. Send a 0x03 GPS record to plot.
- GSM records only
Type 0x04 attaches cell to the last point. It will not invent a new coordinate.
FAQ
Robotrack leftover questions
Does Robo Track send Concox 0x7878 frames?
No. Login is byte 0x00 with a 15-byte IMEI. Concox families use 0x7878 binary login.
What ACK follows a Robo Track login?
Three bytes: 0x80, 0x01, 0x66. GPS records have no reply.
Which type plots a Robo Track fix?
Byte 0x03 with lat/lon scaled by 1 000 000. Byte 0x04 is cell-only and will not invent a new point.
Where is the Robo Track IMEI?
Fifteen ASCII digits after a 16-byte name on a 0x00 record.
Can a Robo Track unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.