VT200 on TCP 5143: ')' framed binary, six-byte hex id, types 0x2086/0x2084/0x2082/0x3089 plus 0x3088 trip bins.
On Traxelio
Point this protocol at Traxelio
Confirm a body that ends with ')' and a six-byte hex id after the first byte, not a parenthesized IMEI CSV.
Configure only VT200 to TCP 5143. VT200 on 5143 is not VTFMS on 5145, OBD Dongle on 5115, or BSTPL on 5241.
VT200 has no reply byte. A parsed 0x2086-family record is enough.
Send one type 0x2086, 0x2084, 0x2082, or 0x3089 whose valid bit is set on 5143 and verify a map point.
Still offline after GPS lock
Type 0x3088 reuses the last point. Send a 0x2086-family record whose valid bit is set.
This dialect has no reply byte. Check the map, not the socket for an ACK.
These symptoms are answered outside this section:
FAQ
No. A VT200 body is unescape-copied until ')' and the unit id is the hex of six bytes after the first byte. Concox families use 0x7878 binary login.
Types 0x2086, 0x2084, 0x2082, and 0x3089. Type 0x3088 is a trip summary that reuses the last map point.
BCD day, month, year in reverse, then hour, minute, second. Latitude is 8 BCD digits and longitude 9, as degrees plus minutes.
An ignition byte (1 = on) instead of a data-type byte. Speed, course, satellites, RSSI, and odometer are omitted on 0x3089.
This dialect is positions only. Type 0x3088 carries trip start/end, hard accel and brake counts, and speed-band totals. There is no SMS family on this row.