[Elecraft] K3 - LO CUT/HI CUT bugs

[ab2tc]

Hi,

I can confirm this behavior. I have never noticed this because as an SSB
operator I always use a low cut of either 200, 300 or 400. I generally leave
low cut at 300Hz and use high cut as a QRM fighting tool. Since most CW
operators use the SHIFT/WIDTH mode, that is probably is another reason why
this has gone undetected.

BTW the graphic passband representation is also pretty screwed up when
changing back and forth between shift/width and hicut/locut modes. In
particular, changing the hi cut often moves the left edge of the graphics
when switching between the modes. I can provided a detailed scenario if it
helps.



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.
> 
> I'm using FW 2.67 and DSP 1.96. I have the FM filter in FL1, and the  
> 2.7KHz filter in FL2.  No other filters currently installed.  Both the  
> FM and 2.7K filters are enabled for SSB and CW Rx.
> 
> I'll start with SSB mode.
> 
> I expected the LO and HI values to be independently adjustable with  
> the only limitation that the HI value must be higher than the LO  
> value.  However, I find that for HI values greater than 2.70, the  
> maximum LO value I can dial in is lower, Hz for Hz.  In other words,  
> the LO and HI limits track in opposite directions when the HI value is  
>  > 2.70.  Example:
> 
> HI value    Max LO value
> 2.70        2.50
> 2.80        2.40
> 2.90        2.30
> 3.00        2.20
> 3.10        2.10
> ...         ...
> 4.10        1.10
> 
> <snip>
> 


-----
AB2TC - Knut
-- 
View this message in context: http://n2.nabble.com/K3---LO-CUT-HI-CUT-bugs-tp1581668p1582883.html
Sent from the Elecraft mailing list archive at Nabble.com.