PT3000 Protocol (%imei,$GPRMC)
PT3000 on TCP 5045: %imei then a $GPRMC sentence with A or V status and reverse date; no reply byte.
On Traxelio
What PT3000 trackers do once they are on Traxelio
Point this protocol at Traxelio
Point PT3000 at Traxelio
-
1
Capture a PT3000 fingerprint
Confirm a line that starts % then IMEI digits then $GPRMC. Reject >id< wraps and XX binary.
-
2
Point PT3000 at 5045
Configure only PT3000 to TCP 5045. PT3000 on 5045 is not Hunter PRO on 5116 or PT215 on 5197.
-
3
Do not wait for an ACK
PT3000 has no reply byte. A parsed RMC is enough.
-
4
Prove one PT3000 fix
Send one $GPRMC whose status is A on 5045 and verify a map point.
Still offline after GPS lock
PT3000 still not landing
- PT3000 aimed at the wrong port
PT3000 on 5045 is not Hunter PRO on 5116 or PT215 on 5197.
- Bare $GPRMC, empty bind
The line must open with % and the IMEI before $GPRMC. A bare RMC will not bind.
- No ACK, assumed dead
This dialect has no reply byte. Check the map, not the socket for an ACK.
FAQ
PT3000 leftover questions
Does PT3000 send Concox 0x7878 frames?
No. PT3000 is % then digits then $GPRMC. Concox families use 0x7878 binary login.
Which letter plots a PT3000 fix?
A plots. V is void and will not plot.
Does PT3000 send an ACK?
No. There is no reply byte. A parsed $GPRMC is the whole handshake.
Where is the PT3000 unit id?
Immediately after the % mark, before the comma that opens $GPRMC.
Can a PT3000 unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.