Hello,
It's been a while since we've seen firmware updates for the K line -- is
there any chance that the RIT bug described below will be fixed this year?
Thanks,
Bob NW8L
On Thu, 27 Feb 2014, Bob wrote:
Date: Thu, 27 Feb 2014 07:02:55 +0000 (UTC)
From: Bob <[email protected]>
To: Wayne Burdick <[email protected]>
Cc: Elecraft Reflector <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [Elecraft] Need volunteers to try an even better version of
KAT500 firmware (rev. 1.63) -- more accurate initial tunes
I updated to KAT500 1.63 and latest KPA500 and K3 firmware. I like the way
the KAT500 follows the VFO on the K3 but I noticed something odd when the VFO
is set near a boundary between two KAT500 stored band slice memories.
When RIT is enabled, the KAT500 follows the frequency set by the RIT offset.
That is, I hear the relays click after crossing the memory boundary using RIT
and stopping on a new listening frequency. If I press CLR to reset the RIT
offset, the relays click again as the KAT500 follows
the VFO back to the original frequency and recalls the settings for that band
slice.
However, When XIT is enabled, the KAT500 does not follow the frequency set by
the XIT offset. That is, I hear no relay clicking after crossing the boundary
using XIT and stopping on a new transmit frequency in the adjacent band
slice, for which different settings are normally recalled.
Shouldn't it be the other way around, to optimize the match for the
transmitter, not the receiver?
It's late, maybe I'm missing something.
Bob NW8L
On Tue, 25 Feb 2014, Wayne Burdick wrote:
Date: Tue, 25 Feb 2014 09:31:16 -0800
From: Wayne Burdick <[email protected]>
To: Elecraft Reflector <[email protected]>,
"[email protected]" <[email protected]>
Subject: [Elecraft] Need volunteers to try an even better version of KAT500
firmware (rev. 1.63) -- more accurate initial tunes
Hi all,
We just posted a new beta-test release of KAT500 firmware (rev 1.63) that
does a better job on initial tunes than the previous release (1.58). We'd
really like to get this firmware into production quickly, but to do that
we'll need some testing help.
If you can spare a few minutes, please do the following:
1) Save your current configuration so that you can return to it if
necessary
2) Install KAT500 rev. 1.63 (follow instructions for beta releases)
3) Erase memories on at least one band where the tuner has to work to find
solutions (that?s 160 through 40 meters for most of us)
4) Do some full-search tunes.
The KAT500 should find very good tuning solutions (within its specified
impedance-matching limits, of course). Please send me your results.
Thanks--
Wayne
N6KR
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
[email protected]
SDF Public Access UNIX System - http://sdf.org
[email protected]
SDF Public Access UNIX System - http://sdf.org
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]
