¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. N2adr-Sdr
  2. Topics

Quisk Version 4.2.14 December 2022

 

The new file quisk_hardware_fifisdr.py supports the FiFi SDR hardware. Thanks to Joe, LA6GRA.

I added the rig 2 Hamlib command "U TUNER 1" to control the Spot button.

The Quisk remote feature now works with the "Small" screen format. Please test.

Jim
N2ADR
 

Hello Jim,

Could you please give me a little more guidance to implement the "U TUNER 1" command. I have tried the following ...

Rig command: U TUNER 1
set_func: error = Feature not available
rig_has_set_func called
rig_ext_lookup called
rigctl_parse.c(3291):rigctl_set_func return(-11)

Rig command: U
Func: TUNER
Func Status: 1
set_func: error = Feature not available
rig_has_set_func called
rig_ext_lookup called
rigctl_parse.c(3291):rigctl_set_func return(-11)

... but I think I am getting this wrong. In my remote shack controller, when I press the tune button, I prepare my autotuner via the internet to start tuning when it receives sufficient RF (about 0.1 watts will do it) so I was hoping that at the same time as preparing the autotuner, my remote controller will send a signal via Hamlib to operate the spot button on Quisk Ctl-Head. When my autotuner is finished it sends an "I am done" signal back to my local shack remote controller and I would like it to send another Hamlib signal to switch off the spot tune.

I think that this is what you have done with the "U TUNER 1" signal and hope that I have not got this wrong. One QSO on the quisk-4.2.14 with no issues but not tried the small screen yet. Again thanks for everything.

73, Graeme ZL2APV
Michael Black
 

What rig?? Not all support that function.

Mike W9MDB




On Thursday, December 15, 2022 at 04:10:29 PM CST, Graeme Jury <gvjury@...> wrote:


Hello Jim,

Could you please give me a little more guidance to implement the "U
TUNER 1" command. I have tried the following ...

Rig command: U TUNER 1
set_func: error = Feature not available
rig_has_set_func called
rig_ext_lookup called
rigctl_parse.c(3291):rigctl_set_func return(-11)

Rig command: U
Func: TUNER
Func Status: 1
set_func: error = Feature not available
rig_has_set_func called
rig_ext_lookup called
rigctl_parse.c(3291):rigctl_set_func return(-11)

... but I think I am getting this wrong. In my remote shack controller,
when I press the tune button, I prepare my autotuner via the internet to
start tuning when it receives sufficient RF (about 0.1 watts will do it)
so I was hoping that at the same time as preparing the autotuner, my
remote controller will send a signal via Hamlib to operate the spot
button on Quisk Ctl-Head. When my autotuner is finished it sends an "I
am done" signal back to my local shack remote controller and I would
like it to send another Hamlib signal to switch off the spot tune.

I think that this is what you have done with the "U TUNER 1" signal and
hope that I have not got this wrong. One QSO on the quisk-4.2.14 with no
issues but not tried the small screen yet. Again thanks for everything.

73, Graeme ZL2APV
Michael Black
 

Reading this a bit more carefully what you want is not currently possible.

How are you controlling your tuner?? Via some script or your own program?

It would be possible to add some sort of "external" tuning function that could call a script/external program and just wait for it to respond (with some programmable timeout).
Hadn't thought of doing this before.

It's also on my to-do list to add tuner control to hamlib so if you can tell me your? equipment involved I can look into adding it.? My first targets are and LDG tuner and an MFJ-998 that I have access to.

Mike W9MDB




On Thursday, December 15, 2022 at 04:10:29 PM CST, Graeme Jury <gvjury@...> wrote:


Hello Jim,

Could you please give me a little more guidance to implement the "U
TUNER 1" command. I have tried the following ...

Rig command: U TUNER 1
set_func: error = Feature not available
rig_has_set_func called
rig_ext_lookup called
rigctl_parse.c(3291):rigctl_set_func return(-11)

Rig command: U
Func: TUNER
Func Status: 1
set_func: error = Feature not available
rig_has_set_func called
rig_ext_lookup called
rigctl_parse.c(3291):rigctl_set_func return(-11)

... but I think I am getting this wrong. In my remote shack controller,
when I press the tune button, I prepare my autotuner via the internet to
start tuning when it receives sufficient RF (about 0.1 watts will do it)
so I was hoping that at the same time as preparing the autotuner, my
remote controller will send a signal via Hamlib to operate the spot
button on Quisk Ctl-Head. When my autotuner is finished it sends an "I
am done" signal back to my local shack remote controller and I would
like it to send another Hamlib signal to switch off the spot tune.

I think that this is what you have done with the "U TUNER 1" signal and
hope that I have not got this wrong. One QSO on the quisk-4.2.14 with no
issues but not tried the small screen yet. Again thanks for everything.

73, Graeme ZL2APV
 

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
 

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
 

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

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

 

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
 

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

1 - 11 of 11