开云体育

I've had this issue for a while, but I need to see if I can get it fixed. I have set the PTT key to ord(' ') and I get the following repeated in the terminal: wx._core.wxAssertionError: C++ assertion ""Assert failure"" failed at ../src/unix/utilsx11.cpp(2632) in wxGetKeyStateGTK(): Unsupported key, only modifiers can be used Traceback (most recent call last): File "/usr/lib64/python3.11/site-packages/wx/core.py", line 3427, in <lambda> lambda event: event.callable(*event.args, **event.kw) ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib64/python3.11/site-packages/quisk/quisk.py", line 6304, in OnReadSound elif self.hot_key_ptt_active and not wx.GetKeyState(conf.hot_key_ptt1): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ wx._core.wxAssertionError: C++ assertion ""Assert failure"" failed at ../src/unix/utilsx11.cpp(2632) in wxGetKeyStateGTK(): Unsupported key, only modifiers can be used Traceback (most recent call last): File "/usr/lib64/python3.11/site-packages/wx/core.py", line 3427, in <lambda> lambda event: event.callable(*event.args, **event.kw) ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib64/python3.11/site-packages/quisk/quisk.py", line 6304, in OnReadSound elif self.hot_key_ptt_active and not wx.GetKeyState(conf.hot_key_ptt1): The same thing happens when I use any other key for the short cut. I am on Fedora 37 and installed quisk using pip.

All, I am trying to setup quisk to communicate via ttyS0 to an external device (arduino) to control my amplifiers LPF's. I have my user name in the dial out already. In the remote menu I have set up CAT to /dev/ttyS0 which is a real serial port and have it connected to the arduino but I cannot get it to do anything. The arduino is programed with ok1cdj code for band decoding and I have tested it with my picastar which emulates a TS2000 for CAT and it works so I know the arduino is working. Since quisk uses flex cat commands I figured this would work. When I loaded the sketch to the arduino I also changed the baud rate to 9600 following the instruction in quisk. Serial port shows being set to 9600 also. I really would appreciate some help with this. I sure hope this is possible and I am likely missing something here hopefully just in the way I have the serial port setup in quisk. Thank you Ryan KK6DZB

It's been a while since I've had time to mess with radio stuff that isn't work related. I thought over Christmas I'd dust off the old rig and give 'er a go. Setup: Radio = Softrock RXTx on remote side with RPI3 and HiFiBerry DAC/ADC Control = Ubuntu 22.04 running in parallels on mac. Things seem to start OK. I get audio and waterfall. However, after some random amount of time, I'll get a segmentation fault. If I had to guess, it seems to be related to when things lag on either the network or control side PC (i.e. starting another program) and a buffer overflows. Tracebacks have not been much help. So far, I've gotten a couple different ones that are pasted below. The only common point is the line number has something to do with a cw key, which I'm not even utilizing. Could be random though. Possibly related note: I am running the remote headless, which means I have to pipe the X11 session back to my PC for the quisk window. This alone causes a lot of network overhead. I have been trying to minimize this by changing the remote window over to the "config" screen, but I may need to figure out a way to run the remote quisk instance without GUI feedback. -Eric WW4ET (formerly KM4DSJ) Fatal Python error: Segmentation fault Thread 0x677ff440 (most recent call first): File "/home/ewthornton/.local/lib/python3.9/site-packages/quisk/quisk.py", line 1224 in run File "/usr/lib/python3.9/threading.py", line 954 in _bootstrap_inner File "/usr/lib/python3.9/threading.py", line 912 in _bootstrap Current thread 0x76f31980 (most recent call first): File "/home/ewthornton/.local/lib/python3.9/site-packages/quisk/quisk.py", line 6266 in OnReadSound File "/home/ewthornton/.local/lib/python3.9/site-packages/wx/core.py", line 3407 in <lambda> File "/home/ewthornton/.local/lib/python3.9/site-packages/wx/core.py", line 2237 in MainLoop File "/home/ewthornton/.local/lib/python3.9/site-packages/quisk/quisk.py", line 6442 in main File "/home/ewthornton/.local/bin/quisk", line 8 in <module> Segmentation fault ---------------------------------------- Fatal Python error: Segmentation fault Current thread 0x677ff440 (most recent call first): File "/home/ewthornton/.local/lib/python3.9/site-packages/quisk/quisk.py", line 1219 in run File "/usr/lib/python3.9/threading.py", line 954 in _bootstrap_inner File "/usr/lib/python3.9/threading.py", line 912 in _bootstrap Thread 0x76f7f980 (most recent call first): File "/home/ewthornton/.local/lib/python3.9/site-packages/quisk/quisk.py", line 1356 in OnPaint File "/home/ewthornton/.local/lib/python3.9/site-packages/wx/core.py", line 2237 in MainLoop File "/home/ewthornton/.local/lib/python3.9/site-packages/quisk/quisk.py", line 6442 in main File "/home/ewthornton/.local/bin/quisk", line 8 in <module> Segmentation fault

The Alsa sound driver and the Windows sound driver with the "Fast Sound" option are fast enough to produce a useful sidetone for CW operation. I improved the PulseAudio sound driver to produce a fast sidetone too. Jim N2ADR

Hello, I am running Quisk for quite some time now on a Raspberry Pi 4 with "Raspbian GNU/Linux 10 (buster)" with the OOTB Python 3.7 on the Raspi. For Quisk 4.2.14 you need at least Python 3.8, so I installed Python 3.9 following the instructions on https://raspberrytips.com/install-latest-python-raspberry-pi/, which worked fine. I did not replace the links /usr/bin/python and /usr/bin/python3, to point to /usr/local/bin/python3.9, but I used python3.9 to start Python. When I am trying to install Quisk 4.2.14 on a Raspberry Pi 4 executing https://raspberrytips.com/install-latest-python-raspberry-pi/ I am getting this error message Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple Collecting quisk Using cached quisk-4.2.14.tar.gz (4.8 MB) Preparing metadata (setup.py) ... done Collecting wxPython Using cached wxPython-4.2.0.tar.gz (71.0 MB) Preparing metadata (setup.py) ... error error: subprocess-exited-with-error python setup.py egg_info did not run successfully. exit code: 1 [8 lines of output] Traceback (most recent call last): File "<string>", line 2, in <module> File "<pip-setuptools-caller>", line 34, in <module> File "/tmp/pip-install-pgi9obva/wxpython_1febcf57b744490dac9f94020fee773f/setup.py", line 27, in <module> from buildtools.config import Config, msg, opj, runcmd, canGetSOName, getSOName File "/tmp/pip-install-pgi9obva/wxpython_1febcf57b744490dac9f94020fee773f/buildtools/config.py", line 30, in <module> from attrdict import AttrDict ModuleNotFoundError: No module named 'attrdict' [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: metadata-generation-failed Encountered error while generating package metadata. See above for output. note: This is an issue with the package mentioned above, not pip. hint: See above for details. WARNING: You are using pip version 22.0.4; however, version 22.3.1 is available. You should consider upgrading via the '/usr/local/bin/python3.9 -m pip install --upgrade pip' command. although I have installed AttrDict with pi@rigpi3:~ $ /home/pi/.local/bin/pip3 install attrdict Defaulting to user installation because normal site-packages is not writeable Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple Collecting attrdict Downloading https://www.piwheels.org/simple/attrdict/attrdict-2.0.1-py2.py3-none-any.whl (9.9 kB) Collecting six Downloading https://www.piwheels.org/simple/six/six-1.16.0-py2.py3-none-any.whl (11 kB) Installing collected packages: six, attrdict Successfully installed attrdict-2.0.1 six-1.16.0 To be on the safe side I also installed it with the regular pip and pip3 commands, but I am nevertheless always getting the error message during the installation of Quisk, that it cannot import AttrDict. I am currently lost. Did anybody succeed, to run Quisk 4.2.14 with Python >= 3.9 on a Raspberry Pi 4 and what did you do for that? BTW: I can run Quisk 4.2.14 with Python 3.7.3, but under certain circumstances, I am getting a lot of error messages and I always get a "Segmentation fault", when I close Quisk. -- 73, Joerg - DB2OO

I am using quisk version 4.2.12 in remote mode. The hot key at the control end changes the PTT button to red but doesn't key the transmitter. I changed the code in OnReadSound in quisk.py to fix it. Maybe there is a better way, but this gets it going. if ptt is True and not ptt_button_down: self.SetPTT(True) # code added to set remote PTT when hot key pressed Don Magee if application.remote_control_head: application.Hardware.RemoteCtlSend('PTT' + ';1\n') elif ptt is False and ptt_button_down: self.SetPTT(False) if application.remote_control_head: application.Hardware.RemoteCtlSend('PTT' + ';0\n') Don Magee

Is there a way to view the current frequency of the additional receivers? Very hard to judge viewing only the graph.

I want to try the newest release of quisk with my hermes hardware instead of my peaberry. I have a hermes lite also but first want to try the 16 bit board. I am not sure how to setup. I have a static IP in the hermes and tried putting it in quisk with the radio setup as hermes and don’t get anything. I know I am missing something here just don’t know what. thanks ryan KK6DZB

Is there a CAT command for the SPOT function? I tried the tune command from the FLEX command list and nothing. Trying to set up something in FLRIG to control my antenna tuner. Also can the SPOT or TX level be controlled by CAT? Thanks Ryan KK6DZB

Hi Jim Thought I'd carry on adding digital voice modes to quisk. I'd previously added P25, I've now also included D-STAR. I've also simplified it a bit. Originally it used the op25 vocoder for TX and mbelib for RX. It now just uses the op25 vocoder. Receive is still based on dsd - with unused bits of dsd commented out (might be useful if someone wants to add other modes such as pmr) It also uses code from G4KLX's extensive projects and stuff specifically written as needed to complete the TX side. The attached file contains the delta from quisk 4.2.10 plus two extra folders - one is for the dv tx & rx code, the other for the codecs. I hacked setup.py to include the extra C modules and built it under msys2-64 under windows but found I needed a different set of dlls (apologies for not getting this quite right). To build, then first go to the folder mbe/imbe_vocoder and execute 'make' then go up one to the folder mbe and execute make again. Then build quisk. The D-STAR user interface is pretty basic :-) Also it will attempt to generate GPS data for D-STAR if it's enabled in settings. To do this in the absence of a GPS module it will attempt to use the python package 'geocoder' which needs to be installed (pip install geocoder). Or you can manually enter a GPGGA string and it will try to generate a GPRMC string from this. In both cases it will use lots of dummy values. Take a look at the stuff added to the start of configure.py I'm not completely happy with the receive filtering but it seems to work. Might have a go at improving it but think I'll go take a look at M17 next. I's been an interesting self-learning exercise into how P25 and D_STAR work. Have fun Dave G8KBB

Hello Jim et all, I have a slight issue getting the HiQSDR to work when I have a cold start up. The Quisk SW will assign it an address, which is not the default 192.168.2.196, but 192.168.4.196. This works, except when I set up firewall rules in Ubuntu 22 which I am running (UFW). I set specific rules which allow all traffic on the specific eth port ("all allowed") for 192.168.4.196. But perhaps it goes wrong at the initial setting of the IP-number? Hence, is there info on the specific ports which are required to be set open? The IP-address of the port which communicates with the HiQSDR has a static address (192.168.4.20). As soon as I disable the firewall the HiQSDR connects, and keeps working also after re-enabling the firewall. Any suggestions? 73s, Peter

Trying to figure out how to widen the transmit bandwidth in side band. Currently looking at it on another sdr panadapter it’s only 2.7 ish khz wide. I would like to go out to at least 3khz and possibly 4 for essb. Using an external eq i can clip all the higher frequencies. Just cannot figure out where to change the bandwidth. thank you

Python 2 was obsolete as of January 1, 2020. And the new code by Ben, AC2YD, needs Python 3. It is troublesome to write code that runs on both Python 2 and Python 3. So it is time to stop supporting Python 2 in Quisk. Please upgrade to Python 3. If you have both versions on your computer use Python 3 for Quisk. Some have reported that the remote Quisk graph stops after a long Tx. No graph data is sent during Tx, so perhaps the open UDP port has expired. I added keepalive graph data that is sent at one second intervals. Let's see if that fixes it. I added support for the HiQSDR radio to Remote Quisk. I corrected some drawing errors on the config screens. I removed the "Help with Radios" config tab and moved the text to the documentation available from the Help button. Jim N2ADR

I have installed Quisk 4.2.11 on a freshly-downloaded copy of Pi OS on a headless pi 3B+. It is connected to a Softrock RX ensemble and the whole system is in the boiler room of my condo building 5 floors above my apt. I had this system working a few years ago using an earlier version of Quisk and Raspian OS, and was able to listen to audio by piping it down to my laptop using pulseaudio. So I know the setup is well-connected. After the fresh install, I can watch the frequency display using VNC. Eventually I want to using the remote control option with my laptop down in the apt. but I thought I should get the head end set up first. I can see cxr and mod side-bands from CHU on 7850 kHz, and then started into calibration. However when I hit the button to calibrate phase and level between I and Q, I get this message: ** Quisk started on linux at Fri Nov 18 14:23:45 2022 Traceback (most recent call last): File "/usr/local/lib/python3.9/dist-packages/quisk/quisk_widgets.py", line 590, in OnButton self.command(event) File "/usr/local/lib/python3.9/dist-packages/quisk/configure.py", line 2029, in OnBtnPhase application.w_phase = QAdjustPhase(self, self.width, rx_tx) NameError: name 'QAdjustPhase' is not defined I am confused, since the installation went without any errors. Did I forget to add a path somewhere? How can I find out? Any suggestions greatly appreciated! 73 de Nigel ve3id

Hello group, I have been working on my remote over the internet and have run into some mysteries. To test my path to the Quisk-remote software I have been trying to telnet nn.nn.nn.nn port gvj@DLap:~$ telnet nn.nn.nn.nn 4585 Trying nn.nn.nn.nn... telnet: Unable to connect to remote host: Connection refused gvj@DLap:~$ telnet nn.nn.nn.nn pppp Trying nn.nn.nn.nn... Connected to nn.nn.nn.nn. Escape character is '^]'. In the first case I was trying the command port for Quisk and was refused. In the second case I was telneting to my remote shack controller and was able to connect perfectly as I can for port 22 (ssh). I know that port 4585 works because I can connect remotely over the internet and apart from getting RF into my home network and dropping the command port it works 100% I am OK at QRP levels and strangely enough with CW. 73, Graeme ZL2APV Can anyone explain why I can't telnet to quisk on 4585/6/7 please?

I made the Hermes LNA slider control value persistent. This make more sense than having it be a configuration setting. When using Quisk Remote, band changes from WSJT-X now correctly set the HL2 filters. I fixed a bug in the SoftRock amplitude/phase adjustment screens. I started work on using the "small screen" version of Quisk work as a control head. Please test, as more work may be needed. Jim N2ADR