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 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

baja

Concox timestamp parsing fixed: timezone shift is not applied for the following devices:

namo

New device supported for concox protocol: Concox JC200

namo

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

namo

Protocol number 0xAA is supported in concox protocol. Text payload that is contained in 0xAA packet is saved into payload.text parameter.
Applicable for Concox JC200

namo

New settings are added for Concox WeTrack2 device:

tab Tracking: GPS Data Upload
tab Configuration: Delayed Defense, SOS Numbers, Center Number
tab Alarm: Overspeeding Alarm, Vibration Alarm
tab Actions: Restart Device

See WeTrack2 User Manual for more details.

namo

Concox protocol updated: protocol number byte is now stored as protocol.number parameter.

namo

New device type added: Concox AT5

namo

Concox AT5: battery.level parameter added

namo

New settings added for Concox JC200 device, Actions tab:

Upload
Reboot
Reset
Upgrade

namo

namo
Concox JC200: several settings were deleted because they didn't worked with JC200 properly:

Actions tab: Upload, Reboot, Reset, Upgrade
Configuration tab: APN, Server Setup

Please contact us in support chat if you need these or any other settings to be implemented in flespi telematics hub.

namo

Concox protocol updated: implemented Transparent transmission protocol (protocol number 0x9B) for receiving the data from external devices connected to RS232.
Applicable for Concox X3 device.

namo

Concox protocol updated: parameter oil.electric.connection.status is renamed to engine.blocked.status.
Both old and new parameters are registered now, old parameter will be removed 31-jan-2020.

namo

namo
Concox protocol updated: old parameters removed after renaming.

namo

Concox X3 device received two more settings:

Transparent Transmission, Configuration tab:
Restart Device, Actions tab:

namo

Concox JC200: add new setting Picture, Actions tab:

baja

Bugfix: engine.blocked.status boolean parameter parsing fixed: reverted to correct values: true when engine is blocked and false if engine is unblocked.

namo

New setting added for the following Concox devices:
GT100, GV20, X3, WeTrack2, QBit, GT06N, GT06E, GT06F

Where [Actions tab] - Obtain device real-time position

namo

Concox protocol updated: internal implementation changed.

namo

This is to announce upcoming Concox protocol fix:
protocol numbers 0x32 (location) and 0x33 (alarm type) parsing will be updated - date time will be parsed as UTC time (without applying timezone shift).
The updated is applicable to BL10, JS40 and GB100 devices

The update is planned for tomorrow, 2020-07-22 7:00 UTC.
You may contact us with any questions regarding this update via flespi.io chat.

namo

namo
Update installed