Den 25.11.2019 kl. 09.18 skrev Nate Bargmann:
My intention in this was only ,as a casual contester, to create a easy
way to do CW on my rig using a logprogram.
* On 2019 21 Nov 05:32 -0600, Christian Treldal wrote:
All modern rigs have keying via hamlib.
I would caution, that is possible with varying degrees of support and
On the N1MM+ mailing list there is this recent thread that asks about a
warning when CAT keying is used:
Rich, VE3KI, weighs in later with:
where he states:
Which rig? The KY command works differently in Elecraft vs.
Kenwood vs. Yaesu. The examples that have been posted in various
places were for Elecraft radios. IIRC, the KY command for
Kenwood radios requires a fixed-length argument (padded with
blanks), which makes it essentially impossible to use
substitution macros. Also as I recall, the Yaesu KY command does
not send text, it selects one of the radio's own CW memories and
I've not seen the code, of course, but I presume that N1MM+ is handling
all of the rig control stuff internally. For Tlf and other programs
using Hamlib, the rig capabilities would be queried and if
rig_send_morse() is supported, it can be used, however, things like the
speed up/down characters in the keying macro would need to be handled by
the calling program and speed changes sent to the rig interspersed with
the message text. I can see this becoming very clunky very quickly!
Any given Hamlib backend will probably be coded so as to perform needed
work-arounds as best as possible. Again, this is very rig specific and
even Hamlib likely cannot hide certain differences.
I only have access to a K3 these days. I've not seen much mention of
anyone using the Hamlib send_morse function for any serious CW keying.
If I could offer a wishlist item to the manufacturers, it would be for
those radios incorporating a USB connector for rig control and sound
card IO that a second virtual serial port be available to expose a K1EL
It don't need to be the perfect solution, and if there are some timing
issues, who cares in a contest anyway. I have a K1EL keyer myself; but
then I have to bring another gizmo almost as big as my KX3 when I go to
DU-land. That doesn't make sense to me, when I already has a keyer in
Ervin and I will continue to work on our rigkeyer daemon who listens on
a port, parses it and sends it to 4532 for handeling by rigctld.
Med venlig hilsen
"Remember Darwin; building a better mousetrap merely results in smarter mice."