OtfDiagnosicRuntimeSystem

Configuration diagnostic runtime system

Diagnosis without runtime system the OTF can not communicate with a control unit. The diagnostic system controls the duration of communication between the diagnostic application and the bus system. The DiagCom library provides an interface for a standardized diagnostic runtime system (MVCI server) according to ISO 22900 are available.

The OTF works with a MVCI server the company DSA, Aachen. The documentation for MVCI server, see [PROGDIR] \ DSA \ MCD kernel \ doc \.

Configuration

The configuration of the MVCI server occurs within the properties of a OTX document:

1. From the Solution Explorer, the corresponding OTX document and click with the right mouse button on the document.
2. It appears the context menu. Click "Properties".
3. This opens a properties window. Under "diagnostic runtime system" the "DsaMVCIServer" from.
4. Click in the line "settings" on the Button "...".
5. This opens a configuration dialog. Select on the project previously converted ODX project from.
6. Under "a vehicle" one of Cars included in the parameterization.
7. Turn in "simulation" on demand a PDU simulation.
   The diagnostic runtime system is to simulate a ECU communication without a connected VCI able to see PDU simulation. The values ​​for the simulation can thereby be recorded in a real communication or edited manually. The following settings are possible:
   • Off
   The simulation is turned off. Communication with the controller takes place via the above set VCI.
   • Record
   All requests and responses of the current ECU communication is recorded and stored in the set simulation file. Communication with the controller takes place via the above set VCI.
   • On
   The simulation is on. There is no ECU communication.
8. Select an appropriate "simulation file" from.

Configuration of the diagnostic runtime system (MVCI server)

Manual Configuration

The configuration can also be carried out manually. The configuration is done via multiple INI files and 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. This must be converted into an internal format before use. The exact procedure is described in the file [PROGDIR] \ DSA \ MCD kernel \ doc \ PRODIS.MCD_BHB.pdf described section ODX converter.

PDU simulation

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

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

• Development of diagnostic applications without VCI and control unit.
• Development of diagnostic application parallel to the ECU development.
• Simulation of messages that have not yet been implemented in the control unit.
• Generation of error states.
• Recording of communication problems and forwarding the file for troubleshooting.
• Offline analysis of a previously recorded, for example, in a data logger diagnostic communication.

The PDU simulation is very realistic, since it focuses below the DSA MVCI server to D-PDU API level and also the time behavior quite good maps. The MVCI server therefore not be taken that 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 the project OTF PDU simulation can be configured.