Dway Protocol (AA55, CSV)
Dway on TCP 5150: AA55, CSV with IMEI and signed lat/lon; AA55,HB is heartbeat only.
On Traxelio
What Dway trackers do once they are on Traxelio
Point this protocol at Traxelio
Point Dway at Traxelio
-
1
Capture a Dway fingerprint
Confirm AA55, plus IMEI. Reject *XX, or NV: captures as the wrong neighbor.
-
2
Point Dway at 5150
Configure only Dway to TCP 5150. Dway on 5150 is not EasyTrack on 5056.
-
3
Bind the IMEI field
The third CSV field after AA55, is the IMEI.
-
4
Prove one Dway fix
Send one full AA55, data line on 5150 and verify a map point.
-
5
Allow AA55,HB keepalives
Heartbeats refresh the session. They do not plot.
Still offline after GPS lock
Dway still not landing
- Dway aimed at the wrong port
Dway on 5150 is not EasyTrack on 5056 or Cguard on 5123.
- Only AA55,HB traffic
A heartbeat will not plot. Wait for a full AA55, data line or check GPS.
- IMEI mismatch
The third CSV field is the IMEI. A typo prevents the session from binding.
FAQ
Dway leftover questions
Does Dway send Concox 0x7878 frames?
No. Dway is ASCII CSV that starts with the characters AA55,. Concox families use 0x7878 binary login.
Is AA55 a binary header?
No. Those four characters are ASCII. A data line is comma-separated text.
Why does AA55,HB leave the map empty?
That line is a heartbeat. It is answered 55AA,HB,OK. A map point needs a full AA55, data line.
Where is the Dway IMEI?
The third field after AA55, is the IMEI. Index and type sit before it.
Can a Dway unit run SMS setup or a controlled-action flow?
This dialect is positions only. D-WAY is the listed device. There is no SMS family on this row.