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
Currently, communication errors are polled for in the CO_JOB_PERIODIC context by calling co_emcy_handle_can_state(). To avoid the need for periodic polling (see #6), the drivers could send events on errors, just like RX is handled.
For embedded controllers they most likely provide the ability to interrupt on error flags.
Currently, communication errors are polled for in the
CO_JOB_PERIODIC
context by callingco_emcy_handle_can_state()
. To avoid the need for periodic polling (see #6), the drivers could send events on errors, just like RX is handled.For embedded controllers they most likely provide the ability to interrupt on error flags.
SocketCAN on linux can be told to send error events through the regular RX path, see https://www.kernel.org/doc/html/latest/networking/can.html#raw-socket-option-can-raw-err-filter for details.
If some platform doesn't support it, there's always the option to fall back to a separate polling thread.
The text was updated successfully, but these errors were encountered: