Hi all,
I wanted to share a small Windows utility I have been working on in case it helps anyone else using wfview with N3FJP Amateur Contact Log.
The project is called W3NTB Power Bridge:
One of the main reasons I built this was to avoid COM port sharing/splitting. I saw a few older discussions here about using N3FJP with wfview, virtual ports, VSPE, etc., and it seems like that approach can get messy pretty quickly. I wanted wfview to keep the direct radio connection, and have the logger talk through supported network interfaces instead of trying to split the radio’s serial port.
The basic setup is:
- wfview controls the radio
- N3FJP ACLog handles logging
- W3NTB Power Bridge sits between them
- ACLog talks to the bridge through the ACLog TCP API
- The bridge talks to wfview through wfview’s local Hamlib/rigctld server
So far it is working well with my IC-7300 setup.
What it currently does:
- Syncs frequency and mode between wfview and ACLog
- Lets ACLog DX cluster frequency changes tune wfview
- Updates ACLog from wfview/radio frequency changes
- Shows station status, mode, RF power, and transmit status
- Can launch wfview and ACLog locally
- Can launch/restart a shack-side wfview server over SSH
- Includes beta Shelly plug support for station power control
My personal use case is remote operation on a budget. I run wfview on the shack computer as the radio server, connected to the radio over USB/CI-V. On the remote computer I run wfview as the client, ACLog, and W3NTB Power Bridge. I use Tailscale for the private network path back to the shack. The app also works locally if everything is on the same Windows desktop.
This is not an official wfview or N3FJP project, just a small open-source bridge that solved a problem in my station. I’m sharing it here because wfview is the key piece that made this setup practical, and because it may help someone avoid the virtual COM port rabbit hole.
Installer releases are here:
Feedback, bug reports, and feature ideas are welcome. Best way to do so would be to open an issue on GitHub. If this belongs in a different category, no problem at all.
73,
Kevin
W3NTB