2 months later
  • Edited

BCE protocol updated according to BCE documentation:

  • parameter ain.2 is replaced by external.powersource.voltage
  • parameter ain.6 is replaced by battery.voltage

Both old and new parameters will be registered until 5 Dec 2019. After this date old parameters (ain.2 and ain.6) will be removed.

BCE protocol updated: fixed coefficient for parameter external.powersource.voltage

  • ysv likes this.
7 days later
  • Edited

Deprecated parameters removed from BCE protocol. See this post for details.

    2 months later
    14 days later

    ibutton.code parameter parsing fixed for BCE protocol - bytes order changed to reverse.

      12 days later
      • Edited

      engine.ignition.status parameter added as boolean representation of DIN №5

      a month later
      • Edited

      Digital inputs 2 bytes parsing added according to the protocol docs table:
      DIN №1: movement.status
      DIN №7: engine.generator.status
      DIN №8: power.on.status
      Next flags are registered only when appropriate DIN is true:
      DIN №9: gsm.jamming.event
      DIN №13: rollover.event
      DIN №14: vibration.alarm
      DIN №15: accident.event

      5 months later

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

        namo
        BCE protocol updated

          3 months later

          BCE protocol updated: raw bytes from RS232 interface that are sent in Data Type 9 structure are stored now into payload.hex parameter.

            19 days later

            wiegand.code parameter parsing for Wiegand26 RFID reader added.

            3 months later

            The following settings are added for Xirgo FMS500 Light+, Input/Output tab:

            • Output1, Output2, Output3
            • Signal1, Signal2
            • Fmset Force
            9 months later
            2 months later

            BCE protocol updated: parameters tyre.pressure and tyre.temperature are renamed to tire.pressure and tire.temperature. Old parameters tyre.pressure and tyre.temperature will be registered until 05-Jan-2022 together with the new ones. Old parameters will be removed 05-Jan-2022.

              2 months later

              Added new setting Output 1 (Input/Output tab) for Xirgo FMS500 STCAN device. The setting allows to activate/deactivate digital output 1 of the device.

              8 days later

              We've detected discrepancy in our parameter naming regarding LLS sensors. The refactoring results into the following:
              liquid.sensor.fuel.volume to lls.value
              liquid.sensor.fuel.temperature to lls.temperature
              Both versions of the parameters will be registered for 1 month until 5th April 2022. Then old naming will be removed

              a month later

              baja update installed

                • Edited

                BCE protocol updated: Data type 12: Diagnostic Trouble Codes is supported.
                Mapping to flespi parameters is below.

                Sub type 1: J1939 DM1 DTC

                • Source ECU address - can.j1939.dm1.dtc.sa
                • Suspect Parameter Number - can.j1939.dm1.dtc.spn
                • Failure Mode Identifier - can.j1939.dm1.dtc.fmi
                • SPN Conversion Method - can.j1939.dm1.dtc.cm
                • Occurrence Count - can.j1939.dm1.dtc.oc

                Sub type 2: J1939 DM1 Lamp Status DTC

                • Source ECU address - can.j1939.dm1.dtc.sa
                • Malfunction Indicator Lamp Status - can.j1939.dm1.dtc.mil
                • Red Stop Lamp Status - can.j1939.dm1.dtc.rsl
                • Amber Warning Lamp Status - #can.j1939.dm1.dtc.awl
                • Protect Lamp Status - can.j1939.dm1.dtc.pl
                • Flash Malfunction Indicator Lamp - can.j1939.dm1.dtc.mil.flash
                • Flash Red Stop Lamp - can.j1939.dm1.dtc.rsl.flash
                • Flash Amber Warning Lamp - can.j1939.dm1.dtc.awl.flash
                • Flash Protect Lamp - can.j1939.dm1.dtc.pl.flash

                Sub type 3: J1587 (PID 194) DTC

                • MID - message identifier - can.j1587.dtc.mid
                • SID - subsystem identifier - can.j1587.dtc.sid
                • FMI - failure mode identifier - can.j1587.dtc.fmi
                • Low character identifier for a standard diagnostic code - can.j1587.dtc.lci
                • Type of diagnostic code - can.j1587.dtc.type
                • Current status of fault - can.j1587.dtc.status
                • Occurrence Count - can.j1587.dtc.oc

                Sub type 4: J1979 (Service 03) DTC

                • Source ECU address - can.j1979.s3.dtc.sa
                • Diagnostic trouble code - can.j1979.s3.dtc

                Sub type 5: J1979 (Service 07) DTC

                • Source ECU address - can.j1979.s7.dtc.sa
                • Diagnostic trouble code - can.j1979.s7.dtc

                Sub type 6: J1979 (Service 0A) DTC

                • Source ECU address - can.j1979.s10.dtc.sa
                • Diagnostic trouble code - can.j1979.s10.dtc

                If the Data type 12 structure contains information about more than one DTC code, than the first group of parameters are registered without indexes, and the subsequent groups - with indexes starting from 1. For example:
                {
                "can.j1979.s7.dtc": "P1498",
                "can.j1979.s7.dtc.1": "P24A7",
                "can.j1979.s7.dtc.2": "P24A8",
                "can.j1979.s7.dtc.sa": 0,
                "can.j1979.s7.dtc.sa.1": 0,
                "can.j1979.s7.dtc.sa.2": 0,
                "ident": "860665057222111",
                "timestamp": 1648450450
                }

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