http://elecraft.85.s1.nabble.com/Sudden-K3-AGC-pop-off-after-adding-P3-tp6872073p6873071.html
I'm not a programmer nor do I play one on TV. I'm just an observer.
affected, only the AGC.
AGC should be able to be polled without it turning off.
> 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 <
[hidden email]
> <mailto:
[hidden email]>> 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
>