[Elecraft] K3 - LO CUT/HI CUT bugs

[Ed Muns]

While this isn't a major issue, it will be nice to have it operate more
smoothly and predictably.  The issue has been on the firmware "list" for
some time now but other enhancements and improvements have taken priority.
Even though I personally would like this issue addressed, I strongly support
Elecraft engineering putting emphasis where they have been.

In general, WIDTH/SHIFT are best applicable to CW and DATA modes while HI
CUT/LO CUT fit SSB better.  When I want to narrow my RX SSB bandwidth, I
reduce HI CUT because that simultaneously narrows the bandwidth and moves Fc
down at half the rate which is exactly where I want the narrower bandwidth
located in the audio passband.  (Using WIDTH requires a correlated
adjustment of SHIFT while searching for the best intelligibility.  I find
this much more difficult and time-consuming than simply reducing HI CUT.  LO
CUT never needs to be touched until you get to SSB bandwidths lower than
about 1.5 kHz.)  Narrowing WIDTH, then switching to LO CUT/HI CUT, etc. is
not a viable solution for quick bandwidth changes on SSB.

One of my K3s is has nominal LO CUT at 250 Hz while the other one is at 300
Hz, with both having increments of 100 Hz.  This is a minor annoyance, not a
major problem.  To that point, I don't spent time trying to keep them the
same.  It just doesn't matter much and I'd rather spend the time operating.

Ed

Rich, KE0X replied:
> Is this really a case that something is broken or is it that 
> the operation needs to be explained better? 
> If you set the BW to a very narrow width, THEN, switch over 
> to adjust the HI and/or LO CUT, things seem to work as I 
> would expect. 
> It appears to me that the HI/LO CUT is associated with the 
> center frequency and not that the LO cut is associated with 
> the HI CUT or vice versa.
> Since the K3 has a minimum (minimal) amount of front panel 
> controls some of the controls function is counter intuitive.
> 
> Rich,
> KE0X
> 
> 
> Joe Planisky wrote:
> > 
> > Up until recently, I had only used the SHIFT/WIDTH functions for 
> > setting the DSP filter parameters.  This morning I decided 
> to try the 
> > LO CUT/HI CUT functions.  I really don't understand the 
> behavior I'm 
> > seeing and I suspect there's something wrong.
> > 
> > 
> >