2
I have found related questions on this topic, but not an answer to this specific question (at least none that is a solution).
I use two kinds of USB/Serial Adapters on the same PC (Windows 8 / Windows 10). 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).
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).
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.
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.
I suspect this is because both mentioned FTDI chips use the same PID 0x6001 (btw: is the PID the only property upon which a driver is selected for a given device?)
What is a clean solution to the problem (without manually changing the PID of one of the adapters)?
Ok, that´s what i feared. So no way around changing the PID... I wonder how this is handled in professional use. Just because a comnay rolls out its own usb driver for a specific device it should not affect other vendor´s devices just because they also use a FTDI inside? – None – 2019-04-15T09:03:49.693
1@Junius You can change the PID/VID of FTDI chips with the FT_PROG tool. – Jeroen3 – 2019-04-15T10:36:50.957