Mictrack on TCP 5191: MT; type; unit; R0 plus-fields, or unit$ then A/V NMEA-like; not Meitrack $$.
On Traxelio
Hardware that speaks this protocol
Point this protocol at Traxelio
Confirm a line that starts with MT; or a unit id then $. Reject $$ as Meitrack and JSON imei as B2316.
Configure only Mictrack to 5191 as TCP or UDP. Mictrack on 5191 is not Meitrack on 5020 or B2316 on 5230.
Mictrack has no reply. A parsed R0 line is enough.
Send one R0 plus-field GPS line on 5191 and verify a map point.
Guided setup available
Set reporting mode
mode,1,60#Check configuration
rconf,1#APN commands depend on the carrier SIM in your tracker, so they are not shown here.
Still offline after GPS lock
Mictrack on 5191 is not Meitrack $$ on 5020 or B2316 JSON on 5230.
R0 carries lat/lon. RH reuses the last point. R1/R2 are wifi/cell and will not plot a new GPS fix.
$$ flag CSV belongs on Meitrack 5020. This listen wants MT; or unit$.
FAQ
No. Mictrack is MT; semicolon plus-fields, or a unit id then $ and an A/V sentence. Concox families use 0x7878 binary login.
No. Mictrack is MT; on 5191. Meitrack is $$ flag CSV on 5020. MT80 and MT90 belong on Meitrack.
R0 plus-fields with lat/lon. RH reuses the last point. R1 and R2 are wifi and cell.
A plots. V is void and will not plot. The MT; R0 path has no A/V letter.
This dialect is positions only. There is no SMS family on this row. B2316 JSON is a different dialect.