Hi Bob,
If you want to run CW using Roeland’s method, then you will need to run your own rigctl and connect it to the virtual serial port in wfview. This is because wfview does not have the CW command yet in our own rigctld. wfview’s built-in rigctld is designed for external programs like fldigi or WSJT-x to connect to and issue simple commands like “what frequency is this” and so on. But there are some commands, like CW, that we don’t have yet. You can use any serial port program to connect to the virtual serial port and issue commands directly to the radio, including your own copy of rigctl. Sorry for the confusion – the world we live in, so to speak.
I have no idea about the rigctl-wsjtx.exe programsyou mentioned, as I have not actually used that yet, but someone here can probably answer you. I am tempted to say “do not use them” since we don’t know what it does. Perhaps it is just a compiled version of rigctl distributed with wsjt-x for your convenience, I really do not know. But I do know that wsjt-x can connect to wfview’s own rigctld-compatible server, and that this is how many users do it.
Most any CW program designed to work with an Icom will work via wfview’s virtual serial port. Programs that use the audio to do CW decoding, like fldigi, can use wfview with a loopback audio device, which we detail in our manual.
We definitely welcome any contributions to wfview, and we have had contributions to the source code from several people already. Just like sharing schematics and design files, we can share source code and make something better via collaboration.
FLEX? Yaesu? Sure, I’m all for it! Send the radios
or at least send the code :)!
The GNU/GPL license stipulates most importantly, that any copy of wfview distributed has to include the source code, including derivative works. For example, if someone copies parts of the source code into their application, then their application must also be open source. They can charge for it, but they must provide the source code under the GNU/GPL license.
Some people don’t like the kind of “viral” nature of it, but what it does, is assure that the code stays open and available. And I think that’s important. Especially today. We have too many applications and technologies being distributed without the opportunity to learn and grow. Winlink, D-STAR, C4FM, etc.
It’s vital to ham radio that we roll with technology as it evolves (software and hardware) and, that we keep the ideas out in the open. The ARRL should embrace this. There’s so much they could do in this area.
Ok, well, there you have it, one of my soap boxes :-).
Take care,
–E
de W6EL