ub1zcb
/
openwebrx
mirror of https://github.com/jketterl/openwebrx.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated SDRPlay device notes (markdown)

Jakob Ketterl 2021-03-01 17:33:09 +01:00
parent e05ccae668
commit 581d08ad17
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
SDRPlay-device-notes.md

@ -6,10 +6,7 @@ Only the OpenWebRX Raspberry Pi images and the OpenWebRX docker images come with
# SoapySDR support
There is multiple versions of the SoapySDRPlay module available, depending on the SDRPlay API version the following ones are recommended:
* For API version 2, please use https://github.com/pothosware/SoapySDRPlay
* For API version 3, please use https://github.com/SDRplay/SoapySDRPlay
The SoapySDR module for SDRPlay devices is available here: https://github.com/pothosware/SoapySDRPlay3
# Gain
@ -49,12 +46,16 @@ There is currently no solution available to this problem. The only workaround is
# RSPDuo: Using both tuners simultaneously
This should be possible using the API version 3, but I haven't been able to get it to work yet.
This is in theory possible with API version 3, the process is complicated and requires strict sequencing and use of the correct device selector strings.
# SDRPlay API service (API version 3 only)
Sample rates in dual tuner mode are limited to 2MS/s.
Dual tuner mode consumes so much CPU that it cannot be used on any Raspberry Pi model (tested up to RPi 4 as of writing).
# 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 process `sdrplay_apiService` has been seen consuming vast amounts of CPU (especially on SBCs like the Raspberry Pi) during normal operation, so please don't be alarmed if it does.
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.
If your device stops working and cannot be detected, the API service may have stopped working. You can restart it using the command `sudo systemctl restart sdrplay`.