[Elecraft] K3/KPA500/KAT500 revs 4.83/1.38/1.58

bill conkling nr4c at widomaker.com
Fri Feb 21 21:46:37 EST 2014


It's plugged into the same PS as the K3.

...bill

Sent from my Verizon Wireless 4G LTE DROID

Jack Brindle <jackbrindle at me.com> wrote:

>You might want to say how you have the KAT powered. In my station I have a relay-switch power panel that I built. The relay is powered by the K3’s 12V output jack. When the K3 turns on, it powers the relay, which the switches 12V power to the various station boxes, including the KAT500. By the time the K3 is ready to talk to the KAT, it is awake and listening, as is the KRC2, P3, etc...
>
>
>Jack B, W6FB
>
>
>On Feb 21, 2014, at 5:44 PM, bill conkling <nr4c at widomaker.com> wrote:
>
>
>Sounds great but most of the time my KAT500 won't turn on until I turn on the K3.
>
>
>What now?
>
>
>...bill nr4c
>
>
>Sent from my Verizon Wireless 4G LTE DROID
>
>
>
>Jack Brindle <jackbrindle at me.com> wrote:
>
>The KAT500 needs to be powered on whenever the K3 is on in order to avoid loading the Auxbus. It can be powered up at the same time, but must be on before the K3 completes its initialization.
>
>The KPA500 has no restriction, and can be powered on any time before or after the K3 is turned on.
>
>Jack Brindle, W6FB
>
>On Feb 21, 2014, at 2:23 AM, Stephen Prior <eastbrantwood at gmail.com> wrote:
>
>> Chuck,
>> 
>> I seem to remember reading that the order of turning on the K-line is
>> important.  I always turn on the KAT500, then the KPA500 followed by the
>> K3/P3.  I have not had any issues doing things in that order.  Maybe this
>> is why you had the 'problem'?
>> 
>> 73 Stephen G4SJP
>> 
>> 
>> On 21 February 2014 10:19, ke9uw <c-hawley at illinois.edu> wrote:
>> 
>>> Oh yes, I remember now yesterday I got a soft fault on the KPA500. I turned
>>> on the K3, the KAT500 went to the pretuned setting on 40M and then I turned
>>> on the KPA500 and clicked it into operate.
>>> I said one word and the KPA500 went to standby. No red lights. I returned
>>> it to operate and everything worked well. Forgot about that...not a
>>> problem,
>>> but don't know why it did that.
>>> 
>>> 
>>> 
>>> -----
>>> Chuck, KE9UW
>>> --
>>> View this message in context:
>>> http://elecraft.365791.n2.nabble.com/K3-KPA500-KAT500-revs-4-83-1-38-1-58-tp7584490p7584507.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 at mailman.qth.net
>>> 
>>> This list hosted by: http://www.qsl.net
>>> Please help support this email list: http://www.qsl.net/donate.html
>>> 
>> ______________________________________________________________
>> 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
>
>______________________________________________________________
>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
>
>


More information about the Elecraft mailing list