NovaSDR is uploaded to the github, and is no longer compatible with PhantomSDR, beware of this. Also it's still in beta-stage.

Possible issue with running more than one RSP1a

Started by Phil-NY4Q, Today at 13:13

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Phil-NY4Q

I am seeing this upon startup if I try to use more than one RSP1a.

2026-01-10T11:54:06.996194Z  INFO novasdr-dsp-rx1 ThreadId(08) novasdr_server::dsp_runner: DSP thread started receiver_id=rx1
2026-01-10T11:54:06.996210Z  INFO            main ThreadId(01) novasdr_server::app: server listening bind=[::]:80
2026-01-10T11:54:06.996274Z  INFO novasdr-dsp-rx0 ThreadId(09) novasdr_server::dsp_runner: DSP thread started receiver_id=rx0
[INFO] devIdx: 0
[INFO] SerNo: 18070E4096
[INFO] hwVer: 255
[INFO] rspDuoMode: 0
[INFO] tuner: 1
[INFO] rspDuoSampleFreq: 0.000000
[INFO] Using format CS16.
[INFO] devIdx: 0
[INFO] SerNo: 19110CDF97
[INFO] hwVer: 255
[INFO] rspDuoMode: 0
[INFO] tuner: 1
[INFO] rspDuoSampleFreq: 0.000000
[ERROR] SelectDevice Error: sdrplay_api_Fail
2026-01-10T11:54:07.088402Z ERROR novasdr-dsp-rx0 ThreadId(09) novasdr_server::dsp_runner: DSP loop terminated receiver_id=rx0 error=open SoapySDR device

Caused by:
    Other: SelectDevice() failed

I am concerned at the devIdx: 0 being on both receivers.

Phil

Phil-NY4Q

I am going to remove the SDRplay API v 3 and move back to v2 and try that.

Bas ON5HB

This is an SDRplay problem, it should not matter how fast Nova sends commands to Soapy.
I had the same problems before with the RSP-TCP server.
This is a problem of SDRplay.

Their API is buggy. V2.13 has the same problems, so I wonder if the chip has a problem.
As I have seen it many times, the chip just stops responding until you remove USB and plug it back in.

Phil-NY4Q

Quote from: Bas ON5HB on Today at 17:46This is an SDRplay problem, it should not matter how fast Nova sends commands to Soapy.
I had the same problems before with the RSP-TCP server.
This is a problem of SDRplay.

Their API is buggy. V2.13 has the same problems, so I wonder if the chip has a problem.
As I have seen it many times, the chip just stops responding until you remove USB and plug it back in.


There's lots of info here too pointing to the SDRPlay API and this exact issue.

https://groups.io/g/SDRPlayUsers/topic/selectdevice_error/104335929

Powered by EzPortal