| 
 
libftdi Archives
 
 | 
| From: | Robert Poor <rdpoor@xxxxxxxxx> | 
|---|---|
| To: | libftdi@xxxxxxxxxxxxxxxxxxxxxxx | 
| Date: | Fri, 9 Mar 2018 02:14:22 -0800 | 
| 
 @Uwe: I confess I was slightly confused in my original note.  It turns out that libftdi isn't causing any trouble: I can reliably wiggle the CBUS pins under program control.  However, other parts of our system depend upon using the FTDI part in serial mode. My real problem is that I haven't found a reliable way to load a backend driver (e.g. libusb-win32) for use by PySerial.  The manifestation is that I can create a "filter" for the FTDI that makes it known to Windows, but on occasion (and I can't tell what that occasion is) it forgets about the device and I have to re-run the filter installer. So...truly this issue doesn't belong in the libftdi.  However, perhaps someone on this list has had some experience with the problem I describe. On Fri, Mar 9, 2018 at 2:01 AM, Uwe Bonnes <bon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote: >>>>> "Robert" == Robert Poor <rdpoor@xxxxxxxxx> writes: libftdi - see http://www.intra2net.com/en/developer/libftdi for details.  | 
| Current Thread | 
|---|
 
  |