+++++++++++++++++++++++++++++++++++++++ Date: Mon, 12 Mar 2001 15:56:43 -0800 From: Eric Swartz WA6HHQ - Elecraft Subject: Re: [Elecraft] K2 Keyer Bug? Hi Ron, If your straight key contacts are oxidized or dirty, they might be creating excessive contact 'bounce' on closure. This rapid set of pulses might confuse the auto detect feature. 73, Eric WA6HHQ Ron D'Eau Claire wrote: > If I connect my manual key to the K2 with > both the dot and dash lines shorted together (with or without diodes) and > leave the K2 in iambic mode, I will get false strings of iambic characters > at times. That is, even though the dot and dash lines are both being tied to > ground simultaneously, the K2 will occasionally read it as an iambic input. +++++++++++++++++++++++++++++++++++++++++++++ Date: Mon, 12 Mar 2001 18:42:15 -0800 From: "Ron D'Eau Claire" Subject: RE: [Elecraft] K2 Keyer Bug? Eric wrote: "If your straight key contacts are oxidized or dirty, they might be creating excessive contact 'bounce' on closure." A-yup. That did it. No dirty key contacts allowed . Ron AC7AC K2 # 1289 +++++++++++++++++++++++++++++++++++++++++ Date: Sat, 7 Apr 2001 15:15:21 -0700 From: "Robert Marlan" Subject: Re: [Elecraft] K1 keyer problem I had the same problem only with the dash paddle... M became N.... I checked everything and all was ok. The paddle was the same as yours... The problem was solved simply by cleaning the contacts of the paddle. I hope it works for you. Please let us know. My guess is that the firmware is not debouncing the contacts quite as well as other keyers... Good Luck Robert Marlan KA6NOC/7 rsm at otology.com - ----- Original Message ----- From: "Vron - Charter" To: Sent: Saturday, April 07, 2001 11:10 AM Subject: [Elecraft] K1 keyer problem > Hi, Group. > I recently installed the KNB1, the KAT1, and the Firmware upgrage (Rev 109). > > I am frustrated because I am often embarassed. > Infrequently, the DAH paddle adds an leading DIT (T becomes A, M becomes W). > The frequency of the problem seems to be inversely related to operating time > (the longer I operate, the less it seems to happen). > > It happens at least once per QSO, but I often don't > have more that 1 QSO per operating session. > > I am using a Kent paddle with Iambic mode A, Keying Device: PDr, 10-12 WPM. > > I have searched the Elecraft web page - no mention of this problem. > > Has anyone else had this problem? > Is there a fix other than trying another firmware chip? > > THANK YOU!!! > > WD0EFQ > Vron Jones +++++++++++++++++++++++++++++++++++++++++++ Date: Fri, 04 May 2001 01:13:49 -0500 From: Tom Hammond =?iso-8859-1?Q?N=D8SS?= Subject: Re: [Elecraft] K2 Keyer...possible errors Folks: Although Robert commented that he'd cleaned his contacts with "a rough piece of paper", please do NOT misinterpret this to indicate that he used an ABRASIVE paper... at least I assume he didn't. As doing so will immediately remove any trace of gold or silver plating that might have been on the contacts. I good choice (among many others I'm sure), is a paper with a high 'rag' content... such as a DOLLAR BILL!!! Just slip it between the contacts, LIGHTLY press the contacts together and pull the bill thru while the contacts are closed. 73 - Tom Hammond N0SS >I had posted a similar problem but it was with my K1. It was somewhat >intermittent in nature. The problem turns out to be slightly dirty >contacts. > >I cleaned them with a rough piece of paper and no more problems. I believe >Wayne can fill us in about contact debouncing which is done in the software. >The firmware fix made some adjustments to this. I know of 1 other ham >with a similar problem - it was also fixed by contact cleaning. > >Robert >rsm at otology.com -------- > Hi Everyone- > > A few months ago there was some discussion on the reflector about apparent > errors in CW characters being generated by the K2 keyer. I believe the > problem and the fix (in firmware) both occurred about last Thanksgiving with > the release of Firmware Upgrade, Rev. 1.06F. A few defective earlier > version FW chips were replaced as I recall. Since then I've seen nothing > more about the topic of CW errors on the reflector. > > Anyway, in the past couple of weeks I've experienced several disruptive > incidents during CW QSOs when either my K2 keyer, my ham-fisted technique, > or my paddle conspire to generate CW errors. Typically, such occasions > occur at speeds of 15 to 20 WPM (my usual speed) when, for no apparent > reason, the keyer generates an unwanted DIT when it ought to be generating > one or more DAHs. As far as I know, the errors are being transmitted on the > air as well as being heard in sidetone. > > To illustrate, for example when attempting to transmit the first character > of my own callsign (K0PQ), instead of the keyer sending DAH-DIT-DAH, it > sometimes sends instead DIT-DAH-DIT-DAH for the letter 'K'. The remaining > three characters [0 (zero), P, and Q} may be correct, or they too may also > be errored in a similar manner with unwanted DITs. > > Often when the erroneous characters occur, I've also seen the keyer enter a > continuous solid key-down mode--similar to tuning up with an old hand > key--even though only one paddle is being held hard in the continuous DAH > position. > > I'm curious to ask whether anyone else has experienced errors similar to > mine. FYI I use the IAB A and INP PDLR menu options (yes, I reversed the > tip and ring of the paddle cable when I wired it). My K2 is equipped with > FW Upgrade Rev. 1.06F. > > I have a VERY strong hunch that the center post and/or contact spacing on my > paddle (unadjustable and too doggone close to suit me) may be at fault. The > paddle is not really designed for tabletop use...it's very lightweight and > designed for mobile use, I believe (can't recall now who made it). I > readily admit too that my fist isn't the best, but I'm sure it's more than > just my technique. > > In any event these error events seem random...some Qs are completely fine > while others are riddled with frequent errors. > > If any of you CW afficionados have any thoughts, please let me know. BTW I > DO intend to replace the paddle. > > Thanks and 73 > > Steve Banks > K0PQ > K2 S/N 1599 > +++++++++++++++++++++++++++++++++++++++