Disha Protocol ($A#A# hash CSV)
Disha on TCP 5097: $A#A# then IMEI, A/V/M/X validity, lat/lon, speed, course, and a closing *.
On Traxelio
What Disha trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Disha
Point this protocol at Traxelio
Point Disha at Traxelio
-
1
Capture a Disha fingerprint
Confirm a line that opens with $A#A# and closes with *.
-
2
Point Disha at 5097
Configure only Disha to TCP 5097. Disha on 5097 is not ExtremTrac on 5126 or Envotech on 5240.
-
3
Do not wait for an ACK
Disha has no reply byte. A parsed $A#A# line is enough.
-
4
Prove one Disha fix
Send one line whose validity is A on 5097 and verify a map point.
Still offline after GPS lock
Disha still not landing
- Disha aimed at the wrong port
Disha on 5097 is not ExtremTrac on 5126 or Envotech on 5240.
- Session up, empty map
Validity must be A. V, M, and X bind the IMEI and will not plot.
- No ACK, assumed dead
This dialect has no reply byte. Check the map, not the socket for an ACK.
FAQ
Disha leftover questions
Does Disha send Concox 0x7878 frames?
No. Disha is hash-delimited ASCII that opens with $A#A# and closes with *. Concox families use 0x7878 binary login.
Which letter plots a Disha fix?
A plots. V, M, and X bind the IMEI and will not plot.
Does Disha send an ACK?
No. There is no reply byte. A parsed $A#A# line is the whole handshake.
Where is the Disha IMEI?
First hash field after $A#A#, immediately before the validity letter.
Can a Disha unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.