yeah, but I'd like to see what happens with the driver when it's inserted. Maybe reboot without it connected, then connect it and post everything dmesg spits out about it.
I'm just trying to eliminate stuff...
I just installed cangaroo and the GUI together with x2goserver in the end. I'll try to see if I can figure something else out.
Another thing puzzling me: from
https://canable.io/getting-started.html#alt-firmware it seems that the default driver is slcan, while candlelight uses the gs_usb driver.
cansniffer lists some of the possible drivers that can be selected:
{canalystii,cantact,etas,
gs_usb,iscan,ixxat,kvaser,neousys,neovi,nican,nixnet,pcan,robotell,seeedstudio,serial,
slcan,socketcan,socketcand,systec,udp_multicast,usb2can,vector,virtual}
So why was it defaulting to socketcan (or at least the error I had before fixing the "close connection properly" or using your updated code) ?
And why in dmesg I have
Code:
dmesg | grep -i can
[ 6.060750] usb 1-1.2.5: Product: candleLight USB to CAN adapter
[ 6.350431] usb 1-1.2.7: Product: candleLight USB to CAN adapter
[ 13.570422] CAN device driver interface
[ 14.755824] vc4-drm soc:gpu: [drm] Cannot find any crtc or sizes
[ 14.758447] vc4-drm soc:gpu: [drm] Cannot find any crtc or sizes
[ 17.209193] IPv6: ADDRCONF(NETDEV_CHANGE): can1: link becomes ready
[ 18.232968] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
[ 80.618222] can: controller area network core
[ 80.618297] NET: Registered PF_CAN protocol family
[ 80.633199] can: raw protocol
can: raw protocol ???
Is it possible that python-can library is trying to use the wrong driver ?
Note that I implemented venv since with Debian Bookworm and later you cannot install extra packages with pip into your system (or shouldn't).