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 Vic Rosenthal 4X6GP/K2VCO wrote > Right, but I conclusively proved that this is not the (only?) cause by > reproducing the bug without any applications running on my computer that > access the K3. > > On 29 Dec 2014 22:58, Joe Subich, W4TV wrote: >> >>> It only happens here when the logging program (N1MM+) is active, >>> which suggests it is related to traffic on the RS232 link - perhaps >>> some kind of data collision which is being resolved by timeouts. >> >> N1MM Logger (both Classic and Plus) is extremely aggressive in its >> polling - something like 7 or 9 "GET" items - including FA; FB; and IF; >> all at once every 300 ms. Add a second polling source - e.g. the P3 - >> and the chance of collision, timeout, and/or buffer overflow gets >> fairly substantial rather quickly. >> >> 73, >> >> ... Joe, W4TV -- View this message in context: http://elecraft.365791.n2.nabble.com/P3-bug-tp7596500p7596508.html Sent from the Elecraft mailing list archive at Nabble.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
