We have produced two new video guides which describe the use of the Frequency Scanner and I/Q Output functions: This release of SDRuno uses a new version of the Windows Service based API (3.02) and so users that also used other applications such as dump1090 and HDSDR with the previous version of the Windows Service based API (3.01) will need to download and install the latest versions of API, dump1090 and the ExtIO plugin from our website at

I/Q → Audio Output (for CW Skimmer for example)įor a full list of additions/changes and bug fixes, please see the release notes at:.

Frequency Scanning (for both frequency ranges and stored memory panel lists).

Major new features of SDRuno V1.3 include: Creating, sharing and storing your own preferred set of frequencies for scanning is straightforward too. It can store found signals, has a number of built in pre-sets (including the marine and air-bands) and has the ability to both wait on signal and hold for a period of time on a signal. The scanner has 2 modes it can scan an arbitrary frequency range with a defined raster or it can scan through a list of frequencies from the memory panel. The introduction of a fast frequency scanner for SDRplay products has been greatly anticipated and this will make SDRuno the first fully featured SDR package with integrated frequency scanning. This is a major upgrade to SDRuno, which adds a number of important new features and is intended for all RSP models (RSP1, RSP1A, RSP2, RSP2pro and RSPduo) Reply to this email directly, view it on GitHub, or unsubscribe.SDRplay is pleased to announce the release of SDRuno v1.3.

You are receiving this because you are subscribed to this thread.

And the software stoping to receive signals shoult just not happen. Even having a workaround for this would be fine. However, I highly dislike having to restart my system to fix things. I can live with having to kill the sdrplay_apiService process once in a while. I discovered this while trying to record some POCSAC messages over night. SDR++ disengages and there is no error explaining why. Listening to the radio waves for an extended time, things just stops. There is no sdrplay_apiService process running and disconnecting and reconnecting the SDRPlay hardware does also not change anything. The only way to recover from this, is to reboot the system.

In that case the log shows Could not init RSP device: sdrplay_api_Fail. Sometimes that does not work and SDRPlay does not even show up as a source. This usually can be fixed by sending SIG TERM to the sdrplay_apiService process. When that happens, I can select the SDRPlay as a source but the device shows as unavailable (red text in SDR++). When starting SDR++, its console output shows Could not intiatialized the SDRplay API. I have several observations that might or might not be related. Using SDR++ on macOS 11.5.2 with an SDRPlay 1A.

Sdruno for mac