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

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

namo

namo
Concox protocol updated

namo

New settings are added for Concox GV20 device: Heartbeat Interval, Tracking tab and Time Zone, Configuration tab

namo

Concox protocol updated: parameter alternating.current.high is renamed to engine.ignition.status.
Both old and new parameters are registered for now.
Old parameter will be removed in a week, 17-Sep-2020.

namo

namo
Concox protocol updated: old parameter alternating.current.high is removed.

namo

Two new Concox devices have been supported in flespi: JM-VG01U and JM-VG02U

namo

Several settings added for Concox JM-VG01U device:

GPRS Setup, Server Setup - Connectivity tab
GPS Data Upload - Tracking tab
SOS Numbers, Center Number - Configuration tab
Overspeeding Alarm - Alarm tab
Petrol/Electricity Control - Actions tab

namo

This is to announce upcoming significant change in Concox protocol implementation.
The following change will be introduced in a week 03-Nov-2020 at 07:00 UTC:

in the current implementation server sends GMT# command to query time zone setting from the device, if server doesn't know device's time zone (i.e. time zone is not stored in flespi device's setting and not received in login packet from device)
but there are a lot of Concox clones that don't reply to this command or even constantly disconnect after receiving the command, and thus fail to operate with flespi channel
that's why we decided to abandon this practice and remove sending GMT# command from protocol implementation
the change will take effect in a week 03-Nov-2020 at 07:00 UTC
therefore in order your Concox devices continue work well with flespi you should take care of time zone setting by yourselves in advance
to do this you should either create flespi device and setup time zone in it's settings, or configure UTC+0 time zone on your Concox unit

namo

namo
Update installed.

namo

New device added: Concox JM-LL01

namo

Concox protocol updated: added parameter alarm.code that will contain alarm number.
To get alarms numbers meaning please refer to the protocol documentation.

namo

Concox protocol update is planned for the next Thursday, 14-Jan-2121 08:00 UTC: settings will be removed for device type Concox (concox) #16.
After the updated is installed, devices of Concox generic device type will not have any settings, and Settings tab will not be displayed for such devices.

namo

namo
Concox protocol updated: settings are removed for device type Concox (concox) #16

namo

New configuration settings are added for Concox EG02:

Tracking tab:
- GPS Tracking Interval
Configuration tab:
- SOS Numbers
- Center Number
Alarm tab:
- Battery Alarm
- Displacement Alarm
Actions tab:
- Find
- Where
- Arm/Disarm

namo

Concox protocol updated:

fixed date time parsing for protocol numbers 0x22, 0x26, 0x27 - time zone shift is not applied to this packets any more, as they contain time in UTC
new alarm bits are supported for 0x26 and 0x27 protocol numbers:
0x24 Insert charger alarm (apply to asset tracker) - charger.insert.event
0x2D Vehicle Rolling alarm - vehicle.rolling.alarm
0x3C Car theft alarm - car.theft.alarm
0x3D Illegal start of alarm - illegal.start.alarm
0x4B Tilting alarm - tilt.alarm
0x4C Sharp turn alarm - sharp.turn.alarm
0x4D Abrupt lane switching alarm - abrupt.lane.switch.alarm
0x4E Vehicle stability - vehicle.stability.alarm
0x4F Vehicle angle abnormality - vehicle.angle.abnormal.alarm

namo

Concox protocol support is enhanced:
For 0x94 Information transmission packet the following new information types are supported:

0x21 Terminal Bluetooth address - flespi parameter bluetooth.mac.address
0x23 Terminal Bluetooth key - flespi parameter bluetooth.key

namo

Concox protocol updated:
commands sent to the concox devices over the channel's connection will now wait for the reply from device. In the other words, the command will be marked as executed and moved to commands-results queue only after receiving a reply from the device.

namo

The following settings are added for Concox GV40 device:

Configuration tab: GPRS Setup, Server Setup
Tracking tab: GPS Tracking Interval
Configuration tab: Defense Timeout, SOS Numbers, Center Number

namo

Concox protocol updated: parameter rear.light.enum is renamed to rear.light.state.
Both old and new parameters are registered now, old parameter will be removed 22-jun-2021.

namo

Parameters engine.ignition.status and engine.blocked.status are removed for Concox AT6 as invalid for asset trackers. Those parameter won't be registered any more for AT6 device.

namo

GPS Locating Interval (Tracking tab) setting for Concox BL10 tracker has been refactored and now it has additional optional parameter - the second time interval for standby mode.
The reason is that various versions of BL10 devices have either one or two parameters for GTIMER command that is used to configure GPS location interval(s) on the device. So from now on the setting should work for the devices that support both one and two parameters of GTIMER command.