www.dl2rum.de

QK4 is a new app for controlling a remote K4 over the Internet. Author is KF5O (formerly AI5QK).

When connected to a remote K4, QK4 listens on port 9299 on the local machine (127.0.0.1 typically) for connect requests from external programs like RUMlog. It connects to RUMlog but it appears that RUMlog doesn't poll Elecraft radios, perhaps relying on the AutoInfo feed. For various good reasons, QK4 doesn't implement AutoInfo so frequency on the RUMlog log page doesn't update when QK4 changes frequency. (Reset CAT #1 works for manual update.) I can work around this by telling RUMlog that it is talking to a Kenwood radio. Then it appears to poll QK4, updating frequency but not mode. It would be nice to update mode as well. It would be even nicer if this could be enabled when RUMlog knows it is talking to an Elecraft K4 simulator like QK4.

Why don't you just connect RUMlog with the K4 directly?

DL2RUM wrote: ↑Sun 24. May 2026, 03:16 Why don't you just connect RUMlog with the K4 directly?

Because I'm hundreds of km away from the K4, operating remotely across a TCP connection. RUMlog connects but does not seem to poll the K4. I think it relies on K4 AUTO INFO which only works on a serial port. I am only able to update frequency with Transceiver | Reset CAT #1, not by tuning the VFO.

I think it relies on K4 AUTO INFO which only works on a serial port.

All functions were tested over the network. Also the auto info command works as expected. Make sure other software isn't switching off AI.

Never mind. KF5O just updated QK4 to generate AUTO INFO so RUMlog can track the remote K4 via QK4. Mike is very responsive!