Skip to main content

Supported platforms and protocols

RemotiveTopology runs on Linux, on Windows with WSL2, and on macOS. Linux has full support. Some features need RemotiveBus, which is only available on Linux, including WSL2. For installation, see Install RemotiveTopology.

Operating systems​

LinuxWindows (WSL2)macOS
Container engineDocker Engine or PodmanDocker Engine, installed in WSL2Docker or Podman
RemotiveBusYesYes, with a WSL2 kernel that has the vcan and vxcan modules, see WSL2 in WindowsNo, run RemotiveTopology in a Linux virtual machine
remotive topology commandsYesIn WSL2, not in PowerShellYes
Behavioral models and tests in PythonPython 3.10 or laterPython 3.10 or laterPython 3.10 or later

On macOS, the preferred way is to run RemotiveTopology in a Linux virtual machine, so you can use RemotiveBus. Without RemotiveBus, CAN and LIN channels fall back to UDP emulation, and the features in the following table that need RemotiveBus aren't available.

Channel drivers and features​

FeatureNeedsLinuxWindows (WSL2)macOS
CAN with SocketCAN, the defaultRemotiveBusYesYesLinux VM
CAN emulation using UDPNothingYesYesYes
LIN, over the CAN driversRemotiveBus or UDPYesYesUDP, or Linux VM
Ethernet with Docker bridge networks, the defaultNothingYesYesYes
Ethernet with VLANRemotiveBusYesYesLinux VM
Test access points (TAP)RemotiveBus with DockerYesYesLinux VM
SocketCAN tools such as candumpRemotiveBusYesYesLinux VM
Virtual ECUs on CANRemotiveBusYesYesLinux VM
Connecting hardwareRemotiveBus and a Linux driver for the adapterYesUSB adapters passed through to WSL2Linux VM

RemotiveBus provides TAP only for Docker networks, not for Podman.

Protocols​

ProtocolDescribed byNotes
CANDBC, ARXMLBit rate set in the platform, see CAN channel
CAN FDDBC, ARXMLData phase bit rate and bit rate switching set in the platform with baudrate_fd and brs
LINLDFTransported inside CAN frames, see LIN channels
Ethernet PDUs over UDPARXML, platform filePoint-to-point sockets, see Ethernet PDUs
SOME/IP over UDPARXML, FibexServices and instances, see SOME/IP

File formats​

FormatUsed for
*.platform.yamlPlatforms, see Describing the platform
*.instance.yamlInstances, see Instantiating topology
DBCCAN channels, their ECUs, frames, and signals
LDFLIN channels, their ECUs, frames, signals, and schedule tables
ARXMLSystem descriptions and ECU extracts: channels, ECUs, sockets, and SOME/IP services
FibexSOME/IP services
FMU, FMI 2.0 and 3.0 with co-simulationFMU models
CAN dump and CSVRecordings

The topology schema describes every field of the platform and instance files.