The real deal would be why the over-polling is necessary in the first place. I'd guess it's done to service ALL the different rig types (not just Elecraft and K3) with a single strip of code, instead of pushing those constants at program startup based on the target or configured hardware.
If it's not cheep code, then it's certainly not state of the art, nor at all close. One always should have a constants library which carries the array of values necessary to drive any hardware timing sensitive code. Where I worked at my last TWO places of employment, going back to an AT&T school in 1976 (!), embedding target-variable constants in program code and using code switches would get your code summarily rejected by a reviewer or auditor, subject one to an auditor approved redesign and recode (with prior effort flushed down the turlet), and have an effect on one's pay grade. There was a brutal "standards are just that" attitude. Putting in the table driven code costs some in the beginning, but saves huge in maintenance, and a maze of switches eventually means recoding in its entirety. That's probably what we're really fighting with the HRD code. Otherwise it's a simple table change that gets done in seconds, and then recompiled. 73, Guy. On Sat, Oct 8, 2011 at 12:31 PM, Alan Sewell N5NA <alan.n...@gmail.com>wrote: > This is a problem not only for HRD but any software in which the AGC > status is polled continuously. I frequently use CQ/X by NO5W and had > the same problem. Chuck turned off the AGC polling in CQ/X and the > problem no longer occurs. Of course, now the AGC status can't be shown > in his remote interface. > > I sent Wayne, N6KR, a couple of log files from portmon back in July > showing what was happening but so far I haven't seen any updates on this. > > 73, Alan N5NA > > > ------------------------------ > > > > Message: 39 > > Date: Sat, 08 Oct 2011 10:11:21 +0100 > > From: David Honey<da...@honeyfamily.org.uk> > > Subject: Re: [Elecraft] Sudden K3 AGC pop-off after adding P3 > > To:elecraft@mailman.qth.net > > Message-ID:<4e9013b9.6000...@honeyfamily.org.uk> > > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > > Dan, > > > > This is a known issue with HRD used with the K3. It happens with me a > > few times a week with my K3+P3. Reducing the polling rate of the K3 in > > HRD may reduce the frequency of this issue, but it won't eliminate it. > > The choice seems to be either put up it, or stop using HRD. Simon Brown > > has handed over the reins of HRD development, so perhaps the new team > > can devote some time to investigating and fixing this. > > > > vy 73 de David M0DHO > > > > > > ------------------------------ > > ______________________________________________________________ > 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 > ______________________________________________________________ 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
