Updated SDRPlay device notes (markdown)
parent
581d08ad17
commit
798e425200
|
|
@ -1,10 +1,8 @@
|
|||
# General
|
||||
|
||||
SDRPlay currently provides two major versions of their driver ("API") for Linux on their [website](https://www.sdrplay.com/): versions 2 and 3. Most of the devices currently available are supported by both versions, with the exception of the RSPDx which requires version 3 explicitly.
|
||||
The OpenWebRX Raspberry Pi images and the OpenWebRX docker images come with the driver preloaded. If you're installing from the Debian or Ubuntu repository, or are following the manual installation process, you will need to install both the driver and the SoapySDRPlay module manually.
|
||||
|
||||
Only the OpenWebRX Raspberry Pi images and the OpenWebRX docker images come with the driver preloaded, if you're installing from packages you will need to install both the driver and the SoapySDRPlay module manually.
|
||||
|
||||
# SoapySDR support
|
||||
SDRPlay currently provide their driver ("API") for Linux on their [website](https://www.sdrplay.com/) exclusively.
|
||||
|
||||
The SoapySDR module for SDRPlay devices is available here: https://github.com/pothosware/SoapySDRPlay3
|
||||
|
||||
|
|
@ -54,7 +52,7 @@ Dual tuner mode consumes so much CPU that it cannot be used on any Raspberry Pi
|
|||
|
||||
# SDRPlay API service
|
||||
|
||||
The API version 3 comes with a dedicated SDRPlay API service that manages interaction with the hardware. It is installed as a systemd unit.
|
||||
The SDRPlay API comes with a dedicated SDRPlay API service that manages interaction with the hardware. It is installed as a systemd unit and must be running to be able to access any SDRPlay devices.
|
||||
|
||||
The process `sdrplay_apiService` has been seen consuming vast amounts of CPU (especially on SBCs like the Raspberry Pi) during normal operation. This seems to be expected, so please don't be alarmed if it does.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue