||1 week ago|
|CMakeLists.txt||1 week ago|
|mainserver.cpp||6 months ago|
|mainserver.h||1 year ago|
|readme.md||2 years ago|
This folder holds the objects specific to the server (headless) version of SDRangel. The
MainServer class is the headless equivalent of the
MainWindow class in the GUI version and plays the same central role. Plugins are built specifically without GUI and are located in the
This document focuses on the functional description of SDRangel server. More details on the technical architecture can be found in the developer's documentation.
The main motivations are:
- be able to run SDRangel on hardware with less CPU/GPU requirements in particular without OpenGL support.
- 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.
- possibility to use SDRangel remotely for the RF device interface even more distributed architectures can be supported to share workload in a cluster.
- using the Web REST API interface developers with web technology skills can implement their own GUI.
- AM demodulator
- BFM (Broadcast FM) demodulator
- Remote sink
- DSD (Digital Vouice) demodulator
- NFM (Narrowband FM) demodulator
- SSB demodulator
- WFM (Wideband FM) demodulator
- UDP sink
- AM modulator
- ATV modulator
- Remote source
- NFM (Narrowband FM) modulator
- SSB modulator
- WFM (Wideband FM) modulator
- UDP source
- Airspy HF
- BladeRF input
- FCD (Funcube Dongle) Pro
- FCD Pro Plus
- File source
- HackRF input
- LimeSDR input
- Perseus (24 bit build only)
- PlutoSDR input
- Remote input
- SDRplay RSP1
- Test source
- BladeRF output
- File sink
- HackRF output
- LimeSDR output
- PlutoSDR output
- Remote output
Command line options
- -h: help
- -v: displays version information
- -a: Web REST API server interface IP address
- -p: Web REST API server port
☞ the GUI version supports the exact same options.
You can control the SDRangel application (server or GUI) by the means of the REST API. For SDRangel server the REST API is the only interface as there is no GUI. The network interface on which the REST API server listens can be controlled with the
-a option and its port with the
-p option. By default the server listens on the loopback address
127.0.0.1 and port
The API documentation is accessible online when the SDRangel application (GUI or server) is running at the address and port specified in the program options. The default is http://127.0.0.1:8091.
The documentation home page dispays two links on the left:
- Static HTML2 documentation: classical HTML based documentation
- Interactive SwaggerUI documentation: dynamic interactive documentation using the SwaggerUI interface. It offers a way to visualize and interact with the running SDRangel application API’s resources.
swagger/sdrangel/examples/ directory you can check various examples of Python scripts interacting with an instance of SDRangel using the REST API.