[Elecraft] Function Keyboard Revisited

[Don Wilhelm]

John,

If your intent is to have the keyboard function through some 
application, then the feasibility of your solution depends on the 
capability of the application, and that may have nothing to do with the 
K3 capability.

The K3 has many capabilities available through applications that connect 
to it.  Almost any function of the K3 front panel can be accomplished in 
one way or another through programming (see the K3 Programmer's Reference).

To use ASCII codes from the keyboard directly would require significant 
changes to the K3 firmware to recognize those ASCII characters.  I do 
not think that is going to happen.
Refer to the K3 Programmers Reference to see what can be accomplished 
and the data stream that is required to produce the desired results.

In other words, the functions are available to do most everything that 
can be done from the front panel, but it takes a bit of processing to 
send the correct commands to the K3.

73,
Don W3FPR

On 5/1/2014 8:33 PM, John Lawrence via Elecraft wrote:
> Thanks for all the ideas
>
>
> First, I gather there is some confusion as to my application intent. My inquiry
> was to add a stand alone device to allow the function key ascii codes to
> come in via an additional keyboard on a computer.  And, it was to work with the computer logging programs directly must like the standard computer keyboard but be more user friendly with the function key macros by placing it off to the side of the main board.  Back in the early days of computer logging with CT on DOS there were keyboards with the function keys in a cluster off to the side thus avoiding the need to reach up beyond normal touch keyboard range to access function keys and in some cases also press Fn to reach F7 through F12.  By having a programmable cluster with 12 keys set as ascii keys for F1 thru F12, it would be easier to work with them at high run rates.  That's all.
>
>
> I haven't had time to investigate the alternatives offered to me but I will.  When I come up with the
> best answer it will be presented on here.  Again a 12 key cluster with USB to run with the logging program is the goal...I did not intend to interface directly with the K3.
>