You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MessageA:
SignalA (Plain / Normal signal)
Signal multiplexorX
SignalY multiplexed by multiplexorX
SignalZ multiplexed by multiplexorX
Basically this means here the multiplexorX indicates whether SignalY or SignalZ ist send as part of this frame. A "plain" signal is always included in the frame (not multiplexed). A message may contain zero, one or multiple multiplexors.
Whether a signal is multiplexed or not is indicated by the MultiplexIndicator.
The text was updated successfully, but these errors were encountered:
Designwise I think multiplexed signals can be represented in two ways:
A function that returns an Option e.g. here signal_y_raw(&self) -> Option<...>
A function that returns an Enum e.g. here signal_x_raw(&self) -> SignalXMultiplexed where the SignalXMultiplexed enum would basically be Y or Z.
I think from an API perspective it's actually more convenient to use the enum variant as it makes it clear what signals are part of which multiplexor and saves some comparsions with Option values that can not even be Some.
Messages may contain multiplexed signals e.g.
MessageA:
SignalA (Plain / Normal signal)
Signal multiplexorX
SignalY multiplexed by multiplexorX
SignalZ multiplexed by multiplexorX
Basically this means here the multiplexorX indicates whether SignalY or SignalZ ist send as part of this frame. A "plain" signal is always included in the frame (not multiplexed). A message may contain zero, one or multiple multiplexors.
Whether a signal is multiplexed or not is indicated by the MultiplexIndicator.
The text was updated successfully, but these errors were encountered: