ASAM: XIL¶
Vendor information
Vendor |
Web page |
Product name |
Version |
|---|---|---|---|
ASAM e.V. |
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:/ProgramData/ASAM/XIL/Implementation.
If required, the directory can be changed via the environment
variable XIL_MANIFEST_DIR or the setting XIL_MANIFEST_DIR in
the [GenericXilApiLib] section of the ToolLibs.ini.
The environment variable will override the setting in ToolLibs.ini.
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
setting XIL_MANIFEST_DIR in the [GenericXilApiLib]
section of the ToolLibs.ini.
The environment variable will override the setting in ToolLibs.ini.
Properties 🛈¶
Name |
Available if |
Default value |
Valid values |
Type |
Description |
|---|---|---|---|---|---|
XIL-API Server |
[ONLINE] |
string |
Server or server version to be connected |
||
Model directory |
uri |
Base directory for searching MAPort configuration files. Absolute path or relative to the tool host base path. |
|||
EES directory |
uri |
Base directory for searching EESPort configuration files. Absolute path or relative to the tool host base path. |
|||
Use .NET Runtime configuration |
☐ |
bool |
Determines if a specific .NET Runtime configuration should be used. |
||
.NET Runtime configuration |
Use .NET Runtime configuration |
uri |
Path to .NET Runtime configuration for running the XIL server. Path can be absolute or relative to the tool host base path. |
||
Timeout for tool call ❲in sec.❳ |
‘600’ |
string |
Timeout after which a tool call is aborted. |