I think that @eliggett was being polite, when I emailed him about possibly testing his software with wfview, he told me that I was welcome to purchase a copy. I wasn’t “that” interested.
My guess is that wfview isn’t configured correctly. Most likely you haven’t enabled CI-V transceive on your radio and have specified a manual CI-V address in settings?
C-IV transceive has been on and I have no need to change the CI-V address from the default on any of my radios. Been using your software to control my IC-7300 for over a year just upgraded to v2 today. I run my station remote full time (radios are in a closet) so I use your software daily.
And yeah I get it, the iPad software is not cheap (shoot you have to pay for it twice if you want it on your iPhone & iPad). There is no expectation that this works but it did work on the v1 beta why I bring it up. I would be happy to donate the $50 if you have access to an iPad and wanted to look into it more then what I can do.
Phil,
The good news is that the serial feature is working. Thank you!
However, 2.03 is not usable for me yet. There’s some kind of crackling and popping being introduced into the TX audio that makes it sound bad. The waterfall when transmitting also shows the noise both on wfview and the radio itself.
I did not have this issue with the previous version.
I did not try 2.01 as I was with guests at the house and missed trying that one.
Also, the Data mode indicator keeps flipping back and forth from Data 1 to Data Off all by itself.
Anything I can try?
Turning down the TX audio does not change the noise.
Wired network. Windows 11. Running x64 version. Freshly rebooted PC and radio.
I can submit a quick video of what it sounds like if you so desire.
Rob KW2E
Phil,
Rob/Kw2e,
You may wish to disconnect and try one of the other audio systems (QtAudio, PortAudio, and RT Audio). Sometimes clicking sounds are created by audio device issues and switching systems helps.
You should also check your Log within wfview for dropped packet notices, as these can make strange sounds sometimes.
–E
de W6EL
Elliot,
I did try those, same result. Thanks for the suggestion though. On the older version of wfview I have been running for the last few hours I have:
Attaching the log from 2.03
Rob KW2E
wfview-20250104205839.log (1.36 MB)
that issue of noise, I have seen before and was due to my level settings of the mike, always.
1 Like
Looking through the code, it does look like the CI-V address isn’t being sent in the correct way, this doesn’t effect wfview clients as we actually query the rig CI-V port for this directly. I will fix this.
Phil
1 Like
Roeland,
I have made no changes to the mic settings on the radio between the old version and this one. And the noise persists regardless of how much TX audio I am using. I can turn down the TX audio in wfview, no difference. Turning down the audio in WSJT-X, no difference.
Setting the LAN modulation level in the radio to 60%, no change. Setting LAN modulation level in the radio to 30%, no change. Nor does a combination of the audio settings in the software and the radio make any difference.
The noise persists regardless of audio settings.
Thanks,
Rob KW2E
The vast majority of changes to wfview in v2 are related to rig-control, the method of connecting to network radios has not really changed at all, so not sure why you would be seeing this?
A few observations from your log:
- I see that you have the UDP Server enabled, why? This is only for USB connected radios
- It looks like you are using a single Virtual Audio Cable for both TX and RX audio. While this ‘may’ work, it is absolutely not supported as it can result in RX audio being fed back into TX. The fix for this is to purchase the commercial version of VAC (or similar software) that supports multiple ‘cables’.
- I can see lots of ‘unsupported command’ messages in the log, while this shouldn’t cause a problem, it suggests that you might have features enabled on your radio that we aren’t aware of. Most of the development of v2 was done using an IC-7610 so these are quite surprising. In extreme cases, the sheer number of logged messages ‘could’ cause audio glitching. I will look through your log and add those commands to wfview though.
Phil
Phil,
Thanks for your input. I created a second virtual audio cable and made the appropriate changes to the software and I no longer see the noise. Great call. Strange that It would be working fine with the older version.
As for the server settings, I don’t know why that was enabled but it is disabled now.
Thanks again,
Rob KW2E
That’s great. Not sure why it worked before, it could be a timing issue, but separate ‘cables’ has always been our recommendation for this reason.
I am very intrigued by your log though. Some of those unknown commands are really obscure and the radio would never send them ‘unsolicited’ (Like external monitor resolution and NB width/depth) so you have anything else connected to the CAT or USB ports on your radio?
1 Like
Phil,
Nothing is connected to the radio other than the lan cable. I was using Ham Radio Deluxe and that could be what is causing those errors in the log. I shut it down and set WSJT-X to control the rig direct and all the log errors stopped.
Thanks,
Rob KW2E
Thanks Phil! Looking forward to the next update.