Hamish wrote:
> > The reason is, that a lot of CW ops use a computer to both send CW and
> > also log with it. The CW 'keyer' needs to know the call of the guy being
> > worked, in order to fire it back at him, and also the RST report you have
> > decided to give him (as typed into the RST-sent field).
>
> Hmm. I'm a bit surprised (even shocked) to know that these guys
> let the computer do most/all of the sending for them.
Using the computer to send is virtually standard practice for modern CW
contesters. The integration with computerized logging is just too
powerful to resist -- you type the call and the received report once,
and that's all you need to do. And, of course, the quality of the CW
sent is better than the mistakes that some of us (like me!) make.
Whether all this is sporting or not is another issue... I do virtually
all of my HF operating on CW and send (at home) by hand. But every
year when we go out for the US Field Day operation, I agonize over
whether to switch to computer logging and sending (there's also an
ergonomics issue -- moving hand from keyboard to paddles is
inconvenient and time consuming; sending by hand, I keep the pencil in
my left hand while sending with my right...).
>
> > 1. A CW keyer on the parallel port with programmable speed.
>
> Personally, I would prefer to generate the CW as audio tones injected
> as SSB.
This is probably not a good idea. Many (most?) rigs are only optimum
for CW receive when set to CW mode -- operating in SSB will lose a lot
of RX capability (narrow filters, fast AGC, and proper zero beat).
73,
John N8UR
[EMAIL PROTECTED]
--
John Ackermann N8UR
Dayton, Ohio, USA
[EMAIL PROTECTED] -- http://www.febo.com
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.3a
mQBtAzgI9hgAAAEDAMiMQDZTVVuVIS0AscJ0Wy63oK4+Q5xvtxbX/ZoG1qCOuYDI
Fph4/RqL9vVEItWBy6ISk+zbkATzPgy84nrI7+GBtld4F9DoHWARQXjC1I8cFZjY
TSe16ffqO/ba1ukLnQAFEbQlSm9obiBSLiBBY2tlcm1hbm4gTjhVUiA8anJhQGZl
Ym8uY29tPokAdQMFEDgI9hjqO/ba1ukLnQEBtYIC/AxJ2RqT0/9TqY8JGEkPx2sw
+W5Z6Tu4UI654t9diGdCcIEPjOG1qUvwH2Xop0Yj9QGoM4NnHIw6qUSN5VH7hHKA
bGnpuTxinuW/gKaI3bt2MC8QZZq0gy2de26907lE2A==
=UHWl
-----END PGP PUBLIC KEY BLOCK-----
