Pi5 Rasbian

[ebfourie (Eben)]

WFView Version: ?.??
Hardware: Raspberry Pi5 4Gb
OS: Debian GNU/Linux 13 (trixie)
Radio: FT-710
Connection method: USB
Driver: installed FT4222 as per Yaesu FT-710 Setup | wfview
Install method: fullbuild-wfview.sh
FAQ / Manual: Yes

Driver install notes:

ls -l /dev/serial/by-id lists both ttyUSB0 and ttyUSB1

lsusb | grep FT4222 - all good, see the device when the radio is switched on

Install script notes

Modified the install script dependencies librtaudio6 to librtaudio7

script runs for about 13 minutes, and ends with the message
'Did not install. Program may be manually installed by running “sudo make install” from the build folder’

Looks like the install script created a folder in ~/Downloads called 'wfview–20260612–16-03-12". I changed to the build sub-folder in there, and ran “sudo make install”

Did not see any error messages. Tried running “wfview” from command line.

bash: /home/pi/.local/wfview: cannot execute binary file: Exe format error

[eliggett (Elliott Liggett)]

It really seems like you may have tried to install the app image version first. If so, you need to remove it.

Can you also change directory into the build folder for the wfview build and just run “make” and share the output with us?

[ebfourie (Eben)]

Hi Elliot, all good.

Is there a simple way to remove the app image install ? If not I can just reflash the pi.

Eben

[eliggett (Elliott Liggett)]

Yes,

rm /home/pi/.local/wfview

And then to continue the failed compile (or rather, find the error) :

cd ~/Downloads
cd wfview–20260612–16-03-12
cd build
make

And share with us any errors you see. It’s likely just some missing library.

–E
de W6EL

[eliggett (Elliott Liggett)]

Also, it would be neat to see exactly what that “exe format” is:

file /home/pi/.local/wfview
ldd /home/pi/.local/wfview

–E
de W6EL

[ebfourie (Eben)]

re-flashed the Pi5 for a clean start.

ran fullbuild-wfview.sh

same messages as before

pi@raspberrypi:~/Downloads/wfview–20260614–14-04-41/build $ sudo make install
[sudo] password for pi:
/usr/lib/qt5/bin/qmake -install qinstall -exe wfview /usr/local/bin/wfview
strip /usr/local/bin/wfview
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/resources/wfview.desktop /usr/local/share/applications/wfview.desktop
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/resources/icons/bitmap/wfview.png /usr/local/share/icons/hicolor/256x256/apps/wfview.png
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/resources/org.wfview.wfview.metainfo.xml /usr/local/share/metainfo/org.wfview.wfview.metainfo.xml
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/qdarkstyle /usr/local/share/wfview/qdarkstyle
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/DEFAULT-ICOM.rig /usr/local/share/wfview/rigs/DEFAULT-ICOM.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/DEFAULT-KENWOOD.rig /usr/local/share/wfview/rigs/DEFAULT-KENWOOD.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/FT-710.rig /usr/local/share/wfview/rigs/FT-710.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/FTX-1.rig /usr/local/share/wfview/rigs/FTX-1.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-705.rig /usr/local/share/wfview/rigs/IC-705.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-706.rig /usr/local/share/wfview/rigs/IC-706.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-706MK2G.rig /usr/local/share/wfview/rigs/IC-706MK2G.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-7100.rig /usr/local/share/wfview/rigs/IC-7100.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-718.rig /usr/local/share/wfview/rigs/IC-718.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-7200.rig /usr/local/share/wfview/rigs/IC-7200.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-7300.rig /usr/local/share/wfview/rigs/IC-7300.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-7300MK2.rig /usr/local/share/wfview/rigs/IC-7300MK2.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-746.rig /usr/local/share/wfview/rigs/IC-746.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-746PRO.rig /usr/local/share/wfview/rigs/IC-746PRO.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-756.rig /usr/local/share/wfview/rigs/IC-756.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-756PRO.rig /usr/local/share/wfview/rigs/IC-756PRO.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-756PROII.rig /usr/local/share/wfview/rigs/IC-756PROII.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-756PROIII.rig /usr/local/share/wfview/rigs/IC-756PROIII.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-7600.rig /usr/local/share/wfview/rigs/IC-7600.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-7610.rig /usr/local/share/wfview/rigs/IC-7610.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-7760.rig /usr/local/share/wfview/rigs/IC-7760.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-785x.rig /usr/local/share/wfview/rigs/IC-785x.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-905.rig /usr/local/share/wfview/rigs/IC-905.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-9100.rig /usr/local/share/wfview/rigs/IC-9100.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-9700.rig /usr/local/share/wfview/rigs/IC-9700.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-R7100.rig /usr/local/share/wfview/rigs/IC-R7100.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-R8500.rig /usr/local/share/wfview/rigs/IC-R8500.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/IC-R8600.rig /usr/local/share/wfview/rigs/IC-R8600.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/ID-31.rig /usr/local/share/wfview/rigs/ID-31.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/TS-590SG.rig /usr/local/share/wfview/rigs/TS-590SG.rig
/usr/lib/qt5/bin/qmake -install qinstall /home/pi/Downloads/wfview–20260614–14-04-41/wfview/rigs/TS-890S.rig /usr/local/share/wfview/rigs/TS-890S.rig

pi@raspberrypi:~/Downloads/wfview–20260614–14-04-41/build $ make
make: Nothing to be done for ‘first’.
pi@raspberrypi:~/Downloads/wfview–20260614–14-04-41/build $ file /home/pi/.local/wfview
/home/pi/.local/wfview: cannot open `/home/pi/.local/wfview’ (No such file or directory)
pi@raspberrypi:~/Downloads/wfview–20260614–14-04-41/build $ ldd /home/pi/.local/wfview
ldd: /home/pi/.local/wfview: No such file or directory
pi@raspberrypi:~/Downloads/wfview–20260614–14-04-41/build $

[eliggett (Elliott Liggett)]

What happens when you try to start wfview?

–E
de W6EL

[ebfourie (Eben)]

wfview launches

cat control works. including tx and tune

s-meter is working

nothing on the waterfall display - just blue

radio status shows FT-710, all green, baud rate = 0

log:

2026-06-14 15:11:29.956 INF system: wfview version: 2.22 (Git:cd18ea5 on Jun 14 2026 at 14:11:53 by pi@raspberrypi)

2026-06-14 15:11:29.956 INF system: Operating System: Debian GNU/Linux 13 (trixie) (arm64)

2026-06-14 15:11:29.956 INF system: Looking for External Dependencies:

2026-06-14 15:11:29.956 INF system: QT Runtime Version: 5.15.15

2026-06-14 15:11:29.956 INF system: OPUS Version: libopus 1.5.2

2026-06-14 15:11:29.956 INF system: HIDAPI Version: 0.14.0

2026-06-14 15:11:29.956 INF system: EIGEN Version: 3.4.0

2026-06-14 15:11:29.956 INF system: QCUSTOMPLOT Version: 2.1.0

2026-06-14 15:11:29.956 INF system: RTAUDIO Version: 6.0.1

2026-06-14 15:11:29.956 INF system: PORTAUDIO Version: PortAudio V19.6.0-devel, revision 396fe4b6699ae929d3a685b3ef8a7e97396139a4

2026-06-14 15:11:29.958 INF default: Starting caching queue handler thread (ThreadId: 0x7fff3b7eefe0 )

2026-06-14 15:11:29.996 INF system: Loading settings from “/home/pi/.config/wfview/wfview.conf”

2026-06-14 15:11:30.036 WRN qt.qpa.wayland: Wayland does not support QWindow::requestActivate()

2026-06-14 15:11:30.037 INF gui: Got Audio Output from Settings: “default:CARD=Device”

2026-06-14 15:11:30.037 INF gui: Got Audio Input from Settings: “default:CARD=Device”

2026-06-14 15:11:30.037 INF default: tciServer() listening on 50001

2026-06-14 15:11:30.038 INF audio: Audio device(s) found (*=default)

2026-06-14 15:11:30.111 INF audio: * ( 0 “alsa” ) Input Device : “default”

2026-06-14 15:11:30.111 INF audio: ( 1 “alsa” ) Input Device : “sysdefault”

2026-06-14 15:11:30.111 INF audio: ( 2 “alsa” ) Input Device : “hw:CARD=Device,DEV=0”

2026-06-14 15:11:30.111 INF audio: ( 3 “alsa” ) Input Device : “plughw:CARD=Device,DEV=0”

2026-06-14 15:11:30.111 INF audio: ( 4 “alsa” ) Input Device : “default:CARD=Device”

2026-06-14 15:11:30.111 INF audio: ( 5 “alsa” ) Input Device : “sysdefault:CARD=Device”

2026-06-14 15:11:30.111 INF audio: ( 6 “alsa” ) Input Device : “front:CARD=Device,DEV=0”

2026-06-14 15:11:30.111 INF audio: ( 7 “alsa” ) Input Device : “dsnoop:CARD=Device,DEV=0”

2026-06-14 15:11:30.111 INF audio: ( 8 “default” ) Input Device : “alsa_input.usb-C-Media_Electronics_Inc._USB_Audio_Device-00.mono-fallback”

2026-06-14 15:11:30.112 INF audio: ( 9 “default” ) Input Device : “alsa_output.usb-C-Media_Electronics_Inc._USB_Audio_Device-00.analog-stereo.monitor”

2026-06-14 15:11:30.112 INF audio: ( 10 “default” ) Input Device : “alsa_output.platform-107c701400.hdmi.hdmi-stereo.monitor”

2026-06-14 15:11:30.323 INF audio: * ( 0 “alsa” ) Output Device : “default”

2026-06-14 15:11:30.323 INF audio: ( 1 “alsa” ) Output Device : “sysdefault”

2026-06-14 15:11:30.323 INF audio: ( 2 “alsa” ) Output Device : “hw:CARD=vc4hdmi0,DEV=0”

2026-06-14 15:11:30.323 INF audio: ( 3 “alsa” ) Output Device : “plughw:CARD=vc4hdmi0,DEV=0”

2026-06-14 15:11:30.323 INF audio: ( 4 “alsa” ) Output Device : “default:CARD=vc4hdmi0”

2026-06-14 15:11:30.323 INF audio: ( 5 “alsa” ) Output Device : “sysdefault:CARD=vc4hdmi0”

2026-06-14 15:11:30.323 INF audio: ( 6 “alsa” ) Output Device : “hdmi:CARD=vc4hdmi0,DEV=0”

2026-06-14 15:11:30.323 INF audio: ( 7 “alsa” ) Output Device : “dmix:CARD=vc4hdmi0,DEV=0”

2026-06-14 15:11:30.323 INF audio: ( 8 “alsa” ) Output Device : “hw:CARD=vc4hdmi1,DEV=0”

2026-06-14 15:11:30.323 INF audio: ( 9 “alsa” ) Output Device : “plughw:CARD=vc4hdmi1,DEV=0”

2026-06-14 15:11:30.324 INF audio: ( 10 “alsa” ) Output Device : “default:CARD=vc4hdmi1”

2026-06-14 15:11:30.324 INF audio: ( 11 “alsa” ) Output Device : “sysdefault:CARD=vc4hdmi1”

2026-06-14 15:11:30.324 INF audio: ( 12 “alsa” ) Output Device : “hdmi:CARD=vc4hdmi1,DEV=0”

2026-06-14 15:11:30.324 INF audio: ( 13 “alsa” ) Output Device : “dmix:CARD=vc4hdmi1,DEV=0”

2026-06-14 15:11:30.324 INF audio: ( 14 “alsa” ) Output Device : “hw:CARD=Device,DEV=0”

2026-06-14 15:11:30.324 INF audio: ( 15 “alsa” ) Output Device : “plughw:CARD=Device,DEV=0”

2026-06-14 15:11:30.324 INF audio: ( 16 “alsa” ) Output Device : “default:CARD=Device”

2026-06-14 15:11:30.324 INF audio: ( 17 “alsa” ) Output Device : “sysdefault:CARD=Device”

2026-06-14 15:11:30.324 INF audio: ( 18 “alsa” ) Output Device : “front:CARD=Device,DEV=0”

2026-06-14 15:11:30.324 INF audio: ( 19 “alsa” ) Output Device : “surround21:CARD=Device,DEV=0”

2026-06-14 15:11:30.324 INF audio: ( 20 “alsa” ) Output Device : “surround40:CARD=Device,DEV=0”

2026-06-14 15:11:30.324 INF audio: ( 21 “alsa” ) Output Device : “surround41:CARD=Device,DEV=0”

2026-06-14 15:11:30.324 INF audio: ( 22 “alsa” ) Output Device : “surround50:CARD=Device,DEV=0”

2026-06-14 15:11:30.324 INF audio: ( 23 “alsa” ) Output Device : “surround51:CARD=Device,DEV=0”

2026-06-14 15:11:30.324 INF audio: ( 24 “alsa” ) Output Device : “surround71:CARD=Device,DEV=0”

2026-06-14 15:11:30.324 INF audio: ( 25 “alsa” ) Output Device : “iec958:CARD=Device,DEV=0”

2026-06-14 15:11:30.324 INF audio: ( 26 “alsa” ) Output Device : “dmix:CARD=Device,DEV=0”

2026-06-14 15:11:30.324 INF audio: ( 27 “default” ) Output Device : “alsa_output.usb-C-Media_Electronics_Inc._USB_Audio_Device-00.analog-stereo”

2026-06-14 15:11:30.324 INF audio: ( 28 “default” ) Output Device : “alsa_output.platform-107c701400.hdmi.hdmi-stereo”

2026-06-14 15:11:30.324 INF default: Looking for inputs

2026-06-14 15:11:30.326 INF default: Looking for outputs

2026-06-14 15:11:30.327 INF default: Searching for radios with Manufacturer = 2

2026-06-14 15:11:30.381 INF default: Searching for radios with Manufacturer = 2

2026-06-14 15:11:30.434 INF default: Searching for radios with Manufacturer = 2

2026-06-14 15:11:30.583 INF default: Setting color Preset 0 name “Dark”

2026-06-14 15:11:30.595 INF audio: "Client Audio input device default:CARD=Device found! "

2026-06-14 15:11:30.595 INF audio: "Client Audio output device default:CARD=Device found! "

2026-06-14 15:11:30.599 INF default: Changing queue interval to 250 ms

2026-06-14 15:11:30.601 INF rig: creating instance of rigCommander()

2026-06-14 15:11:30.601 INF rig: creating instance of yaesuCommander()

2026-06-14 15:11:30.601 INF cluster: starting dxClusterClient()

2026-06-14 15:11:30.607 INF rig: FTDI libraries loaded successfully

2026-06-14 15:11:30.607 INF rig: Could not open FT4222 device

2026-06-14 15:11:30.607 INF rig: The specific error was error number 2

2026-06-14 15:11:30.607 INF rig: Failed to initialize FT4222 device

2026-06-14 15:11:30.745 INF default: Changing queue interval to 100 ms

2026-06-14 15:11:30.745 INF system: Delay command interval timing: 100 ms

2026-06-14 15:11:30.761 WRN default: Cannot draw meter without scale data!

2026-06-14 15:11:30.761 WRN default: Cannot draw meter without scale data!

2026-06-14 15:11:30.761 WRN default: Cannot draw meter without scale data!

2026-06-14 15:11:30.785 WRN default: Cannot draw meter without scale data!

2026-06-14 15:11:30.785 WRN default: Cannot draw meter without scale data!

2026-06-14 15:11:30.785 WRN default: Cannot draw meter without scale data!

2026-06-14 15:11:30.855 WRN default: Cannot draw meter without scale data!

2026-06-14 15:11:30.855 WRN default: Cannot draw meter without scale data!

2026-06-14 15:11:30.855 WRN default: Cannot draw meter without scale data!

2026-06-14 15:11:31.054 INF rig: Response to rig id query “0800” decoded as 800

2026-06-14 15:11:31.054 INF rig: “Have new rig ID: 800”

2026-06-14 15:11:31.056 INF rig: “Loading Rig: FT-710 from /usr/local/share/wfview/rigs/FT-710.rig”

2026-06-14 15:11:31.057 INF rig: Adding mode: 49 “LSB”

2026-06-14 15:11:31.057 INF rig: Adding mode: 50 “USB”

2026-06-14 15:11:31.057 INF rig: Adding mode: 51 “CW-U”

2026-06-14 15:11:31.057 INF rig: Adding mode: 52 “FM”

2026-06-14 15:11:31.057 INF rig: Adding mode: 53 “AM”

2026-06-14 15:11:31.057 INF rig: Adding mode: 54 “RTTY-L”

2026-06-14 15:11:31.057 INF rig: Adding mode: 55 “CW-L”

2026-06-14 15:11:31.057 INF rig: Adding mode: 56 “DATA-L”

2026-06-14 15:11:31.058 INF rig: Adding mode: 57 “RTTY-U”

2026-06-14 15:11:31.058 INF rig: Adding mode: 65 “DATA-FM”

2026-06-14 15:11:31.058 INF rig: Adding mode: 66 “FM-N”

2026-06-14 15:11:31.058 INF rig: Adding mode: 67 “DATA-U”

2026-06-14 15:11:31.058 INF rig: Adding mode: 68 “AM-N”

2026-06-14 15:11:31.058 INF rig: Adding mode: 69 “PSK”

2026-06-14 15:11:31.058 INF rig: Adding mode: 70 “DATA-FM-N”

2026-06-14 15:11:31.059 INF default: Receiving rigcaps into repeater setup.

2026-06-14 15:11:31.059 INF default: repeaterSetup got rigcaps for: “FT-710”

2026-06-14 15:11:31.060 INF system: Running configureVFOs()

2026-06-14 15:11:31.127 INF default: nb max val 1

2026-06-14 15:11:31.127 INF default: nr max val 1

2026-06-14 15:11:31.127 INF default: Changing queue interval to 25 ms

2026-06-14 15:11:31.127 INF system: Delay command interval timing: 25 ms

2026-06-14 15:11:31.127 INF system: Start periodic commands (and delete unsupported)

2026-06-14 15:11:31.139 WRN default: Cannot draw meter without scale data!

2026-06-14 15:11:31.139 WRN default: Cannot draw meter without scale data!

2026-06-14 15:11:31.175 WRN default: Cannot draw meter without scale data!

2026-06-14 15:11:31.175 WRN default: Cannot draw meter without scale data!

2026-06-14 15:11:31.184 INF default: "Data: 0 Input: USB current: "

2026-06-14 15:11:31.541 INF rig: “Selected Mode” New mode 49 “LSB” Old mode 49

2026-06-14 15:11:31.541 INF system: receiveMode “Received new mode for Main (0): 49 (LSB) filter:255 data:255”

2026-06-14 15:11:31.617 INF rig: “Unselected Mode” New mode 49 “LSB” Old mode 49

2026-06-14 15:11:31.644 INF rig: Rig error, last command sent: “Meter Type” (min: 0 max: 255 bytes: 7 ) data: “RM0000000;”

2026-06-14 15:11:31.951 INF default: “Data: 0 Input: AUTO current: USB”

2026-06-14 15:12:14.706 WRN qt.qpa.wayland: Wayland does not support QWindow::requestActivate()

[eliggett (Elliott Liggett)]

@ebfourie

2026-06-14 15:11:30.607 INF rig: FTDI libraries loaded successfully

2026-06-14 15:11:30.607 INF rig: Could not open FT4222 device

2026-06-14 15:11:30.607 INF rig: The specific error was error number 2

2026-06-14 15:11:30.607 INF rig: Failed to initialize FT4222 device

You are very close. I will let one of the other Yaesu testers comment on how to proceed.

[ebfourie (Eben)]

Thanks Elliot.

Im picking up a club IC-7300 on Tue night, so I can test that from Ubuntu and Rasbian as well. I figure if that works at least I know the USB cable is ok…

[Nakao]

Hello.

Error code 2 indicates FT_DEVICE_NOT_FOUND.

Sorry, let me verify this.
Were you able to confirm the FT4222 device using the lsusb command?

Solution 1
The primary cause of this error in a Linux environment is that the OS’s standard serial driver (ftdi_sio) automatically takes control of the device, preventing the FT4222-specific D2XX/libft4222 drivers from accessing it.

1. Unload the standard drivers
   When Linux detects an FTDI chip, it automatically loads the standard serial conversion drivers (ftdi_sio and usbserial). This can sometimes cause conflicts.
   Open a terminal and run the following commands to disable them:

sudo modprobe -r ftdi_sio
sudo modprobe -r usbserial

Please run the program again and let us know the results.

DE JG3HLX NAKAO

[Nakao]

Hello.

The PC I ordered arrived, so I installed Debian 13 (Trixie).

1. I built wfview and configured it for the FT-710 while referring to the manual.

   1. Installed libft4222
   2. Also needed to install libftd2xx

2. Launch wfview
   An error stating “ttyUSB0 cannot be used” occurred.

Solution
Permissions are required to use ttyUSB0.
I added the target user to the dialout group.
$ sudo usermod -aG dialout username

Restarting the computer ensures the changes take effect.

3. Launch wfview
   Error number 2 occurred
   Configure permissions to access the SPI device as described in the manual.

If error number 2 still occurs after configuration, check if you can launch the program as root. If it still fails to launch, there is another issue.

4. wfview launched (displayed) without issues

Here is the startup log:
https://termbin.com/6p3c

Point of concern
Although this was also seen in other users’ logs, I do not understand why audio-related logs are being displayed.

DE JG3HLX NAKAO

[eliggett (Elliott Liggett)]

Hi Nakao and Eben,

Did you do the udev rules on this page:

Yaesu FT-710 Setup | wfview

They should help with the permissions issue for the 4222 device. But since I don’t have this device, I was unable to verify. Feel free to send corrections.

Also, Nakao may be on to something with the modprobe command and his recommendation to check lsusb is a good one too. Please try those things, Eben, and let us know what happens.

—E
de W6EL

[ebfourie (Eben)]

@eliggett

Did you do the udev rules on this page:

Yes

@Nakao

Were you able to confirm the FT4222 device using the lsusb command?

pi@raspberrypi:~ $ ls -l /dev/serial/by-id/
total 0
lrwxrwxrwx 1 root root 13 Jun 15 12:15 usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_011F388D-if00-port0 → ../../ttyUSB0
lrwxrwxrwx 1 root root 13 Jun 15 12:15 usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_011F388D-if01-port0 → ../../ttyUSB1
pi@raspberrypi:~ $ lsusb | grep FT4222
Bus 001 Device 004: ID 0403:601c Future Technology Devices International, Ltd FT4222
pi@raspberrypi:~ $

@Nakao

sudo modprobe -r ftdi_sio
sudo modprobe -r usbserial

Did this as well. To get the 2nd command to work I had to unplug the usb cable and reboot, as it was giving me a “in use” error.

Started wfview again, still seeing the FT4222 error 2.

Will look at libftd2xx next.

[Nakao]

Hello

I think the “in use” error when running sudo modprobe -r usbserial is because cp210x is currently using it.
To verify this, run the following command; the device listed to the right of “usbserial” is the one currently in use.
lsmod | grep usbserial

Correct example
$ lsmod | grep usbserial
usbserial 73728 1 cp210x

To verify, please show me the contents of the created udev rule using the following command.

ls -l /etc/udev/rules.d/99-ftdi.rules
cat /etc/udev/rules.d/99-ftdi.rules

DE JG3HLX NAKAO

[ebfourie (Eben)]

pi@raspberrypi:~ $ lsmod | grep usbserial

usbserial 81920 1 cp210x

pi@raspberrypi:~ $ ls -l /etc/udev/rules.d/99-ftdi.rules

-rw-r–r-- 1 root root 78 Jun 15 12:14 /etc/udev/rules.d/99-ftdi.rules

pi@raspberrypi:~ $ getent group dialout

dialout:x:20:pi

pi@raspberrypi:~ $ cat /etc/udev/rules.d/99-ftdi.rules

SUBSYSTEM==“usb”, ATTR{idVendor}==“0403”, ATTR{idProduct}==“601c”, MODE=“0666”

I did have a missing character in the 99-ftdi.rules file. iVendor instead of idVendor.

Corrected that, and it looks like I am getting past the FT4222 load now !

Getting the same sync issue on Rasbian as I am getting on my Ubuntu machine

2026-06-15 15:47:08.425 INF system: Start periodic commands (and delete unsupported)

2026-06-15 15:47:08.437 WRN default: Cannot draw meter without scale data!

2026-06-15 15:47:08.437 WRN default: Cannot draw meter without scale data!

2026-06-15 15:47:08.455 WRN default: Cannot draw meter without scale data!

2026-06-15 15:47:08.456 WRN default: Cannot draw meter without scale data!

2026-06-15 15:47:08.476 WRN default: Cannot draw meter without scale data!

2026-06-15 15:47:08.476 WRN default: Cannot draw meter without scale data!

2026-06-15 15:47:08.484 INF default: "Data: 0 Input: USB current: "

2026-06-15 15:47:08.838 INF rig: “Selected Mode” New mode 49 “LSB” Old mode 49

2026-06-15 15:47:08.838 INF system: receiveMode “Received new mode for Main (0): 49 (LSB) filter:255 data:255”

2026-06-15 15:47:08.915 INF rig: “Unselected Mode” New mode 49 “LSB” Old mode 49

2026-06-15 15:47:08.941 INF rig: Rig error, last command sent: “Meter Type” (min: 0 max: 255 bytes: 7 ) data: “RM0000000;”

2026-06-15 15:47:09.250 INF default: “Data: 0 Input: AUTO current: USB”

2026-06-15 15:47:09.874 WRN qt.qpa.wayland: Wayland does not support QWindow::requestActivate()

2026-06-15 15:47:10.116 INF rig: FT4222 failed to resync

2026-06-15 15:47:10.126 INF rig: Init FT4222 as SPI master

2026-06-15 15:47:10.133 INF rig: Init FT4222 as SPI master completed successfully!

2026-06-15 15:47:12.272 INF rig: FT4222 failed to resync

2026-06-15 15:47:12.282 INF rig: Init FT4222 as SPI master

2026-06-15 15:47:12.289 INF rig: Init FT4222 as SPI master completed successfully!

2026-06-15 15:47:13.681 WRN qt.qpa.wayland: Wayland does not support QWindow::requestActivate()

2026-06-15 15:47:14.420 INF rig: FT4222 failed to resync

2026-06-15 15:47:14.430 INF rig: Init FT4222 as SPI master

2026-06-15 15:47:14.436 INF rig: Init FT4222 as SPI master completed successfully!

2026-06-15 15:47:16.539 INF rig: FT4222 failed to resync

2026-06-15 15:47:16.549 INF rig: Init FT4222 as SPI master

2026-06-15 15:47:16.556 INF rig: Init FT4222 as SPI master completed successfully!

2026-06-15 15:47:18.661 INF rig: FT4222 failed to resync

[Nakao]

Hello.

If the device resets every two seconds after synchronization, it is likely due to a communication issue (missing packets?) between the PC and the FT4222 chip.
Solutions
This problem occurs when there is noise on the USB cable.
Please try the following for the USB cable:

1. Attach a ferrite core.
2. Replace it with a high-quality shielded cable.

wfview is also a likely culprit.
It might seem odd to ask this here, but could differences in PC processing power cause synchronization errors at the end of packets (4096 bytes)?

DE JG3HLX NAKAO

[Nakao]

I confirmed that it works on the Raspberry Pi 4.

I followed the manual exactly, but encountered a permission error with the FT4222; I resolved it by installing the D2XX driver.

Even on a slow PC, the waterfall is visible

DE JG3HLX NAKAO

[ebfourie (Eben)]

Hi Nakao & Elliot

Installed FTD2xx driver on Pi 5.

Still no waterfall.

Then tested using a loan IC-7300.

Waterfall works no issues.

So, to me that points to the fact that it is not my the Pi5 or the USB A-to-B cable, but something in the software ?

P.S. also tested on Ubuntu laptop and similar results. Ic-7300 waterfall works fine, Ft-710, cat control ok but waterfall just blue, no signal.

Eben

[eliggett (Elliott Liggett)]

Hi Eben,

The waterfall on the 7300 comes with all the other 7300 data over a normal USB-serial interface.

The waterfall data on the yaesu comes in via another method which, as you see, is more tricky. Yaesu waterfall can work, but the protocol of the radio’s waterfall interface is much more sensitive to timing – do try some other USB cables as silly as the suggestion may sound, and keep an eye on the log of wfview for related messages each time. Keep in mind that we are also at the behest of a closed-source driver with the yaesu; we cannot just peek inside and see what it’s upset about.

If you want to loan me a Yaesu, I will work on it with a Pi and see what I can figure out. @phil may also have some suggestions as he has a Yaesu too.

–E
de W6EL