Problem is that when I look into the device manager and plug in the second device again, also the second one (for which I did NOT change the driver) is listed as a libusbk device. Therefore, I have first installed the FTDI Serial Drivers, then unplugged one device and used the ZADIG tool to change the driver of the remaining adapter to libuskK. What I want to do is use one of the adapters with the 'standard' FTDI VCP Driver and the second adapter via libusk and python (libftdi). One of the adapters has an FT245R inside, the other one an FT232R (I see that by reading the device information with the FT_Prog tool from FTDI). I use two kinds of USB/Serial Adapters on the same PC (Windows 8 / Windows 10). Each PCB supports a data transfer rate up to 3. The PCB is USB powered and USB 2.0 full speed compatible. The PCB is RoHS compliant at TTL levels of + 5V or + 3.3V. The FT232R datasheet, DSFT232R, is available at FTDI website. VID/PID), thus effectively doing the same thing the kernel does. Each TTL-232RPCB contains a small internal electronic circuit board, utilising the FT232R plus a USB type-A connector. I have found related questions on this topic, but not an answer to this specific question (at least none that is a solution). Each TTL-232RPCB contains a small internal electronic circuit board, utilising the FT232R plus a USB type-A connector. The FT232R is the latest device to be added to FTDI’s range of USB UART interface Integrated Circuit Devices. Since the malicious FTDI driver modifies the PID without modifying.
