Recoda Protocol (0x20001001 / 0x20001011)
Recoda on TCP 5151: LE type 0x20001001 twelve-byte ASCII bind, then 0x20001011 GPS with deg/min plus /3600; no reply.
On Traxelio
What Recoda trackers do once they are on Traxelio
Point this protocol at Traxelio
Point Recoda at Traxelio
-
1
Capture a Recoda fingerprint
Confirm a little-endian type dword 0x20001001 with twelve ASCII bytes, then 0x20001011 GPS.
-
2
Point Recoda at 5151
Configure only Recoda to TCP 5151. Recoda on 5151 is not Radar on 5188 or Naviset on 5194.
-
3
Do not wait for a reply
Recoda has no reply byte. A parsed GPS record is enough.
-
4
Prove one Recoda fix
Send one 0x20001011 record whose flag bit 0 is set and whose status bit 0 is valid, then verify a map point.
Still offline after GPS lock
Recoda still not landing
- Recoda aimed at the wrong port
Recoda on 5151 is not Radar on 5188 or Naviset on 5194.
- Session up, empty map
Heartbeat 0x00001001 and registration 0x20001001 will not plot. GPS 0x20001011 needs flag bit 0.
- No reply, assumed dead
This dialect has no reply byte. Check the map, not the socket for an echo.
FAQ
Recoda leftover questions
Does Recoda send Concox 0x7878 frames?
No. Recoda opens with a little-endian type dword. Bind is 0x20001001 with twelve ASCII bytes. GPS is 0x20001011.
Which Recoda type plots a new coordinate?
0x20001011 with flag bit 0 set and status bit 0 valid. Heartbeat 0x00001001 will not plot.
Does Recoda send a reply?
No. There is no reply byte. A parsed GPS record is the whole handshake.
Where is the Recoda unit key?
On type 0x20001001, twelve ASCII bytes after the version word and the index word.
Can a Recoda unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.