ICOM IC-7410 Wfview shuts down shortly after opening

Bugs
1

Hello,

I’m using an ICOM IC-7410 on Windows 11 64, and version 1.62 of Wfview.

I opened the software and set the COM port and baud rate, closed down and now everytime I start up the program opens, then after around 5 seconds it closes.

Please find the debug file. As a new user I can’t attach files. Please let me know if you need any further information.

Many thanks.

Peter

2023-05-06 09:28:38.863 INF system: "wfview version: 1.62 (Git:3fa14eb on Mar 12 2023 at 15:51:31 by build@wfview.org). Operating System: Windows 11 Version 2009 (x86_64). Build Qt Version 6.3.2. Current Qt Version: 6.3.2"
2023-05-06 09:28:38.878 DBG system: Running with debugging options enabled.
2023-05-06 09:28:38.893 INF system: Loading settings from  "\\HKEY_CURRENT_USER\\Software\\wfview\\wfview"
2023-05-06 09:28:38.940 INF gui: Got Audio Output from Settings:  "Speakers (Realtek(R) Audio)"
2023-05-06 09:28:38.940 INF gui: Got Audio Input from Settings:  "Stereo Mix (Realtek(R) Audio)"
2023-05-06 09:28:38.972 INF cw: "Sidetone Output: Speakers (2- USB Audio CODEC ) (volume: 0 rate: 44100 type: 2"
2023-05-06 09:28:38.987 INF audio: Audio device(s) found (*=default)
2023-05-06 09:28:38.987 INF audio: * ( 0 ) Input Device :  "Microphone (2- USB Audio CODEC )"
2023-05-06 09:28:38.987 INF audio:   ( 1 ) Input Device :  "Stereo Mix (Realtek(R) Audio)"
2023-05-06 09:28:38.987 INF audio:   ( 2 ) Input Device :  "Microphone (Realtek(R) Audio)"
2023-05-06 09:28:38.987 INF audio: * ( 0 ) Output Device :  "Speakers (2- USB Audio CODEC )"
2023-05-06 09:28:38.987 INF audio:   ( 1 ) Output Device :  "Realtek Digital Output (Realtek(R) Audio)"
2023-05-06 09:28:38.987 INF audio:   ( 2 ) Output Device :  "5 - Q3279WG5B (AMD High Definition Audio Device)"
2023-05-06 09:28:38.987 INF audio:   ( 3 ) Output Device :  "Speakers (Realtek(R) Audio)"
2023-05-06 09:28:38.987 INF audio:   ( 4 ) Output Device :  "6 - Q3279WG5B (AMD High Definition Audio Device)"
2023-05-06 09:28:38.987 INF default: Looking for inputs
2023-05-06 09:28:38.987 INF audio: "Client Audio input device Stereo Mix (Realtek(R) Audio) found! "
2023-05-06 09:28:38.987 DBG gui: Changed audio input to: "Stereo Mix (Realtek(R) Audio)"
2023-05-06 09:28:38.987 INF default: Looking for outputs
2023-05-06 09:28:38.987 INF audio: "Client Audio output device Speakers (Realtek(R) Audio) found! "
2023-05-06 09:28:38.987 DBG gui: Changed audio output to: "Speakers (Realtek(R) Audio)"
2023-05-06 09:28:39.003 INF audio: "Server Audio input device Stereo Mix (Realtek(R) Audio) found! "
2023-05-06 09:28:39.003 INF audio: "Server Audio output device Speakers (Realtek(R) Audio) found! "
2023-05-06 09:28:39.003 DBG system: Audio devices done.
2023-05-06 09:28:39.003 DBG system: Running setUIToPrefs()
2023-05-06 09:28:39.110 INF system: Cannot prepare WF view without rigCaps. Waiting on this.
2023-05-06 09:28:39.110 DBG system: Running setInititalTiming()
2023-05-06 09:28:39.110 DBG system: Running openRig()
2023-05-06 09:28:39.110 INF rig: creating instance of rigCommander()
2023-05-06 09:28:39.110 DBG system: Running rigConnections()
2023-05-06 09:28:39.110 INF cluster: starting dxClusterClient()
2023-05-06 09:28:39.282 INF serial: Opened port:  "COM8"
2023-05-06 09:28:39.282 INF system: Received CommReady!! 
2023-05-06 09:28:39.282 INF system: Delay command interval timing:  75 ms
2023-05-06 09:28:39.282 INF default: Setting rig state for wfmain
2023-05-06 09:28:39.282 DBG rig: Caught it! Found the echo'd broadcast request from us! Rig has not responded to broadcast query yet.
2023-05-06 09:28:39.298 DBG rigTraffic: Received from radio:
2023-05-06 09:28:39.298 DBG rigTraffic: "---- Begin hex dump -----:"
2023-05-06 09:28:39.298 DBG rigTraffic: "DATA:  19 00 80 fd "
2023-05-06 09:28:39.298 DBG rigTraffic: "INDEX: 00 01 02 03 "
2023-05-06 09:28:39.298 DBG rigTraffic: "----  End hex dump  -----"
2023-05-06 09:28:39.298 DBG rig: ---Rig FOUND from broadcast query:
2023-05-06 09:28:39.298 INF rig: Using incomingCIVAddr: (int):  128  hex:  "0x80"
2023-05-06 09:28:39.298 INF serial: Received rigCapabilities for "IC-7410"
2023-05-06 09:28:39.298 INF rig: Have rig ID: decimal:  128
2023-05-06 09:28:39.298 DBG system: Rig name:  "IC-7410"
2023-05-06 09:28:39.298 DBG system: Has LAN capabilities:  false
2023-05-06 09:28:39.298 DBG system: Rig ID received into wfmain: spectLenMax:  0
2023-05-06 09:28:39.298 DBG system: Rig ID received into wfmain: spectAmpMax:  0
2023-05-06 09:28:39.298 DBG system: Rig ID received into wfmain: spectSeqMax:  0
2023-05-06 09:28:39.298 DBG system: Rig ID received into wfmain: hasSpectrum:  false
2023-05-06 09:28:39.313 INF system: Delay command interval timing:  25 ms
2023-05-06 09:28:39.313 DBG default: Inserting 3 To slow queue, priority 128 len 0
2023-05-06 09:28:39.313 DBG default: Inserted 3 To slow queue, priority 128 len 1
2023-05-06 09:28:39.313 DBG default: Inserting 5 To slow queue, priority 128 len 1
2023-05-06 09:28:39.313 DBG default: Inserted 5 To slow queue, priority 128 len 2
2023-05-06 09:28:39.313 DBG default: Inserting 44 To slow queue, priority 128 len 2
2023-05-06 09:28:39.313 DBG default: Inserted 44 To slow queue, priority 128 len 3
2023-05-06 09:28:39.313 DBG default: Inserting 47 To slow queue, priority 128 len 3
2023-05-06 09:28:39.313 DBG default: Inserted 47 To slow queue, priority 128 len 4
2023-05-06 09:28:39.313 DBG default: Inserting 17 To slow queue, priority 128 len 4
2023-05-06 09:28:39.313 DBG default: Inserted 17 To slow queue, priority 128 len 5
2023-05-06 09:28:39.313 DBG default: Inserting 88 To slow queue, priority 128 len 5
2023-05-06 09:28:39.313 DBG default: Inserted 88 To slow queue, priority 128 len 6
2023-05-06 09:28:39.313 DBG default: Inserting 44 To slow queue, priority 128 len 6
2023-05-06 09:28:39.313 DBG default: Inserted 44 To slow queue, priority 128 len 7
2023-05-06 09:28:39.313 DBG default: Inserting 87 To slow queue, priority 128 len 7
2023-05-06 09:28:39.313 DBG default: Inserted 87 To slow queue, priority 128 len 8
2023-05-06 09:28:39.313 DBG default: Inserting 53 To slow queue, priority 128 len 8
2023-05-06 09:28:39.313 DBG default: Inserted 53 To slow queue, priority 128 len 9
2023-05-06 09:28:39.313 DBG default: Removing 62 From periodic queue, len 9
2023-05-06 09:28:39.313 DBG default: Removed 62 From periodic queue, len 9
2023-05-06 09:28:39.407 DBG rigTraffic: Final payload in rig commander to be sent to rig: 
2023-05-06 09:28:39.407 DBG rigTraffic: "---- Begin hex dump -----:"
2023-05-06 09:28:39.407 DBG rigTraffic: "DATA:  fe fe 80 e1 03 fd "
2023-05-06 09:28:39.407 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 "
2023-05-06 09:28:39.407 DBG rigTraffic: "----  End hex dump  -----"
2023-05-06 09:28:39.438 DBG rigTraffic: Received from radio:
2023-05-06 09:28:39.438 DBG rigTraffic: "---- Begin hex dump -----:"
2023-05-06 09:28:39.438 DBG rigTraffic: "DATA:  03 00 00 03 05 80 e1 15 02 fd "
2023-05-06 09:28:39.438 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 07 08 09 "
2023-05-06 09:28:39.438 DBG rigTraffic: "----  End hex dump  -----"
2023-05-06 09:28:39.470 DBG rigTraffic: Final payload in rig commander to be sent to rig: 
2023-05-06 09:28:39.470 DBG rigTraffic: "---- Begin hex dump -----:"
2023-05-06 09:28:39.470 DBG rigTraffic: "DATA:  fe fe 80 e1 04 fd "
2023-05-06 09:28:39.470 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 "
2023-05-06 09:28:39.470 DBG rigTraffic: "----  End hex dump  -----"
2023-05-06 09:28:39.532 DBG rigTraffic: Final payload in rig commander to be sent to rig: 
2023-05-06 09:28:39.532 DBG rigTraffic: "---- Begin hex dump -----:"
2023-05-06 09:28:39.532 DBG rigTraffic: "DATA:  fe fe 80 e1 03 fd "
2023-05-06 09:28:39.532 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 "
2023-05-06 09:28:39.532 DBG rigTraffic: "----  End hex dump  -----"
2023-05-06 09:28:39.548 DBG rigTraffic: Received from radio:
2023-05-06 09:28:39.548 DBG rigTraffic: "---- Begin hex dump -----:"
2023-05-06 09:28:39.548 DBG rigTraffic: "DATA:  03 00 00 03 15 00 fd "
2023-05-06 09:28:39.548 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-05-06 09:28:39.548 DBG rigTraffic: "----  End hex dump  -----"
2023-05-06 09:28:39.595 DBG rigTraffic: Final payload in rig commander to be sent to rig: 
2023-05-06 09:28:39.595 DBG rigTraffic: "---- Begin hex dump -----:"
2023-05-06 09:28:39.595 DBG rigTraffic: "DATA:  fe fe 80 e1 04 fd "
2023-05-06 09:28:39.595 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 "
2023-05-06 09:28:39.595 DBG rigTraffic: "----  End hex dump  -----"
2023-05-06 09:28:39.610 DBG rigTraffic: Received from radio:
2023-05-06 09:28:39.610 DBG rigTraffic: "---- Begin hex dump -----:"
2023-05-06 09:28:39.610 DBG rigTraffic: "DATA:  04 05 01 fd "
2023-05-06 09:28:39.610 DBG rigTraffic: "INDEX: 00 01 02 03 "
2023-05-06 09:28:39.610 DBG rigTraffic: "----  End hex dump  -----"
2023-05-06 09:28:39.610 DBG default: Removing 29 From periodic queue, len 9
2023-05-06 09:28:39.610 DBG default: Removed 29 From periodic queue, len 9
2023-05-06 09:28:39.610 DBG default: Removing 25 From periodic queue, len 9
2023-05-06 09:28:39.610 DBG default: Removed 25 From periodic queue, len 9
2023-05-06 09:28:39.610 DBG default: Removing 27 From periodic queue, len 9
2023-05-06 09:28:39.610 DBG default: Removed 27 From periodic queue, len 9
2023-05-06 09:28:39.720 DBG rigTraffic: Final payload in rig commander to be sent to rig: 
2023-05-06 09:28:39.720 DBG rigTraffic: "---- Begin hex dump -----:"
2023-05-06 09:28:39.720 DBG rigTraffic: "DATA:  fe fe 80 e1 03 fd "
2023-05-06 09:28:39.720 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 "
2023-05-06 09:28:39.720 DBG rigTraffic: "----  End hex dump  -----"
2023-05-06 09:28:39.735 DBG rigTraffic: Received from radio:
2023-05-06 09:28:39.735 DBG rigTraffic: "---- Begin hex dump -----:"
2023-05-06 09:28:39.735 DBG rigTraffic: "DATA:  03 00 00 03 15 00 fd "
2023-05-06 09:28:39.735 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-05-06 09:28:39.735 DBG rigTraffic: "----  End hex dump  -----"
2023-05-06 09:28:39.782 DBG rigTraffic: Final payload in rig commander to be sent to rig: 
2023-05-06 09:28:39.782 DBG rigTraffic: "---- Begin hex dump -----:"
2023-05-06 09:28:39.782 DBG rigTraffic: "DATA:  fe fe 80 e1 04 fd "
2023-05-06 09:28:39.782 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 "
2023-05-06 09:28:39.782 DBG rigTraffic: "----  End hex dump  -----"
2023-05-06 09:28:39.798 DBG rigTraffic: Received from radio:
2023-05-06 09:28:39.798 DBG rigTraffic: "---- Begin hex dump -----:"
2023-05-06 09:28:39.798 DBG rigTraffic: "DATA:  04 05 01 fd "
2023-05-06 09:28:39.798 DBG rigTraffic: "INDEX: 00 01 02 03 "
2023-05-06 09:28:39.798 DBG rigTraffic: "----  End hex dump  -----"
2023-05-06 09:28:39.845 DBG rigTraffic: Final payload in rig commander to be sent to rig: 
2023-05-06 09:28:39.845 DBG rigTraffic: "---- Begin hex dump -----:"
2023-05-06 09:28:39.845 DBG rigTraffic: "DATA:  fe fe 80 e1 1a 06 fd "
2023-05-06 09:28:39.845 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-05-06 09:28:39.845 DBG rigTraffic: "----  End hex dump  -----"
2023-05-06 09:28:39.860 DBG rigTraffic: Received from radio:
2023-05-06 09:28:39.860 DBG rigTraffic: "---- Begin hex dump -----:"
2023-05-06 09:28:39.860 DBG rigTraffic: "DATA:  1a 06 00 00 fd "
2023-05-06 09:28:39.860 DBG rigTraffic: "INDEX: 00 01 02 03 04 "
2023-05-06 09:28:39.860 DBG rigTraffic: "----  End hex dump  -----"
2023-05-06 09:28:39.907 DBG rigTraffic: Final payload in rig commander to be sent to rig: 
2023-05-06 09:28:39.907 DBG rigTraffic: "---- Begin hex dump -----:"
2023-05-06 09:28:39.907 DBG rigTraffic: "DATA:  fe fe 80 e1 fd "
2023-05-06 09:28:39.907 DBG rigTraffic: "INDEX: 00 01 02 03 04 "
2023-05-06 09:28:39.907 DBG rigTraffic: "----  End hex dump  -----"
2

Seems to be resolved by installing the 32bit version. Would be nice to be able to use the 64bit version at some point. Thanks

3

Did you install the right icom drivers before you connected it to your windows 11 system?

And generally I think that using 32 bit is not the solution.

4

Hi, yes I did. V 1.3. I noticed there were similar issues reported.

5

Hi Peter.

That reply of mine has nothing to do with a possible 32/64 bit issue and was regarding adding manually keyed CW.

The vast majority of Windows users are successfully using the 64bit version and I have never been able to replicate this issue (so far we have only received 2 reports including yours)

The main difference between the 32bit and 64bit versions of wfview, is the version of the underlying framework (Qt) that we use. In the 64bit version, we are using Qt6, it is likely that your machine has some incompatibility with this version of Qt, but it is almost impossible to say what/where.

The next release of wfview will use a newer version of Qt6 so it is worth waiting for that and try the 64bit version again.

73 Phil M0VSE

6

Thanks for the clarification Phil

I tested on another W11 machine (this time a laptop) and had exactly the same experience.

In both cases if I run without the USB cable connected it does not crash.

Will test the next version as you suggest.

Thanks

Peter 2E0LRZ

7

I’m not sure if these logs from Event Viewer help Phil?

Faulting application name: wfview.exe, version: 0.0.0.0, time stamp: 0x640df66d
Faulting module name: wfview.exe, version: 0.0.0.0, time stamp: 0x640df66d
Exception code: 0xc0000005
Fault offset: 0x00000000000c2444
Faulting process ID: 0x0x1648
Faulting application start time: 0x0x1D97FF77F7B1F50
Faulting application path: C:\Program Files\wfview\wfview.exe
Faulting module path: C:\Program Files\wfview\wfview.exe
Report ID: 19cf7dd6-f59b-496f-9be6-d0cf05b1c8fc
Faulting package full name: 
Faulting package-relative application ID:

I tried this afternoon on a fresh install of W11 with my ICOM 7410 again and had the same issue. With the radio not attached the program does not crash.

I’m happy with the 32bit version, so just providing these logs for information and will try the next update when available.

Thanks for your work on this great project! It’s fantastic.

8

Hi Pter,
Same issue here, also using IC-7410, albeit with Rpi as server and Win11 as Wfview client. I got a lot of collisions on the server log, which disappeared after changing the baudrate from 19200 to 4800. However, still crashing a few seconds after startup.
I posted as a separated topic.

73, Reinier

9

Collisions are reported by the radio, try setting a fairly high “Manual Polling Interval” like 500ms within the User Interface tab and see if the collisions are reduced/eliminated.

Phil

~WRD0001.jpg

10

Hi Phil,
The collisions disappeared after the baudrate setting change to 4800. I changed to manual polling, but 500 msec is not accepted. I tried 200 msec. However, the client Win11 (64) still stops after 2 seconds. Noticed some unrecognized commands in the l(server) log.

https://termbin.com/37p5

73, Reinier

11

Here is the server log when opening a Wfview Win11 client:
https://termbin.com/tcap

12

Hi,

What baud rate has the collision problem? Just trying to catalog these results for other users.

And are you using the internal USB interface?

Thanks,

—E
de W6EL

13

Hi Elliott,

Thanks for the followup. I am using teh IC-7410 internal USB port. Using WSJTx directly from the laptop no issues. Now trying a new Raspberry Pi as server, with newly installed OS for good measure. 19200 baud rate produces collisions, 9600 and 4800 work without collisions reported in the log. Per @jonesypeter jonesypeter comment, I have installed the 32-bit version and the originally reported problem (Wfview client app close after 2 seconds) is now gone. It works, but just barely.
The frequency indicator jumps to an out-of-band frequency occasionally. I have set the polling to 250 msec, the max setting that the application allows. Rx delay is still 520 msec, where my ping is producing < 3 msec. My impression is that moving closer to the WiFi router improves a lot.
Last issue is that I lost the TX audio from WSJTx, where it worked before via VB audio. There are a lot of audio settings to try, wondering if these are all relevant or can this be simplified? RX latency remains around 520 msec, no matter what codec or bitrate.

Here is the log for just the Rpi server (w/o client connected)
https://termbin.com/cmnbe

Here is the log from the client with WSJTx and Log4OM connected via Hamlib:
https://termbin.com/3nd5

73, Reinier

14

Hi Reinier,

We are, unfortunately, aware of the frequency jumping issue. It’s all down to bus contention and it’s a rather difficult one to address. But we are working on it.

As for audio, you should put the sample rate at 16k and try 8-bit uLaw and also try Opus. Opus will probably produce the best results. All the settings are indeed relevant! You may also find that one of the three available audio systems works better on your system. Don’t forget to disconnect, change the audio settings, and re-connect.

What’s nice about Opus is that it is much more tolerant of weak links and dropped packets, and it has a lower bandwidth requirement overall. Give it a go, see if it is better.

If you can do your initial troubleshooting using Ethernet, with wifi off, that may be easier to deal with at first. One problem at a time, you know?

–E
de W6EL

15

Hi Elliott,

As always, thanks for the fast support followup.
I can report that TX audio on the Rpi server works now.

I found that de audio settings to enable USB audio on the Raspberry Pi are hidden in the command line system settings: $ sudo raspi-config.

Next, the VBcable version that works for me is the A+B version. The free evaluation version is a single audio link. With that I had Rx audio, but could not get TX audio to work.
I use the TX monitor feature of the IC-7410 to check the TX audio quality. 48000 samples rate sounds the cleanest. I made several FT8 and FT4 contacts.

Wfview works pretty well or me now, well done!! I really like the CAT integration. Great progress since I started looking at Wfview 2 years ago.

73, de W6WYN/PA3AAA

1 Like