GL601 Protocol (TLV dataId 81/82 binary)
GL601 on TCP 5257: length-field binary with 15-digit IMEI, record batches, and TLV dataId 81/82 lon/lat.
On Traxelio
What GL601 trackers do once they are on Traxelio
Point this protocol at Traxelio
Point GL601 at Traxelio
-
1
Capture a GL601 fingerprint
Confirm a length-prefixed binary frame with TLV dataId 81 or 82. Reject a +RESP:GT capture as GL200 or GL100.
-
2
Point GL601 at 5257
Configure only GL601 to TCP 5257. GL601 on 5257 is not GL200 on 5004 or GL100 on 5003.
-
3
Do not wait for an ACK
GL601 has no reply byte. A parsed dataId 81 or 82 record is enough.
-
4
Prove one GL601 fix
Send one record whose dataId 81 or 82 carries filled lon/lat and verify a map point.
Still offline after GPS lock
GL601 still not landing
- GL601 aimed at the wrong port
GL601 on 5257 is not GL200 on 5004 or GL100 on 5003.
- Session up, empty map
dataId 81 or 82 must carry lon/lat. A record with no coordinate TLV reuses the last fix and will not plot a new point.
- No ACK, assumed dead
This dialect has no reply byte. Check the map, not the socket for an ACK.
FAQ
GL601 leftover questions
Does GL601 send +RESP:GT text?
No. GL601 sends length-prefixed binary records with TLV dataId 81 or 82. The +RESP:GT text row is GL200.
Which TLV plots a GL601 fix?
dataId 81 or 82. 81 carries lon, lat, fix time, and speed. 82 also carries HDOP, course, altitude, and sats.
Does GL601 send an ACK?
No. There is no reply byte. A parsed dataId 81 or 82 record is enough to plot.
How is the GL601 IMEI packed?
Eight bytes of hex with the first nibble dropped, leaving 15 digits.
Can a GL601 unit run SMS setup or a controlled-action flow?
This dialect is positions only. GL601 and GL601CEU are listed. There is no SMS family on this row.