Software Defined Radio, DAB, FM and much more


To operate Software Defined Radio one obviously needs both software and hardware. My interest is in developing software and I am the happy owner of SDRplay, Hackrf, RT2832 based DABsticks and AIRspy devices, more than enough to keep me busy.

The SDRplay device has the advantage of supporting a frequency range starting at app 100 kHz without having to perform tricks, so for shortwave reception it is for me the device of choice. The HACKrf starts at 1 Mhz, so that is also usable on shortwave. Other devices support frequencies between say 50 Mhz and 2000 Mhz, bands with interesting broadcasts and service transmissions.

The Hackrf device furthermore supports both reception and transmission on frequencies to 6 GHz, while a limitation on the AIRspy is that it only provides a limited number of sample rates. For e.g. DAB decoding an additional rate conversion is required.

Further differences between the devices is in the number of output bits, while DABsticks and HACKrf deliver I/Q samples of 8 bits, the SDRplay delivers 12 to 14 bits I/Q samples (depending on the chosen model).

Receiving DAB Fm Reception-2 Spectrum viewer cw decoder

There is an enormous amount of software already available for SDR applications, For me, it is just fun, however, to write and develop my own programs for this domain. One of the major gains in writing one's own software is (given that one has a sufficient amount of time since it requires lots of code) that it really deepens the understanding of elements in the domain and it definitely contributes to the further development of the programming skills.

After retirement, I actually did have spare time. Starting with some simple software for rtty and psk decoding on shortwave using an "Elektor" card as "hardware" device, the software soon included FM reception (using a PMsdr device), followed by some DAB software (DABstick and SDRplay) and a decoder for DRM (Digital Radio Mondiale), transmitted on shortwave. It evolved into the current series of programs for looking at the various bands, decoding some signals and listening to and analyzing radio transmissions.

Most of the programs support all mentioned device types, SDRplay, AIRspy, HACKrf and DABsticks; exceptions being the swradio-8 program which - since it aims at shortwave reception - takes the SDRplay device as input device and the sdrplayDab program, a DAB decoder more tightly integrated with the SDRplay software.

The programs are:

  1. a program for showing spectra (spectrumViewer);
  2. some programs for decoding FM transmissions (fmReceiver, wfm-rpi and xxx-radio);
  3. a program for decoding some amateur modes, wheatherfax and DRM on shortwave (swradio-8);
  4. some programs for decoding DAB transmissions (qt-dab, sdrplayDab, dabradio);
  5. DAB library, with some command line based example programs;
  6. some other programs, discussed later on

While my development platform is Linux, it is clear that for programs to be useful, they should be available for Windows as well. Happily, the Linux platform I am on, fully supports the mingw32 cross compiler environment, so it was/is relatively easy to cross compile all software and make it available under Windows.

For all this software, sources are available from github; the qt-dab respository contains in its releases section a zipped windows folder ( with all Windows executables (together with libraries that are required).

To overcome the problem of differences in different Linux distributions for PC's, for some of the programs, AppImages are made. An AppImage is a file containing the executable and most of the required dynamic link libraries (see "" for details). The basic idea is that such a file is downloaded, the exec bit is set and the program can run.

The RPI (2 and up) are popular devices, and since "Stretch" is a real and full Linux distro, it is straightforward to build an executable for the above mentioned programs on such a device. From time to time I create an AppImage for Qt-DAB for Stretch on the RPI2/3.

Some programs in detail

A description of the program(set)s is quite lengthy and the programs are quite different, that is why one just might select a description. For each of the programs it holds that there are sources available for use under Linux, and for many of them precompiled executables are available for use under Windows.

DAB programs.

DAB is being pushed as the replacement of FM broadcast, it operates in most countries in the "old" TV Band III (somewhere between 170 and 230 Mhz). In my local environment I receive - with an indoor telescope antenna - 4 ensembles with over 40 services (most of them for me not worth listening though). From a technical point of view, DAB, being digital radio, is quite interesting and I made different versions of a DAB decoding program, three with, others without a GUI. In this section the programs with GUI are described.

Receiving DAB Receiving DAB Receiving DAB

The picture on the left, dabradio is the simple version, just start the program, select a service and listen. The one on the middle, Qt-DAB, is the most extended one, and the picture shows that the HACKrf device is used as input device. The one on the right, sdrplayDab, is similar to Qt-DAB, but for use solely with SDRplay devices.

The first two programs support - if so configured - the SDRplay, the AIRspy and rtlsdr based DABsticks as input device. As the picture shows, the Qt-DAB program can be configured to accept input from an HACKRF device and furthermore, it is standard configured for input from a file, both a "raw" file (".iq" or ".raw", 8 bit I/Q samples) as produced by e.g. osmocom tools or an "sdr" file (a ".wav" file) generated by the Qt-DAB program.

The sdrplayDab program also takes ".sdr" files as input, however, due to a different architecture of the front end, only those generated by the sdrplayDab program itself.

The repositories qt-dab , sdrplayDab and dabradio contain all sources and further descriptions of these programs.

For Qt-DAB and dabradio so-called AppImages are available as well. For such an AppImage to run, one should have the library for the device of choice installed (most modern distros do have the rtlsdr library in the repositories, the driver for the SDRplay devices can be downloaded from, the AppImage itself contains all further dependencies. Running is then simply setting the exec bit on the AppImage and executing the file.

For Windows, a "zip-file" ( is available, a folder compressed in "zip" format, with the executables of these (and other) programs and the required DLL's.

This file and an AppImage for Qt-DAB are available in the releases section of the Qt-DAB repository.

An Appimage for dabradio is available in the repository (releases) section of the dabradio repository. The Windows executable of dabradio is in the aforementioned zipped folder.

The Windows version provides additional support for selected devices with an Extio plugin dll, tested with plugins for the SDRPlay and rtlsdr based DABsticks.

The main differences between the various versions is the amount of buttons and selectors. By dabradio there are only a few, Qt-DAB has an abundant amount with which selections can be made and aspects of the signal can be made visible. Things like TII recognition are implemented in Qt-DAB (and sdrplayDab), but missing is dabradio. The same for showing a spectrum.

Other implementations

Just as a programming exercise - and to (re-)gain some experience with the languages - the core of the C++ implementation was recoded in both Ada and Java. Both implementations are functioning and provide more or less the same functionality as dabradio. Both programs make use of a number of "native" (i.e. "C") libraries. gnat, the compiler used for the Ada version, is part of the gcc ecosystem, making it relatively easy to bind to C libraries, in Java it is more complex - and it is far less portable - to handle "native" libraries.

javaDab adaDab

The sources are to be found in the github repositories for JavaProject , and ada-dab .

While both programs are functioning, making them was merely an exercise and the programs are not actively maintained. Feel free to adapt, modify and extend. A reasonably extended implementation description of ada-dab is contained in the repository.

Command line versions: the DAB library

In order to create a command line version for DAB processing, a library was created with entries to the functionality to process DAB and DAB+. The sources can be compiled into a shareable library, or they can be included in an application. The sources for the library, as well as the sources for a number of example programs are to be found in the github repository here.

Examples of the use of this library, some (sources for) example programs are provided for in subdirectories (each directory contains a CMakeLists.txt file that can be used to create an executable).

  1. Example 1 implements a simple command line version, using a precompiled library. In the configuration phase one has to select the device to be used;

  2. Example 2 implements a simple command line version, using the sources of the library. In the configuration phase one has to select the device to be used;

  3. Example 3 is based on example 2, it differs from example 2 in that the PCM output is now being sent to stdout rather than using portaudio to control a soundcard;

  4. Example 4 is based on example 2, it differs from example 2 in that the raw MP2 or aac data (depending on the service selected) is being sent to stdout rather than to an MP2 resp. AAC decoder;

  5. Example 5 implements the functionality of example 2, with as addition the possibility of selecting the "next" service in the channel;

  6. Example 6 implements a version with an internet interface. Commands to select a channel, set the gain of the device (on a scale from 1 .. 100) and select a service can be given through an IP port, some data (i.e. the names of the services in an ensemble) are passed back. The code for the example contains a "mini" client implemented using Qt.

  7. The Python example implements a simple command line version using Python 3. A Python API layer is created implementing a library with a Python binding to DAB handling functionality. This Python API together with the library sources are made into a separately compiled library and references from with the Python program.

  8. The dab-scanner example implements a simple scanner over the selected band (default Band III). It collects the data of the ensembles and the services and prints that out, if selected to a file, otherwise to stderr. The resulting file can be viewed in e.g. LibreOffice Calc.

    dab scanner

A typical command line for e.g. the Example 2 program, configured to run with an SDRplay device is

./linux/dab-sdrplay-2 -M 1 -B "BAND III" -C 12C -P "Radio 4" -G 40 -A default

In this example Mode 1 is selected explicitly, which happens to be the default one. VHF Band III is selected, which also happens to be the default one, channel 12 C is selected, and in that channel the program "Radio 4". The Gain for the input device is set to 40 (on a scale from 1 .. 100), and as output device "default" is chosen (which, almost obviously, happens to be the default one).

The example programs - although all functioning quite well - are merely meant to show the usage of the library (or its sources) and are hopefully a source of inspiration, rather than complete implementations. Use your own imagination to adapt and extend.


The swradio-8 program is used to "listen" to frequencies on the "shortwave" bands, it takes the SDRplay (all models) as input device and it implements half a dozen decoders. While there are no decoders specific to signals in the higher bands the covered frequency range is only determined by the device and with the SDRplay allows access to frequencies up to 2 GHz.

Shortwave Radio

The software is a (partial) rewrite and simplification of the sdr-j-sw software, the latter, still available on github, supports more decoders and input devices than this one, but is more complex to build and to use.

The swradio-8 assumes that the interesting signals are small-band. The inputrate of the SDRplay is set to just over 2M, and decimated (and filtered) to a rate of 96000. The software will then select a band with a width of 12K, based on the user's frequency selection, and filter it out and decimate the samplerate to 12K. The user then can select a subband (usb, lsb, AM, wide) to be send to the selected decoder, the decoder will - if required - do further filtering.

SW Reception

Implemented decoders are:

  1. An AM decoder,
  2. a decoder for USB and LSB
  3. an rtty decoder,
  4. a psk decoder,
  5. a CW decoder,
  6. a weather-fax decoder,
  7. an AMTOR (Navtex) decoder,
  8. a MFSK decoder,
  9. and a DRM decoder (only 10K and smaller) for DRM broadcast transmissions (see picture).

The bandwidth for the decoder can be set to AM (9 kHz), wide, for DRM (12 kHz), USB (2.5 kHz) or LSB (2.5 kHz). Using the right mouse button on any of the two "scopes", the view is switched between "spectrm view" and "waterfall view".

On the 7 and 14 MHz band there are plenty of CW and psk calls. The 3855 Khz frequency is often used by me to receive weatherfaxes, the coastguard sends regularly messages in Amtor format on 518 Khz. DRM transmissions are rather scarce, the transmissions of Kuwait and Nigeria are well received here.

To aid in finetuning for psk decoding and cw decoding, the control widget for those decoders show as waterfall a very small band around the received frequency. Correction of the frequency is possible by clicking the mouse on this "waterfall" widget.

SW Reception

A program list is maintained between program invocations, selecting a program on the list is just by clicking the mouse on the selected program. The GUI contains a button with which a frequency can be saved and stored in the list. The main GUI contains a button for storing the currently selected frequency in this program list.

For use under Linux, one might want to download an AppImage from the releases section in this repository from github. The AppImage is "ready to run" (after downloading and setting the exec bit of course), one only needs to have installed the support library for the SDRplay (the library can be downloaded from

The README in the repository is quite extended.

The implementation of the DRM decoder depends on the use of a special version of the faad library, since faad 2.8 this specialized version is standard available.

The Windows version is included in the aforementioned "zip" file, maintained in the releases section of the Qt-DAB repository, the sources are in the aforementioned repository.

WFM-RPI software

The WFM-RPI software is the implementation of a simple (W)FM decoder, compiled for use with radio devices as SDRplay, AIRspy and/or DABsticks (depending on the configuration). The software runs under Windows (precompiled version configured for all three devices mentioned) and under Linux. The sources are to be found on the github repository.

The program(s) support decoding FM transmissions in mono and stereo and support RDS decoding (obviously, the frequencies to be received depend on the radio device connected).

A program list, a list of known programs with their frequencies, is maintained between invocations.

Fm Reception

Tooltips tell the function of the various buttons and sliders.

A general (W)FM decoder

The more general sdr-j-fm software contains more elements, the GUI shows the spectrum of the incoming signal as well as the spectrum of the decoded signal.

Fm Reception-2

This version supports - under Linux - next to the SDRPlay, the AIRspy, DABsticks, HACKrf and a soundcard, the sw-elad-s1, to be used with a downconverter. Note that the program is - especially when running Windows - quite resource hungry.

While an executable for Windows is in the aforementioned zip file as maintained in the releases section of the Qt-DAB repository, the sources can be downloaded from github .

A command-line (W)FM decoder

For experimental purposes a simple command line based version of the FM software was created. The software sends it output to stdout or to a selected file, rather than to a soundcard. It can be used e.g. to listen to mono or stereo transmissions, or to see what is happening on the P2000 band on 169650 kHz. It is modelled after the - excellent - fm software in the osmocon site for DABsticks.

Receiving P2000

sdrplay_radio -f 169650000 [-p3] |multimon-ng -a FLEX -t raw /dev/stdin

To listen to an FM transmission (the only classical station in the Netherlands on FM)

sdrplay-radio -f 94700000 -g 30 -M fm-stereo -D -Z |aplay -r 22050 -f S16_LE -t raw -c 2 

Since the osmocom site has an excellent version of rtl_fm, the version here can only be configured for the SDRplay or the AIRspy.

The sources for the xxx-radio are to be found at the github repository . An executable can be configured with either an AIRspy or an SDRplay device as "radio" device.


The spectrumviewer program just shows the spectrum, up to the selected bandwidth determined by the selected samplerate. The spectrumviewer software can be configured with the SDRplay, the AIRspy, the HACKRF and DABsticks.

Spectrum viewer

Operation of the spectrumviewer software is straightforward, tooltips tell the function of the various buttons and sliders.

The spectrumviewer will open a device that is configured and connected, in case of more devices are configures, it just opens the first one that is connected.

A frequency can be selected by entering the number in the keypad, terminating it with either MHz (for interpreting the number as the frequency in MHz) or kHz (for interpreting the number as the frequency in kHz). A scanning function is implemented with which it is possible to look at a wide range of frequencies.

The program shows both a spectrum and a waterfall, here over a range of frequencies in the FM broadcast band.

Since the input is usually wideband, up to 8 or 10 MHz, a decimator is part of the program, where the decimation rate can be selected. For e.g. an input signal with a width of 8 Mhz, decimation with a factor 100 gives a signal width of 80 Khz, making smaller band signals visible.

The "set scan" selector starts (or stops) scanning though the frequencies The 4 selectors to the left of the "set scan" button determine the frequency range, the stepsize and the rate at which the frequency change will occur.

The precompiled Windows executable is to be found in the zipped folder available on the github repository for Qt-DAB . The sources are to be found in the repository.

Other software

qt-1090 software

The popular dump1090 software (Copyrights Salvatore Sanfilipo) to keep track on planes is tightly integrated with software for rtlsdr devices and lacks support for the SDRplay and the HACKRF devices. So, some reconstruction was done to create a separation between "device" and "algorithm", and at the same time a kind of GUI was added.


The current version is 0.8: while it is definitely running, it is still an experimental version and does not have all of its final functionality. In the aforementioned zipped folder, a windows version is included.

Unfortunately, it seems that the free access to the maps API is restricted and - since end of june 2018 - one needs to register and - in some cases - one seems to have to pay for the usage of the API.

The sources, for compilation under Linux, are in their own repository . In the configuration file,, one can select or deselect the devices supported. The program, when started, will sequence through a (short) list to open one of the configured devices.

An rtlsdr emulator

Many interesting software packages for (sole) use with an RTLSDR compatible device exist and are available, dump1090 and acarsdec are typical examples. It would be interesting to have these programs and be able to use them with other devices, e.g. the SDRplay RSP. The acarsdec software was extended by me with an option to use the SDRplay, and a derived version of dump1090 was written with a small GUI and support for the SDRplay (the above mentioned qt-1090 program).

There are, however, other programs as well, e.g. rtl_433, aiswatcher etc. that are interesting and, somehow, tightly bound to the use of an rtlsdr compatible stick. I realized that it would be easier to write an rtlsdr emulator using the SDRPlay device than rewriting all software that I encountered and works only (primarily) with a DABstick. That lead to the development of the rtlsdr emulator for the SDRplay. Implemented as a plugin replacement for the rtlsdr library, either for Linux ( or windows ([lib]rtlsdr.dll).

The sources of the library can be found in the github repository . Operation of the emulator is simple, it is just a replacement of "" under Linux or (lib)rtlsdr.dll under windows (it is assumed that you have the SDRplay lib installed).

In my environment the emulator works fine with both dump1090 (although qt-1090 has a better performance), acarsdec, rtl_433 and others, and on my development laptop the "standard" is replaced by the emulating one. The aforementioned contains an "rtlsdr.dll-fake" that can be used (after renaming of course) instead of the real "rtlsdr.dll" lib.

Filter demo.

Modern radio devices deliver a wideband signal (e.g. the SDRplay up to 10 Mhz, the hackrf to up to 20Mhz). While it is nice to be able to show the spectrum of e.g. half the FM broadcast band in a single view, for decoding a dignal a smaller band is usually needed. As an example, the band width for decoding a psk31 mode signal or a cw signal is less than 100 Hz. The sw software takes as input from the SDRplay a signal with a width of just over 2 MHz (the smallest possible), and (filters and) decimates that to 96 Khz. Then, depending on the user selected frequency, a subband of 12 Khz is selected (and filtered out) and made available for decoding at a rate of 12 Khz. The user may select a subband of 12, 9, 2.5 Khz (upper or lower sideband) to be handled by the decoder. The latter will further filter the signal as required.

All these filterings are done by Finite Impulse Response filters, some with a pretty high degree to obtain steep flanks (a degree of 255 is no exception, although then implemented using a FFT). FIR is chosen over IIR since FIR does not destroy the phase of the signal.

The pictures all show a filter with a degree 64 and a width of 0.33 (in the range 0 .. 100, i.e. for a signal with a sampling rate of 96000, this would mean 0.33 * 96000 / 2, i.e. 16Khz). So the pictures show a low pass filter with a 3DB point at 16 Khz. The pictures differ in the windowing applied.

filter-1 filter-2 filter-3 filter-4

The sources of the program can be found in the github repository .

Documents ..

Since my interest is primarily in programming, I'm less interested in writing manuals (that no one ever reads anyway), so manuals are pretty much absent. The programs that are equipped with a GUI have tooltips, telling the function of the GUI elements. For the others, read the README and the CMakeLists.txt and/or the file. The repository for dab-cmdline contains a fairly extensive README.

There are some documents though, an informal description of the synchronization in the DRM decoder is given in this description. The document will be a draft forever, but it contains quite some practical information on issues encountered in writing the software (one of the decoders for the sw-radio-8 program) for decoding the DRM signal.

A description - also informal - of processing of DAB and DAB+, as implemented in the Ada version of the software, is given here. This (also eternal draft) report describes in quite some detail - including a number of code fragments - how the Ada version of the DAB software is built up. The description presumes some basic knowledge on Ada and on the structure of DAB and DAB+.

For those interested in really old stuff that has nothing to do with Software Defined radio, this repository contains (sources for) an algol 60 to C translator, with a number of example programs. The program was written in plain C around 2002, also as a hobby project at that time. A manual, contained in the repository, gives - in about 20 examples - in quite some detail the mapping between Algol 60 constructs and the resulting plain C code. Actually, it works pretty well on my x64 based laptop.

Finally ....

In creating this software, existing dynamic libraries (linux) and dll's (windows) were used, e.g. libraries for audio output, fft, handling "wav" files, all available under a GPL-V2 or V3. So the software is itself also made available under a GPL-V2 licence.

It is - obviously - nice if the software is useful, but there are no warrantees. As the license states:
SDR-J is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

Suggestions for improving or extending the software are always welcome, as are (material) contributions.

I am grateful to SDRplay ltd for providing me the possibility to use different versions of the SDRplay RSP devices, all wonderful devices. Furthermore, thanks to Benjamin Vernoux for making an AIRSPY device and Great Scott Gadgets for making an HACKRF device available to me.

Have Fun!!!

Pijnacker, November 2018
Jan van Katwijk
Lazy Chair Computing