Difference between revisions of "OtfDiagnosicRuntimeSystem"

From emotive
Jump to navigation Jump to search
Line 1: Line 1:
 
{{DISPLAYTITLE:Open Test Framework - Diagnostic Runtime System}}[[Category:OTF]]
 
{{DISPLAYTITLE:Open Test Framework - Diagnostic Runtime System}}[[Category:OTF]]
 +
 +
'''UNDER DEVELOPMENT'''
 +
 
==Configuration diagnostic runtime system==
 
==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 [[Extensions.DiagCom|DiagCom]] library provides an interface for a standardized diagnostic runtime system (MVCI server) according to ISO 22900 are available.
+
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 [[Extensions.DiagCom|DiagCom]] library provides an interface for a standardized diagnostic runtime system (MVCI server) according to ISO 22900.
 
 
The OTF works with a MVCI server the [http://www.dsa.de/ company DSA, Aachen]. The documentation for MVCI server, see {{FontStyle1|blue|[PROGDIR] \ DSA \ MCD kernel \ doc \}}.
 
  
==Configuration==
+
The OTF works with a MVCI-Server the [http://www.dsa.de/ company DSA, Aachen]. The documentation for MVCI server, see {{FontStyle1|blue|[PROGDIR] \ DSA \ MCD kernel \ doc \}}.
  
 +
==Configuration Program==
 +
...
 +
<!--
 
The configuration of the MVCI server occurs within the properties of a OTX document:
 
The configuration of the MVCI server occurs within the properties of a OTX document:
  
Line 32: Line 36:
  
 
{{ImageStyleCenter|OTFOption DiagRuntimeSys.png||Configuration of the diagnostic runtime system (MVCI server)}}
 
{{ImageStyleCenter|OTFOption DiagRuntimeSys.png||Configuration of the diagnostic runtime system (MVCI server)}}
 +
-->
  
 
==Manual Configuration==
 
==Manual Configuration==

Revision as of 09:48, 14 September 2018


UNDER DEVELOPMENT

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 a MVCI-Server the company DSA, Aachen. The documentation for MVCI server, see [PROGDIR] \ DSA \ MCD kernel \ doc \.

Configuration Program

...

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.