Some other questions about the screen
What is the Rflna slider, what is its purpose?
What is the screen got when hitting the Bscope button?
How can I show the "slider 0 to 100% to change the transmit power", which is indicated in the HL2 - Bands - Tx level comment?
73 - Pierre - FK8IH
|
I'm using Quisk v.4.2.29 with my Hermes Lite 2. After one the last upgrades a "FDV button" appeared but it is in White color and is inoperative. I have already FreeDV v.1.9.8 installed on my computer. What did I miss to use it with Quisk?
73 - Pierre - FK8IH
|
Re: Bug. Window width pixels
?I think that here ? if conf.window_width > 0:
? ? ? wFrame, h = frame.GetClientSize().Get() # client window width
? ? ? graph = GraphScreen(frame, self.width//2, self.width//2, None) # make a GraphScreen to calculate borders
? ? ? self.graph_width = wFrame - (graph.width - graph.graph_width) # less graph borders equals actual graph_width
? ? ? graph.Destroy()
? ? ? del graph
? ? ? if self.graph_width % 2 == 1: # Both data_width and graph_width are even numbers
? ? ? ? self.graph_width -= 1
? ? ? width = int(self.graph_width / conf.display_fraction) # estimated data width
? ? ? for x in fftPreferedSizes:
? ? ? ? if x >= width:
? ? ? ? ? self.data_width = x
? ? ? ? ? break
? ? ? else:
? ? ? ? self.data_width = fftPreferedSizes[-1]
|
Re: Bug. Window width pixels
This is..  
|
 If you switch from -1 to any value (or from value to -1), then it's fine. But if you switch between different values, then there is a problem. For example, between 1366 and 1920 (forward and backward). The previous value is applied. If the operation is repeated, the new value is applied. You have to apply it twice (button "On").
|
Hi
Could sqelsh option be extended to cw?
It works with ssb/am and fm ..
It would be useful for monitoring a frequency preparatory to the start of a cw net or waiting for activity on a common calling frequency.
It can be fudged by using lsb (or usb) and offsetting the frequency .. but then has to be converted back to cw when activity occurs
Also .. in 4.2.26 there seems to be a default offset of 600Hz when initiating .. presumably to generate bfo freq for audio .. but there does not seem to be much
control over initial start up (like not? to have it when starting)
Thanks de zl1any stephen
\
|
Re: Hamlib 'dummy' rig support for quisk?
I think I'm seeing the bigger picture now after reading Mike's comments and also reading the pihpsdr manual ( ref:??).
In that pihpsdr manual, search for?19090 to find where it discusses rig control (it's the port number pipsdr uses by default for rig control).
The manual says:
piHPSDR listens on port 19090 (by default, can be changed in the RigCtl menu). For standard digimode operation, choose the Kenwood TS-2000 radio model. If your digimode program can use the hamlib CAT connection library (for example, both Fldigi and WSJTX can), choose the ,,OpenHPSDR PiHPSDR¡± radio model.
And:
The CAT command set is explained in Appendix C. In most cases, using the Kenwood TS-2000 as the radio model would do it, if the digimode or laptop program uses hamlib to interface with radios, either choose TS-2000 or (preferably) the ,,OpenHPSDR PiHPSDR¡± radio model because this uses time- out values adapted to piHPSDR.
And:
Important here is to choose the correct rig model OpenHPSDR PiHPSDR and port :19090 (note the colon!).
So, if I understand this, pihpsdr is implementing TS-2000 commands passed over the network, and it also has its own back-end selected as "OpenHPSDR PiHPSDR" that still mostly implements TS-2000 commands but also extends some timeouts.
This agrees with my reading of pihpsdr's rigctl.c code that is implementing a bit-level protocol to emulate TS-2000, as opposed to quisk and others that implement a character-based protocol to emulate rigcrld.
And, if I can interpret what Mike is saying, quisk users (who have a new-enough version of Hamlib) presumably should select radio model 10 named "Quisk" to send rigctld CAT commands to Quisk, but only ones that Mike (and/or other Hamlib maintainers) think Quisk can/should handle correctly.
I'm typing all this in because reading the posts I linked above suggests there may be some disconnects on this topic.
I sure found it difficult to comprehend.
Thanks,
RDP
|
Re: Hamlib 'dummy' rig support for quisk?
On Sun, Feb 25, 2024 at 05:30 PM, Mike Black wrote:
Because quick and sdrsharp are both trying to emulate rigctld which is a bad idea.
They'd be much better off emulating a rig like the TS-2000 or TS-480 or whatever matches their capability.
?
So had to disable some things that they cannot handle.
If I understand??correctly there was a time where the only way you could emulate a TS-2000 was if you had a (real or virtual) serial port, and many (most?)? SDRs do not have real serial ports, and most linuxes don't have virtual serial ports.? ?Maybe this is still the same now, maybe it has changed? I also think the client programs forced you to provide serial port names (either COMx or /dev/ttyXX formats) and not TCP names (hostname:port?format) when using TS-2000 but there may be no real notion of connecting via TCP to a serial port so it's easy to understand why a client programmer would not code that. This suggests that at the time there really was nothing workable except emulating rigctld.?? But this is just me guessing, so if you know more, please share. PS: gqrx also emulates rigctld ( ref:??)... Thanks, RDP
|
Re: Hamlib 'dummy' rig support for quisk?
Because quick and sdrsharp are both trying to emulate rigctld which is a bad idea. They'd be much better off emulating a rig like the TS-2000 or TS-480 or whatever matches their capability.
So had to disable some things that they cannot handle.
Mike W9MDB
On Sunday, February 25, 2024 at 02:27:29 PM CST, Roger David Powers via groups.io <progpwr@...> wrote:
The hamlib source code on github has:
I'm having a hard time understanding its purpose.
I've read??in detail and it doesn't explain why hamlib would have a back end for quisk in the rigs/dummy directory.
It looks like there's one for sdrsharp as well, so at least one other sdr app thinks it needs one.
It's like 3,000 lines of code so it's hard to pick up on its intent, and it doesn't have a comment block at the top explaining its purpose.
At best I can guess it's for people who want to drive quisk via a (physical or virtual) serial port rather than through quisk's built-in hamlib net rig ctl support?
I thought they would do this by telling their app that they have a Kenwood TS-2000 which is what most SDR apps support?
Not an urgent question, just one that's bothering me...
Regards,
RDP
|
Re: Hamlib 'dummy' rig support for quisk?
To follow up on my own question, maybe this is the code that supports 'rig 10' mentioned in these two messages:
I am not running this code.? I am just reading source code and web pages trying to figure out how hamlib net rig control works, and this file is confusing me. I don't understand why quisk needs its own rig/model instead of clients just using '2' for hamlib net rig control. Regards, RDP
|
Hamlib 'dummy' rig support for quisk?
The hamlib source code on github has:
I'm having a hard time understanding its purpose.
I've read??in detail and it doesn't explain why hamlib would have a back end for quisk in the rigs/dummy directory.
It looks like there's one for sdrsharp as well, so at least one other sdr app thinks it needs one.
It's like 3,000 lines of code so it's hard to pick up on its intent, and it doesn't have a comment block at the top explaining its purpose.
At best I can guess it's for people who want to drive quisk via a (physical or virtual) serial port rather than through quisk's built-in hamlib net rig ctl support?
I thought they would do this by telling their app that they have a Kenwood TS-2000 which is what most SDR apps support?
Not an urgent question, just one that's bothering me...
Regards,
RDP
|
Re: PATCH: quisk-4.2.29 fix build with python-3.13
Thanks?Jaroslav. I will add this.
Jim
N2ADR
|
PATCH: quisk-4.2.29 fix build with python-3.13
Hi,
it seems python-3.13 relaxed includes, so the following patch is needed, because the code uses gettimeofday which is included by sys/time.h
73! Jaroslav, OK2JRQ
|
Quisk - Debian 12 - HL2 Filter Board Settings
Fresh install of Quisk from git and clicking the boxes to enable the filters on HL2 does nothing. Works by clicking in the empty boxes on Windows. Any suggestions?
73,
James / K4JVV
|
Re: Quisk 4.2.29 with linux Mint on HP laptop with Softrock 6.1
The usb microphone seems to have done the trick. Just received one in the post and plugged it in today.
This was? picked up buy the config menu in Quisk and the screenshot shows the final result that now works with the Raspberry Pi and Startech usb soundcard.
Not tried the Linux Mint laptop yet.
Don m5aky
|
Re: Quisk Version 4.2.29 January 2024
Hi,
in the 700D I can hear some analog noise like if the monitor is ON, even if it is OFF. In 700C it seems it's OK and the monitor checkbox works as expected. It's quisk-4.2.29 and system codec2-1.2.0 in Fedora 39, not the bundled one.
I will retry with the bundled codec. Are there some additional downstream patches used? Fedora builds upstream codec2 with the -DLPCNET=ON and it's pure 1.2.0 release from the [1] without additional downstream patches
thanks & regards
Jaroslav, OK2JRQ
[1]
|
Re: Quisk Version 4.2.29 January 2024
Hello Jim.
?
We have now been able to test version 4.2.29 and it is working perfect in mode 1600, 700C and 700D.
We haven't tested mode 700E and 800XA yet, but we assume that they work perfect as well. The reason is that it is only me that have installed the new version.
Thank you very much for what you have made and for maintaining this fantastic program.
73 de OZ1UM Bjarne
?
|
Re: Quisk Version 4.2.29 January 2024 - Windows 10 Fails to Build With subprocess error
It is working fine Jim. Been messing with it most of the evening and it's nice piece of software. I have to get the I/O board configured now and hopefully I'll be in business to xmit for now. You have certainly done a great job with all. By the way, how were the slopes??
Jim
W3BG
|
Re: Quisk Version 4.2.29 January 2024 - Windows 10 Fails to Build With subprocess error
I am glad it is working. But the installation procedure installs a pre-compiled version of Quisk. This version does not need to be compiled. There is no pre-compiled version of Quisk for Python 3.12, so the installer tried to make one and failed. I was away skiing or I would have answered sooner.
Jim
N2ADR
|
Re: Quisk Version 4.2.29 January 2024 - Windows 10 Fails to Build With subprocess error
Solved - with the help of VE3TOS, Dave, and OZ9NY, Neils, from a discussion back in June 2023 on the reflector. I was using Python?3.12. Their recommendation was to use Python 3.10.? I?quickly uninstalled Python 3.12 and reinstalled 3.10 and Microsoft VS completed the build. I have a working Windows 10 version of Quisk 4.2.29 up and running. Thanks - Niels and Dave.
|
Pierre - FK8IH
Nick Abramenko RA3PKJ
Jim Samuels W3BG