Anyone got this scope working with libusb installed on same computer.
I have 2 computers Win2k and XP, both not working when libusb installed.
To get the scope work i needed to completely remove all libusb files.
So is there anyone with working combination?
I need this scope on my laptop and theres also software which uses libusb.
I tried installing libusb along side our usb drivers and our drivers still work fine.
I'm not sure how libusb works but could you have associated the pico usb device with the libusb driver? Try re-installing the driver from device manager and ensure you choose the pico driver.
I've installed LibUSB on a system with a working picoscope 3206. After installation my scope stopped working. Everytime I reinstall the driver the scope is recognized, and appears shortly in the device list, but during installation it is removed and does not appear again.
Did anyone find a solution for the libusb-win32 and PicoScope incompatibility?? I think I have the same problem and I can't just de-install libusb as doing development work with that is a major activity for me.
I'm currently using Libusb-win32 version 1.1.14.0 and PicoScope 6.4.28.0 with PicoScope 3205 hardware and the 3205 seems to enumerate, then disconnects itself. Further it totally screws up any chance of connecting new USB equipment and also stops the PC turning off normally.
I have the solution, which came from me asking on the libusb site.
I came to the conclusion that the libusb-win32 stuff I have was causing trouble, but I did not know how. I therefore asked on the libusb forum
(https://lists.sourceforge.net/lists/lis ... in32-devel , June 2010, "Libusb incompatibility with PicoScope??") and I got the answer I needed.
libusb-win32 is a package of USB goodies for the PC. It allows me to write my own USB firmware on a microcontroller and interface it to my PC using the libusb drivers. That bit works fine.
However, there is also a libusb "filter". I did not know what that was, but the recommendation was that I should install it, so I did. It turns out that this software attempts to replace all USB drivers for all USB kit. Mostly this works, so if a new USB device that the PC has never seen before is plugged in, this filter software intercepts it and provides libusb as a suitable driver. No need to pre-load CDs, etc.
Unfortunately there are still some bugs in the filter software, and it seems to have tried to use the libusb driver AS WELL AS the PicoScope driver. Confusion then reigned and it all fell over.
The solution is to disable the libusb filter.
[(Start Menu->LibUSB-Win32->Disable Filter (admin only)]
Once I did that, the PicoScope worked fine. Fortunately, my other USB kit works fine too, probably falling back on its own drivers. Some other bug may come out of the woodwork as I start to stress the system, but it all looks good so far.