Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- N2adr-Sdr
- Messages
Search
|
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: 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. |
|
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 |
|
Re: Quisk Version 4.2.14 December 2022
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 |
|
Re: Quisk Version 4.2.14 December 2022
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 |
|
Re: Quisk Version 4.2.14 December 2022
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 |
|
Re: CAT command for the Spot
Thank you for the responses. ?I should have been mor clear in what I want to accomplish. ?I need to be able to activate the spot function which sends out the carrier and at the same time activate the rts or dtr pin from a serial port. ?I have a small circuit built and connected to the rts dtr pins that activates the tuner to go into ¡°tune¡±. ?I had this setup in my ddutil on windows where via macros I could combine the two outputs together and believe I can do this in flrig. ?It would be great if this could be done natively in quisk but didn¡¯t think that was likely. ?
|
|
Re: CAT command for the Spot
Michael Black
Hamlib does have a "TUNER" function but it depends on the rig supporting it.
toggle quoted message
Show quoted text
U TUNER 1 U TUNER 0 Mike W9MDB On Friday, December 9, 2022 at 09:27:19 AM CST, Christoph v. W¨¹llen <dl1ycf@...> wrote:
yes, but hamlib lacks a "TUNE" functionality (just emitting a carrier) and temporarily switching to FM (or AM, for? that matter, but with less power) and activating PTT gives you right that. So in my "Rig controller GUI", whenever I hit the "TUNE" button, the reported sequence of events (all possible with hamlib) is emitted. The original post wanted to by-pass hamlib and directly send a CAT command (many rigs *do* have such a command), and I wanted to show just a "compatible" procedure. Yours, Am 09.12.2022 um 15:37 schrieb Michael Black via groups.io <mdblack98@...>: |
|
Re: CAT command for the Spot
yes, but hamlib lacks a "TUNE" functionality (just emitting a carrier) and
toggle quoted message
Show quoted text
temporarily switching to FM (or AM, for that matter, but with less power) and activating PTT gives you right that. So in my "Rig controller GUI", whenever I hit the "TUNE" button, the reported sequence of events (all possible with hamlib) is emitted. The original post wanted to by-pass hamlib and directly send a CAT command (many rigs *do* have such a command), and I wanted to show just a "compatible" procedure. Yours, Am 09.12.2022 um 15:37 schrieb Michael Black via groups.io <mdblack98@...>: |
|
Re: CAT command for the Spot
Michael Black
Hamlib knows nothing about audio so cannot, by itself, generate any audio.
toggle quoted message
Show quoted text
Rig in FM or CW should generate a carrier as opposed to USB/LSB with a suppressed carrier. Mike W9MDB On Friday, December 9, 2022 at 02:15:30 AM CST, Christoph v. W¨¹llen <dl1ycf@...> wrote:
I have once made a "GUI rig controller" and this is how I implemented emitting a "TUNE" using hamlib: a) set power to desired value b) change mode to FM c) activate PTT at the end of "TUNE" I then do a) deactivate PTT b) change mode to previous mode c) set power to previous value For each step, there is a hamlib command, while there seems to be none for just emitting a carrier. Am 08.12.2022 um 22:18 schrieb jimahlstrom <jahlstr@...>: |
|
Re: CAT command for the Spot
I have once made a "GUI rig controller" and this is how I implemented
toggle quoted message
Show quoted text
emitting a "TUNE" using hamlib: a) set power to desired value b) change mode to FM c) activate PTT at the end of "TUNE" I then do a) deactivate PTT b) change mode to previous mode c) set power to previous value For each step, there is a hamlib command, while there seems to be none for just emitting a carrier. Am 08.12.2022 um 22:18 schrieb jimahlstrom <jahlstr@...>: |
|
HiQSDR ports and IP addressing
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 |
to navigate to use esc to dismiss