- Edited
Fixed Detect ACC setting for TLW2-12B devices
Fixed Detect ACC setting for TLW2-12B devices
Fixed parsing of 0x13, 0x14 reports in case of missing coordinates
parameter collision.status renamed to crash.status
BLE ELA TAG support has been extended to specification 2.0.
Added Alert data parsing, parameters: alert.level and alert.status.
Topflytech protocol is updated: Message type 0x27 0x27 0x25 Alarm message is supprted
Added BLE ELA ANG tag parsing
Fixed 0x24 - Position message report parsing
Added Detect ACC setting for TLD2-L devices
Fixed parsing of 4G-LTE LBS parameters
Parameter rename schedule: on November 5th array-type parameter ble.sensros will be renamed to ble.beacons. Inside each object of the array, the field mac will be renamed to id. Currently both ble.sensors and ble.beacons are registered. Switch your usage to ble.beacons, because ble.sensors will be removed.
Topflytech protocol is updated: fixed parsing of BLE Driver Identification Data Type field of BLE Message report (0x10)
The OBDII DTC codes registration is planned to be changed. Currently, error codes are stored in the can.dtc parameter as an array of strings. To unify with other diagnostic protocol types, errors will be stored as an array of objects.
The changes will be applied in 2 weeks, on May 8, 2025.
For reference, two additional parameters have been added:
can.dtc.strings example:
["P0020","U0001"]
can.dtc.objects example:
[{"standard":"OBDII","code":"P0020"},{"standard":"OBDII","code":"U001"}]
YuryAheichyk changes applied, can.dtc array contain objects now.
For reference, two additional parameters added:
can.dtc.strings example:
["P0020","U0001"]
can.dtc.objects example:
[{"standard":"OBDII","code":"P0020"},{"standard":"OBDII","code":"U001"}]
Added 0x18 Alarm message report parsing
Added 0x16 Position message report parsing
YuryAheichyk changes applied, can.dtc.strings and can.dtc.objects parameters removed