Cheap Chinese RSP1 Msi2500 board only works for seconds on GQRX and SDR++

[swissdigitalnet]

Describe the bug
RSP1 Msi2500 board only works for seconds on GQRX and SDR++

To Reproduce
I tried with RTL-SDR dongle V2 and RSP2pro with GQRX and they work ok.
Then I replace the SDR with an RSP1 Msi2500 board. I can select it and the waterfall starts. But after a few seconds the waterfall and the sound stop.

Here is the output of the terminal:
gr-osmosdr 0.2.0.0 (0.2.0) gnuradio 3.9.5.0-rc1
built-in source types: file rtl rtl_tcp uhd hackrf rfspace airspy airspyhf soapy redpitaya
gr::log :WARN: file_source0 - file size is not a multiple of item size
Resampling audio 96000 -> 48000
Resampling audio 96000 -> 48000
BandPlanFile is /home/pi/.config/gqrx/bandplan.csv
BookmarksFile is /home/pi/.config/gqrx/bookmarks.csv
[INFO] [UHD] linux; GNU C++ version 10.2.1 20210110; Boost_107400; UHD_3.15.0.0-0-e35f66e8
gr-osmosdr 0.2.0.0 (0.2.0) gnuradio 3.9.5.0-rc1
built-in source types: file rtl rtl_tcp uhd hackrf rfspace airspy airspyhf soapy redpitaya
[INFO] devIdx: 0
[INFO] SerNo: B0001P0003
[INFO] hwVer: 1
[INFO] rspDuoMode: 0
[INFO] tuner: 1
[INFO] rspDuoSampleFreq: 0.000000
[INFO] Using format CF32.
Resampling audio 96000 -> 48000
[WARNING] Not updating IFGR gain because AGC is enabled
[WARNING] Not updating IFGR gain because AGC is enabled
gr-osmosdr 0.2.0.0 (0.2.0) gnuradio 3.9.5.0-rc1
built-in source types: file rtl rtl_tcp uhd hackrf rfspace airspy airspyhf soapy redpitaya
[INFO] devIdx: 0
[INFO] SerNo: B0001P0003
[INFO] hwVer: 1
[INFO] rspDuoMode: 0
[INFO] tuner: 1
[INFO] rspDuoSampleFreq: 0.000000
[INFO] Using format CF32.
Resampling audio 96000 -> 48000
[WARNING] Not updating IFGR gain because AGC is enabled
[WARNING] Not updating IFGR gain because AGC is enabled

Expected behavior
I would like to use it for a training class
Screenshots

Device Version
Raspberry Pi 4

Additional context
Add any other context about the problem here.

[SensorsIot]

I used the wrong account. Sorry. This is me. HB9BLA

[luigifcruz]

Hi, Apologies for the extremely long delay! The Pi shortage impacted my ability to pump out new releases. This problem is consistent with a driver failure. I think this could be resolved with a version upgrade. I plan to release a new PiSDR version soon. I’ll return to this issue once this happens. Best Regards, Luigi Cruz

…

On Oct 12, 2022 at 11:03 AM -0300, SensorsIOT ***@***.***>, wrote: I used the wrong account. Sorry. This is me. HB9BLA — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>