[Elecraft] Re: K2 Instability on Transmit

Mon Feb 4 10:01:01 2002

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

Fred Cady
Department of Electrical and Computer Engineering
Montana State University
Bozeman, MT  59717
[email protected]
http://www.coe.montana.edu/ee/cady/cadyhmpg.htm
(406) 994-5976
=20

> -----Original Message-----
> From: David A. Belsley [mailto:[email protected]]
> Sent: Monday, February 04, 2002 7:03 AM
> To: Tom Hammond N=D8SS; [email protected]; [email protected]
> Subject: Re: [Elecraft] Re: K2 Instability on Transmit
>=20
>=20
> I also have had a strange 'drifting' behavior similar to that=20
> to which John=20
> refers, although I am pretty sure I've only had it happen in=20
> split mode.=20
> Usually when I hit A=3DB it goes away.  But for a bit, when I=20
> transmit I can=20
> watch the display slowly move upwards (in the second spot to=20
> the right of=20
> the decimal), and the op I'm working indicates there has been=20
> a drift.=20
> Once, during a round-table on cw, my signal just took off up=20
> band, and I=20
> didn't realize it until I heard the guys I was operating=20
> talking about the=20
> disappearance of my signal up band.  That was, however, with the 1.06 =

> firmware, and I haven't had anything quite that drastic with the new=20
> firmware.
>=20
> So, whether this is the same as your problem, John, which=20
> seems to be rit=20
> related, or an altogether different problem, I don't know. =20
> But they sure=20
> sound related.  It's almost like some offset is being recalculated in =

> dynamically iterative manner.  It doesn't happen often and I=20
> don't ever=20
> recall its happening to the receive frequency, just the transmit.
>=20
> best wishes,
>=20
> dave belsley, w1euy
>=20
>=20
>=20
>=20
> --On Monday, February 4, 2002 7:44 AM -0600 Tom Hammond N=D8SS=20
> <[email protected]> wrote:
>=20
> > John:
> >
> >> K3 #139 performed **almost** perfectly during the FOC Marathon =
this
> >> weekend.
> >
> > You have a "K3"... damn! I thought ALL Of the FT's would=20
> get it, not just
> > a 'chosen few'...!!! <G>
> >
> >> The rig was interfaced to TR Log via the KIO2 and the combination
> >> was amazing. The power of TR Log (freeware version) surprised me.
> >
> > Had I known you were gonna use TRLog, I'd have sent you a =
Full-Blown
> > (e.g. current) release to try out!
> >
> >> Now for the problem... Twice during the contest (which I=20
> operated about
> >> 12 hours) the frequency display on the K2 would begin to dither, =
in
> >> random fashion, while transmitting CW. The dithering was=20
> fortunately
> >> confined to the right of the frequency readout decimal point as I
> >> recall. Also, the sound of the sidetone became choppy when=20
> this happened
> >> and several stations commented on the drifting. In one case, =
simply
> >> disengaging RIT corrected the problem; in the other,=20
> powering on/off
> >> twice was necessary.  The K2 ran cool the whole time so I=20
> don't think
> >> heat is an issue. With contest style operation, T/R=20
> change-over cycles
> >> are short/rapid/frequent which might be challenging to=20
> internal timing.
> >
> > Hmmm... I operated 20+ hours in the CW SS and never experienced any
> > problems... any chance it might have been RF-inflicted?
> >
> >> I also notice that occasionally, when RIT is engaged, the transmit
> >> frequency does not always display when transmitting on this K2 =
(the
> >> display stays on the RIT freq). This has happened often=20
> since the rig
> >> was put into service July of 99, but I don't know if the=20
> transmit freq
> >> actually "jumps" or if it's just the display. No one has=20
> ever made note
> >> of it on the air.
> >
> > This is NORMAL (e.g. firmware-related)... I think all of us=20
> who run RIT
> > with ANY logging program find the same thing occuring.
> >
> >> Although this problem resulted in only seconds of=20
> inconvenience over
> >> hours of otherwise flawless contest operation, I am=20
> concerned that it
> >> might get worse and hopeful there is a known cause and=20
> solution.Your
> >> advice would be appreciated. Has anyone else reported such=20
> a problem?
> >
> > Tom
> >
> > _______________________________________________
> > Elecraft mailing list: [email protected]
> > You must be a list member to post to the list. Postings=20
> must be plain
> > text (no HTML or attachments). See:
> > http://mailman.qth.net/mailman/listinfo/elecraft Elecraft Web Page:
> > http://www.elecraft.com
>=20
>=20
>=20
> ----------------------------
> David A. Belsley
> Professor of Economics
> _______________________________________________
> Elecraft mailing list: [email protected]
> You must be a list member to post to the list.=20
> Postings must be plain text (no HTML or attachments).=20
> See: http://mailman.qth.net/mailman/listinfo/elecraft
> Elecraft Web Page: http://www.elecraft.com
>=20