Bus Off occurs when the transmit error count raises above 255. Whenever a node fails to transmit a frame, it increases the error counter and when the counter increases beyond 255, the node gets in bus-off state and can not further participate on the bus.
Some situations which lead to Bus Off situation–
CAN_H / CAN_L line interrupted CAN_H shorted with CAN_L Incorrect Baud Rates at receiving and transmitting nodes.
An interesting article on Bus-Off - [LINK]
The article lists several bus failure modes which can be also be used to inject bus off.
Bus Off occurs when the transmit error count raises above 255. Whenever a node fails to transmit a frame, it increases the error counter and when the counter increases beyond 255, the node gets in bus-off state and can not further participate on the bus.
Some situations which lead to Bus Off situation–
CAN_H / CAN_L line interrupted CAN_H shorted with CAN_L Incorrect Baud Rates at receiving and transmitting nodes.
An interesting article on Bus-Off - [LINK]
The article lists several bus failure modes which can be also be used to inject bus off.
Thank you for the answer.
Would it be possible to produce Bus-Off state with the help of a debugger? e.g. would it be possible to set an incorrect Baud rate via a debugger? (I looked at the manual, but could not locate the address to manipulate an incorrect baud rate.)
You can set the baudrates from config tool like EB tresos, S32 CT, etc.
Different baudrates would result in error in frame transmission and would increase the error count. And when the counter increases over 255, the controller will go in Bus off state.