¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: QSK Limits

 

Well, one "can" hear in-between, one does not really hear what is between the dots (as pointed out by Jim), but one can
observe the band.

The following four points should be considered:

- this is no fun unless you have PIN diode switchin

- for normal relays, there is not only "relay chatter" but also
a lot of cross-talk (I have no knowledge about the cross-talk
with PIN diode switching)

- this cross-talk makes you crazy because you hear your own signs
with a delay. I completely loose the rhythm in that case

- for relays, the cross-talk is so strong that it pumps the AGC,
making your RX deaf after a TX/RX transition (the duration depends
on the AGC time constant).
You have to use special AGC parameters when doing QSK.

For me the bottom line is simply "don't", but others may have a different
opinion.

Am 02.04.2024 um 18:09 schrieb jimahlstrom <jahlstr@...>:

Hello Bob,

At 27 wpm the dot length is 44 milliseconds. Listening between dots is a problem with an SDR. Relay changeover including bounce is about 10 msec, and the Rx path has to recover from the overload from Tx. And then there is the delay from antenna to speaker and that can be lengthy with an SDR. The digital filters have a fixed delay. And since the HL2 is connected over a network, there are buffers to smooth out the network delays. I am running Quisk with a hardware poll of 10 msec and a play latency of 250 msec. I could reduce these settings, but not down to the point that I can listen between dots. Semi break in works fine.

A faster computer doesn't help. If Quisk runs at all, your computer is fast enough. An SDR generally has more delay than an analog radio and this is caused by how it works.

Jim
N2ADR


Re: QSK Limits

 

Hello Bob,

At 27 wpm the dot length is 44 milliseconds. Listening between dots is a problem with an SDR. Relay changeover including bounce is about 10 msec, and the Rx path has to recover from the overload from Tx. And then there is the delay from antenna to speaker and that can be lengthy with an SDR. The digital filters have a fixed delay. And since the HL2 is connected over a network, there are buffers to smooth out the network delays. I am running Quisk with a hardware poll of 10 msec and a play latency of 250 msec. I could reduce these settings, but not down to the point that I can listen between dots. Semi break in works fine.

A faster computer doesn't help. If Quisk runs at all, your computer is fast enough.? An SDR generally has more delay than an analog radio and this is caused by how it works.

Jim
N2ADR


Re: Quisk MIDI Control

 

This is a bug. The "Tune" item should appear in the Jog menu and the speed can be set there. I will fix it in the next release but first I must find a Midi device for test.

Jim
N2ADR


Re: Quisk MIDI Control

 

After I defined the MIDI controller, a section "MidiNoteDict" showed up in "quisk_settings.json". Before there was not such section.

With the information from message #2771 /g/n2adr-sdr/message/2771 I was now able, to assign the VFO to a Jog Wheel on the controller:
?{
??? "MidiNoteDict": {
????? "0xB03D": "Vol",
????? "0x9032": "Band \u2b06",
????? "0x9034": "Band \u2b07",
????? "0xB039": "Rit",
????? "0xB03B": "Ys",
????? "0xB03F": "Yz",
????? "0xB03C": "Yz",
????? "0xB040": "Zo",
????? "0x9030": "SSB U/L",
????? "0x9031": "Filter 1",
????? "0xB030": "Rit +1",
????? "0x9051": "PTT",
????? "0xB031": "Tune +3"
??? }
? }

With "Tune +3" the tuning step size will be 100Hz.
It would still be nice, if there would be a way to change the step size by a button.

Happy Easter
--

73, Joerg - DB2OO


QSK Limits

 

Please have I got hold of QSK limitations in SDR,? particularly in QUISK?

?Receive:? before replying I must hear the end of the previous over.? Causality then implies an ultimate limit set by processing power in the computer.? The next limit will be the rx hardware changeover.??

Transmit:? ?for the very first character there is a limit in computer processing.? Subsequently the sending will lag in real time but reception will be continuous.

My practical setup:? HIQSDR or HermrsLite plus linear. Computer Raspberry Pi, mostly, or laptop, Linux.? External keyer direct to hardware.? Obvious limit; relay changeover.? No way around this except diode switching.? Next:? Pi computation - use faster computer.?

To key at 25-30 wpm I believe that a changeover time of a few msec is required.? ?Mine has been more than 1 sec in worst case, just overloading cpu.? Is the only answer to increase computing power?? Should I be able to get down to relay time ??

Do not confuse the real time issue at the start and end of transmission and listening through between characters, this is what matters for QSK, with processing latency in the middle of transmission.??

73 Bob g3udi?


Re: Quisk MIDI Control

 

Seems that I was blind for the drop-down "Midi device name" in the right column yesterday. Perhaps I looked only into the left column or thinking, that the right column is related to CW only.

Anyways, after I picked my MIDI controller in "Midi Device Name", buttons, knobs and jog wheels were recognized and values shown in "Midi Control" and could be assigned:

But nevertheless I still have 3 questions:
  1. When I map a knob, with a value range from 0-127 to the "RIT" knob, it will change RIT in the +/- 2000Hz range with a step size of 32Hz, Is this somehow configurable?
  2. How can I map a jog wheel on the MIDI controller to become the "VFO wheel" in Quisk? It was my primary goal, when I bought the MIDI controller, to get a VFO knob. Unfortunately I could not find a way to map a Jog Wheel on the MIDI controller to the VFO. The only options in "Assign Midi Control to Jog Wheel" are (1) Vol, (2) Rit, (3) Ys, (4) Yz and (5) Zo !?
  3. Assigning a MIDI Jog Wheel to "Rit" in Quisk is working fine. Is there a way to influence the "Speed" in Quisk by the speed of the Jog wheel? My Jog Wheel returns 1 (127, turning counter-clockwise) for normal speed of rotation and 2 (126) for high speed of rotation.

Looking forward to your expertise
--

73, Joerg - DB2OO


Quisk MIDI Control

 

I am trying to use my "Hercules DJControl Compact" together with the MIDI capabilities of Quisk 4.2.30.
I tried it on
  1. Windows 10
  2. Linux Mint
I could validate on both platforms, that the communication between the MIDI Controller and the OS is working, by using
  1. Pocket MIDI on Windows
  2. "aconnect -l" and "aseqdump -p "DJControl Compact" on Linux Mint

But in both cases the config dialog for MIDI in Quisk stays grayed out and there is no way, to map any MIDI commands/events to Quisk functions:


According to my understanding a MIDI event should show up in the field "MIDI Control" and I should be able to map it to a function in Quisk.
But whatever I do on the MIDI controller nothing shows up in that field!?

I guess, I need to configure somewhere the "name" of the MIDI controller, which is in my case "DJControl Compact", but I could not find where.
Any help will be greatly appreciated, to get it going.

BTW: I looked into F5NPV's posting (https://f5npv.wordpress.com/quisk-midi-controller/), how he is using his MIDI controller, but he is mapping the MIDI events in a bash script to key presses, which essentially makes the Quisk MIDI functionality (if it exists) obsolete. I also searched this group and the internet for any relevant information, how to configure a MIDI controller in Quisk and could not find anything useful.

--

73, Joerg - DB2OO


Re: Some other questions about the screen

 

Thanks Neil, I found it. I thought it was on the main Quisk panel with all the other buttons and sliders and I did not look inside the config screen.
73 Pierre FK8IH


Re: Reading band or frequency from quisk_widgets.py

 

Hi Jim,

very good to know - thanks!

73
Michael, DK1MI


Re: Some other questions about the screen

 

Hi Pierre,

Just in case you haven't found it yet (I just read your question).
If you select config using the "Config" button on the screen, then choose the "Config" tab then
the "Tx level" slider is the 7th item down on the left hand side.

73, Neil G4BRK


Re: How to configure Midi wheel for VFO?

 

Hi Mario,

Thanks for this info and thanks to Michael for his post which reminded me to try it.
I now have my VFO knob mapped (on a Serato DJ2GO) to tune.

73, Neil? G4BRK


Re: How to configure Midi wheel for VFO?

 

Hi Mario,

Thanks to you I was able to map the VFO knob of my DM4DS Midi controller correctly. Very much appreciated.
+1 for adding this to the config screen.

73
Michael, DK1MI


Quisk Version 4.2.30 March 2024

 

A new option "Tx-Rx silence msec" on the Timing configuration screen controls how long to suppress Rx audio when switching from Tx to Rx. The previous fixed time was 50 msec.
?
The SSB squelch control now works on CW too. Please test.?

Jim
N2ADR


Re: cw squelsh

 

Hello Stephen,

I will extend squelch to CW in the next release. Please test, as I am a little worried about latency. You may need to turn off squelch once the net starts.

Jim
N2ADR


Re: Some other questions about the screen

 

Jim,
Thanks for your answers.
About the last point you don't understand: I read in Config-HL2-Bands-Tx Level the following (i) "This sets the transmit level 0 to 255 for each band. The config screen has a slide 0 to 100% so you can reduce the transmit power..." I don't find this slide, where should it be. I'm using v.4.2.29.
Pierre - FK8IH


Re: Quisk Error on pip install (Cannot open include file: 'sys/time.h') on Windows 11

 

¿ªÔÆÌåÓý

Thanks Jim!
Rob


From: [email protected] <[email protected]> on behalf of jimahlstrom via groups.io <jahlstr@...>
Sent: Sunday, March 17, 2024 2:05 PM
To: [email protected] <[email protected]>
Subject: Re: [n2adr-sdr] Quisk Error on pip install (Cannot open include file: 'sys/time.h') on Windows 11
?
CAUTION: This email originated from outside the Walla Walla University email system.

This is a good time to train your students to read the documentation. Quisk does not work with Python 3.12. Once there is a version of wx that works with 3.12, and once I get some free time, I will fix this.

Jim
N2ADR


Re: FDV button

 

Please see freedvpkg/README.txt for information.

Jim
N2ADR


Re: Some other questions about the screen

 

On Tue, Feb 27, 2024 at 12:51 AM, Pierre FK8IH wrote:
What is the Rflna slider, what is its purpose?
I controls the RF low noise amplifier in the HL2.
What is the screen got when hitting the Bscope button?
A bandscope display is the whole RF spectrum received by the HL2.
How can I show the "slider 0 to 100% to change the transmit power", which is indicated in the HL2 - Bands - Tx level comment?
I don't understand.

Jim
N2ADR


Re: Quisk Error on pip install (Cannot open include file: 'sys/time.h') on Windows 11

 

This is a good time to train your students to read the documentation. Quisk does not work with Python 3.12. Once there is a version of wx that works with 3.12, and once I get some free time, I will fix this.

Jim
N2ADR


Re: Tips on interfacing I/Q data into quisk?

 

Hello Rob,

The sdriqpkg directory was eliminated, and the Python hardware file quisk_hardware_sdriq.py reads the Rx I/Q samples up to a rate of 185 ksps. This interface is worth a try. You will probably have to program carefully using large blocks and no print statements.

Jim
N2ADR