I have largely sorted out my problems. I suspect it related to using blocking calls at both ends, while the weather station device is prone to doing i/o in a sequence that has a few random variations in it. This led to deadlock when my code assumed there was some logical sequence to the comms.
This became clearer using the trial version of USBlyzer, rather than usbpcap, while running the vendor software under windows. This way, the usb handshaking was revealed. Of course, I have no way to know if the eccentric timing was due to the hardware or a limitation of usblyzer. I am still living with the libusb0 error reporting bug, but can work around it by referrring to the e.backend_error_code. Hardly elegant, but the code is there now. Cameron. ------------------------------------------------------------------------------ _______________________________________________ pyusb-users mailing list pyusb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pyusb-users
