OtfDiagnosicRuntimeSystem

From emotive
Jump to navigation Jump to search


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.

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

MVCI Server Configuration Program

The MVCI Server Configuration program is attached in the OTF (or OTP installer, or DotNet OTX-Runtime API) installer. You can find and start the program (MVCIServerConfiguration.exe) in the installation folder. You can also open the program from the OTF through the "Diagnostic Runtime System" button in the bottom Status Bar, or the "Open" button in the "Runtime Environment" page in the OTF global options. In OTP, after loading a PPX using Diagnostic Runtime System, you can find the button displaying the current MVCI- or MCD- Server with the car icon in its Status Bar, clicking on this button shall open the MVCI Server Configuration Program.

When you start the Configuration Program and you has not ever configured a Diagnostic Runtime System for your computer, the "Search of Diagnostic Runtime System (MVCI-Server)" dialog occur to help you search for all installed Diagnostic Runtime System (MVCI-Server) in your system drives. You only need to select a system drive and click on the "Start" button, then wait for a moment before the search progress finishes. When the progress has finished, you can select one or more MVCI Servers and click on the "Apply" button to register them in the list of the MVCI Servers in the Configuration Program (this list is saved in the 'MVCI-Server.rdf' file), you can configure the added MVCI-Servers then. If you do not want the automatic search, you can close the search dialog and go to the Configuration Program to manually configure your MVCI Server (see details below). If you install a new MVCI-Server installer from emotive, the installed MVCI-Server shall be automatically registered, you only need to restart the OTF (if it is opened) and use the new MVCI-Server without searching and registering. Otherwise, if you installed your own MVCI-Server, you can open the "Search of Diagnostic Runtime System (MVCI-Server)" dialog to search for it by clicking on the "Search..." button at the main tab of the Configuration Program.

The Configuration Program consists of 2 tabs: the "Diagnostic Runtime System (MVCI-Server)" tab and the "Vehicle Communication Interface (D-PDU-API)" tab.

Diagnostic Runtime System (MVCI-Server) tab

This tab contains 2 panels.

Registered MVCI-Server list (left panel)

The left panel has the Command Bar and the list of the registered MVCI-Servers. You can select one MVCI-Server in the list at a time, the selected MVCI-Server can be managed with the buttons in the Command Bar. You can also right click on an MVCI-Server, select the context menu "Select" and click OK button to set the selected MVCI-Server as the current server used with the OTF (or the OTP, or the OTX-Runtime Api). Note that it is necessary to restart the OTF (or any related programs) in order to apply the selected MVCI-Server.

The Command Bar at the top of the left panel has the following buttons (according to their positions from left to right):

Button Description
Search... Opens the "Search of Diagnostic Runtime System (MVCI-Server)" dialog to search for all the installed MVCI-Server in a system drive.
Add (with dropdown list) Allows you to add a new MVCI-Server entry from a template in the dropdown list. You can then configure the new MVCI-Server entry e.g. set path to your MVCI-Server location.
Delete Deletes the selected MVCI-Server.
Up Moves the selected MVCI-Server up one line.
Down Moves the selected MVCI-Server down one line.

MVCI-Server details (right panel)

The right panel displays the information of the selected MVCI-Server from the left panel. Here users can configure the MVCI-Server by editing the information through the text boxes and other controls. Here we can not declared the details because they may vary according to the MVCI Server types.

Icons Note.png Almost the MVCI-Servers has the D-PDU-API property. This property is mapped with a dropdown list, here you can select the 'D-PDU-API' or the 'D-VCI-API'.
  • The 'D-PDU-API' means you will connect directly to an ECU microcontroller and send/receive data from it. Communication with the controller takes place via the above current VCI.
  • The 'D-VCI-API' means there is no ECU communication. 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.

Vehicle Communication Interface (D-PDU-API) tab

This tab is only visible if you have install at least a D-PDU-API. On the left panel of this tab, you can find one or more D-PDU-API entries, there is also one or many D-VCI-API entries (this kind of API supports the PDU simulation, see below). When you select an entry from the left panel, the detailed information of the selected API shall be displayed in the right panel. Here users can configure the API by editing the information through the text boxes and other controls. Here we can not declared the details because they may vary according to the API suppliers.


MvciConfigProgram Search.png
The "Search of Diagnostic Runtime System (MVCI-Server)" dialog helps to browse all the available MVCI-Servers in a system drive and register for using


MvciConfigProgram.png
The MVCI Server Configuration Program helps to configure the registered MVCI-Server to use with emotive products in design time and run time

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.

Besides converting the ODX data files directly with the converter, you can also indirectly convert them during design time in OTF through the PDX Converter section of the DiagCom project settings (it shall use the converter of the current diagnostic runtime system selected in the MVCI Server Configuration Program above).

PDU simulation

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

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. The PDU simulation can be configured in the Vehicle Communication Interface (D-PDU-API) tab of the MVCI Server Configuration Program above.


DoIP Configuration

DOCUMENT UNDER DEVELOPMENT...