I've noticed a couple of anomalies (problems, really), with the latest
(4.36) K3 firmware in combination with a KRC2 configured for AUXBUS
operation. If I remove power from the KRC-2 while it's connected to
the K3's ACC port (using a cable that I build, which has only the
AUXBUS and ground wires connected), the K3 locks up, hard - no front
panel control has any effect. When I power the KRC-2 back on, the K3
comes back to life, but now it thinks it has an active KPA500
connected (it doesn't) - i.e. there's a "*" after the "W" when I
adjust "PWR". The only way I've found to clear that is to "reboot" the
K3.
Curiously, I cannot reproduce either problem with a different K3 (also
running the 4.36 firmware). I have reproduced it with two different
KRC2s on the problem radio. The KRC2s work OK, in that they are able
to follow the K3's band-changes.
Is there a specification of the AUXBUS protocol somewhere? How,
exactly, does the K3 "know" when an active KPA500 is connected?
Based on the above, I'm a bit dubious of trusting the AUXBUS method of
ensuring appropriate drive level from the K3 for the KPA500.
Does anyone else have a KRC2 configured for AUXBUS connected to a K3
with the latest firmware? Does anyone have that *and* a KPA500
connected to the AUXBUS at the same time? Does it work? I haven't
built the cable for the KPA500 yet...
~iain / N6ML
______________________________________________________________
Elecraft mailing list
Home:
http://mailman.qth.net/mailman/listinfo/elecraftHelp:
http://mailman.qth.net/mmfaq.htmPost: mailto:
[hidden email]
This list hosted by:
http://www.qsl.netPlease help support this email list:
http://www.qsl.net/donate.html
Locked
