Genx on TCP 5148: comma CSV mapped by column numbers for unit id, MM/dd/yyyy stamp, lat/lon, optional ignition ON, and feet altitude.
On Traxelio
Hardware that speaks this protocol
Point this protocol at Traxelio
Confirm a comma CSV with a mapped id and MM/dd/yyyy HH:mm:ss stamp. Reject $GNX_ as GNX.
Configure only Genx to TCP 5148. Genx on 5148 is not GNX on 5106 or FOX on 5105.
Genx has no reply byte. A parsed id plus lat/lon is enough.
Send one comma line whose mapped id and lat/lon parse on 5148 and verify a map point.
Still offline after GPS lock
Genx on 5148 is not GNX $GNX_ on 5106 or FOX A/V CSV on 5105.
The mapped id column must be present and registered. An empty id drops the row.
This dialect has no reply byte. Check the map, not the socket for an ACK.
FAQ
No. Those belong to the GNX dialect. Genx is comma CSV with a numeric column map.
Column 11 must read ON. Any other value is stored as off.
No. There is no reply byte. A parsed id plus lat/lon is the whole handshake.
The row is dropped. No map point is written.
This dialect is positions only. GNX-10, GNX-10L, GNX-20, GNX-3, GNX-5P, and GNX-6 are listed. GNX-2 uses the GNX dialect. There is no SMS family on this row.