Skip to content

Handling of errors of ixxat can interface #560

@marcel-kanter

Description

@marcel-kanter

Hi,
for the ixxat backend, all the errors, that may occur are just logged, including stuffing, ack and crc errors. These should be rare but can occur and should be handled.

This is an todo for the ixxat backend in the _recv_internal method.

Are there plans to update the implementation?
Should I try to fix this (this may involve a change in the return of the _recv_internal and adding some general exceptions to the can interface)?
I would change it to something like this, the method should return a message, None or raise an exception.

wait until timeout is over:
if message received:
return message
if ack, stuff, etc error:
raise exception
if timeout (in the interface):
pass

Metadata

Metadata

Assignees

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions