[Elecraft] Contest cw speed and a ham since 1952

Sat Jun 19 15:53:18 EDT 2010

Peoples:
I operate from quite a few dx spots....I have been on the air steady since 1952,,,call me old fashioned,....call me crotchedy...BUT....I never , ever answer or qso with a high speed cw station that does not slow down to my speed.

Yes I do 35wpm, but I prever 20.....sorry, had to vent my spleen somewhere.

My, My, there are a lot of lids on the air today....but then most of them do not know what lid refers to.

Susan (Old lady of 76 years)

If you don't change direction you WILL arrive exactly where you're headed!! Susan Meckley, Skipper W7KFI-mm  AFA9SM                         USSV DHARMA 

--- On Sat, 6/19/10, Guy Olinger K2AV <olinger at bellsouth.net> wrote:

> From: Guy Olinger K2AV <olinger at bellsouth.net>
> Subject: Re: [Elecraft] K3 Beta Firmware Rev. 4.03: "CW+" mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM)
> To: "The Smiths" <notforchat at hotmail.com>
> Cc: "Elecraft Reflector" <elecraft at mailman.qth.net>
> Date: Saturday, June 19, 2010, 6:09 AM
> For speeds that people can send with
> a bug (usually) the regular CW
> seems to work quite fine. CW plus is primarily intended to
> support
> very fast speeds, often heard now with operators sending
> with
> keyboards and other electronic keying devices.
> 
> Debouncing a bug to prevent false starts when someone has
> poor
> contacts on one side is not one of the design goals for CW
> plus I've
> heard passed about, though the buffering of keying circuits
> used in
> most transmitters now has a small amount of debouncing
> effect which
> has likely been hiding the glitch. This would include the
> regular CW
> of the K3.
> 
> With CW plus, however, that small false start has to be
> taken as
> legitimate, because pausing a small amount to "make sure"
> that the
> operator really means it, would make high speed CW sound
> jerky.  CW
> plus was made to faithfully reproduce the keying at very
> high speeds,
> and has to take the blip seriously.
> 
> Cleaning and proper adjustment of bug contacts were always
> needed in
> the day, because the condition you are talking about would
> result in
> scratchy keying...which was never blamed on the
> transmitter, only on
> the op who was not keeping his bug "greased".  The
> need is greater now
> because noone is keying the +100V or more found on the old
> open
> cathode circuits any more, and bad bug contacts will easier
> bother a
> mere 12 volts on the key, and bother 5 volts even worse.
> 
> 73, Guy.
> 
> On Sat, Jun 19, 2010 at 11:11 AM, The Smiths <notforchat at hotmail.com>
> wrote:
> >
> > I've noticed this as well.  For me it's a "Tick"
> sound EVERY time I hit the Dah side of my bug. Nothing on
> the dit side, regardless of the speed or preasure.
> >
> > I thought at first it was the force that I was using..
> So I tried pushing the lever slowly and carefully against
> the Dah contact, and it didn't make the sound.. So then I
> tried lighting my touch on the dah side while I was sending,
> and sure enough it was still there.
> >
> > So, I switched from my Begali Intrepid to my Vibroplex
> Original, and then I found that the ticking sound was GONE
> all together!  Now I'm competely confused.  What does the
> one dah side have that the other bug's doesn't??? Gold
> Contacts? A bad ground connection? More surface contact
> area, a larger area? You tell me.
> >
> >
> >
> > I LOVE the new QSK (QRQ), but if I had to deal with
> that Tick sound on the dah contact, I would just not use it.
> Shame.
> >
> >
> >
> >
> >
> >> Date: Sat, 19 Jun 2010 05:37:18 -0700
> >> From: drewko1 at verizon.net
> >> To: elecraft at mailman.qth.net
> >> Subject: Re: [Elecraft] K3 Beta Firmware Rev.
> 4.03: "CW+" mode (Ultra-fastbreak-in; VOX-CW up to 100 WPM)
> >>
> >>
> >> Yes, I noticed this on my bug also. This happens
> almost entirely on
> >> characters that start with a 'dah'. I think this
> is because the index finger
> >> is off the paddle between characters and the
> initial attack is a little more
> >> forceful. Subsequent dahs in the same character
> sound fine, but that first
> >> one has a 'tick' (a spike by the sound of it). No
> problem at all with the
> >> dits.
> >>
> >> BTW, I don't think this is a matter of bug
> adjustment; you can get the same
> >> effect by tapping down on a straight key from a
> slight distance. So it is a
> >> matter of technique. I can avoid it on the bug by
> keeping my index finger
> >> resting against the paddle all the time and
> avoiding that first hard strike,
> >> but can't send as well that way; maybe with
> practice...
> >>
> >> 73,
> >> Drew
> >> AF2Z
> >
> >
> _________________________________________________________________
> > The New Busy is not the old busy. Search, chat and
> e-mail from your inbox.
> > http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3
> >
> ______________________________________________________________
> > Elecraft mailing list
> > Home: http://mailman.qth.net/mailman/listinfo/elecraft
> > Help: http://mailman.qth.net/mmfaq.htm
> > Post: mailto:Elecraft at mailman.qth.net
> >
> > 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:Elecraft at mailman.qth.net
> 
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> 