开云体育

Hello Jim,

Gave Quisk a really good run this morning and made several recordings which all worked perfectly. I used your suggested setup with a Quisk sub directory in my Music directory and a base name of quisk.wav and sure enough they loaded up as quisk001.wav, quisk002.wav, quisk003.wav etc. Playback played the highest suffix and of course I can play any file individually with my normal music player.

I was going to mention on your next release that the control sliders on the config screens were out of position and in the audio tab overlaid but I see that you have redone this and everything is now in line and working perfectly so you beat me to it hi.

I have been using a sample rate of 384 ksps for all tests in order to flog the radio (Rpi4) as hard as I can and it seems to have plenty of headroom so I expect that it will support demands that you are proposing for lower audio bandwidth but I will be happy to test.

I have been running the remote via the internet for all testing with no dropouts and my laptop is running on WiFi with nothing programmed to prevent it paging through channels so it is very good with traffic. I have also run a kiwiSDR in my web browser at the same time and the audio in the Quisk receiver is several milliseconds ahead of the kiwiSDR and I am able to support the simultaneous operation of both lots of software.

I am going to have to revisit my shack setup and now rebuild things as remote operation is definitely on. I need to consider turning on the gear, restarting quisk remote in the event of a power outage etc. but I think that this is a topic on its own and I will be looking again at your hardware board.

The radio is running really well and the addition of the NR2 has made it such a pleasure to work on the erstwhile noisy 80M band. It's getting better and better and really appreciated thanks.

73, Graeme ZL2APV

My remote quisk is started automatically at boot by adding this line to /etc/xdg/lxsession/LXDE-pi/autostart .

cat /etc/xdg/lxsession/LXDE-pi/autostart

@lxpanel --profile LXDE-pi
@pcmanfm --desktop --profile LXDE-pi
@/usr/bin/python3 /home/pi/quisk-4.2.9/quisk.py? ## <<< oz9ny
@xscreensaver -no-splash

If you kill quisk for example after a config change quisk will restart without reboot.

de oz9ny, niels

Hello Jim and Niels,

@Jim The help text on the 'Window X' and 'Window Y' text boxes on the setup menu are the same as the 'Window width' and 'Window height' texts.

@ Niels Thank you for that info which of course works. I was looking at the case where I was away from my house and wanted to switch on my HL2 and connect my aerial, operate the tuner and so on. I don't normally leave Quisk running on the remote Pi as my HL2 is turned off. Setting this up will be a bit more complex. I have it running on my local LAN with a little app I wrote which does all this and monitors my shack voltage but I need that to be accessible over the internet and don't want to open any more ports than I have to. I was thinking of using port 1025 next to the hardware UDP port and will redo all the hardware to use the gpio on the Rpi4 instead of the Arduino and ESP01 that I use at present.

73, Graeme ZL2APV

jimahlstrom napsal(a):

I improved the Config/Config and Config/TxAudio screens and added help buttons for all items. The File Record button no longer overwrites an existing file. It creates a new file each time it is pressed. Enter a base name and the files will be base001.wav, base002.wav, etc. Decide on a directory for these files, perhaps the Music directory on your computer or a special directory. Files will accumulate there, and must deleted. The File Play names will follow the File Record names so that pressing Play after Record plays the current recording. I had to change a lot of logic for this, and there may be bugs. So please test.

For even more flexibility could it support special variables in the name? E.g. the name in the config "base%d.wav" where the %d would expand to the number. Personally, I currently don't need this feature, just RFE idea

73! Jaroslav, OK2JRQ

Hello Jim,

The levels label boxes have disappeared from the 'Menu/TX Audio' screen for setting the mic level.

73, Graeme ZL2APV

Hello Jim,

another one:
The 'Menu/Radio-in-use/Timing and CW' has in the 'CW Settings for Remote and' below Keyup delay the edit box label of "Use" which probably should be 'Use Sidetone'

73, Graeme ZL2APV

Hello Jim

This is really a preference for those using python3 but in the "quisk" file in the install directory it starts with:

"#!/usr/bin/env python" to set the environment. In the case of at least Ubuntu, python2 has been phased out and therefore the startup program fails to start due to being directed to an environment that does not exist.

There a few approaches to fixing this:
1. Change the line to "#!/usr/bin/env python3" which then compromises the python2 builds.

2. On Ubuntu, install the program 'python-is-python3' which simply places a symlink from python to python3.

3 In the install notes advise the user of this issue and leave it up to them what to do. Editing the 1st line of the 'quisk' file would have to be done for each upgrade if using this approach.

4. Perhaps do nothing as it is fairly trivial but it might catch some out. Others may have a better ideas than these presented.

73, Graeme ZL2APV

Hi Jim,

It looks like you fixed the problem with split mode Tx Lock indication, however, it still transmits on the Rx frequency (green line), until I Reverse Rx and Tx a couple of times.

After doing this, Quisk also has confusion coming out of split mode ... it will continue Tx on the old split Tx frequency (bad), while (single) red line is positioned at the old split Rx frequency (good -- same frequency as before entering Split mode). If I touch the tuning after coming out of Split mode, all returns to as it should be, with Rx and Tx on same (red line) frequency.

-----

Regarding Rasp Pi bandwidth, I think there's plenty to spare.? A quick look at htop (nice program!) on a Pi 4 (HLT2) shows a total CPU usage of about 80-100% for quisk, i.e. <= 1/4 of its total 4-CPU capability.? Entering "quisk" in htop's Filter, I see 4 entries (with 4 PIDs for 4 threads) ... one running around 70-75%, one around 15-17%, and two at 0%.

For my older Pi 3B+ (SoftRock), total CPU is about 115-140%, i.e ~1/3 of its total 4-CPU capability ...? htop show *5* threads (why is this different from Pi4/HLT2?? I don't know, but see below **).? One running around 95-110%, one around 20-30%, and 3 running 0%.

On both Pi machines, the 4 bars (one for each CPU) at the top of htop look as if they are in comfortable range as an overall group.? Every once in a while, one or another bar will peak kinda high, but others have plenty to spare, so I think you'll be okay adding some additional processing.

**? I have looked into the Segmentation Fault on my Pi 4 (HLT2), which does not(!) occur on my Pi 3B+ (SoftRock), even though both Pi machines have the latest updates for Pi OS ... using gdb, it appears the fault occurs in glib(?) when tearing down a thread ... I have not yet succeeded in tracking this down to a particular Quisk line of code or function ... however, when it occurs, another Quisk thread is waiting in a loop for the sound system to be torn down.? I'm wondering if the following may be a factor in the SEGFAULT ...

... I'm wondering why there are 5 threads showing in htop for my SoftRock, but only 4 for the HLT2.? I just noticed (looking at htop) that Quisk launches with two different commands on the two platforms, but I don't know if that's a factor for number of PIDs:

Pi 3B+ (Softrock):? I type "quisk" in terminal, htop shows command "python3 -m quisk" (and it shows 4 PIDs until I select a radio, *6* PIDs for about 10-15 seconds, then drops to 5)

Pi 4 (HLT2):? I type "quisk" in terminal, htop shows command "usr/bin/python3 usr/local/bin/quisk" (and it shows 4 PIDs until I select a radio, 5 PIDs for about 10-15 seconds, then drops to 4).

I hope that's not "too much information"!

I'm also working on making re-connection from a Windows Control Head more reliable ... more on that later.

As always, THANKS!!

-- Ben, AC2YD --