[Elecraft] AGC Problem

[David Herring]

I don't run windows or HRD in the shack anymore, but I just checked my notes, and you can change the polling rate and timeout in HRD.  Bring up HRD, go in to Options. Once there, click on the "Comms" tab. Once there, look around...there is "Polling Timeout" and "Refresh Interval" which may be adjusted to make HRD a little more neighborly.  I think it defaulted to something like 500 milliseconds maybe, and I think I set mine to 1000 milliseconds (1 second) and it helped.  The polling timeout might help the P3 users as well.

HTH.

73 & Aloha,

Dave, AH6TD


On Jun 19, 2011, at 7:46 AM, Joe Subich, W4TV wrote:

> 
>> Agree - but since it got much worse after installing ver. 1.08 it
>> looks to me as there might be a timing issue in P3 firmware.
> 
> It is still a timing issue in HRD ... HRD gets "p***ed off" when it
> does not get an instant reply to its polls.  Watch the data with a
> port snooping tool and you will see a regular set of polls with the
> same data requested, three or even four times in succession with the
> "retry" the very instant the K3 responds to the first (or second, etc.)
> poll for the same data.  HRD insists on changing the command protocol
> (K30 -> K31 and back) on a regular basis and polls for a large amount
> of "excess" data (firmware versions, option levels, etc. that does
> not change during operation) every couple of seconds.
> 
> Frankly it is a miracle that the P3/K3 combination can cope with
> so much programmatic abuse.
> 
>> I'm sure Simon Brown (mr HRD) will do what he can to address this
>> issue, but he dont have a P3 in his shack.
> 
> AFAIK, he doesn't have a K3 any more either.  In any case, it does
> not take a P3 to fix the basic polling issues responsible for this
> problem.
> 
> 73,
> 
>    ... Joe, W4TV
> 
> 
> On 6/19/2011 12:28 PM, Jens Petersen wrote:
>> On Sun, 19 Jun 2011 11:14:37 -0400, you wrote:
>> 
>>> Just to note firmly that this is not a problem with the K3.  Radio
>>> firmware cannot be expected to provide workarounds for any and all
>>> programming mistakes in third party software.
>> 
>> Agree - but since it got much worse after installing ver. 1.08 it
>> looks to me as there might be a timing issue in P3 firmware.
>> 
>>> We have to make sure that we do not misplace the source of the
>>> trouble, and dump our complaints on the innocent party just because
>>> they may be more available or visible.
>>> 
>>> HRD has a problem on this one.  It will not do to say that K3 should
>>> be "immune".  The conversation should move to HRD's venue.
>> 
>> I'm sure Simon Brown (mr HRD) will do what he can to address this
>> issue, but he dont have a P3 in his shack.
>> 
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at mailman.qth.net
> 
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html