rpi - wfserver

Installation Help
1

Please provide the following information with your question:

  1. Operating System: Debian 13 (trixie) on Raspberry Pi
  2. Method of download attempted (from wfview.org, package manager, source code, etc): Compiled from source (after much frustration)
  3. Radio Make and Model: Icom 7300
  4. Method of radio connectivity (USB, WiFi, Ethernet, etc): USB from Rpi to 7300, wfview on windows
  5. Did you check the FAQ and read the manual? Yes…

I have a compiled version of wfserver (2.11) compiled on a fresh debian 13 install on a rpi 4.

wfserver version: 2.11 (Git:7bef945c on Mar 17 2026 at 12:05:21 by wfview@radiopi)
Operating System: Debian GNU/Linux 13 (trixie) (arm64)
Build Qt Version 5.15.15. Current Qt Version: 5.15.15

I have attempted to configure this for an IC-7300.

[General]
AudioSystem=0

[Radios]
size=1
1\RigName=IC-7300
1\RigCIVuInt=148
1\SerialPortRadio=/dev/ttyUSB0
1\SerialPortBaud=115200
1\PTTType=0
1\ForceRTSasPTT=false
1\GUID={34888e66-c3f0-48d5-a042-c9ec78050df2}
1\AudioInput=plughw:CARD=CODEC,DEV=0
1\AudioOutput=plughw:CARD=CODEC,DEV=0

[Server]
ServerEnabled=true
ServerControlPort=50001
ServerCivPort=50002
ServerAudioPort=50003
Users\1\Password=verysecret
Users\1\UserType=0
Users\1\Username=radiopi
Users\size=1

I can successfully connect to wfserver (rpi) from wfview (windows) and see the waterfall, change frequency mode/etc. However; I don’t seem to be getting any audio. I’m fairly certain that the audio input/outputs selected are correct.

I did have a boat load of compile issues related to this post: Debian 13 wfserver unable to compile (pi) - #9 by eliggett so maybe I broke the audio portion during compile?

I’m don’t know if that branch was available when I compiled. What is the best path forward to test this and verify the audio on the rpi?

2

Indeed it does seem that your audio input and output are somehow set to the same device. That can’t be good!

Please do a fresh checkout and rebuild. We merged a new version to master just an hour ago.

Use the new --setup option to help with the audio configuration. You should probably use Qt Audio as the audio backend and look for something like “USB CODEC Burr-Brown” for the audio devices.

–E
de W6EL

3

I do seem to recall my first compile I had to add a bunch of audio headers to get it to compile. That didn’t happen this time but it does still appear to have some possible header issues.

termbin doesn’t appear to be working for me either…so here it the /tmp/build.log and the compile failure.

4

The compile error indicates that the modification to the code was not seen.

Please erase the directory where you ran qmake.

Edit the file. Be sure the include statement is not obscured by a block comment.

Make a new build directory. Run qmake from the new build directory followed by make (per the manual).

—E
de W6EL

5

This was a new directory using wget to download the full build.sh script. I can make that header change but is that (whet of the build script) the intended process for a clean build?

6

I put the change in the repo. Hopefully now the build script will work for building the graphical client.

For building the headless command-line server, please run the directions in our manual from a clean directory:

—E

7

Thank you. I forgot there was a different method for the headless compile.

Headless compiled mostly fine. A couple of warnings but it compiled.

The -–setup flag is great. Here is the config it built for me.

cat ~/.config/wfview/wfserver.conf

[General]
AudioSystem=0
Manufacturer=0

[Radios]
1\AudioInput=alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo
1\AudioOutput=alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo
1\ForceRTSasPTT=false
1\GUID={c41deea7-2951-4091-ba6f-548c944033d8}
1\PTTType=0
1\RigCIVuInt=148
1\RigName=IC-7300
1\SerialPortBaud=115200
1\SerialPortRadio=/dev/ttyUSB0
1\WaterfallFormat=1
size=1

[Server]
ServerAudioPort=50003
ServerCivPort=50002
ServerControlPort=50001
ServerEnabled=true
Users\1\Password=secret
Users\1\UserType=0
Users\1\Username=radiopi
Users\size=1

Now this will be buried at the bottom but what I wanted was do be able to do WSJT-X remotely on my windows machine. I was getting the waterfall with QTaudio but not any waterfall data on WSJT-X. I can now see waterfall data on WSJT-X with RTAudio. But I had to switch my config above from AudioSystem=0 to AudioSystem=2.

8

You’re running WSJT-X on your remote windows machine, correct?

Make sure audio is working via wfview on your windows machine with speakers and a mic first. I cannot emphasize how important it is to do this basic check. Familiarize yourself with how to set the radio’s input to USB and how to adjust the audio levels, including enabling the TxRxAudio meter and ALC meter in wfview. Failure to complete this step will make the next set of steps nearly impossible. Once this is all working, no changes should be made on the server side at all.

Then read up these two chapters from our manual on how to share audio and share control on your windows computer.

Share control: Hamlib rigctld emulation | wfview

Share audio: Audio Configuration | wfview

–E
de W6EL