[Elecraft] Remote Control Programs for the K2
Julian, G4ILO
[email protected]
Sun Jan 27 09:50:19 2002
In my opinion, rig control programs should just control the rig, logging
programs should concentrate on logging and data programs should just do
data. The rig control programs should have a standard API, which the other
programs would use to control the rig. This way, you could have one user
interface to control the radio, no matter what you wanted to do with it.
Logging and data program authors needn't worry about the quirks of
different CAT radios: all they would need to do is support the standard
control API and their software would work with all radios. With the present
situation you can only use one program at a time, since each one takes over
the serial port and wants to talk exclusively to the K2, and you have to
get used to a different UI for every darn mode.
As my idea isn't going to happen, I reckon your best bet is to go with
MixW. If people write MixW macros for the K2, perhaps they can post them
here for the benefit of those who find macro writing a bit difficult.
73,
--
Julian, G4ILO. (RSGB, ARRL, K2 #392)
Homepage: http://www.qsl.net/g4ilo
Jim Campbell <[email protected]> wrote:
I recently installed a KIO2 in my K2. Naturally, I began trying various
remote control programs to drive the K2. Each of the programs I have
tried has its strong points, but none of them does the whole job. K2
Remote does a fine job of controlling all aspects of the K2, but can't
do PSK31 for example. MixW does every mode imagineable, but makes you
write macros to control the K2. If I could somehow take the good
features of both programs, I would be much happier.