Re: Quisk Version 4.2.14 December 2022
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
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
|
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
|
Re: CAT command for the Spot
Hello Ryan,
The simplest way to do this is to just press the Spot button and have it assert RTS. This is easy from your own hardware file. That is why Quisk has hardware files.?
Jim
N2ADR
|
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
On Fri, Dec 9, 2022 at 10:39 AM, Michael Black wrote:
Hamlib does have a "TUNER" function but it depends on the rig supporting it.
I will add this to Quisk.? Jim N2ADR
|
Re: CAT command for the Spot
Hamlib does have a "TUNER" function but it depends on the rig supporting it.
U TUNER 1
U TUNER 0
Mike W9MDB
toggle quoted message
Show quoted text
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@...>:
Hamlib knows nothing about audio so cannot, by itself, generate any audio.
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@...>:
There is currently no HamLib control for Spot. The command does not seem to exist in rig 2. What commands from the Flex ZZ list do you want to add?
Jim
N2ADR
|
Re: CAT command for the Spot
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,
toggle quoted message
Show quoted text
Am 09.12.2022 um 15:37 schrieb Michael Black via groups.io <mdblack98@...>:
Hamlib knows nothing about audio so cannot, by itself, generate any audio.
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@...>:
There is currently no HamLib control for Spot. The command does not seem to exist in rig 2. What commands from the Flex ZZ list do you want to add?
Jim
N2ADR
|
Re: CAT command for the Spot
Hamlib knows nothing about audio so cannot, by itself, generate any audio.
Rig in FM or CW should generate a carrier as opposed to USB/LSB with a suppressed carrier.
Mike W9MDB
toggle quoted message
Show quoted text
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@...>:
There is currently no HamLib control for Spot. The command does not seem to exist in rig 2. What commands from the Flex ZZ list do you want to add?
Jim
N2ADR
|
Re: CAT command for the Spot
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.
toggle quoted message
Show quoted text
Am 08.12.2022 um 22:18 schrieb jimahlstrom <jahlstr@...>:
There is currently no HamLib control for Spot. The command does not seem to exist in rig 2. What commands from the Flex ZZ list do you want to add?
Jim
N2ADR
|
Re: CAT command for the Spot
There is currently no HamLib control for Spot. The command does not seem to exist in rig 2. What commands from the Flex ZZ list do you want to add?
Jim
N2ADR
|
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
|
Re: HiQSDR ports and IP addressing
I solved the IP assignment, using "sudo ufw allow in on eth1" (eth1 in my case, the nic which only connects to the HiQSR).
It resulted in a new issue for the VPN though....?
73s,
Peter, PA3BIY
|
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
|
Re: How to widen ssb transmission bandwidth
Jim,
Thank you for the explanation. ?I know its not a priority and my never happen but having the transmitter bandwidth adjustable at least out to 3k with the low end at 50 hz would be awesome. ?The audio reports over the weekend running 500 watts and using easy effects were very good. ?The essb guys even commented on how good it sounded even being so narrow by comparison. ?Out to at least 3k I would use 99 percent of the time. ?
I am having a lot of fun on linux right now. ?One thing that kept me from playing with the peaberry was being spoiled by the nr2 noise reduction in thetis and the noise reduction in my picastar. ?Now that it¡¯s in quisk my cheap peaberry is a joy to use.
thanks?
ryan
kk6dzb
|
Re: Quisk Version 4.2.13 December 2022
Hello Jim,
Since installing quisk-4.2.13 I have (over the internet) participated in a CW contest with many short duration contacts, followed by an SSB QSO in which I transmitted an over whose length was likely to have my QSO partner drop off to sleep. The good news is that at no time was there any graphics stoppage and everything works 100%
73, Graeme ZL2APV
|
Re: Successful new install on raspberry pi but fails to calibrate
Thanks for that. I will
scope around and look for noise, but I cannot hook up a stereo
headphone since the line2 USB does not have outputs.? I can't
use anything for output as this is in a sealed metal box that I
run remotely five floors away and there is not room for anything
else in the box!? I presently have brought it down to the apt to
see about adjusting
The images going back happen as soon as I get out of the config
screen. I have not found any 'save' button in the screens and
other settings seem to be safe on leaving.
One thing I do notice is that when receiving an AM signal,
multiple spurious sidebands appear when I turn the AM modulation
up past about 30% on the service monitor.
I looked into the subsample delay earlier on and found something
to compensate from the documentation (I can;t remember what it was
- that was a few months ago) and it didn't change anything. I
would imaging that if this was the case though, I wouldn't be able
to get clean audio demodulated on BC stations as well as CHU and
WWV, and some CW on 40m.
One thing I did was to disconnect the Adafruit 12V-5V switch-mode
regulator and power it directly from my lab supply, and that
didn't make any difference to the mountain.
I'm still leaning towards a driver issues since the chip is not
the TI one and I wonder if there is a way to change it, but so far
have found nothing!
Thanks for your help
Nigel ve3id
Nigel Johnson, MSc., MIEEE, MCSE VE3ID/G4AJQ/VA3MCU
Amateur Radio, the origin of the open-source concept!
Skype: TILBURY2591
On 2022-12-05 13:26, Chuck Ritola
wrote:
toggle quoted message
Show quoted text
To determine if the spectral hump in the center is noise,
switch Quisk's mode to DGT-IQ, tune to the center where the
spectral hump is and give it a listen on stereo headphones.
What you hear is more-or-less a direct feed from your audio
interface as it is heard by Quisk. The center hump does NOT
look amplitude/phase/delay related, or, at least, whatever
amp/phase issues are being buried by a much bigger issue.
I warn that some of those Behringer interfaces have
subsample delay which will cause phase/mirroring issues. If
your hardware indeed has that bug, phase corrections will be
futile as the subsample delay changes every time the interface
is powered up, making the saved corrections unusable. I did a
write-up on this a few months ago:
On Nov. 24th you stated? "The image seems to reduce but then goes back to
the previous level." but did not state /when/ it goes back
to the previous level, so I can't comment as to whether or
not subsample delays, which change with every powerup, is
contributing to your issue.
It's doubtful that the interface is placing bass emphasis
on the audio /input/ as low frequencies are not generally a
bottleneck in transformerless recording.?
My understanding is that you are using a Behringer Line2
for input. I don't know if it has the subsample delay bug.
It's not clear if you are still using the UFO202 for output.
From what I can find, the UFO202 uses a TI 2902 chip, which I
had confirmed has the subsample delay bug.
Looking at the softrock ensemble 40 RX's schematic, I don't
see any isolation transformers on the softrock's analog audio
output but I do see isolator caps. Ground hum, usb data noise,
ethernet noise or supply noise may be happening. The DGT-IQ
listen should help determine that.
On Mon, Dec 5, 2022 at 12:48
PM Nigel Johnson MIEEE via <nw.johnson= [email protected]>
wrote:
I got that, but the
Behringer does not have USB output!
Nigel Johnson, MSc., MIEEE, MCSE VE3ID/G4AJQ/VA3MCU
Amateur Radio, the origin of the open-source concept!
Skype: TILBURY2591
On 2022-12-05 12:44, Ben Cahill wrote:
Hello Nigel,
I mean listening to the Behrenger's digital USB output,
via an audio app of some sort on your computer, rather
than via Quisk.
Good luck!
-- Ben, AC2YD --
On 12/5/22 09:35, Nigel Johnson MIEEE via wrote:
The line2 by
Behringer does not have outputs, just inputs.?
|
Re: Successful new install on raspberry pi but fails to calibrate
To determine if the spectral hump in the center is noise, switch Quisk's mode to DGT-IQ, tune to the center where the spectral hump is and give it a listen on stereo headphones. What you hear is more-or-less a direct feed from your audio interface as it is heard by Quisk. The center hump does NOT look amplitude/phase/delay related, or, at least, whatever amp/phase issues are being buried by a much bigger issue.
I warn that some of those Behringer interfaces have subsample delay which will cause phase/mirroring issues. If your hardware indeed has that bug, phase corrections will be futile as the subsample delay changes every time the interface is powered up, making the saved corrections unusable. I did a write-up on this a few months ago:
On Nov. 24th you stated? "The
image seems to reduce but then goes back to the previous level." but did not state /when/ it goes back to the previous level, so I can't comment as to whether or not subsample delays, which change with every powerup, is contributing to your issue.
It's doubtful that the interface is placing bass emphasis on the audio /input/ as low frequencies are not generally a bottleneck in transformerless recording.?
My understanding is that you are using a Behringer Line2 for input. I don't know if it has the subsample delay bug. It's not clear if you are still using the UFO202 for output. From what I can find, the UFO202 uses a TI 2902 chip, which I had confirmed has the subsample delay bug.
Looking at the softrock ensemble 40 RX's schematic, I don't see any isolation transformers on the softrock's analog audio output but I do see isolator caps. Ground hum, usb data noise, ethernet noise or supply noise may be happening. The DGT-IQ listen should help determine that.
On Mon, Dec 5, 2022 at 12:48 PM Nigel Johnson MIEEE via <nw.johnson= [email protected]> wrote:
I got that, but the
Behringer does not have USB output!
Nigel Johnson, MSc., MIEEE, MCSE VE3ID/G4AJQ/VA3MCU
Amateur Radio, the origin of the open-source concept!
Skype: TILBURY2591
On 2022-12-05 12:44, Ben Cahill wrote:
Hello Nigel,
I mean listening to the Behrenger's digital USB output, via an
audio app of some sort on your computer, rather than via Quisk.
Good luck!
-- Ben, AC2YD --
On 12/5/22 09:35, Nigel Johnson MIEEE
via wrote:
The line2 by Behringer
does not have outputs, just inputs.?
|
Re: Successful new install on raspberry pi but fails to calibrate
I got that, but the
Behringer does not have USB output!
Nigel Johnson, MSc., MIEEE, MCSE VE3ID/G4AJQ/VA3MCU
Amateur Radio, the origin of the open-source concept!
Skype: TILBURY2591
On 2022-12-05 12:44, Ben Cahill wrote:
toggle quoted message
Show quoted text
Hello Nigel,
I mean listening to the Behrenger's digital USB output, via an
audio app of some sort on your computer, rather than via Quisk.
Good luck!
-- Ben, AC2YD --
On 12/5/22 09:35, Nigel Johnson MIEEE
via groups.io wrote:
The line2 by Behringer
does not have outputs, just inputs.?
|
Nigel Johnson MIEEE