Procedure
This section takes a brief look at the procedure in INCA – for more details, refer to the tutorial:
in the ODX-LINK User Guide in ? > Manuals and Tutorials.
- Create a main directory and workspace.
Add an ECU project if necessary.
This step can be skipped (see Diagnostics without an A2L File).
Read in the ODX project.
For ODX projects, you can use the following file formats: *.pdx, *.odx-*, *.xprj, *.prj.
With ODX V2.2, a consistency check is executed after the import of the project. The consistency check report of the last imported ODX V2.2 project can be found in \ETAS\LogFiles\ODX.
For a ODX V2.0.1 project, no consistency check is performed. Therefore, an imported ODX project of the INCA database can have three different consistency states. When you click on the project, the state is displayed:
- consistent: ODX projects without consistency errors
- not consistent: ODX projects with consistency errors
- consistency state unknown: for ODX V2.0.1 projects that have not been checked
WARNING |
|---|
Risk of unexpected vehicle behavior ODX consistency errors in the ODX files can result in INCA runtime errors. This can lead to unexpected vehicle behavior, such as engine shutdown as well as breaking, accelerating, or swerving of the vehicle. Do not use the respective ODX files if relevant diagnostic functions are affected by inconsistencies. |
Add a hardware configuration (see Automatic Search for and Configuration of OBDonCAN Devices and OBDonUDS Devices).
In the Hardware Configuration Editor: Device>Add.
ODX configuration
In the Hardware Configuration Editor: Hardware>Configure ODX. Select the ODX project.
Logical link mapping (assignment of a logical link of the ODX project to the INCA device).
- Add experiment and assign workspace.