SDRangel server

Starting with version 4 (v4.0.0) it is a fully implemented feature with support of nearly all plugins:

• Channel Rx: AM, BFM, DSD, NFM, SSB, WFM demodulators and UDP source.
• Channel Tx: AM, ATV, NFM, SSB, WFM modulators and UDP sink.
• Sample sources: Airspy, AirspyHF, BladeRF, FCDPro, FCDPro+, File source, HackRF, LimeSDR, Perseus, PlutoSDR, RTL-SDR, SDRdaemon, SDRPlay, Test source (that's all of them)
• Sample sinks: BladeRF, File sink, HackRF, LimeSDR, PlutoSDR, SDRdaemon (that's all of them also)

The most graphical plugins: Channel analyzer and ATV related demods are not part of the deal but they are also very unlikely to be useful in a server. However for DATV support could be added in the future with a proper implementation of TS communication.

It is implemented as a new binary sdrangelsrv that is similar to sdrangel but does not fire up a GUI. This server mode binary has therefore no dependency on Qt Widgets nor OpenGL. Since it has no GUI its control is left entirely up to the web REST API interface. It also uses a different set of plugins with their GUI parts removed. These are placed in the lib/pluginssrv directory.

The main motivations are:

• be able to run SDRangel on hardware with less CPU/GPU requirements in particular without OpenGL suport.
• be used in sophisticated remote transponders or repeaters in a headless server configuration.
• possibility to use Docker technology to host SDRangel server instances in a distributed environment.
• using SDRdaemon for the RF device interface even more distributed architectures can be supported to share workload in a cluster.
• open to third party development for custom GUI implementation thanks to the RET API.

This is distributed only in Linux packages.