Skip to content

Conversation

@LukasLendvorsky
Copy link

@LukasLendvorsky LukasLendvorsky commented Dec 11, 2025

When running in CAN-FD mode, but with same nominal and data baudrate (just 64B data payload, but without transmitting data faster), BRS bit has to remain at zero. That indicates that there is no bitrate switch happening for data and data is transmitted at same speed.
If I send message with BRS=1, even with data & nominal speed configured the same, I get framing errors on the bus. Even single message like this kills my whole bus.

This introduces option to do that via uavcan.udp.disable_brs set to true, or determines this automatically when uavcan.udp.bitrate indicates same bitrate for header & data.

@coveralls
Copy link

coveralls commented Dec 11, 2025

Coverage Status

coverage: 93.791% (-0.1%) from 93.912%
when pulling f23e13d on LukasLendvorsky:disable_brs
into 811e2eb on OpenCyphal:master.

When running in CAN-FD mode, but with same nominal and data baudrate, BRS bit has to remain at zero. That indicates that there is no bitrate switch happening for data and data is transmitted at same speed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants