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: Hamlib/rigctl compatibility?
Mike Black
Ensure the rig shows VFOA as the active VFO.
toggle quoted message
Show quoted text
On Monday, August 21, 2023 at 05:51:06 PM CDT, ag5gt@... <ag5gt@...> wrote:
Yes, "IP address for Hamlib Rig 2" is localhost and "IP port for Hamlib" is 4532, but there's "Rig 2" again. Is this really rig 2 specific or should it also work with the new rig 10? |
|
Re: Hamlib/rigctl compatibility?
Mike Black
Model 10 is intended to be customized to Quisk capabilities.
toggle quoted message
Show quoted text
Forgot to ask -- what rig? are you using?? ?That could make a difference. Mike W9MDB On Monday, August 21, 2023 at 05:51:06 PM CDT, ag5gt@... <ag5gt@...> wrote:
Yes, "IP address for Hamlib Rig 2" is localhost and "IP port for Hamlib" is 4532, but there's "Rig 2" again. Is this really rig 2 specific or should it also work with the new rig 10? |
|
Re: Hamlib/rigctl compatibility?
First, yes, rig 2 behaves the similarly. However, being unaware of split support, and having never used it, I had never looked at "I" or "i" commands with respect to rigctl. Here's a sequence where quisk started with 3903000 on its display:
rigctl -m 2
?
Rig command: F 7150000
?
Rig command: f
Frequency: 7145000
?
Rig command: i
TX Frequency: 7150000
?
Quisk's display correctly responded to the F command by displaying 7150000. The follow-up response to "f" seems wrong by 5khz. Then the "i" returns "TX Frequency" 7150000, which matches what was set with the initial "F" command. The fact that "i" returns what we set with "F" seems reasonable, if we do not intend to operate split; i.e., the intended receive frequency (F) actually should be the same as transmit(i). But, I don't understand the response to "f". If "F" sets the rx frequency, shouldn't "f" return the rx frequency??Incidentally, the "RIT" button shows "0", if that matters.
I have only one piece of hardware plugged in to the pi. So, hardware-wise at least, there is only one receiver. Your question causes me to wonder if there might be some piece of software detritus lingering from a previous quisk or rigctl installation, and it is making trouble. The original installation used repository binaries. A concern is the updates were built from the latest releases on the respective websites for quisk and hamlib. I would like to say I removed the repository versions before doing anything else, but too much time has passed. Even if I did remove the packages, was something left behind anyway? I do vaguely recall an issue recently, during these various experiments, where some fragment of something (the wsjtx package?) had to be removed to clear an error flag.? I definitely did retain config files through the updates. Could that cause trouble when moving from one version to another? I guess I have some homework to do... A clean install, starting with the OS, may still be the fix, though 64 bit may not be required. Bruce ag5gt |
|
Re: Hamlib/rigctl compatibility?
I set up my 32-bit raspberry pi and downloaded and built the Hamlib 4.6~git. The F and f commands worked perfectly. So I don't think the problem is the 32-bit OS.
Here are some things to try. Make sure you do not have split Rx/Tx. The F command is really the Rx frequency. The I command is the Tx frequency. So test with the "I" and "i" commands and see what happens. Also, make sure you are not using multiple receivers. I would still like to know if rig 2 works. You are using rig 10. Try rig 2. Jim N2ADR |
|
Re: Hamlib/rigctl compatibility?
Mike Black
One thing I forgot to ask...what version of Quisk are you running? Mike W9MDB
On Monday, August 21, 2023 at 02:34:25 PM CDT, ag5gt@... <ag5gt@...> wrote:
With the first set, quisk does correctly follow the F command. There are errors on read-back. Here's the sequence: ~ $ rigctl -m 10
?
Rig command: F 7071000
?
Rig command: f
Frequency: 7067000
?
Rig command: F 7072000
?
Rig command: f
Frequency: 7073000
?
Rig command: F 7071000
?
Rig command: f
Frequency: 7070000
?
Rig command: F 7072000
?
Rig command: f
Frequency: 7073000
For the second sequence, quisk follows the F command correctly and the f (read-back) is consistently correct, too! Here is that sequence: ?
~ $ rigctl -m 10
?
Rig command: F 7070000 f
?
Rig command:?
Rig command: Frequency: 7070000
?
Rig command: F 7071000 f
?
Rig command:?
Rig command: Frequency: 7071000
?
Rig command: F 7072000 f
?
Rig command:?
Rig command: Frequency: 7072000
?
Rig command: F 7073000 f
?
Rig command:?
Rig command: Frequency: 7073000
?
Rig command: F 7074000 f
?
Rig command:?
Rig command: Frequency: 7074000
?
Rig command: F 7075000 f
?
Rig command:?
Rig command: Frequency: 7075000
?
Rig command: F 7076000 f
?
Rig command:?
Rig command: Frequency: 7076000
?
Rig command: F 7077000 f
?
Rig command:?
Rig command: Frequency: 7077000
?
Rig command: F 7078000 f
?
Rig command:?
Rig command: Frequency: 7078000
?
Rig command: F 7079000 f
?
Rig command:?
Rig command: Frequency: 7079000
?
Rig command: F 7080000 f
?
Rig command:?
Rig command: Frequency: 7080000
?
Rig command: F 7081000 f
?
Rig command:?
Rig command: Frequency: 7081000
?
Rig command: F 7082000 f
?
Rig command:?
Rig command: Frequency: 7082000
?
Rig command: F 7083000 f
?
Rig command:?
Rig command: Frequency: 7083000
?
Rig command: F 7084000 f
?
Rig command:?
Rig command: Frequency: 7084000
?
Rig command: F 7085000 f
?
Rig command:?
Rig command: Frequency: 7085000
?
Rig command: F 7086000 f
?
Rig command:?
Rig command: Frequency: 7086000
?
Rig command: F 7087000 f
?
Rig command:?
Rig command: Frequency: 7087000
?
Rig command: F 7088000 f
?
Rig command:?
Rig command: Frequency: 7088000
?
Rig command: F 7089000 f
?
Rig command:?
Rig command: Frequency: 7089000
?
Rig command: F 7090000 f
?
Rig command:?
Rig command: Frequency: 7090000
Next, I tried something a little different. I used your F xxxxxxxx f commands, but followed each with two more f commands. Quisk started at 7090000 where the last test left it. Then Quisk correctly followed the F commands, as before. The most immediate read-back (f) was also correct, as before. However, responses to the second and third f commands were wrong and identical, though quisk remained tuned according to the most recent F command. I got bored, so did not run your whole list, but jumped around a bit. Errors could be plus or minus 1K, 10.5K or 20K. Here is the whole sequence: rigctl -m 10
?
Rig command: f
Frequency: 7091000
?
Rig command: F 7070000 f
?
Rig command:?
Rig command: Frequency: 7070000
?
Rig command: f
Frequency: 7050000
?
Rig command: f
Frequency: 7050000
?
Rig command: f
Frequency: 7050000
?
Rig command: F 7071000 f
?
Rig command:?
Rig command: Frequency: 7071000
?
Rig command: f
Frequency: 7072000
?
Rig command: F 7072000 f
?
Rig command:?
Rig command: Frequency: 7072000
?
Rig command: f
Frequency: 7073000
?
Rig command: f
Frequency: 7073000
?
Rig command: F 7073000 f
?
Rig command:?
Rig command: Frequency: 7073000
?
Rig command: f
Frequency: 7074000
?
Rig command: f
Frequency: 7074000
?
Rig command: F 7074000 f
?
Rig command:?
Rig command: Frequency: 7074000
?
Rig command: f
Frequency: 7075000
?
Rig command: f
Frequency: 7075000
?
Rig command: F 7075000 f
?
Rig command:?
Rig command: Frequency: 7075000
?
Rig command: f
Frequency: 7076000
?
Rig command: f
Frequency: 7076000
?
Rig command: F 7090000 f
?
Rig command:?
Rig command: Frequency: 7090000
?
Rig command: f
Frequency: 7105000
?
Rig command: f
Frequency: 7105000
?
Rig command: F 7089000 f
?
Rig command:?
Rig command: Frequency: 7089000
?
Rig command: f
Frequency: 7088000
?
Rig command: f
Frequency: 7088000
?
Rig command: F 7088000 f
?
Rig command:?
Rig command: Frequency: 7088000
?
Rig command: f
Frequency: 7087000
?
Rig command: f
Frequency: 7087000
?
Rig command: F 7087000 f
?
Rig command:?
Rig command: Frequency: 7087000
?
Rig command: f
Frequency: 7086000
?
Rig command: f
Frequency: 7086000
There was arbitrary jumping around in that last sequence, but consistencies emerged. Quisk always responded correctly to an F. The response to the first f immediately after the F (on the same command line) was always also correct. Responses to subsequent f commands (on new lines) were wrong and unchanging with repetition. These interactive command line experiments are interesting because of what works and what doesn't. However, unlike the interactive command line stuff, I seem to recall quisk did not necessarily respond correctly to set frequency commands from wsjtx via udp nor to a cat command sent through a virtual serial port. I also recall response times being highly variable by cat, whereas rigctl interactive command lines execute without perceptible delay. One bug could have cascading consequences, but to a person ignorant of the code construction of hamlib or quisk, it also seems there could be multiple issues. Do you have any more 32 bit experiments for me, or is it time to try the 64 bit OS? |
|
Re: Hamlib/rigctl compatibility?
With the first set, quisk does correctly follow the F command. There are errors on read-back. Here's the sequence:
~ $ rigctl -m 10
?
Rig command: F 7071000
?
Rig command: f
Frequency: 7067000
?
Rig command: F 7072000
?
Rig command: f
Frequency: 7073000
?
Rig command: F 7071000
?
Rig command: f
Frequency: 7070000
?
Rig command: F 7072000
?
Rig command: f
Frequency: 7073000
For the second sequence, quisk follows the F command correctly and the f (read-back) is consistently correct, too! Here is that sequence: ?
~ $ rigctl -m 10
?
Rig command: F 7070000 f
?
Rig command:?
Rig command: Frequency: 7070000
?
Rig command: F 7071000 f
?
Rig command:?
Rig command: Frequency: 7071000
?
Rig command: F 7072000 f
?
Rig command:?
Rig command: Frequency: 7072000
?
Rig command: F 7073000 f
?
Rig command:?
Rig command: Frequency: 7073000
?
Rig command: F 7074000 f
?
Rig command:?
Rig command: Frequency: 7074000
?
Rig command: F 7075000 f
?
Rig command:?
Rig command: Frequency: 7075000
?
Rig command: F 7076000 f
?
Rig command:?
Rig command: Frequency: 7076000
?
Rig command: F 7077000 f
?
Rig command:?
Rig command: Frequency: 7077000
?
Rig command: F 7078000 f
?
Rig command:?
Rig command: Frequency: 7078000
?
Rig command: F 7079000 f
?
Rig command:?
Rig command: Frequency: 7079000
?
Rig command: F 7080000 f
?
Rig command:?
Rig command: Frequency: 7080000
?
Rig command: F 7081000 f
?
Rig command:?
Rig command: Frequency: 7081000
?
Rig command: F 7082000 f
?
Rig command:?
Rig command: Frequency: 7082000
?
Rig command: F 7083000 f
?
Rig command:?
Rig command: Frequency: 7083000
?
Rig command: F 7084000 f
?
Rig command:?
Rig command: Frequency: 7084000
?
Rig command: F 7085000 f
?
Rig command:?
Rig command: Frequency: 7085000
?
Rig command: F 7086000 f
?
Rig command:?
Rig command: Frequency: 7086000
?
Rig command: F 7087000 f
?
Rig command:?
Rig command: Frequency: 7087000
?
Rig command: F 7088000 f
?
Rig command:?
Rig command: Frequency: 7088000
?
Rig command: F 7089000 f
?
Rig command:?
Rig command: Frequency: 7089000
?
Rig command: F 7090000 f
?
Rig command:?
Rig command: Frequency: 7090000
Next, I tried something a little different. I used your F xxxxxxxx f commands, but followed each with two more f commands. Quisk started at 7090000 where the last test left it. Then Quisk correctly followed the F commands, as before. The most immediate read-back (f) was also correct, as before. However, responses to the second and third f commands were wrong and identical, though quisk remained tuned according to the most recent F command. I got bored, so did not run your whole list, but jumped around a bit. Errors could be plus or minus 1K, 10.5K or 20K. Here is the whole sequence: rigctl -m 10
?
Rig command: f
Frequency: 7091000
?
Rig command: F 7070000 f
?
Rig command:?
Rig command: Frequency: 7070000
?
Rig command: f
Frequency: 7050000
?
Rig command: f
Frequency: 7050000
?
Rig command: f
Frequency: 7050000
?
Rig command: F 7071000 f
?
Rig command:?
Rig command: Frequency: 7071000
?
Rig command: f
Frequency: 7072000
?
Rig command: F 7072000 f
?
Rig command:?
Rig command: Frequency: 7072000
?
Rig command: f
Frequency: 7073000
?
Rig command: f
Frequency: 7073000
?
Rig command: F 7073000 f
?
Rig command:?
Rig command: Frequency: 7073000
?
Rig command: f
Frequency: 7074000
?
Rig command: f
Frequency: 7074000
?
Rig command: F 7074000 f
?
Rig command:?
Rig command: Frequency: 7074000
?
Rig command: f
Frequency: 7075000
?
Rig command: f
Frequency: 7075000
?
Rig command: F 7075000 f
?
Rig command:?
Rig command: Frequency: 7075000
?
Rig command: f
Frequency: 7076000
?
Rig command: f
Frequency: 7076000
?
Rig command: F 7090000 f
?
Rig command:?
Rig command: Frequency: 7090000
?
Rig command: f
Frequency: 7105000
?
Rig command: f
Frequency: 7105000
?
Rig command: F 7089000 f
?
Rig command:?
Rig command: Frequency: 7089000
?
Rig command: f
Frequency: 7088000
?
Rig command: f
Frequency: 7088000
?
Rig command: F 7088000 f
?
Rig command:?
Rig command: Frequency: 7088000
?
Rig command: f
Frequency: 7087000
?
Rig command: f
Frequency: 7087000
?
Rig command: F 7087000 f
?
Rig command:?
Rig command: Frequency: 7087000
?
Rig command: f
Frequency: 7086000
?
Rig command: f
Frequency: 7086000
There was arbitrary jumping around in that last sequence, but consistencies emerged. Quisk always responded correctly to an F. The response to the first f immediately after the F (on the same command line) was always also correct. Responses to subsequent f commands (on new lines) were wrong and unchanging with repetition. These interactive command line experiments are interesting because of what works and what doesn't. However, unlike the interactive command line stuff, I seem to recall quisk did not necessarily respond correctly to set frequency commands from wsjtx via udp nor to a cat command sent through a virtual serial port. I also recall response times being highly variable by cat, whereas rigctl interactive command lines execute without perceptible delay. One bug could have cascading consequences, but to a person ignorant of the code construction of hamlib or quisk, it also seems there could be multiple issues. Do you have any more 32 bit experiments for me, or is it time to try the 64 bit OS? |
|
Re: Hamlib/rigctl compatibility?
Mike Black
Yes -- let's try going back and forth to see if the error is consistent with frequency.
toggle quoted message
Show quoted text
And does quisk follow the set frequency correctly? F 7071000 f F 7072000 f F 7071000 f F 7072000 f Then...see? how the? error behaves with this. F 7070000 f F 7071000 f F 7072000 f F 7073000 f F 7074000 f F 7075000 f F 7076000 f F 7077000 f F 7078000 f F 7079000 f F 7080000 f F 7081000 f F 7082000 f F 7083000 f F 7084000 f F 7085000 f F 7086000 f F 7087000 f F 7088000 f F 7089000 f F 7090000 f On Sunday, August 20, 2023 at 06:40:58 PM CDT, ag5gt@... <ag5gt@...> wrote:
OK. Starting with quisk at 3903, as with previous tests, here's your first sequence: ~ $ rigctl -m 10 ? Rig command: f Frequency: 3903000 ? Rig command: F 7071000 ? Rig command: f Frequency: 7067000 ? Rig command: f Frequency: 7067000 ? Rig command: F 7072000 ? Rig command: f Frequency: 7073000 ? Rig command: f Frequency: 7073000 ? Each read-back has an error, and the error repeats with a follow-up read-back. I then kill rigctl and start again, with your incantation, with quisk still displaying 7072000. rigctl -m 10 --set-conf=cache_timeout=0 f 7073000 There is the 1K error again. Anything else? |
|
Re: Hamlib/rigctl compatibility?
OK. Starting with quisk at 3903, as with previous tests, here's your first sequence:
~ $ rigctl -m 10
?
Rig command: f
Frequency: 3903000
?
Rig command: F 7071000
?
Rig command: f
Frequency: 7067000
?
Rig command: f
Frequency: 7067000
?
Rig command: F 7072000
?
Rig command: f
Frequency: 7073000
?
Rig command: f
Frequency: 7073000
?
Each read-back has an error, and the error repeats with a follow-up read-back. I then kill rigctl and start again, with your incantation, with quisk still displaying 7072000.
rigctl -m 10 --set-conf=cache_timeout=0 f
7073000
There is the 1K error again. Anything else? ? |
|
Re: Hamlib/rigctl compatibility?
Mike Black
So the next question is what if you keep rigctl runn?
toggle quoted message
Show quoted text
rigctl -m 10 f F 7071000 f f F 7072000 f f Does Quisk follow and you get the right answers every time? One other possiblity rigctl -m 10 --set-conf=cache_timeout=0 f See? if that? makes a difference. Mike W9MDB On Sunday, August 20, 2023 at 01:24:31 PM CDT, ag5gt@... <ag5gt@...> wrote:
Mike, This is interesting. I fired up the rpi P400 and quisk, and did what you asked, though quisk was initially at 3903000 rather than 7060000. The response was correct. I then followed that with another query of quisk's frequency. I got the same wrong answer (7067000) as in previous tests. Here's the exact sequence: rigctl -m 10 f F 7071000 f 3903000 7071000 rigctl -m 10 f 7067000 I am poised to wipe the 32 bit OS and try re-building with 64 (a laborious process), but will hold off, if you need more experimentation with 32 here. Bruce |
|
Re: Hamlib/rigctl compatibility?
Just for grins, I did a couple more combinations where I set quisk's frequency on its display and then tried a read-back from rigctl . Here's the sequence:
Set quisk to 7072000, then: rigctl -m 10 f
7071000
rigctl -m 10 f 7071000
There was a consistent read-back error of 1khz in that case. Then, after I set quisk to 7080000: rigctl -m 10 f
7088000
rigctl -m 10 f 7088000
Again the read-back error is consistent, once it happens, until the next change at quisk's display. I'm no pro as a programmer, but when I encounter stuff like that, I go looking for a number type conversion problem. That's the sort of thing that can work on one version/revision of a compiler and not on another. ?
? |
|
Re: Hamlib/rigctl compatibility?
Mike,
This is interesting. I fired up the rpi P400 and quisk, and did what you asked, though quisk was initially at 3903000 rather than 7060000. The response was correct. I then followed that with another query of quisk's frequency. I got the same wrong answer (7067000) as in previous tests. Here's the exact sequence: rigctl -m 10 f F 7071000 f
3903000
7071000
rigctl -m 10 f
7067000
I am poised to wipe the 32 bit OS and try re-building with 64 (a laborious process), but will hold off, if you need more experimentation with 32 here. Bruce ? |
|
Re: Hamlib/rigctl compatibility?
Mike Black
I can't duplicate the problem here.? I get the actual frequency Quisk shows every time.
toggle quoted message
Show quoted text
So what happens with this.... rigctl -m 10 f F 7071000 f I get this... rigctl -m 10 f F 7071000 f 7060000 7071000 Mike On Saturday, August 19, 2023 at 11:05:39 PM CDT, ag5gt@... <ag5gt@...> wrote:
Mike, I'm replying to your message sent before Jim responded. First, your command line didn't work. I'm guessing you meant this, " rigctl -m 10 -vvvvv -Z f >log.txt 2>&1". The log file from that is attached. FYI, the computer and quisk had been shut down after this morning's test. Interestingly, powering up tonight and repeating the sequence produced the identical result: Quisk displays 7071000 and the read-back from rigctl reports 7067000. Perhaps I should remind everybody this problem shows up on a Raspberry Pi P400 while running the 32 bit version of the Pi OS. Could we have a bug that is hardware or compiler specific? Bruce ag5gt |
|
Re: Hamlib/rigctl compatibility?
Mike,
I'm replying to your message sent before Jim responded. First, your command line didn't work. I'm guessing you meant this, " rigctl -m 10 -vvvvv -Z f >log.txt 2>&1". The log file from that is attached. FYI, the computer and quisk had been shut down after this morning's test. Interestingly, powering up tonight and repeating the sequence produced the identical result: Quisk displays 7071000 and the read-back from rigctl reports 7067000. Perhaps I should remind everybody this problem shows up on a Raspberry Pi P400 while running the 32 bit version of the Pi OS. Could we have a bug that is hardware or compiler specific? Bruce ag5gt |
|
Re: Hamlib/rigctl compatibility?
Mike Black
I need to know what the problem is..... What's not working?? I'm lost now in this thread.
On Friday, August 18, 2023 at 12:50:23 PM CDT, jimahlstrom <jahlstr@...> wrote:
I downloaded Hamlib 4.6~git and built rigctl. I tested rigctl with my Quisk 4.2.22 using model 10. The "F" and "f" commands worked fine. This is still on Ubuntu 64-bit. I can alter Quisk's Hamlib code if it makes it more convenient for the Hamlib community, but I need a description of what to change. And I have struggled to find documentation. Jim N2ADR |
|
Re: Hamlib/rigctl compatibility?
I downloaded Hamlib 4.6~git and built rigctl. I tested rigctl with my Quisk 4.2.22 using model 10. The "F" and "f" commands worked fine. This is still on Ubuntu 64-bit.
I can alter Quisk's Hamlib code if it makes it more convenient for the Hamlib community, but I need a description of what to change. And I have struggled to find documentation. Jim N2ADR |
to navigate to use esc to dismiss