Smart Sole Protocol (#GTXRP= IMEI CSV)
SmartSole on TCP 5178: #GTXRP= IMEI CSV, longitude before latitude, valid 1 plots, no ACK.
On Traxelio
What Smartsole trackers do once they are on Traxelio
Point this protocol at Traxelio
Point Smartsole at Traxelio
-
1
Capture a SmartSole fingerprint
Confirm an ASCII line that opens #GTXRP= then the IMEI, split on $.
-
2
Point SmartSole at 5178
Configure only SmartSole to TCP 5178. SmartSole on 5178 is not Smartcar on 5262 or Path Away on 5099.
-
3
Do not wait for an ACK
SmartSole has no reply byte. A parsed #GTXRP= row is enough.
-
4
Prove one SmartSole fix
Send one #GTXRP= row whose valid flag is 1 on 5178 and verify a map point.
Still offline after GPS lock
Smartsole still not landing
- SmartSole aimed at the wrong port
SmartSole on 5178 is not Smartcar on 5262 or Path Away on 5099.
- Session up, empty map
Valid flag must be 1. Flag 0 binds the IMEI and will not plot.
- No ACK, assumed dead
This dialect has no reply byte. Check the map, not the socket for an ACK.
FAQ
Smartsole leftover questions
Does SmartSole send Concox 0x7878 frames?
No. SmartSole is ASCII that opens #GTXRP=. Concox families use 0x7878 binary login.
Which flag plots a SmartSole fix?
1 plots. 0 is invalid and will not plot.
Does SmartSole send an ACK?
No. There is no reply byte. A parsed #GTXRP= row is the whole handshake.
What order are SmartSole coordinates in?
Longitude then latitude, as signed decimals, immediately after the first yymmddhhmmss stamp.
Can a SmartSole unit run SMS setup or a controlled-action flow?
This dialect is positions only. SmartSole is the listed device. There is no SMS family on this row.