It’s been a while since I’ve run RUMLOG…. but I’ve been using WFView and WSJT-X together with no issues. I wasn’t keen on the logging abilities of WSJT, so I’ve been paper logging, which is fine, except for remembering the proper time difference between UTC and local… and proper date…

I’m still “stuck” using an Icom 7300. The 705 is great, but FT8 works better with a little more power (100W vs. 5W)

I started trying to get all three pieces of software to work together, at least for basic rig commands. After quite a bit of tinkering with settings, and looking at other websites, I did find a set of RIGCTL settings that allowed the system to function. With a little more work (and help from ), it all seems to be fairly seamless.

First, WFView needs to be set up as the primary rig interface and serial port controller. Radio Access is pretty self explanatory – in my case, I use an Icom 7800, Serial (USB), Auto-detect, and 115200 for a serial speed. I use networked connection for the 705 to cut down on noise.

Next,t he RigCtld server needs to be set up. I used to use 7300 for the TCP Server Port, but one of the other setup sites used this, so I tried it just to see what settings did what… and I left it at 4545.

Next, I got RumLog working with WFView to capture frequency and mode. This seems to be a sticking point for some folks – the primary work is on the TX1 tab. Note that this is using the direct TCP server port set up in the previous step.

Next, to get WSJT integration working with RumLog, there’s several settings on the UDP tab. These are the settings that (once UDP is set up in WSJT) will allow WSJT to write to the Rumlog database and log QSOs automatically.

Now, on to WSJT-X.

The radio tab is fairly easy – this sets the software to talk to the RigCtld server (not the TCP server), using HamLlib

To complete the logging features, go to the reporting tab, and set up the UDP server… this will connect to the UDP settings from Rumlog

One I got those all set up, everything just WORKED. WSJT-X connects (For audio) to the USB Audio Codec directly. for now, WFView is still looking at BlackHole audio, since that’s what the 705 uses for audio patching between software applications. No point in messing with what’s working for the moment!