[Elecraft] Feature Request: improved internal keyer and CW PTT behavior

[Chester Alderman]

First, I admit to not understanding the problem! I do run QSK and VOX during
contest and during regular QRQ QSO's. With my K3/Alpha 9500 setup, I can run
full QSK CW up to 100 wpm and I have no PTT delay issues? I do not run with
PTT asserted and therefore I do not witness the issues other contesters
have.. As for N1MM's "poorly designed internal K3 keyer logic", I certainly
have to disagree with that comment. During 'normal' contest I operate from
28 to 40 wpm, full QSK and would go nuts if there were any perturbations
with my K3's keying. 

A so called 'solution' to CW stuttering is to purchase and use the K1EL
keyer. The real problem is with Windows op system wherein the CPU is often
interrupted to do 'internal chores'; and when this happens, all I/O ports
are shut down, which causes the CW stutter. Simply turning off the Windows
generated sound, eliminates the stutter issue and the 'requirement' to
purchase the K1EL keyer.

73,
Tom - W4BQF



-----Original Message-----
From: Elecraft [mailto:elecraft-bounces at mailman.qth.net] On Behalf Of
donovanf at starpower.net
Sent: Tuesday, February 14, 2017 12:53 AM
To: Elecraft Reflector
Subject: [Elecraft] Feature Request: improved internal keyer and CW PTT
behavior

Okay, lets take Eric's lead and open an interesting thread directly related
to an excellent Elecraft product. 



For years many of us have suffered with the odd behavior of the K3 
in CW PTT mode. There are at least two inexplicble aspects of K3 
CW PTT behavior that have forced many of us to use external 
Winkeyers rather than the poorly designed internal K3 keyer logic 
when the K3 is in CW PTT mode. 


For CW contesters, its necessary to operate the K3 in PTT mode 
to avoid unwanted VOX delay. But for some strange reason the 
K3 always applies VOX delay after external PTT is unasserted. 
I can think of no logical reason why VOX delay should be applied 
at the end of the external PTT input when the K3 is PTT mode or 
any other mode. When PTT is unasserted, the K3 should always 
immediately return to receive mode, no exceptions. 


When using the internal K3 keyer when in PTT mode, for some 
inexplicable reason the K3 behaves like its in QSK mode. The 
only way to avoid this is to use VOX rather than PTT mode or 
to use a foot switch when in PTT mode. Both alternatives 
are unacceptable. 


The band aid solution many contesters use with excellent results 
is to avoid using the internal K3 keyer and to use an external 
K1EL Winkeyer that generates both a key output and a PTT 
signal generated according to well designed Winkeyer CW PTT 
logic. 


Why can't the K3 implement logic similar to the Winkeyer to 
generate the equivalent of "Winkeyer PTT" when using the K3 
internal keyer when the K3 is in PTT mode? 


73 
Frank 
W3LPL 
______________________________________________________________
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
Message delivered to aldermant at windstream.net