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
I implemented the CANopen project, canopend, into my controller and am able to use it just fine with I/O modules through the CAN bus. When I physically disconnect the CAN bus from my controller, however, I notice the CPU% of the canopend command in linux shoots up to 5-6x from what is was before.
When the CAN bus is disconnected, I see these log messages from the canopend: (CO_CANsend) Transmitting CAN msg OID 0x202 failed(can0)
...and it persists until I reconnect the CANbus back into the controller. I found
My best guess for the CPU% increase at this moment is that canopend sees that there is no CAN bus and it is stuck on a cycle where it keeps retrying often, and maybe that's whats taking up the extra CPU? Is there any setting in the stack that I can set in order to mitigate this?
Any insight/direction on this would be much appreciated, thank you!
The text was updated successfully, but these errors were encountered:
Hello!
I implemented the CANopen project, canopend, into my controller and am able to use it just fine with I/O modules through the CAN bus. When I physically disconnect the CAN bus from my controller, however, I notice the CPU% of the canopend command in linux shoots up to 5-6x from what is was before.
When the CAN bus is disconnected, I see these log messages from the canopend:
(CO_CANsend) Transmitting CAN msg OID 0x202 failed(can0)
...and it persists until I reconnect the CANbus back into the controller. I found
My best guess for the CPU% increase at this moment is that canopend sees that there is no CAN bus and it is stuck on a cycle where it keeps retrying often, and maybe that's whats taking up the extra CPU? Is there any setting in the stack that I can set in order to mitigate this?
Any insight/direction on this would be much appreciated, thank you!
The text was updated successfully, but these errors were encountered: