I think Soapy is leaving Pluto open, which affects the functioning of Pluto SDR Sink and Pluto SDR Source (gr-iio module of GNU Radio)

[vicruz99]

Using the blocks Pluto SDR Sink and Pluto SDR Source (from the module gr-iio), I was able to send and receive a signal in the same Adalm-Pluto with no problems.

Then, because I wanted to use the Soapy library, I installed the Soapy Pluto plugin (https://github.com/pothosware/SoapyPlutoSDR) and then used the blocks Soapy Pluto Sink and Soapy Pluto Source to again send the same signal, which went fine.

Then, when I tried to run the initial blocks again, Pluto SRD Sink and Pluto SDR Source, despite the program starting and being apparently able to connect to the Plutos, I wasn't receiving any signal, or being able to control on run-time the transmitting or receiving power of Adalm-Pluto.

When I tried to use another Pluto, I could send signals again. However, as soon as I use the Soapy blocks, the blocks from the gr-iio module stop working. This error is probably due to Soapy leaving Pluto open. I suspect this because if I unplug the Pluto and then turn it on again, the modules Pluto SDR Sink and Pluto SDR Source work fine again.

System Information
OS: Fedora 39 on Virtual Box
GR Installation Method: Source

GNU Radio Version
3.11-git (main)

Specific Version
v3.11.0

Steps to Reproduce the Problem

• Send and receive a signal using blocks Pluto SDR Sink and Pluto SDR Source. Everything should go well.
• Send and receive a signal using blocks Soapy Pluto Sink and Soapy Pluto SDR. Everything should go well.
• Send and receive a signal again using blocks Pluto SDR Sink and Pluto SDR Source. You should be able to start the flowgraph, but not of receiving any signal.

[zuckschwerdt]

Is this specific to using both Sink and Source? Or can you reproduce this with e.g. just Source?
When the native Pluto blocks can't connect, are you still able to use the Soapy blocks?