Navis Protocol (@NTC / *>S / F20-F60)
Navis on TCP 5019: @NTC then *>S bind, *>T or *>A F-format bodies, Flex ~C, F20/F50/F51/F52/F60 plot.
On Traxelio
What Navis trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Navis
Who ships hardware on this wire
Brands using Navis
Point this protocol at Traxelio
Point Navis at Traxelio
-
1
Capture a Navis fingerprint
Confirm an @NTC header then *>S, *>T, or *>A. Reject Naviset 0b00 IMEI headers as 5194.
-
2
Point Navis at 5019
Configure only Navis to TCP 5019. Navis on 5019 is not Naviset on 5194 or NVS on 5101.
-
3
Expect *<S / *<T / *<A
Traxelio answers *<S after bind, *<T plus the index after *>T, and *<A plus the count after *>A. Those replies are not map points.
-
4
Prove one Navis fix
Send one F20, F50, F51, F52, or F60 record with nav-sensor bit 1 set on 5019 and verify a map point.
Still offline after GPS lock
Navis still not landing
- Navis aimed at the wrong port
Navis on 5019 is not Naviset 0b00/0b01 on 5194 or NVS on 5101.
- Session up, empty map
*>S only binds the unit id. F10, F30, and F40 have no lat/lon. Send F20, F50, F51, F52, or F60 with nav-sensor bit 1 set.
- *<S reply, assumed plotted
The *<S / *<T / *<A replies are not map points. Check the map for an F20-F60 coordinate block.
FAQ
Navis leftover questions
Does Navis send Concox 0x7878 frames?
No. Navis opens @NTC then *>S / *>T / *>A, or Flex ~C / ~T / ~A. Concox families use 0x7878 binary login.
Which Navis formats plot a fix?
F20, F50, F51, F52, and F60 carry lat/lon when nav-sensor bit 1 is set. F10, F30, and F40 will not plot.
What reply does a Navis bind get?
*<S after *>S. *<T plus the index after *>T. *<A plus the count after *>A. Those replies are not map points.
How are Navis F60 coordinates scaled?
Signed integers divided by 600 000. F20, F50, F51, and F52 use little-endian floats in radians, converted to degrees.
Can a Navis unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.