Route

This page documents the route configuration.

The route configuration defines how CAN-bus traffic is routed between CAN-P and the CAN-S (CAN-S1, CAN-S2, CAN-S3 and CAN-S4) interfaces.

Configuration file fields

This section is autogenerated from the Rule Schema file.

Routing mode phy.can.route.mode

The routing mode defines the method used to route traffic between the primary interface and the secondary interfaces.

Type

Default

Options

integer

0

Mux: 0 Direct: 1

Configuration explained

Mode

The mode field sets the routing mode used. For additional practical information on the modes, see Introduction and Use cases.

The device supports the following modes (follow the links for details on the specific mode configuration).

Direct-mode

In direct-mode, traffic is (generally) forwarded directly between CAN-P and CAN-S (maintaining message header and payload).

Note

Direct-mode introduces no additional protocols/layers, but offers less control of CAN-S from CAN-P compared to mux-mode.

Mux-mode

Mux-mode uses a protocol for communicating with CAN-S from CAN-P. The protocol enables full control of CAN-S from CAN-P using only a few messages IDs on CAN-P.

Note

Mux-mode offers full control of CAN-S from CAN-P, but introduces additional complexity by adding an additional layer/protocol compared to direct-mode.

The default CANmod.router mux-mode configuration is defined in below DBC-file (uses custom DBC attributes to define the MUX transport-protocol).