Assistant Telematics: AVT20
Thanks :) It works in HEX.
Also, it seems that alarms are not supported for this protocol for AVT devices.
Send up protocol documentation and alarm samples from logs.
Below is an real example message from my server containing a Crash / Accident alarm. (The message does not contain all the attributes because some of them are not enabled on the device side and some, such as the number of satellites, are not shown even if enabled)
2b5250543a004e560a4c085b54530023020407000000010c10336400fe01020000000000a5031ae84801410d7507ea050e0d0e28000010150312110105010105003efdf207ea050e0e1236025223
Parsed:
Header(+RPT:) Length(78) IMEI(861076089184830) Device ID(0x23) Protocol Version(0204) Event Type(7) Event State(00) Data Mask(0000010C) Battery Voltage(4147) Battery Level(100) GNSS Info Mask(00FE) GNSS number(1) HDOP(2) Speed(0) Azimuth(0) Altitude(165) Latitude(52.095048) Longitude(21.040501) UTC Time(20260514131440) Event Data Mask(00001015) Main Power VCC(7860) Ignition & Motion State(11) Digital Output State(01) Crash Counter(5) ASC Status(1) Crash X Value(261) Crash Y Value(62) Crash Z Value(-526) Generated Time(20260514141854) Serial Number(0252) Tail Character(23)
Event Type(7) seems to be the key - 7 means Crash alarm for the rest:
0 Terminal Power Event
1 Regular Report Event
2 Moving Event
3 Battery Alarm Event
7 Crash Alarm Event
11 Upgrade Firmware Event
12 External Temperature Alarm Event
13 Ignition Event
14 Main Power Alarm Event
15 Tow Alarm Event
16 Over Speed Alarm Event
17 Reserved
18 Reserved
19 Harsh Behavior Alarm Event
20 G-Sensor Self-Calibration Event
21 Geo Fence Alarm Event
22 Digital Input 1 Event
27 Output Alarm Event
28 Delta AIS Alarm Event
29 PDP Alarm Event
30 BLE Common info Event
31 External Humidity Alarm Event
32 Jamming Alarm Event
I will send full documentation by email
You have to send commands in HEX.