¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. N2adr-Sdr
  2. Messages
Expanded Topics Messages Polls
Date
Re: Segmentation faults with remote mode

 

Graeme,

Thanks for the reply. I started with a fresh install of the latest Raspbian (bullseye) and tried running with DISPLAY=:0. That trick does in fact help network congestion, but I can't seem to get more than a few minutes without a segmentation?fault on the remote side. It always?seems to occur when changing?filter widths or clicking on a different part of the spectrum.

The backtraces seem to be all over the place. I don't think python's built-in faulthandler is giving me the correct line. It changes every time, which makes me think it's the sound thread that is really crashing and the python line is whatever the main loop happens to be at that moment.

I'll need to try running inside of GDB to catch a real backtrace, and I'm a little rusty with that.

-73
Eric

On Wed, Dec 28, 2022 at 9:43 PM Graeme Jury <gvjury@...> wrote:
Hello Eric,

I have been running my remote on an Rpi4 with python 3.9.2 and using ssh in a terminal on the local end, invoke it with "DISPLAY=:0 nohup ~/quisk/quisk &" which runs a graphical version. I have no issues with the connection and can run it over the internet with a 50ish ksps

73, Graeme ZL2APV

Re: Quisk 4.2.14 installation fails on Raspberry PI with Python 3.9

 

Hallo Joerg,

I installed and updated Quisk on my Raspberry Pi4 "Raspbian GNU/Linux 11 (bullseye 64-bit)" following the " Linux Pip Installation" advises on

without any problem and Quisk 4.2.24 works perfectly.
# sudo apt update
# sudo apt install libfftw3-dev libasound2-dev portaudio19-dev libpulse-dev python3-dev libpython3-dev python3-wxgtk4.0 python3-usb python3-setuptools python3-pip
# sudo -H python3.9 -m pip install --upgrade quisk

Maybe it is better to update your OS to bullseye.

73, Walter DL8FCL
Re: Quisk 4.2.14 installation fails on Raspberry PI with Python 3.9

 

Hello Joerg,

If you have read my response to Eric re: segmentation fault you will see that I am using Rpi4 with python 3.9. To set Quisk up I downloaded the tar.gz version of quisk from https://pypi.org/project/quisk/#files and compiled with "make quisk3". It simply runs for me and I followed up the instructions to set it up as my remote. Something which is a little unclear (and I should make some instructions) is which items are controlled from the remote end and which are set from the control head end, e.g. the s-meter offset. I have always used the tar.gz and compiled with my running version of python on every computer that I have and suggest that it may be a solution for you as I can assure you that python 3.9 and Rpi4 and Quisk really does work.

73, Graeme ZL2APV
Re: Quisk 4.2.14 installation fails on Raspberry PI with Python 3.9

 

¿ªÔÆÌåÓý

Hello Joerg,

I run Quisk on Raspberry Pi 4, using the 3.7.3 version of Python.? It works fine for me, but I do see the Segmentation Fault when shutting down Quisk.? I'm very timid and conservative regarding "if it works, don't fix it" ... and since it works for me, I have not tried to install a later version of Python.? Actually, Jim asked me if I could try to find the Seg Fault ... I made an attempt, but really did not know how to track it down.? My apologies!? :-(

I am *no expert* here, but not replacing the links may be causing trouble, although maybe you don't want other programs to use 3.9.

Just a thought ... there is a line in the message regarding the old version of pip:

You should consider upgrading via the '/usr/local/bin/python3.9 -m pip install --upgrade pip' command.

Have you tried the following (with or without --upgrade)?? I'm hoping it might put attrdict where it could be found by your 3.9 installation:

/usr/local/bin/python3.9 -m pip install --upgrade attrdict

Then use a similar command (with --upgrade) to install Quisk?

No guarantees on my feeble suggestion ... Good luck!!

-- Ben, AC2YD --


On 12/28/22 12:09, Joerg DB2OO wrote:


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.


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: ,
Collecting attrdict
? Downloading (9.9 kB)
Collecting six
? Downloading (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

Re: Segmentation faults with remote mode

 

Hello Eric,

I have been running my remote on an Rpi4 with python 3.9.2 and using ssh in a terminal on the local end, invoke it with "DISPLAY=:0 nohup ~/quisk/quisk &" which runs a graphical version. I have no issues with the connection and can run it over the internet with a 50ish ksps

73, Graeme ZL2APV
Segmentation faults with remote mode

 

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
Quisk 4.2.14 installation fails on Raspberry PI with Python 3.9

 

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??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



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
Re: Anyone using a anan 10 or 100 or hermes 16bit board with quisk?

 

Thanks Sid!

I could always put the hermes back to protocol 1. ?I like linhpsdr but it has problems. ?Hermes lite on the other hand was working nicely. ?Tried it last night. ?Side note is there anyway to display frequency of extra receivers? ? I had a second receiver on what I hoped was 7.070 but it¡¯s hard to tell from just the graph if your off 50 or more hz. ?I was listening to 40 meter ssb and decoding psk at the same time.

Ryan?
KK6DZB?

?
Re: Anyone using a anan 10 or 100 or hermes 16bit board with quisk?

 

It's been a long time ago but I think I ran piHPSDR with the Hermes under Protocol 2.

Quisk does not support Hermes Protocol 2 - I also have an ODYSSEY-II programmed as Angelia which runs with piHPSDR.
Quisk will work with the ODY-II with the 100MB firmware.

I did ask Jim if support for Hermes could be included in quisk --- A definite NO.

If you remember, Protocol 2 took a long time from being discussed to being implemented and released -- Support for the Gigabit Ethernet appears not a trivial task.
73 ... Sid.

On 28/12/2022 02:08, Ryan Wesolowski via groups.io wrote:
I should also mention I am on protocol 2. ?I don¡¯t know if quisk will work with that.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
Re: Anyone using a anan 10 or 100 or hermes 16bit board with quisk?

 

I should also mention I am on protocol 2. ?I don¡¯t know if quisk will work with that.?
Anyone using a anan 10 or 100 or hermes 16bit board with quisk?

 

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?
Re: Quisk Version 4.2.14 December 2022

 

Hi Jim,

I did not ran an extensive test, but as far as I can tell all the features using the pop up window work! While on the small screen changing mode properties etc worked very smoothly. Thanks a lot again for this past year full of improvements of the Quisk Software! Also many thanks to Ben!

There's very cold weather advertised here on the news to hit you guys in the US, I hope you make it through safely! Merry Christmas to everyone and a peaceful 2023.....

73s,

Peter, PA3BIY
Re: Quisk Version 4.2.14 December 2022

 

Hello Mike,

Many thanks for this. I need some time to digest the info and probably for Jim to do stuff too. For your information and for the group too, here is a small Python3 script that I use to test the spot button in my Quisk Ctl-Head.

import sys
import telnetlib
import time

HOST = "localhost"
PORT = 4532

tn = telnetlib.Telnet(HOST,PORT)
tn.set_debuglevel(1)
time.sleep(1)
msg = "U TUNER 1\n".encode()
tn.write(msg)
print(tn.read_until('\n'.encode(), 1))
time.sleep(10)
msg = "U TUNER 0\n".encode()
tn.write(msg)
print(tn.read_until('\n'.encode(), 1))
tn.close()

and this is the output ...
gvj@DLap:~/PythonProjects/Remote_Hamlib$ python3 spotTest.py
Telnet(localhost,4532): send b'U TUNER 1\n'
Telnet(localhost,4532): recv b'RPRT 0\n'
b'RPRT 0\n'
Telnet(localhost,4532): send b'U TUNER 0\n'
Telnet(localhost,4532): recv b'RPRT 0\n'
b'RPRT 0\n'

73, Graeme ZL2APV or ZL2TE on CW
Re: Quisk Version 4.2.14 December 2022

Michael Black
 

Check out the current master repo

Use the --set-conf=tuner_control_pathname?

Set it to the path for your tuner control program which will get the 0/1 argument passed to it.

commit 04b18c9d5be503a064c9198843408799d2c53e0f
Author: Mike Black W9MDB <mdblack98@...>
Date:? ?Mon Dec 19 12:55:18 2022 -0600

? ? Add --set-conf=tuner_control_pathname=hamlib_tuner_control
? ? Program will be passed 0 or 1 (Off or On)
? ? Example script in tests/hamlib_tuner_control
? ? https://github.com/Hamlib/Hamlib/issues/1192

Mike W9MDB




On Thursday, December 15, 2022 at 05:45:33 PM CST, Graeme Jury <gvjury@...> wrote:


Hello Michael,

Jim has a small Hamlib server built into Quisk and I guess that as the autotuner function has not been implemented in Hamlib (yet) he has added an unused command (U) to accomodate several requests he has had from users. As I will be generating the call directly from my remote control software the use of a not officially implemented command is not a problem for me. Your messaqge has cleared up the why rigctl didn't work for me but Telnet did.

One day we will have to face the issue of the "U" command being implemented and not necessarily for a tuner but if you are showing some interest in getting this function into Hamlib that will be a good thing. My autotuner is a home brew one and I initiate a tune by pressing a button on its front panel or sending a tune signal from my remote controller (which simply blips a relay in parallel with the button) and the tuner waits for RF to appear and starts tuning when it does. At the completion of tuning it stops and sends an "I'm finished" signal back to the Remote Controller. I think that a lot of commercial tuners work like this and the becoming popular open source AT-100 series tuners by David Fainitski certainly work this way. Other tuners check the SWR continuously and if deviating too far automatically tune with no user intervention.

My issue was that when I pressed the tune button I needed Quisk to press its spot button so I had two different pieces of software that needed to talk to each other and I wanted to keep to a standard interchange - enter Hamlib.

73, Graeme ZL2APV

Re: Quisk Version 4.2.14 December 2022

Michael Black
 

That's correct....

You should get an error it's not available.

?1:rigctl_parse.c(3413):rigctl_set_func returning(-11) Feature not available

Feature not available

Mike W9MDB




On Saturday, December 17, 2022 at 02:17:53 PM CST, jimahlstrom <jahlstr@...> wrote:


Hello Graeme and Michael,

I checked the man page for rigctl and I think the "U TUNER" is a standard HamLib command. Anyway, I programmed it as a HamLib command and Quisk should respond to it correctly. It is true that not all rigs will recognize it. But the "u ?" should tell HamLib whether it is supported or not.

Jim
N2ADR

Re: Quisk Version 4.2.14 December 2022

 

Hello Graeme and Michael,

I checked the man page for rigctl and I think the "U TUNER" is a standard HamLib command. Anyway, I programmed it as a HamLib command and Quisk should respond to it correctly. It is true that not all rigs will recognize it. But the "u ?" should tell HamLib whether it is supported or not.

Jim
N2ADR
Re: CAT command for the Spot

 

Jim. ?This is what I wanted to hear thank you. ?I am not sure how to do that but will start looking.
Re: P25 and DSTAR

 

An update to the P25 and DSTAR code.
I realised that the end of transmission was not handled properly, so it now holds TX on until after the final frame plus a configurable time delay.
There is a fudge factor for the DSTAR TX audio gain as per the OP25 release notes. Yeuch.
The attached zip file is a delta on build 4.2.14.

quisk-4.2.14-dev-Jim.zip
quisk-4.2.14-dev-Jim.zip

Re: Quisk Version 4.2.14 December 2022

 

Hello Michael,

Jim has a small Hamlib server built into Quisk and I guess that as the autotuner function has not been implemented in Hamlib (yet) he has added an unused command (U) to accomodate several requests he has had from users. As I will be generating the call directly from my remote control software the use of a not officially implemented command is not a problem for me. Your messaqge has cleared up the why rigctl didn't work for me but Telnet did.

One day we will have to face the issue of the "U" command being implemented and not necessarily for a tuner but if you are showing some interest in getting this function into Hamlib that will be a good thing. My autotuner is a home brew one and I initiate a tune by pressing a button on its front panel or sending a tune signal from my remote controller (which simply blips a relay in parallel with the button) and the tuner waits for RF to appear and starts tuning when it does. At the completion of tuning it stops and sends an "I'm finished" signal back to the Remote Controller. I think that a lot of commercial tuners work like this and the becoming popular open source AT-100 series tuners by David Fainitski certainly work this way. Other tuners check the SWR continuously and if deviating too far automatically tune with no user intervention.

My issue was that when I pressed the tune button I needed Quisk to press its spot button so I had two different pieces of software that needed to talk to each other and I wanted to keep to a standard interchange - enter Hamlib.

73, Graeme ZL2APV
Re: Quisk Version 4.2.14 December 2022

 

Hello Michael and Jim,

I didn't try hard enough. I had been using rigctl to test and probably didn't have a recent enough version. When I used Telnet it went just fine and just as I had hoped for. In my final code I won't be using rigctl(d) as I intend to simply create a socket to connect to Quisk on 4532 in my remote control software and send the "U TUNER 1" command. After my autotuner reports that it is complete send "U TUNER 0" command and close the socket. I will use the tune button on my remote controller to initiate the autotune. I have attached a screenshot of my Remote Controller which basically controls 8 relays and reads from 3 analog inputs plus 2 digital inputs. Soon I will add Hamlib connectivity which will be really useful as I also want to pass on the TX frequency to my autotuner and also my Mag-Loop tuner.

73, Graeme ZL2APV
841 - 860 of 3443