|
From: Xiaofan C. <xia...@gm...> - 2018-03-10 02:23:49
|
On Sat, Mar 10, 2018 at 2:43 AM, Tim Roberts <ti...@pr...> wrote: > Robert Poor wrote: >> ... >> Two questions: >> >> * I know that libusb-win32 is long in the tooth. Is there something >> else we should be using as the backend for PyFtdi? >> >> * From time to time, Windows appears to forget about the filter, >> requiring the user to re-run the filter installer. Do you have >> insights on how or why this happens (and how to prevent it)? > > Unless your device has a serial number, every time you move it to a > different port or a different hub, it is seen as a brand-new device, and > a fresh driver record is created. > > I don't know how deep you want to go. It is certainly possible to have > your application use the extremely verbose SetupDi APIs to scan through > the USB devices, check whether they have the filter, add the filter, and > restart the device. Pete's libwdi may be used as well. https://github.com/pbatard/libwdi Zadig is an example provided in libwdi, it has the feature to install libusb-win32 filter to a USB device or an interface of a USB composite device. There are command line example as well. -- Xiaofan |