Open darsor opened 5 years ago
Thanks for the report. If you have an elegant solution to automatically handle this, do not hesitate to share it !
I am seeing this issue too when using my new Raspberry Pi 4... I can't see the "detach kernel driver" command in the pyusb log file. When using my Raspberry Pi 3 and 2 I can see the "detach kernel driver" in the log file. I have no idea why there is a difference.
I have a sensor which implements two USB interfaces, one is USB HID, the other is USBTMC.
Currently when connecting to a USB device, pyvisa-py detatches any kernel driver from the first interface (here).
In the case of this sensor, the USBTMC interface is interface number 1, not 0. In order to use the device I have to manually detach the kernel driver using pyusb, before opening it with pyvisa.
For reference, the error message generated was
and dmesg reported