This information is also included in the 'Documentation' folder of the installation directory for Raptor-Dev.
Steps to build A2L files for Vector CANape
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
From the top level of the model, double click on the ‘XCP Protocol Definition’, and check ‘Generate A2L for CANape’.
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
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.)
Initial Setup with Vector CANape 16.0
Open CANape, then select “<Create new project>”
vCANape1
Name the project
Choose the destination for the project
Once a project is created right Click on "Devices"
Click on New Device from > 'Click Database'
Select the a2l file with “projectName_A4” type from C:\ECU\a2l
Check the "Activate dataset management" true > click "Next"
Select the corresponding CAN channel from the drop down menu under "Channel:"
Click "Next", no changes needed yet for the Map File Settings, click "Next" again
Click on browse, and select the .hex file found C:\ECU\project_name
Note: This file was created during the Raptor build
Once selected, click OK. A window for settings will pop up automatically. Select “protocol” from the menu on the left and click “Test connection”. This will verify that the project is connected to the ECU in order to run necessary tests.
Note: If there is an error, please check if Baud rate is correct.
Press “OK” once communication is established. Now from the explorer on the left, click on the “device name” > Datasets\.. > “project name” > “parameter of interest”. Drag and drop the parameter onto the right.
Click on the start icon highlighted in the step above. It will take CANape online with the connected ECU. The selected parameters will be updated in real-time.
Merging Offline Calibration Changes
If you have made offline calibration changes, or received a calibration set from a colleague you may want to merge those changes into the executable to create a new programming file for the ECU. This can be accomplished by using Vector CANape and the Raptor-CAL Tool.
Once you have made offline changes or opened your calibration file, explore in the 'Device_Name > Datasets' directory.
Right click on the dataset of interest then click “Export reference set…”
Choose destination and click “Save”. This will create a hex file with the application and calibration settings (including any changes you made). In order to program this into the ECU, you need to create a RPG file for us with Raptor-Cal.
"Raptor-Cal Tool".
Click on "Program" -> "Create Raptor Package"
Click on "Program File (.Hex)" and navigate to your new .hex file with offline calibration
Click on “Signals File (.a2l)” and navigate to the corresponding .a2l file under C:\ECU\a2l.
Click "Start"
Save the .rpg file that was created and close the Raptor Package program.
From the "Raptor-Cal Tool", click "Flash".
Once the module (ECU) has been detected, click "Select"
Navigate to C:\ECU\RPG and open the .rpg file saved from using the Raptor Package program.
Once the file is opened, it will automatically flash the ECU with offline calibrated changes
Steps to verify the offline calibration changes
Go to the "Vector CANape" program and click the "Flash" button.
Click "Go Online"
Choose "Upload data segments and create a new dataset". This will allow for the new calibrations flashed on the ECU to by synchronized with the dataset on the hard drive.
