1

I am struggeling to get some communication via USB using PyUSB (help there is also very much appreciated). For me, the documentation of PyUSB does not cover the full picture (including such traps and time-consuming annoyances. The minimal examples do not work in my case. During the annoying trial and error process, I also used Zadig to force a certain driver.

enter image description here

enter image description here

The communication was working with the Keysight IO Libraries Suite, however, I want to use PyUSB in my own programs. Due to forcing another USB driver (libusbK) via Zadig, the Keysight Suite doesn't work anymore. However, now it seems I can't go back to the original driver which was installed when installing the Keysight IO Library Suite. Re-installation or reparing of the Keysight Suite does not help.

How to get the Keysight Suite back to work? Which file do I maybe have to delete manually or which Registry entry to change? Any hints appreciated!

theozh
  • 185

1 Answers1

1

Ok, it seems it was easier than expected:

  • Device Manager
  • Device in question (right mouse click)
  • Update driver
  • Browse my computer for drivers
  • Let me pick from a list of available drivers on my computer
  • Select USB Test and Measurement Device (IVI) (which is ausbtmc.sys). Luckily, this driver was still on the list.

enter image description here

What puzzled me and made me feel unsure...

  • the first time I changed the driver with Zadig it took forever and Zadig stopped with the message that driver (libusbK.sys) installation failed (at least, I got entertained by Zadig status messages ;-). But the new driver was apparently installed nevertheless. Pretty strange!
  • after having changed the driver with Zadig, and trying to get back to the original driver (ausbtmc.sys), why the Keysight software did not install their original driver when re-installing it?
theozh
  • 185