[Changelog] coban protocol

namo

flespi telematics hub supports coban protocol.

List of supported devices

Coban GPS102
Coban GPS103-B
Coban GPS104
Coban GPS303-C
Coban GPS303-F
Coban GPS303-G
Coban GPS303-H
Coban GPS303-I
Coban GPS306
Coban GPS311
Coban GPS403-A
Coban GPS403-B

namo

Coban protocol updated: added custom command.

namo

Block Engine setting was added for Coban GPS102 and Coban GPS103-B devices, Actions tab.

In Format fields you should choose one of the following:

Numbers - if your device accepts numerical commands (109 - cut off oil and power, 110 - resume oil and power)
Letters - if your devices accepts letter commands (J - cut off oil and power, K - resume oil and power)

namo

New settings added for Coban GPS102, GPS103-B, GPS303-C, GPS306 devices, Actions tab:

Time Zone - set device time zone
Tracking - enable repeated tracking with specified interval

namo

Coban protocol updated:

added new parameter event.code which contains keyword from device's message
parameter oil.power.cut.off.status is renamed to engine.blocked.status
parameter oil.power.cut.off.event is deprecated, event.code=509 will be registered instead

Deprecated parameters oil.power.cut.off.status and oil.power.cut.off.event will be removed in a week - 31-jan-2020.

namo

namo
Coban protocol updated: old parameters removed after renaming.

namo

New devices added for Coban protocol:
Coban GPS303-F
Coban GPS303-G
Coban GPS303-H
Coban GPS303-I

namo

Coban protocol updated: Block Engine, Time Zone and Tracking settings (Actions tab) added for the following devices:

Coban GPS303-F
Coban GPS303-G
Coban GPS303-H
Coban GPS303-I

namo

Arm/Disarm setting is added for the following Coban devices (Actions tab):
GPS102, GPS103-B, GPS303-C, GPS303-F, GPS303-G, GPS303-H, GPS303-I, GPS306

namo

New device type added: Coban GPS104

namo

Coban protocol update is planned for tomorrow 2020-09-01, 12:00 UTC - parsing will be switched to new parsing engine. This is an internal process, no changes in devices' work are expected.

namo

namo
Coban protocol updated

namo

Settings added for Coban GPS311 device:

Block Engine
Time Zone
Arm/Disarm
Tracking

namo

New Coban devices added: GPS403-A and GPS403-B

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

Coban protocol is updated: fixed processing of heartbeat packets in bulk data uploaded from black box.

YuryAheichyk

Coban protocol has been updated, added battery.level parameter, parsed from the 20th field

YuryAheichyk

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

YuryAheichyk changes have been applied, the can.dtc parameter type changed to array

YuryAheichyk

The OBDII DTC codes registration is planned to be changed. Currently, error codes are stored in the can.dtc parameter as an array of strings. To unify with other diagnostic protocol types, errors will be stored as an array of objects.

The changes will be applied in 2 weeks, on May 8, 2025.

For reference, two additional parameters have been added:

can.dtc.strings - contains errors in the current format (will be removed in 1 month, on May 24, 2025)
can.dtc.objects - contains errors in the new format (will be removed in 2 weeks, on May 8, 2025)