Mux-mode CAN-P to CAN-S direction
This section describes mux-mode in the CAN-P to CAN-S direction.
Configuration file fields
This section is autogenerated from the Rule Schema file.
Primary to secondary (P to S) routing phy.can.route.mux.p2s
Configuration of P-to-S. Configure messages used for transporting traffic from P to S. Add one message for each CAN-bus node on P generating traffic for S.
Type |
Min items |
Max items |
|---|---|---|
array |
0 |
8 |
Item phy.can.route.mux.p2s.item
ID Format phy.can.route.mux.p2s.item.id_format
Message identifier format.
Type |
Default |
Options |
|---|---|---|
integer |
0 |
Standard (11-bit): |
Message ID (hex) phy.can.route.mux.p2s.item.id
Message identifier. Example: 1FF.
Type |
|---|
string |
Configuration explained
When in mux-mode, the CANmod.router must be configured to know which message IDs use the mux-protocol on CAN-P. Up to 8 message IDs can be added, such that multiple CAN-bus nodes can simultaneously (without risk of ID collisions) transmit messages on CAN-P through the CANmod.router to CAN-S. I no traffic should be routed from CAN-P to CAN-S, the list can be left empty.
Note
The CANmod.router accepts messages on the configured IDs regardless of frame-format (standard or FD).
Examples
Example: The CANmod.router CAN-P is connected to a bus with several other CAN-bus nodes. Two nodes, node-A and node-B, (also connected to P) implement the mux-protocol and should be able communicate with CAN-S through the CANmod.router. To avoid that message generated by node-A and node-B collide, they should use separate IDs to communicate with the CANmod.router on CAN-P.
Below table illustrates how the two p2s messages can be configured.properties
# |
ID-format |
ID-value |
|---|---|---|
1 (node-A) |
Standard |
11 |
2 (node-B) |
Standard |
12 |
The CANmod.router is configured to expect messages using the mux-protocol on standard IDs 0x11 and 0x12.