Remote access - is this solely an audio issue?

Hello,
I’m running Wfview server (v2.04) on a fresh install of Ubuntu 24.04.20, connected to an IC-7300 via serial USB. The Wfview client is running on a MacBook Air (M1) with macOS Sequoia 15.3.2.

The connection is partially working:

  • I can successfully connect to the server from the client.
  • The waterfall displays correctly.
  • WSJT-X (on the Mac) can receive some data and occasionally decodes messages.
  • PTT works from the client and WSJT-X can key the rig — but no RF power is output.
  • The audio from the client sounds fluttery or has a pulsating character. I’ve tried multiple audio configurations without success. (The remote instructions did say streaming audio could be hard!)

I’ve also checked the logs, but they’re full of errors, and I’m having a hard time distinguishing what’s critical from what’s just informational.

I’ve been trying to troubleshoot this for a while and at this point, I’m not sure what to do next. Is it just the audio config or I’m missing some OS issue?

Any suggestions would be appreciated! Thanks in advance - Steve

Yikes, I was just about to create this topic and had powered off the radio a while ago, but it had crashed. Here’s the log leading to the crash: https://termbin.com/h03m



The MIC:MIC changes to MIC:USB when I connect.

Can you retry with a version 2 client on your mac? Looks like you’re running 1.64.

–E
de W6EL

Elliott,

That seems to have been it - things appear to be running as expected!

Thank you…

Steve

This solution reminds me of a saying in my line of work - “when you hear hoofbeats, think horses- not zebras.” It seems I’ve been looking for zebras in my troubleshooting efforts!

Elliott,

My excitement about it working was short lived. About 30 minutes after it was working, the original issues started popping up with no change in configuration. After working on this off and for two weeks I’m going to step away for a while. The logs have so many different error messages and the wfview function changes intermittently, I’m beginning to think it could be a layer 1 issue. I’ve ordered a new USB cable and I’ll see if that makes any difference.

Anyway, I’ve appreciated your help along the way.

Steve

if it is a layer 1 issue, you can check locally in the server log and check the timestamps compared to the client side. if yiu face client issues, look at the server to rule in/out the USB cable.

a good cable does not hurt by the way

Thanks for the suggestions.

It was indeed the USB cable. I replaced the old cable with one from RT systems and virtually all the error messages disappeared. The system is now up and running and seems to be fully functional including data exchange with WSJT and GridTracker.

1 Like