开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
  1. N2adr-Sdr
  2. Topics

Requesy to add connect/disconnect or start/stop button to UI

 

Hello Jim,

I am using QUISK with the redpitaya as an SDR transceiver but also my rf- lab to generate test signals and/or make rf measurements in reception mode. As any test environment/set-up it changes often depending on what I want to measure and for this reason it is not unusual that QUISK " temporarily loses" the connection to the red-pitaya (for instance if I reboot the redpitaya or if I temporarily disconnect the Ethernet cable).? At the moment when this happens, I have to quit QUISK and restart it (I launch QUISK from the terminal) then re-select? the right radio ( I have 3 redpitaya). It would be faster and more convenient for me? if we could have a simple CONNECT / DISCONNECT button in the UI (or START/STOP but the idea is the same) so I can click on that button to reconnect QUISK to the RP after it has lost connection instead of having to re-start QUISK). Please note LinHPSDR,? PowerSDR , SparkSDR and SDRAngel all have this facility and it would be nice to have it for QUISK too ( if? is feasible to implement it with the QUISK concept/architecture).

Many Thanks
Regards
Peter

PS: any news on the support of SoapySDR in TX mode ? ? ??
 

Hello Peter,

I agree it would be good to have a start/stop button. I will work on this. I can't seem to get the Soapy Tx to work. I was hoping someone would figure out how to do it. I find Soapy very frustrating.

Jim
N2ADR
 

Thank you Jim, it is going to be really useful.

Something totally different now ; I would like to have the possibility to use the fields below in my redpitaya environment


image.png

As you know these fields only work with some specific hardware and unfortunately not with the redpitaya that I use. Unless I am mistaken there is currently no possibility to connect to the redpitaya some temperature and current sensors, the output of an swr bridge? or an external atenuator controlled by this RfLna slider .

Why the RfAGC doesn't work with my redpitaya today remains a mystery for me though, it should logically work because no sensors are needed for an RfAGC to work, right ?? .

Anyway, I am not too sure what is the best way of moving forward; to open a ticket on github to request to Pa add these functionalities to the redpitaya "sdr-transceiver compatible with HPSDR" or instead connect those sensors/rf bridge output/rf attenuator commands to an Arduino (for instance) instead of the redpitaya and then,? find a way of getting all the sensor information transferred from the arduino to quisk so it is displayed in the fields above. (but is this possible ?)

I would welcome your advise on this
Regards
Peter?

On Thu, Nov 21, 2019 at 12:47 PM Peter Ide-Kostic via Groups.Io <on7yi.pik973=[email protected]> wrote:
Hello Jim,

I am using QUISK with the redpitaya as an SDR transceiver but also my rf- lab to generate test signals and/or make rf measurements in reception mode. As any test environment/set-up it changes often depending on what I want to measure and for this reason it is not unusual that QUISK " temporarily loses" the connection to the red-pitaya (for instance if I reboot the redpitaya or if I temporarily disconnect the Ethernet cable).? At the moment when this happens, I have to quit QUISK and restart it (I launch QUISK from the terminal) then re-select? the right radio ( I have 3 redpitaya). It would be faster and more convenient for me? if we could have a simple CONNECT / DISCONNECT button in the UI (or START/STOP but the idea is the same) so I can click on that button to reconnect QUISK to the RP after it has lost connection instead of having to re-start QUISK). Please note LinHPSDR,? PowerSDR , SparkSDR and SDRAngel all have this facility and it would be nice to have it for QUISK too ( if? is feasible to implement it with the QUISK concept/architecture).

Many Thanks
Regards
Peter

PS: any news on the support of SoapySDR in TX mode ? ? ??
 

Hello Peter,

These fields are present because they are part of the Hermes protocol, and Red Pitaya implements the Hermes protocol. But that doesn't mean that the features exist in the hardware. If you want to pursue this, the first thing to do is ask on the Red Pitaya group if there is a temperature sensor in the hardware. If there is not, then nothing you do in software will add one. The same for AGC, RF Gain and current. There won't be a power output or SWR because Red Pitaya lacks a power amp.

You can control which fields are shown on the last line of the screen by changing the widget file shown on the Config radio Hardware screen.?

Jim
N2ADR
 

Hello Jim,

Thanks for the input. The easiest solution is obviously for me to delete those fields of the UI.

My understanding is that the RP implements the so called "Metis Protocol" . The difference between "Metis"/"Hermes" is a? bit of Chinese to me to be frank (no offense for our Chinese friends), but I know it is a real one as I have been confronted to it at least once (and if you remember, this is how you kindly implemented the ALEX filter functionality in QUISK).

?I will open a ticket on GitHub to find out if the "SDR transceiver compatible with HPSDR" supports those "Hermes" commands/Interface" with the current "Metis" implementation. If it does it would be a good news because the redpitaya hardware offers a number of GPIO pins an I2C bus interface "a la rawbery PI" and "a la Arduino" so by very nature of? this device, external temp/current/swr sensors monitoring the external PA and/or LNA could be potentially connected to the RP and then the info chaneled through the hermes/metis? protocol to QUISK (at least on paper)

Regards
Peter

On Fri, Nov 22, 2019 at 2:00 PM jimahlstrom <jahlstr@...> wrote:
Hello Peter,

These fields are present because they are part of the Hermes protocol, and Red Pitaya implements the Hermes protocol. But that doesn't mean that the features exist in the hardware. If you want to pursue this, the first thing to do is ask on the Red Pitaya group if there is a temperature sensor in the hardware. If there is not, then nothing you do in software will add one. The same for AGC, RF Gain and current. There won't be a power output or SWR because Red Pitaya lacks a power amp.

You can control which fields are shown on the last line of the screen by changing the widget file shown on the Config radio Hardware screen.?

Jim
N2ADR

 

Hi Jim

This probably adds very little but I did have Soapy working fine on Quisk 4.1.48 Tx as well as Rx on Lime mini.? A bit flaky but had qso's on 2m and 70cm.? Lost module on 4.1.51;? I see this is common problem.? 73? Bob g3udi
 

Hi Bob,
Glad to hear this works for you with the lime mini because Ibhave had no success with the Pluto, QUISK makes it ?crash in TX mode. Are you using windows or Linux .? What do you mean when you say it is a bit flaky ?

On Mon, 25 Nov 2019 at 23:42, R.J. Butcher <rjb2@...> wrote:
Hi Jim

This probably adds very little but I did have Soapy working fine on Quisk 4.1.48 Tx as well as Rx on Lime mini.? A bit flaky but had qso's on 2m and 70cm.? Lost module on 4.1.51;? I see this is common problem.? 73? Bob g3udi

 

?Hi Peter

1. Using Linux, I have no Windows facility.

Using Python2.7:
2. Built Quisk 4.1.48 a little while ago, from quisk-1.4.48.tar.gz
3. Downloaded GNURadio.
4. Downloaded Soapy to give Soapy out-of-tree blocks in GNURAdio.
5. Downloaded Limesuite and Lime out-of-tree blocks to GNURAdio.

At this point I could program Lime in GNURadio via Lime oot or Soapy oot, and run Lime under Quisk.? Lime Receive always worked correctly, bandwidths of several MHz.? Lime Tx presented more problems but I could always get it to work starting from a "minimum configuration" - 48kHz display.? Usually I could then increase display range - this can be done from configuration screen without restarting.?

I am embarrassed? to say that my computer notes are inadequate, although I might have more in my written notebook back home.? My impression is that "flaky" problems really came from trying to deal with a data rate too high for this computer.? In addition, if I changed various settings I sometimes had to restart the computer - some residual info hanging around perhaps.

Python3:? tried to change over yesterday evening, and with Quisk -4.1.51 using pip and pip3 to download.? This is all working as advertised except that Soapy is not available - I have no idea why!

I have a lot of things to deal with just now and cannot devote quite enough time to this problem - but I will try!

73? Bob g3udi
 

Thanks Bob, maybe you could just post a pictures / print screen in the config menu,? of the tx and rx soapysdr hardware parameters? that work with your limemini. I will inspire myself from what works for you and try again this week-end with mu plutosdr.
Thanks
Regards
Peter

On Tue, 26 Nov 2019, 10:36 R.J. Butcher, <rjb2@...> wrote:
?Hi Peter

1. Using Linux, I have no Windows facility.

Using Python2.7:
2. Built Quisk 4.1.48 a little while ago, from quisk-1.4.48.tar.gz
3. Downloaded GNURadio.
4. Downloaded Soapy to give Soapy out-of-tree blocks in GNURAdio.
5. Downloaded Limesuite and Lime out-of-tree blocks to GNURAdio.

At this point I could program Lime in GNURadio via Lime oot or Soapy oot, and run Lime under Quisk.? Lime Receive always worked correctly, bandwidths of several MHz.? Lime Tx presented more problems but I could always get it to work starting from a "minimum configuration" - 48kHz display.? Usually I could then increase display range - this can be done from configuration screen without restarting.?

I am embarrassed? to say that my computer notes are inadequate, although I might have more in my written notebook back home.? My impression is that "flaky" problems really came from trying to deal with a data rate too high for this computer.? In addition, if I changed various settings I sometimes had to restart the computer - some residual info hanging around perhaps.

Python3:? tried to change over yesterday evening, and with Quisk -4.1.51 using pip and pip3 to download.? This is all working as advertised except that Soapy is not available - I have no idea why!

I have a lot of things to deal with just now and cannot devote quite enough time to this problem - but I will try!

73? Bob g3udi

 

Hello Bob,

If you are running Python3, you must make soapy for Python3 too. Use "make soapy3". You also need to install Soapy with the correct bits, either 32 or 64. If your Python2 is 32-bit, and your Python3 is 64-bit, you are probably using a 32-bit Soapy which will not work with 64-bit Python. The problem of getting shared libraries (DLLs) to work together is known as "DLL Hell".

Jim
N2ADR

1 - 10 of 10