concox protocol has been updated, fixed Custom Command for JC200, JC400, GV40
Command update Config setting "G-Sensor sensivity" is added for models JM-LL01, JM-LL02.
Parsing update for model JM-LL702. Added registration of alarm parameters. In addition to the alarm.code, statuses are now registered separately: Key 0x01 described in the docs as SOS is stored as parameter alarm.event Key 0x02 described in the docs as Power cut alarm is stored as parameter power.cut.alarm Key 0x03 described in the docs as Vibration alarm is stored as parameter vibration.alarm Key 0x04 described in the docs as Enter fence alarm is stored as parameter geofence.status Key 0x05 described in the docs as Exit fence alarm is stored as parameter geofence.status Key 0x06 described in the docs as Over speed alarm is stored as parameter overspeeding.event Key 0x09 described in the docs as Moving alarm is stored as parameter towing.event Key 0x0A described in the docs as Enter GPS dead zone alarm is stored as parameter gnss.signal.status Key 0x0B described in the docs as Exit GPS dead zone alarm is stored as parameter gnss.signal.status Key 0x13 described in the docs as Tamper Alert is stored as parameter tamper.alarm Key 0x14 described in the docs as Door Alert is stored as parameter door.alarm Key 0x19 described in the docs as Internal low battery alarm is stored as parameter internal.battery.low.alarm Key 0xFE described in the docs as ACC ON Alarm is stored as parameter engine.ignition.status Key 0xFF described in the docs as ACC OFF Alaram is stored as parameter engine.ignition.status
new device type added JC261
EvgenyShatilo applied zeroed timezone fix with 0xA packet for JM-VL03 devices. They always report time in that packet in UTC timezone despite timezone configured via device settings.
New device types added:
concox protocol has been changed, added Power Alarm, Harsh deceleration alarm setup, Harsh acceleration alarm setup, Horisontal collision alarm setup settings for JM-VL501
JM-VL502 parsing change:
JM-VL04 commands update. The following commands have been added:
Concox protocol updated. Fixed Working mode setting (Tracking tab) for JM-LL01 and JM-LL02
Concox protocol has been updated, new devices added:
Concox protocol has been updated, added 0x000A Charging voltage and 0x000B Battery temperature status id parsing from JM-LL301, JM-LL302, JM-LL303, JM-LL701, JM-LL702 devices
Concox protocol has been changed, added Speed parameter parsing for Report of alarm and driving behavior data 0x03 report from JM-VL502
Concox protocol has been updated, added battery.level parameter for JM-LL01, JM-LL02 devices
Concox protocol has been updated, added JM-VL02 device
Update parsing #gsm.signal.dbm parameter for the type 0x70. Previously, the calculation was performed incorrectly without taking into account the sign of the value. This parameter shows the cellular signal strength in dbm. Such values must be presented in negative form. The change has been agreed upon with the hardware manufacturer. Example: previous value 50, now it will be -50 dbm.
Fixed date and time parsing of 0xA0 - GPS Location Packet (UTC, 4G Base Station Data) report from JM-VL512
Concox protocol updated: fixed Working Mode settings, Traking tab for Jimi IoT AT1
The protocol will be affected by the change in parameter can.dtc to be installed in 2 weeks - Mar 15th, 2024: the parameter can.dtc is currently of string type and will be converted to type array with separate DTC codes.
Added parameter can.dtc.array as an example of future implementation of can.dtc
YuryAheichyk changes have been applied, the can.dtc parameter type changed to array
All changes were applied in accordance with the manufacturer's recommendations.
