[Elecraft] P3 Question

[Joe Subich, W4TV]

 > To me it seems more logical to report to the outside world the
 > displayed frequency, not some internal portion of that frequency.

The K3 (along with Kenwood and recent Yaesu rigs) report the current
VFO frequency and RIT in the IF command.  It also reports each VFO
(FA, FB), RIT (RO) and XIT (XO) on demand.  A well written logging
program will be able to log the correct frequency with that data.

Relying on "display" data would require the logging software to play
games to read the display during both transmit and receive.  In some
cases - with some transceivers - polling during transmit can result
in problems.  It is better to report the "pieces" on demand and allow
the logging software to use them as needed.

73,

    ... Joe, W4TV

On 2/25/2011 1:16 PM, Wes Stewart wrote:
> Inline posting for consistency...
>
> --- On Fri, 2/25/11, Joe Subich, W4TV<lists at subich.com>  wrote:
>
>> From: Joe Subich, W4TV<lists at subich.com> Subject: Re: [Elecraft] P3
>> Question To: "Wes Stewart"<n7ws at yahoo.com> Cc: "Elecraft
>> Reflector"<elecraft at mailman.qth.net> Date: Friday, February 25,
>> 2011, 9:39 AM
>>
>>
>>> The foregoing probably answers my own question which
>> is this: will
>>> the P3 markers/cursors that show the A and B VFO
>> frequencies account
>>> for the case of both RIT and XIT being engaged at the
>> same time?
>>
>> Since the P3 does not operate in transmit, XIT is a moot point but
>> both the cursor and "current frequency" show the effect of RIT.
>
> Fair enough.
>
>>
>>> A related question is why doesn't the K3 just report
>> the actual
>>> displayed frequency when queried?
>>
>> Because the displayed frequency is the VFO Frequency +/- RIT and
>> RIT is reported in the IF "broadcast" or in response to RO.  It
>> would be difficult for many computer applications if the "VFO"
>> frequencies were jumping around between transmit and receive.
>
> Well, if I do use split, my logging program (DXBase) has no problem
> logging both my (different) TX and RX frequencies.  But it does not
> log correctly if I'm using XIT, even though the displayed TX
> frequency might be the same in both cases.
>
> If for example, I set my A VFO to 14.010 and set RIT/XIT to +1 KHz,
> and turn both on, the K3 will now display the frequency as 14.011.
> To me that is the new "A" frequency, but it will still be reported as
> 14.010 via the interface.
>
> To me it seems more logical to report to the outside world the
> displayed frequency, not some internal portion of that frequency.
>
> Regards,
>
> Wes
>
>>
>> 73,
>>
>> ... Joe, W4TV
>>
>>
>> On 2/25/2011 11:05 AM, Wes Stewart wrote:
>>> When working DX stations that are operating split I
>> much prefer to
>>> use the transmit offset (XIT) function rather than
>> using the
>>> "Split/A/B" method.  This puts all of the needed
>> controls together.
>>>
>>> Using my current panadapter setup, an SDR-IQ +
>> SpectraVue, if I want
>>> to see where my transmitter is with respect to QRM, I
>> just tap the
>>> RIT button to engage both RIT and XIT and the center
>> of the display
>>> now shows my TX freq with respect to other
>> signals.  Unfortunately,
>>> the K3 doesn't report the actual displayed frequency
>> via the "FA"
>>> command, which I assume is what SpectraVue uses, so
>> the spectrum
>>> display frequency axis still shows the non-shifted
>> frequency.
>>>
>>> The foregoing probably answers my own question which
>> is this: will
>>> the P3 markers/cursors that show the A and B VFO
>> frequencies account
>>> for the case of both RIT and XIT being engaged at the
>> same time?
>>>
>>> A related question is why doesn't the K3 just report
>> the actual
>>> displayed frequency when queried?
>>>
>>> Wes  N7WS
>>>
>>>
>>>
>>>
>> ______________________________________________________________
>>> Elecraft mailing list Home:
>>> http://mailman.qth.net/mailman/listinfo/elecraft Help:
>>> http://mailman.qth.net/mmfaq.htm Post:
>>> mailto:Elecraft at mailman.qth.net
>>>
>>> This list hosted by: http://www.qsl.net Please help support
>> this
>>> email list: http://www.qsl.net/donate.html
>>>
>>
>
>
>
>