Tuesday, February 24, 2026

ECU Diagnostic DSPACE Control desk--ODX/CDD file

 

ECU Diagnostics Demo

Opening demo projects

For instructions on opening demo projects, refer to Copying and opening a demo project.

Description of the demo project

The DiagDemo project lets you perform the following tasks even without a real ECU connected to your host PC:

Required products and modules

Working with this demo requires:

  • ControlDesk

Demo setup

The DiagDemo project contains the ECU Diagnostics (MCD-3D v2.0.2) experiment, which contains the following devices:

  • ECU Diagnostics (MCD-3D v2.0.2) device

    The device is preconfigured to access the CalDemo ECU via CAN using a virtual CAN channel. ControlDesk starts the CalDemo ECU automatically when you open the DiagDemo project. For instructions on starting the CalDemo ECU manually, for example, if you closed it unintentionally, refer to Starting the CalDemo ECU.

    ControlDesk automatically loads a demo ODX database to the device when you open the DiagDemo project. A variable description based on the ODX database is added to the device so you can perform measurement and calibration of diagnostic variables via the ECU Diagnostics device.

  • CAN Bus Monitoring device

    The device is preconfigured to monitor CAN communication between ControlDesk and the CalDemo ECU.

The illustration below shows the demo setup in ControlDesk's Project pane:

Demo layouts

The ECU Diagnostics (MCD-3D v2.0.2) experiment contains the following layouts:

Executing diagnostic jobs

You can execute jobs with the Diagnostics Instrument. For example, you can execute the UDS Demo Security Access Job diagnostic job to enable security access, which is required to perform parameter changes on the CalDemo ECU via the ECU Diagnostics device.

Tip

The job is executed for demonstration purposes only. Normally, you do not have to execute it manually. ControlDesk executes it automatically when you start online calibration since this is necessary for write operations and access to protected areas.

To get security access by executing a diagnostic job, perform the following steps:

  1. On the Home ribbon, click Status Control – Go Online to start online calibration. ControlDesk connects to the CalDemo ECU. You are now directly accessing the hardware.

  2. In the Diagnostics Instrument on the diagnostics layout, select UDS Demo Security Access Job and click Execute.

The job performs the following steps:

  1. It executes the DiagnosticSessionControl service and changes to the programmingSession.

  2. It executes the SecurityAccessRequestSeed service to request the seed value from the CalDemo ECU.

  3. It executes the SecurityAccessSendKey service to send the key to the CalDemo ECU.

Configuring and executing diagnostic services

You can configure and execute services with the Diagnostics Instrument. For example, you can execute the WriteDataByIdentifier service to configure the current gear value.

To configure the gear value by executing a service, perform the following steps:

  1. On the Home ribbon, click Status Control – Go Online to start online calibration. ControlDesk connects to the CalDemo ECU. You are now directly accessing the hardware.

  2. In the Diagnostics Instrument on the diagnostics layout, select the WriteDataByIdentifier service.

  3. Select DemoCarEngineData as the DataIdentifier.

  4. Specify 0x4 as the CurrentGear value.

  5. Click Execute to execute the WriteDataByIdentifier service.

    The Time Plotter on the diagnostic variables layout displays the gear change:

Measuring and calibrating variables via the ECU Diagnostics device

You can measure and calibrate diagnostics variables via the ECU Diagnostics device in connection with ControlDesk's standard instruments. Measurement and calibration via the ECU Diagnostics device uses diagnostic services available from the ODX database. When you calibrate a parameter value, for example, you implicitly configure and execute the service related to that parameter.

ControlDesk's Variables pane shows all the available diagnostics variables:

Perform the following steps:

  1. On the Home ribbon, click Status Control – Start Measuring to start measuring.

    The Time Plotter on the diagnostics variables layout displays various variables that originate from the ECU Diagnostics device.

  2. Use, for example, the Climate Control Multiswitch on the diagnostics variables layout to change the Desired Temperature parameter value.

    You can observe the effect of the changed parameter value in the Time Plotter.

Measuring diagnostic trouble codes (DTCs)

The demo provides DTC measurement variables generated from the device's ODX database. DTC measurement variables make diagnostic trouble codes visible in ControlDesk instruments other than the Fault Memory and the Diagnostics Instrument.

ControlDesk's Variables pane shows all the available DTC measurement variables in the <Diagnostic Trouble Codes> node:

To change the current DTC states (set and clear DTCs) for DTC measurements, perform the following steps:

  1. On the Home ribbon, click Status Control – Start Measuring to start measuring.

    The instruments on the diagnostic trouble codes layout display various DTC measurement variables.

  2. Clear the checkboxes next to 0x1CC, 0x145 and 0x78.

    This deactivates the occurrence of the selected DTCs, i.e., sets the DTC states to 0.

  3. Click  next to the three DTCs.

    This clears the DTCs:

    Note

    When you clear a DTC without having deactivated its occurrence, the DTC reoccurs immediately after you clear it.

Tip

The Fault Memory Instrument on the diagnostic trouble codes layout also displays when DTCs occurred. If you specify an Update Rate [s] value in the instrument, this information is updated cyclically.

Monitoring CAN communication

Via ControlDesk's Bus Navigator, you can monitor CAN communication using the CAN Bus Monitoring device. The CAN Monitor monitoring list displays the raw data of the monitored CAN communication:

The monitored CAN messages originate from communication between the ECU Diagnostics device and the CalDemo ECU:

  • CAN messages with the 0x001 ID are requests from the ECU Diagnostics device.

  • CAN messages with the 0x002 ID are responses from the CalDemo ECU

-

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

ECU Diagnostic DSPACE Control desk--ODX/CDD file

  ECU Diagnostics Demo Opening demo projects For instructions on opening demo  projects , refer to  Copying and opening a demo project . Des...