L100 Protocol (ATL / $GPRMC # frames)
L100 on TCP 5112: ATL plus IMEI and $GPRMC, hashed IO tail, ACK 0x01, or @imei,00 index reply.
On Traxelio
What L100 trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak L100
Point this protocol at Traxelio
Point L100 at Traxelio
-
1
Capture an L100 fingerprint
Confirm ATL, a 15-digit IMEI, and $GPRMC, or an L/H archive row.
-
2
Point L100 at 5112
Configure only L100 to TCP 5112. L100 on 5112 is not Hunter PRO on 5116 or ExtremTrac on 5126.
-
3
Wait for 0x01
The common ATL+$GPRMC form is answered with a single 0x01 byte.
-
4
Prove one L100 fix
Send one $GPRMC whose status is A on 5112 and verify a map point.
Still offline after GPS lock
L100 still not landing
- L100 aimed at the wrong port
L100 on 5112 is not Hunter PRO on 5116 or ExtremTrac on 5126.
- Archive type 1 only
Type 1 is answered @imei,00,index,*xor and is not a map point.
These symptoms are answered outside this section:
FAQ
L100 leftover questions
Does L100 send Concox 0x7878 frames?
No. L100 is ATL ASCII around $GPRMC, or L/H archive rows. Concox families use 0x7878 binary login.
What does an L100 ACK look like?
The common form gets a single 0x01 byte. Archive type 1 gets @imei,00,index plus an XOR star.
Why does an L100 OBD row bind without a map fix?
ATLOBD writes PIDs onto the last location. It will not invent a new point.
What do L100 letters N, P, and T mean?
P is SOS. T is tamper. N is a compact location without those alarms.
Can an L100 unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.