Milesmate Protocol (ApiString={...})
Milesmate on TCP 5176: ApiString={A:imei then hem lat/lon, A or V, and a +##Received OK reply.
On Traxelio
What Milesmate trackers do once they are on Traxelio
Point this protocol at Traxelio
Point Milesmate at Traxelio
-
1
Capture a Milesmate fingerprint
Confirm a line that opens ApiString={ and closes }, with A: IMEI and an A or V status.
-
2
Point Milesmate at 5176
Configure only Milesmate to TCP 5176. Milesmate on 5176 is not Mictrack on 5191 or Hunter PRO on 5116.
-
3
Wait for +##Received OK
Traxelio answers +##Received OK. That string is not proof of a map point.
-
4
Prove one Milesmate fix
Send one ApiString={ wrapper whose status is A on 5176 and verify a map point.
Still offline after GPS lock
Milesmate still not landing
- Milesmate aimed at the wrong port
Milesmate on 5176 is not Mictrack on 5191 or Hunter PRO on 5116.
- Got +##Received OK, empty map
The reply can fire after the wrapper matches. Status must be A and the E:/F: pair must parse.
- Session up, empty map
Status V binds the IMEI and will not plot. Send a wrapper whose letter is A.
FAQ
Milesmate leftover questions
Does Milesmate send Concox 0x7878 frames?
No. Milesmate wraps lettered fields inside ApiString={ }. Concox families use 0x7878 binary login.
Which letter plots a Milesmate fix?
A plots. V is void and will not plot.
What does a Milesmate reply look like?
Traxelio answers +##Received OK. That string is not a map point by itself.
Where is the Milesmate IMEI?
After A: inside the ApiString={ } wrapper, before B: battery.
Can a Milesmate unit run SMS setup or a controlled-action flow?
This dialect is positions only. GB101 and MM101A are listed.