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 informing 
them about this problem.73 Ian IK4EWX



----Messaggio originale----
Da: [email protected]
Data: 19-giu-2016 18.37
A: <[email protected]>
Ogg: Re: [Elecraft] K3S losing swr-wattmeters indications on tx - please        
help

Yes, both my K3 and a K3s do this when I key them with my bugs or with my
straight key. Even my K2's will behave strangely, though not quite as bad as
the K3 and s. It's not a problem with the rig; it's just a contact bounce
issue, so you'll just need a debouncing circuit. Either an external keyer
(most of them have debouncing circuitry in them) or you can home-brew one.
There are a couple good circuits in the list archives.

A capacitor across the bug terminals will help, say a .1 uf, but beware that
it'll key the rig momentarily when you first plug it in as the cap charges.

73,
LS
W5QD



--
View this message in context: 
http://elecraft.365791.n2.nabble.com/K3S-losing-swr-wattmeters-indications-on-tx-please-help-tp7618984p7618995.html
Sent from the Elecraft mailing list archive at Nabble.com.
______________________________________________________________
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
Message delivered to [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
Message delivered to [email protected]

Reply via email to