I have noticed that, even with a dummy load or disconnected antenna, I see 9 equally spaced signals in both the spectrum and the waterfall. It doesn’t matter which band, nor whether the mode is Fixed or Center, I see the same 9 solid signals at the same physical positions on the display. If I tune to any of them, I hear nothing, so I believe that they are a data/display issue. For comparison, I ran Commander and it does not show them, even with REF at +20.
I am running “C:\Program Files\wfview\wfview-master-20230206–03-00-02.exe” on Windows 10 connected to a 7300, but it also shows the same in earlier versions.
That is strange… I have never seen that on any of my radios (including my IC7300).
In the IC7300 the scope data is sent in 11 separate CI-V commands with the first command containing information about the scope and the remaining 10 the actual data. It looks like there is another ‘signal’ at the very beginning of the scope, which suggests that the very first byte of scope data in each packet is somehow incorrect?
Can you confirm which firmware version is on your radio (shown in the startup screen)? Did you see this with previous versions of wfview?
Thanks, Phil. I am running firmware v1.41 in my 7300.
The earliest version of wfview that I have is wfview-master-20221001–11-24-08, and it also shows it.
@eliggett is the scope expert, so worth waiting for him to wake-up later today. My initial thought was a fault in the radio, but if other software doesn’t show it, maybe your scope is in a mode that we have never seen?
A few thoughts @DaveKE3HJ as this is something we have never seen before, can you check the log (both with and without Debug) as any anomalies with the scope data should appear in there?
Also, there is a function in wfview that can combine the scope data received from the radio into a single “packet” which is designed to replicate what the LAN radios send. It is in Settings → External Control → Waterfall Format. For normal use, this should be set to Default, but try selecting “Single (Network)” and reconnect to the radio.
Confirming that if it were PS noise (or any electrical noise), it would show on the 7300 and it would also show when I run Commander.
The lines are separated a fixed physical distance, independent of width or mode, so that is why I believe them to be a data issue.
My anti-malware will not let me send the log file to termbin.com. I have included it. It starts without debug, then continues with debug on. Sorry for the method.
I have been running in Format Single(Network) but it does the same in Default.
2023-02-07 09:21:23.086 INF system: “wfview version: 1.60 (Git:16eb459 on Feb 6 2023 at 03:02:06 by build@wfview.org). Operating System: Windows 10 Version 2009 (x86_64). Build Qt Version 6.3.2. Current Qt Version: 6.3.2”
2023-02-07 09:21:23.138 INF system: Loading settings from “\HKEY_CURRENT_USER\Software\wfview\wfview”
2023-02-07 09:21:23.203 INF rigctld: started on port 4533
2023-02-07 09:21:23.204 INF gui: Got Audio Output from Settings: “Speakers (FxSound Audio Enhancer)”
2023-02-07 09:21:23.204 INF gui: Got Audio Input from Settings: “Internal Microphone Array (Conexant SmartAudio HD)”
2023-02-07 09:21:23.287 INF audio: Audio device(s) found (*=default)
2023-02-07 09:21:23.351 INF audio: * ( 0 ) Input Device : “Internal Microphone Array (Conexant SmartAudio HD)”
2023-02-07 09:21:23.352 INF audio: ( 1 ) Input Device : “Output from 7300 (2- USB Audio CODEC )”
2023-02-07 09:21:23.352 INF audio: ( 2 ) Input Device : “Line In (BEHRINGER USB WDM AUDIO 2.8.40)”
2023-02-07 09:21:23.369 INF audio: * ( 0 ) Output Device : “Speakers (FxSound Audio Enhancer)”
2023-02-07 09:21:23.369 INF audio: ( 1 ) Output Device : “Speakers (2- USB Audio Device)”
2023-02-07 09:21:23.369 INF audio: ( 2 ) Output Device : “Input to 7300 (2- USB Audio CODEC )”
2023-02-07 09:21:23.370 INF audio: ( 3 ) Output Device : “Line Out (BEHRINGER USB WDM AUDIO 2.8.40)”
2023-02-07 09:21:23.370 INF audio: ( 4 ) Output Device : “Internal Speakers (Conexant SmartAudio HD)”
2023-02-07 09:21:23.370 INF default: Looking for inputs
2023-02-07 09:21:23.371 INF audio: "Client Audio input device Internal Microphone Array (Conexant SmartAudio HD) found! "
2023-02-07 09:21:23.371 INF default: Looking for outputs
2023-02-07 09:21:23.372 INF audio: "Client Audio output device Speakers (FxSound Audio Enhancer) found! "
2023-02-07 09:21:23.374 INF audio: "Server Audio input device Line In (BEHRINGER USB WDM AUDIO 2.8.40) found! "
2023-02-07 09:21:23.374 INF audio: "Server Audio output device Line Out (BEHRINGER USB WDM AUDIO 2.8.40) found! "
2023-02-07 09:21:23.704 INF system: Cannot prepare WF view without rigCaps. Waiting on this.
2023-02-07 09:21:23.704 INF system: Cannot prepare WF view without rigCaps. Waiting on this.
2023-02-07 09:21:23.727 INF rig: creating instance of rigCommander()
2023-02-07 09:21:23.731 INF cluster: starting dxClusterClient()
2023-02-07 09:21:23.744 INF serial: Opened port: “COM3”
2023-02-07 09:21:23.853 INF system: Received CommReady!!
2023-02-07 09:21:23.853 INF system: Delay command interval timing: 75 ms
2023-02-07 09:21:23.853 INF default: Setting rig state for wfmain
2023-02-07 09:21:23.853 INF default: Setting rig state
2023-02-07 09:21:23.856 INF rig: Using incomingCIVAddr: (int): 148 hex: “0x94”
2023-02-07 09:21:23.856 INF serial: Received rigCapabilities for “IC-7300”
2023-02-07 09:21:23.856 INF rig: Have rig ID: decimal: 148
2023-02-07 09:21:23.857 INF rigctld: Got rigcaps for: “IC-7300”
2023-02-07 09:21:23.860 INF system: Delay command interval timing: 25 ms
2023-02-07 09:21:25.340 INF system: Could not find modulation input: 4
2023-02-07 09:21:44.221 INF log: Sending data to termbin.com. Standby.
2023-02-07 09:21:44.329 INF log: Connected to logging host
2023-02-07 09:21:44.541 INF log: Receiving data from logging host.
2023-02-07 09:21:44.545 INF log: Sent log to URL: “HTTP/1.1 303 See Other\r\nLocation: Malwarebytes close”
2023-02-07 09:21:44.545 INF log: This address already copied to the clipboard. Please paste this URL in to your support questions.
2023-02-07 09:21:45.542 INF log: Disconnected from logging host
2023-02-07 09:23:28.356 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:28.356 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:28.356 DBG rigTraffic: "DATA: fe fe 94 e1 11 fd "
2023-02-07 09:23:28.356 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 "
2023-02-07 09:23:28.356 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:28.359 DBG rigTraffic: Received from radio:
2023-02-07 09:23:28.359 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:28.359 DBG rigTraffic: "DATA: 11 00 fd "
2023-02-07 09:23:28.359 DBG rigTraffic: "INDEX: 00 01 02 "
2023-02-07 09:23:28.359 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:28.670 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:28.671 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:28.671 DBG rigTraffic: "DATA: fe fe 94 e1 1c 00 fd "
2023-02-07 09:23:28.671 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:28.671 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:28.673 DBG rigTraffic: Received from radio:
2023-02-07 09:23:28.674 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:28.674 DBG rigTraffic: "DATA: 1c 00 00 fd "
2023-02-07 09:23:28.674 DBG rigTraffic: "INDEX: 00 01 02 03 "
2023-02-07 09:23:28.674 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:28.984 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:28.984 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:28.984 DBG rigTraffic: "DATA: fe fe 94 e1 16 02 fd "
2023-02-07 09:23:28.984 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:28.984 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:28.987 DBG rigTraffic: Received from radio:
2023-02-07 09:23:28.987 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:28.987 DBG rigTraffic: "DATA: 16 02 00 fd "
2023-02-07 09:23:28.987 DBG rigTraffic: "INDEX: 00 01 02 03 "
2023-02-07 09:23:28.987 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:29.294 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:29.294 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:29.294 DBG rigTraffic: "DATA: fe fe 94 e1 0f fd "
2023-02-07 09:23:29.294 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 "
2023-02-07 09:23:29.294 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:29.294 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:29.294 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:29.294 DBG rigTraffic: "DATA: fe fe 94 e1 1a 05 00 46 fd "
2023-02-07 09:23:29.294 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 07 08 "
2023-02-07 09:23:29.294 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:29.297 DBG rigTraffic: Received from radio:
2023-02-07 09:23:29.297 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:29.297 DBG rigTraffic: "DATA: 1a 05 00 46 00 fd "
2023-02-07 09:23:29.297 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 "
2023-02-07 09:23:29.297 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:29.610 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:29.610 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:29.610 DBG rigTraffic: "DATA: fe fe 94 e1 1a 03 fd "
2023-02-07 09:23:29.610 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:29.610 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:29.613 DBG rigTraffic: Received from radio:
2023-02-07 09:23:29.613 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:29.613 DBG rigTraffic: "DATA: 1a 03 32 fd "
2023-02-07 09:23:29.613 DBG rigTraffic: "INDEX: 00 01 02 03 "
2023-02-07 09:23:29.613 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:29.919 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:29.919 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:29.919 DBG rigTraffic: "DATA: fe fe 94 e1 14 07 fd "
2023-02-07 09:23:29.919 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:29.919 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:29.922 DBG rigTraffic: Received from radio:
2023-02-07 09:23:29.922 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:29.922 DBG rigTraffic: "DATA: 14 07 01 28 fd "
2023-02-07 09:23:29.922 DBG rigTraffic: "INDEX: 00 01 02 03 04 "
2023-02-07 09:23:29.922 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:30.231 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:30.231 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:30.231 DBG rigTraffic: "DATA: fe fe 94 e1 14 08 fd "
2023-02-07 09:23:30.231 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:30.231 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:30.233 DBG rigTraffic: Received from radio:
2023-02-07 09:23:30.233 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:30.233 DBG rigTraffic: "DATA: 14 08 01 28 fd "
2023-02-07 09:23:30.233 DBG rigTraffic: "INDEX: 00 01 02 03 04 "
2023-02-07 09:23:30.233 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:30.544 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:30.544 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:30.544 DBG rigTraffic: "DATA: fe fe 94 e1 03 fd "
2023-02-07 09:23:30.544 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 "
2023-02-07 09:23:30.544 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:30.547 DBG rigTraffic: Received from radio:
2023-02-07 09:23:30.547 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:30.547 DBG rigTraffic: "DATA: 03 00 40 16 07 00 fd "
2023-02-07 09:23:30.547 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:30.547 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:30.858 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:30.858 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:30.858 DBG rigTraffic: "DATA: fe fe 94 e1 04 fd "
2023-02-07 09:23:30.858 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 "
2023-02-07 09:23:30.858 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:30.860 DBG rigTraffic: Received from radio:
2023-02-07 09:23:30.860 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:30.860 DBG rigTraffic: "DATA: 04 00 02 fd "
2023-02-07 09:23:30.860 DBG rigTraffic: "INDEX: 00 01 02 03 "
2023-02-07 09:23:30.860 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:31.169 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:31.169 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:31.169 DBG rigTraffic: "DATA: fe fe 94 e1 1c 00 fd "
2023-02-07 09:23:31.169 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:31.169 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:31.172 DBG rigTraffic: Received from radio:
2023-02-07 09:23:31.172 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:31.172 DBG rigTraffic: "DATA: 1c 00 00 fd "
2023-02-07 09:23:31.172 DBG rigTraffic: "INDEX: 00 01 02 03 "
2023-02-07 09:23:31.172 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:31.484 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:31.484 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:31.484 DBG rigTraffic: "DATA: fe fe 94 e1 14 0a fd "
2023-02-07 09:23:31.484 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:31.484 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:31.487 DBG rigTraffic: Received from radio:
2023-02-07 09:23:31.487 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:31.487 DBG rigTraffic: "DATA: 14 0a 02 55 fd "
2023-02-07 09:23:31.487 DBG rigTraffic: "INDEX: 00 01 02 03 04 "
2023-02-07 09:23:31.487 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:31.795 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:31.796 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:31.796 DBG rigTraffic: "DATA: fe fe 94 e1 14 02 fd "
2023-02-07 09:23:31.796 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:31.796 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:31.801 DBG rigTraffic: Received from radio:
2023-02-07 09:23:31.801 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:31.801 DBG rigTraffic: "DATA: 14 02 02 55 fd "
2023-02-07 09:23:31.801 DBG rigTraffic: "INDEX: 00 01 02 03 04 "
2023-02-07 09:23:31.801 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:32.109 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:32.109 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:32.109 DBG rigTraffic: "DATA: fe fe 94 e1 11 fd "
2023-02-07 09:23:32.109 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 "
2023-02-07 09:23:32.109 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:32.111 DBG rigTraffic: Received from radio:
2023-02-07 09:23:32.111 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:32.111 DBG rigTraffic: "DATA: 11 00 fd "
2023-02-07 09:23:32.111 DBG rigTraffic: "INDEX: 00 01 02 "
2023-02-07 09:23:32.111 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:32.420 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:32.421 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:32.421 DBG rigTraffic: "DATA: fe fe 94 e1 1c 00 fd "
2023-02-07 09:23:32.421 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:32.421 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:32.423 DBG rigTraffic: Received from radio:
2023-02-07 09:23:32.423 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:32.423 DBG rigTraffic: "DATA: 1c 00 00 fd "
2023-02-07 09:23:32.423 DBG rigTraffic: "INDEX: 00 01 02 03 "
2023-02-07 09:23:32.423 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:32.734 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:32.734 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:32.734 DBG rigTraffic: "DATA: fe fe 94 e1 16 02 fd "
2023-02-07 09:23:32.734 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:32.734 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:32.738 DBG rigTraffic: Received from radio:
2023-02-07 09:23:32.738 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:32.738 DBG rigTraffic: "DATA: 16 02 00 fd "
2023-02-07 09:23:32.738 DBG rigTraffic: "INDEX: 00 01 02 03 "
2023-02-07 09:23:32.738 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:33.049 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:33.049 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:33.049 DBG rigTraffic: "DATA: fe fe 94 e1 0f fd "
2023-02-07 09:23:33.049 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 "
2023-02-07 09:23:33.049 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:33.049 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:33.049 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:33.049 DBG rigTraffic: "DATA: fe fe 94 e1 1a 05 00 46 fd "
2023-02-07 09:23:33.049 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 07 08 "
2023-02-07 09:23:33.049 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:33.054 DBG rigTraffic: Received from radio:
2023-02-07 09:23:33.054 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:33.054 DBG rigTraffic: "DATA: 1a 05 00 46 00 fd "
2023-02-07 09:23:33.054 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 "
2023-02-07 09:23:33.054 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:33.357 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:33.357 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:33.357 DBG rigTraffic: "DATA: fe fe 94 e1 1a 03 fd "
2023-02-07 09:23:33.358 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:33.358 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:33.361 DBG rigTraffic: Received from radio:
2023-02-07 09:23:33.361 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:33.361 DBG rigTraffic: "DATA: 1a 03 32 fd "
2023-02-07 09:23:33.361 DBG rigTraffic: "INDEX: 00 01 02 03 "
2023-02-07 09:23:33.361 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:33.671 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:33.671 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:33.671 DBG rigTraffic: "DATA: fe fe 94 e1 14 07 fd "
2023-02-07 09:23:33.671 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:33.671 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:33.674 DBG rigTraffic: Received from radio:
2023-02-07 09:23:33.675 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:33.675 DBG rigTraffic: "DATA: 14 07 01 28 fd "
2023-02-07 09:23:33.675 DBG rigTraffic: "INDEX: 00 01 02 03 04 "
2023-02-07 09:23:33.675 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:33.984 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:33.984 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:33.984 DBG rigTraffic: "DATA: fe fe 94 e1 14 08 fd "
2023-02-07 09:23:33.984 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:33.984 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:33.992 DBG rigTraffic: Received from radio:
2023-02-07 09:23:33.992 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:33.992 DBG rigTraffic: "DATA: 14 08 01 28 fd "
2023-02-07 09:23:33.992 DBG rigTraffic: "INDEX: 00 01 02 03 04 "
2023-02-07 09:23:33.992 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:34.294 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:34.294 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:34.294 DBG rigTraffic: "DATA: fe fe 94 e1 03 fd "
2023-02-07 09:23:34.294 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 "
2023-02-07 09:23:34.294 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:34.299 DBG rigTraffic: Received from radio:
2023-02-07 09:23:34.299 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:34.299 DBG rigTraffic: "DATA: 03 00 40 16 07 00 fd "
2023-02-07 09:23:34.299 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:34.299 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:34.607 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:34.607 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:34.607 DBG rigTraffic: "DATA: fe fe 94 e1 04 fd "
2023-02-07 09:23:34.607 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 "
2023-02-07 09:23:34.607 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:34.610 DBG rigTraffic: Received from radio:
2023-02-07 09:23:34.610 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:34.610 DBG rigTraffic: "DATA: 04 00 02 fd "
2023-02-07 09:23:34.610 DBG rigTraffic: "INDEX: 00 01 02 03 "
2023-02-07 09:23:34.610 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:34.919 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:34.919 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:34.919 DBG rigTraffic: "DATA: fe fe 94 e1 1c 00 fd "
2023-02-07 09:23:34.919 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:34.919 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:34.922 DBG rigTraffic: Received from radio:
2023-02-07 09:23:34.922 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:34.922 DBG rigTraffic: "DATA: 1c 00 00 fd "
2023-02-07 09:23:34.922 DBG rigTraffic: "INDEX: 00 01 02 03 "
2023-02-07 09:23:34.922 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:35.232 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:35.232 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:35.232 DBG rigTraffic: "DATA: fe fe 94 e1 14 0a fd "
2023-02-07 09:23:35.232 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:35.232 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:35.235 DBG rigTraffic: Received from radio:
2023-02-07 09:23:35.235 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:35.236 DBG rigTraffic: "DATA: 14 0a 02 55 fd "
2023-02-07 09:23:35.236 DBG rigTraffic: "INDEX: 00 01 02 03 04 "
2023-02-07 09:23:35.236 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:35.543 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:35.543 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:35.543 DBG rigTraffic: "DATA: fe fe 94 e1 14 02 fd "
2023-02-07 09:23:35.543 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:35.543 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:35.546 DBG rigTraffic: Received from radio:
2023-02-07 09:23:35.546 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:35.546 DBG rigTraffic: "DATA: 14 02 02 55 fd "
2023-02-07 09:23:35.546 DBG rigTraffic: "INDEX: 00 01 02 03 04 "
2023-02-07 09:23:35.546 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:35.857 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:35.857 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:35.857 DBG rigTraffic: "DATA: fe fe 94 e1 11 fd "
2023-02-07 09:23:35.857 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 "
2023-02-07 09:23:35.857 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:35.859 DBG rigTraffic: Received from radio:
2023-02-07 09:23:35.860 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:35.860 DBG rigTraffic: "DATA: 11 00 fd "
2023-02-07 09:23:35.860 DBG rigTraffic: "INDEX: 00 01 02 "
2023-02-07 09:23:35.860 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:36.169 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:36.169 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:36.169 DBG rigTraffic: "DATA: fe fe 94 e1 1c 00 fd "
2023-02-07 09:23:36.169 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:36.169 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:36.173 DBG rigTraffic: Received from radio:
2023-02-07 09:23:36.174 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:36.174 DBG rigTraffic: "DATA: 1c 00 00 fd "
2023-02-07 09:23:36.174 DBG rigTraffic: "INDEX: 00 01 02 03 "
2023-02-07 09:23:36.174 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:36.485 DBG rigTraffic: Final payload in rig commander to be sent to rig:
2023-02-07 09:23:36.485 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:36.485 DBG rigTraffic: "DATA: fe fe 94 e1 16 02 fd "
2023-02-07 09:23:36.485 DBG rigTraffic: "INDEX: 00 01 02 03 04 05 06 "
2023-02-07 09:23:36.485 DBG rigTraffic: “---- End hex dump -----”
2023-02-07 09:23:36.489 DBG rigTraffic: Received from radio:
2023-02-07 09:23:36.489 DBG rigTraffic: “---- Begin hex dump -----:”
2023-02-07 09:23:36.489 DBG rigTraffic: "DATA: 16 02 00 fd "
2023-02-07 09:23:36.489 DBG rigTraffic: "INDEX: 00 01 02 03 "
2023-02-07 09:23:36.489 DBG rigTraffic: “---- End hex dump -----”
Do you have CI-V Transceive turned on? If not, please turn it on.
Do you have either of these two checkboxes checked? If so, please uncheck both:
Manual Radio CI-V Address
Use CI-V Address as Model ID too
Make sure those are unchecked and that CI-V Transceive is turned ON on the radio.
I suspect you have somehow uncovered a condition where the radio capabilities are not being assessed on startup correctly. I’ll try and replicate it here.
Also please set the waterfall format to “Default”.
Once all three of these things are set (the two checkboxes, and the default waterfall format), verify that CI-V Transceive is turned ON in the radio. Press Save Settings and relaunch wfview.
I have seen this before and found it was caused by a digital data switch I bought from best buy to share my wifi in the shack. The footprint that was being displayed on my IC-7610 was so annoying, I returned the digital data switch and went with a dedicated static IP for my desktop and another one for my IC-7610. This solved the problem. Also, please consider “Digital Intermod”? Try running wfview on laptop in full remote operation from another location at your QTH.
This particular issue has now been confirmed to be a data integrity problem within the code. Leave the waterfall format to “default” and it will go away.
With that said, I’ve seen similar from poorly-designed equipment. Regular interval spacing is always a giveaway.
A few examples from my own selection:
Incorrectly wired ethernet cables
The power converter for my vehicle’s rear camera+display system
One early generation 2A iPad charger
The supplied power supply for the Inovato Quadra, which is so bad that it could be used as a comb signal generator! It’s a spike every 50KHz from 1 MHz up to about 30 MHz, and some above as well.
My HVAC fan is atrocious, spikes every 10 KHz all over HF.
My old plasma TV made 40M unusable
My blueray player made horrible hash, but only when it was off. When it was on it was fine. Bad power supply design!! That things stays unplugged now anyway.
A radioshack-branded switch-mode 12V power supply (the 25 amp one)
Several “made for radio use” switch-mode 12V power supplies made by companies that ought to know better and marketed for ham radio operators. They have good reviews from folks using them for UHF but not so much on HF…
Ok, enough trauma for today. I’m confident that the original issue in this thread is a bug in the code. Do not use the “Waterfall format” option unless you are 100% confident that you need this; it is not a commonly-needed option. And we’ll get it fixed soon.
I verified the settings as you specified:
CI-V Tranceive ON in the 7300
Manual Radio CI-V Address and Use CI-V Address as Model ID both unchecked.
Waterfall Format set to Default. (I did have it on Single due to flickering in first 1.6 release)
I saved settings and restarted wfview and all back to normal again!
The waterfall format is pretty low-level. It is designed to aid in compatibility with 3rd party programs that one might connect to wfview. I would not set it if not needed as it does not (or should not) change the display or operation within wfview at all.
Phil is patching the bug up, it’s a pretty minor one. But just keep it on Default unless you are running a wfview server.
