The problem: I remarked we have been spending a lot of time lately on problems that could be solved with much less effort if we all agree to adopt a minimum of discipline. As this mailing list grows, there will be less and less people interested in reading about problems they have already discussed, solved, and beaten to death in this same mailing list. Here's a quick reminder for everyone having problems with SDR software and computers. Unless you describe exactly what you are doing, in which context, with the exact hardware and software configuration, the odds of someone giving helpful advice are close to zero. The social media (and mailing lists) have the undesirable ability to amplify noise because there are naturally more people who have opinion than people who have actual knowledge. So please, read this post carefully. What do I do first? Use common sense. Determine if it is a support topic or a general discussion: Airspy Hardware related => Contact the support; Everything else goes to the list. For support related questions, prepare your list of "Steps to Reproduce" and send it by mail to The Support. For general discussion/best practices, try to avoid duplicates: Use the search bar to find an existing topic/answer/advice that solves your problem or improves your life. Don't jump on other's threads. Statistically, "Mee too" is never an actual "Mee Too". You are just making things difficult for all. Use separate threads for separate problems. A "segfault" has nothing to do with the noise from your Plasma TV or PC PSU. Try to keep the content technical. People from different cultures will read and ignore your untranslatable joke, but will definitely understand the tech stuff. How to report a problem: Steps to Reproduce Be precise Include exact data used during testing for easy reference, including hardware, OS and user software versions The steps have to be in the exact order Mention pre-requisites when applicable: Software dependencies, glibc, modified kernel, etc. Do not write composite steps. The devil is in the detail. Always recheck your steps to reproduce on a new system with the default configuration Make sure the sentences are short and unambiguous Thanks for reading to the end!

FMSuite 2.2 can be downloaded from http://www.freqmgrsuite.com/ using the link at the top right of the page. As always, feel free to email me or make a comment on the web site above if you have questions or issues. Special thanks to prog, jdow, and Edward McDonald for suggestions and directions, and to beta testers Ignacio, Paolo, and Edward for their valuable feedback. Change Log All Plugins Theming has been implemented where possible. Note that only Dark Mode / Light Mode settings are used, not individual colors, due to compatibility issues with some Microsoft controls. Improved the reliability of multitasking. Replaced obsolete or deprecated Microsoft features with current technology. Replaced icons and images that would have been invisible in Dark Mode themes. Fixed the case where permissions to file "FMSuiteException.txt" was denied. Replaced tab controls with radio buttons because theming is incompatible with Microsoft tab controls. All software was upgraded to the current Microsoft .NET Core 5 platform. Data Tools Upgraded the Data Tools Zip file processing to a built-in Microsoft function. Removed the "Custom" delimiter option and replaced it with the "Pipes" option due to reliability issues. Frequency Manager + Scanner Moved Scan Decisions and Frequency Data Display plugins out of Frequency Manager + Scanner and into their own plugins. Removed Scan Decisions and Frequency Data Display options from the Preferences dialog as they are now defunct. Removed the Automatic Frequency Rejection feature in favor of new features in SDR#. Fixed a case where the scanner could get stuck if the radio doesn't change frequency when requested. Changed the "Locked" or "Lock" labels to "Ignore", "Ignored", or "Ign" to remove confusion with the word "Lock" as used by hardware radio scanners. When scanning sometimes a radio will not tune to a requested frequency. To indicate this an error popup will appear and recommend actions. It is unclear whether this issue is caused in SDR# or in the radio.

(source files are included as an attacmement) Airspy HF+ and/or Discovery to WebSDR (working on RPi III B+ and RPi IV, not testing yet with other Linux distros) Step I Install drivers for Airspy for Linux/Raspberry Prerequisites for Linux (Debian/Ubuntu/Raspbian): (open a terminal and type) sudo apt-get install build-essential cmake libusb-1.0-0-dev pkg-config Build host software on Linux: (open a terminal and type) wget https://github.com/airspy/airspyhf/archive/master.zip unzip master.zip cd airspyhf-master mkdir build cd build cmake ../ -DINSTALL_UDEV_RULES=ON make sudo make install sudo ldconfig Clean CMake temporary files/dirs: (open a terminal and type) cd airspyhf-master/build rm -rf * Step II Make a no-ip address for your raspberry. Please refer to: http://sizious.com/2017/04/30/how-to-properly-install-no-ip-dynamic-update-client-duc-under-raspbian/ Step III Setting up an Apache server : (more info) https://www.raspberrypi.com/documentation/computers/remote-access.html#setting-up-an-apache-web-server Installing Apache First, update the available packages by typing the following command into the Terminal: sudo apt update Then, install the apache2 package with this command: sudo apt install apache2 -y Installing PHP for Apache To allow your Apache server to process PHP files, you’ll need to install the latest version of PHP and the PHP module for Apache. Type the following command to install these: sudo apt install php libapache2-mod-php -y Change port Apache Default port is 80. You can change it e.g. to 8900. This port will be used for changing the bands: sudo nano /etc/apache2/ports.conf Listen 8900 Then Ctl+X for exit and Y and Enter for saving Restart apache : sudo service apache2 restart Go to Raspberry, open a terminal and type and type: sudo chmod -R 777 /var/www/html . This will change permissions, so to save files into the folder. Go to the downloaded file. Find all files included in www/html and copy them all to /var/www/html Go to the folder /var/www/html and pickup a file to open with a text editor e.g. (for 80.php) echo shell_exec('touch 80.flag'); echo shell_exec('touch 80.cfg'); echo shell_exec('lynx -cmd_script=q 127.0.0.1:8901/restart.html'); header('Location: http://YOUR IP:PORT'); ?> Now change YOUR IP with the no-ip address you get (e.g. myaddres.no-ip.org) and port with 8900. Do the same to all php files included in this folder /var/www/html Don’t forget to open ports on router. You will need open the ports 8900 and 8901 Step IV Go to the downloaded file. Find the folder hfp_tcp-bas and copy it as it is to the home directory of Raspberry /home/pi Open a Terminal and type: cd /home/pi/hfp_tcp-bas make sudo make install Step V * The WebSDR server needs several libraries. Most of them will be installed by default by your Linux distribution, but two of them may not be, namely: libfftw3f (i.e., version 3 of the FFTW library, compiled for float) and libpng12 (i.e., version 1.2 of the PNG library). Usually they will be available through your distribution's package management system. In the case of Debian and Ubuntu, you can install them using the following command (as root): sudo apt-get install libfftw3-3 libpng12-0 Step VI Go to the downloaded file, find websdr folder and copy it as it is to /home/pi Open folder /home/pi/websdr/cfg Open websdrcfg.template and websdr.cfg and make the changes for the hostname, QTH, description, email, antenna information. “antenna” must also be changed to all files in the folder. These are the “bands”. You can make new, or use only the bands you want. Open folder /home/pi/websdr/dist11/pub2 Find the files index.html, websdr-controls, m.html - search YOUR IP and replace it with your no-ip address. After editing, copy index.html, and m.html to folder /home/pi/websdr/pub Step VI Go to the downloaded file, find files dongle and kill.server and copy them to /home/pi FINAL STEP Open a Terminal and type ./dongle . You will see the following: pi@raspberry:~ $ ./dongle rmmod: ERROR: Module dvb_usb_rtl_28xxu is not currently loaded rmmod: ERROR: Module dvb_usb_rtl28xxu is not c