Data Description for ECU Calibration
Three types of description files play a key role in ECU calibration. They describe:
- Internal ECU variables
- Different communication networks
- Diagnostic services and data as well as the flash process
To make it easier to display and edit description files, CANape contains various viewers and editors for all types of description files. Furthermore, dedicated high-performance authoring tools make it easier for you to create A2L, ARXML, DBC, FIBEX, LDF, CDD, ODX files and others.
Format | Support in CANape |
A2L | Editing with integrated ASAP2 Studio |
ARXML | Visualization with AUTOSAR Explorer |
DBC | Editing with CANdb++ Editor |
LDF | Visualization with LIN Explorer |
FIBEX | Visualization with FIBEX Explorer |
| CDD | Visualization with CDD Viewer |
| ODX-C, ODX-D | Visualization with ODXStudio View |
| ODX-F | Visualization with ODXStudio View |
Description Files for Internal ECU Parameters
Description files let the user access internal ECU parameters by symbolic names. A2L files are elementary components of every measurement and calibration operation, and it should be noted that the CCP and XCP protocols are address-oriented in their operation. The user selects objects by symbolic name, while CANape takes the associated addresses from the A2L and uses them in communication with the ECU.
Contents of the A2L database
An ASAP2 description file (also called A2L) contains all information on the relevant data objects in the ECU such as characteristics (parameters, characteristic curves and maps), real and virtual measurement variables and variant dependencies. Information is needed for each of these objects, such as memory address, storage structure, data type and conversion rules for converting them into physical units. In addition, an A2L also contains the parameters for communication between CANape and the ECU.
Supporting you in data description of internal ECU variables
CANape contains an editor (ASAP2 Studio) so that you can easily edit ECU description files in A2L format. The following tools, which are available separately, support you in working with ECU description files:
Easily create and edit ECU description files | |
Functional library for reading and writing ASAP2 files |
Generating A2L Files
Manual generation
You can generate A2L files from CANape at any time with the information from the Linker Map file. To define communication-specific data in the A2L, you just need to create a suitable new driver in CANape (XCP-on-FlexRay, CCP-on-CAN, etc.) and save the settings. The measurement and calibration parameters from the ECU can be selected from the Linker Map file using object names. You can use the editor to conveniently input and manage all other settings, such as entry of minimum and maximum values, groupings, definition of conversion rules and storage schemes.
Automatic generation by C Code Parser
Special comments in C code are parsed with the A2L Creator, which is supplied as a component of the ASAP2 Tool-Set. Software developers do not need to define the objects a second time in a parallel database, rather they define them in the form of comments in the C code. This minimizes the risk of inconsistencies between the code and a separate database.
The software developer makes a change to the code directly at the relevant point. That is also precisely where the comments are located; so the developer can make all changes at one point, without having to update the changes in another tool.
The parser searches the C code for the comments and generates a partial A2L from them, which represents the measurement and calibration parameters. The communication section of the A2L, or other partial A2L files containing the complex conversion rules, can be merged into a complete A2L in another step and be updated with current address information from the Linker Map file.
Updating Addresses and Merging A2L Files
The ASAP2 Editor in CANape reads address and data type information from the linker-map file and updates the A2L file. The ASAP2 Editor also lets you subdivide an existing A2L file into partial subfiles or merge them together again.
In setting up an automated build process, the ASAP2 Tool-Set supports you with the programs ASAP2 Creator, ASAP2 Updater, ASAP2 Merger, ASAP2 Comparer, ASAP2 Checker and ASAP2 Modifier.
Supported compiler and map file formats by CANape:
-
Standard (CANape-specific format)
-
Archimedes HC11
- Borland C++ (16 Bit) and Borland C++ (32 Bit)
- COFF, COFF/DWARF
- Cosmic
- DIABDATA
- ELF/DWARF/NEC
- Fujitsu Softune MP1/MAP and Fujitsu Softune MPS
- Greenhill Multi 2000
- GNU, GNU C16x, GNU VxWorks and GNU 68k
- Hitachi HEW SH7055
- HiTech 68HC05 and H8S
- Hiware HC12
- IAR
- ICCAVR
- IEEE (Tasking, Cosmic, Microtec)
- ISI MatrixX
- Keil 16x, Keil 16x (Static Symbols) and Keil 8051
- LN308 (MITSUBISHI) for M16C/80
- Metroworks
- Microsoft (Standard VC8, Microsoft Extended and PDB)
- Microware Hawk and Hawk Plug&Play ASCII
- NEC CC78K/0 v35
- OMF96, OMF96 (Tasking C196), OMF166 (Keil C166), OMF251 (Keil C251)
- Renesas M32R/M32192 ASCII
- SDS
- Tasking ASCII 16x (M166)
- Texas Instruments TMS470 and C6711
- UBROF
- VisualDSP
- VisualDSP DOS
- Watcom
If you do not see the format you need, please contact us.
Description Files for Communication Networks
CANape not only lets you edit internal ECU parameters. It also gives you access to the data streams of CAN, CAN-FD, LIN, FlexRay and Ethernet / BroadR-Reach bus systems. The specific description files have different formats. The Vector DBC format has become established as the industry standard for the CAN bus. An editor for viewing and creating DBC files is integrated in CANape.
As the description format for the LIN bus, the LIN Consortium has defined the LDF format (LIN Description Files). The FIBEX format (Field Bus Exchange format) developed under the auspices of ASAM is bus-independent and is currently used exclusively for FlexRay.
An editor for viewing and creating DBC files is integrated in CANape. There is also a viewer for displaying LDF and FIBEX formats:
Bus system | Format | Support in CANape |
CAN | DBC | Editing with CANdb++ Editor |
LIN | LDF | Visualization with LDF Explorer |
FlexRay | FIBEX | Visualization with FIBEX Explorer |
Description Files for Diagnostics and Flashing
CANape provides access to diagnostic data and services for the KWP2000 and UDS protocols. This requires description files that can exist in ODX or CDD form.
For access to OBD data, you do not need any additional description files. The required information is already present in CANape. CANape reads-in diagnostic data in ODX and CDD format and displays them in the integrated viewers.
Furthermore CANape supports you when flashing using CCP/XCP and diagnostic protocols with the help of Flash projects.
Format | Support in CANape | Separate authoring tool |
ODX | Access to diagnostic data and services with visualization via ODXStudio View | |
CDD | Access to diagnostic data and services with visualization via CANdelaStudio Viewer | |
vflash, vflashpack | Reprogramming of ECUs with the help of vFlash projects |