> You can recall the default bandwidth for each roofing filter by using > the XFIL button. If you then used PF1/PF2 for two other bandwidths > you would not tie up M1 - M4.
When operators come in and have an hour or two to learn things, it is easier to relabel the M1-M4 bandwidth and just tap them. When there is QRM and a contact lasts only a few seconds bandwidth needs changed fast! Push and hold takes too long. The RIT and XIT are also used all the time, so there is that consideration. > > It would be nice to have a second frequency tucked away for instant > > recall with one quick tap, not what is on VFO A or B. > > If you free up M1 - M4 you can store four frequencies per band ... to > save them it's V>M M1-M4, to recall them it's M>V M1-M4 (in fact it > appears that you can have eight frequencies and M1-M4 can be both tap > and hold). The use of RIT and the need for speed in changing BW means I have to keep bandwidths on M1-M4. It might be ok but it might also be too inconvient with so many button pushes, I haven't tried it because one of the first suggestions was to get bandwidths on push buttons. :-) I'll give it a try though by eliminating one preset bandwidth and see how it plays. It's just really nice to have a stacking memory in the BAND buttons. Everyone I know uses it far more than regular memories. > I haven't tired it but you might even be able to use "Hold" M1-M4 for > setting bandwidth No, that has to be FAST. >and M>V "tap" M1-M4 for your per band scratchpad > memories. That might be able to be a "hold", I'm going to try making the hold delay longer. 73 Tom ______________________________________________________________ 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
