P3 Problem

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

P3 Problem

Larry Burke
I am using a P3 with the SVGA option. It is connected to a K3. I find that
frequently after transmitting -- particularly calling a DX station in a
split-frequency pileup -- the P3 display comes back sluggish or almost
frozen for up to 20 seconds or so. Then it returns to providing real-time
information. It's almost like the P3 is suffering from data overload,
finally processes it, and gets back to normal.

 

This is particularly annoying as one cannot spot where the DX is listening
in said pileup because the screen is essentially frozen and does not display
stations real-time until it "unfreezes". This happens regardless of mode
(CW, SSB or RTTY). In RTTY this "freeze time" also locks up the USB
keyboard.


The problem does not appear to be RFI related, as I get it regardless of the
power output level.

 

Any idea what's going on?

 

 

Larry K5RK

______________________________________________________________
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
Reply | Threaded
Open this post in threaded view
|

Re: P3 Problem

Stephen G4SJP
I get that too, but usually just for 2 or 3 seconds and sometimes not at
all.  I have never got my head around it, but I think it got worse after
fitting the SVGA board.  That leads me to another 'feature', in that the
SVGA screen will occasionally do a complete refresh of the waterfall,
without me touching anything else such as the VFO.  It's as if a buffer
which is much bigger than the screen data is being flushed, leaving no
history in the waterfall at all.

I can't imagine myself being without the P3 now, however!

73 Stephen G4SJP


On 4 December 2013 02:20, Larry Burke <[hidden email]> wrote:

> I am using a P3 with the SVGA option. It is connected to a K3. I find that
> frequently after transmitting -- particularly calling a DX station in a
> split-frequency pileup -- the P3 display comes back sluggish or almost
> frozen for up to 20 seconds or so. Then it returns to providing real-time
> information. It's almost like the P3 is suffering from data overload,
> finally processes it, and gets back to normal.
>
>
>
> This is particularly annoying as one cannot spot where the DX is listening
> in said pileup because the screen is essentially frozen and does not
> display
> stations real-time until it "unfreezes". This happens regardless of mode
> (CW, SSB or RTTY). In RTTY this "freeze time" also locks up the USB
> keyboard.
>
>
> The problem does not appear to be RFI related, as I get it regardless of
> the
> power output level.
>
>
>
> Any idea what's going on?
>
>
>
>
>
> Larry K5RK
>
> ______________________________________________________________
> 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
>
______________________________________________________________
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
Reply | Threaded
Open this post in threaded view
|

Re: P3 Problem

Paul Saffren N6HZ
In reply to this post by Larry Burke
Hi Larry,

It sounds like the SVGA is not seeing that the K3 has stopped transmitting and has gone into receive.  Here are some suggestions:

1) Make sure both the SVGA and P3 are running latest firmware.  P3 1.26  SVGA 1.16
2) Ensure that the serial cable going between the K3 and P3 is good and screwed in tight.
3) If you are using a 3rd party logging program that is connected to the K3, try closing it down to see if there is an interaction that may be causing the problem.  
4) If after all the above doesn't solve it, email me directly Larry.  My email is pauls ....at.... elecraft

73,

Paul