Cguard Protocol (NV:/BC: line text)
Cguard on TCP 5123: ID: or IDRO: bind, NV: yymmdd hhmmss colon lat/lon/speed, BC: CSQ1/BAT1 status.
On Traxelio
What Cguard trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Cguard
Point this protocol at Traxelio
Point Cguard at Traxelio
-
1
Capture a Cguard fingerprint
Confirm ID: or IDRO: then NV: or BC:. This is not Cradlepoint CSV and not Dway AA55,.
-
2
Point Cguard at 5123
Configure only Cguard to TCP 5123. Cguard on 5123 is not Cradlepoint on 5118 or Dway on 5150.
-
3
Do not wait for a reply
Cguard has no reply byte. A parsed NV: line is enough.
-
4
Prove one Cguard fix
Send one NV: line after the bind and verify a map point. BC: alone will not plot.
Still offline after GPS lock
Cguard still not landing
- Cguard aimed at the wrong port
Cguard on 5123 is not Cradlepoint on 5118 or Dway on 5150.
- Session up, empty map
NV: plots. BC: reuses the last point. ID: and IDRO: bind only. Send NV: after the bind.
- NAN fields look broken
Accuracy, course, or altitude can be NAN. Traxelio stores those as absent, not as a failed parse.
FAQ
Cguard leftover questions
Does Cguard send Concox 0x7878 frames?
No. Cguard sends ASCII lines that open NV: or BC:. Concox families use 0x7878 binary login.
Which Cguard line plots a fix?
NV: plots. BC: reuses the last map point. ID: and IDRO: bind only.
Does Cguard send a reply?
No. There is no reply byte. A parsed NV: line is the whole handshake.
What does NAN mean on a Cguard NV: line?
Accuracy, course, or altitude can be NAN. Traxelio stores those as absent, not as a failed parse.
Can a Cguard unit run SMS setup or a controlled-action flow?
This dialect is positions only. Five catalogue devices are listed (cGuard Atom, cGuard Beacon, cGuard Litom, cGuard OBD, cGuard Personal). There is no SMS family on this row.