Sanav Protocol (imei=…&rmc=$GPRMC)
Sanav on 5051: imei= and rmc= wrappers around a $GPRMC sentence with A or V status.
On Traxelio
What Sanav trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Sanav
Point this protocol at Traxelio
Point Sanav at Traxelio
-
1
Capture a Sanav fingerprint
Confirm imei= or imei: before a $GPRMC sentence. This is not a bare NMEA line.
-
2
Point Sanav at 5051
Configure only Sanav to 5051. Sanav on 5051 is not GpsGate on 5026 or Sanul on 5186.
-
3
Keep the imei wrapper
A $GPRMC without imei= will not match on 5051.
-
4
Prove one Sanav fix
Send one A-status $GPRMC on 5051 and verify a map point.
Still offline after GPS lock
Sanav still not landing
- Sanav aimed at the wrong port
Sanav on 5051 is not GpsGate on 5026 or Sanul on 5186.
- Bare $GPRMC with no imei=
This dialect needs the imei= wrapper. A bare NMEA sentence will not match.
- Sanav session up, empty map
A void V sentence will not plot. Wait for an A-status $GPRMC after the imei= wrapper.
FAQ
Sanav leftover questions
Does Sanav send Concox 0x7878 frames?
No. Sanav is ASCII. A line starts with imei= or imei:, then a $GPRMC sentence. Concox families use 0x7878 binary login.
Which keys wrap a Sanav $GPRMC?
imei= or imei: is required. rmc= or rmc: may sit between that key and the $GPRMC sentence.
Why does a bare $GPRMC miss the map?
Without the imei= wrapper the line will not match. Add the IMEI key, then send an A-status sentence.
What extra follows the Sanav checksum?
Some units append an IO word: five inputs, ignition, two outputs, charge, and a low-battery flag. The wrapper plus $GPRMC still prove the path.
Can a Sanav unit run SMS setup or a controlled-action flow?
This dialect is positions only. Catalogue devices include CT-24, CT-58, GC-101, and GS-818. There is no SMS family on this row.