A while back I thought it would be useful to be able to limit a VFO's frequency excurusion to a user-selected segment. Then if you should get to the end of such a defined segment the VFO reading would simply jump to the other end of the segment and keep going, traversing the same segment again as you kept spinning the knob.
I didn't think of this as a method of marking the legal band boundaries, but rather for the purpose of sorting through a pileup without having to keep looking at the frequency display, reversing VFO direction, etc. Just keep spinning the knob and you'd always be within your defined segment. BTW, I don't work any pileups myself; just like to hunt through them to find who/where the DX is currently working (no sub rcver or band scope here). But I suppose those who generate the pileups might find it useful as well. It could of couse also be used to limit the VFO excursions to the legal band boundaries if someone wanted to do that. 73, Drew AF2Z On Tue, 20 Aug 2013 13:30:48 -0500, Terry, W0FM wrote: >My needs are much simpler than those involving international frequency tables, >license classes, memory locations, etc. I haven't thought this through >thoroughly so I don't know all the ramifications. I'll leave that all to >someone smarter than me. > >I know that I am quite embarrassed to be told that I have just transmitted >outside the legal US band (usually involves DX pounces) and would like to be >reminded if my inattention causes me to do that. I see *self enforcement* >here. > >I could envision a "Band Marker" that could be set by the K3 user personally. >Tune the VFO to the band (or sub band) edge you'd like to be notified of. Say >14.000. In the menu you find "Band Marker". Select that option and the >software creates a tone (beep if you will) on 14.000. If you wanted to be >alerted that you are passing the high end of the 20M band, simply set your VFO >to 14.350, and, in the menu, select "Band Marker". BEEP created. Same >process to mark the CW, RTTY, etc sub-band if that's your desire. > >The K3 owner could be free to opt for doing this or not, as well as for which >bands, license privileges or mode sub-bands he wished. Nothing forced. All >on the operator (and sw guys like Lyle, of course). No software tables, band >lists per country or license classes involved. Nothing to force a transmitter >shut down. It would simply be an *operator assigned* aid for the >*convenience* of the individual operator. > >Of course, this would not help direct frequency entry band errors, instant >spots, etc. Just thinking through my keyboard. ;o) > >Thoughts? Someone will probably tell me that this already exists in the K3. >;o) > >Terry, W0FM > > ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
