[Elecraft] K3 Feature Idea

Dave G4AON elecraft at astromag.co.uk
Mon Sep 21 17:59:44 EDT 2009


If I interpret the geekSpeak correctly, this looks like rounding off the
frequency whether the user wants it or not. Coarse tuning rounding off
when using the main tuning control is not a problem, but when the
RIT/XIT tuning control is configured for coarse tuning works just fine
for me the way it is, it is very similar to the implementation from
Kenwood on the TS570 and TS480. Rounding off the frequency when using
the RIT/XIT for tuning is a pain, as an accidental move of that control
means you can't return in a couple of clicks to your original frequency.
The K3 interface already has awkward compromises (accidentally going up
or down a band when turning VOX on, QSK on, not being able to spin
through multiple memories while listening to each one across different
bands, etc.) lets not make it harder to use.

73 Dave, G4AON
K3/100 #80
---------------------

Suppose the VFO were tuned to, say, 7040.23, in CW mode. Further
assume your CONFIG:VFO CRS menu parameter is set to 1.0 kHz (i.e.,
your COARSE tuning step is set to 1.0 kHz in CW mode). If you then go
into COARSE mode and move the VFO up one tic, you'll get 7041.23 with
present firmware. In the future you'll get 7042.00: "quantized" to the
nearest "quantum" which in this case is the next even multiple of 1.0
kHz.

The same will apply if you have the RIT/XIT offset control enabled for
use as VFO coarse tuning when it's not being used for RIT/XIT (see
CONFIG:VFO OFS). The control will be quantized just like the VFO when
it is in COARSE mode.

The VFO already quantizes with smaller tuning increments selected
(e.g. 50 Hz). So quantizing COARSE increments would be more consistent
with present behavior.

73,
Wayne
N6KR


More information about the Elecraft mailing list