There is currently no portable way of knowing what has gone wrong in case of an error. Perhaps there should be some more specific subclasses of can.CanError for some generally usable exceptions.

If this sounds like a good idea we should start a list of exceptions that could be useful.

• Transmit buffer full
• Unknown channel
• Hardware not connected
• Connection/handle is down
• Bus off
• Drivers could not be loaded