This isn't a glitch, but a definite complaint about SCAN..... It would be a lot better if we didn't have to go to the trouble of first storing a frequency pair in memory then recalling it every time we want to scan a new range. I often find that I don't really want a particular scan range to be permanently stored in memory. Why can't SCAN simply use the current contents of the VFOs for its scan range, however they happen to be set.
Plus, there are all the extra button pushes you have to go through... V->M select a memory location V->M M->V M->V SCAN That's six button pushes required to do what a single push of SCAN alone should be able to accomplish, i.e., just scan from the VFO-A freq to the VFO-B freq. 73, Drew AF2Z On Tue, 20 Oct 2009 12:48:05 -0700 (PDT), Dunc, W5DC wrote: > >Occasionally, the scan function on my K3, S/N 3543, does not function >properly. After loading the frequency range to be scanned with M->V, first >a message appears for perhaps a second saying "AF ON", then scanning starts >without the audio being muted, and scanning fails to pause on signals. This >is not a major problem; I just thought I'd post it to call the programmers >attention to it. I'm currently using 3.44 but I think this also happened in >earlier versions. > >73, Dunc, W5DC ______________________________________________________________ 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
