Tran Sync Protocol (binary /1800000 lat/lon)
Tran Sync on TCP 5247: packed binary, 8-byte hex unit, lat/lon divided by 1800000, status sign bits, optional odometer RFID ADC tags.
On Traxelio
What Transync trackers do once they are on Traxelio
Point this protocol at Traxelio
Point Transync at Traxelio
-
1
Capture a Tran Sync fingerprint
Confirm packed binary that ends with ##. This is not ^TM pipe CSV and not a=connect text.
-
2
Point Tran Sync at 5247
Configure only Tran Sync to TCP 5247. Tran Sync on 5247 is not Trak Mate on 5127 or Trackbox on 5068.
-
3
Do not wait for an ACK
Tran Sync has no reply byte. A parsed binary frame is enough.
-
4
Prove one Tran Sync fix
Send one frame whose valid bit is set and whose lat/lon divide by 1800000 on 5247 and verify a map point.
Still offline after GPS lock
Transync still not landing
- ASCII Trak Mate aimed at 5247
Tran Sync on 5247 is not Trak Mate ^TM pipe CSV on 5127.
- Session up, empty map
Status bit 0 must be set. A clear valid bit will not plot.
- Coordinates in the wrong ocean
Integers divide by 1800000. Status bits 1 and 2 pick north/south and east/west. Do not treat the pair as /1e6.
FAQ
Transync leftover questions
Does Tran Sync send Concox 0x7878 frames?
No. Tran Sync sends packed binary whose coordinates divide by 1800000. Concox families use 0x7878 binary login.
What scale turns Tran Sync integers into degrees?
Divide latitude and longitude by 1800000. Status bits 1 and 2 pick the sign.
Does Tran Sync send an ACK?
No. There is no reply byte. A parsed binary frame is the whole handshake.
How long is the Tran Sync unit key?
Eight bytes, shown as hex. ASCII ^TM text will not match.
Can a Tran Sync unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.