Date   

Error 12v

rodger bryce
 

This morning while running my Elecraft K3 Ser No. 02377 at 32 watts I got the above error message. I was feeding an amplifier at the time, now power out will not go above 12/13 watts and the fan starts to run. The problematic pins known to be a cause of this error message were replaced about 2 years ago.

I have had this message a couple of times in the last 3 weeks .... but the message always disappeared after a few minutes and full out put returned, there was no burning smell or any amount of unusual heat. Before I start to take the rig apart I am looking for suggestions of the possible cause and remedy, the radio has the ATU and 2nd RX fitted....any help appreciated.

Tnx, Rodger/GM3JOB


Re: K3s & RTTY

Don Jones
 

Just this past week I successfully used NG7M's video to integrate MMTTY FSK to my K3S / ACOM 2000A station. I strongly recommend it. I really like dropping the received tones down to 915 Hz from the default setting. I did have to use a multiple of 4 for my sound card sample rate, another excellent tip in the video. 

Integrating to N1MM+ was a snitch.

I attribute my success to the NG7M YouTube video. It is found very quickly by searching keywords NG7M FSK on YouTube. 2 thumbs up.

Also, I did purchase a N6TV designed Y BOX too. I strongly endorse the use of that accessory port splitter box. It avoids the mess of multiple splitter cables. It makes it easy to access the FSK port yet does not interfere with other devices the require accessory port access (i.e. P3, SteppIR, or other devices needing band data). Bob N6TV gives outstanding tech support. 

I really like the AA5AU diode OR'ing trick for doing SO2V operation too. A really simple way of paralleling 2 serial comm ports for PTT & FSK functions. 

Bottom line, I would buy NG5M, N6TV, & AA5AU a cup of water at Vasalia... (watch the video and you will know what I'm talking about.)

73,
Don KO7I


Re: K3s & RTTY

Jim - WS6X
 

Re: K3s & RTTY
From: Max NG7M
Date: Wed, 16 Jan 2019 19:04:51 PST

 

<SNIP>

 

I chose the long winded route and haven't had to spend hours on the phone or remoted in to some guys station via TeamViewer to unwind all the crazy chaotic button clicking and jacked up sound card / n1mm settings / K3 config menu settings they usually apply because the concepts never quite sink in… 

…Plus, I never need to field several phone calls before a contest weekend with guys that seem to do a Steller job of  screwing up their FSK setup from contest to contest.  I point them to the video and say, now you can learn to do it on your own. :)

 

>>>> As someone who spent the best part of his career in customer / technical service, I admire the plucky soul who has the courage to publish a ham-related “how to” video, or to write software for the amateur radio market. Especially anything involving interfacing a computer to a rig! They must have the patience of Job!

73,

Jim – WS6X

 


Re: K3s & RTTY

Max NG7M
 

Good and Long Winded... I guess that's a compliment? :) I don't think I have seen someone that create something more detailed, that is for sure.  However, the detail pretty much leaves everything covered if you want to setup FSK with a serial port with a K3 and MMTTY.  One thing that is very handy in YouTube is jumping forward and back 10 seconds with the arrow keys.  You can also use the 'J' and 'L' keys to jump back and forward in YouTube.  10 second jumps really let you move quickly.  Using the keyboard shortcuts make a big difference if you need to repeat a section 100 times like some guys need, based on my experience.

I also made the video during the BARTG so I would have signals to demo live with in the video.  It's always a challenge when you put yourself out there in a video like this, short and sweet with very little info, or long and detailed... which I guess is long winded.  I chose the long winded route and haven't had to spend hours on the phone or remoted in to some guys station via TeamViewer to unwind all the crazy chaotic button clicking and jacked up sound card / n1mm settings / K3 config menu settings they usually apply because the concepts never quite sink in.  Never again now I have my video... ;)

Plus, I never need to field several phone calls before a contest weekend with guys that seem to do a Steller job of  screwing up their FSK setup from contest to contest.  I point them to the video and say, now you can learn to do it on your own. :)

Max NG7M


Re: K3s & RTTY

Jeff Jolie
 

Hi Lou,
If you haven't seen it yet, there is a very good, but long-winded, tutorial on Youtube by NG7M. He goes over everything in detail.  Here is the link:

73 Jeff NM1Y

On Wed, Jan 16, 2019 at 11:24 AM KE1F Lou <lmecseri@...> wrote:
I am running a K3s and trying to set up MMTTY using WIN 10 OS without
success. (I had it working once)

My device manager shows that Com 3, Com 9 and Com198 available.
Regardless which com port I use on MMTTY, I get an error message "Can't
open port X.

Port 3 is used by WinKey and Port 9 is used by K3s for CAT.

Is this a K3s (Config), RTTY or Windows issue?????

73 Lou KE1F

Computers will destroy us. :)





Re: K3s & RTTY

ve3ki
 

Wrong.

The WInkeyer's output is Morse code, and it is connected to the rig's CW key input. FSK RTTY requires keying using the Baudot code applied to the rig's FSK input on the ACC connector. Until such time as the Winkeyer is redesigned to produce Baudot FSK keying as well as (or instead of) CW keying, together with some way to connect the FSK keying output of the Winkeyer to the radio's FSK keying input, it cannot be used to do FSK RTTY. As it stands, neither COM3 (Winkeyer) nor COM9 (rig control) can be used for FSK keying - they are both dedicated to other incompatible uses.

If you have a third serial port with a keying circuit on it that is connected to the FSK keying input, use that. If you don't, use AFSK instead - no serial port is required for that.

73,
Rich VE3KI


On Wed, Jan 16, 2019 at 12:23 PM, rich wrote:
Assuming you are using FSK keying,  MMTTY should be set to Com3 since
WinKey is the device that is keying your rig.   Try that first.

Rich

On 1/16/2019 11:24 AM, KE1F Lou wrote:
I am running a K3s and trying to set up MMTTY using WIN 10 OS without
success. (I had it working once)

My device manager shows that Com 3, Com 9 and Com198 available.
Regardless which com port I use on MMTTY, I get an error message
"Can't open port X.

Port 3 is used by WinKey and Port 9 is used by K3s for CAT.

Is this a K3s (Config), RTTY or Windows issue?????

73 Lou KE1F

Computers will destroy us. :)





Re: K3s & RTTY

rich
 

Assuming you are using FSK keying,  MMTTY should be set to Com3 since WinKey is the device that is keying your rig.   Try that first.

Rich

On 1/16/2019 11:24 AM, KE1F Lou wrote:
I am running a K3s and trying to set up MMTTY using WIN 10 OS without success. (I had it working once)

My device manager shows that Com 3, Com 9 and Com198 available.
Regardless which com port I use on MMTTY, I get an error message "Can't open port X.

Port 3 is used by WinKey and Port 9 is used by K3s for CAT.

Is this a K3s (Config), RTTY or Windows issue?????

73 Lou KE1F

Computers will destroy us. :)




Re: K3s & RTTY

Ed Pflueger
 

Is it a K3 or K3S? I use AFSK with my K3S. TX is set at none, Misc. is set
at Sound, and Sound card is set at USB audio codec in the MMTTY program. In
the K3S use AFSK A for the data mode and VOX turned on and PTT is OFF-OFF in
CNFG. Works great here.

Ed.. AB4IQ

-----Original Message-----
From: Elecraft-K3@groups.io [mailto:Elecraft-K3@groups.io] On Behalf Of KE1F
Lou
Sent: Wednesday, January 16, 2019 10:24 AM
To: elecraft-k3@groups.io
Subject: [Elecraft-K3] K3s & RTTY

I am running a K3s and trying to set up MMTTY using WIN 10 OS without
success. (I had it working once)

My device manager shows that Com 3, Com 9 and Com198 available.
Regardless which com port I use on MMTTY, I get an error message "Can't open
port X.

Port 3 is used by WinKey and Port 9 is used by K3s for CAT.

Is this a K3s (Config), RTTY or Windows issue?????

73 Lou KE1F

Computers will destroy us. :)


WTB: XV432

Stephen Bloom
 

Hey all:

I'd like to get a hold of a XV432 transverter. Elecraft discontinued it
awhile back, and it looks like the international distributors are out of
stock as well.

Thanks/73
Steve KL7SB


K3s & RTTY

KE1F Lou
 

I am running a K3s and trying to set up MMTTY using WIN 10 OS without success. (I had it working once)

My device manager shows that Com 3, Com 9 and Com198 available.
Regardless which com port I use on MMTTY, I get an error message "Can't open port X.

Port 3 is used by WinKey and Port 9 is used by K3s for CAT.

Is this a K3s (Config), RTTY or Windows issue?????

73 Lou KE1F

Computers will destroy us. :)


Re: Remote antenna switching

Jeff Wheeler W7JW
 

Tnx to all who replied. I now have a better idea of I need to move forward. 
 
Jeff W7JW
 

From: Rick Tavan
Sent: Tuesday, January 15, 2019 2:19 PM
Subject: Re: [Elecraft-K3] Remote antenna switching
 
I have a Top Ten Devices Band Aide decoder picking up band data from the AUX/ACC connector (15 pin D-Sub) on my K3. I use the internal jumper pad in the Band Aide so that multiple bands select the same output for a multi-band antenna (SteppIR). The decoder outputs antenna selection lines to a WX0B Six Pak antenna switch. That's all I really need and what I use 95% of the time.
 
Although not currently in use, I can also connect a dummy load or seventh antenna to ANT2 on the KPA1500 and switch it manually via KPA1500 Remote.
 
And I have an external relay board that can re-steer certain bands to a rarely-used, alternate, multi-band antenna. I control the relays using a program on a server computer in the shack that I access using Chrome Remote Desktop. It doesn't have to be this complex and if you have all mono-banders, it could be a lot simpler!  ;-)
 
73,
 
/Rick N6XI
--

Rick Tavan
Truckee, CA


Re: Remote antenna switching

Rick Tavan
 

I have a Top Ten Devices Band Aide decoder picking up band data from the AUX/ACC connector (15 pin D-Sub) on my K3. I use the internal jumper pad in the Band Aide so that multiple bands select the same output for a multi-band antenna (SteppIR). The decoder outputs antenna selection lines to a WX0B Six Pak antenna switch. That's all I really need and what I use 95% of the time.

Although not currently in use, I can also connect a dummy load or seventh antenna to ANT2 on the KPA1500 and switch it manually via KPA1500 Remote. 

And I have an external relay board that can re-steer certain bands to a rarely-used, alternate, multi-band antenna. I control the relays using a program on a server computer in the shack that I access using Chrome Remote Desktop. It doesn't have to be this complex and if you have all mono-banders, it could be a lot simpler!  ;-)

73,

/Rick N6XI
--

Rick Tavan
Truckee, CA


K3S with P3, XV144, CW, FM, AM filters, TX monitor For Sale

joesands@...
 

See Ad in QTH.com.  All gear is in excellent condition and operated in a smoke free environment.

Joe W7UV


Re: Using a Bug key with the K3s

Bob McGraw - K4TAX
 

I can't see how mike gain has anything to do with using a bug on CW mode.    

In SSB operation the ALC and / or Speech Processor does have an attack time of a defined small number.  It can be that certain speech elements are fast enough such as the ALC or Speech processor does not react. In other words the rise time of the voice element is faster than the circuit can respond.    In these instances, the may be a small overshoot, causing the 70 watt indication while the ALC or Speech processor "gets its act together" so to speak.  I'm not aware of the actual attack times of the circuits.  But in my experience in pro audio and related equipment, I am speaking of milliseconds or less for attack times.  It is never instantaneous.   Perhaps observing the ALC level and the CMP levels, where as an excessive value of either or both may be a contributor to the issue.  

Regarding FT-8 and RTTY, those are slow signals and have very slow rise times.  Plus the ALC and SP systems should not be engaged or active for these modes.  Clearly Elecraft has very specific instructions on setting levels in these modes.

For what its worth........I tried a bug with my K3S and did not experience satisfactory results.  The dit bounce of the contacts was unacceptable.   Older radios provided debounce circuits and waveform shaping in the analog world.   Thus If one uses an external keyer, as some have stated, that circuit does debounce the dit contact.   To wit, I did look at the keying of my bug in a test configuration by applying a small bias across the contacts and looking at the HIGH / LOW signal transition on a scope.  I was appalled at the garbage coming off of the contacts.  Thus the bug went back in its case and on the shelf.  The Iambic paddle and internal keyer are top drawer performance in my findings.

73
Bob, K4TAX


Re: Using a Bug key with the K3s

Al N1AL
 

For the P3 problem you might try changing the setting of "TX SensEn" in the TX Monitor menu.  This changes the method by which the P3 switches between transmit and receive mode: either by RS-232 command from the K3 or by sensing the RF signal.  Normally this should be set to the default disabled mode (i.e. RS-232 command mode enabled) when the P3 is used with a K3 or K3S.

If that doesn't work you could try adjusting the value of the "TX hang" parameter.  That sets the transmit hang time in ms.

Alan N1AL

On 1/14/19 5:50 AM, wb6bee wrote:
I have had three instances of unexplained events, using a Bug key with the K3s.   I am 100 % cw and only use a bug.   My speed is about 26-27 wpm on the key.

1.  Event one:   I added the TXMON to the P3 to see if I could use it for evaluating keying, hoping it would show things like scratchy dots, etc.   It didn't show much at all, actually.   What was odd was the with some regularity, but no consistency, the display would go from the keying envelope to a line of static, similar looking to band noise on a spectrum analyzer.   A friend of mine, also using a Bug with the TXMON, was experiencing a similar situation.   I reported it to Elecraft Tech. They sent me, one component at a time, a new TXMON.   Nothing changed, the unit continued to have the erratic display.   Being somewhat useless, I put the TXMON in the box of unused parts.   Elecraft tech never followed up with the issue, probably not that many bug users with the TXMON.

2. Event Two:  Noted in this relfector some weeks ago.   Minor frequency shifts ( a few hertz) while keying with a bug.

3. Event Three:   I have a new KPA 1500.   Twice now, when in a long transmission, the amp will kick out.   No apparent reason, but my keying in the CW monitor would sound like something was wrong with the bug, loose weight or something.   Then, the amp would be in a fault condition.   In both cases, the fault log would show an overdrive condition.  My normal drive for the KPA from the K3s is about 30 watts or so (depending).   The default log showed drive at over 65 watts.   The first time it happened, I thought perhaps I hit something on the front of the K3s.   The second time, no such possibility (probably  not the first time either).   The first time was 160 meters.  The second time was 80 meters.   A common denominator is the 68 ft vertical antenna used for both bands.

These could all be related, or they could not.   Elecraft tech indicated they were going to try to use a bug to replicate the last event.   It is so irregular that I don't that would work.  However, K3s are so popular, maybe other owners have had issues with using a bug with the K3s

Don
WB6BEE


Re: Using a Bug key with the K3s

Michael Kopec
 

Hello again Don.  What I forgot to mention is:  I use QSK.  The weird stuff only happened in QSK and I did not experience it in semi auto delayed break. de Mike K8NS

On Monday, January 14, 2019, 8:50:12 AM EST, wb6bee <wb6bee@...> wrote:


I have had three instances of unexplained events, using a Bug key with the K3s.   I am 100 % cw and only use a bug.   My speed is about 26-27 wpm on the key.   

1.  Event one:   I added the TXMON to the P3 to see if I could use it for evaluating keying, hoping it would show things like scratchy dots, etc.   It didn't show much at all, actually.   What was odd was the with some regularity, but no consistency, the display would go from the keying envelope to a line of static, similar looking to band noise on a spectrum analyzer.   A friend of mine, also using a Bug with the TXMON, was experiencing a similar situation.   I reported it to Elecraft Tech. They sent me, one component at a time, a new TXMON.   Nothing changed, the unit continued to have the erratic display.   Being somewhat useless, I put the TXMON in the box of unused parts.   Elecraft tech never followed up with the issue, probably not that many bug users with the TXMON.

2. Event Two:  Noted in this relfector some weeks ago.   Minor frequency shifts ( a few hertz) while keying with a bug.   

3. Event Three:   I have a new KPA 1500.   Twice now, when in a long transmission, the amp will kick out.   No apparent reason, but my keying in the CW monitor would sound like something was wrong with the bug, loose weight or something.   Then, the amp would be in a fault condition.   In both cases, the fault log would show an overdrive condition.  My normal drive for the KPA from the K3s is about 30 watts or so (depending).   The default log showed drive at over 65 watts.   The first time it happened, I thought perhaps I hit something on the front of the K3s.   The second time, no such possibility (probably  not the first time either).   The first time was 160 meters.  The second time was 80 meters.   A common denominator is the 68 ft vertical antenna used for both bands.  

These could all be related, or they could not.   Elecraft tech indicated they were going to try to use a bug to replicate the last event.   It is so irregular that I don't that would work.     However, K3s are so popular, maybe other owners have had issues with using a bug with the K3s

Don
WB6BEE


Re: Using a Bug key with the K3s

harry latterman <harrylatterman@...>
 

I am just guessing, so take it for whatever it is worth.  One problem with high speed digital is key bounce. It is sometimes so fast that it is a pain to catch and fix. You are using a system that depends on bouncing and it is possible that the contacts are adding very small and fast extras thus giving the radio and amp fits. As I said, I could be wrong and this is just a guess, but one thing about working with control systems for almost 40 yrs, is you see same damn strange things that don't always make sense until your look really close to things that are not obvious

Harry  K7ZOV


On Monday, January 14, 2019, 11:20:14 AM MST, Michael Kopec via Groups.Io <michaelkopec1@...> wrote:


Hello Don.  I have a K3s, P3, KPA500 combo and also use bugs,  I have experienced some strange things, as u did.  My fix was to insert either my bug descratcher (Jackson Harbor Press) or my old MFJ Econo keyer set to semi auto position between the bug(s) and the K3s.  No more strange stuff happening anymore.  Maybe not a real fix or explanation but works for me. GL de Mike K8NS

On Monday, January 14, 2019, 8:50:12 AM EST, wb6bee <wb6bee@...> wrote:


I have had three instances of unexplained events, using a Bug key with the K3s.   I am 100 % cw and only use a bug.   My speed is about 26-27 wpm on the key.   

1.  Event one:   I added the TXMON to the P3 to see if I could use it for evaluating keying, hoping it would show things like scratchy dots, etc.   It didn't show much at all, actually.   What was odd was the with some regularity, but no consistency, the display would go from the keying envelope to a line of static, similar looking to band noise on a spectrum analyzer.   A friend of mine, also using a Bug with the TXMON, was experiencing a similar situation.   I reported it to Elecraft Tech. They sent me, one component at a time, a new TXMON.   Nothing changed, the unit continued to have the erratic display.   Being somewhat useless, I put the TXMON in the box of unused parts.   Elecraft tech never followed up with the issue, probably not that many bug users with the TXMON.

2. Event Two:  Noted in this relfector some weeks ago.   Minor frequency shifts ( a few hertz) while keying with a bug.   

3. Event Three:   I have a new KPA 1500.   Twice now, when in a long transmission, the amp will kick out.   No apparent reason, but my keying in the CW monitor would sound like something was wrong with the bug, loose weight or something.   Then, the amp would be in a fault condition.   In both cases, the fault log would show an overdrive condition.  My normal drive for the KPA from the K3s is about 30 watts or so (depending).   The default log showed drive at over 65 watts.   The first time it happened, I thought perhaps I hit something on the front of the K3s.   The second time, no such possibility (probably  not the first time either).   The first time was 160 meters.  The second time was 80 meters.   A common denominator is the 68 ft vertical antenna used for both bands.  

These could all be related, or they could not.   Elecraft tech indicated they were going to try to use a bug to replicate the last event.   It is so irregular that I don't that would work.     However, K3s are so popular, maybe other owners have had issues with using a bug with the K3s

Don
WB6BEE


I: [Elecraft-K3] Using a Bug key with the K3s

IK4EWX
 





Don, the K3 seem to not like a bug.
With my K3S i use always a bug (a Vibroplex Presentation or a Begali Intrepid).
In the past, when keying with the bug, the K3 displey become blank and sometime appeared on the K3S display, diagnostic  that disappeared when I used my paddle with the internal keyer. 
Even with HI CURR the transceiver transmitted well. 
With a firmware upgrade this problem was solved and I hadnt this strange problem, us since when last month I installed the last firmware 5.66.
Now, only on 20m it seem to me, when transmitting with 100w HI CURR appear and the transceiver reduce the power to 85 watts.
I signaled it to Elecraft, at first they thought it was a power supply low voltage on transmission, but when I said that i see the problem only on 20m, with 1.5 SWR, that it disappear when using ATU, they said me to reinstall 5.64 firmware and try again to see if there is the problem.
In the past I thought that K3S (and K3 as it seem) doesnt like the bug little bounces (or scratch dots...), on the keying input.

I send you below my exchange with Elecraft support  in  2016 that can evidence better the past problems. I hope it help you.
For the actual problem of HI CURR diagnostic on 20m, I am thinking to reinstall the 5.64 firmware version. With it I havent problems even without ATU inserted.
What is your firmware version? do you have 5.66?

73,

Ian IK4EWX

Da: Gian Luca Cazzola <glcazzola@...>
Oggetto: Re: IK4EWX: K3S losing swr-watt meters indications on tx - please help
Data: 29 giugno 2016 00:05:04 CEST
A: k3support@...
Cc: Carlo Bianconi <carlobianconi@...>

Sorry Dave, I have seen only today that your elecraft server haven’t received my reply.
So I repeat here.
-MY K3S HAVE SERIAL NUMBER 10715
-I SEE THE PROBLEM AT ALL POWER LEVELS, REDUCING AT 80 -60-40W DOESNT SOLVE. I AM NOT SURE ABOUT 20 W.
WITH THE ATU INSERTED IT HAPPEN LESS FREQUENTLY.
- THERE ARENT DIFFERENCEs IN WATTS OR SWR REaD ON K3S OR MY BIRD 43.
BUT WHEN THE SWR AND RF INDICATIONS ON K3S DISPLAY GONE BLANK, WHEN I MAKE  WITH  A LITTLE TUNE WITH THE BUG  DASH CONTACTS, OR  
EVEN SENDING NORMAL MESSAGES, DOTS AND DASHES KEYING WITH MY BUG, THE POWER ON THE BIRD 43  READ NORMAL WATTS, THOSE  CHOICED ON THE K3S
(EXAMPLE WITH POWER 90W CHOICED WITH THE K3S POT, AND KEYING WITH THE BUG, THE SWR AND RF DISPLAY GO BLANK - I READ THE SWR AND RF LETTERS 
BUT NO PIXELS OVER THEM - BUT ON THE BIRD 43 I SEE THE NORMAL 90 W OUTPUT).
I HAVENT OPTED THE QRQ NEW COMMAND ON THE CONFIG - SO IT ISN’T THE PROBLEM, WITH MY BUG ADJUSTED AT 18-25WPM
I have understood from your mail that the key input  is well filtered and  also debounced, but I have this problem, that also other hams on the K3 forum say to have.
You have read them.
Can you make something?
Mi friend Carlo Bianconi say that the rig have no electronic problems.
So do you know what can be the problem? Firmware?
Thanks es 73
Ian IK4EWX


Il giorno 20 giu 2016, alle ore 20:36, David Shoaf < k3support@...> ha scritto:

Hi Ian,

Thanks for the contact.  To your questions, we do not believe that adding additional components will affect the problem.

As shown on the K3S schematic, there are RF chokes and capacitors bypassing all the inputs on the K3S so additional ones outside the K3S would not be adding anything.

<lncmegamcpmiohfj.png>

We are also CC'ing our Authorized Warranty Repair Center, who may also be able to help.  

Additional questions:

- What is the serial number of your K3S?

- Do you see the problem at lower power levels (20, 40, 60 watts)?  Does it do the same thing on the dummy load?

- When you see the RF on the Bird 43, what do you see on the K3S display for RF and SWR?  Do they agree or not?

Cheers,

David

---------------------------------------
David Shoaf/KG6IRW
Elecraft International Distributor and Customer Support
831-763-4211 x121
---------------------------------------
On 6/20/2016 8:55 AM, glcazzola@... wrote: 


Yesterday I wrote on Elecraft K3 email list:


I own a great K3S from a pair of months. It work great, dx, qsos, contest (just worked CQWPX, 1200 qsos).  
Just after bought it, sometime on cw transmission  the swr-rf indications, the moving black dots, gone all blanked, all on the swr and on RF indications.  
I thought about rfi problems, but it happened even with dummy load. And with no swr on antenna.  
With atu inserted is seemed more rarely happen.  
This morning I have this problem happen at least on 14-18-21-24-28mhz, keying the rig with my bug, only with long dash and not with dots string.  
It is a rainy cloudy day, but I think that doesnt matter :)  
When using the paddle with internal keyer I havent the problem.  
It seem to happen only when keying is at least 2-3 seconds long.  
When it happen, with the two measurements blanked, the rig really continue to transmit - I see regular power on my external Bird 43 wattmeter.  
Somebody had this problem and know how to solve it?  
Many thanks  
Ian IK4EWX 

I received this reply from Lucien W5QD:

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 

I can say only that I am astonhished. 
It seem impossible that  rig of the K3S quality and price have this incredible ridicoulous problem.
Is it true and should I make a home made modification of the kind suggested?
Thanks

Gian Luca Cazzola - IK4EWX



----Messaggio originale----
Da: wb6bee@...
Data: 14-gen-2019 14.50
A: <Elecraft-K3@groups.io>
Ogg: [Elecraft-K3] Using a Bug key with the K3s

I have had three instances of unexplained events, using a Bug key with the K3s.   I am 100 % cw and only use a bug.   My speed is about 26-27 wpm on the key.   

1.  Event one:   I added the TXMON to the P3 to see if I could use it for evaluating keying, hoping it would show things like scratchy dots, etc.   It didn't show much at all, actually.   What was odd was the with some regularity, but no consistency, the display would go from the keying envelope to a line of static, similar looking to band noise on a spectrum analyzer.   A friend of mine, also using a Bug with the TXMON, was experiencing a similar situation.   I reported it to Elecraft Tech. They sent me, one component at a time, a new TXMON.   Nothing changed, the unit continued to have the erratic display.   Being somewhat useless, I put the TXMON in the box of unused parts.   Elecraft tech never followed up with the issue, probably not that many bug users with the TXMON.

2. Event Two:  Noted in this relfector some weeks ago.   Minor frequency shifts ( a few hertz) while keying with a bug.   

3. Event Three:   I have a new KPA 1500.   Twice now, when in a long transmission, the amp will kick out.   No apparent reason, but my keying in the CW monitor would sound like something was wrong with the bug, loose weight or something.   Then, the amp would be in a fault condition.   In both cases, the fault log would show an overdrive condition.  My normal drive for the KPA from the K3s is about 30 watts or so (depending).   The default log showed drive at over 65 watts.   The first time it happened, I thought perhaps I hit something on the front of the K3s.   The second time, no such possibility (probably  not the first time either).   The first time was 160 meters.  The second time was 80 meters.   A common denominator is the 68 ft vertical antenna used for both bands.  

These could all be related, or they could not.   Elecraft tech indicated they were going to try to use a bug to replicate the last event.   It is so irregular that I don't that would work.     However, K3s are so popular, maybe other owners have had issues with using a bug with the K3s

Don
WB6BEE




Re: Using a Bug key with the K3s

Michael Kopec
 

Hello Don.  I have a K3s, P3, KPA500 combo and also use bugs,  I have experienced some strange things, as u did.  My fix was to insert either my bug descratcher (Jackson Harbor Press) or my old MFJ Econo keyer set to semi auto position between the bug(s) and the K3s.  No more strange stuff happening anymore.  Maybe not a real fix or explanation but works for me. GL de Mike K8NS

On Monday, January 14, 2019, 8:50:12 AM EST, wb6bee <wb6bee@...> wrote:


I have had three instances of unexplained events, using a Bug key with the K3s.   I am 100 % cw and only use a bug.   My speed is about 26-27 wpm on the key.   

1.  Event one:   I added the TXMON to the P3 to see if I could use it for evaluating keying, hoping it would show things like scratchy dots, etc.   It didn't show much at all, actually.   What was odd was the with some regularity, but no consistency, the display would go from the keying envelope to a line of static, similar looking to band noise on a spectrum analyzer.   A friend of mine, also using a Bug with the TXMON, was experiencing a similar situation.   I reported it to Elecraft Tech. They sent me, one component at a time, a new TXMON.   Nothing changed, the unit continued to have the erratic display.   Being somewhat useless, I put the TXMON in the box of unused parts.   Elecraft tech never followed up with the issue, probably not that many bug users with the TXMON.

2. Event Two:  Noted in this relfector some weeks ago.   Minor frequency shifts ( a few hertz) while keying with a bug.   

3. Event Three:   I have a new KPA 1500.   Twice now, when in a long transmission, the amp will kick out.   No apparent reason, but my keying in the CW monitor would sound like something was wrong with the bug, loose weight or something.   Then, the amp would be in a fault condition.   In both cases, the fault log would show an overdrive condition.  My normal drive for the KPA from the K3s is about 30 watts or so (depending).   The default log showed drive at over 65 watts.   The first time it happened, I thought perhaps I hit something on the front of the K3s.   The second time, no such possibility (probably  not the first time either).   The first time was 160 meters.  The second time was 80 meters.   A common denominator is the 68 ft vertical antenna used for both bands.  

These could all be related, or they could not.   Elecraft tech indicated they were going to try to use a bug to replicate the last event.   It is so irregular that I don't that would work.     However, K3s are so popular, maybe other owners have had issues with using a bug with the K3s

Don
WB6BEE


Re: Using a Bug key with the K3s

john ni0k
 

Bob,

I have a peak reading meter on the output of my K3, with the output set at 60 watts. I will see some peaks at 70. Some people think it has to do with how hard you drive the mic gain. I haven't really looked at it on CW. It doesn't do it on FT8 or RTTY. And yes, I've done the power output calibration.

-John NI0K

Bob McGraw - K4TAX wrote on 1/14/2019 10:05 AM:

I would check for warm PL-259 connectors.  Make sure to snug them with 4" Channel lock pliers.  Finger tight is not good enough.  And any PL-259 which is warm along with the coax jumper is suspect.  Follow this all the way to the vertical.   I use a $29 laser IR thermometer purchased from Harbor Freight to make such measurements.  

Item 3....seems that a bit of RF is getting into the system somewhere.  Maybe due to SWR increase.  Again check all connectors and connections in the RF and ground system path. 

I have seen some slight overshoot with my K3S when driving my KPA500 with 20 to 22 watts.  In watching the PWR LED's on the KPA500, it indicates things run along at 400 watts and then an occasional 550 to 600 watt LED flash.  Haven't been able to exactly nail down why.   I'm using an Iambic paddle and the internal K3S keyer running 15 to 20 WPM.  I've tried both configurations, ALC from the amp being active to my  K3S and ALC from the amp not active to my K3S.   Still no conclusion. 

73
Bob, K4TAX