The ETAS INCA software is a measurement, calibration, and diagnostic tool for ECUs.


The INCA Transform uses API calls to create an object instance to connect to INCA using the specified INCA Database, Experiment, Hardware, and Workspace. Input data is periodically sent to INCA and output signals are scanned and transmitted from outports.


To use this transform, the ETAS INCA Tool (Product Version and ETAS INCA MDA (Product Version must be installed.

During the installation of INCA, select the MCS-Tool-API component.


Since access to the interfaces is via the TCP/IP network protocol, the network services for using the ToolAPI must be enabled on the local computer.

After the installation of INCA has finished, the tool server through which the COM-API is accessed is not yet active. Use the user settings on the General tab in INCA to start the tool server.



Set values for the following properties:

A2L File path – Browse to the A2L file. The file provides a list of Signals used.

Pick signals – Use this dialog to select Signals for the test.


DataBase Path – Browse for the INCA database folder. If this property is left blank, the INCA Transform opens the default database loaded in the INCA tool.

INCA Experiment – Enter the name of the INCA Experiment to be loaded by the Transform.

INCA Hardware – Enter the INCA hardware device name that is used in the Experiment.

INCA Workspace – Enter the name of the INCA Workspace to be loaded into INCA.

Raster Name – For projects that have segment-synchronous default raster, where a fixed rate raster is preferred. If not specified, the default raster is used. If specified, SetAcquisitionRate()is called with the specified name.


Tick Period – Enter the Tick Period in seconds. This specifies how often the transform sends input data to INCA and scans output ports for data. Depending on PC characteristics, avoid making this value too small. The recommended value is 50 ms or more.

INCA Record Control Signal

INCA_RecordThis Signal can be used to record an INCA experiment.



To Start Recording: Double-click on the Signal's plot line to add a transition. When the window opens, select the Start Recording radio button and click OK.


To Stop Recording: Double-click on the Signal's plot line. When the dialog opens, select the Stop Recording radio button. Two more fields populate:

Record File Path – Browse to the path where the recorded file should be stored and specify a file name.

Record Format – Select a file format for the recorded file from the drop-down list.

Click OK to add an transition. This transition stops the recording and saves the recorded file.


Note: If the stop recording transition is not be added to the TestCase, then the recording is discarded and not saved to any file.

Executing an INCA Experiment with Multiple Devices

To access multiple devices from one INCA experiment, multiple INCA Transforms must be added to the Harness. All the required properties should be same in all Transforms except A2L File path, Pick signals, and INCA Hardware . These properties can be varied according to the device configuration.



Make sure the ECU is powered and in “ignition on” state before attempting an INCA connection.

Make sure the INCA Reference Page (RP) and the Working Page (WP) are exactly the same before starting the test. You can verify this by looking at the checksums.

Make sure the Transform properties for Experiment, Hardware, and Workspace match the names in INCA exactly. The Hardware/device name can be seen in the INCA status window during connection when the dialog “Connecting to <Hardware name>" appears.

Use unique names for each Experiment and Workspace inside the INCA database. This ensures that MxVDev launches the correct INCA Experiment and Workspace. If two different Workspaces have the same name, ‘Workspace_A’ for example, there is a chance of the wrong Workspace being loaded.