Radar Protocol (tracking 0x4C)
Radar on TCP 5188: tracking 0x4C binary with a field mask; both device time and fix time must plot.
On Traxelio
What Radar trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Radar
Point this protocol at Traxelio
Point Radar at Traxelio
-
1
Capture a Radar fingerprint
Confirm a length-framed binary record whose type byte is 0x4C and whose mask can carry both times.
-
2
Point Radar at 5188
Configure only Radar to TCP 5188. Radar on 5188 is not Raveon on 5117 or Ramac on 5251.
-
3
Do not wait for 0x9C
This dialect has no reply byte. A parsed 0x4C record is enough.
-
4
Prove one Radar fix
Send one 0x4C item with both device time and fix time and non-zero lat/lon on 5188 and verify a map point.
Still offline after GPS lock
Radar still not landing
- Radar aimed at the wrong port
Radar on 5188 is not Raveon on 5117 or Ramac on 5251.
- Session up, empty map
A 0x4C item plots only when the mask supplies both device time and fix time. Missing either drops the record.
- No 0x9C, assumed dead
This dialect has no reply byte. Check the map, not the socket for 0x9C.
FAQ
Radar leftover questions
What type byte plots a Radar record?
0x4C tracking only. Any other type is ignored.
When does a Radar record plot?
Both device time and fix time must be present. A record missing either is dropped.
Does Radar emit 0x9C?
This dialect does not write a reply. Silence is not a failed bind.
How are Radar coordinates scaled?
Latitude and longitude are signed integers divided by 360000.
Can a Radar Duo or Trio run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.