Channels

Channels in an instance use sensible defaults and work without configuration in a purely virtual environment. Channels must be configured when connecting to physical hardware or when connecting to software running outside the containerized environment.

CAN

RemotiveTopology supports two ways of instantiating a CAN channel:

LIN

Local Interconnect Networks (LIN) aren't exposed as network interfaces, unlike Ethernet and CAN via SocketCAN. To work around that, RemotiveBroker transports LIN frames inside CAN frames. This is why a LIN channel uses the same drivers and driver configuration as a CAN channel. RemotiveBus is available on Linux and Windows (WSL), or on macOS by using a Linux virtual machine. UDP emulation is available on all platforms as a fallback.

Ethernet

Ethernet channels don't require any configuration by default. The Docker bridge driver is used to provide ECUs with a network interface on the subnet that's configured for the channel in the platform.

Test access points (TAP)

A test access point (TAP) lets you view the raw traffic on an Ethernet channel, including traffic between ECUs that don't use a broker. Traffic on the channel is mirrored so that it can be passively observed without affecting the actual ECU communication.