Tuning Wiki

This is a historical revision. Read the current page or return to its history.

Page organisation in this revision
Page type
Technical article
Subject
Protocols
Parent
Section level
Applies to
No ECU-specific applicability
Tool groups
None
Manufacturers
None

Changes from revision 2 to revision 2

Removed text is struck through; added text is highlighted.

ISO 22900-3 specifies the diagnostic server API. A server can use diagnostic descriptions to map application-level requests to the required vehicle messages and interpret results.

Diagnostic D-Server. Original Tuning Wiki diagram.

Executing a diagnostic service. Original Tuning Wiki diagram.

Using the interface

ODX describes diagnostic data such as variants and services. The D-Server executes diagnostic communication using that data. The interface layer below it handles access to the VCI.

See D-PDU API and the vehicle diagnostics protocol guide.

Sources: ACTIA IME overview.

Rendered revisions

Open each version to inspect formatting, tables and photographs.

Revision 2: Diagnostic D-Server

ISO 22900-3 specifies the diagnostic server API. A server can use diagnostic descriptions to map application-level requests to the required vehicle messages and interpret results.

Client application, D-Server and diagnostic data, Vehicle communication interface
Diagnostic D-Server. Original Tuning Wiki diagram.
Client selects service, D-Server resolves ODX definition, Request is encoded. VCI sends request, ECU returns response, D-Server decodes result
Executing a diagnostic service. Original Tuning Wiki diagram.

Using the interface

ODX describes diagnostic data such as variants and services. The D-Server executes diagnostic communication using that data. The interface layer below it handles access to the VCI.

See D-PDU API and the vehicle diagnostics protocol guide.

Sources: ACTIA IME overview.

Revision 2: Diagnostic D-Server

ISO 22900-3 specifies the diagnostic server API. A server can use diagnostic descriptions to map application-level requests to the required vehicle messages and interpret results.

Client application, D-Server and diagnostic data, Vehicle communication interface
Diagnostic D-Server. Original Tuning Wiki diagram.
Client selects service, D-Server resolves ODX definition, Request is encoded. VCI sends request, ECU returns response, D-Server decodes result
Executing a diagnostic service. Original Tuning Wiki diagram.

Using the interface

ODX describes diagnostic data such as variants and services. The D-Server executes diagnostic communication using that data. The interface layer below it handles access to the VCI.

See D-PDU API and the vehicle diagnostics protocol guide.

Sources: ACTIA IME overview.