Skip to content

Conversation

@msuevern
Copy link
Contributor

To align simulation behavior with real-world FlexRay systems, the symbol operation has been extended with an additional Slot ID. This field must be set in the case of a COLLISION_AVOIDANCE_SYMBOL. By including the Slot ID, the simulation can resolve conflicts based on the timing and slot assignment of the startup frames, ensuring deterministic and realistic behavior.

@msuevern msuevern linked an issue Oct 24, 2025 that may be closed by this pull request

|Slot ID
|2 byte
|The Slot ID of the startup frame. In case of `COLLISION_AVOIDANCE_SYMBOL`, the slot ID of the startup frame to be sent must be specified.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@msuevern the additional line break is missing here.

fmi3LsBusFlexRayCycleId cycleId; /**< The cycle the symbol is transmitted in. */
fmi3LsBusFlexRayChannel channel; /**< The channel(s) on which the symbol is transmitted. */
fmi3LsBusFlexRaySymbolType type; /**< The type of symbol. */
fmi3LsBusFlexRaySlotId slotId; /**< The slot ID of the startup-frame in cases of a COLLISION_AVOIDANCE_SYMBOL */
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@msuevern you also had to adapt the other FlexRay header file for creating the operations via C functions. Please be aware that you also had to adapt the specified test afterwards.

@bmenne-dspace bmenne-dspace added the flexray Issue related to FlexRay bus label Nov 7, 2025
@bmenne-dspace bmenne-dspace added this to the 1.1.0-final milestone Nov 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

flexray Issue related to FlexRay bus

Projects

None yet

Development

Successfully merging this pull request may close these issues.

FlexRay: Inconsistent Startup Conflict Resolution

3 participants