• baja

  • Post #1
  • Edited

Plugin gets parameters with automobile industry DTC - Diagnostic Trouble Codes, and enriches message with human-readable description of the code (which is standardized among the industry).
Check the step-by-step guide on how to use it:
https://flespi.com/kb/msg-dtc-decoder-plugin

    5 days later
    shal changed the title to [Changelog] msg-dtc-decoder plugin.
      3 months later

      The process of processing parameters by the plugin is changed.
      In accordance with the changes related to the registration of DTC parameters throughout the platform, the operation of the plugin has also been changed. Now the plugin accepts only an array of DTC codes as input, for example:

      can.dtc: ["P0068", "P0507"]

      Parameters with a description of the codes will be registered at the output, for example:

      can.dtc.P0068.description: "MAP/MAF - Throttle Position Correlation"
can.dtc.P0507.description: "Idle Air Control System RPM Higher Than Expected"

      If the description is not found, the parameter value will be Unknown, for example:

      can.dtc.P0507.description: "Unknown"
        5 months later

        The DTC (OBD II) codes database has been updated:

        • Added new 458.
        • Edited existing 20.

        Added support for DTC codes according to the J1939 standard.
        Short summary.
        • SPN (Suspect Parameter Number) 1675: Identifier of the parameter that caused the error, "Engine Starter Mode".
        • FMI (Failure Mode Identifier) ​​7: Code describing the type of failure. FMI 7 means “Not Responding Properly”.
        • OC (Occurrence Count): Counter indicating the number of times this error has been registered.
        • CM: This parameter can mean different things depending on the context, for example, it can indicate the presence or absence of confirmatory data about the failure. In some cases, cm can mean “Conversion Method” and can indicate the type of interpretation of the sensor data, but for the exact interpretation, it is also necessary to look at the specifications of the specific vehicle.

        DTC format: a json array of objects with error parameters:
        [
        {"cm":0,"fmi":7,"oc":1,"spn":1675,"standard":"J1939"},
        {"cm":1,"fmi":12,"oc":1,"spn":65612,"standard":"J1939"}
        ]
        DTC are registered in the view parameters:

        can.dtc.1675.7.description : "Engine Starter Mode (Not Responding Properly), occur: 1"
can.dtc.65612.12.description : "Unknown" // If the parameter description was not found
        5 months later

        Added support for DTC codes according to the J1708/J1587 standard
        MID (Message Identifier) - the address of the module from which the error was received
        SID (Subsystem Identifier) - the parameter that caused the error
        FMI (Failure Mode Identifier) - code describing the type of failure

        The description parameter has been moved to the can.dtc array object.

        Added parameter SA (Source Address) for J1939 dtc codes

        Write a Reply...