JT,
You are correct, not many applications support the K2 "virtual keying".
I do wish that would change, and perhaps it will now that Elecraft has
gotten more attention with the K3 (well, wishful thinking sometimes
produces results <G>).
I can only believe that it is not supported because the applications
attempt to support multiple transceivers with the same code - the K2 is
unique in this function (as far as I know), and the programmers would
have to branch off into routines that are specific for the K2 - that
means more code in their programs.
Perhaps one of the application authors could respond and provide his
reasons, but for the time being, it is prudent to use whatever
conversion hardware is necessary to activate the K2 key line.
73,
Don W3FPR
John Tobias Croteau wrote:
""Virtual" keying, using computer commands sent to the KIO2's serial
port: In this case, no
connection to the key or mic jacks is required for keying the K2. In
SSB mode, the computer sends the K2 "TX" and "RX" commands, which the
K2 responds to by turning PTT on and off internally. In CW mode, the
computer sends typed characters to the K2 using a "KY" command, and
the K2 converts the characters to dots and dashes internally. This
method of keying is supported by only a few remote control
applications, including RCP570 and Elecraft's K2REMOTE program. (For
details on the TX, RX, and KY commands, refer to the KIO2 Programmer's
Reference.)"
However, it doesn't look like many third party programs support it at
this time so I will most likely have to split off a line and use PTT
through the KEY jack like you suggest.
_______________________________________________
Elecraft mailing list
Post to: [email protected]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com
