Hi,
I think part of the problem is that HRD's author purchased an early K3,
soured rather quickly on it and sold it again before many early firmware
shortcomings in the serial communications area were ironed out. Hopefully
the new owners of HRD will add full support for the current state of the
That's a pretty fair analysis Knut I think. I listened to a lecture by
Simon of HRD fame yesterday morning (at the RSGB Convention) and it's very
clear that Simon, by his own admission, much prefers the computer controlled
big screen route and abhors multifunction buttons on transceivers such as
On Sun, Oct 9, 2011 at 2:45 PM, Stephen Prior eastbrantw...@gmail.comwrote:
the more advanced RFSpace
offerings will give the K3 a good run for its money in receive performance
terms, but from my perspective, I'm afraid it's got to have knobs on!
It's been observed by many on
All,
After building and installing a new P3 pan adapter on a relatively new K3, I
notice the AGC fast or slow setting would suddenly shut off, accompanied by
a loud, distorted blast of signal audio. Normal AGC function is
re-established by holding the AGC button, then tapping to select fast or
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
Dan,
As David indicated, this is caused by HRD. Nothing wrong in the K3 or
P3 at all.
73,
Don W3FPR
On 10/8/2011 4:51 AM, Dan Sherwood wrote:
All,
After building and installing a new P3 pan adapter on a relatively new K3, I
notice the AGC fast or slow setting would suddenly shut off,
At the time, the P3 was also connected to a PC running HRD v5.0. No
specific commands issued to HRD at the times of the AGC pop-off. I
was not transmitting at the time it occurred either, (RF not an
issue).
As indicated by others, this is an issue with overpolling by HRD. HRD
enables the
Joe,
That's certainly a plausible explanation. We ran MM logger all last weekend
during the CQP without problems, (P3 not built yet). I had no issue with
HRD earlier yesterday, until later at night when I switched to 40 and 80
meters looking for few signals through heavy static crashes. With
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
N5NA
--
Message: 39
Date: Sat, 08 Oct 2011 10:11:21 +0100
From: David Honeyda...@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
: [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
I'm not a programmer nor do I play one on TV. I'm just an observer.
Why should polling the AGC randomly turn it off on the K3? None of the
other parameters that are polled at the same frequency are adversely
affected, only the AGC.
AGC should be able to be polled without it turning off.
Why should polling the AGC randomly turn it off on the K3?
Because HRD uses the *K22* mode. If HRD would use the K3 commands
and not enable the K2 extended command set, the GT command would
require an explicit off command.
What appears to happen is a data clash between HRD and the P3 ...
P3
13 matches
Mail list logo
