Bad behavior on startup

Bugs
1

I was listening to some guys chatting on 40m SSBa while ago. Then decided to move down to the CW portion. When I did, I could still here the guys in LSB and they’re appeared on the waterfall, even though the correct frequency in the CW portion was shown in the VFO display and along the bottom of the waterfall.

I shut down wfview and restarted it. When it starts again I click Power On to start my 7300 and after a few seconds I can hear audio but nothing on the spectrum or waterfall displays (Enable WF checkbox is already checked).

The VFO shows all zeros and the numbers 0 through 5 are displayed across the bottom of the spectrum and waterfall displays. I double clicked at a random location on the waterfall and got WWV on 2.5 MHz, which I guess is where I clicked. 2.5 MHz is properly displayed on the VFO, but the spectrum and waterfall displays still don’t show anything.

None of the buttons in the row just below the waterfall have started the displays back up.

Disconnecting and reconnecting to the radio don’t help. Neither does cycling to power OFF and back ON.

wfview 1.64 is running on an i3 NUC with 16 Gbytes of RAM, under Windows 11. Connection is via USB.

I’m stumped. I don’t know how to get it to behave as it should.

73,
Ken Alexander VE3HLS

2

It kind of seems like the radio’s serial port (over USB) is not working. Check the wfview log and see what it may say about it.

–E
de W6EL

3

Hi Elliott,

We’re very quickly leaving my area of expertise here. I have copied the logfile into this message in hopes that you can make sense of it.

2023-08-09 08:47:32.718 INF system: “wfview version: 1.64 (Git:b4c079f on Jul 16 2023 at 14:29:30 by build@wfview.org). Operating System: Windows 11 Version 22H2 (x86_64). Build Qt Version 6.5.1. Current Qt Version: 6.5.1”
2023-08-09 08:47:32.765 INF system: Loading settings from “\HKEY_CURRENT_USER\Software\wfview\wfview”
2023-08-09 08:47:32.812 INF gui: Got Audio Output from Settings: “Speakers (USB Audio CODEC )”
2023-08-09 08:47:32.812 INF gui: Got Audio Input from Settings: “Microphone (USB Audio CODEC )”
2023-08-09 08:47:32.834 INF audio: Audio device(s) found (*=default)
2023-08-09 08:47:32.852 INF audio: * ( 0 ) Input Device : “Microphone (USB Audio CODEC )”
2023-08-09 08:47:32.853 INF audio: ( 1 ) Input Device : “CABLE Output (VB-Audio Virtual Cable)”
2023-08-09 08:47:32.859 INF audio: * ( 0 ) Output Device : “Speakers (USB Audio CODEC )”
2023-08-09 08:47:32.859 INF audio: ( 1 ) Output Device : “CABLE Input (VB-Audio Virtual Cable)”
2023-08-09 08:47:32.859 INF audio: ( 2 ) Output Device : “28E850 (Intel(R) Display Audio)”
2023-08-09 08:47:32.859 INF default: Looking for inputs
2023-08-09 08:47:32.860 INF audio: "Client Audio input device Microphone (USB Audio CODEC ) found! "
2023-08-09 08:47:32.861 INF default: Looking for outputs
2023-08-09 08:47:32.862 INF audio: "Client Audio output device Speakers (USB Audio CODEC ) found! "
2023-08-09 08:47:32.864 INF audio: "Server Audio input device Microphone (USB Audio CODEC ) found! "
2023-08-09 08:47:32.865 INF audio: "Server Audio output device Speakers (USB Audio CODEC ) found! "
2023-08-09 08:47:32.892 INF system: Cannot prepare WF view without rigCaps. Waiting on this.
2023-08-09 08:47:32.892 INF system: Cannot prepare WF view without rigCaps. Waiting on this.
2023-08-09 08:47:32.914 INF rig: creating instance of rigCommander()
2023-08-09 08:47:32.915 INF cluster: starting dxClusterClient()
2023-08-09 08:47:32.915 INF udp.server: Starting udp server
2023-08-09 08:47:32.915 INF audio: Audio Input device “Microphone (USB Audio CODEC )”
2023-08-09 08:47:32.915 INF audio: Audio Output device “Speakers (USB Audio CODEC )”
2023-08-09 08:47:32.921 INF serial: Opened port: “COM3”
2023-08-09 08:47:32.936 INF udp.server: My IP Address: “192.168.2.19”
2023-08-09 08:47:32.936 INF udp.server: Server Binding Control to: 50001
2023-08-09 08:47:32.944 INF udp.server: Server Binding CIV to: 50002
2023-08-09 08:47:32.944 INF udp.server: Server Binding Audio to: 50003
2023-08-09 08:47:33.011 INF system: Received CommReady!!
2023-08-09 08:47:33.011 INF system: Delay command interval timing: 75 ms
2023-08-09 08:47:33.011 INF system: Skipping automatic CIV, using user-supplied value of 148
2023-08-09 08:47:33.011 INF system: Skipping Rig ID query, using user-supplied model from CI-V address: 148
2023-08-09 08:47:33.011 INF default: Setting rig state for wfmain
2023-08-09 08:47:33.011 INF rig: Setting rig ID to: (int) 148
2023-08-09 08:47:33.011 INF rig: Using incomingCIVAddr: (int): 148 hex: “0x94”
2023-08-09 08:47:33.011 INF serial: Received rigCapabilities for “IC-7300”
2023-08-09 08:47:33.023 INF system: Delay command interval timing: 25 ms
2023-08-09 08:49:10.119 INF serial: Opened port: “COM3”

73,
Ken Alexander VE3HLS

4

This is likely your problem

2023-08-09 08:47:33.011 INF system: Skipping automatic CIV, using user-supplied value of 148
2023-08-09 08:47:33.011 INF system: Skipping Rig ID query, using user-supplied model from CI-V address: 148

Please DO NOT specify a CIV address, this is ONLY for very old radios that do not support CIV Transceive. You must enable CIV transceive on the radio and select auto CIV address for wfview to work correctly.

Phil

5

Hi Phil!

Many thanks! That did it! There are two checkboxes to do with CIV. I unchecked them both, tweaked the display settings and got my spectrum and waterfall back. I think I was looking through the settings late yesterday, came across them and said “Those two ought to be checked”…but I guess not.

I hear you have some impressive things in store for future releases. Can’t wait to see them! thanks for all your good work and thanks for the quick response on this in particular.

73,
Ken Alexander VE3HLS

6

these two boxes only are used in the event that it cannot detect the rig at all. Most of the time, when needed it is because of misconfigured rigs.

normally spoken they should NOT be touched.