2 months later

The protocol will be affected by deleting the parameters can.j1939.dm1.dtc.oc, can.j1939.dm1.dtc.cm, can.j1939.dm1.dtc.fmi, can .j1939.dm1.dtc.spn to be installed in 1 week - April 12, 2024: these values have been moved to the can.dtc array parameter

    7 days later

    YuryAheichyk Changes installed, params can.j1939.dm1.dtc.oc, can.j1939.dm1.dtc.cm, can.j1939.dm1.dtc.fmi, can .j1939.dm1.dtc.spn deleted

        2 months later
        6 months later

        The existing communication/telemetry protocol (“BCE simple communication protocol”) that impacts FM-500 & FMS500 series devices has a custom TIME format that is meant to overflow 28bits on Sat Jan 04 2025 18:48:30 GMT+0000.

        We have made changes to prevent registration with incorrect timestamps after counter overflow

        2 months later

        Change in sending custom command.

        According to the protocol, the devices do not have the ability to send text commands that are intended for SMS in binary form via TCP.

        • Now text commands can only be sent via SMS. The 'bestpassword' prefix will be automatically substituted by the server according to the protocol.
        • When trying to send a text command via the connection, an error message will be displayed saying "The protocol does not support sending SMS commands in binary form".
          7 days later

          bce protocol has an error parsing the parameter tacho.vehicle.mileage that store the mileage in meters. In a week, on 21-Jan-2025, the error will be fixed, the parameter will store the mileage in km.

          8 days later

          YuryAheichyk changes applied, the unit of measurement for the tacho.vehicle.mileage parameter is now km.

            9 days later

            These parameters will be removed in 2 weeks 14-Feb-2025:

            • can.j1587.dtc.mid
            • can.j1587.dtc.sid
            • can.j1587.dtc.fmi
            • can.j1979.s3.dtc
            • can.j1979.s7.dtc
            • can.j1979.s10.dtc
              Use can.dtc parameter instead
              24 days later

              YuryAheichyk changes applied, parameters removed:

              • can.j1587.dtc.mid
              • can.j1587.dtc.sid
              • can.j1587.dtc.fmi
              • can.j1979.s3.dtc
              • can.j1979.s7.dtc
              • can.j1979.s10.dtc
                  2 months 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"}]

                    14 days later

                    YuryAheichyk changes applied, can.dtc array contain objects now.

                    For reference, two additional parameters added:

                    • can.dtc.strings - contains errors in the old format (will be removed on May 24, 2025)
                    • can.dtc.objects - contains errors in the new format (will be removed on May 24, 2025)

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

                        Write a Reply...