Wfview 2.10 released

We are pleased to announce that wfview version 2.10 has now been officially released.

Downloads for Windows (x64 and x86) and MacOS are available in Download | wfview

This version adds a number of features/fixes, the main ones being:

  • (hopefully) better rigctld emulation
  • Fixes for the memory manager (especially radios with multiple groups)
  • wfview will now automatically power-on radios on startup
  • Meters now calibrated to each radio (S/SWR/Power/V/A etc.)
  • IC-7600 and IC-7760 rig files added
  • Add filter shape and roofing filters (where supported)
  • Improved support for Kenwood TS-890 including LAN mode
  • Improve smoothness of USB knobs
  • Various other fixes
2 Likes

the link should be Download | wfview :slight_smile:

2 Likes

Thanks @DL3EL, finger trouble!

I forgot to mention, the Band and Frequency input windows now save their position which was a feature requested by @Neptune

2 Likes

Hello many thanks for the email. After the update should one do all the settings again from scratch or does the updated version retains the existing settings?
Thanks
Peter IU0DHV

Peter,

Settings are retained.

–E
de W6EL

hi there,
I[ā€˜m trying to connect to my ts-890 via my local area network, and I’m using voiceover, I’m hearing some kind of push-notification, and being told that there is a new dialogue on the screen, but voiceover is not bringing focus to the dialogue. Also when I click on the power on button, nothing happens, I’ve gone to Wfview > settings> network radios, and entered the ip address of my radio, 192.168.0.40, as well as the control port, 60001, and am not able to turn the radio on as of yet. I’m assuming that since Kenwood doesn’t use the civ address, there is nothing that I have to do with that?
THanks,
Justin-ai5os

Hi Justin.

It’s difficult to say, did you select Kenwood as the manufacturer? It should automatically change the port to 60001 which is why I suspect you haven’t?

The Manufacturer combobox is at the top left of the settings screen. I am not sure if I configured an accessible name for it?

73 Phil

I am currently trying to get a remote connectin to Kenwood TS-890 running. Everything is as expected, just the sound doesn’t work. Sound generally looks like working for WFView as I do have the local sidetone in cw. But I do not hear what the scope shows. I have checked the log, it is stated that the soundcards are found as configured - looks ok.

vy 73 de Thomas, DL3EL

Hello,

I had probably same issue on my IC-7610 and MacOS but resolved.

What I did was select another audio output device once then select original device again.

de JJ1HMR

@DL3EL the log will tell us whether it is successfully starting the VOIP (audio) connection. If you need help deciphering it, please click ā€˜Send to Terrmbin’ and post the URL you receive.

https://termbin.com/3o9x

Iā€m having that issue in mac os, I can’t get the sound to come out of the speakers that I’m trying to use.
Thanks,
Justin

could it be, that there is a general sound problem? Currently I have three setups here:
a) local IC7300 - Raspberry WFView Sevrer - local W11 WFView Client
b) remote TS890 - local WFView Client
c) remote IC7300 - Raspberry WFView Sevrer - local W11 WFView Client

Only in a) I have receiving sound (didnot try tx yet)
in b) there is no sound from the Kenwood
in c) there is no sound from the IC7300, however I hear my own, local sound (keyboard click etc) in the speaker. When I increase the volume, it leads to some nasty back coupling

All WFView instances are on 2.10

Termbin from the W11 Client attached
https://termbin.com/vzb7

vy 73 de Thomas, DL3EL

You may need to re-select the audio devices but no I don’t think there is a general problem (tested with Mac, Linux, Windows and lots of different radios)

Check the server audio devices are correct.

the rx audio input was empty after the upgrade. I was also not available for the local WSJT-X installation,after a reboot it looks like attached. For me it seems ok

I would suspect that either a firewall is blocking UDP port 60001 or some other software is using this port and preventing wfview from listening on it.

one important info, just discovered: before I did the upgrade, I copied /usr/local/bin/wfview to wfview.203. When I now switch back to that version on the Raspberry, the sound on my local W11 Client (with wfview 2.10) starts immediatly.

It’s quite possible that the device names have changed, as 2.10 uses a newer version of the Qt framework.

You can also try PA or RT audio systems, rather than the default QT one.