开云体育

I'm using automatic tuner in the balcony to long wire antenna. Coax is ~10m. After tuning in different bands it shows higher than usual SWR value (close to 3:1), when tuner (Z-11ProII) shows it is less 2:1. I'm using chock balun after tuner and other (1:1 current) before tuner. Mostly SWR shown wrong in higher bands (17,15,12,10m). Antena wire is ~32m and counterpose ~7.5m. I checked with external SWR meter (newr HL2) - it shows <2:1.

Hi, I have external amplifier connected to HL2 and it is controlled by external PTT via RCA plug. But I would like to tune external automatic tuner without engaging amplifier. Also I would like to disable external PTT (external amplifier) for some bands also. From schematics it is at different FPGA output from internal PTT for K2 (28 vs 7). Regards Rolandas

I would like to get to the bottom of the following error message snipped from my quisk_logfile.txt file. *** Quisk started on linux at Sun Nov 24 11:09:34 2024 WxPython 4.2.1 gtk3 (phoenix) wxWidgets 3.2.4 Start of wdsp Found public wdsp Wdsp version 118 Library wdsp is active Open channel 1 Traceback (most recent call last): File "hermes/quisk_widgets.py", line 78, in OnAtu if not self.hardware.io_board.have_IO_Board: ^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'Hardware' object has no attribute 'io_board' Traceback (most recent call last): File "hermes/quisk_widgets.py", line 78, in OnAtu if not self.hardware.io_board.have_IO_Board: ^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'Hardware' object has no attribute 'io_board' Traceback (most recent call last): File "hermes/quisk_widgets.py", line 78, in OnAtu if not self.hardware.io_board.have_IO_Board: ^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'Hardware' object has no attribute 'io_board' Closing Remote Control connection I do have an IO board installed and working properly and am able to customize it to operate my peripherals. It appears to me that Quisk does not interrogate the board on startup as the case REG_FIRMWARE_MAJOR: and case REG_FIRMWARE_MINOR: in the IO board firmware is never called. I believe that piHPSDR does not use these calls to detect the board either but uses other methods to see if it is installed or not. The error messages are not an issue in terms of operating Quisk and cause no problems but I'm simply not comfortable with not understanding what is going on. 73 de Graeme ZL2TE

It is possible to improve Gui of Quisk in two sections? - A separate button for favorite, without pass through "Config" notebook - An added row for Soapy device with rx gain control duplicating rx gain control in "Config" tab (choice from Total/Detailed/Automati and slider for value of each mode of the device) Regards Franco Spinelli IW2DHW

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