Raptor-Dev-A2L-File-Generation

From NewEagleWiki
Jump to navigation Jump to search


Steps to build A2L files for Vector CANape and INCA

From the top level of the model, double click on the ‘ECU Definition’ block, and check ‘Output HEX/A2L Files (Third-Party Tool Support)’.
vCANape1
vCANape1
From the top level of the model, double click on the ‘XCP Protocol Definition’, and check ‘Generate A2L for CANape/INCA’.
vCANape2
vCANape2
Once these options are configured, a Vector CANape a2l file will be created automatically during the build process and placed at C:\ECU\a2l. The a2l file contains information about the built application such as details about measurements and adjustments. Using this file, you can connect to the programmed ECU to view live data and make calibration adjustments.
vCANape3
vCANape3
In the step above, you will notice that there are 3 extra files created labeled “…_CANAPE”. This is because the model that caused these files to be generated contained parameters with access level 1 and 4. The file for access level 1 ends with ‘_A1’ and contains only those parameters for access level 1. The file for access level 4 ends with ‘_A4’ and contains parameters defined with access level 4 or lower (e.g. all parameters.)

Using A2L Files for Calibration

Using A2L Files with Vector CANape

Please see the Vector CANape support page: Raptor-Dev-Vector-CANape-Support

Using A2L Files with INCA

Please see the INCA support page: Raptor-Dev-INCA-Support