Diagnostic Messages

Diagnostic Messages Qt App Example

An example of J1939 Diagnostic Messages received, handled and displayed in a Qt Quick2 application (QML) on the CCpilot Display Computers or on the Virtual Machine (UX-Designer v5.0).

The Qt example app runnig on the VMExample Application running in Virtual MAchine

This example project uses CrossControl's Data Engine and Fieldbus Access Management tools (Available as Qt Creator plugins in UX-Designer) for receiving and displaying J1939 DM1 messages in a QML application. Incoming messages are received as Data Engine BLOB data messages. The first two bytes of the ByteArray holds the CAN message source address. The rest of the message contains the Diagnostic Trouble Codes DTC.

The following information is contained within a DTC:

  1. Suspect Parameter Number (SPN)
  2. Failure Mode Indicator (FMI)
  3. Occurrence Count (OCC)
  4. Conversion Method (CM)

And an active DM contains the following parameters:

Parameter                                                      Description
Protect Lamp Status                                    Lamp to indicate a problem with a vehicle system that is most likely not electronic subsystem related. e.g. Coolant Temperature has exceeded it defined range.
Amber Warning Lamp Status                     Lamp to indicate a problem with the vehicle system but the vehicle does not need to be stopped immediately.
Red Stop Lamp Status                                Lamp to indicate a problem that is severe enough to warrant stopping the vehicle.
Malfunction Indicator Lamp Status      Lamp to indicate when there is an emission related trouble code active.
DTC[0], DTC[1], DTC[2] ...DTC[n]      The DTC list contains 1 or more DTC’s. Each entry in the list contains an SPN, FMI, ccurrence Count, and Conversion Method.

For more details and on how to proceed with the deployment of the application both in the VM and on a CCpilot display, please click on the documentation in pdf-format below.

Attachments:

Application note article for detailed information: J1939_DM_application_note.pdf
Download the project in a zip-file from here: example_j1939_DM.zip

    • Related Articles

    • Window Manager Example

      A guide on how to deploy multiples Qt applications in Window Manager module on CCpilot target displays with different configurations and layouts. CrossControl’s Window Manager allows developers to realize integration of multiple applications with ...

    • Data Engine access from CODESYS

      This article contains two project parts – a CODESYS NoVisu project and a Qt GUI application. The two projects use the Data Engine (DE) to send signal values between the two applications. The DE signals in the Qt application have been created with the ...

    • Access CCpilot VI2 Hardware Buttons and Buzzer from CODESYS

      This CODESYS application example shows how the state of the hardware buttons and the buzzer on the CCpilot VI2 display can be read and used in the application. There are four squares for ech of the buttons and when a button is pressed, the square ...

    • Where can I find Operation System update packages for CCpilot Displays

      Crosscontrol has all the downloadable packages available for each of the CCpilot Display Computers. Head to our list of different CCpilot devices: Display computer | CrossControl From here, choose and click on the CCpilot Display that the OS update ...

    • Installing the LinX-Base runtime on a CCpilot iMX8 display

      When you order a product with LinX-Base (UX-Designer, Fieldbus Access and Data Engine) the required runtime will be pre-installed. If you still need to download this runtime package manually, follow the steps below. This article is valid for all the ...