K1: Inp Menu Item Pdn Only Allows Dits

[MGFoster]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I changed my Inp from Pdn to Hnd to test out my hand key.  When I
changed back to Pdn only the Dits side responds.  The Dah side doesn't
produce anything (yes, the paddle works outside the K1).

While in Hnd mode I plugged in my hand key with a mono jack.  When the
key was closed a continuous tone was generated.  I figured out that the
mono jack was shorting the ground and Dah poles in the stereo jack, thus
producing the continuous tone.  So I changed the Inp menu item back to
Pdn while I assembled a stereo jack for the hand key.  That's when I
discovered the paddle's Dah was not recognized.  Could I have shorted
something in the keyer circuit?

Thanks,
--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)
KI6OFN
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBR7Nn+oechKqOuFEgEQJ/4wCg+yLTr3FbhzGbpzfwC8Mfq/BSSgwAnRZR
eirQ47YDhKToathlI3fbRDQq
=UgXd
-----END PGP SIGNATURE-----
_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft   

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

[MGFoster]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Brett Howard wrote:
> What happens if you use the test points next to the connector?  Open
the box
> up and just use a paper clip or test lead to short them to the ground
pad
> there and let us know what happens then.
>

I turned on the K1 & tested to see if the problem still existed - it
did.  Turned off the K1 & unplugged, & exposed the bottom of the RF
board.  Powered up & inserted a bent component lead into the Dits &
Ground - OK.  The same on the Dash & Ground - OK!  Plugged the paddles
back in & it worked OK.

OK, so what happened there?

Thanks,
--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBR7Pdy4echKqOuFEgEQJa2ACcCuUY10L5SDKP7XujHgmULXqr61cAoPla
NHHpn7N6lFXBikZqmq8SSy4f
=q0Rc
-----END PGP SIGNATURE-----

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft   

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

[crstrode]

MGFoster Wrote:
I turned on the K1 & tested to see if the problem still existed - it
did.  Turned off the K1 & unplugged, & exposed the bottom of the RF
board.  Powered up & inserted a bent component lead into the Dits &
Ground - OK.  The same on the Dash & Ground - OK!  Plugged the paddles
back in & it worked OK.

OK, so what happened there?

//////////////////////////////

This is very similar to my experience building K1 #2476 last month.  First try with the paddle resulted in strange behavior - can't recall the exact details, but very similar to your experience.  After I unplugged and re-plugged a time or two all was well.

I also vaguely recall a similar phenomenon when K2# 3777 was built.

It almost seems like a micro-controller initial startup hiccup.


I'm guessing the notoriously spooky key jack may have had some debris, poor mechanical alignment, stiff contacts, etc.

I was particularly careful when soldering the key jack to the board - just enough heat to flow, but not melt the flimsy plastic housing.  I've experienced more than one failure of these (both K1 and K2 key and headphone ) jacks so I always keep a spare on-hand.  Both rigs are woking A-OK (at the moment) but I do try to limit the in-out cycles as much as possible to delay the inevitable jack failure.

Carl
WA7CS

[Joseph M. Durnal]

I'm in the process of building a K1, I'll be sure to check the key
jack carefully.  I guess it would be best to wire the straight key,
which is all I use for now, to a stereo plug anyway.

73 de Joseph Durnal NE3R

On Thu, Feb 14, 2008 at 11:22 AM, crstrode <[hidden email]> wrote:

>
> MGFoster Wrote:
> I turned on the K1 & tested to see if the problem still existed - it
> did.  Turned off the K1 & unplugged, & exposed the bottom of the RF
> board.  Powered up & inserted a bent component lead into the Dits &
> Ground - OK.  The same on the Dash & Ground - OK!  Plugged the paddles
> back in & it worked OK.
>
> OK, so what happened there?
>
> //////////////////////////////
>
> This is very similar to my experience building K1 #2476 last month.  First
> try with the paddle resulted in strange behavior - can't recall the exact
> details, but very similar to your experience.  After I unplugged and
> re-plugged a time or two all was well.
>
> I also vaguely recall a similar phenomenon when K2# 3777 was built.
>
> It almost seems like a micro-controller initial startup hiccup.
>
>
> I'm guessing the notoriously spooky key jack may have had some debris, poor
> mechanical alignment, stiff contacts, etc.
>
> I was particularly careful when soldering the key jack to the board - just
> enough heat to flow, but not melt the flimsy plastic housing.  I've
> experienced more than one failure of these (both K1 and K2 key and headphone
> ) jacks so I always keep a spare on-hand.  Both rigs are woking A-OK (at the
> moment) but I do try to limit the in-out cycles as much as possible to delay
> the inevitable jack failure.
>
> Carl
> WA7CS
>
>
>
>
> --
> View this message in context: http://www.nabble.com/K1%3A--Inp-Menu-Item-Pdn-Only-Allows-Dits-tp15468892p15481259.html
> Sent from the Elecraft mailing list archive at Nabble.com.
>
>
> _______________________________________________
> Elecraft mailing list
> Post to: [hidden email]
> You must be a subscriber to post to the list.
> Subscriber Info (Addr. Change, sub, unsub etc.):
>  http://mailman.qth.net/mailman/listinfo/elecraft
>
> Help: http://mailman.qth.net/subscribers.htm
> Elecraft web page: http://www.elecraft.com
>

_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft   

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com

[Don Wilhelm-4]

I can guess at 2 possibilities - one is that there was something sticky
on the shell of that mono plug which adhered to the wiper in the paddle
jack - it only takes a bit of something like the adhesive from
electrical tape to do that.

The second is that somewhere along the dash signal line, you have a bad
solder connection that made contact when it was touched.  If you have
trouble again, I suggest checking the schematic for everything connected
to the dash signal (including connectors) and re-flow the solder.

73,
Don W3FPR

MGFoster wrote:
> I turned on the K1 & tested to see if the problem still existed - it
> did.  Turned off the K1 & unplugged, & exposed the bottom of the RF
> board.  Powered up & inserted a bent component lead into the Dits &
> Ground - OK.  The same on the Dash & Ground - OK!  Plugged the paddles
> back in & it worked OK.
>
> OK, so what happened there?
>
> Thanks,
_______________________________________________
Elecraft mailing list
Post to: [hidden email]
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
 http://mailman.qth.net/mailman/listinfo/elecraft   

Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com