Automotive dictionary

Explains vocabulary and abbreviations used in Automotive

Alphabetic selection:

Definitions:

Data block

The ODX element data block describes a logical software component.

Data extraction

Data extraction is a conversion of the data (e.g. of a CAN data field) to symbolic data for a diagnostic application. For that reason, basic data types, encoding, byte order, masks, and computational methods are used opposed to packing.

Data field

The data field is part of a message and contains the payload of the message. For CAN, the data field is 8 bytes long and is called data field of the CAN data frame.

Data file

A data file is an ODX reference to an external file that contains data for a download to an ECU.

Data identifier

The data identifiers identify a diagnostic datum or a diagnostic data record. In the UDS standard, they are 2 bytes long.

Data Object Property (DATA-OBJECT-PROP)

The ODX element data object property describes a data type of an element of the type parameter.

Data packing

Data packing is packing of tester data (e.g. in CAN data fields) for transmitting as a diagnostic request to an ECU. For that reason, base-data-types, encoding, byte order, masks, and computational methods are used. This operation is the contrast to extraction.

Data parameter

All service parameters, except the service identifier, are called data parameters.

Database location

Conversion of a diagnostic layer of the ODX structure and its inheritance objects to a run­ time object. This runtime object can be accessed by a diagnostic application via D-server API.

DAVIE

DAVIE is the workshop tester by DAF Trucks, based on SIDIS by Siemens. The runtime system of the current DAVIE is EDIABAS.

Default value

A default value is a predefined value of an object that can have a value.

DefaultSession

The defaultSession is the session that is active in the ECU after power-up or a reset. See also diagnostic session.

Delimiter

The delimiter indicates the end of a field or a string of signs.

Diag-Layer-Container - Diag-Layer-Structure

This is a category of ODX 2.0.1 and ODX 2.x.

Diagnostic data

Diagnostic data are values in the memory of the ECU. The tester can read and/or modify the data. Typical examples include physical values such as the vehicle speed. Diagnostic data can be current values (e.g. vehicle speed), stored values (e.g. data that is stored in the moment of an error occurrence), and static values (e.g. the vehicle identification number).

Diagnostic message

A diagnostic message is a diagnostic service (request or response) that contains a diagnostic service identifier (SID).

Diagnostic process

A diagnostic process is the logical sequence of several processes, typically of diagnostic services. Examples are security access and response-on-event processes. The processes can be encapsulated in jobs.

Diagnostic routine

The diagnostic routine is a part of the ECU application software. It supports diagnostic communication and is enabled by the tester.

Diagnostic service

A diagnostic service consists of a diagnostic service request that is sent by the tester to an ECU or a group of ECUs and the diagnostic service response that are sent by the ECUs to the tester.

Diagnostic session

A session is a specific state of the ECU. A typical example of a diagnostic session is the default session. The session definition includes the diagnostic services supported by the ECU. The tester can request session transitions.

Diagnostic session type

The diagnostic session type is the data parameter of the service $10 (diagnosticSessionControl).

DIAG-SERVICE

The DIAG-SERVICE is an ODX element that describes a diagnostic service.

Download

Download is a procedure to transfer data from external (test) equipment to an ECU.

DTC fault symptom

The 4-bit DTC fault symptom indicates the fault symptom of a diagnostic trouble code (DTC). See also DTC structure in KWP 2000.

DTC groups

Abbr.-Bit 15/14-DTC group name: P-00-Powertrain; C-01-Chaissis; B-10-Body; U-11-Network communication; A-11-All groups.

DTC status byte

The DTC status byte consists of four elements (see also DTC structure in KWP 2000): DTC warning lamp calibration status (1 bit) DTC storage state (2 bits) DTC readiness flag (1 bit) DTC fault symptom (4 bits)

DTC storage state

The 2-bit DTC storage state indicates the memory status for the DTC. See also DTC structure in KWP 2000.

DTC structure in KWP 2000

The DTC structure consists of three bytes. The two upper bytes determine the error code group and the error code. The third byte consists of four parts (see also DTC status byte).

DTC warning lamp calibration status

The 1-bit DTC warning lamp calibration status indicates if the MIL is switched on (1) or off (0). See also DTC structure in KWP 2000.

DTS

DTS is short for Diagnostic Tool Set by Softing. DTS is a collective term for software modules that are used for on-board and diagnostic communication. Examples include run­ time systems (COS), authoring systems (Venice), and applications (Monaco, DTS-OBD, DTS-Flash).

Source Christoph Marscholik and Peter Subke (2008) - Road vehicles, Diagnostic communication - automotive.softing.com