[Elecraft] KX3 Paddle Problem

Fri Jul 25 20:24:11 EDT 2014

Jerry ‹

The cause of the problem is pretty well understood - the route to ground
is through the pivot pins, and their contact with the grounded pivot-pin
socket is unreliable.  It may be that your manhandling the levers put
enough stress on the assembly to drive the pins into their sockets for a
while.  

I too tried the Deoxit route, which worked for a few months.  A couple of
weeks ago I adopted the suggestion several people have made here - wire
the spring-holder screws to the ground terminal on the chassis plug (on
the paddle) and the problem is solved.

Turns out to be pretty easy.  I soldered a wire at its mid-point to the
long lead going from the paddle¹s circuit board into the plug¹s ground
point, then threaded each side to the spring-holder screws, backed those
out, wrapped the wire around the screws, tightened them down, and that¹s
it.  The wire was a single strand from a small-guage speaker wire.  It is
almost invisible.  I can take a photo if you like - email me off-list
(edauer at law.du.edu)

Ted, KN1CBR

>Message: 19
>Date: Fri, 25 Jul 2014 12:23:32 -0700 (PDT)
>From: AB3SX <whelanjh at gmail.com>
>To: elecraft at mailman.qth.net
>Subject: [Elecraft] KXPD3 Paddle Intermittent - At the hinge-posts ?
>Message-ID: <1406316212495-7591582.post at n2.nabble.com>
>Content-Type: text/plain; charset=us-ascii
>
>Good afternoon, Gentlemen -
>
>I have been experiencing intermittent contact problems on my KX3 paddle
>for
>weeks now. ( I have read all the experiences on the group, and tried those
>suggestions.) Sometimes I would gain temporary relief from dis-assembly,
>cleaning, reassembly, but the problem always returned.
>
>The main symptoms are "missing dit"; with easy wrist-rolling from side to
>side, I suddenly come up with no dit where one should be. I learned I
>could
>minimize this problem by "man-handling" the levers, but this was tiring (
>that is, forceful lever movements seemed to solve the problem of
>intermittent contact ). This seemed strange, since I could clearly "feel"
>the movable contact stop on the post, even though no electrical contact
>was
>completed.
>
>Well, something FORCED me to have a better look into what was happening,
>and
>I thought I would see if any of you have been experiencing this same
>problem. I have recently been operating the KX3 set up as "hand-key" and
>the
>automatic creation of proper length dots and dashes is no longer present
>to
>cover up the frequently intermittent contact. So today, I followed a hunch
>and connected two clip leads to provide ground from the chassis to each of
>the movable levers. Sure enough, this put an end to the intermittent
>operation. I repeated the test several times, and each time the
>intermittent
>would appear without the clip leads, and disappear once the clip leads
>were
>reattached. 
>
>I followed this up with a power-off resistance measurement from each of
>the
>movable levers to the chassis and, sure enough, LARGE resistances were
>found. Depending on the amount of pressure exerted on the lever ( to load
>the swing-lever/pin joint, the resistance could be varied from 8000 ohms
>to
>1200, 800, all the way down to 1.3 ohms ). I went further to check the
>resistance to chassis from the knurled-bolt KXPD3 fasteners ( 1.0 ohm )
>and
>the resistance to chassis from the top-place of the KXPD3 ( 1.2 ohms ).
>Only
>the last part of the path to each lever seems to be involved in the
>high-resistance problem ( the vertical hinge that supports and grounds
>each
>lever ).
>
>So, AT-LAST, my problem has been located. I am wondering if this has
>happened to anyone else with the KXPD3? ( It looks like most of such
>discussion peaked and went away in year 2012, so I am guessing I am the
>only
>one with the problem ).
>
>Love my KX3, and can't wait to get this one little quibble quashed :)
>
>Jerry AB3SX
>
>
>
>
>
>--
>View this message in context:
>http://elecraft.365791.n2.nabble.com/KXPD3-Paddle-Intermittent-At-the-hing
>e-posts-tp7591582.html
>Sent from the Elecraft mailing list archive at Nabble.com.
>
>
>------------------------------
>
>Message: 20
>Date: Fri, 25 Jul 2014 15:44:25 -0400
>From: K8JHR <jrichards at k8jhr.com>
>To: elecraft at mailman.qth.net
>Subject: Re: [Elecraft] WRTC 2014 - Congratulations, Elecraft!...(and
>	firmware update)
>Message-ID: <53D2B399.6010701 at k8jhr.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>Shucks, fellers.  All that does not add up.
>
>WE can rationalize this any way we like, but the fact is, 5 of the 6
>best operators did not choose a K3, and I know least one other happy K3
>owner used a Brand-X radio for the competition, and in all of his
>qualifying rounds.
>
>Logically - If you say the rig does not matter, and it all turns on
>operator skill ... then no one can brag about any particular radio used
>in the competition for any reason.   We cannot have it both ways.
>We cannot say the K3 is best because 70 percent of the field used one,
>but it does not matter what the winners used, because after all, it all
>turns on operator skill.   If the rig does not matter for the winners,
>it does not matter for anyone.
>
>So the unfortunate bottom line take-away is the top three teams used 5 5
>ICOMS and one K3.
>
>Again, if you claim the radio does not matter, then it does not matter,
>and we cannot claim any victory for any rig used in the contest.  That
>would be inconsistent.
>
>
>
>Personally, I think the fact 70 percent of the field used the same model
>radio is significant, although it may just prove it is easier than other
>radios to ship and travel with.  Still... it is a big number.
>
>Just MY take.
>----------------------- K8JHR  ---------------------
>
>
>
>
>
>On 7/25/2014 8:27 AM, Barry wrote:
>> I agree completely.  The rig and logging software have very to do with
>>the
>> outcome.
>>
>> The #1 team probably has a sore back and sore arms, from lugging 7800s
>>there
>> :-)
>>
>> Barry W2UP
>>
>>
>>
>> Don Wilhelm-4 wrote
>>> Yes, very interesting, and I think most of the credit goes to the
>>> operators, rather than the radios.
>>>
>>> However, the fact that a very large percentage of these top operators
>>> *choose* to use the Elecraft K3 does say a lot about the desirability
>>>of
>>> the K3 for contesting.  Whether that be because of the weight, or
>>> because of the performance and operating interface, you would probably
>>> have to ask each K3 operator about his choice.
>>>
>>> 73,
>>> Don W3FPR
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>>http://elecraft.365791.n2.nabble.com/WRTC-2014-Congratulations-Elecraft-t
>>p7591534p7591572.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: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 jrichards at k8jhr.com
>>
>
>
>------------------------------
>
>Message: 21
>Date: Fri, 25 Jul 2014 16:18:43 -0500
>From: n5ib at juno.com
>To: Elecraft at mailman.qth.net
>Subject: [Elecraft] Bluetooth serial interface for K2/KIO2
>Message-ID: <20140725.161843.86400.20.n5ib at juno.com>
>Content-Type: text/plain; charset=us-ascii
>
>I finished a prototype of the little Bluetooth serial data interface for
>my K2.
>Just plugs in the back of the K2 on the KIO2's DB9 connector, drawing its
>power from there.
> 
>The prototype seems to work fine. Have been running for about a week.
>I'm presently using it with N3FJP's ACLog, and have tried it out with an
>older version of Ham Radio Deluxe.
> 
>Info (schematic, BOM, photos) here:
><http://n5ib.net/Elecraft%20K2%20Bluetooth%20Interface%20Overview.pdf>
> 
>72,
>Jim, N5IB
>
>
>------------------------------
>
>Message: 22
>Date: Sat, 26 Jul 2014 07:37:12 +1000
>From: Matt VK2RQ <matt.vk2rq at gmail.com>
>To: AB3SX <whelanjh at gmail.com>
>Cc: "elecraft at mailman.qth.net" <elecraft at mailman.qth.net>
>Subject: Re: [Elecraft] KXPD3 Paddle Intermittent - At the hinge-posts
>	?
>Message-ID: <8EE84C88-624A-48BE-A5D3-1B92CDC46C7A at gmail.com>
>Content-Type: text/plain;	charset=us-ascii
>
>Yes, this has been discussed in both this reflector, and the KX3 yahoo
>group. Here is a blog posting from one of the guys who did this mod:
>http://wv0h.blogspot.com.au/2013/09/kxpd3-mod.html
>
>I did pretty much the same thing, and it has proven effective.
>
>73,
>Matt VK2RQ
>
>> On 26 Jul 2014, at 5:23 am, AB3SX <whelanjh at gmail.com> wrote:
>> 
>> Good afternoon, Gentlemen -
>> 
>> I have been experiencing intermittent contact problems on my KX3 paddle
>>for
>> weeks now. ( I have read all the experiences on the group, and tried
>>those
>> suggestions.) Sometimes I would gain temporary relief from dis-assembly,
>> cleaning, reassembly, but the problem always returned.
>> 
>> The main symptoms are "missing dit"; with easy wrist-rolling from side
>>to
>> side, I suddenly come up with no dit where one should be. I learned I
>>could
>> minimize this problem by "man-handling" the levers, but this was tiring
>>(
>> that is, forceful lever movements seemed to solve the problem of
>> intermittent contact ). This seemed strange, since I could clearly
>>"feel"
>> the movable contact stop on the post, even though no electrical contact
>>was
>> completed.
>> 
>> Well, something FORCED me to have a better look into what was
>>happening, and
>> I thought I would see if any of you have been experiencing this same
>> problem. I have recently been operating the KX3 set up as "hand-key"
>>and the
>> automatic creation of proper length dots and dashes is no longer
>>present to
>> cover up the frequently intermittent contact. So today, I followed a
>>hunch
>> and connected two clip leads to provide ground from the chassis to each
>>of
>> the movable levers. Sure enough, this put an end to the intermittent
>> operation. I repeated the test several times, and each time the
>>intermittent
>> would appear without the clip leads, and disappear once the clip leads
>>were
>> reattached. 
>> 
>> I followed this up with a power-off resistance measurement from each of
>>the
>> movable levers to the chassis and, sure enough, LARGE resistances were
>> found. Depending on the amount of pressure exerted on the lever ( to
>>load
>> the swing-lever/pin joint, the resistance could be varied from 8000
>>ohms to
>> 1200, 800, all the way down to 1.3 ohms ). I went further to check the
>> resistance to chassis from the knurled-bolt KXPD3 fasteners ( 1.0 ohm )
>>and
>> the resistance to chassis from the top-place of the KXPD3 ( 1.2 ohms ).
>>Only
>> the last part of the path to each lever seems to be involved in the
>> high-resistance problem ( the vertical hinge that supports and grounds
>>each
>> lever ).
>> 
>> So, AT-LAST, my problem has been located. I am wondering if this has
>> happened to anyone else with the KXPD3? ( It looks like most of such
>> discussion peaked and went away in year 2012, so I am guessing I am the
>>only
>> one with the problem ).
>> 
>> Love my KX3, and can't wait to get this one little quibble quashed :)
>> 
>> Jerry AB3SX
>> 
>> 
>> 
>> 
>> 
>> --
>> View this message in context:
>>http://elecraft.365791.n2.nabble.com/KXPD3-Paddle-Intermittent-At-the-hin
>>ge-posts-tp7591582.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: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 matt.vk2rq at gmail.com
>
>
>------------------------------
>
>Message: 23
>Date: Fri, 25 Jul 2014 17:00:06 -0500
>From: John Cooper <wt5y at gt.rr.com>
>To: n5ib at juno.com, Elecraft at mailman.qth.net
>Subject: Re: [Elecraft] Bluetooth serial interface for K2/KIO2
>Message-ID: <nbhwrswxhuxqmj3gh7bt1nop.1406325606314 at email.android.com>
>Content-Type: text/plain; charset=utf-8
>
>Very nice! My thing is I'm using that port for the kat100 tuner. ?If it
>could be wired directly to kpa100 serial and left inside the k2/100 that
>would be perfect.?
>
>WT5Y
>
>
>Sent from my Cricket smartphone
>
>-------- Original message --------
>From: n5ib at juno.com
>Date: 07/25/2014  16:18  (GMT-06:00)
>To: Elecraft at mailman.qth.net
>Subject: [Elecraft] Bluetooth serial interface for K2/KIO2
> 
>I finished a prototype of the little Bluetooth serial data interface for
>my K2.
>Just plugs in the back of the K2 on the KIO2's DB9 connector, drawing its
>power from there.
>
>The prototype seems to work fine. Have been running for about a week.
>I'm presently using it with N3FJP's ACLog, and have tried it out with an
>older version of Ham Radio Deluxe.
>
>Info (schematic, BOM, photos) here:
><http://n5ib.net/Elecraft%20K2%20Bluetooth%20Interface%20Overview.pdf>
>
>72,
>Jim, N5IB
>______________________________________________________________
>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 wt5y at gt.rr.com
>
>------------------------------
>
>Message: 24
>Date: Fri, 25 Jul 2014 15:36:05 -0700
>From: Jim Brown <jim at audiosystemsgroup.com>
>To: Reflector Elecraft <elecraft at mailman.qth.net>
>Subject: [Elecraft] XV144 Advice Needed -- And Another Manual Goof
>	Noted
>Message-ID: <53D2DBD5.7050506 at audiosystemsgroup.com>
>Content-Type: text/plain; charset=utf-8; format=flowed
>
>I've reclaimed an XV144 that I bought used in 2005 and have never used
>from a friend to whom I loaned it. I'll be using it with a K3, that will
>be dedicated to 2M. I'm told that frequency stability is a concern, and
>that it's important to drive it at the "right" level so that fixed
>attenuation is not switched in to protect the TX input. The question is,
>what is the "right" level to minimize dissipation inside the XV144? So
>far, I haven't found that in the manual or the specs.
>
>Another observation. The latest manual for the XV-series converters
>contains another massive goof in the wiring of the AUX cable. It shows
>only two conductors with no return, depending on the coax to carry a
>return signal. That's fine for DC, but our stations produce RF, so the
>large loop formed by the coax and the control lines is a big antenna.
>TILT!
>
>Time for another manual re-writing. And to fire the guy who conceived
>the drawing.
>
>73, Jim K9YC
>
>
>------------------------------
>
>Message: 25
>Date: Fri, 25 Jul 2014 17:43:01 -0500
>From: dave <ho13dave at gmail.com>
>To: elecraft at mailman.qth.net
>Subject: Re: [Elecraft] WRTC 2014 - Congratulations, Elecraft!...(and
>	firmware update)
>Message-ID: <53D2DD75.4000903 at gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>I think that the rig is not very important. One tidbit to support this
>theory, although far from conclusive, is to compare what happened to
>the OE3DIA team in 2010 vs 2014.
>
>In 2010 there was a nasty lightning storm the took out both of this
>teams K3's. They were knocked out about 1 hour into the contest. But
>Yaesu had some reps on site and they had a pair of FT857's which they
>loaned to the team. They lost about an hour in the switchover. So they
>ran for 23 hours while the other teams ran for 24.
>
>If you compare their score at the end of the contest to the other
>teams after 23 hours (the hour-by-hour scores was available on the
>Russian web site for a while after the contest) they were in about the
>middle of the pack. This is using K3's for 1 hour and FT857's for 22
>hours.
>
>In 2014 I see no notes about anyone suffering such a loss and the
>OE3DIA team finished 22nd out of 59. Again about the middle of the
>pack. I think this somewhat better than their 23 hour comparison in
>2010, but not a lot better.
>
>This would tend to indicate that - when in the hands of very competent
>operators - a pair of lowly FT857's is nearly as good as a pair of K3's.
>
>Now, don't get me wrong here, I'm not saying the FT857 is as good as a
>K3, it is *not*. No doubt about that. In fact, it is not as good as a
>K2. I have those two sitting here side by side and I can assure you
>that the K2 is the superior rig. What it says to me is that the K3 and
>others of its class are somewhat overkill. The lowly FT857 is 'nearly
>good enough'. Certainly not great, but 'nearly good enough'.
>
>73 de dave
>ab9ca/4
>
>
>
>On 7/25/14 2:44 PM, K8JHR wrote:
>> Shucks, fellers.  All that does not add up.
>>
>> WE can rationalize this any way we like, but the fact is, 5 of the 6
>> best operators did not choose a K3, and I know least one other happy
>> K3 owner used a Brand-X radio for the competition, and in all of his
>> qualifying rounds.
>>
>> Logically - If you say the rig does not matter, and it all turns on
>> operator skill ... then no one can brag about any particular radio
>> used in the competition for any reason.   We cannot have it both ways.
>> We cannot say the K3 is best because 70 percent of the field used one,
>> but it does not matter what the winners used, because after all, it
>> all turns on operator skill.   If the rig does not matter for the
>> winners, it does not matter for anyone.
>>
>> So the unfortunate bottom line take-away is the top three teams used 5
>> 5 ICOMS and one K3.
>>
>> Again, if you claim the radio does not matter, then it does not
>> matter, and we cannot claim any victory for any rig used in the
>> contest.  That would be inconsistent.
>>
>>
>>
>> Personally, I think the fact 70 percent of the field used the same
>> model radio is significant, although it may just prove it is easier
>> than other radios to ship and travel with.  Still... it is a big number.
>>
>> Just MY take.
>> ----------------------- K8JHR  ---------------------
>>
>>
>>
>>
>>
>> On 7/25/2014 8:27 AM, Barry wrote:
>>> I agree completely.  The rig and logging software have very to do
>>> with the
>>> outcome.
>>>
>>> The #1 team probably has a sore back and sore arms, from lugging
>>> 7800s there
>>> :-)
>>>
>>> Barry W2UP
>>>
>>>
>>>
>>> Don Wilhelm-4 wrote
>>>> Yes, very interesting, and I think most of the credit goes to the
>>>> operators, rather than the radios.
>>>>
>>>> However, the fact that a very large percentage of these top operators
>>>> *choose* to use the Elecraft K3 does say a lot about the
>>>> desirability of
>>>> the K3 for contesting.  Whether that be because of the weight, or
>>>> because of the performance and operating interface, you would probably
>>>> have to ask each K3 operator about his choice.
>>>>
>>>> 73,
>>>> Don W3FPR
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> 
>>>http://elecraft.365791.n2.nabble.com/WRTC-2014-Congratulations-Elecraft-
>>>tp7591534p7591572.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: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 jrichards at k8jhr.com
>>>
>> ______________________________________________________________
>> 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 ho13dave at gmail.com
>>
>
>
>------------------------------
>
>Message: 26
>Date: Fri, 25 Jul 2014 16:23:17 -0700
>From: Fred Jensen <k6dgw at foothill.net>
>To: elecraft at mailman.qth.net
>Subject: Re: [Elecraft] WRTC 2014 - Congratulations, Elecraft!...(and
>	firmware update)
>Message-ID: <53D2E6E5.8010702 at foothill.net>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>I think you're correct Dave.  Unlike all other contests, WRTC is
>refereed and everyone uses identical antennas and power ... about as
>level a playing field as you could ever create.  WRTC *is* structured to
>focus on operator skills vs station excellence, 100W is 100W in that
>situation, it doesn't really matter which rig generated the RF.
>Mandating a specific radio would put all the ops who don't use that
>radio in everyday contesting at a big disadvantage.
>
>There could be some small advantages on receive, I imagine they were
>confronted with pile-ups earlier in the contest, but eventually, they
>likely worked everyone they heard, and I doubt there would be much
>difference in what one could hear on a K3 vs a 7600, FT1000, or other
>radios.  They're all either current state-of-the-art radios or close.
>
>The one factor that using different radios does not control for is
>spurious emissions such as key clicks and phase noise.  There *is* a
>wide difference in those between the radios.  Don't know if that would
>turn out to be an issue in the WRTC environment, although I sure know it
>was when my "neighbor" Jack, KF6T, was running a Yaesu rig with serious
>phase noise problems.  Of course, if clicks and phase noise was an issue
>at WRTC, it would impact everyone else negatively.
>
>73,
>
>Fred K6DGW
>- Northern California Contest Club
>- CU in the 2014 Cal QSO Party 4-5 Oct 2014
>- www.cqp.org
>
>On 7/25/2014 3:43 PM, dave wrote:
>> I think that the rig is not very important. One tidbit to support this
>> theory, although far from conclusive, is to compare what happened to the
>> OE3DIA team in 2010 vs 2014.
>>
>> In 2010 there was a nasty lightning storm the took out both of this
>> teams K3's. They were knocked out about 1 hour into the contest. But
>> Yaesu had some reps on site and they had a pair of FT857's which they
>> loaned to the team. They lost about an hour in the switchover. So they
>> ran for 23 hours while the other teams ran for 24.
>>
>> If you compare their score at the end of the contest to the other teams
>> after 23 hours (the hour-by-hour scores was available on the Russian web
>> site for a while after the contest) they were in about the middle of the
>> pack. This is using K3's for 1 hour and FT857's for 22 hours.
>>
>> In 2014 I see no notes about anyone suffering such a loss and the OE3DIA
>> team finished 22nd out of 59. Again about the middle of the pack. I
>> think this somewhat better than their 23 hour comparison in 2010, but
>> not a lot better.
>>
>> This would tend to indicate that - when in the hands of very competent
>> operators - a pair of lowly FT857's is nearly as good as a pair of K3's.
>>
>> Now, don't get me wrong here, I'm not saying the FT857 is as good as a
>> K3, it is *not*. No doubt about that. In fact, it is not as good as a
>> K2. I have those two sitting here side by side and I can assure you that
>> the K2 is the superior rig. What it says to me is that the K3 and others
>> of its class are somewhat overkill. The lowly FT857 is 'nearly good
>> enough'. Certainly not great, but 'nearly good enough'.
>>
>> 73 de dave
>> ab9ca/4
>
>
>
>
>------------------------------
>
>Subject: Digest Footer
>
>_______________________________________________
>Elecraft mailing list
>Post to: Elecraft at mailman.qth.net
>http://mailman.qth.net/mailman/listinfo/elecraft
>You must be a subscriber to post.
>Elecraft web page: http://www.elecraft.com
>
>------------------------------
>
>End of Elecraft Digest, Vol 123, Issue 31
>*****************************************