technical software development
Downloads FAQ

Getting started using the ASAP2Demo...

Table of contents:

  1. Introduction
  2. Graphical user interface description
  3. Find and select ASAP2 objects
  4. Change ASAP2 objects
  5. Add ECU calibration data
  6. Display, adjust and store calibration data
  7. Export and import calibration data
  8. Updating A2L object addresses from an ELF file
  9. Connect to an ECU with XCP over Ethernet(TCP/UDP)
  10. Activating and connecting to CAN hardware
  11. Connect to an ECU with XCP on CAN or CCP
  12. Configuring DAQ lists for online measuring
  13. The ECUSimulator
  14. Starting the ECUSimulator manually
  15. Force ASAP2Demo to run as a 32Bit process

or watch demos on the


After starting the ASAP2Demo...

For each specified ASAP2 file a document is created displaying the ASAP2 hierarchy in a tree, the original content and the received ASAP2 parser messages in a data table. After selecting a specific ASAP2 object in the tree, the property grid below the tree displays properties corresponding to the selected ASAP2 object.

Graphical user interface description:

ASAP2 UI overview

How to find and select ASAP2 objects...

How to change ASAP2 object properties

How to add ECU calibration data files to the A2L model

How to display, adjust and store calibration data

After a calibration data file is loaded...

After a calibration data file is changed...

How to export and import calibration data

After a calibration data file is loaded...

Updating A2L object addresses from an ELF file

  1. Open any A2L file with ASAP2Demo
  2. Open an ELF file containing symbols corresponding to the A2L objects
  3. The ELF File demo window displays a table with known A2L objects, the original A2L address, the symbol's address read from the ELF file and a synchronizer message
  4. If no A2L file is opened before the ELF File demo window displays only the ELF file analysis tabs.

The ASAP2Demo currently does not allow to save the updated content to a new A2L file!
For an example of how to do an A2L address update with the ASAP2Library see the ELF example

How to connect to an ECU over XCP on Ethernet (TCP/UDP)

After an XCP over Ethernet supporting A2L File is loaded...

Activating and connecting to CAN hardware

The philosophy of ASAP2Demo/ASAP2Library to communicate with CAN Hardware is:

Depending on the CAN Hardware driver, ASAP2Demo searches the %SYSTEMROOT%\system32 directory for a driver DLL. See the list below of supported CAN hardware and it's corresponding driver DLLs.

CAN provider 32 Bit driver 64 Bit driver Supports
8devices usb2can.dll not available
Advantech not needed not needed
ESD ntcan.dll ntcan.dll
Ebersp├Ącher electronics fcbase.dll fcbase.dll
IXXAT vcinpl.dll vcinpl.dll
Kvaser canLib32.dll canLib32.dll
MHS Elektronik Tiny-CAN mhstcan.dll mhstcan.dll
Lawicel canusbdrv.dll canusbdrv64.dll
National Instruments (NI-CAN) nican.dll not available
National Instruments (XNET) nixnet.dll nixnet.dll
Peak pcanbasic.dll pcanbasic.dl
Softing canl2.dll canl2.dll
Vector vxlapi.dll vxlapi64.dll

How to connect to an ECU over XCP on CAN or CCP

Prerequisites (for a Vector CAN enabled product), for any other type of CAN hardware, the same procedure of configuration applies:


Vector driver CAN configuration

After this, enable the checkbox to use the Vector CAN device in the options dialog. ASAP2Demo should now be able to access the CAN device. If the configuration is successful, the ASAP2Demo shows an accessible CAN device in it's status bar:
Active Vector CAN Configuration

Using the ECUSimulator on the same machine, the hardware type must be set to 'Virtual'.

Configuring DAQ lists for online measuring

The XCP and CCP DAQ selection pages displays available DAQ lists and connected DAQ events. The page allows to enable or disable each single DAQ List to be used in online measuring.

The ECU Simulator

Starting the ECU Simulator manually

  1. Open a console window in the ASAP2Demo installation folder.
  2. The following command line is required to start the ECUSimulator process:
    ECUSimulator [-debug] TCP:Port|UDP:Port|CAN:Driver:Port|CCP:Driver:Port|UDS:Driver:Port A2LFile [DataFile]
    XCP on TCP Simulator on port 1800:
    ECUSimulator TCP:1800 ASAP2Example.a2l ASAP2Example.hex
    XCP on CAN Simulator using the Vector CAN driver on Port 2:
    ECUSimulator CAN:vector:1 ASAP2Example.a2l ASAP2Example.hex
    CCP Simulator using the Kvaser CAN driver on Port 1:
    ECUSimulator CCP:kvaser ASAP2Example.a2l ASAP2Example.hex
    UDS Simulator using the Kvaser CAN driver on Port 3:
    ECUSimulator UDS:kvaser:2 ODXExample.odx

The result is an ECUSimulator process supporting the specified protocol. The process simulates an ECU defined in the ASAP2Example.a2l with calibration data from ASAP2Example.hex.

Force ASAP2Demo to run as a 32 Bit process

This paragraph is only of interest if ASAP2Demo is installed on a 64 Bit OS, but usually this is the default in these days.
As the ASAP2Demo/ECUSimulator starts in this case in 64 Bit mode, using 32 Bit CAN drivers (the National Instruments CAN driver only supports 32 Bit applications) or using a 32 Bit Seed&Key DLL to get CCP/XCP/UDS access on ECUs will fail.

ASAP2Demo provides a workaround in this case:
The shortcut 'Force to run as 32Bit Process' in the ASAP2Demo folder forces an ASAP2Demo/ECUSimulator process to start always in 32 Bit mode.
This has only to be done once after ASAP2Demo is installed or updated to a newer version.

Execute the shortcut by a right-click and click 'Run as administrator'