ASAM: XILΒΆ

Legacy/internal identifier: GENERIC-XIL-API

Vendor information

Vendor

Web page

Product name

Version

ASAM e.V.

https://www.asam.net

Generic Simulator Interface

2.0.x, 2.1.x, 2.2

Categories

MDL πŸ›ˆ

APL πŸ›ˆ

BAN πŸ›ˆ

BMA πŸ›ˆ

SVC πŸ›ˆ

DGN πŸ›ˆ

FIU πŸ›ˆ

EES πŸ›ˆ

FCT πŸ›ˆ

DBG πŸ›ˆ

IMG πŸ›ˆ

AUDIO πŸ›ˆ

ENVSIM πŸ›ˆ

ENVCOM πŸ›ˆ

βœ“

βœ“

βœ“

βœ“

Data sources

File format

Comment

*.portconfig

Port configuration files

Signal recordings πŸ›ˆ

File format

Comment

*.csv, *.mdf, *.mf4

Platform

Operating system

Support

Windows

βœ“

Linux

βœ“

Info

This tool can be configured and used multiple times in parallel.

PortsΒΆ

SpecificsΒΆ

Initial setup

The XIL API server must always be selected. If none is displayed, check the installation of the XIL API server and make sure the *.imf files are in the right directory. See sections XIL under Windows and XIL under Linux for details.

In addition, you need to set

  • the model directory if a model port is used,

  • the EES directory if an EES port is used.

Info

This is the generic implementation for the ASAM XIL standard. There are more specific implementations for certain tools like dSPACE: XIL or Typhoon.

Mandatory software

  • The XIL-API server and the ASAM AE XIL Standard Assemblies 2.0.1 or higher

    • both shipped with the software you want to connect

    • sometimes needs to be installed separately

  • ASAM AE XIL Standard Assemblies 2.0.1 or higher

  • Specific configuration file for each port.

If all prerequisites are fulfilled, you can select the tool with the XIL-API Server property.

The bus ports can only be used if at least one model port is configured.

XIL servers built for the following .NET platforms are supported by ecu.test:

  • .NET-Framework (up to 4.8, Windows specific)

  • .NET (version 6 or newer)

From .NET 6 on, please specify a .NET Runtime configuration for the selected XIL-API Server accordingly. This is a path to the *.runtimeconfig.json file which has been shipped with the XIL-API Server. If this is not the case, please refer to the Microsoft documentation on .NET Runtime configuration settings.

XIL under Windows

In Windows there is a default directory for manifest files. ecu.test looks for *.imf files in the directory C:ProgramDataASAMXILImplementation.

XIL under Linux

In contrast to Windows there is no default directory for manifest files in Linux. The directory can be set manually via the environment variable XIL_MANIFEST_DIR or the correspondent setting in ToolLibs.ini. The environment variable will override the setting in ToolLibs.ini.