Quote History Originally Posted By Amish_Bill:
by all means, please post your notes
knowledge is best when shared
View Quote
The latest published version of wfview is 1.65 - which has very minimal support for the 7200. To get the latest enhancements (v1.94+) you have to build from source and issue the "creator-widgets" argument against the build script. This is easy to do in Linux and links to the build script can be found on the Developer's Corner area of the wfview website.
Once installed on client and server device, configure the Radio Server section of the program on the server PC. "Half Duplex" will cause the program to crash every single time. Set it to Full Duplex. Joe is likely removing this choice in future builds. The audio devices and audio system should be set to use the two Burr-Brown devices (one for input; the other output) via the QT Audio drop-down. Set the radio to use a USB connection (in Radio Access) and set a user name/password (in the Radio Server section). Connect the 7200's rear panel USB interface to a USB jack on the host system - you're using it for audio I/O as well as CAT control.
On the client: If using an RC-28 remote, there are instructions on the support forum for adding a profile to the /etc/rules.d directory to allow users to access USB HIDs. Once this is done and the client launched you should be able to go to the "External Control" section of the Settings dialog, select the RC-28 and configure its buttons. Use QT Audio here - your headset must be registered as a Hands-Free Profile (HFP) device in Bluetooth Manager. Select "source" and "sink" for the input and output devices appropriately. My KH-23 shows up as a "bluez...source" and "bluez...sink" if HFP is selected. RX and TX Codecs should be selected next; Opus and LCPM 2ch/1ch seem to work be with regards to network latency for me. In Radio Access, enter the IP address of your host server, along with the user/pass you entered on server setup.
On the server side, "Connect to radio" via the button. Once the display indicates sync, do same from the client PC. If all was configured properly you should get audio in the headset and the various buttons, sliders and whatnot allow control of the radio remotely. I'd try this operation in the same room so one can get a feel of how things work before trying it at a distance. Note you may have to play with the TX and RX Latency sliders (in the client Settings - Radio Access area) to minimize audio dropouts. Experiment with what works best for your specific LAN.
I configured my RC-28's setting as: Knob is VFO A, left button and LED2 is NB On/Off as a Toggle, right button and LED3 is NR On/Off (same), and the big button as PTT On/PTT Off (momentary) with LED1 as its indicator. You have to hold the button to transmit. Releasing it puts the rig back into RX.