Hamlib error -- running WFview for 7300, RPi3B+, JS8CALL

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.

Not sure what to do. Thanks for any advice. 73.

Jonathan, KK7PW

1 Like

Hi Jonathan,

What OS?

–Elliott
de W6EL

Current Raspian OS. Also with current sudo apt-get updates.

Hi Jonathan,

That should have been obvious to me since you are on a Pi!

You’re connecting to the rig using the wfview pseudo-terminal, correct?

Can you send me a logfile from when wfview is running and JS8CALL throws the error?

If the log file is enormous, delete the log file, and then run wfview and JS8 to generate a fresh one.

Thanks,

–E
de W6EL

Will do. More soon. Thanks.

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)

git submodule init
git submodule update

73 Phil M0VSE

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?

Thanks again.

de KK7PW

Elliot – here is my Log File:

2021-06-11 13:44:06.728 INF system: Starting wfview
2021-06-11 13:44:12.789 INF system: Loading settings from “/home/pi/.config/wfview/wfview.conf”
2021-06-11 13:44:12.808 INF gui: Got Audio Output: “alsa_output.platform-bcm2835_audio.analog-stereo”
2021-06-11 13:44:12.808 INF gui: Got Audio Input: “alsa_output.platform-bcm2835_audio.analog-stereo.monitor”
2021-06-11 13:44:12.813 INF default: Getting server config
2021-06-11 13:44:12.821 INF default: setState 1
2021-06-11 13:44:12.826 INF default: setState 0
2021-06-11 13:44:12.827 INF default: setState 1
2021-06-11 13:44:12.835 INF system: Could not find Icom serial port. Falling back to OS default. Use --port to specify, or modify preferences.
2021-06-11 13:44:12.840 INF serial: Opened port: “/dev/ttyUSB0”
2021-06-11 13:44:12.841 INF serial: Opened pt device: 19 , attempting to grant pt status
2021-06-11 13:44:12.843 INF serial: Opened pseudoterminal, slave name : /dev/pts/1
2021-06-11 13:44:12.844 INF serial: Created link to “/dev/pts/1” from “/home/pi/rig-pty1”
2021-06-11 13:44:13.793 INF system: Received CommReady!!
2021-06-11 13:44:17.861 INF system: Skipping automatic CIV, using user-supplied value of 148
2021-06-11 13:44:17.867 INF rig: Have rig ID: decimal: 148
2021-06-11 13:44:18.034 INF system: Delay command interval timing: 70 ms
2021-06-11 13:44:18.034 INF system: Periodic polling timer: 35 ms
2021-06-11 13:44:19.932 INF rig: Received 0x15 center span data: for frequency 5000
2021-06-11 13:44:22.326 INF rig: Received 0x15 center span data: for frequency 5000
2021-06-11 13:44:54.625 INF serial: pty detected remote CI-V: e0
2021-06-11 13:45:31.506 INF default: setState 3
2021-06-11 13:45:34.210 INF default: setState 0
2021-06-11 13:46:19.041 INF default: setState 3
2021-06-11 13:46:29.098 INF default: setState 0
2021-06-11 13:48:04.662 INF default: setState 3
2021-06-11 13:48:16.027 INF default: setState 0
2021-06-11 13:49:48.006 INF default: setState 3
2021-06-11 13:50:00.031 INF default: setState 0
2021-06-11 13:52:48.642 INF default: setState 3
2021-06-11 13:52:59.521 INF default: setState 0
2021-06-11 13:53:01.502 INF default: setState 3
2021-06-11 13:53:14.525 INF default: setState 0
2021-06-11 13:53:18.155 INF default: setState 3
2021-06-11 13:53:30.021 INF default: setState 0
2021-06-11 13:53:31.000 INF default: setState 3
2021-06-11 13:53:45.024 INF default: setState 0
2021-06-11 13:53:48.002 INF default: setState 3
2021-06-11 13:54:00.031 INF default: setState 0
2021-06-11 13:54:01.005 INF default: setState 3
2021-06-11 13:54:30.017 INF default: setState 0

Hi Jonathan,

I am assuming you followed the instructions at INSTALL.md · master · Elliott Liggett / wfview · GitLab

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

73 Phil M0VSE

Thanks, Phil. I did the update and still getting the error message. Will keep working on this.

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.

  1. de KK7PW

Well, typed too soon. Error returned. But functional.

Hi Jonathan.

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

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?

73 Phil M0VSE

Thanks, Phil. Yes, JS8 allows for that adjustment as well. Will try it out.

Thanks again. 73.

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”

Thanks,

Bill
W4BRZ