IC-7610 via ethernet with WSJT-X/Fldigi on MacOS Sequoia 15.3

Wfview is exactly the piece of software that I need - amazing work! I’m having some difficulties with the integrated rigctld that I could use a hand troubleshooting.

Radio: IC-7610 connected via ethernet.
Operating System: MacOS Sequoia 15.3 on Macbook Air M2
Software: wfview v2.03, WSJT-X v2.6.1, fldigi 4.2.06

Log file: https://termbin.com/98qw

  • Opened wfview
  • Opened WSJT-X
  • Pressed the “Tune” button on the main display of WSJT-X
  • Captured this log

Background:

  • This is a new radio, just got it a couple weeks ago, brand new from HRO. MARS modded by HRO.
  • The problems I’m encountering are the same in WSJT-X and Fldigi. Since WSJT-X is simpler (to me), I’m focusing my debugging attention there, assuming when I get that working it should also fix Fldigi.
  • The radio is connected to the network via ethernet, no USB cable is plugged into the radio.

Docs I’ve read:

  • Sharing Control Overview
  • Audio Configuration

What works:

  • wfview itself works great. I’m able to receive & hear, as well as navigate the VFO while viewing the waterfall and trigger the tuner and PTT.
  • I’ve read through the Audio Configuration guide and used Blackhole for the virtual audio on Mac (brew install blackhole-2ch was just too simple to pass up)
  • Audio output is going to a multi-output device defined in the Audio MIDI Setup application (the multiple outputs are my speakers and a virtual Blackhole-2CH device that is used as input to other applications)
  • Audio input is coming from Blackhole-16ch, a separate virtual device that is the output from other applications (WSJT-X & fldigi). When I send audio from WSJT-X (like when pressing the Tune button), I see the “TxAudio” meter in wfview spike to max.
  • Any other applications like WSJT-X and fldigi are able to receive and decode audio just fine, and are able to read the current VFO frequency. When I change the frequency in wfview, the frequency displayed in the other applications updates very quickly.

What doesn’t work:

  • Changing the frequency, mode, or attempting to do any other activity that triggers transmit from the other applications.

What I’ve tried/checked:

  • I’ve changed the Audio System (default was QtAudio) to RT Audio
  • Uninstalled and re-installed wfview a couple times (each time removing the saved settings found in ~/Library/Containers/org.wfview.wfview before retrying setup)
  • Connecting WSJT-X to the virtual serial port (~/Downloads/rig-pty1) instead of HamLib NET rigctl works well and I can send/receive and make QSOs. But since I want to use multiple applications downstream from wfview, I want to use the embedded rigctld.
  • I have a homelab with access to both Windows and Linux machines as well. I installed wfview on a Debian 12 linux host, and enabled rigctld there. When I leave all settings identical in WSJT-X except for the ip address of the rigctld, clicking the “Tune” button in WSJT-X triggers transmit in the wfview running in linux (and of course on the physical radio). I’m not a fan of Windows, so I haven’t yet tried setting it up there - but since I see it working on Linux, I’m inclined to believe that the radio setup is ok, and that wfview software itself is ok in general, and that the problem is local to my mac.
  • Radio settings:
    • CI-V transceive is ON
    • “Unlink from Remote” is set
    • Data Off Modulation Input: LAN
    • Data 1 Input: LAN
    • Data 2 Input: LAN
    • Data 3 Input: LAN

My (probably wrong) assumptions:

  • This is something extraordinarily simple that I’ve overlooked
  • Since I can see the TxAudio meter spiking when I send data from WSJT-X, I believe the audio setup is fine.
  • The issue is related to the embedded rigctld started by wfview on my Mac. Since I’m able to successfully trigger transmit via rigctld on a remote wfview instance on linux, but not on my mac, I am assuming that WSJT-X’s configuration is ok.

What is the obvious thing that I’m missing or should try? I can share all kinds of screenshots if it would help.

Thanks :slight_smile:

1 Like

Hi Matt.

Firstly, thanks for the comprehensive report, you wouldn’t believe how much work we often have to drag information out of some people!

There is an issue with v2.03 rigctld, where it can try to use the wrong commands to get/set frequency/mode information, I have also found issues with the latest beta version of wsjtx-x, as they use a newer version of Hamlib. You may have more luck with an older version of wsjt-x?

We will soon be releasing v2.04 which should work a lot better with a wider range of rigctld clients.

Thanks

Phil

Hi Phil - thanks for the quick reply. Would you be so kind as to recommend a pair of versions that you all have found to be stable? Or I could perhaps beta test the v2.04 release for you to see if it resolves my particular issue.

Thanks!

We don’t really release beta versions, as the source code is online, so generally Linux users get first access to new features/fixes and then once we are reasonably happy that it is stable, we release a Windows/MacOS build.

It is possible to create a Windows build environment, but it generally requires manually downloading and compiling all dependant libraries.

We have started to document this process at How to compile with Windows | wfview

Downgrading wfview to v1.64 has everything working to my expectations. Both WSJT-X (v2.6.1) and Fldigi (v4.2.06) are able to send/rcv and control the VFO with the embedded rigctld.

Thanks for confirming some known issues with rigctld and suggesting that I try an older version. I’ll accept the victory, and test out wfview v2.04 with caution - although the fact that the latest source worked on my linux host gives me hope.

wfview 1.64 will often work in these situations, as it has a much simpler implementation, with no knowledge of multiple receivers or VFOs that many modern radios have.

It turn’s out that supporting these, makes things an order or magnitude more complex, but with 2.04 I think we are pretty close.

2 Likes