Tech TLT Protocol (INFOGPRS / *POS=Y)
Tech TLT on UDP 5189: unit-id*POS=Y time, date, NS/EW lat/lon fixes, or unit-id,INFOGPRS battery and temp status.
On Traxelio
What Techtlt trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Techtlt
Point this protocol at Traxelio
Point Techtlt at Traxelio
-
1
Capture a Tech TLT fingerprint
Confirm id*POS=Y or id,INFOGPRS. Reject $$A Techto Cruz and *HQ, H02 captures as the wrong neighbor.
-
2
Point Tech TLT at 5189
Configure only Tech TLT to UDP 5189. Tech TLT on 5189 is not Techto Cruz on 5234 or H02 on 5013.
-
3
Do not wait for an ACK
Tech TLT has no reply byte. A parsed *POS=Y line is enough.
-
4
Prove one Tech TLT fix
Send one *POS=Y line on 5189 and verify a map point. INFOGPRS alone will not plot.
Still offline after GPS lock
Techtlt still not landing
- Tech TLT aimed at the wrong port
Tech TLT on 5189 is not Techto Cruz on 5234 or H02 on 5013.
- Only INFOGPRS arrives
INFOGPRS writes battery, temperature, and RSSI onto the last fix. A *POS=Y line is required to plot.
- No ACK, assumed dead
This dialect has no reply byte. Check the map, not the socket for an ACK.
FAQ
Techtlt leftover questions
Does Tech TLT send $$A lines?
No. Position lines use *POS=Y. $$A length CSV is Techto Cruz, a different row.
Does INFOGPRS plot a map point?
No. INFOGPRS writes battery, temperature, and RSSI onto the last fix. Only *POS=Y plots.
Does Tech TLT send an ACK?
No. There is no reply byte. A parsed *POS=Y line is the whole handshake.
What marks a Tech TLT position line?
The unit id, then *POS=Y, then hh:mm:ss, dd/mm/yy, and NS/EW lat/lon.
Can a Tech TLT unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.