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!

A few problems have arisen when some people install and use FMSuite v2.3. To aid in troubleshooting, please note these and ensure that they are not the cause of any issues you are having. Also refer to the Troubleshooting section of the User’s Guides. First off, *DO NOT INSTALL DOWNLOADED FMSUITE INTO THE COMMUNITY VERSION OF SDR#*. Sorry to shout but people aren't reading the installation instructions. Wait for CE to provide the newest version of FMSuite. *Problem: You see an error message regarding opening a database.* *Causes* : * Windows often blocks applications downloaded from the internet. When installing the software did you perform step 4 under “New Installation” in the Read Me First document? If not, delete the FMSuite folder and start over with a new installation and be sure to follow the instructions closely to remove the Windows block. * The database file may be in use by Windows or by some other program (anti-virus, backup program, etc.) Reboot your computer and try to start SDR# again. * The FMSuite folder contains a subfolder named “x86”. Some people mistakenly delete that folder thinking that since they are running 64-bit Windows the x86 folder is not needed, but that is not the case; it is required. Do not delete anything from the FMSuite folder. *Problem* : *SDR# loads properly after installing FMSuite, but you can’t see its plugins in the SDR# “hamburger” menu.* *Cause* : SDR# now has all third-party plugins in a submenu named “Plugins”. Look there for FMSuite plugins. *Problem* : *SDR# crashes when started. One or more error messages related to FMSuite are displayed.* *Cause* : One cause is the installation of FMSuite v2.3 into the Community Plugins package by Rodrigo Pérez, which already contains FMSuite v2.2. As stated in the Read Me First document, do not install FMSuite into the Community plugins package. *Problem: Using the Data Tools Wizard, importing a generic file fails with the error message “Line X has less than 35 columns”.* *Cause* : The documentation for importing generic files did not get updated for that 35 th column. In your generic file, add another value at the end of each row. It is named “SpectrumDisplay” and you can add the data “,0” (without quotes and with a zero). The documentation has been corrected. I apologize for any confusion. *Problem* : *Descriptions of frequencies on the spectrum no longer works.* *Cause* : As described in the User’s Guide, a new feature is the ability to selectively show some frequencies’ descriptions using the Edit window to checkmark that option. In other words you have to enable "Show descriptions of frequencies on the spectrum" in Preferences and then mark every frequency whose description you want to see using the Edit window. You may use the Bulk Edit feature of the Browse window to enable multiple frequencies at once. As always feel free to email me at sdrs.freqmgr [at] cox.net with questions or problems. Thanks for trying my software. 73, Jeff N8GJL

Can your plugin scan a list of specific frequencies in addition to a range of frequencies? Thanks, George

Anyone help? There use to be on the web a site for identifying radio signals I believe it was complied by someone called Sigi It showed in graphic form various traces of transmission with explanatory notes I have looked but cannot come across it Anyone can help !?

What does it do? Bote Man <http://www.botecomm.com/bote/radio/streaming.html> http://www.botecomm.com/bote/radio/streaming.html Sent: Wednesday, 4 May, 2022 22:39 To: airspy@groups.io Subject: [airspy] [MOD] install-rtlsdr.bat but with Keenerds RTL-SDR Driver and a more recent Zadig version Usage: just extract it in SDR# folder replacing the older file and run it as always. Attachments: * install-rtlsdr.7z <https://groups.io/g/airspy/attachment/43299/0>

NEW DX101 VIDEO: Using Airspy's Co-Channel Canceller to Get More DX! (on AM AND FM!): https://youtu.be/Rk_0LMFAquk Premieres Monday at 6pm CDT! 73, Loyd Van Horn - W4LVH DX Central dxcentralonline.com youtube.com/@DXCentral

FMSuite 2.3.4 can be downloaded from http://www.freqmgrsuite.com/. As always, feel free to email me or make a comment on that web site if you have questions or issues. Known Issues • There is an issue in displaying some of the FMSuite plugins immediately after they are enabled in SDR#. Controls may be displayed out of position, overlaying other controls, or otherwise “mangled”. If this happens, simply restart SDR# and the plugins should be displayed correctly. This will be corrected in a future version of FMSuite. • In the Data Tools Wizard, the download URLs for most of the online databases are out of date. When downloading online databases, enter the correct URLs for them in the supplied field. This will be corrected in a future version of FMSuite. • The Frequency Data Display is not working at this time. This will be corrected in a future version of FMSuite. • The Scanner Activity Logger is making multiple entries under some conditions. This will be corrected in a future version of FMSuite. I'm having many challenges working on FMSuite as my new PC is randomly crashing several times per hour. Indicators seem to point to the Intel CPU and I'm seeing others on the Web having the same problem. -Jeff

I apologize if this is a dumb question but I cannot find a way to automatically save the setup information in vs 1920. When I shut down SDR# and restart it goes back to the original start screen, remembers nothing, not even the HF+ I am using. Thanks all. Keith

Below is from the Airspy website for the HF+ Discovery. What are the sensitivity specs for the R2? I just didn't see them listed on the R2 product page. How will the Ranger compare with the Discovery in this regard? Thanks, George

Hi, Really enjoy my HF+, (anxiously awaiting for the release of the Ranger), but was wondering if there is any way (assuming it's even legal) to use SDR# with an Icom R-8600 Would love to see the radio's screen on a pc monitor, and, perhaps, even control some of the radio's functions. Bob

I'm playing with a new voice activity detection (VAD) algo to complement SDR#'s NINR. You can try it in the next release candidate: https://airspy.com/downloads/sdrsharp-x86-next.zip

Hello, I'm having some trouble getting the spyserver to run on my pi. I had it running on the BBB but the audio was always choppy. $ uname -a Linux rpi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux If I try to run the current aarch64 spyserver binary, I get the file not found error. $ ./spyserver -bash: ./spyserver: No such file or directory $ file spyserver spyserver: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, BuildID[sha1]=2aa3e83f756adfc24d51d2e369dca82d113a78e8, for GNU/Linux 3.7.0, stripped I went down the docker path but that doesn't seem to fix the error either, the container crashes with an error indicating the server couldn't execute. Perhaps the one I tried (on github) still didn't target the correct glibc..? $ docker logs spyserver ./entrypoint.sh: line 24: /usr/bin/spyserver: cannot execute: required file not found ./entrypoint.sh: line 24: /usr/bin/spyserver: cannot execute: required file not found -- repeats forever as the container is restarted -- So what I would really like is the source so I can build the program directly on the pi. I don't mind pitching in on any updates that may be necessary for running on the modern rpi. Maybe it's just a re-compile against the newer gcc / glibc??? Thanks, -- Nick (AI6NN)

As seen in the video in the google drive link the discovery produces a spike 5 kHz up when tuning. It is the same either up or down. Mouse scrolling or manually clicking. The spike is smaller when manually change the frequency. It is there in AM, NFM, WFM modes. It starts at 64 MHz and stops at 118 MHz. Is it something to do with the bandpass filter as it is the same span? It does not matter if the antenna is connected or not. I have tested several USB-cables incl the original cable. Also tested an older clean SDR# 1919 version. The discovery has the latest firmware 4.0.8. That spike is mostly disturbing when scanning due to it will have false stops. The local frequencies I listen to here is mostly between 69-87 MHz and 140 - 173 MHz. And every time the scanning come back to 69 MHz the spike often result in false stops until it has passed. Is it possible to fix somehow or is it hardware related due to the bandpass filter? https://drive.google.com/file/d/1e5jYRxqa1pRxl89MJ33VEI1OVjzJugbT/view?usp=sharing

Hi all Prog what is the changes in spyserver Noticed its a different size ? is there a 'change log' to see these changes ? > instead of filling this area up HAGO Bear