Had LimeSDR working with SDR-Console with some issues. Was fiddling around, eventually decided to uninstall windows driver, to install it again, but something went wrong.
LimeSDR is now under Other Devices in Device Manager with a yellow exclamation mark. Properties shows no driver installed. Tried Update driver, pointing at 64 bit W7 driver directory on harddrive gives “your LimeSDR-USB can not be installed”.
Disconnected Lime, restarted computer, connected Lime again, same thing.
Try to uninstall it as described here in first answer (using pnputil).
In my case, when I run pnputil -e, I have:
Published name : oem98.inf
Driver package provider : Lime Microsystems
Class : Universal Serial Bus controllers
Driver date and version : 08/19/2015 1.2.3.14
Signer name : Lime Microsystems Ltd
So, removing in my case would be: pnputil.exe -d oem98.inf
Thanks for your help.
Did the procedure, uninstalled the drivers.
LimeSDR had to be removed first, otherwise pnputil didn’t let me uninstall the drivers.
Rebooted.
Attached LimeSDR, tried to install new drivers, no go. See screenshots. Text in Dutch I’m afraid…
May be important, may be not. But the drivers from the Wiki LimeSDR-USB User Guide, chapter 4.1 from Cypress are version 1.2.3.10,the ones in the Github are version 1.2.3.14.
Both do not install.
Just reread my first post, will try to give more detailed info on what happened.
At first setup I installed the USB driver from Cypress as described in LimeSDR-USB User Guide 4.1.
Later updated the drivers with the ones from Github.
Also updated firmware.
LimeSDR worked ok with SDR-Console but the program would freeze when changing bandwidth and other settings.
I noticed that LED 5 FX (USB) status sometimes blinked red instead of steady green, especially just before freezing of the SDR-Console. So suspected the USB 3.0 port to be the problem.
Started fiddling with the drivers, back to the earlier (Cypress) version, no improvement. Uninstalling LimeSDR and installing it again. No improvement.
Somewhere along this path the problem occured.
Could it be that somehow the driver files of different versions got mixed up?