P3 recovery time after spot selection

[Mike K2MK]

Using WriteLog, I have noticed that it takes the P3 (in Fixed Tune mode) a full 3 seconds to recover after clicking on a spot. This happens consistently even if the spot is only a few KHz away from the present frequency. The K3 changes frequency instantly but the P3 first freezes, then the cursor jumps, then the screen shifts left or right, and then finally the P3 unfreezes and displays new data.

This situation does Not occur in Tracking Mode.

I was wondering if this is P3 related or WriteLog related. Anybody else seeing this in WriteLog or other programs?

73,
Mike K2MK

[Tony Estep]

On Sat, Jun 18, 2011 at 3:51 PM, Mike K2MK <[hidden email]> wrote:

> ...K3 changes frequency instantly but the P3 first freezes, then
> the cursor jumps....


Sounds like a polling issue. Does it happen with Writelog turned off? If
not, then maybe you can adjust the polling frequency in Writelog. Some
logging programs (e.g. HRD) follow very bad polling practices.

73,
Tony KT0NY
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

[Mike K2MK]

Hi Tony,

You are right on the money. I tried this with MixW and hitting a spot
results in an instantaneous P3 update whether the P3 is in Fixed Tune mode
or Tracking mode. This is very peculiar situation. I'll have to post it on
the WriteLog reflector.

73,
Mike K2MK

>Tony Estep
>Sat, 18 Jun 2011 14:06:46 -0700
>
>>On Sat, Jun 18, 2011 at 3:51 PM, Mike K2MK <[hidden email]> wrote:

>> ...K3 changes frequency instantly but the P3 first freezes, then
>> the cursor jumps....
>
>Sounds like a polling issue. Does it happen with Writelog turned off? If
>not, then maybe you can adjust the polling frequency in Writelog. Some
>logging programs (e.g. HRD) follow very bad polling practices.
>
>73,
>Tony KT0NY

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

[Tony Estep]

On Sat, Jun 18, 2011 at 6:14 PM, K2MK <[hidden email]> wrote:

> ...I tried this with MixW and hitting a spot results in an instantaneous P3
> update...


The main MixW guy is a true real-time and FFT software engineer. A lot of
his code is really superb. Still, even MixW suffers somewhat from the same
human-resource issue that afflicts most ham-related code.

Every project seems to grow to the point where it strains the capacity of
its developer right to the limit and in many cases beyond. All those goodies
that we get with consumer products, are a pretty big stretch for the typical
one-man show, or small team of guys, working part-time for love more than
money. Nowadays, the available ham software includes drivers, virtual ports,
virtual audio channels, FFTs, interrupt-driven routines, forward error
correction, and a whole bunch of stuff that requires a far higher level of
expertise than was needed to write the simple apps we played with a decade
ago.

Maybe it all started with Peter Martinez, the guy who concocted PSK31.
Anyway, with respect to your specific question, it sounds like if you stick
with MixW then your P3 will update the way you  want it to.

73 & DX
Tony KT0NY
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html