[Elecraft] Re: K2 Instability on Transmit

Sun Feb 10 23:50:01 2002

I just had this problem while working the Sprint. N6TR can atest to it as he was the station I was sending an exchange to at the time. I was not in split. KIO2 was in use. Computer was a laptop. Software NA.
Band 40 meters.
Bob WO3B

----Original Message-----
   >From:     =09"Ron D' Eau Claire" <[email protected]>
   >To:         =09<[email protected]>
   >Subject:     =09RE: [Elecraft] Re: K2 Instability on Transmit
   >Reply-To:     =09<[email protected]>
   >Date:    =09Monday, February 04, 2002 08:19
   >
   >
   >> We had the same problem during the CQWW test at 6YxA.  Pretty sure it was
   >> while operating split, which I did a lot due the the RIT not being very
   >> convenient.  Power off/on seemed to cure it and away we would go again.
   >>
   >> Fred KE7X
   >
   >
   >Egad! So this OLD bug is still with us?
   >
   >The last time I e-mailed Wayne about it was last May (2001), but I am also
   >still running the 1.06 firmware and so I haven't reported the subsequent
   >incidences. I'll be putting in new firmware in a few days in the hopes that
   >it would cure the problem.
   >
   >Guess not...
   >
   >I run SPLIT 100% of the time, and the problem appears about once every 10
   >hours of operation or so. Suddenly the TX frequency starts incrementing up
   >the band as I key. I've gotten used to doing to things: 1) Noting my EXACT
   >TX frequency as shown on the display at the start of every QSO and 2)
   >Keeping an eye on the display because I will see it start moving when the
   >bug strikes. Then I can quickly hit A/B and manually reset the transmit
   >frequency and then apologize to the op on the other end. Changing the TX
   >frequency manually seems to cure it every time... until the next time...
   >
   >It's sort of a big hole in the K2 MOJO bucket that opens at random. But I've
   >tried and tried and have not been able to give the Elecraft guys a way to
   >make it happen on demand. And if you can't make it break on cue, it's very
   >hard to know when it's fixed. Last Spring when it last came up on the
   >reflector here there were about a dozen of us who swapped messages about
   >being afflicted with the problem. So it's NOT an isolated incident limited
   >to one or two K2's.
   >
   >Ron AC7AC
   >K2 # 1289
   >
   >_______________________________________________
   >Elecraft mailing list: [email protected]
   >You must be a list member to post to the list. 
   >Postings must be plain text (no HTML or attachments). 
   >See: http://mailman.qth.net/mailman/listinfo/elecraft
   >Elecraft Web Page: http://www.elecraft.com
   >