Thanks Joe. I hadn't noticed that. I seldom use RIT/XIT when working split, but I played with that to demonstrate what you're saying.
Didn't realize the cursor actually changes color (on VFO B/SubRX) from purplish to red - I just knew it was quite simple to distinguish the diff between where I was listening and where I would be transmitting! My partial color-blindness is referred to as "red-green" but I have no trouble seeing the obvious green line for the VFO A and the "other" color for the VFO B. My affliction is revealed by the test of pages with all the colored dots. (Wechsler or something like that.) People with normal vision see numbers - the numbers tend to stand out distinctly among all the colored dots. Those with red-green color-blindness (surprisingly common) can eventually find the numbers, but they don't "leap" off the page like they do for "normal" people. Fortunately, stand-alone, distinct colors (like the red and green of a traffic light!) do not cause problems. Art - N4PJ On Sat, May 19, 2012 at 7:28 AM, Joe Subich, W4TV <li...@subich.com> wrote: > > > With the sub-receiver engaged, split engaged and the difference in > > color between the two cursors, I guess I fail to understand whey > > there would be a huge need for anything else - at least anything else > > relating to the P3/K3 functionality that already exists. > > When split, RIT or XIT is engaged a third - RED transmit - cursor is > also visible. It is inexcusable for anyone with a P3 to ever fail to > realize they are/are not split simply because the red cursor is to > very visible. The transmit cursor is present when transmit frequency > is different from the main receiver frequency (when the K3 red "delta > F" LED is on) even if one turns off the VFO B cursor. > > 73, > > ... Joe, W4TV > > > On 5/19/2012 7:15 AM, Arthur Burke wrote: > > Guess I don't understand what all the fuss is about. In "standard" mode, > > there are two cursors on my P3 - one green and one sort of purplish (I > have > > a partial color blindness, but there is a distinct difference between the > > two cursors, even for me). > > > > Even if you're not operating in SPLIT mode, when you tune the VFO B (the > > purplish marker) away from the frequency of VFO A, it stands out quite > > prominently on the P3 display. > > > > I operate mostly CW. When a split operation takes place, and I tune > > somewhere "into the piluep" I might typically have reduced the SPAN to 20 > > kHz so there's 10 kHz on each side of the DX operating frequency. As I > tune > > the VFO B (most often it's actually the sub-receiver so I can also hear > > what's going on in the pileup), you can see an obvious "gap" between the > > two cursors. > > > > Personally, I enjoy cruising through the pileup, trying to find who the > DX > > is currently working, trying to quickly discern a "pattern" (if any) of > the > > DX operator. When someone in a cluster spot writes that he worked 'em, it > > is most often something like "QSX 14027.5" as opposed to "up 1.375." > > > > With the sub-receiver engaged, split engaged and the difference in color > > between the two cursors, I guess I fail to understand whey there would > be a > > huge need for anything else - at least anything else relating to the > P3/K3 > > functionality that already exists. > > > > I think any reasonable operator would only accidentally operate on the DX > > frequency once or twice before it became a habit to engage SPLIT and then > > "split" your xmit frequency. If a given op consistently makes the same > > mistake of NOT operating split, a bunch of ugly descriptives come to > mind! > > > > Art - N4PJ > > > > > > > > On Fri, May 18, 2012 at 9:18 PM, k7hbg @dslextreme.com< > k7...@dslextreme.com > >> wrote: > > > >> Good thought Stewart! > >> > >> I had been thinking of this new feature for a while now but you gave > it > >> wings. > >> The frequency difference on the display between the cursor and the > >> marker(s) or, between the markers would be a most welcome addition > >> > >> Thanks and 73. Bob K7HBG > >> ______________________________________________________________ > >> 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 > >> > > ______________________________________________________________ > > 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 > > > ______________________________________________________________ > 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 > ______________________________________________________________ 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
