ASAM: iLinkRTΒΆ

Legacy/internal identifier: GENERIC-ILINKRT

Vendor information

Vendor

Web page

Product name

Version

ASAM e.V.

https://www.asam.net

High-Speed Automation-Access-Protocol for MC-Server

3.0.0

Categories

MDL πŸ›ˆ

APL πŸ›ˆ

BAN πŸ›ˆ

BMA πŸ›ˆ

SVC πŸ›ˆ

DGN πŸ›ˆ

FIU πŸ›ˆ

EES πŸ›ˆ

FCT πŸ›ˆ

DBG πŸ›ˆ

IMG πŸ›ˆ

AUDIO πŸ›ˆ

ENVSIM πŸ›ˆ

ENVCOM πŸ›ˆ

βœ“

Platform

Operating system

Support

Windows

βœ“

Linux

βœ“

Info

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

PortsΒΆ

SpecificsΒΆ

The ASAM iLinkRT standard defines a protocol for high-speed measurement and calibration data exchange in test automation systems. From protocol version 3 the standard supports multi-server multi-client environments. So multiple clients can connect to multiple servers to receive data via Ethernet (UDP/P) multicast messages to achieve higher throughput and minimum delay.

Software requirements

  • iLinkRT server with protocol version 3.0.0

Features

  • Start and stop measurements manually via tool job or automatically at package start

  • Access scalar measurements

  • Start and stop recording

  • Trace analysis of captured signals if recording format is MDF3 or MDF4 (recommended)

Limitations

  • No server discovery

  • Data acquisition only via multicast supported

  • No page handling

  • A2L information is not requested from iLinkRT server and has to be configured in ecu.test

  • No calibration

  • No access to complex data types (vector, matrix, curve, map)

  • Measurements are captured in default time raster

  • Support for one device respectively port at the same time

Notes

  • The desired capture format can’t be configured in ecu.test tool adapter and has to be set in the tool respectively in the iLinkRT server

  • Multiclient recording: all clients have to send the STOP command to finish the recording

Info

If the communication between iLinkRT server and ecu.test is working but no measurement is received, please check the firewall settings. The UDP destination port for DAQ frames, that is configured in iLinkRT server should be allowed for inbound connections. If there are multiple network nodes like Ethernet routers and switches between Tool Server and iLinkRT server, check their support for multicast forwarding. If Tool Server and iLinkRT server are running on the same machine it is recommended to not operate the iLinkRT server on the loopback device (β€œ127.0.0.1”) but to use a real network interface instead and configure its true IP address in the test bench configuration.