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

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

Parsing of bluetooth.key parameter for Concox EG02 device is fixed.
Now parameters is registered as a HEX string:
"bluetooth.key": "414DC47BF2794E7F154C454192496922"

namo

BLE Key setting is added for Concox EG02 device, Actions tab:

namo

New devices are added:

namo

New device type is added:

Concox JM-VL03

namo

The following settings are added for Concox JM-VL03, Actions tab:

Petrol/Electricity Control - for command RELAY#
Restart Device - for command RESET#

namo

Concox protocol is updated - new protocol numbers are supported:

0xA0 - GPS Location Packet with 4G Base Station
0xA1 - LBS Multi-Base Extended Information Packet with 4G Base Stations
0xA4 - Multi-fence Alarm Packet with 4G Base Station

The update is applicable for Concox JM-VL03

namo

Parameters renaming in Concox protocol: parameter car.theft.alarm is renamed to theft.alarm.
For the sake of backward compatibility both parameters will be registered until 03-Dev-2021.
Old parameter car.theft.alarm will be removed 03-Dec-2021.

baja

0x95 Alarm type report remastered to store alarm.code as separate parameter with additional parsing for the following codes:
0x01 code standing for event "SOS value" true to alarm.event parameter
0x02 code standing for event "Power cut alarm value" true to power.cut.alarm parameter
0x03 code standing for event "Vibration alarm value" true to vibration.alarm parameter
0x04 code standing for event "Enter fence alarm value" true to geofence.status parameter
0x05 code standing for event "Exit fence alarm value false to geofence.status parameter
0x06 code standing for event "Over speed alarm value" true to overspeeding.event parameter
0x09 code standing for event "Moving alarm value" true to movement.event parameter
0x0A code standing for event "Enter GPS dead zone alarm value false to gnss.signal.status parameter
0x0B code standing for event "Exit GPS dead zone alarm value" true to gnss.signal.status parameter
0x0E code standing for event "Low external battery alarm value" true to external.battery.low.alarm parameter
0x19 code standing for event "Low internal battery alarm value" true to internal.battery.low.alarm parameter
0xFE code standing for event "ACC ON Alarm value" true to engine.ignition.status parameter
0xFF code standing for event "ACC OFF Alaram value false to engine.ignition.status parameter
0x29 code standing for event "Harsh acceletation alarm value" true to harsh.acceleration.event parameter
0x30 code standing for event "Harsh braking alarm value" true to harsh.braking.event parameter
0x4C code standing for event "Sharp turn alarm value" true to harsh.cornering.event parameter
0x47 code standing for event "Fatigue driving alarm value" true to fatigue.driving.status parameter
0x2C code standing for event "Sharp Crash alarm value" true to crash.event parameter
0x2A code standing for event "Sharp Left Turn alarm value" true to harsh.turn.left.event parameter
0x2B code standing for event "Sharp Right Turn alarm value" true to harsh.turn.right.event parameter
0x67 code standing for event "Login alarm(RFID) value" true to ibutton.authorized.status parameter
0x68 code standing for event "Log out alarm(RFID) value false to ibutton.authorized.status parameter

namo

Concox protocol updated, parameters

can.left.front.tyre.pressure.status
can.right.front.tyre.pressure.status
can.left.rear.tyre.pressure.status
can.right.rear.tyre.pressure.status

are renamed to
can.left.front.tire.pressure.status
can.right.front.tire.pressure.status
can.left.rear.tire.pressure.status
can.right.rear.tire.pressure.status

Old parameters will be registered until 05-Jan-2022 together with the new ones. Old parameters will be removed 05-Jan-2022.

namo

Concox protocol updated:

command reply from device, that is received in either 0x15, 0x21 or 0x81 protocol numbers, is now stored in the response field of command-result object, for example:
```
{
  "address": {
    "ident": "352503022221111",
    "type": "connection"
  },
  "channel_id": 100,
  "executed": true,
  "id": 6677,
  "name": "custom",
  "properties": {
    "payload": "Picture,innn"
  },
  "response": "PICTURE",
  "timestamp": 1643626857.51175,
  "transport": "tcp"
}
```
Parsing of commands replies into settings values is refactored.

namo

Concox protocol is updated: fixed parsing of wifi.signal.strength parameter, so that it has negative value (dBm) now.

baja

The protocol will be affected by the change in type of parameters gsm.mcc and gsm.mnc to be installed in 2 weeks - May 23rd, 2022: both parameters that now have type "string" will be stored as "number". The possible leading zeroes in MNC will be ignored (e.g. the value "01" will be stored as 1).

namo

New device model is supported Concox JM-LL303

namo

Concox protocol is updated: several new settings are added for Concox JM-LL303

Connectivity tab: GPRS Setup, Server Setup settings
Configuration tab: Time Zone setting
Alarm tab: Vibration Alarm, Tamper Alarm, Battery Alarm, Sensitivity settings
Ations tab: Exit Tamper Alarm, Where settings

If you would like to have more settings for Concox JM-LL303 supported in flespi, please contact us in Support chat.

namo

This is an announce of important upcoming update in Concox protocol.
Manufacturer has confirmed that parameter vehicle.mileage is measured in meters, not in km.
That's why in three days, on the 7th of July 2022, the update will be installed after which the parameter vehicle.mileage will be registered in km. The update will have no backward compatibility.

Below is an example of the message parameter's values before and after the update:
Before the update:
"vehicle.mileage": 21400
after the update:
"vehicle.mileage": 21.400

Please, be prepared for the upcoming changes.

namo

namo The update is installed.
vehicle.mileage is not expressed in km.

namo

Concox protocol is updated: WIFI information collection package 0xC3 is supported. The following flespi parameters are registered for the packet fields:

Date and time (UTC) - timestamp
GPS information satellite number - position.satellites
Latitude - position.latitude
Longitude - position.longitude
Heading, state - position.direction, position.valid, gnss.realtime.status
WIFI MAC1, WIFI MAC2, etc - wifi.mac.address.1, wifi.mac.address.2, etc
WIFI signal strength1, WIFI signal strength2, etc - wifi.signal.strength.1, wifi.signal.strength.2, etc

The update is applicable for Concoc GV40, Concox JM-VL01 device types.

namo

Concox protocol is updated: External module transmission protocol 0x9C packet is supported. The following parameters are registered for different types of modules:

for module type 0x09 Terminal log upload:
```
{
  "payload.text": "$ERROR,183246.00,0,0,0,0,0,3,14.00,-22.0,-42.0,0.000,0,16,0,00,00,2,1118*40",
  "protocol.number": 156, 
}
```

for module type 0x0A Inertial Navigation UBI Protocol (Update):

{
  "gnss.realtime.status": true,
  "position.latitude": 8.159356,
  "position.longitude": -72.614418,
  "position.valid": true,
  "protocol.number": 156,
  "timestamp": 1663970271,
  "ubi.event.data": [
    {
      "acc_change_rate": -27, // Acc_T_Data Vehicle horizontal acceleration change rate
      "acc_x": 0, // Acc_X_Data, accelerated speed of x-axis
      "acc_y": 0, // Acc_Y_Data, accelerated speed of y-axis
      "alarm_type": 0, // UBI_On alarm type
      "event_type": 1, // UBI_kind event type
      "gyr_z": 0, // Gyr_Z_Data, Angular velocity of z-axis
      "ins_state": 0, // INS_Flag INS activated flag
      "number": 1, // SN, serial number of each packet
      "pitch": 0, // Pitch_Angle Vehicle pitch angle
      "roll": 0, // Roll_Angle Vehicle roll angle
      "set_value_a": 0, // UBI_A alarm parameter set value
      "set_value_b": 0, // UBI_B alarm parameter set value
      "speed": 0, // Car_Speed Vehicle speed
      "ubi_serial_number": 8669, // UBI_Num Serial number
      "valid": false, // UBI_Valid UBI valid flag
      "yaw": 0 // Yaw_Angle Vehicle orientation change angle
    },
    ...
  ],
  "ubi.event.end.status": true

namo

Concox protocol is updated: the following packets are supported:

WiFi Information Packet over 4G 0xA2

message example

{
  "gsm.cellid": 206184707,
  "gsm.cellid.1": 206107414,
  "gsm.cellid.2": 206107444,
  "gsm.cellid.3": 206107443,
  "gsm.cellid.4": 206150156,
  "gsm.cellid.5": 0,
  "gsm.cellid.6": 0,
  "gsm.lac": 50213,
  "gsm.lac.1": 50213,
  "gsm.lac.2": 50213,
  "gsm.lac.3": 50213,
  "gsm.lac.4": 50213,
  "gsm.lac.5": 0,
  "gsm.lac.6": 0,
  "gsm.mcc": 724,
  "gsm.mnc": 10,
  "gsm.signal.dbm": 65,
  "gsm.signal.dbm.1": 54,
  "gsm.signal.dbm.2": 51,
  "gsm.signal.dbm.3": 47,
  "gsm.signal.dbm.4": 33,
  "gsm.signal.dbm.5": 0,
  "gsm.signal.dbm.6": 0,
  "gsm.timing.advance": 255,
  "protocol.number": 162,
  "timestamp": 1664144804,
  "wifi.mac.address.1": "78:E9:CF:1C:BF:7F",
  "wifi.mac.address.2": "74:DA:DA:ED:03:6A",
  "wifi.mac.address.3": "88:40:33:70:CE:B8",
  "wifi.mac.address.4": "94:2C:B3:A7:8A:EF",
  "wifi.mac.address.5": "00:E0:20:80:08:58",
  "wifi.mac.address.6": "80:8F:E8:5E:E2:E1",
  "wifi.signal.strength.1": -60,
  "wifi.signal.strength.2": -69,
  "wifi.signal.strength.3": -72,
  "wifi.signal.strength.4": -76,
  "wifi.signal.strength.5": -76,
  "wifi.signal.strength.6": -81
}

LBS Alarm Packet over 4G 0xA5
message example
```
{
  "alarm.code": 3,
  "battery.charging.status": false,
  "battery.level": 15,
  "defense.active.status": false,
  "engine.blocked.status": false,
  "engine.ignition.status": true,
  "gnss.status": false,
  "gsm.cellid": 206184707,
  "gsm.lac": 50213,
  "gsm.mcc": 724,
  "gsm.mnc": 10,
  "gsm.signal.level": 100,
  "protocol.number": 165,
  "vibration.alarm": true
}
```

The update is applicable for Concox JM-LL303

namo

Concox protocol is updated: the following modules are added for GPS Position Packet 0x70 report:

Information about the WiFi hotspot 0x36
```
{
  "battery.voltage": 3.72,
  "event.enum": 14,
  "gnss.satellites": 6,
  "position.altitude": 214,
  "position.direction": 173,
  "position.latitude": 43.173716,
  "position.longitude": -80.226738,
  "position.speed": 0,
  "position.timestamp": 1664186164,
  "position.valid": true,
  "protocol.number": 112,
  "timestamp": 1664186164,
  "wifi.mac.address.1": "54:64:D9:34:F2:11",
  "wifi.mac.address.2": "40:B0:34:7F:74:11",
  "wifi.mac.address.3": "D0:57:94:B6:3F:11",
  "wifi.mac.address.4": "5E:BA:EF:67:FE:11",
  "wifi.mac.address.5": "58:EF:68:B9:BF:11",
  "wifi.mac.address.6": "60:38:E0:A1:A3:11",
  "wifi.signal.strength.1": -27,
  "wifi.signal.strength.2": -35,
  "wifi.signal.strength.3": -47,
  "wifi.signal.strength.4": -52,
  "wifi.signal.strength.5": -54,
  "wifi.signal.strength.6": -57
}
```
Master LTE station 0x43
```
{
  "battery.voltage": 3.77,
  "event.enum": 14,
  "gnss.satellites": 3,
  "gsm.cellid": 3893821440,
  "gsm.mcc": 310,
  "gsm.mnc": 4,
  "gsm.signal.dbm": 57,
  "gsm.tac": 31955,
  "position.altitude": 190,
  "position.direction": 351,
  "position.latitude": 32.895229,
  "position.longitude": -96.870916,
  "position.speed": 0,
  "position.timestamp": 1604029450,
  "position.valid": true,
  "protocol.number": 112,
  "timestamp": 1604029450
}
```