Yeah, that's kind of how I've always thought of it, a "user is responsible
for debouncing" type of thing.
Especially the Dah paddle and my Kent straight key, when bouncing, may not
be indistinguishable from a straight key going 100wpm as far as the rig is
concerned LOL.
So I never really thought o
Odd ... I operate almost exclusively CW at 20 - 40 WPM with both a K3
(#0056) and a K2/100 (#5665) and have never experienced the problem you
describe.
FWIW, the K3 has been heavily used in numerous contests by KE7X.
73
K0PP
On Jun 20, 2016 10:52 AM, "glcazz...@alice.it" wrote:
Lucien, many th
I have heard numbers like 90 and 100 wpm for operative QRQ for the K3, but
don't have time to go research where I heard that. I *know* it runs sweet
at 60 and 70 WPM. BTDT.
But I will caution that certain problems with key contact surfaces will
produce a signal impossible to debounce. These proble
I imagine it's because of the QRQ support that it doesn't have dedicated
debouncing circuitry for straight keys, but I'm not sure about that. The K2
does have some small caps across the key input, but it too still gives me
slight problems when I key it with my straight key. Though it's not as bad
a
Lucien, many thanks for your help. I am ashtonished. It is incredible that a
great rig as the K3S doesnt have the simpler debouncing circuit on the key
input, input obviously available for all mechanical kind of key, so with
potential bounces. This afternoon I have written to elecraft support in
5 matches
Mail list logo