Skip to main content

RemotiveTopology glossary

The terms used in the RemotiveTopology documentation and on the RemotiveLabs website.

ARXML​

AUTOSAR XML, the file format of AUTOSAR system descriptions and ECU extracts. RemotiveTopology reads ECUs, channels, sockets, and SOME/IP services from ARXML. See Describing the platform.

Behavioral model​

Code that emulates the behavior of an ECU, for example written in Python with the RemotiveTopology framework or as an FMU. It runs in its own container and sends and receives through the RemotiveBroker of its ECU. See Behavioral models.

Channel​

A network that ECUs communicate on, such as a CAN bus, a LIN bus, or an Ethernet network. The platform describes the channels, and the instance decides how each one is run, for example as a virtual network or connected to hardware. See Channels.

Closed-loop simulation​

A simulation where the inputs to the device under test respond to what it does, because the ECUs around it are mocks or behavioral models that react to its outputs. Compare with open-loop simulation.

Container​

An isolated process that Docker or Podman runs. Every part of a running topology is a container, including the RemotiveBrokers, mocks, models, virtual ECUs, tests, and tools. See What runs in a topology.

DBC​

A file format that describes the frames and signals on a channel (typically CAN), and which ECUs send and receive them. A DBC file doesn't name the channel, so you name the channel in a platform file. See Using DBC.

Device under test (DUT)​

The ECU or software that a test verifies. In RemotiveTopology the device under test is often a virtual ECU or hardware, surrounded by mocks and behavioral models.

ECU​

Electronic control unit, a computer in the vehicle. In RemotiveTopology an ECU is anything that communicates on the channels, whatever its implementation. See ECU.

ECU extract​

An ARXML file that only describes what's relevant for a single ECU. A platform can combine several ECU extracts. See Modularity.

External ECU​

An ECU that's part of the instance but that RemotiveTopology doesn't run, for example hardware. See External ECUs.

FMU​

Functional Mock-up Unit, a simulation model that follows the Functional Mock-up Interface (FMI) standard. An FMU can run as a behavioral model. See FMU models.

Hardware-in-the-loop (HIL)​

Testing where the device under test is physical hardware, connected to a simulated environment. See Connect hardware.

Hybrid HIL​

A setup that mixes virtual and physical ECUs, communicating over CAN, LIN, or Ethernet as in the vehicle. Virtual ECUs run in containers and can be replaced with hardware one at a time. See Connect hardware.

Instance​

A file, *.instance.yaml, that describes what to run: which ECUs and channels of the platform, how each ECU is implemented, how channels connect to hardware, and which tests to run. See Instantiating topology.

LDF​

LIN description file, a file format that describes a LIN channel: its ECUs, frames, signals, and schedule tables. An LDF file doesn't name the channel, so you name the channel in a platform file. See Using LIN description files.

Mock​

An ECU that sends its cyclic frames with default values and has no behavior of its own. Tests or other code control the values. Mocks are the simplest way to provide a restbus. See Mocks.

Namespace​

How an ECU sees a channel, named <ECU>-<Channel>, for example BCM-BodyCan. Models, mocks, and tests send and receive signals in namespaces. See Namespaces.

Open-loop simulation​

A simulation that plays back recorded data, such as a drive cycle, into the system. The outputs of the system don't affect the inputs. See Recordings.

Platform​

A description of the vehicle: its ECUs, its channels, and how the ECUs communicate. A platform can combine DBC, LDF, ARXML, and Fibex files with *.platform.yaml files. See Describing the platform.

Profile​

A Docker Compose profile. A container with a profile, such as a test container, only starts when you ask for that profile. See Profiles.

RemotiveBroker​

The RemotiveLabs software that sends and receives on vehicle networks and encodes and decodes signals, with a gRPC API. In a topology it stands in for ECUs and acts as the TopologyBroker. See What runs in a topology.

RemotiveBus​

A Docker and Podman network plugin for Linux that gives containers SocketCAN and VLAN networks, and connects them to hardware on the host. See RemotiveBus.

Restbus​

Simulated traffic from the rest of the vehicle: the cyclic frames that the ECUs around the device under test send, at their cycle times. Mocks and behavioral models in RemotiveTopology send their frames with a restbus.

Software-in-the-loop (SIL)​

Testing where all ECUs are software, for example mocks, behavioral models, FMUs, and virtual ECUs, running on a computer or in CI without hardware.

Test access points (TAP)​

A copy of the traffic on an Ethernet channel that tests can observe without affecting it. See Test access points (TAP).

Topology​

The ECUs and channels of a vehicle and how they're connected. In RemotiveTopology, it also means a running instance.

TopologyBroker​

The RemotiveBroker that every topology has, which gives tests and tools access to all namespaces in the topology. It's reachable at http://localhost:50051 from your computer. See The TopologyBroker.

Vehicle-as-code​

Describing the vehicle's architecture, ECUs, and test environments in text files that you keep in version control, review, and run like code. See RemotiveTopology concepts.

Virtual ECU (vECU)​

The production software of an ECU running without its hardware, for example in a container. A virtual ECU replaces the RemotiveBroker of its ECU and communicates on the channels directly. See Virtual ECUs.

Workspace​

The folder that RemotiveTopology commands run in, with a hidden .remotive folder for caches. See Workspace.