First reply, I am using a Gigabit usb3 lan “C” adapter& cat5 cable from the host port to the router 4m away. The system info is …
APP: v1.1.9 Sept 14 2024,12:11:57
Base v2.2.8 Sept 15 2024,15:22:37
I will get a log file in the next reply
John
No promises but I have just created a new rig file for the X6200 (should work for the 6100 as well) as the IC705 has lots of features that are not supported by the little Xiegu and I see errors in the log of commands being bounced. These bounces are taking up valuable network bandwidth and could be part of the reason for the audio drop-outs.I’ve searched this forum and the online user manual to see how to change the rig file beiung used by WFView and not found a simple option, so I’m currently de-installing and re-installing, in the hope that I will get the chance to specify my custom rig file in place of the standard ones.
Watch this space …
73 Ed DD5LP.
EDIT: Added three back ticks to the top and bottom to format the text.
2025-02-26 16:39:05.282 INF system: wfview version: 2.03 (Git:ed9a02a on Jan 3 2025 at 21:05:03 by phil.taylor@PHIL-WIN11)
2025-02-26 16:39:05.283 INF system: Operating System: Windows 11 Version 24H2 (x86_64)
2025-02-26 16:39:05.283 INF system: Looking for External Dependencies:
2025-02-26 16:39:05.283 INF system: QT Runtime Version: 6.8.1
2025-02-26 16:39:05.283 INF system: OPUS Version: libopus 1.5.1-19-g95dbea83
2025-02-26 16:39:05.283 INF system: HIDAPI Version: 0.14.0
2025-02-26 16:39:05.283 INF system: EIGEN Version: 3.4.90
2025-02-26 16:39:05.283 INF system: QCUSTOMPLOT Version: 2.1.1
2025-02-26 16:39:05.283 INF system: RTAUDIO Version: 6.0.1
2025-02-26 16:39:05.283 INF system: PORTAUDIO Version: PortAudio V19.7.0-devel, revision unknown
2025-02-26 16:39:05.285 INF default: Starting caching queue handler thread (ThreadId: 0x4af0 )
2025-02-26 16:39:05.481 INF system: Loading settings from "\\HKEY_CURRENT_USER\\Software\\wfview\\wfview"
2025-02-26 16:39:05.525 INF gui: Got Audio Output from Settings: "Speakers (2- USB Audio CODEC )"
2025-02-26 16:39:05.525 INF gui: Got Audio Input from Settings: "Microphone (2- USB Audio CODEC )"
2025-02-26 16:39:05.532 INF default: tciServer() listening on 50001
2025-02-26 16:39:05.539 INF default: Setting color Preset 2 name "2"
2025-02-26 16:39:05.590 INF audio: Audio device(s) found (*=default)
2025-02-26 16:39:05.625 INF audio: * ( 0 ) Input Device : "Microphone (USB Audio Device)"
2025-02-26 16:39:05.626 INF audio: ( 1 ) Input Device : "Line 2 (Virtual Audio Cable)"
2025-02-26 16:39:05.626 INF audio: ( 2 ) Input Device : "Line 1 (Virtual Audio Cable)"
2025-02-26 16:39:05.626 INF audio: ( 3 ) Input Device : "Mic 1 (Virtual Audio Cable)"
2025-02-26 16:39:05.626 INF audio: ( 4 ) Input Device : "Microphone (2- USB Audio CODEC )"
2025-02-26 16:39:05.634 INF audio: * ( 0 ) Output Device : "Speakers (USB Audio Device)"
2025-02-26 16:39:05.634 INF audio: ( 1 ) Output Device : "Line 2 (Virtual Audio Cable)"
2025-02-26 16:39:05.634 INF audio: ( 2 ) Output Device : "Line 1 (Virtual Audio Cable)"
2025-02-26 16:39:05.634 INF audio: ( 3 ) Output Device : "HP E231 (Intel(R) Display Audio)"
2025-02-26 16:39:05.636 INF audio: ( 4 ) Output Device : "Speakers (2- USB Audio CODEC )"
2025-02-26 16:39:05.636 INF default: Looking for inputs
2025-02-26 16:39:05.637 INF default: Looking for outputs
2025-02-26 16:39:05.639 INF audio: "Client Audio input device Microphone (2- USB Audio CODEC ) found! "
2025-02-26 16:39:05.639 INF audio: "Client Audio output device Speakers (2- USB Audio CODEC ) found! "
2025-02-26 16:39:05.724 INF default: Changing queue interval to 250 ms
2025-02-26 16:39:05.725 INF rig: creating instance of rigCommander()
2025-02-26 16:39:05.725 INF rig: creating instance of icomCommander()
2025-02-26 16:39:05.725 INF cluster: starting dxClusterClient()
2025-02-26 16:39:05.725 INF udp: Starting udpHandler user: "User" rx latency: 150 tx latency: 150 rx sample rate: 48000 rx codec: 4 tx sample rate: 48000 tx codec: 4
2025-02-26 16:39:05.726 INF cluster: Starting tcpSocket() on: 1836008295
2025-02-26 16:39:05.731 INF udp: UDP Stream bound to local port: 52845 remote port: 50001
2025-02-26 16:39:05.830 INF system: Skipping automatic CIV, using user-supplied value of 164
2025-02-26 16:39:06.236 INF udp: udpHandler : Received I am here from: "::ffff:192.168.1.117"
2025-02-26 16:39:06.237 INF udp: udpHandler : Received I am here
2025-02-26 16:39:06.239 INF udp: udpHandler : Received I am ready
2025-02-26 16:39:06.239 INF udp: udpHandler : Sending login packet
2025-02-26 16:39:06.242 INF udp: Got connection type: "WFVIEW"
2025-02-26 16:39:06.242 INF udp: udpHandler : Received matching token response to our request
2025-02-26 16:39:06.242 INF udp: udpHandler : Detected connection speed WFVIEW
2025-02-26 16:39:06.247 INF udp: udpHandler "Received radio capabilities, Name: X6100, Audio: ICOM_VAUDIO, CIV: a4, MAC: 00:90:c7:36:44:3a CAPF: 5001"
2025-02-26 16:39:06.249 INF udp: Got Connection status for: X6100 Busy: 0 Computer IP "0.0.0.0"
2025-02-26 16:39:06.249 INF udp: Got Radio 0
2025-02-26 16:39:06.249 INF udp: Find available local ports
2025-02-26 16:39:06.256 INF default: Received serial port baud rate from remote server: 115200
2025-02-26 16:39:06.256 INF default: Changing queue interval to 100 ms
2025-02-26 16:39:06.256 INF system: Delay command interval timing: 100 ms
2025-02-26 16:39:06.262 INF udp: Starting udpCivData
2025-02-26 16:39:06.264 INF udp: UDP Stream bound to local port: 52846 remote port: 50002
2025-02-26 16:39:06.265 INF udp: Starting udpAudio
2025-02-26 16:39:06.275 INF udp: UDP Stream bound to local port: 52847 remote port: 50003
2025-02-26 16:39:06.276 INF udp: udpHandler Got serial and audio request success, device name: "X6100"
2025-02-26 16:39:06.277 INF udp: Got Connection status for: X6100 Busy: 1 Computer DESKTOP--wfview IP "192.168.1.228"
2025-02-26 16:39:06.278 INF audio: Output audio handler starting: "Speakers (2- USB Audio CODEC )"
2025-02-26 16:39:06.278 INF audio: Input audio handler starting: "Microphone (2- USB Audio CODEC )"
2025-02-26 16:39:06.279 INF udp: udpCivData : Received I am here
2025-02-26 16:39:06.279 INF udp: udpAudio : Received I am here
2025-02-26 16:39:06.282 INF audio: Output thread id 0x2f54
2025-02-26 16:39:06.282 INF audio: Output start() running
2025-02-26 16:39:06.282 INF audioconverter: Starting audioConverter() Input: 1 Channels of 0 48000 Int16 Output: 2 Channels of 0 48000 Float
2025-02-26 16:39:06.286 INF audio: Input thread id 0x1ee0
2025-02-26 16:39:06.286 INF audio: Input start() running
2025-02-26 16:39:06.287 INF audioconverter: Starting audioConverter() Input: 1 Channels of 0 48000 Float Output: 1 Channels of 0 48000 Int16
2025-02-26 16:39:06.337 INF udp: udpHandler Got new radio time: ( 59946517 ) QTime(16:39:06.517) Offset: -180 Calc time: QTime(Invalid)
2025-02-26 16:39:06.363 INF udp: udpCivData Got new radio time: ( 59946544 ) QTime(16:39:06.544) Offset: -181 Calc time: QTime(Invalid)
2025-02-26 16:39:06.803 INF udp: udpAudio Got new radio time: ( 59946984 ) QTime(16:39:06.984) Offset: -181 Calc time: QTime(Invalid)
2025-02-26 16:39:06.842 INF rig: "Have new rig ID: 0xa4"
2025-02-26 16:39:06.844 INF rig: "Loading Rig: IC-705 from C:/Program Files/wfview/rigs/IC-705.rig"
2025-02-26 16:39:06.847 INF serial: Got rigcaps for: "IC-705"
2025-02-26 16:39:06.847 INF rig: Using incomingCIVAddr: (int): 164 hex: "0xa4"
2025-02-26 16:39:06.847 INF default: Receiving rigcaps into repeater setup.
2025-02-26 16:39:06.847 INF default: repeaterSetup got rigcaps for: "IC-705"
2025-02-26 16:39:06.847 INF system: Running configureVFOs()
2025-02-26 16:39:06.915 INF cw: Starting sidetone. Thread= 0x9f8
2025-02-26 16:39:06.915 INF cw: Sidetone init() Thread= 0xa5c
2025-02-26 16:39:06.918 INF default: Changing queue interval to 25 ms
2025-02-26 16:39:06.918 INF system: Delay command interval timing: 25 ms
2025-02-26 16:39:06.918 INF system: Start periodic commands (and delete unsupported)
2025-02-26 16:39:06.923 INF cw: "Sidetone Output: Speakers (USB Audio Device) (volume: 0 rate: 44100 type: 2"
2025-02-26 16:39:07.305 INF default: Band Buttons found current band: "40m"
2025-02-26 16:39:07.664 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:07.664 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:08.280 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:08.533 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:09.812 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:10.066 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:11.390 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:11.647 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:12.975 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:13.228 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:14.515 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:14.824 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:16.448 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:17.011 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:18.694 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:19.309 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:20.990 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:21.607 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:23.295 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:23.858 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:25.597 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:26.158 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:27.896 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:28.459 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:30.197 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:30.760 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:32.495 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:33.110 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:34.793 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:35.409 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:37.104 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:37.267 INF udp: Audio Watchdog: no audio data received for 30s, restart required? last: QTime("16:39:06.888")
2025-02-26 16:39:37.267 INF audioconverter: Closing audioConverter() Input: 1 Channels of 0 48000 Int16 Output: 2 Channels of 0 48000 Float
2025-02-26 16:39:37.292 INF audioconverter: Closing audioConverter() Input: 1 Channels of 0 48000 Float Output: 1 Channels of 0 48000 Int16
2025-02-26 16:39:37.766 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:39.807 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:40.472 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:42.513 INF rig: Unsupported command received from rig "1a0500" Check rig file
2025-02-26 16:39:43.275 INF rig: Unsupported command received from rig "1a0500" Check rig fileI
Ed, you’ve got us hooked. 
'ER its actually hook, line and sinker! 
Civ commands use an almost insignificant amount of bandwidth compared to audio, so I doubt this will be the issue.
If you use rigreator, simply remove the recurring commands that you don’t think are needed, then save the file. As long as you don’t change the default save directory, It will be used in place of the wfview provided one
From your log:
Hm, doesn’t this line indicate there’s no audio anymore? 
Dont forget I had wf and the ios app running together and both had audio at the same time. The ios app was via wifi and the wf via a lan cable, perhaps a sharing function involved ?
Duty calls so will be back after 7pm
Yes as well as going through the list of CiV commands (I’ve done this rig definition before in several programs, so I’m happy with what will work and what not) and I also removed the recurring commands that were either not supported by the radio or not critical.
While the CAT control bandwidth saved may be minimal, there is also the processing effort both in the embedded WFserver code in the X6100/6200 and the processing within the WFView program on Windows.
I did not overwrite the existing IC-705 rig file, rather created an X-6200 one (in the user rigs directory). I have just done a complete de-install and fresh install but some of the settings I had set before are still appearing so it seems that not all registry entries are removed and I did not get asked what radio I am using just how I will be connecting to it.
I’m sure someone on this list can tell me how to change between rig files in WFView for Windows??
By the way, it also seems that WFView only wants to have ICOM, Yaesu & Kenwood as radio manufacturers (a conf/ini file change I expect) - but at the moment my rig file is for an ICOM X-6200 !!
Step by step…
73 Ed DD5LP.
Ed et al,
The Xiegu radios self-identify as Icom IC-705. I assure you, we wish they had picked an unused or ancient CI-V identifier rather than reusing the IC-705 address.
Worse yet, the 6100 and 6200 have an added command, which returns “6100” on both radios. This is far from ideal.
If you are using rig creator to tune the rig file, be aware that wfview may load the 705 file anyway. This is because they share the same ID!! You will need to place the modified file in the user-writable directory so that it takes preference over our stock 705 file. Double-check the wfview log to verify which rig file is actually being loaded and used.
There was a screenshot here showing the “server” settings page for wfview, which is not relevant for use as a client to the X61/6200. So please don’t try and replicate those settings. What would be helpful is a screenshot of “Radio Access” showing the various settings.
Lastly, if you do make a rig file with good results, please share it! This is a community-driven project and your work is appreciated.
Thanks,
—E
de W6EL
Looks like the X6100 just doesn’t have the muscle for the job. The moment wfserver kicks in, one of its CPU cores goes full “help, I’m dying” mode at 100%. Probably not ideal.
Anyway, since you asked, here are my radio settings – they give me at least a few precious seconds of audio before the connection gracefully keels over and dies: 
Hi Elliot,
Thanks for the help.
One correction - the Xiegu-specific CiV command 1D 19 returns “6100” from the X6100 and “6200” from the X6200. Initially, it was identical but was fixed in a firmware upgrade (v1.0.3 I think).
Also, within my X6200 rig file, I have updated the RigCtlD code - the IC705 was 3085 the X6200 is 3091 (and a new 6100 rig file would have 3087 in this code).
I agree, I would prefer that Xiegu had not chosen the CiV code A4, especially as it can’t be easily changed from the radio’s user menus (as can be done on many ICOM radios). Are you saying that the rig file loaded is based on the CiV code? I hope not, but if it is, I suppose I could backup the IC705 rig file and rename mine to be IC705 rather than X6200.
This is from the LOG:
2025-02-26 19:58:17.355 INF default: “Found User Rig X-6200 with CI-V address of 0xa4 and newer or same version than system one (2.03>=2.02)”.
So it looks like my file is being loaded - time to see if this makes any difference.
By the way, I am using the built-in X6200 WiFi connection but have ordered today an external USBC-Ethernet adapter for the radio so I can connect via cable to the network. That should arrive tomorrow.
Of course, I am happy to share my revised rig file (once I have checked it isn’t “buggy”), I have done the same with OmniRig, PocketRxTx and others when I do this kind of work.
One last question - is there a way for the rig file to have the correct manufacturers name? at the moment in the rig creator menu, there is no way that I can see to add a new name to the list of ICOM, Yaesu and Kenwood. I can of course change it in the actual text file, but it would be better that the manufacturer name could be entered through rig creator.
73 Ed DD5LP.
I have the same problem. Using a new X6200.
Almost all of this discussion is well over my head.
Seems for the moment a no go for me.
John Wimer, KO4KVV
The CIV address shouldn’t be used to identify the radio type. I could set my 705 to a totally different CIV address.
73 Phil GM3ZZA
It isn’t. Wfview queries for the radio model (which just happens to be the default C-IV address)
If you set a different CI-V address, wfview would still identify the correct model.
Hi Ed, like others I have no real idea what you modify where…anyhow, once you’re done it would be brilliant your share a bit of your knowledge and teach us newbies how to make wfview audio working with our Xiegus X6100/X6200.
73, Roland
No this isn’t possible, as it is ‘pretending’ to be an Icom rig. If you change this in the rig file, it will not work.
As I said, I am pretty sure that this won’t make any difference, but what do I know, I only wrote the software?
It would be useful to know ‘which’ thread is maxing out the CPU, my guess is audioConverter() depending on the version of htop, you should be able to tell it to display ‘custom thread names’
John,
Can you show a screenshot of wfview on the Radio Access page?
–E
de W6EL
Thanks for the clarification Phil - all good. Yes I know you and Elliot are the minds behind this great piece of software (thanks for that).
As the model number is given in the bottom right of the program and the program is picking up my rig file from the user rig file directory rather than the standard IC705 one (as proved in the log) - all is good. The only place where ICOM is mentioned is within the rig creator. The fact that the program is picking up the updated rig file means I don’t have to select it from a list, which is where the correct manufacturer name would have been nice.
Onwards and upwards …
73 Ed DD5LP (G8GLM/VK2JI)
