Hello. My CAT control and RX / TX seems to work fine. Just getting this persistent pop-up “Rig Control Error – Hamlib error: Command rejected by the rig while getting current VFO frequency.”
I have tried CI-V unlink / link changes, CI-V Transceive on / off, CI-V Baud Rate on 19200 / Auto, and currently running at USB baud rate at 115200.
This ‘May’ be an issue that I (hopefully) fixed yesterday when sometimes CI-V packets addressed to wfview itself escape through the pty device when they should be filtered.
Unfortunately, Hamlib isn’t at all tolerant of receiving packets that it isn’t expecting (even ones not addressed to Hamlib) and it generates this kind of error.
If you pull the latest master (from today) and rebuild. It should have the fix.
You will also need to run these commands from the source directory as I have added a couple of sub modules)
thanks, Phil. I am limited in my linux knowledge. If I WGET the new build and install, will it overwrite the existing? Can you offer the basic commands to do so?
cd wfview (or wherever you downloaded the source to)
git pull (this will get the latest updates)
git submodule init
git submodule update
cd ../build
qmake ../wfview/wfview.pro
make
sudo ./install.sh
Update – been running fine this afternoon with no errors so far. Perhaps simply restarting occasionally will clear the cobwebs. Currently on JS8 20m.
Thanks for a great program. If you are collecting ideas for future updates, wonder if it would be possible to include Club Log (or some other service) spots in the spectrum scope. Could be handy. Just a thought.
Yes we have an idea of ‘overlays’ that can be superimposed on the spectrum scope, these can include band edge markers, cluster spots, memory locations and anything else that we can think of
I haven’t tried JS8Call but the most recent version seems to work much better on WSJT-X, I also changed the polling frequency to 2 seconds (from 1 second) and that seemed to help, I’m not sure if JS8Call has this option?
In JS8, changed my polling freq to 4 seconds. Seems like it could be a latency issue with my older 3B+ that may be tripping up Hamlib. Fingers crossed.
I am having the same issue using WFview controlling an IC-7300 with an M1 Mac Mini. I get the same issue with JS8 running direct too. I know this is not a WFview issue, it works great. I am not running any other application.
I am posting here since it was mentioned on this post.
The message log says “ Hamlib error: Command rejected by the rig while getting current VFO frequency”