Carscop Protocol (* UB05 then A/V, caret ^)
Carscop on TCP 5040: UB05 plus 15-digit IMEI, then * hhmmss A/V lat/lon, frames closed by ^.
On Traxelio
What Carscop trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Carscop
Point this protocol at Traxelio
Point Carscop at Traxelio
-
1
Capture a Carscop fingerprint
Confirm a caret-closed sentence with UB05 plus 15 IMEI digits, then * and an A/V letter.
-
2
Point Carscop at 5040
Configure only Carscop to TCP 5040. Carscop on 5040 is not Cellocator on 5033 or CarTrack on 5061.
-
3
Do not wait for an ACK
Carscop has no reply byte. A parsed A-status body is enough.
-
4
Prove one Carscop fix
Send one * body whose status is A and verify a map point.
Still offline after GPS lock
Carscop still not landing
- Carscop aimed at the wrong port
Carscop on 5040 is not Cellocator on 5033 or CarTrack on 5061.
- No IMEI on the * body
Send a UB05 plus 15-digit IMEI before orphan * fixes.
- Status V forever
The sentence can parse. The map stays empty until an A status arrives.
FAQ
Carscop leftover questions
What closes a Carscop sentence?
A caret ^. A CR closer is Carcell, not Carscop.
Which letter plots a Carscop fix?
A plots. V is void and will not plot.
Does Carscop send an ACK?
No. There is no reply byte. A parsed A-status body is the whole handshake.
Where is the Carscop IMEI?
After the UB05 marker, fifteen digits. A * body with no UB05 needs a session already bound.
Can a Carscop unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.