¿ªÔÆÌåÓý

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

Quisk Version 4.2.7 September 2022


 

This is an update to the new Quisk Remote feature by Ben, AC2YD.
?
These features are due to Jaroslav, OK2JRQ: The clip indicator is now sent from the remote to the control head. The remote radio IP address can now be a host name or an IP address. TCP and UDP ports are now distinguished in the documentation. The control head sends initial graph data to the remote in order to establish a path through NAT. The remote radio can now be operated as a normal radio unless there is an active connection to the control head.
?
The Favorites screen now works. I fixed all the bugs I know of except the segmentation fault on RPi4 raspian when closing Quisk. But I need help testing everything. Please test and let me know of any new bugs or bugs I missed.

Jim
N2ADR


 

Hello Jim,

It just keeps getting better and better. had a qso on the radio this morning using the remote and localhost for the server and also tested the Favorites which worked perfectly.

So far there is only 1 bug. When I left click on the playback button on the quick record, I can create the file and save it but when I play it (on Celluloid) there is no audio. The file size indicates a recording so I assume the volume is too low to hear.

How many times have I said thanks? - probably not enough :-)

73, Graeme ZL2APV


 

Awesome work here. I got this working with an earlier version, but I have messed something up in my config. I'm trying to figure out how to start with a completely fresh config and install, but I can't find the config file being left behind on my pi and fedora laptop after I use pip to remove quisk. I thought I found it before, but I didn't make a note :(. How can I completely clean all quisk related stuff on my systems so I can start new?


 

A minor bug report. If I run the ctl-head with an lna gain shifted to say 20 and then close the ctl-head down. next time I restart the ctl-head it defaults to my remote's initial gain setting of 14 but the remote remains at 20 where it was last set. Touching the lna gain on the ctl-head immediately synchronizes the remote and the gains track. Of course this only occurs if the remote was not restarted.

73, Graeme ZL2APV


 

¿ªÔÆÌåÓý

If you are looking for quisk_init.json and quisk_settings.json, I see them in my home directories on my Pi (/home/pi) and Ubuntu desktop (/home/bmcahill).

-- Ben, AC2YD --

On 9/23/22 18:52, Heath Petty wrote:

Awesome work here. I got this working with an earlier version, but I have messed something up in my config. I'm trying to figure out how to start with a completely fresh config and install, but I can't find the config file being left behind on my pi and fedora laptop after I use pip to remove quisk. I thought I found it before, but I didn't make a note :(. How can I completely clean all quisk related stuff on my systems so I can start new?


 

jimahlstrom napsal(a):
This is an update to the new Quisk Remote feature by Ben, AC2YD.
These features are due to Jaroslav, OK2JRQ: The clip indicator is now sent from the remote to the control head. The remote radio IP address can now be a host name or an IP address. TCP and UDP ports are now distinguished in the documentation. The control head sends initial graph data to the remote in order to establish a path through NAT. The remote radio can now be operated as a normal radio unless there is an active connection to the control head.
The Favorites screen now works. I fixed all the bugs I know of except the segmentation fault on RPi4 raspian when closing Quisk. But I need help testing everything. Please test and let me know of any new bugs or bugs I missed.
Jim
N2ADR
_._,_._,_
Hi Jim,

thanks for the update, most of the problems seems to be fixed now and it's almost perfect. But I still have problem with the remote mic if the control-head is behind NAT. I have to port forward UDP port 4588 from the router to the control-head, then it works correctly. The problem here is that this router usually is not under your control (e.g. hotel wifi), so you cannot port forward.

This is the UDP dump on the control-head (with the port 4588 forward setup):
a)
1. REMOTE:59029 -> CONTROL-HEAD:4588
2. CONTROL-HEAD:4588 -> REMOTE:59029
...

I think it needs to be the other way to work without port forwarding, i.e.:
b)
1. CONTROL-HEAD:59029 -> REMOTE:4588
2. REMOTE:4588 -> CONTROL-HEAD:59029
...

59029 is randomly taken source port by the IP stack. In the a) the packet from the REMOTE:59029 hits the NAT router and without explicit port forward it doesn't know that it should forward the UDP packet to the CONTROL-HEAD, so you get multiple:
read_remote_mic_sound_socket(), sendto(): Connection refused
read_remote_mic_sound_socket() sending 'rr', *sock = 28
read_remote_mic_sound_socket() sending 'rr', *sock = 28
read_remote_mic_sound_socket() sending 'rr', *sock = 28
read_remote_mic_sound_socket() sending 'rr', *sock = 28
read_remote_mic_sound_socket() sending 'rr', *sock = 28
...

73! Jaroslav, OK2JRQ


 

Re: minor bug report. Not a very well done report. On the remote the record and save works perfectly but on the ctl-head the audio does not record any sound at all so the recording is of silence which when saved, saves the recording time of silence. Hope this is more understandable.

73, Graeme ZL2APV


 

jimahlstrom napsal(a):
This is an update to the new Quisk Remote feature by Ben, AC2YD.
These features are due to Jaroslav, OK2JRQ: The clip indicator is now sent from the remote to the control head. The remote radio IP address can now be a host name or an IP address. TCP and UDP ports are now distinguished in the documentation. The control head sends initial graph data to the remote in order to establish a path through NAT. The remote radio can now be operated as a normal radio unless there is an active connection to the control head.
The Favorites screen now works. I fixed all the bugs I know of except the segmentation fault on RPi4 raspian when closing Quisk. But I need help testing everything. Please test and let me know of any new bugs or bugs I missed.
Jim
N2ADR
_._,_._,_
I spotted one more bug: on the control-head when clicked any bookmark link (the asterisk sign in the spectrum), it changes frequency, filter, mode indicator, but it doesn't change the mode itself. For example, if you are in the USB mode, and you click any bookmark with the FM mode, it still retains in the USB mode although the FM mode is indicated on the control panel

73! Jaroslav, OK2JRQ


 

Hi Jaroslav,

It looks to me that all 4 ports need to be implemented as servers on the remote end ... do you agree?

In the prototype, I implemented mic sound as a server on the control head; for that one port, the remote end is a client and requests the connection ... I didn't know any better than to do that, and it worked fine on my local network.? But it sounds like it's causing a problem on the internet.

-- Ben, AC2YD --

On 9/24/22 15:33, Jaroslav ?karvada wrote:

thanks for the update, most of the problems seems to be fixed now and it's almost perfect. But I still have problem with the remote mic if the control-head is behind NAT. I have to port forward UDP port 4588 from the router to the control-head, then it works correctly. The problem here is that this router usually is not under your control (e.g. hotel wifi), so you cannot port forward.

73! Jaroslav, OK2JRQ


 

Hi Ben,

yes, but it depends on the terminology what you call the server,
i.e. control-head needs to initiate the UDP communication to the static
remote ports (4585 - 4588) for smooth operation over internet with NAT.

BTW, I made dozens of voice QSOs during my vacation (I was cca. 500 km from the remote) and also during yesterday when I was just few kilometers from the remote. Nobody complained nor noticed that I am working remote, so this project is UFB

73! Jaroslav, OK2JRQ

Ben Cahill napsal(a):

Hi Jaroslav,
It looks to me that all 4 ports need to be implemented as servers on
the remote end ... do you agree?
In the prototype, I implemented mic sound as a server on the control
head; for that one port, the remote end is a client and requests the
connection ... I didn't know any better than to do that, and it
worked fine on my local network. But it sounds like it's causing a
problem on the internet.
-- Ben, AC2YD --
On 9/24/22 15:33, Jaroslav ?karvada wrote:
thanks for the update, most of the problems seems to be fixed now
and it's almost perfect. But I still have problem with the remote
mic if the control-head is behind NAT. I have to port forward UDP
port 4588 from the router to the control-head, then it works
correctly. The problem here is that this router usually is not
under your control (e.g. hotel wifi), so you cannot port forward.
73! Jaroslav, OK2JRQ


 

On Sat, Sep 24, 2022 at 05:10 PM, Graeme Jury wrote:
Re: minor bug report. Not a very well done report. On the remote the record and save works perfectly but on the ctl-head the audio does not record any sound at all so the recording is of silence which when saved, saves the recording time of silence. Hope this is more understandable.
I tested the control head file-circle and file-triangle buttons and they record and play the radio sound. I also played the recorded file with aplay on Linux. So I can not duplicate the problem. If you are trying to record the samples, this will not work on the control head because it does not have the samples.

Jim
N2ADR


 

Hello Jim,

My mistake, I was testing the upper record and playback buttons not realizing that they recorded samples not audio. I have redone the test with the lower button set and it works perfectly and allows me to play audio samples back over the radio when testing with other stations etc. Sorry about the time waste but on the positive side I learned something from this. The attachment will show what I am calling upper and lower record/playback buttons.

73, Graeme