Ndtp V6 on TCP 5243: 0x7E 0x7E signature, conn request 100 binds id, navdata type 0 plots.
On Traxelio
Point this protocol at Traxelio
Confirm a TCP record that starts with 0x7E 0x7E and carries an NPH body.
Configure only Ndtp V6 to TCP 5243. Ndtp V6 on 5243 is not Noran on 5053 or Granit on 5113.
Finish service 0 type 100 with the 16-bit device id on 5243 before expecting map points.
Send one service 1 item type 0 record with flag bit 7 set on 5243 and verify a map point.
Still offline after GPS lock
Ndtp V6 on 5243 is not Noran 0x0008 on 5053 or Granit +RRCB~ on 5113.
Service 0 type 100 binds the 16-bit device id and is stored as not valid. Wait for service 1 item type 0.
Flag bit 7 must be set. A type 0 block with that bit off will not plot.
FAQ
No. Ndtp V6 starts with 0x7E 0x7E and then an NPH body. Concox families use 0x7878 binary login.
Service 0 type 100 binds the 16-bit device id and is answered with result OK. That record is not a map point.
The connection request is stored as not valid and reuses last location. A later service 1 item type 0 record with flag bit 7 is required.
Longitude comes first, then latitude. Each is a signed 32-bit little-endian value divided by 10,000,000. Valid is flag bit 7.
This dialect is positions only. Granit-Navigator is the listed device. There is no SMS family on this row.