FW: [Elecraft] K2 BFO Parameter rewrite macro

[Dan Barker]

Wayne, from your encourgement for me to write this macro, I'm assuming you
don't plan on including a "touch all BFO parameters" function in any future
firmware.

So, I'll dive in.

The KIO2 does not support any sort of handshaking so we have two options.

 1) Send a short enough command such that buffer overruns are not possible,
or

 2) Implement handshaking in software.

Software handshaking is fairly easy. Send a bunch of commands followed by a
"K2;" and then wait for a "K2n" reply. Only when the KIO2 is through with
the list of commands will it echo the K2n response.

However, this method still begs the question, "How big is the KIO2 buffer?"
I'm thinking it's fairly short, as the keying buffer is pretty short. But I
need to know. If you can buffer 8K of commands, then my macro can just be
"Select-All|Copy this stuff in Notepad and Paste-to-host in Hyperterminal".
If you can't, then I need to know the buffer size.

If I send (the "KY <;" has already been sent):

ky 1 test paris one;
ky  2 test paris two;
ky  3 test paris three;
ky  4 test paris four;
ky  5 test paris five;
ky  6 test paris six;
ky  7 test paris seven;
ky  8 test paris eight;

the sending is perfect up to the "e" in "test" on the eighth line. That's
160 characters, I guess. If the CW Sending buffer is distinct from the
command buffer, then I may be looking for a different limit. I imagine
touching all the BFO parameters, remembering the current settings (AI and
K2) for restore after completion, checking if RTTY filters are desired,
etc., all imply an application. So, I'll dive in to that, limiting my
commands to 50 characters or so, until I hear otherwise. If I hear of a
different limit for the command buffer, then my macro can degenerate into
the "giant paste" I'd hoped.

Dan / WG4S / K2 #2456

Wayne sez (Jan 12, 2004):
<snip>
Let us know if you write an application for this.
</snip>