I'm capable of sending much faster than I can reliably copy.  So I find what
works best for me is I send slower to start off to try and get the other
person to match my speed.  I'm sending much slower than I can but I send
slower so that I can copy.  I find that 9 times out of 10 people answer me
at considerably higher speed than I'm sending.  Commonly I'll call at 10WPM
and get calls at 13 to 15 which is the difference between solid cpy and I'm
barely getting what your saying cpy.  But I usually muddle through.

I find that I'm happiest if I can send faster and talk the other OP into
QRSing below my sending speed.  Allows me to get out what I had to say and
also get a better print of what they are saying.  I find that it often
reduces stress on the faster guy and they talk to me longer too.

~Brett (KC7OTG)

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of dw
Sent: Friday, August 07, 2009 9:27 AM
To: Elecraft_List
Subject: [Elecraft] Off-Topic: CW sending vs. recieving speed

What's the general consensus?
Is it logical to assume that a person's CW sending speed approximates
their copy speed?

I can't help but assume this, and so when I call CQ and get a return
caller sending at half the speed which I called or sending extreme
farnsworth, I almost always lower my speed in order to be considerate.

Thanks
Duane
N1BBR
 
-- 
 [email protected]

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Reply via email to