wfview provides a number of methods to allow other programs to share control of the connected radio. This is useful, for example, if you are running a logging program, or a digital mode program such as fldigi or WSJT-X. In principle, one needs to share the control CI-V bus, and for some programs, the audio.
First, if you need to route the audio, visit the audio page.
Each supported platform has a different means of sharing control, plus there are methods in development:
|Windows||Virtual serial loop-back|
Generally speaking, if your application supports Hamlib’s rigctl connection mechanism over TCP/IP, you should try that method first. Here is the page on wfview’s rigctld-compatible server.
Again, do not use the Virtual Serial Port if your program supports rigctld (most hamlib programs do!). The virtual serial port is provided as a catch-all for any program which does not have a more modern method available. The rigctld method is superior to the virtual serial port as it supports multiple simultaneous clients, radio model abstraction, and the data are shared with wfview internally in a much smarter way. Click here to read about how to turn on the rigctld server.
Virtual Serial Ports
If you wish to connect other software such as digital mode interfaces or logging programs to wfview, this can be accomplished by creating a serial port pair. There are a number of Windows programs that can achieve this, here are a small selection:
- Eterlogic VSPE http://www.eterlogic.com/Products.VSPE.html
- Eltima Virtual Serial Port Driver https://www.eltima.com/products/vspdxp/
- com0com This is a FOSS driver but a Windows signed binary can be downloaded from https://pete.akeo.ie/2011/07/com0com-signed-drivers.html
Each solution operates in (broadly) the same way, you create a “pair” of virtual serial ports which are interconnected in software so any data sent to one port, automatically appears at the other. wfview is therefore configured with one “end” of the virtual serial port pair in the “Virtual Serial Port” combobox within the settings page. Your digital mode software/logging software is configured with the other “end” of the pair. Your software can then communicate with the rig as if it was directly connected.
On Linux and macOS, wfview provides a pseudo-terminal device out of the box, which may be used as a normal serial port by other applications. Previous versions created the device at
/tmp/rig but newer releases of wfview allow the user to specify the device under the Settings tab, using the Virtual Serial Port combo menu:
Users can either select one of the pre-defined names, or type within the box to define a custom name (for example, /home/user/ic-7300). Dpn’t forget to press Save Settings after changing this box. To use the pseudo-terminal in a “client” program (such as fldigi, Ham Radio Deluxe, etc), you will need to either enter the device into the settings for the program, or, for programs that don’t allow free-form entry, close the program and edit the program’s settings files, manually specifying the same pseudo-terminal port name.
One example for flrig is included here in the repository. We welcome users to submit directions and/or files for popular ham radio software.
This is by no means an exhaustive list, but it shows which software we have successfully tested the virtual serial port/pty system with.
|WSJT-X||2.3.1||Windows, Mac, Linux||YES||Hamlib|
|Minos||2.4.1||MacOS, Windows||PARTIAL||Hamlib||Not Linux/MacOS|
|fldigi and flrig||Current||Linux||YES||Hamlib (preferred) and Pseudo-Term|
|MacLoggerDX||6.35b5||MacOS||YES||Pseudo-Term||Requires com.dogparksoftware.MacLoggerDX dp_virtual_serial_port configuration option|