Duane,
You are describing the kind of things that go well with a control program.
My N4PY Orion control program allows you to define a remote pod key for
"Up". To do what you describe, all you do is press the "Up" key followed by
the "5" key. This will make VFO B be VFO A + 5 khz and make VFO B be the
transmit VFO. Now, if you wish to listen to both sides of the DX pile, you
can press the key you have defined as "DUAL" on the remote pod. This "DUAL"
button will toggle the VFO B receiver off and on. I find this is a great
way to work through split DX pileups.
73,
Carl Moreschi N4PY
Franklinton, NC
----- Original Message -----
From: "Duane A Calvin" <ac5aa@juno.com>
To: <tentec@contesting.com>
Sent: Thursday, July 08, 2004 7:46 PM
Subject: Re: [TenTec] An example of changing Orion firmware to
meetexpectations of the operator.
> I appreciate the design point of having two receivers, not two VFO's, and
> the potential flexibility that this provides us as users. This does
> bring up the difficulty of how to manage the added complexity. For
> example, as a DX'er, the thing I need in a rig to have an edge when the
> DX suddenly says "up 5" is the ability to be there and be the first guy
> he works there. With my Omni VI+, that meant punching in XIT and dialing
> up 5 - very easy and fast. With the Orion, however, if I want to make
> use of the 2nd RX for listening to the pile, it's more of a problem. I
> punch A>B, then I have to remember to set TX to B, then I dial up 5 on
> the B VFO/receiver. Hopefully the mode, PBT and BW follow since I'll
> also be listening on B to see where I am in the pileup (after all, it had
> been set to a shortware AM broadcast station).
>
> I'd like to see a "quick split" function that is definable by the user to
> do multiple things (perhaps activated by a 'long push' on the A>B
> button). It might do the following:
>
> - Copy A settings to B (user selectable as to which additional
> settings besides freq/mode)
> - Set TX to B
> - Optionally reset the headphone audio to a user defined
> preference
>
> There could be a complementary function that works the other way -
> copying from B>A on a long push and doing all the same functions but in
> the other order (TX to A, etc.)
>
> What's important is how it will be used, and how to implement in a way
> that brings an advantage to the user.
>
> 73, Duane
>
>
> On Thu, 08 Jul 2004 09:19:49 -0500 "Grant Youngman" <nq5t@comcast.net>
> writes:
> > > -- VFO's are not receivers --
> >
> I suspect that not everyone buys into the traditionalist
> > view of
> > what switching VFOs ... uh .. receivers ... uh .. VFOs? what? I'm
> >
> > confused just thinking about it. :-)
> >
> > (It was good the way it was)
> >
> > Grant/NQ5T
> >
> > _______________________________________________
> > TenTec mailing list
> > TenTec@contesting.com
> > http://lists.contesting.com/mailman/listinfo/tentec
> >
> >
>
>
> Duane Calvin, AC5AA
> Austin, Texas
> _______________________________________________
> TenTec mailing list
> TenTec@contesting.com
> http://lists.contesting.com/mailman/listinfo/tentec
_______________________________________________
TenTec mailing list
TenTec@contesting.com
http://lists.contesting.com/mailman/listinfo/tentec
|