Configuration and running

Notice for GNU radio 3.8 users

Due to an issue present in GNU radio 3.8, it is necessary to perform a workaround step to re-enable digital modes. You need to run the volk_profile command, and after it completes, inspect the file ~/.volk/volk_config in the /home directory. Locate the line starting with volk_8u_x4_conv_k7_r2_8u and ensure it ends with spiral spiral: volk_8u_x4_conv_k7_r2_8u spiral spiral. If it does not not, change it so it looks like this. After performing this step, digital modes should work again.

Operation guide


Please report any issues you have encountered using the Github bug tracker


The project has a discussion group at Github which can be used to discuss issues, request features and contact developers.


Is the packet radio system within QRadioLink compatible with other existing amateur packet radio modes and / or FM radios?
No, the packet radio modem is not compatible with FM radios and 1200 / 9600 baud amateur radio packet.
The receiver needs to be able to demodulate in a bandwidth of at least 1 MHz to receive this radio packet mode.
Furthermore, the Internet packet modes in QRadioLink do not even use the same data link layer. Instead of AX.25 frames, QRadioLink sends Ethernet frames over the air. This means that you do not need AX.25 Linux kernel support to create an IP link with QRadioLink. Also, both the 4FSK and DQPSK packet radio modes require a full duplex transceiver, or at least two devices (a semi-duplex transceiver and an RTL-SDR receiver for example).

I am trying to use the official Mumble server package, but it does not seem to work with QRadioLink
The best response I can come up with is that the official Mumble protocol reference possibly ommits some steps required to connect to the latest version of the official server. My Mumble client is written according to this document, but it uses the umurmur server package for this reason. Your help in resolving this issue is also welcome.

Why is there no Android APK for QRadioLink?
Because QRadioLink is not a native Android application and needs a GNU/Linux Android container and userspace. For this reason the user interface is rather clunky for a mobile device and needs a rewrite. You can expect that to happen once KDE Plasma mobile becomes stable. While the application is not native, the performance is similar to a native application, but there is some overhead from the visualisation layers, especially if you use a VNC display instead of an X server. For most modes, expect at least 50% CPU usage on 3-4 cores running at 1.2 GHz.

I am running QRadioLink on a very limited CPU power platform, what can I do?
The FFT and waterfall widgets are not active if you disable the FFT checkbox. No FFT is performed on the data by GNU radio and no UI painting is happening. When you switch FFT on, that code becomes active and the application takes a performance hit which is proportional to the sample rate, FFT size and the FPS. Reduce them to the minimum for lowest CPU demand. You should run volk_profile before running the application for optimization.

I have issues forwarding the VoIP digital audio to the radio and viceversa
If your SDR receives an FM or other analog signal there is no transcoding involved and the voice packets encoded with Opus are sent directly to connected clients. If your SDR receives a digital voice signal like Codec2, the audio is transcoded first before being sent to the VoIP network. Audio artefacts and delays may be present in this case.

Can QRadioLink be used headless (with no graphical user interface on the Raspberry Pi?
Yes, starting with version 0.8.2, QRadioLink can be used as a terminal application (possibly daemonized) without X11 or any screens. Remote operation in this case is possible either via commands sent through Mumble as private messages, or via the embedded telnet server, for which you will need a telnet client or similar application to connect with. No authentication or security features are implemented at the moment, so you should not expose the configured remote port to the Internet and instead use SSH to connect to the system and telnet from there. If you are not using local audio, you will need to also enable VOIP forwarding.

Is there a Windows version?
No. QRadioLink only works on Linux systems at the moment. However, it is not impossible to port to the Windows operating system if someone is interested to do the work, with only a few parts that are very Linux specific (including some calls into Linux kernel API). However, Windows users should keep in mind that QRadioLink is a very simple educational tool for hobbyist and learning users and cannot achieve or even wants to achieve what professional SDR applications can perform on Windows. To avoid disappointment, I am recommending some professional products with first grade suppport for the Windows OS: FlexRadio SmartSDR and SDRConsole.