2 months later

  • namo

  • Post #3
  • Edited

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)
5 days later
a month later

  • namo

  • Post #5

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.

    8 days later

    • namo

    • Post #6
    • Edited

    namo
    Coban protocol updated: old parameters removed after renaming.

        10 days later
        19 days later
        10 days later
        4 months later
        2 months later

        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

          • Post #12

          namo
          Coban protocol updated

              3 months later

              • namo

              • Post #13

              Settings added for Coban GPS311 device:

              • Block Engine
              • Time Zone
              • Arm/Disarm
              • Tracking
                14 days later
                a year later

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

                  2 months later

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

                    2 years later

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

                      2 months later

                      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

                        17 days later
                        a year later

                        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)

                        can.dtc.strings example:
                        ["P0020","U0001"]
                        can.dtc.objects example:
                        [{"standard":"OBDII","code":"P0020"},{"standard":"OBDII","code":"U001"}]

                          Write a Reply...