Diagnostics without an A2L File
Communication with the connected ECUs is established during hardware -initialization. The communication parameters necessary for this can be defined in A2L or ODX files and must correspond to the ECUs.
A different set of parameters is also required for each protocol (KWP2000, UDS, CCP, XCP, etc.). A2L files normally contain parameters for a specific protocol and a specific bus system and cannot be used for other protocols and buses.
In earlier versions of ODX-LINK, KWP2000 and UDS devices could only be used if they were assigned an A2L file with the corresponding communication parameters. If there was no such file, a dummy file had to be created containing these KWP2000 or UDS parameters.
ODX-LINK can also be used without an ECU project (in the form of an A2L file). The communication parameters for UDS or KWP2000 devices are then determined from the assigned logical link of the ODX project.
Note |
|---|
The ODX communication parameters must comply with the ISO 22900-1 specification for ODX V2.0.1 or V2.2 (as far as parameter names, values, units, etc. are concerned)! |
An ECU project can still be assigned to UDS or KWP2000 devices – in this case, the A2L file is the "master" and ODX parameters are ignored.
If you use a UDS or KWP2000 device in the hardware configuration, you can simply skip assigning an A2L file – after assigning an ODX project and logical link for the device, the communication parameters are read out of ODX and used during hardware initialization.
Note |
|---|
If hardware initialization via ODX communication parameters does not work, you have either assigned the wrong logical link or the ODX data does not correspond to the ECU. |