Mux-mode CAN-S to CAN-P direction

This section describes mux-mode in the CAN-S to CAN-P direction.


Configuration file fields

This section is autogenerated from the Rule Schema file.

Secondary to primary (S to P) routing phy.can.route.mux.s2p

Configuration of S-to-P.

Filter phy.can.route.mux.s2p.filter

Configure S-to-P traffic type filters. Disable unused traffic types to reduce load on P.

RX message phy.can.route.mux.s2p.filter.rx_msg

Type

Default

Options

integer

1

Disable: 0 Enable: 1

TX acknowledge phy.can.route.mux.s2p.filter.tx_ack

Type

Default

Options

integer

0

Disable: 0 Enable: 1

Error frame phy.can.route.mux.s2p.filter.err

Type

Default

Options

integer

0

Disable: 0 Enable: 1


Message phy.can.route.mux.s2p.message

Configure the message used for transporting traffic from S to P. If supported by P, enable CAN-FD and BRS for increased bandwidth.

ID Format phy.can.route.mux.s2p.message.id_format

Message identifier format.

Type

Default

Options

integer

0

Standard (11-bit): 0 Extended (29-bit): 1

ID value (HEX) phy.can.route.mux.s2p.message.id

Message identifier. Example: 1FF.

Type

string

Frame format phy.can.route.mux.s2p.message.frame_format

Message frame format.

Type

Default

Options

integer

0

Standard: 0 FD: 1

Bit-Rate Switch phy.can.route.mux.s2p.message.brs

Message data bit-rate-switch (FD only).

Type

Default

integer

0


Configuration explained

When in mux-mode, the CANmod.router can be configured to output traffic observed on CAN-S to CAN-P (using the mux-protocol).properties

The filter section configures the traffic (types) to forward to CAN-P (e.g. messages received on CAN-S). The message section configures the message header information of the message used to output traffic from CAN-S to CAN-P.


Filter

The CANmod.router can output the following event types observed on CAN-S to CAN-P:

  • Messages received on CAN-S (rx_msg).

  • Messages successfully transmitted by the CANmod.router on CAN-S (tx_ack)[1].

  • Error frames observed on CAN-S (err).

Each of above event types can be enabled/disabled.

Note

It is recommended to disable unused event types to reduce load on the CAN-P bus.


Message

The output message generated by the CANmod.router on CAN-P (containing events observed on CAN-S) is configurable.

Warning

Ensure that the message ID generated by the CANmod.router does not collide with other message IDs on the CAN-P bus.

If the CAN-P bus supports CAN-FD, bandwidth can be optimized by configuring the message to use CAN-FD (longer payloads) and bit-rate-switch (fast data transfer).

Note

It is possible to communicate CAN-FD on CAN-S without using (or supporting) CAN-FD on CAN-P.