Concox protocol has advanced support level in flespi telematics hub. Supported devices are below Jimi IoT (Concox) HVT001 Jimi IoT (Concox) GT230 Jimi IoT (Concox) GT300 Jimi IoT (Concox) GK309E Jimi IoT (Concox) Qbit Jimi IoT (Concox) Qbit-M Jimi IoT (Concox) GK310 Jimi IoT (Concox) Q2 Jimi IoT (Concox) GT710 Jimi IoT (Concox) AT1 Jimi IoT (Concox) AT2 Jimi IoT (Concox) AT3 Jimi IoT (Concox) AT4 Jimi IoT (Concox) AT4U Jimi IoT (Concox) AT5 Jimi IoT (Concox) AT6 Jimi IoT (Concox) CT10 Jimi IoT (Concox) GT03A Jimi IoT (Concox) GT03C Jimi IoT (Concox) GT06N Jimi IoT (Concox) GT06E Jimi IoT (Concox) GT06F Jimi IoT (Concox) GT100 Jimi IoT (Concox) GT800 Jimi IoT (Concox) GT08 Jimi IoT (Concox) MOPLUS Jimi IoT (Concox) GV20 Jimi IoT (Concox) GV40 Jimi IoT (Concox) JV200 Jimi IoT (Concox) WeTrack2 Jimi IoT (Concox) WeTrack Lite Jimi IoT (Concox) X1 Jimi IoT (Concox) X3 Jimi IoT (Concox) BL10 Jimi IoT (Concox) BL11 Jimi IoT (Concox) OB22 Jimi IoT (Concox) EG02 Jimi IoT (Concox) ET25 Jimi IoT (Concox) JS40 Jimi IoT (Concox) JC200 Jimi IoT (Concox) JM-VG01U Jimi IoT (Concox) JM-VG02U Jimi IoT (Concox) JM-VL01 Jimi IoT (Concox) JM-VL03 Jimi IoT (Concox) JM-VL04 Jimi IoT (Concox) JM-LL01 Jimi IoT (Concox) JM-LL303 Jimi IoT (Concox) JM-LL305 Jimi IoT (Concox) JC400 Jimi IoT (Concox) JM-VL103 Jimi IoT (Concox) JM-VL802 Jimi IoT (Concox) JM-VL502 Jimi IoT (Concox) JC261 Jimi IoT (Concox) JC450 Jimi IoT (Concox) JC181 Jimi IoT (Concox) JM-VL501 Jimi IoT (Concox) JM-VL512 Jimi IoT (Concox) JM-VL106 Jimi IoT (Concox) VG502 Jimi IoT (Concox) JM-VL02 Jimi IoT (Concox) JC371 Jimi IoT (Concox) JM-VL110C Jimi IoT (Concox) JM-LL705

New settings added for Concox GT06N device: Overspeeding Alarm Vibration Alarm GPS Data Upload Interval

Concox AT6 : fixed parsing of the following settings: Static Mode Cover Remove Alarm Vibration alarm Tamper Alarm Battery Alarm

One more setting parsing is fixed today for Concox AT6 device: Heartbeat Interval

New configuration settings added for the Concox GT08 device, tab Tracking : GPS Data Upload Heartbeat Interval Angle Report

Concox protocol updated: GT03A : timezone setting parsing fixed.

we've added a logic to correctly parse wrong timestamps caused by GPS Rollover problem This problem is caused because GPS date is defined by 10-bit week number which results to max 1024 number. So when this number overflows to 0 then tracker (with firmware algorithms not covering this) starts to send time as it is in the beginning of the 1024 week period which is August 21, 1999.

Concox protocol updated: JV200 : timestamp parsing fixed: timezone shift is not applied.

Concox timestamp parsing fixed: timezone shift is not applied for the following devices: WeTrack Lite X3 ET25 GT300 Q2 GT800

New device supported for concox protocol: Concox JC200

Concox protocol is updated: Information types 0x7 and 0x8 are supported for Data Transfer Common Packet (protocol number 0x94) Device information settings are added for Concox JC200

[Changelog] concox protocol

YuryAheichyk

New device model is supported Concox JC400

YuryAheichyk

New device models are supported:

EvgenyShatilo

New device models are supported:

Concox JM-VL502

EvgenyShatilo

DTC parsing is added for JM-VL502
Multiplier of the parameter can.maf.air.flow.rate is changed to * 0.1. (Updated with accordiance with the official documentation)
Upgrade parsing OBD Data Stream Report (a lot of new parameters is added, and separation for commercial and passenger vehicles.)

EvgenyShatilo

Parsing update for the model JM-VL502:

Alarm and driving behavior parsing has been added.

EvgenyShatilo

Parsing update for the model JM-VL103:

Long format of the answer for the command "MILEAGE#" is now being taken into account:
MILEAGE:ON, Total Mileage:10000km,K:1000,offset:10000000

YuryAheichyk

Concox protocol has been updated, fixed 0x21 packet parsing

EvgenyShatilo

Parsing update for the model JM-VL502:

parameter position.timestamp is renamed to timestamp.
Added report.code parameter which registers the type of the current message.
Made some improvements for the custom command of this model.

EvgenyShatilo

Bug fix for model JM-VL502:
The parameter #alarm.code.description could be subject to error due to incorrect tracker behavior. The bug has been neutralized.

EvgenyShatilo

New model is added: JM-LL02
JM-LL01: commands for this model have been updated.
Added:
- Center Number
- Status
- Heartbeat
- Restart Device
- Working Mode.

EvgenyShatilo

Added commands for models JM-LL01, JM-LL02:

Alarm:
- Vibration Alarm
- Voice alarm
- Tamper Alarm
- Overspeeding Alarm
- Battery Alarm
Actions:
- Where (Obtain real-time position)
- Check (Obtain general information about the device. The response will be stored as a message)
- Status (Update status of the device)
Configuration:
- Delayed Defense (Delayed Defense Setup)

Fixed issue with registering time from the past for package type 0xA for JM-ll models. The essence is that even though the device has a configurable time zone, it still sends this type of message with the UTC 0.

shal

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.

YuryAheichyk

concox protocol has been updated, fixed Custom Command for JC200, JC400, GV40

EvgenyShatilo

Command update
Config setting "G-Sensor sensivity" is added for models JM-LL01, JM-LL02.

EvgenyShatilo

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

baja

new device type added JC261

YuryAheichyk

New device types added:

YuryAheichyk

concox protocol has been changed, added Power Alarm, Harsh deceleration alarm setup, Harsh acceleration alarm setup, Horisontal collision alarm setup settings for JM-VL501

EvgenyShatilo

JM-VL502 parsing change:

Fixed parameter vehicle.vin registration. In case of an invalid value, the parameter value was previously filled with zeros, which caused an error.

EvgenyShatilo

JM-VL04 commands update.
The following commands have been added:

Query current device status
Query current device location
Automatically recognize and check current APN
Change server address
Time Zone settings
Factory reset of the device
Reboot of the device
SOS phone numbers configuration
Center phone number configuration
Configuration of the GPS data sending interval
Geofence alarm coniguration
Vibration alarm
Low battery alarm configuration (External power source also)
Speeding alarm configuration
UBI alert configuration
Harsh acceleration configuration
Harsh breaking configuration
Horizontal collision configuration
Query LBS report
Temporary GPS activation
Vibration sensor sensitivity configuration
Mileage settings
Volume speakers settings