开云体育

I am new to this so please bear with me. I have just received a Hermes lite, assembled it and trying to run it with Thetis. On an EFHW antenna I have been unable to get anything but static on all bands. The front of the Hermes indicates I am not making an IP connection as LED D3 is not lit. Is this a firewall issue? My S meter is reading S-9 and higher. I am connected directly with a CAT cable to the Hermes from my laptop running Windows 10. I have not even tried to hook up a mic yet. With receive signal like this, I don’t want to attempt it yet. I have been told by ON7OFF that I have lots of outside QRM and I have attempted to eliminate it with no success.Has anyone else had this problem and how do I go about fixing it?

Hi, After upgrade to 4.2.38 quisk Window at start is too wide and needs to be reduced. I think self.main_frame.SetClientSize(wx.Size(self.graph.width, self.height)) at +3991 in quisk.py is required to reduce window to minimum working in "Large screen" configuration. In my case I use "display_fraction=0.95" and "graph_width=0.55", the display is FullHD (1920x1024) in Debian12 with default GNOME GUI. Regards

I don't remenber how to set up the limesdr unit in quisk. I get a message "your SoapySDR device parameter are out of date...." May be I forget to install the PorthosSDRfrom Myriadrf site ? 73, Pascal

Hello, On the windows computer of a friend, where a visual studio has been installed, we get an error at the end of process : Microsoft Windows [version 10.0.19045.5131] (c) Microsoft Corporation. Tous droits réservés. C:\Users\lucie>python -m pip install --upgrade quisk Collecting quisk Using cached quisk-4.2.39.tar.gz (5.2 MB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Building wheels for collected packages: quisk Building wheel for quisk (pyproject.toml) ... error error: subprocess-exited-with-error × Building wheel for quisk (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [130 lines of output] running bdist_wheel running build running build_py creating build\lib.win-amd64-cpython-313\quisk copying .\configure.py -> build\lib.win-amd64-cpython-313\quisk copying .\dxcluster.py -> build\lib.win-amd64-cpython-313\quisk copying .\filters.py -> build\lib.win-amd64-cpython-313\quisk copying .\midi_handler.py -> build\lib.win-amd64-cpython-313\quisk copying .\portaudio.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_conf_defaults.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_conf_kx3.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_conf_model.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_conf_openradio.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_conf_peaberry.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_conf_sdr8600.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_conf_sdriq.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_conf_win.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_hardware_fifisdr.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_hardware_fixed.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_hardware_hamlib.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_hardware_hl2_oob.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_hardware_model.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_hardware_sdr8600.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_hardware_sdriq.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_utils.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_vna.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_wdsp.py -> build\lib.win-amd64-cpython-313\quisk copying .\quisk_widgets.py -> build\lib.win-amd64-cpython-313\quisk copying .\softrock_tune_vfo.py -> build\lib.win-amd64-cpython-313\quisk copying .\__init__.py -> build\lib.win-amd64-cpython-313\quisk copying .\__main__.py -> build\lib.win-amd64-cpython-313\quisk creating build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\conf1.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\conf2.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\conf3.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\conf3A.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\conf4.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\conf5.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\conf6.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\conf7.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\hl2_hardware.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\quisk_conf.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\quisk_conf_8600.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\quisk_hardware.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\quisk_widgets.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\scanner_widgets.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\startup.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\station_hardware.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\uhf_conf.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\uhf_hardware.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\uhf_widgets.py -> build\lib.win-amd64-cpython-313\quisk\n2adr copying .\n2adr\__init__.py -> build\lib.win-amd64-cpython-313\quisk\n2adr creating build\lib.win-amd64-cpython-313\quisk\softrock copying .\softrock\hardware_net.py -> build\lib.win-amd64-cpython-313\quisk\softrock copying .\softrock\hardware_usb.py -> build\lib.win-amd64-cpython-313\quisk\softrock copying .\softrock\widgets_tx.py -> build\lib.win-amd64-cpython-313\quisk\softrock copying .\softrock\__init__.py -> build\lib.win-amd64-cpython-313\quisk\softrock creating build\lib.win-amd64-cpython-313\quisk\freedvpkg copying .\freedvpkg\__init__.py -> build\lib.win-amd64-cpython-313\quisk\freedvpkg creating build\lib.win-amd64-cpython-313\quisk\hermes copying .\hermes\quisk_conf.py -> build\lib.win-amd64-cpython-313\quisk\hermes copying .\hermes\quisk_conf2.py -> build\lib.win-amd64-cpython-313\quisk\hermes copying .\hermes\quisk_hardware.py -> build\lib.win-amd64-cpython-313\quisk\hermes copying .\hermes\quisk_widgets.py -> build\lib.win-amd64-cpython-313\quisk\hermes copying .\hermes\__init__.py -> build\lib.win-amd64-cpython-313\quisk\hermes creating build\lib.win-amd64-cpython-313\quisk\hiqsdr copying .\hiqsdr\quisk_conf.py -> build\lib.win-amd64-cpython-313\quisk\hiqsdr copying .\hiqsdr\quisk_hardware.py -> build\lib.win-amd64-cpython-313\quisk\hiqsdr copying .\hiqsdr\__init__.py -> build\lib.win-amd64-cpython-313\quisk\hiqsdr creating build\lib.win-amd64-cpython-313\quisk\afedrinet copying .\afedrinet\afedri.py -> build\lib.win-amd64-cpython-313\quisk\afedrinet copying .\afedrinet\quisk_conf.py -> build\lib.win-amd64-cpython-313\quisk\afedrinet copying .\afedrinet\quisk_conf_linux.py -> build\lib.win-amd64-cpython-313\quisk\afedrinet copying .\afedrinet\quisk_conf_mac.py -> build\lib.win-amd64-cpython-313\quisk\afedrinet copying .\afedrinet\quisk_hardware.py -> build\lib.win-amd64-cpython-313\quisk\afedrinet copying .\afedrinet\sdr_control.py -> build\lib.win-amd64-cpython-313\quisk\afedrinet copying .\afedrinet\setup.py -> build\lib.win-amd64-cpython-313\quisk\afedrinet copying .\afedrinet\test.py -> build\lib.win-amd64-cpython-313\quisk\afedrinet copying .\afedrinet\__init__.py -> build\lib.win-amd64-cpython-313\quisk\afedrinet creating build\lib.win-amd64-cpython-313\quisk\soapypkg copying .\soapypkg\quisk_hardware.py -> build\lib.win-amd64-cpython-313\quisk\soapypkg copying .\soapypkg\setup.py -> build\lib.win-amd64-cpython-313\quisk\soapypkg copying .\soapypkg\__init__.py -> build\lib.win-amd64-cpython-313\quisk\soapypkg creating build\lib.win-amd64-cpython-313\quisk\sdrmicronpkg copying .\sdrmicronpkg\quisk_hardware.py -> build\lib.win-amd64-cpython-313\quisk\sdrmicronpkg copying .\sdrmicronpkg\__init__.py -> build\lib.win-amd64-cpython-313\quisk\sdrmicronpkg creating build\lib.win-amd64-cpython-313\quisk\perseuspkg copying .\perseuspkg\quisk_hardware.py -> build\lib.win-amd64-cpython-313\quisk\perseuspkg copying .\perseuspkg\quisk_widgets.py -> build\lib.win-amd64-cpython-313\quisk\perseuspkg copying .\perseuspkg\setup.py -> build\lib.win-amd64-cpython-313\quisk\perseuspkg copying .\perseuspkg\__init__.py -> build\lib.win-amd64-cpython-313\quisk\perseuspkg creating build\lib.win-amd64-cpython-313\quisk\ac2yd copying .\ac2yd\control_common.py -> build\lib.win-amd64-cpython-313\quisk\ac2yd copying .\ac2yd\control_hermes.py -> build\lib.win-amd64-cpython-313\quisk\ac2yd copying .\ac2yd\control_hiqsdr.py -> build\lib.win-amd64-cpython-313\quisk\ac2yd copying .\ac2yd\control_softrock.py -> build\lib.win-amd64-cpython-313\quisk\ac2yd copying .\ac2yd\remote_common.py -> build\lib.win-amd64-cpython-313\quisk\ac2yd copying .\ac2yd\remote_hermes.py -> build\lib.win-amd64-cpython-313\quisk\ac2yd copying .\ac2yd\remote_hiqsdr.py -> build\lib.win-amd64-cpython-313\quisk\ac2yd copying .\ac2yd\remote_softrock.py -> build\lib.win-amd64-cpython-313\quisk\ac2yd copying .\ac2yd\__init__.py -> build\lib.win-amd64-cpython-313\quisk\ac2yd creating build\lib.win-amd64-cpython-313\quisk\multuspkg copying .\multuspkg\quisk_hardware.py -> build\lib.win-amd64-cpython-313\quisk\multuspkg copying .\multuspkg\__init__.py -> build\lib.win-amd64-cpython-313\quisk\multuspkg copying .\CHANGELOG.txt -> build\lib.win-amd64-cpython-313\quisk copying .\libusb.txt -> build\lib.win-amd64-cpython-313\quisk copying .\license.txt -> build\lib.win-amd64-cpython-313\quisk copying .\defaults.html -> build\lib.win-amd64-cpython-313\quisk copying .\docs.html -> build\lib.win-amd64-cpython-313\quisk copying .\help.html -> build\lib.win-amd64-cpython-313\quisk copying .\help_vna.html -> build\lib.win-amd64-cpython-313\quisk copying .\libfftw3-3.dll -> build\lib.win-amd64-cpython-313\quisk copying .\libgcc_s_seh-1.dll -> build\lib.win-amd64-cpython-313\quisk copying .\libwdsp.dll -> build\lib.win-amd64-cpython-313\quisk copying .\libwinpthread-1.dll -> build\lib.win-amd64-cpython-313\quisk copying .\freedvpkg\README.txt -> build\lib.win-amd64-cpython-313\quisk\freedvpkg copying .\freedvpkg\libcodec2_64.so -> build\lib.win-amd64-cpython-313\quisk\freedvpkg copying .\freedvpkg\libcodec2_64.dll -> build\lib.win-amd64-cpython-313\quisk\freedvpkg copying .\hermes\README.txt -> build\lib.win-amd64-cpython-313\quisk\hermes copying .\afedrinet\readme.txt -> build\lib.win-amd64-cpython-313\quisk\afedrinet copying .\afedrinet\SOURCE.txt -> build\lib.win-amd64-cpython-313\quisk\afedrinet copying .\perseuspkg\README.txt -> build\lib.win-amd64-cpython-313\quisk\perseuspkg running build_ext building 'quisk._quisk' extension creating build\temp.win-amd64-cpython-313\Release\ac2yd "C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.41.34120\bin\HostX86\x64\cl.exe" /c /nologo /O2 /W3 /GL /DNDEBUG /MD -DQUISK_HAVE_ALSA -DQUISK_HAVE_PULSEAUDIO -IC:\Users\lucie\AppData\Local\Programs\Python\Python313\include -IC:\Users\lucie\AppData\Local\Programs\Python\Python313\Include "-IC:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.41.34120\include“ ”-IC:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Auxiliary\VS\include“ ”-IC:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt“ ”-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.22621.0\\um“ ”-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.22621.0\\shared“ ”-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.22621.0\\winrt“ ”-IC:\Program Files (x86)\Windows Kits\10\\include\10.0.22621.0\\cppwinrt“ ”-IC:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um" /Tcac2yd/remote.c /Fobuild\temp.win-amd64-cpython-313\Release\ac2yd/remote.obj remote.c ac2yd/remote.c(12): fatal error C1083: Impossible d'ouvrir le fichier include?: 'sys/time.h'?: No such file or directory error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio\\2022\\BuildTools\\VC\\Tools\\MSVC\\14.41.34120\\bin\\HostX86\\x64\\cl.exe' failed with exit code 2 [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for quisk Failed to build quisk ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (quisk) -------------- Any idea to solve this issue ?

Python 3.13 eliminated the telnetlib module, so I wrote a replacement. I fixed a bug in window sizing. If you use the Dx Cluster feature, please report any problems. Dx Cluster used to use the telnetlib module but is now new code. I updated the install to Python 3.13. Please report any problems with Python 3.13. Jim N2ADR

I have an Hermes Lite 2 and a RSP1 from SDRPlay. Can I have 2 receivers in quisk, one from HL2 and the other from RSP1? Regards Franco Spinelli IW2DHW

Hi Team, A few days ago I upgraded to Fedora 41 and Quisk stopped working. It appears that the 'telnetlib' module is depreciated in python 3.13 - https://peps.python.org/pep-0594/#deprecated-modules I can see that the quisk dxcluster.py program imports telnetlib leading to the error messages below. *----------------------------------------* $ quisk Traceback (most recent call last): File "/usr/bin/quisk", line 33, in <module> sys.exit(load_entry_point('quisk==4.2.39', 'gui_scripts', 'quisk')()) ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/bin/quisk", line 25, in importlib_load_entry_point return next(matches).load() ~~~~~~~~~~~~~~~~~~^^ File "/usr/lib64/python3.13/importlib/metadata/__init__.py", line 179, in load module = import_module(match.group('module')) File "/usr/lib64/python3.13/importlib/__init__.py", line 88, in import_module return _bootstrap._gcd_import(name[level:], package, level) ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "<frozen importlib._bootstrap>", line 1387, in _gcd_import File "<frozen importlib._bootstrap>", line 1360, in _find_and_load File "<frozen importlib._bootstrap>", line 1310, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed File "<frozen importlib._bootstrap>", line 1387, in _gcd_import File "<frozen importlib._bootstrap>", line 1360, in _find_and_load File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 935, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 1022, in exec_module File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed File "/usr/lib64/python3.13/site-packages/quisk/__init__.py", line 2, in <module> from .quisk import main File "/usr/lib64/python3.13/site-packages/quisk/quisk.py", line 39, in <module> import dxcluster File "/usr/lib64/python3.13/site-packages/quisk/dxcluster.py", line 6, in <module> import telnetlib ModuleNotFoundError: No module named 'telnetlib' *----------------------------------------* I am running the latest version of Quisk (4.2.39) accessible from within the standard Fedora software repositories. I wanted to pass this message along to anyone who may be considering upgrading to Fedora 41. Regards, Mark Phillips VK4AW

Hello, I was wondering how the tune functionality with an external AH-4 compatible tuner to Hermes Lite 2 is intended to work. My expectation is, after pushing the "Sport" Button tuning starts and depending of the tune response signalized back from tuner the "Spot" button on the Quisk GUI is released automatically. Currently depending on the power slider next on right side to the "Spot" button the ATU-10 goes to "tune" or "reset". After releasing the right mouse down key on "Spot" button the "Spot" button is still pressed. Independent of the tuning result of the ATU-10 I must manually again press the "Spot" button to stop tuning. An response of the tuning result is not displayed in GUI or I haven't found it yet. I measured the response voltage this seems according to AH-4 description: during tuning the response signal goes to low successful tuning the response signal goes to high tuning not possible the response signal goes to high and the switches to low for the next tuning cycle Have I overlook something or is my expectation of the behavior not implemented? 73 Dominik Quisk version 4.2.38 Hermes Lite Code version 74.2 ATU-10 version 1.6

Good Morning , I believe I have resolved this by configuring my teensy mic to also send a MIDI key to engage the PTT. Congrats to the author and all those who helped create this very flexible platform. It sure was very refreshing to continue to "homebrew" in the software side too in true spirit of being an amateur radio operator Cheers and thanks Sanat/ AD0BK

Hello All, I am using QUISK on windows 11 for my Multus Proficio. I want to free up the mouse and keyboard for PTT and wonder if I can have a dedicated hardwired PTT . I am using a TEENSy+audio as my USB microphone. I can send signals through the USB or can have another USB /serial port for a dedicated external PTT. Wonder if such an option already exists. If not can someone can point me in the right direction to explore this option please Cheers and best 73 Sanat/AD0BK

I down version to 4.2.37, it's OK. Hidehiko JA9MAT

Hi I am new to Quisk as of today. Running an HL2 up until now using Thetis. I am mainly a CW op wishing to operate remote, so believe Quisk might better meet my needs. I have Quisk running on receive able to output RF but I am struggling with setup to enable keying the HL2. I have a MIDI enabled keyer which works fine with Thetis. This tells me note 64 is used for keying. I have entered 64 as the MIDI note for CW keying on the HL2 Keys page but I am unable to key the radio. I suspect there must be other things I need to do to enable keying. I wonder whether someone might be willing to walk me through this aspect of set up? Thanks. Bob, 5B4AGN

I added an optional Hardware method PollGuiControl(self). If you define this in your Hardware file, the GUI thread will call it frequently. It can be used to set PTT from your hardware. I am trying to work around a wxPython quirk that causes mouse wheel tuning to fail. Please test. Jim N2ADR

Hi Jim, For some reason the previous thread is locked. Below is the snippet with the change from reply[0] to reply but with the parameters being used. Quisk eventually fails. The Quisk output file is multus-out (attached). Please keep in mind that Quisk runs fine if the print ("TransferIn got", reply) is commented out. I can live without the print statement as it only used for debugging purposes. The question is how do I signal Quisk to go into TX mode, turn on the PTT button and set the button directly to the right of it to TX def PollCwKey(self): # Called frequently by Quisk to check the CW key status global ptt_count global ptt_on # now = datetime.now() ptt_count -= 1 if ptt_count == 0: # print(now) reply = self.TransferIn(0xA5, 1) #INTERROGATE THE STATE OF THE MULTUS PTT SWITCH ptt_count = 200 print ("TransferIn got", reply) return # Quisk is always in Rx Below is the snippet with the parameters commented out and unused. Quisk fails. The Quisk output file is multus-1.out def PollCwKey(self): # Called frequently by Quisk to check the CW key status #global ptt_count #global ptt_on # now = datetime.now() #ptt_count -= 1 #if ptt_count == 0: # print(now) reply = self.TransferIn(0xA5, 1) #INTERROGATE THE STATE OF THE MULTUS PTT SWITCH #ptt_count = 200 print ("TransferIn got", reply) return # Quisk is always in Rx 73, Ron

Hi Folks, Jim was very gracious and provided the code modifications to integrate our product (Multus SDR, LLC. - Proficio Mark II) into Quisk. The rig functions perfectly particularly in CW mode. The Mark II has a built in CW keyer and Jim did a great job of allowing the rig to be QSK capable. The Mark II also has a PTT connector so that a switch (foot switch, etc) may set the rig into TX mode. This was not implemented so I have decided to attempt to do implementation. Jim's implementation of CW polls the rig to determine if the key is active via polling the rig via its USB connection. I need to do something similar to poll the rig to determine if the PTT connection is active. Jim provided the basics of do this and it works as I can see the rig being polled when I put the rig firmware into debug mode. OK, I have almost zero experience with Python. I am an old school C programmer with some C# experience. We (Multus SDR) have our own application called MSCC which is a combination of C# (for the GUI) and C for the back end servers, but for a number of reasons we are dropping support which I will not bore you with in favor of Quisk. Quisk is now our preferred SDR host application. So, I am asking for help with implementing the PTT function. I have included our quisk_hardware.py file. The short of what needs to be accomplished is Quisk needs activate the PTT button and display TX in the button immediately to right of it. Also Quisk needs to placed into TX mode. The question is: how do I do that? Below is are snippets of the hardware file where Quisk is polling the rig for the state of the PTT connection. I have "piggy backed" on the function Jim provided for polling the rigs CW key connection. I admit this might be the completely wrong place to do this, but it does work for polling the rigs PTT connection. previous_ptt = 0 ptt_count = 200 def TransferIN(self, address, message): # If message is an int, convert it to bytes if isinstance(message, int): message = message.to_bytes(1, 'big') # Here, message is mutable (bytes), so we can modify it if self.usb_dev: # Assuming IN is defined somewhere as a constant for the direction result = self.usb_dev.ctrl_transfer(IN, address, self.si570_i2c_address + 0x700, 0, message) # Update message with the result if needed message[:] = result # This updates the original message in place return message # Return the potentially modified message def PollCwKey(self): # Called frequently by Quisk to check the CW key status global previous_ptt global ptt_count ptt = bytearray(1) # Start with a mutable bytearray ptt_count -+ 1 #NO NEED TO POLL THE PTT CONNECTION AS FAST AS POLLING FOR THE CW KEY if ptt_count == 0: self.TransferIN(0xA5, ptt) # ptt will be modified in place. THIS IS WHERE QUISK POLLS THE RIGS PTT CONNECTION #IF PTT EQUALS ONE (1) PLACE QUISK INTO PTT MODE (AND TURN ON THE PTT BUTTON AND DISPLAY TX IN BUTTON NEXT TO IT #IF PTT EQUALS ZERO (0) TAKE QUISK OUT OF PTT MODE ptt_count = 200 #if ptt != previous_ptt: #print ("PTT") #print ("ptt:{}, previous_ptt:{}".format(ptt, previous_ptt)) #previous_ptt = ptt[0] return # Quisk is always in Rx Thanks, Ron W4MMP

Hello all, I must be doing something wrong. Between Thetis and Quisk, the reception and quality of filters are several orders of magnitute greater on Thetis. So much so, that I can't imagin anyone using Quisk over Thetis. However people do use Quisk, so I must be doing something wrong. A station that I can hear clearly and without any noise on Thetis, will have very poor signal to noise ratio on quisk. Also, if I try using NR2 (why is there no NR1?), the signal will be distorted beyond understanding and turning NR2 off again will do nothing, so I have to restart Quisk to remove the distortion from NR2. If I click NB and choose 1, 2 or 3, nothing happens at all. It is as if the button doesn't work. If, however, I choose SNB, I get the same kind of distortion I get from NR2 and I will have to restart Quist to remove it. I like Quisks interface and would like to use it instead of Thetis, so I would appriciate any help in resolving this Hardware: Hermes Lite 2 with n2adr and IO board Lenovo P50 laptop Software: Windows 10 and Quisk version 4.2.38 Thanks Peter

I just install quisk on a linux ubuntu 24lts with the same "quisk_settings.json" file as on my windows computer. ( actually, using a HL1 prototype ) On windows , NR2 works well, on linux, the button stays black. Any adjustment to do ?