I have Xiegu X6100 connected through my network, I have Wfview on windows 11. The radio connects fine but I only have about 30 seconds of audio then the audio drops out. Close Wfview and reopen and 30 more seconds of audio. Can anyone help?
Most likely a network connectivity issue, look in the wfview log for retransmissions. You need to make sure the network between wfview and wfserver is very stable, too many lost packets and it will simply give-up.
Phil’s suggestion reminded me that there is a setting called “RX Latency”. I am no wfview expert by any means, however I wonder if you would see any better performance on RX by assuring it is set to 250 and adjusting from there to see if it has any impact.
Sincerely,
Ev, W2EV
I have a X6100 and if I an 1…2m awat fron an AP, it breaks in pieces. Using an ethernet cable direct connected, all is fine rx audiowise
Hello. Can confirm that the same happens on Windows 10 and even with USB-Ethernet connected cable. Starting with sound, then after some time (<60sec) sound distorts and later no sound till reconnecting. Changed latency values, tried different codecs, nothing helps or does no sound at all. Xiegu X6200.
2025-02-04, an, 11:17 Roeland Jansen via wfview <noreply@wfview.org> rašė:
Hi Peter,
This thread is about the Xiegu X6100, please open a new thread with your question.
–E
de W6EL
Hi everyone,
A bit stunned to see this issue affecting even the relatively fresh X6200.
I’ve tried everything – and I mean everything, including but not limited to:
- Ditching Wi-Fi for a good old-fashioned LAN cable
- Experimenting with every possible codec and sample rate combination
- Cycling through all available Linux audio subsystems like a DJ on speed
- Updating everything to the latest firmware and software versions
- Ensuring there’s zero packet loss and an RTT so low (1ms) it makes fiber connections jealous
And yet, no matter what I do, after 10 to 30 seconds, the audio always trips over a watchdog timeout.
So, my most pressing question:
Can anyone positively confirm that wfview works with full audio support on Windows when paired with the X6100/X6200?
Or is this just another tall tale that old-timers tell wide-eyed newcomers after one too many schnapps?
Thanks in advance, and 73 de Norbi, DF1PC
What version of wfview are you using?
I don’t have a X6100 or X6200, so I cannot comment on how well it works. But I have yet to receive a single report that these radios can transmit network audio. These radios also lack (as far as I can tell) a way to tell the transmitter to transmit LAN audio versus audio from the mic.
–E
de W6EL
I’m now on the latest 2.03 but had also been trying 1.64 a few months ago.
So that makes two of us. 
But I do wonder a bit why Xiegu went through the trouble of creating beautifully illustrated manuals in multiple languages for connecting wfview if it simply doesn’t work. Strange.
Anyway, many thanks for getting back to me so quickly.
Best regards, Norbi
I suspect they were very close to getting it working in the way we were all hoping for, but that there wasn’t funding for continued development. It’s hard to tell.
I think these rigs do set a nice example for what can be accomplished with modern hardware – the embedded software and server ideas could be improved upon and implemented in other experimental or low-volume radios without the massive expense that was required to do so decades ago.
I haven’t checked the groups.io for these radios in a while, so maybe some people have come up with workarounds or have updated the software on the rig to work better. It’s possible.
Feel free to share your log file with the timeout notices. It could be informative.
–E
de W6EL
termbin seems to be down, but I do in fact see some messages in the log that look different from when I was using v1.64, messages like these (excerpt):
2025-02-19 20:26:48.180 INF audio: Input Unsupported sample rate 44100
2025-02-19 20:26:48.180 INF audio: Input Unsupported sample rate 44100
2025-02-19 20:26:48.180 CRT audio: Input Cannot find suitable format, aborting: Invalid sample rate
2025-02-19 20:26:48.189 INF udp: udpCivData : Received I am here
2025-02-19 20:26:48.195 INF udp: udpAudio : Received I am here
2025-02-19 20:26:48.211 INF audioconverter: Starting audioConverter() Input: 1 Channels of 1 8000 Int16 Output: 2 Channels of 0 48000 Float
2025-02-19 20:26:48.211 INF audioconverter: wf_resampler_init() returned: 0 resampleRatio: 6
2025-02-19 20:26:48.212 INF audio: Output device successfully opened
And this:
2025-02-19 20:26:51.943 INF rig: Unsupported command received from rig "1a0500" Check rig file
Just a quick reminder – I do hear RX audio for a few seconds before it cuts out, but latency is always very high, like 490ms.
I’ll keep an eye on termbin, and once it’s back, I’ll gladly upload the full log. It’s pretty short.
73, Norbi
The X6100 has its wifi board mounted just behind the lcd display but between two pcb’s behind it, making wifi comms a mission impossible, unless your router is next to the radio. Its Xiegu’s biggest blunder imo. But it can be overcome by adding an external antenna via a thinnnnn coaxial cable, but its delicate work and not for the feaint hearted. I chose to use a lan adapter cable into the host port, then run a cable to the router. There should be a server screen on the x6100 press system, then select WFserver. Check the contesnt for correct settings
1 Like
Whatever the latency is set at, be it with WFview on Win10 or Ubuntu, I always get only a few seconds of audio, sometimes up to 15 or 20 s, then audio stalls. The log always tells me that the server did not send audio for 2s:
2025-02-26 15:33:06.559 INF rig: Using incomingCIVAddr: (int): 164 hex: “0xa4”
2025-02-26 15:33:06.559 INF serial: Received rigCapabilities for “IC-705”
2025-02-26 15:33:06.559 INF rig: Have rig ID: decimal: 164
2025-02-26 15:33:06.560 INF system: Delay command interval timing: 25 ms
2025-02-26 15:33:10.680 INF udp: Audio Watchdog: no audio data received for 2s, restart required?
2025-02-26 15:33:10.680 INF audioconverter: Closing audioConverter() Input: 1 Channels of 0 48000 SignedInt 16 Output: 2 Channels of 0 48000 SignedInt 16
2025-02-26 15:33:10.704 INF audioconverter: Closing audioConverter() Input: 1 Channels of 0 48000 SignedInt 16 Output: 1 Channels of 0 48000 SignedInt 16
I’m afraid the WFserver on the X6100 is the culprit.
I have the X6100 connected to a wired ethernet network via a USB-Gbit adapter. Base fw is 1.1.8
Thanks for any clue for debugging the thing.
Bonjour Michel,
Yep, that’s exactly what everyone seems to run into when using wfview with the X6100. At this point, it’s almost a feature!
I even had a chat with Radioddity support (super friendly folks, by the way). Just to rule out any weird network gremlins, I connected the X6100 directly to an Ubuntu client via a switch—no router, no middlemen, just a straight-up switch. Fired up Wireshark, and sure enough, after about 15 seconds, the UDP packets shrink from a healthy ~900 bytes to a mere 20. Looks to me like the X6100 hardware just can’t keep up with assembling packets quickly enough.
Radioddity has already reported the issue to Xiegu. A quick fix isn’t on the horizon, but hey, at least it’s on the developers’ radar now. Fingers crossed!
Cheers and 73,
Norbi, DF1PC
If it is a CPU exhaustion issue, then I would avoid Opus and use a codec that requires minimal processing, like LPCM16, and with a lower sample rate,16 KHz should be more than sufficient for most uses.
As an aside, although we were originally asked for permission to include wfserver within the X6100, we have had no further contact with Xiegu, and they have not submitted any patches/fixes to us, so we have no idea what version of wfserver they are using in the different radios.
1 Like
The only fact I can contribute is that the audio issue under Windows 11 is the same with the X6200 (as already posted in another thread). Looks like Xiegu implementation of the wfserver dosen’t work as expected…
1 Like
I use a x6100 with wfview and no issue with audio. Could it be that the ip address changes from time to time . ?
Wow! This might just be the first confirmed case of someone actually getting wfview to work on the X6100. You must be a wizard, John. 
Can you share a few more details—firmware version, audio settings, client setup, and any secret rituals you performed under the moonlight or something?
And to answer your question: in my setup, the IP is locked down by the DHCP service.
73 de DF1PC