Without run-time system diagnostics can not communicate with the ODF with a control device. The diagnostic runtime system handles communication between the application and the diagnostic bus. TheDiagCom Library provides an interface for a standardized diagnostic runtime system (MVCI server) to ISO 22900 are available.

• Configuration
• Manual Configuration
• Conversion of the ODX files
• PDU simulation

The ODF is working with a MVCI server Company DSA, Aachen. The documentation for MVCI server, see [Progdir] \ DSA \ MCD Kernel \ doc \.

Configuration

The configuration of the server is within the MVCI properties of an OTX document:

1. Select Solution Explorer the corresponding OTXDocument and click with the Right to the document.
2. It appears Context Menu. Click on "Properties".
3. This opens a properties window. Choose "Diagnoselaufzeitsystem"The"DsaMVCIServer"Out.
4. Click on the line "Settings"On the Button"...".
5. This opens a configuration dialog. Select on the project before converted ODX project from.
6. Look for 'Vehicle"One of the one contained in the parameterization Cars.
7. Turn in "Simulation"If necessary, the PDU simulation.

   The diagnostic runtime system is able to simulate a communication control device without a connected VCI, see PDU simulation. The values ​​for the simulation it can be a real communication with recorded or edited manually. The following settings are possible:

   • Off

     The simulation is turned off. Communication with the controller takes place via the VCI set above.

   • Record

     All requests and responses of the current control device communications are recorded and stored in the file set simulation. Communication with the controller takes place via the VCI set above.

   • On

     The simulation is turned on. There is no control device communication.

8. Select an appropriate "Simulation file " from.

Configuring the run-time system diagnostics (MVCI server)

Manual Configuration

The configuration can also be performed manually. The configuration takes place over several ini files in the file [Progdir] \ DSA \ MCD Kernel \ doc \ PRODIS.MCD_BHB.pdf described in detail.

Conversion of the ODX files

The DSA server does not work directly on the ODX data. These must be converted before use in an internal format. The exact procedure is described in the file [Progdir] \ DSA \ MCD Kernel \ doc \ PRODIS.MCD_BHB.pdf ODX-section converter described.

PDU simulation

The PDU is a simulation simulative D-PDU API, which can be operated below the MVCI server.

PDU with the simulation, the user can record a communication control device, edit and simulate manually. For the record, all requests and responses at the PDU level, ie stored at the level of the Application Layer (hex blocks) in an INI file. This file can be edited manually, see the file structure of the simulation. The following applications are thus possible:

• Development of diagnostic applications without the VCI and control unit
• Development of diagnostic application in parallel with the ECU development
• Simulation of messages that were not implemented in the controller
• Generation of fault conditions
• Recording of communications problems and forwarding the file for troubleshooting
• Off-line analysis of an earlier example in a data logger recorded diagnostic communication

The PDU simulation is very realistic, since it is below the DSA server on MVCI D-PDU API level starting point and also reproduces quite well the time behavior. The MVCI server setting does not therefore have no real communication takes place.

The PDU simulation is controlled by editable text files. The text files can be generated automatically by the recording of a real communication. Within the project properties of an ODF-simulation project, the PDU can be configured.