Wayne and I are working on a method to reduce the communications latency when the P3 is in the loop. Hopefully I'll have some new beta firmware soon to try it out.
Meanwhile, you might try increasing the refresh interval in HRD. One customer said he was having problems with a short refresh time and the problems went away when he returned it to the default 300 ms. In HRD, click on Options, then the Comms tab. Refresh Interval is in the lower right. Alan N1AL On Tue, 2010-08-24 at 12:29 -0700, Wayne Burdick wrote: > We're making improvements at the P3 end to ensure there's no > significant command latency. We don't feel that PC applications should > have to make adjustments to accommodate the P3. > > There are a lot more P3's out there, now, running in conjunction with > many more third-party applications, so we're getting plenty of useful > feedback :) > > 73, > Wayne > N6KR > > On Aug 24, 2010, at 11:50 AM, Guy Olinger K2AV wrote: > > > The most obvious techno-lurch suspicion is that, predictably and most > > likely necessarily, the P3 introduced a timing delay in the response > > to the commands.... > > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[email protected] > > 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:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
