[Elecraft] [K3] General coverage hijacks ham band

[Rick Dettinger]

Yes, they work that way.
That is why I use the memories to navigate through the ham bands.

73,
Rick Dettinger  K7MW



 
On Feb 14, 2015, at 7:01 PM, dmb at lightstream.net wrote:

> I am probably doing something wrong, but I cannot find any reference to
> the following issue in the K3 manual.
> 
> It seems that if one tunes to a non-ham band (general coverage) frequency
> (I used numerical direct frequency entry), the ham band closest to the
> target frequency now assumes the targeted general coverage frequency.
> 
> For example, I was on 40m and wanted to check a local broadcast AM station
> at 1100 KHz. I entered "1.100" via the "FREQ ENT" button, and the radio
> tuned to 1100 KHz as expected. However, now when I cycle through the ham
> bands, the 160 meter slot is set to 1.100 Mhz instead of 1.8XX MHz.
> 
> Is this the way it is supposed to work? It's a bit of a deterrent to use
> the KBPF3 to explore general coverage frequencies if a ham band gets
> hijacked as a result.
> 
> 73, Dale
> WA8SRA
> 
> 
> 
> 
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at mailman.qth.net
> 
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to k7mw78 at gmail.com