[Elecraft] K3: CW decoder

[Brett Howard]

I don't own a K3 yet but from the research I've done (and I've done a
LOT) I think the K3 is where I'm going to go.  When i say a lot thats to
say that I've read at least 15 or 20 QST reviews and I've read 80%+ of
the manual for 8 or 9 rigs.  The K3 really shines!  

Now for the request.  Its something that I really wish I had on my K1.
I know a lot of you guys are pros at CW and crank that thing to the hilt
and let er rip but I'm just getting into the stuff.  I find that I like
to set the keyer speed at about 13 or so and send at farnsworth 5WPM
spacing (or so).  The problem is when calling CQ and having the keyer
play your CQ for you you can't leave it set at 13 or the guy responding
to you will be going way too fast.  So then I end up setting it down to
8 or 9 WPM.  The problem then is (most) people don't want to slow down
to there and secondly even to me the characters just sound plain WRONG
to me when sent that slow.  

I'd be tickled pink if there was a dual speed control.  Character speed
and character spacing speed.  I'd have to think about the best way to
make it flow in an elecraft fashion though.  

Here are a couple options that I can think of: (bare in mind I don't
have a k3 so I may be saying stupid things below)

- If the mic setting doesn't do anything in CW mode have that adjust the
char spacing when in CW mode and Mic Gain when in SSB (or other mic
using modes).  Maybe CMP could be used for the char spacing while in CW
mode but I think its more elecraft (read elegant) to have full control
of both CW "speeds" setup on one knob.

- Have a menu item for farnsworth sending.  You set it to 0 for normal
operation (as the rig does now) and set it to anything between 0 and the
current speed setting minus 1 to get farnsworth spacing.  

Well I think those are the best I can come up with with my understanding
of the radio.  Anyway this feature would really help us slower guys who
are looking to come up to the speed of you 25+ WPM wonders!  Thanks much
guys for hearing me out.  I'd be interested to see if anyone else shares
in this want/need even if its not able to be implemented.

~Brett (KC7OTG)