Hi,

I have seen this behavior with the SVGA as well. However, 1 or 2 seconds before the P3 returns is not the same issue that I believe most people are talking about. When I have had this issue the spectrum locks up and will not return until a subsequent transmit. The communications between the P3 and K3 will most likely take a bit of time when the transmission is finished. One to two seconds is probably the norm and I would think that this is normal behavior. Since the P3 and K3 use the same serial link, I would think that a faster response would be bad for other third party applications. In my opinion although I do not know for sure, I believe that what is happening is that the command issued to determine if the K3 is transmitting is very slow to receive a response. I have seen this in my software. Perhaps this combined with some code that needs a little additional work for the P3 / K3 communications might solve the issue.

73's Tom
va2fsq.com

-----Original Message----- From: Mike K2MK
Sent: Monday, December 29, 2014 4:40 PM
To: elecraft@mailman.qth.net
Subject: Re: [Elecraft] P3 bug

I also have just proved conclusively that it has nothing to do with RF and
nothing to do with a PC application. I tested the P3 with SVGA with my K3 in
test mode on 15 meter CW. Using the internal keyer and my paddle with QSK
turned on I sent the letter K at 25 WPM and paused. After 5 repeats the P3
hung up for about 1 second. Continuing I sent the letter K about 10 times
and the P3 hung on the 10th repeat for about 2 seconds.

This is a true problem. More of you should run this test.

73,
Mike K2MK



---
This email is free from viruses and malware because avast! Antivirus protection 
is active.
http://www.avast.com

______________________________________________________________
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
Message delivered to arch...@mail-archive.com

Reply via email to