Re: Very simple config screen for quisk on debian new install
You are running a version which precedes that feature (4.1.77). It was not added until 4.1.91 according to the CHANGELOG: "I added a button to set the WSJT-X path and config option. It is on the Config/Config screen."
I recommend uninstalling the existing version and installing the latest:
On Tue, Aug 29, 2023 at 2:19?AM Jonathan Hopper < jrhopper@...> wrote: Hello,
I'm at a bit of a loss, I am trying to setup a copy of quisk on Debian on arm for use with WSJT-X and I cannot find the option I need on the Config->config screen. It's a very much simpler interface. See the attached screen shot. Is there a configuration flag or pkg that quisk checks for before bringing up the launch WSJT-X drop down? I have enabled pulesaudio for digital TX and RX in the audio tab.?
Thanks,
Jon AB8WU
|
Very simple config screen for quisk on debian new install
Hello,
I'm at a bit of a loss, I am trying to setup a copy of quisk on Debian on arm for use with WSJT-X and I cannot find the option I need on the Config->config screen. It's a very much simpler interface. See the attached screen shot. Is there a configuration flag or pkg that quisk checks for before bringing up the launch WSJT-X drop down? I have enabled pulesaudio for digital TX and RX in the audio tab.?
Thanks,
Jon AB8WU
|
Re: Quisk Version 4.2.19 May 2023
A more elegant solution In the quisk.py.
In the first place:
self.sample_rate = Hardware.VarDecimSet() # Get the sample rate.
# ------------------------------------------------------------------------------------------------------added
abc = round(self.sample_rate / 1000)
self.sample_rate = abc * 1000
# ------------------------------------------------------------------------------------------------------------
self.vardecim_set = self.sample_rate And in the second place:
rate = Hardware.VarDecimSet(i)
# ------------------------------------------------------------------------------------------------------added
abc = round(rate / 1000)
rate = abc * 1000
# ------------------------------------------------------------------------------------------------------------
self.vardecim_set = rate
|
Analog noise in FreeDV modes
Hi,
quisk-4.2.22, codec2-1.2.0. If I switch to the 700D, 2020, or 700E modes there is analog noise output from the speaker even if no signal is received like in the FM mode. For other FreeDV modes it seems it works correctly (i.e. no analog noise).
Debug output:
// changed to the 700D
FreeDV codec2 library 1 found, version 15
Change in mode to 7
freedv_open: system codec2 library found, version 15
n_nom_modem_samples 1280
n_speech_samples 1280
n_max_modem_samples 1320
modem_sample_rate 8000
speech_sample_rate 8000
// analog noise received
// changed to the 700C
Change in mode to 6
freedv_open: system codec2 library found, version 15
n_nom_modem_samples 640
n_speech_samples 640
n_max_modem_samples 667
modem_sample_rate 8000
speech_sample_rate 8000
// no analog noise received
73! Jaroslav, OK2JRQ
|
Re: Quisk Version 4.2.19 May 2023
For the information. The problem disappears if I do so (I'm not a professional):? ? ? abc = int(float(self.conf.rx_udp_clock) / dec + 0.5)
? ? if (192005 - abc) < 5 and (192005 - abc) > 0:
? ? ? return 192000 ? ? return abc The problem also occurs with other values. The solution is similar, for example:
? ? if (384005 - abc) < 5 and (384005 - abc) > 0:
? ? ? return 384000
And so on.
|
Re: Quisk Version 4.2.19 May 2023
It's here
return int(float(self.conf.rx_udp_clock) / dec + 0.5)
|
Re: Quisk Version 4.2.19 May 2023
|
Re: Quisk Version 4.2.19 May 2023
Jim, Hi
With my HiQSDR in the quisk_init.json file?I have a stable error - "vardecimal_set": 192001, when trying to make 192000 in Quisk. After a new start, I get 48000.
|
Re: Hamlib/rigctl compatibility?
Next question I forgot to ask -- what rig?
Mike W9MDB
On Monday, August 21, 2023 at 05:52:44 PM CDT, ag5gt@... < ag5gt@...> wrote: The quisk version is 4.2.20
|
Re: Hamlib/rigctl compatibility?
Ensure the rig shows VFOA as the active VFO.
toggle quoted message
Show quoted text
On Monday, August 21, 2023 at 05:51:06 PM CDT, ag5gt@... <ag5gt@...> wrote:
Yes, "IP address for Hamlib Rig 2" is localhost and "IP port for Hamlib" is 4532, but there's "Rig 2" again. Is this really rig 2 specific or should it also work with the new rig 10?
|
Re: Hamlib/rigctl compatibility?
Model 10 is intended to be customized to Quisk capabilities.
Forgot to ask -- what rig? are you using?? ?That could make a difference.
Mike W9MDB
toggle quoted message
Show quoted text
On Monday, August 21, 2023 at 05:51:06 PM CDT, ag5gt@... <ag5gt@...> wrote:
Yes, "IP address for Hamlib Rig 2" is localhost and "IP port for Hamlib" is 4532, but there's "Rig 2" again. Is this really rig 2 specific or should it also work with the new rig 10?
|
Re: Hamlib/rigctl compatibility?
The quisk version is 4.2.20
|
Re: Hamlib/rigctl compatibility?
Yes, "IP address for Hamlib Rig 2" is localhost and "IP port for Hamlib" is 4532, but there's "Rig 2" again. Is this really rig 2 specific or should it also work with the new rig 10?
|
Re: Hamlib/rigctl compatibility?
First, yes, rig 2 behaves the similarly. However, being unaware of split support, and having never used it, I had never looked at "I" or "i" commands with respect to rigctl. Here's a sequence where quisk started with 3903000 on its display:
rigctl -m 2
?
Rig command: F 7150000
?
Rig command: f
Frequency: 7145000
?
Rig command: i
TX Frequency: 7150000
?
Quisk's display correctly responded to the F command by displaying 7150000. The follow-up response to "f" seems wrong by 5khz. Then the "i" returns "TX Frequency" 7150000, which matches what was set with the initial "F" command. The fact that "i" returns what we set with "F" seems reasonable, if we do not intend to operate split; i.e., the intended receive frequency (F) actually should be the same as transmit(i). But, I don't understand the response to "f". If "F" sets the rx frequency, shouldn't "f" return the rx frequency??Incidentally, the "RIT" button shows "0", if that matters.
I have only one piece of hardware plugged in to the pi. So, hardware-wise at least, there is only one receiver. Your question causes me to wonder if there might be some piece of software detritus lingering from a previous quisk or rigctl installation, and it is making trouble.
The original installation used repository binaries. A concern is the updates were built from the latest releases on the respective websites for quisk and hamlib. I would like to say I removed the repository versions before doing anything else, but too much time has passed. Even if I did remove the packages, was something left behind anyway? I do vaguely recall an issue recently, during these various experiments, where some fragment of something (the wsjtx package?) had to be removed to clear an error flag.?
I definitely did retain config files through the updates. Could that cause trouble when moving from one version to another? I guess I have some homework to do...
A clean install, starting with the OS, may still be the fix, though 64 bit may not be required.
Bruce ag5gt
|
Re: Hamlib/rigctl compatibility?
Also, please check under "Remote" that the Hamlib port is 4532 and the host is localhost.
Jim
N2ADR
|
Re: Hamlib/rigctl compatibility?
I set up my 32-bit raspberry pi and downloaded and built the Hamlib 4.6~git. The F and f commands worked perfectly. So I don't think the problem is the 32-bit OS.
Here are some things to try. Make sure you do not have split Rx/Tx. The F command is really the Rx frequency. The I command is the Tx frequency. So test with the "I" and "i" commands and see what happens. Also, make sure you are not using multiple receivers.
I would still like to know if rig 2 works. You are using rig 10. Try rig 2.
Jim
N2ADR
|
Re: Hamlib/rigctl compatibility?
One thing I forgot to ask...what version of Quisk are you running?
Mike W9MDB
On Monday, August 21, 2023 at 02:34:25 PM CDT, ag5gt@... <ag5gt@...> wrote:
With the first set, quisk does correctly follow the F command. There are errors on read-back. Here's the sequence:
~ $ rigctl -m 10
?
Rig command: F 7071000
?
Rig command: f
Frequency: 7067000
?
Rig command: F 7072000
?
Rig command: f
Frequency: 7073000
?
Rig command: F 7071000
?
Rig command: f
Frequency: 7070000
?
Rig command: F 7072000
?
Rig command: f
Frequency: 7073000
For the second sequence, quisk follows the F command correctly and the f (read-back) is consistently correct, too! Here is that sequence:
?
~ $ rigctl -m 10
?
Rig command: F 7070000 f
?
Rig command:?
Rig command: Frequency: 7070000
?
Rig command: F 7071000 f
?
Rig command:?
Rig command: Frequency: 7071000
?
Rig command: F 7072000 f
?
Rig command:?
Rig command: Frequency: 7072000
?
Rig command: F 7073000 f
?
Rig command:?
Rig command: Frequency: 7073000
?
Rig command: F 7074000 f
?
Rig command:?
Rig command: Frequency: 7074000
?
Rig command: F 7075000 f
?
Rig command:?
Rig command: Frequency: 7075000
?
Rig command: F 7076000 f
?
Rig command:?
Rig command: Frequency: 7076000
?
Rig command: F 7077000 f
?
Rig command:?
Rig command: Frequency: 7077000
?
Rig command: F 7078000 f
?
Rig command:?
Rig command: Frequency: 7078000
?
Rig command: F 7079000 f
?
Rig command:?
Rig command: Frequency: 7079000
?
Rig command: F 7080000 f
?
Rig command:?
Rig command: Frequency: 7080000
?
Rig command: F 7081000 f
?
Rig command:?
Rig command: Frequency: 7081000
?
Rig command: F 7082000 f
?
Rig command:?
Rig command: Frequency: 7082000
?
Rig command: F 7083000 f
?
Rig command:?
Rig command: Frequency: 7083000
?
Rig command: F 7084000 f
?
Rig command:?
Rig command: Frequency: 7084000
?
Rig command: F 7085000 f
?
Rig command:?
Rig command: Frequency: 7085000
?
Rig command: F 7086000 f
?
Rig command:?
Rig command: Frequency: 7086000
?
Rig command: F 7087000 f
?
Rig command:?
Rig command: Frequency: 7087000
?
Rig command: F 7088000 f
?
Rig command:?
Rig command: Frequency: 7088000
?
Rig command: F 7089000 f
?
Rig command:?
Rig command: Frequency: 7089000
?
Rig command: F 7090000 f
?
Rig command:?
Rig command: Frequency: 7090000
Next, I tried something a little different. I used your F xxxxxxxx f commands, but followed each with two more f commands. Quisk started at 7090000 where the last test left it. Then Quisk correctly followed the F commands, as before. The most immediate read-back (f) was also correct, as before. However, responses to the second and third f commands were wrong and identical, though quisk remained tuned according to the most recent F command. I got bored, so did not run your whole list, but jumped around a bit. Errors could be plus or minus 1K, 10.5K or 20K. Here is the whole sequence:
rigctl -m 10
?
Rig command: f
Frequency: 7091000
?
Rig command: F 7070000 f
?
Rig command:?
Rig command: Frequency: 7070000
?
Rig command: f
Frequency: 7050000
?
Rig command: f
Frequency: 7050000
?
Rig command: f
Frequency: 7050000
?
Rig command: F 7071000 f
?
Rig command:?
Rig command: Frequency: 7071000
?
Rig command: f
Frequency: 7072000
?
Rig command: F 7072000 f
?
Rig command:?
Rig command: Frequency: 7072000
?
Rig command: f
Frequency: 7073000
?
Rig command: f
Frequency: 7073000
?
Rig command: F 7073000 f
?
Rig command:?
Rig command: Frequency: 7073000
?
Rig command: f
Frequency: 7074000
?
Rig command: f
Frequency: 7074000
?
Rig command: F 7074000 f
?
Rig command:?
Rig command: Frequency: 7074000
?
Rig command: f
Frequency: 7075000
?
Rig command: f
Frequency: 7075000
?
Rig command: F 7075000 f
?
Rig command:?
Rig command: Frequency: 7075000
?
Rig command: f
Frequency: 7076000
?
Rig command: f
Frequency: 7076000
?
Rig command: F 7090000 f
?
Rig command:?
Rig command: Frequency: 7090000
?
Rig command: f
Frequency: 7105000
?
Rig command: f
Frequency: 7105000
?
Rig command: F 7089000 f
?
Rig command:?
Rig command: Frequency: 7089000
?
Rig command: f
Frequency: 7088000
?
Rig command: f
Frequency: 7088000
?
Rig command: F 7088000 f
?
Rig command:?
Rig command: Frequency: 7088000
?
Rig command: f
Frequency: 7087000
?
Rig command: f
Frequency: 7087000
?
Rig command: F 7087000 f
?
Rig command:?
Rig command: Frequency: 7087000
?
Rig command: f
Frequency: 7086000
?
Rig command: f
Frequency: 7086000
There was arbitrary jumping around in that last sequence, but consistencies emerged. Quisk always responded correctly to an F. The response to the first f immediately after the F (on the same command line) was always also correct. Responses to subsequent f commands (on new lines) were wrong and unchanging with repetition.
These interactive command line experiments are interesting because of what works and what doesn't. However, unlike the interactive command line stuff, I seem to recall quisk did not necessarily respond correctly to set frequency commands from wsjtx via udp nor to a cat command sent through a virtual serial port. I also recall response times being highly variable by cat, whereas rigctl interactive command lines execute without perceptible delay. One bug could have cascading consequences, but to a person ignorant of the code construction of hamlib or quisk, it also seems there could be multiple issues.
Do you have any more 32 bit experiments for me, or is it time to try the 64 bit OS?
|
Re: Hamlib/rigctl compatibility?
With the first set, quisk does correctly follow the F command. There are errors on read-back. Here's the sequence:
~ $ rigctl -m 10
?
Rig command: F 7071000
?
Rig command: f
Frequency: 7067000
?
Rig command: F 7072000
?
Rig command: f
Frequency: 7073000
?
Rig command: F 7071000
?
Rig command: f
Frequency: 7070000
?
Rig command: F 7072000
?
Rig command: f
Frequency: 7073000
For the second sequence, quisk follows the F command correctly and the f (read-back) is consistently correct, too! Here is that sequence:
?
~ $ rigctl -m 10
?
Rig command: F 7070000 f
?
Rig command:?
Rig command: Frequency: 7070000
?
Rig command: F 7071000 f
?
Rig command:?
Rig command: Frequency: 7071000
?
Rig command: F 7072000 f
?
Rig command:?
Rig command: Frequency: 7072000
?
Rig command: F 7073000 f
?
Rig command:?
Rig command: Frequency: 7073000
?
Rig command: F 7074000 f
?
Rig command:?
Rig command: Frequency: 7074000
?
Rig command: F 7075000 f
?
Rig command:?
Rig command: Frequency: 7075000
?
Rig command: F 7076000 f
?
Rig command:?
Rig command: Frequency: 7076000
?
Rig command: F 7077000 f
?
Rig command:?
Rig command: Frequency: 7077000
?
Rig command: F 7078000 f
?
Rig command:?
Rig command: Frequency: 7078000
?
Rig command: F 7079000 f
?
Rig command:?
Rig command: Frequency: 7079000
?
Rig command: F 7080000 f
?
Rig command:?
Rig command: Frequency: 7080000
?
Rig command: F 7081000 f
?
Rig command:?
Rig command: Frequency: 7081000
?
Rig command: F 7082000 f
?
Rig command:?
Rig command: Frequency: 7082000
?
Rig command: F 7083000 f
?
Rig command:?
Rig command: Frequency: 7083000
?
Rig command: F 7084000 f
?
Rig command:?
Rig command: Frequency: 7084000
?
Rig command: F 7085000 f
?
Rig command:?
Rig command: Frequency: 7085000
?
Rig command: F 7086000 f
?
Rig command:?
Rig command: Frequency: 7086000
?
Rig command: F 7087000 f
?
Rig command:?
Rig command: Frequency: 7087000
?
Rig command: F 7088000 f
?
Rig command:?
Rig command: Frequency: 7088000
?
Rig command: F 7089000 f
?
Rig command:?
Rig command: Frequency: 7089000
?
Rig command: F 7090000 f
?
Rig command:?
Rig command: Frequency: 7090000
Next, I tried something a little different. I used your F xxxxxxxx f commands, but followed each with two more f commands. Quisk started at 7090000 where the last test left it. Then Quisk correctly followed the F commands, as before. The most immediate read-back (f) was also correct, as before. However, responses to the second and third f commands were wrong and identical, though quisk remained tuned according to the most recent F command. I got bored, so did not run your whole list, but jumped around a bit. Errors could be plus or minus 1K, 10.5K or 20K. Here is the whole sequence:
rigctl -m 10
?
Rig command: f
Frequency: 7091000
?
Rig command: F 7070000 f
?
Rig command:?
Rig command: Frequency: 7070000
?
Rig command: f
Frequency: 7050000
?
Rig command: f
Frequency: 7050000
?
Rig command: f
Frequency: 7050000
?
Rig command: F 7071000 f
?
Rig command:?
Rig command: Frequency: 7071000
?
Rig command: f
Frequency: 7072000
?
Rig command: F 7072000 f
?
Rig command:?
Rig command: Frequency: 7072000
?
Rig command: f
Frequency: 7073000
?
Rig command: f
Frequency: 7073000
?
Rig command: F 7073000 f
?
Rig command:?
Rig command: Frequency: 7073000
?
Rig command: f
Frequency: 7074000
?
Rig command: f
Frequency: 7074000
?
Rig command: F 7074000 f
?
Rig command:?
Rig command: Frequency: 7074000
?
Rig command: f
Frequency: 7075000
?
Rig command: f
Frequency: 7075000
?
Rig command: F 7075000 f
?
Rig command:?
Rig command: Frequency: 7075000
?
Rig command: f
Frequency: 7076000
?
Rig command: f
Frequency: 7076000
?
Rig command: F 7090000 f
?
Rig command:?
Rig command: Frequency: 7090000
?
Rig command: f
Frequency: 7105000
?
Rig command: f
Frequency: 7105000
?
Rig command: F 7089000 f
?
Rig command:?
Rig command: Frequency: 7089000
?
Rig command: f
Frequency: 7088000
?
Rig command: f
Frequency: 7088000
?
Rig command: F 7088000 f
?
Rig command:?
Rig command: Frequency: 7088000
?
Rig command: f
Frequency: 7087000
?
Rig command: f
Frequency: 7087000
?
Rig command: F 7087000 f
?
Rig command:?
Rig command: Frequency: 7087000
?
Rig command: f
Frequency: 7086000
?
Rig command: f
Frequency: 7086000
There was arbitrary jumping around in that last sequence, but consistencies emerged. Quisk always responded correctly to an F. The response to the first f immediately after the F (on the same command line) was always also correct. Responses to subsequent f commands (on new lines) were wrong and unchanging with repetition.
These interactive command line experiments are interesting because of what works and what doesn't. However, unlike the interactive command line stuff, I seem to recall quisk did not necessarily respond correctly to set frequency commands from wsjtx via udp nor to a cat command sent through a virtual serial port. I also recall response times being highly variable by cat, whereas rigctl interactive command lines execute without perceptible delay. One bug could have cascading consequences, but to a person ignorant of the code construction of hamlib or quisk, it also seems there could be multiple issues.
Do you have any more 32 bit experiments for me, or is it time to try the 64 bit OS?
|
Re: Hamlib/rigctl compatibility?
Yes -- let's try going back and forth to see if the error is consistent with frequency.
And does quisk follow the set frequency correctly?
F 7071000
f
F 7072000
f
F 7071000
f
F 7072000
f
Then...see? how the? error behaves with this.
F 7070000 f
F 7071000 f
F 7072000 f
F 7073000 f
F 7074000 f
F 7075000 f
F 7076000 f
F 7077000 f
F 7078000 f
F 7079000 f
F 7080000 f
F 7081000 f
F 7082000 f
F 7083000 f
F 7084000 f
F 7085000 f
F 7086000 f
F 7087000 f
F 7088000 f
F 7089000 f
F 7090000 f
toggle quoted message
Show quoted text
On Sunday, August 20, 2023 at 06:40:58 PM CDT, ag5gt@... <ag5gt@...> wrote:
OK. Starting with quisk at 3903, as with previous tests, here's your first sequence:
~ $ rigctl -m 10
?
Rig command: f
Frequency: 3903000
?
Rig command: F 7071000
?
Rig command: f
Frequency: 7067000
?
Rig command: f
Frequency: 7067000
?
Rig command: F 7072000
?
Rig command: f
Frequency: 7073000
?
Rig command: f
Frequency: 7073000
?
Each read-back has an error, and the error repeats with a follow-up read-back. I then kill rigctl and start again, with your incantation, with quisk still displaying 7072000.
rigctl -m 10 --set-conf=cache_timeout=0 f
7073000
There is the 1K error again. Anything else?
|
Re: Hamlib/rigctl compatibility?
OK. Starting with quisk at 3903, as with previous tests, here's your first sequence:
~ $ rigctl -m 10
?
Rig command: f
Frequency: 3903000
?
Rig command: F 7071000
?
Rig command: f
Frequency: 7067000
?
Rig command: f
Frequency: 7067000
?
Rig command: F 7072000
?
Rig command: f
Frequency: 7073000
?
Rig command: f
Frequency: 7073000
?
Each read-back has an error, and the error repeats with a follow-up read-back. I then kill rigctl and start again, with your incantation, with quisk still displaying 7072000.
rigctl -m 10 --set-conf=cache_timeout=0 f
7073000
There is the 1K error again. Anything else?
?
|
Nick Abramenko RA3PKJ