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 K3 firmware.
AB2TC - Knut Joe Subich, W4TV-4 wrote: > >> 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 data or an echo gets appended to the the GT; poll to the K3. > The the corrupted data is "just right" AGC is turned off. > > Why does HRD use an old command set and why does it poll for AGC > status *THREE TIMES*? Polling for the same data three times in > 31 milliseconds is stupid, sloppy, and increases the chance of > false triggering exponentially. > > 73, > > ... Joe, W4TV > > <snip> > -- View this message in context: http://elecraft.365791.n2.nabble.com/Sudden-K3-AGC-pop-off-after-adding-P3-tp6872073p6875045.html Sent from the Elecraft mailing list archive at Nabble.com. ______________________________________________________________ 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
