Adding CW Operation?

New user here. Delightful program, I’m running it on Windows 10 and a Mac laptop. Thank you for creating WfView!

I’m wondering if you plan to add CW operation to the program, or if someone has thoughts on how to accomplish it.

Thanks & 73,


Hi Warren,

Welcome to wfview

We have a number of plans for CW operation, most are fairly long-term though. A simple keyboard based TX will likely be first, but we are also looking at the possibility of straight key/paddle interfaces as well.

There are a number of timing issues with straight key/paddle operation though, which we have a few ideas how to fix.

Watch this space!

73 Phil M0VSE


the integration of Winkey would be fine!?

73 de Uwe, DL4AC

if the keyer is connected remotely to the rig, it would have the same timing issues Uwe.

Now I have to say that I don’t use a winkeyer so not sure.

Rigctl can key the rig remotely via wfview’s virtual serial port using the rig’s built-in keyer. For example, the following shell command uses the virtual serial port to send the CQ string to the rig and the rig’s built-in keyer takes care of the sending the whole thing, so you could have terrible network latency and still get perfect timing:

rigctl -m 3073 -r /home/pi/rig-pty1 -s 115200 b ‘CQ CQ DE VE3MAL’

(note that in my case,

  • it’s a 7300,

  • /home/pi/rig-pty1 is the virtual serial port,

  • my rig is set to have a baud rate of 115200)

Unfortunately, most loggers don’t support hamlib keying yet, but if you really needed remote keying via wfview, it can be done like this in a pinch while you wait for more features to be implemented. You could even have a keyer type interface in one line of bash:

while true; do read text; rigctl -m 3073 -r /home/pi/rig-pty1 -s 115200 b “$text”; done

I added a more fulsome ( though still extremely minimalist) implementation in clogger that includes speed control and the ability to stop the keyer, etc. (

Good luck! Sorry it’s a cludge of an answer, but it might get you started.

1 Like

Jason, thanks for the ideas. I wonder if anyone has tried your approach to interface N1MM+. That would be a great start.

73, Warren, KC9IL

Hi Phil,

I’ve been enjoying wfview, but this does seem to be the biggest gap. One way to get 80% of the way there (at least for certain use cases) with what I expect would be limited effort would be to add a set of ~8 user programmable buttons on the interface. These could be programmed to send an arbitrary CAT command to the rig; for CW, this would allow a user to take advantage of the rig’s internal memory keyer, or to send an arbitrary set of characters over CW. This would allow most of the control to be done through wfview directly, only jumping over to other avenues in unusual cases.

It would also be useful for users in other modes (e.g. internal voice keyer), as well as users who really want a function that’s further down your roadmap (e.g. NB or NR).

73, Scott KF3CP

Hi there

so far so good, CW CQ WW This weekend and I am stuck at location far away - familly issues - but i can listen in using IC7100 and all my big antennas. I would love to CW TX. So far - WinKey or more like remote VNC to a PC with a Winkey keyer + CW Keyboard was the only option, no delays , no jitter issues. It would be great for newer ICOMs to use their internal keyer if they support.

tnx for the hard work!
Jiri OK2IT

1 Like

Hi Jiri,

It’s definitely on the list. Icom does gives us a command we can use, so it’s just a matter of writing all the code to support it.

de W6EL