Riti Protocol (binary prefix + $GPRMC)
Riti on TCP 5071: 16-bit unit id then a $GPRMC sentence with A or V status and reverse date; no ACK byte.
On Traxelio
What Riti trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Riti
Point this protocol at Traxelio
Point Riti at Traxelio
-
1
Capture a Riti fingerprint
Confirm a 16-bit unit id after a two-byte lead, then a $GPRMC sentence that ends at *.
-
2
Point Riti at 5071
Configure only Riti to TCP 5071. Riti on 5071 is not Hunter PRO on 5116, T55 on 5005, or Sanav on 5051.
-
3
Do not wait for an ACK
Riti has no reply byte. A parsed RMC is enough.
-
4
Prove one Riti fix
Send one $GPRMC whose status is A on 5071 and verify a map point.
Still offline after GPS lock
Riti still not landing
- Riti aimed at the wrong port
Riti on 5071 is not Hunter PRO on 5116, T55 on 5005, or Sanav on 5051. Orion on 5070 is a different dialect.
- Session up, empty map
RMC status must be A. A V status will not plot. A prefix without $GPRMC will not plot.
- No ACK, assumed dead
This dialect has no reply byte. Check the map, not the socket for an ACK.
FAQ
Riti leftover questions
Does Riti send Concox 0x7878 frames?
No. Riti sends a short binary prefix then a $GPRMC sentence that ends at *. Concox families use 0x7878 binary login.
Which letter plots a Riti fix?
A plots. V is void and will not plot.
Does Riti send an ACK?
No. There is no reply byte. A parsed $GPRMC is the whole handshake.
Where is the Riti unit id?
A 16-bit number sits after a two-byte lead, before the mode byte and the $GPRMC sentence.
Can a Riti unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row. Catalogue units are SLS-00886, SLS-012SF, and TYN_886.