V2 Test DLLs

September 19th, 2015: Here are new DLLs, select the correct DLL for your system, then copy this DLL to the SDR-Radio.com installation folder, for example C:\Program Files\SDR-RADIO-PRO.com on a 64-bit system.

Feedback welcome via the Yahoo! group only please.

Screenshot of version 3 (internal kit) with the CloudIQ on 80m.


September 15th, 2015: Great news - a CloudIQ arrived today, implementation starts on Wednesday.

Users are already excited.

Do Not Rename

Do not rename entries for the SDR-IQ or SDR-14, this will confuse the software, When time permits this feature will be supported, but for the time being don't rename...

SDR-IQ & Windows 10

December 25th, 2016: SDR-IQ seems to be very much plug-and-play with Windows 10. As part of a debugging exercise a SDR-IQ was plugged into the development Windows 10 64-bit system, the drivers were downloaded and installed automatically, the SDR-IQ was found and started first time.


Windows 10 Problems

Note: the SDR-IQ works well with the latest releases of Windows 10. This post is left for reference only.

It seems that there's a problem with the SDR-IQ  and Windows 10 64-bit edition. First of all the reason other software such as the most excellent SpectraVue work is because they are 32-bit programs whereas SDR-Radio.com's software uses 64-bit executables on 64-bit editions of Windows.

Fortunately Ian Wade G3NRW determined that it's necessary to roll back the FTDI driver to v2.10.00. Here's his posting from the Yahoo! support group.

Original problem:
After a recent Windows 10/64 update, SDR Console stopped working with the SDR-IQ. One symptom was that although SDR Console recognized that 
the SDR-IQ was plugged in, the program did not see the SDR-IQ's serial number. Investigation narrowed down the cause to Windows automatically 
replacing an old version of the FTDI driver ( with the latest version (2.12.14).

Attempts to solve the problem:
I tried uninstalling the latest FTDI driver and re-installing the older one. But this did not work. After much Googling to find out how to do it (discovering several snake oil methods on the way), I finally unearthed a method that does work.

How to replace newer driver version(s) with an older driver version:
This involves following the procedure at: https://technet.microsoft.com/en-us/library/cc730875.aspx


  1. Create a Restore Point (just in case things go wrong).
  2. Unplug all FTDI devices (including SDR-IQ) from the PC.
  3. Discover an instance of the FTDI driver, using the CLI command pnputil.exe -e . The output consists of a record for each driver, looking something like this:

    Published name : oem56.inf
    Driver package provider : FTDI
    Class : Universal Serial Bus controllers
    Driver date and version : 01/27/2014 2.12.00
    Signer name : Microsoft Windows Hardware 
    Compatibility Publisher

    Make a note of the "inf" reference # (in this case, 56).
  4. Delete the driver with the command pnputil.exe -f -d oem#.inf - for example pnputil.exe -f -d oem56.inf
  5. Repeat steps 3 and 4 until there is no FTDI driver left in the Windows Driver Store.
  6. Install version of the FTDI driver, from here:
    http://www.ftdichip.com/Drivers/CDM/CDM%20v2.10.00%20WHQL%20Certified.exe (a copy is also available here [link]).
  7. Prevent Windows 10 from automatically updating drivers:
    Settings > Control Panel > System > Advanced System Settings > Hardware >Device Installation Settings > No (your device might not work as expected) > Save
  8. Create another Restore Point (so that you can revert to v2.10.0.0 if necessary).
  9. Reboot the PC.

In my case I discovered no fewer than three instances of the FTDI driver. This was totally unexpected, and it was not until I had removed 
all three that I successfully installed the older version of the driver.

Now SDR Console v3/0807 and v2/2381 finally work (very well) on my system -- I have been bereft and inconsolable without them!

Bottom line #1: Do not rely on Windows Device Manager to uninstall a driver. There may be other versions still lurking in the Driver Store.

Bottom line #2: Do not rely on Device Manager showing all the COM ports installed on the system. For example, it does not show VSPE virtual ports.

Bottom line #3: Simon, your mission, should you choose to accept it, is to make SDR Console play with the latest FTDI driver :-)