Sierrawireless protocol is updated: added parsing of J1939 DTC codes for event 47.
The following flespi.parameters are registered for each DTC code:

  • Protect Lamp Status - can.j1939.dm1.dtc.pl
  • Amber Warning Lamp - can.j1939.dm1.dtc.awl
  • Red Stop Lamp Status - can.j1939.dm1.dtc.rsl
  • Malfunction Indicator - can.j1939.dm1.dtc.mil
  • Flash Protect Lamp - can.j1939.dm1.dtc.pl.flash
  • Flash Amber Warning Lamp - can.j1939.dm1.dtc.awl.flash
  • Flash Red Stop Lamp - can.j1939.dm1.dtc.rsl.flash
  • Flash Malfunction Indicator Lamp - can.j1939.dm1.dtc.mil.flash
  • Suspect Parameter Number (SPM) - can.j1939.dm1.dtc.spn
  • Failure Mode Identifier (FMI) - can.j1939.dm1.dtc.fmi
  • SPN Conversion Method - can.j1939.dm1.dtc.cm
  • Occurrence Count (OC) - can.j1939.dm1.dtc.oc

All parameters are indexed, starting with 1 for the first DTC code, and incrementing by 1 for the subsequent DTC codes, if present.

14 days later

Sierrawireless protocol is updated.
Configuration of telematic reports is now stored in the Report Columns setting of the device (Configuration tab):

Parsing of telematic reports is made according to the Report Columns setting of the device.
If you have changed the report composition in any means other than through the flespi setting (e.g. via SMS or through Serial Port), you need to synchronize the setting with flespi device. To do this click the "Request setting from device" (red round arrow) button for Report Columns setting.

⚠️ Please note that column 28 (Serial Number) must be at the first place in Report Columns configuration. This is necessary for the server to identify the connected device.

⚠️ If Report Columns setting is not set (for example you didn't create a device in flespi), then server will query the columns configured for the device with the DIAG PARAMS=24 command upon each connection.

13 days later

  • namo

  • Post #15
  • Edited

Sierrawireless protocol updated: added system parameter timestamp.key.
The parameter is used to distinguish between two messages with the same timestamp of seconds granularity. Integer part of its value is a message timestamp, and the fractional part is two less significant bytes of UniqueID(7) (flespi parameter event.seqnum) of the message.

7 months later

Sierrawireless protocol updated: bug fix.
Fixed registration of can.powersource.takeoff.enum parameter. Previously handled incorrectly.

    7 months later

    SierraWireless protocol has been updated, added Report Column PID(87) (flespi name report.reason)

      4 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

        14 days later
        18 days 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

              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"}]

                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"}]

                    21 days later
                    Write a Reply...