Replace specific FTDI device driver with zadig (leaving similar devices untouched) Unicorn...

Is it OK if I do not take the receipt in Germany?

What is the least dense liquid under normal conditions?

Why isn't everyone flabbergasted about Bran's "gift"?

std::is_constructible on incomplete types

Is there any hidden 'W' sound after 'comment' in : Comment est-elle?

Align column where each cell has two decimals with siunitx

How can I wire a 9-position switch so that each position turns on one more LED than the one before?

Married in secret, can marital status in passport be changed at a later date?

Seek and ye shall find

What is the ongoing value of the Kanban board to the developers as opposed to management

Why did Israel vote against lifting the American embargo on Cuba?

What is the term for a person whose job is to place products on shelves in stores?

Israeli soda type drink

Does Mathematica have an implementation of the Poisson Binomial Distribution?

Why didn't the Space Shuttle bounce back into space as many times as possible so as to lose a lot of kinetic energy up there?

Does Feeblemind produce an ongoing magical effect that can be dispelled?

Is a 5 watt UHF/VHF handheld considered QRP?

A Paper Record is What I Hamper

Is Diceware more secure than a long passphrase?

Why is an operator the quantum mechanical analogue of an observable?

Check if a string is entirely made of the same substring

Are all CP/M-80 implementations binary compatible?

What's parked in Mil Moscow helicopter plant?

How to use @AuraEnabled base class method in Lightning Component?



Replace specific FTDI device driver with zadig (leaving similar devices untouched)



Unicorn Meta Zoo #1: Why another podcast?
Announcing the arrival of Valued Associate #679: Cesar ManaraRS232 to USB conversionHow do I use USB in my own projects on Windows?Prolific USB-to-serial communication port is significantly slower under Windows 7 compared to Windows XPGigaware USB to serial adapter not working on Windows 8Usb to Serial RS232 adapter with full handshake/flowcontrol supportUse different drivers for multiple USB devices with identical Vendor and Product IDsidVendor and idProduct for USBLinux FTDI serial driverEnable Virtual Com port, serial connection (update)FTDI COM port not showing correctly on Windows 10





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















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)?










share|improve this question













migrated from electronics.stackexchange.com 15 hours ago


This question came from our site for electronics and electrical engineering professionals, students, and enthusiasts.

























    0















    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)?










    share|improve this question













    migrated from electronics.stackexchange.com 15 hours ago


    This question came from our site for electronics and electrical engineering professionals, students, and enthusiasts.





















      0












      0








      0








      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)?










      share|improve this question














      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)?







      usb ftdi






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Apr 15 at 6:10







      Junius











      migrated from electronics.stackexchange.com 15 hours ago


      This question came from our site for electronics and electrical engineering professionals, students, and enthusiasts.









      migrated from electronics.stackexchange.com 15 hours ago


      This question came from our site for electronics and electrical engineering professionals, students, and enthusiasts.
























          1 Answer
          1






          active

          oldest

          votes


















          0















          is the PID the only property upon which a driver is selected for a given device




          Windows uses the VID:PID pair to detect which driver it should use - these are referenced in those inf files.



          When you wanted a different driver for a device, you are supposed to change the PID.



          Zadig allows for a workaround (sort of): Manually install the libusb_win32 filter driver. This allows switching between libusbK and normal COM port operation without driver re-install, but would affect all other devices with the same VID:PID pair.






          share|improve this answer
























          • 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?

            – Junius
            Apr 15 at 9:03











          • @Junius You can change the PID/VID of FTDI chips with the FT_PROG tool.

            – Jeroen3
            Apr 15 at 10:36












          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1429051%2freplace-specific-ftdi-device-driver-with-zadig-leaving-similar-devices-untouche%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown
























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0















          is the PID the only property upon which a driver is selected for a given device




          Windows uses the VID:PID pair to detect which driver it should use - these are referenced in those inf files.



          When you wanted a different driver for a device, you are supposed to change the PID.



          Zadig allows for a workaround (sort of): Manually install the libusb_win32 filter driver. This allows switching between libusbK and normal COM port operation without driver re-install, but would affect all other devices with the same VID:PID pair.






          share|improve this answer
























          • 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?

            – Junius
            Apr 15 at 9:03











          • @Junius You can change the PID/VID of FTDI chips with the FT_PROG tool.

            – Jeroen3
            Apr 15 at 10:36
















          0















          is the PID the only property upon which a driver is selected for a given device




          Windows uses the VID:PID pair to detect which driver it should use - these are referenced in those inf files.



          When you wanted a different driver for a device, you are supposed to change the PID.



          Zadig allows for a workaround (sort of): Manually install the libusb_win32 filter driver. This allows switching between libusbK and normal COM port operation without driver re-install, but would affect all other devices with the same VID:PID pair.






          share|improve this answer
























          • 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?

            – Junius
            Apr 15 at 9:03











          • @Junius You can change the PID/VID of FTDI chips with the FT_PROG tool.

            – Jeroen3
            Apr 15 at 10:36














          0












          0








          0








          is the PID the only property upon which a driver is selected for a given device




          Windows uses the VID:PID pair to detect which driver it should use - these are referenced in those inf files.



          When you wanted a different driver for a device, you are supposed to change the PID.



          Zadig allows for a workaround (sort of): Manually install the libusb_win32 filter driver. This allows switching between libusbK and normal COM port operation without driver re-install, but would affect all other devices with the same VID:PID pair.






          share|improve this answer














          is the PID the only property upon which a driver is selected for a given device




          Windows uses the VID:PID pair to detect which driver it should use - these are referenced in those inf files.



          When you wanted a different driver for a device, you are supposed to change the PID.



          Zadig allows for a workaround (sort of): Manually install the libusb_win32 filter driver. This allows switching between libusbK and normal COM port operation without driver re-install, but would affect all other devices with the same VID:PID pair.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Apr 15 at 8:46









          Turbo JTurbo J

          1,8991013




          1,8991013













          • 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?

            – Junius
            Apr 15 at 9:03











          • @Junius You can change the PID/VID of FTDI chips with the FT_PROG tool.

            – Jeroen3
            Apr 15 at 10:36



















          • 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?

            – Junius
            Apr 15 at 9:03











          • @Junius You can change the PID/VID of FTDI chips with the FT_PROG tool.

            – Jeroen3
            Apr 15 at 10:36

















          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?

          – Junius
          Apr 15 at 9:03





          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?

          – Junius
          Apr 15 at 9:03













          @Junius You can change the PID/VID of FTDI chips with the FT_PROG tool.

          – Jeroen3
          Apr 15 at 10:36





          @Junius You can change the PID/VID of FTDI chips with the FT_PROG tool.

          – Jeroen3
          Apr 15 at 10:36


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1429051%2freplace-specific-ftdi-device-driver-with-zadig-leaving-similar-devices-untouche%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...

          Tribunal Administrativo e Fiscal de Mirandela Referências Menu de...

          looking for continuous Screen Capture for retroactivly reproducing errors, timeback machineRolling desktop...