welle.io

Linux (Travis):
Windows (AppVeyor):

This repository contains the implementation of an SDR DAB/DAB+ receiver.
Please see the project website https://www.welle.io for a user oriented documentation.

welle.io is a fork from dab-rpi and sdr-j-dab which is now qt-dab https://github.com/JvanKatwijk/qt-dab.

Download
Usage
Supported Hardware
Building
welle-cli
Limitations
Development

Download

Stable release can be found here:

If you discovered an issue please open a new issue.

welle.io is under heavy development. You can also try the latest developer builds. But PLEASE BE WARNED the builds are automatically created and untested.

welle.io nightly builds

To use it on macOS or on a Raspberry Pi you have to compile welle.io directly from the sources. See below for more information.

Usage

The command-line parameters are:

Parameter	Description
-h, --help	Show help
-v, --version	Show version
--dump-file	Records DAB frames (.mp2) or DAB+ superframes with RS coding (.dab). This file can be used to analyse X-PAD data with XPADxpert (https://www.basicmaster.de/xpadxpert).
--log-file	Log file name. Redirects all log output texts to a file.

Supported Hardware

The following SDR devices are supported

Airspy R2 and Airspy Mini (http://airspy.com/)
rtl-sdr (http://osmocom.org/projects/sdr/wiki/rtl-sdr)
rtl_tcp (http://osmocom.org/projects/sdr/wiki/rtl-sdr#rtl_tcp)
I/Q RAW file (https://www.welle.io/devices/rawfile)
All SDR-devices that are supported by SoapySDR, gr-osmosdr and uhd. These are too many devices to list them all. To see if your SDR is supported, have a look at the lists at SoapySDR and SoapyOsmo.
- Devices supported by gr-osmosdr are supported via SoapyOsmo
- Devices supported by uhd are supported via SoapyUHD
- One limitation is of course that the SDR devices must be tunable to the DAB+ frequencies.

SoapySDR Notes

LimeSDR

Connect the antenna to the RX1_W port and configured SoapySDR antenna option to LNAW. SoapySDRUtil --probe=driver=lime may show other possible options.

USRP

Configured SoapySDR driver arguments option to driver=uhd. Configure also antenna and clock source option. To list possible values for antenna and clock source use the command SoapySDRUtil --probe=driver=uhd.

Building

General Information

The following libraries and their development files are needed:

Qt 5.10 (Qt 5.9 and below is not supported)
FFTW3f
libfaad
librtlsdr
libusb

Ubuntu Linux 18.04 LTS

This section shows how to compile welle.io on Ubuntu 16.04 LTS and Ubuntu 18.04 LTS.

Install Qt 5.10 including the Qt Charts module by using the the "Qt Online Installer for Linux" https://www.qt.io/download-open-source/
Install the following packages

# sudo apt install libfaad-dev libmpg123-dev libmpg123-dev libfftw3-dev librtlsdr-dev libusb-1.0-0-dev mesa-common-dev libglu1-mesa-dev libpulse-dev libsoapysdr-dev libairspy-dev libmp3lame-dev

Clone welle.io

# git clone https://github.com/AlbrechtL/welle.io.git

Start Qt Creator and open the project file welle.io.pro inside the folder "welle.io".
Build welle.io
Run welle.io and enjoy it

Windows 10

A compiled version can be found at the release page

This sections shows how to compile welle.io on Windows 10. Windows 7 should also be possible but is not tested.

Install Qt 5.10 including the Qt Charts and mingw modules by using the the "Qt Online Installer for Windows" https://www.qt.io/download-open-source/
Clone welle.io https://github.com/AlbrechtL/welle.io.git e.g. by using TortoiseGit.
Clone the welle.io Windows libraries https://github.com/AlbrechtL/welle.io-win-libs.git.
Start Qt Creator and open the project file welle.io.pro inside the folder "welle.io".
Build welle.io
Run welle.io and enjoy it

macOS

To build for macOS, you have have several options: Either you install everything incl. dependencies manually (not covered here and not recommended) or use Homebrew or MacPorts.

Homebrew

Assuming that you have Homebrew installed, execute the following steps:

Use the welle.io repository as a "tap" (alternative package repository):

# brew tap AlbrechtL/welle_io https://github.com/AlbrechtL/welle.io

Install welle.io (and dependencies):

# brew install AlbrechtL/welle_io/welle.io

MacPorts

You can either use the welle.io port available in macports, or compile with QT Creator.

use welle.io port

This is the easiest way and will manage the dependencies for you. There are 3 variants all three being enabled by default. Each variant enables compilation with that specific input device library : "airspy" "rtlsdr" "soapysdr".

# sudo port install welle.io

With MacPorts, welle.io is installed as a bundle app in /Applications/MacPorts.

compile with QT Creator

You need to install the dependencies with MacPorts first, assuming you have MacPorts installed:

# sudo port install fftw-3-single faad2 rtl-sdr libusb mpg123 lame

Install Qt 5.10 with Qt Creator directly from Qt website, not through MacPorts.
Clone welle.io

# git clone https://github.com/AlbrechtL/welle.io.git

Open welle.io.pro with Qt Creator.
Make sure in Qt Creator, "Projects, Build&Run, Run" that the checkbox "Add build library path to DYLD..." is off.
Build and run.

CMake instead of Qt Creator (Windows, Linux, macOS)

As an alternative to Qt Creator, CMake can be used for building welle.io after installing dependencies and cloning the repository. On Linux, you can also use CMake to build welle-cli, the command-line backend testing tool that does not require Qt.

Create a build directory inside the repository and change into it

# mkdir build
# cd build

Run CMake. To enable support for RTL-SDR add the flag -DRTLSDR=1 (requires librtlsdr) and for SoapySDR add -DSOAPYSDR=1 (requires SoapySDR compiled with support for each desired hardware, e.g. UHD for Ettus USRP, LimeSDR, Airspy or HackRF). By default, CMake will build both welle-io and welle-cli. Use -DBUILD_WELLE_IO=OFF or -DBUILD_WELLE_CLI=OFF to compile only the one you need.

# cmake ..

or to enable support for both RTL-SDR and Soapy-SDR:

# cmake .. -DRTLSDR=1 -DSOAPYSDR=1

If you wish to use KISS FFT instead of FFTW (e.g. to compare performance), use -DKISS_FFT=ON.

Run make (or use the created project file depending on the selected generator)

# make

Install it (as super-user)

# make install

Run welle.io and enjoy it

Android

A compiled version of welle.io (APK file) can be found at at the Google Play store or at the release page.

welle.io uses the "RTL2832U driver" from Martin Marinov, to be found at the Google play store or at F-droid. Also see (sources or APK file). Please note that a recent version of this driver is needed (v3.06 or above), otherwise welle.io will not find your stick.

This sections shows how to compile welle.io for Android.

Install Qt 5.12 for Android including the Qt Charts and Qt Remote Objects modules by using the the "Qt Online Installer for Windows" https://www.qt.io/download-open-source/
Follow the side https://doc.qt.io/qt-5/androidgs.html to install the Android build enviroment
Clone welle.io https://github.com/AlbrechtL/welle.io.git

# git clone https://github.com/AlbrechtL/welle.io.git

Start Qt Creator and open the project file welle.io.pro inside the folder "welle.io".
Build welle.io
Run welle.io and enjoy it

Raspberry Pi 2 and 3

To build and run welle.io on a Raspberry Pi 2 and 3 with GPU acceleration, please read this guide.

welle-cli

If you compile welle-io with cmake you will also get an executable called welle-cli which stands for welle-io command line interface.

Usage of welle-cli

Receive using RTLSDR, and play with ALSA:

welle-cli -c channel -p programme

Read an IQ file and play with ALSA: (IQ file format is u8, unless the file ends with FORMAT.iq)

welle-cli -f file -p programme

Use -D to dump FIC and all programmes to files:

welle-cli -c channel -D

Use -w to enable webserver, decode a programme on demand:

welle-cli -c channel -w port

Use -Dw to enable webserver, decode all programmes:

welle-cli -c channel -Dw port

Use -C 1 -w to enable webserver, decode programmes one by one in a carousel. Use -C N -w to enable webserver, decode programmes N by N in a carousel. This is useful if your machine cannot decode all programmes simultaneously, but you still want to get an overview of the ensemble. By default welle-cli will switch every 10 seconds. With the -P option, welle-cli will switch once DLS and a slide were decoded, staying at most for 80 seconds on a given programme.

welle-cli -c channel -C 1 -w port
welle-cli -c channel -PC 1 -w port

Example: welle-cli -c 12A -C 1 -w 7979 enables the webserver on channel 12A, please then go to http://localhost:7979/ where you can observe all necessary details for every service ID in the ensemble, see the slideshows, stream the audio (by clicking on the Play-Button), check spectrum, constellation, TII information and CIR peak diagramme.

Backend options

-u disable coarse corrector, for receivers who have a low frequency offset.

Use -t [test_number] to run a test. To understand what the tests do, please see source code.

Examples:

welle-cli -c 10B -p GRRIF
welle-cli -f ./ofdm.iq -p GRRIF
welle-cli -f ./ofdm.iq -t 1

Limitations

Windows 8 and older are not offically supported

Development

You can join the welle.io development. Please visit the wiki to find more information.

Profiling

If you build with cmake and add -DPROFILING=ON, welle-io will generate a few .csv files and a graphviz .dot file that can be used to analyse and understand which parts of the backend use CPU resources. Use dot -Tpdf profiling.dot > profiling.pdf to generate a graph visualisation. Search source code for the PROFILE() macro to see where the profiling marks are placed.

ioerror/welle.io