KAT500 and KPA500 integration

[ANDY DURBIN]

My KPA500 receives serial data (listen only) from my TS-590 and follows TS-590 band changes without needing RF input.   If I connect the KPA500 and KAT500 with an AUX cable will the KAT500 be selected to the same band as the KPA500 before receiving RF input? If so, what minimum pin connection set is required?


Asked another way - Is a K3 required for the AUX bus to have any functionality?


Thanks and 73,

Andy k3wyc
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

[Jack Brindle-2]

To the last question - Yes. The KAT500 and KPA500 do not communicate through the AUX bus. Further, KAT500 is listen only, KPA500 is talk only, and KAT500 cannot listen to the KPA500 data.

Jack, W6FB

> On Jun 21, 2018, at 6:19 AM, ANDY DURBIN <[hidden email]> wrote:
>
> My KPA500 receives serial data (listen only) from my TS-590 and follows TS-590 band changes without needing RF input.   If I connect the KPA500 and KAT500 with an AUX cable will the KAT500 be selected to the same band as the KPA500 before receiving RF input? If so, what minimum pin connection set is required?
>
>
> Asked another way - Is a K3 required for the AUX bus to have any functionality?
>
>
> Thanks and 73,
>
> Andy k3wyc
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [hidden email]

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

[David Shoaf]

Hi Andy,

The short answer is that neither the KPA500 or KAT500 can source signals -
they can only read them from a transceiver and then follow its direction.  
This means that they can both read the status information from a Kenwood's
COM port and act on it.

This does not require the AUX cables which are specifically designed for the
K3/K3S to provide the unique features they have when connected in that way.
This would include the ability of the KAT500 to read the K3/K3S VFO
frequency and pre-select tuning elements, band-tracking with the K3/K3S and
the KPA500's ability to report its OPER/STBY status to the K3/K3S so it can
switch between the 2 RF PWR settings it maintains on a per-band basis.

Cheers,

David/KG6IRW



--
Sent from: http://elecraft.365791.n2.nabble.com/
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

[ANDY DURBIN]

"The short answer is that neither the KPA500 or KAT500 can source signals - they can only read them from a transceiver and then follow its direction. This means that they can both read the status information from a Kenwood's COM port and act on it."


Now I'm getting confused. Based on earlier replies (list and off list) I understood that the KPA500 was the source of the single wire Aux bus and that both the KPA500 and KAT500 were listeners for the band discretes.


How would the KAT500 receive frequency data from the Kenwood COM port? The KPA500 can be configured to do that, and mine is, but I see no way for the KAT500 to do that. There is no RS-232 transceiver port on the KAT500 and the RS-232 PC port appears to be usable only to exchange the KAT500 command set with a device that communicates using that command set. In my case the KAT500 PC port will be used to communicate with my station data logger.


Perhaps its only of academic interest but I do like to have some understanding of the equipment I operate.


73,

Andy k3wyc
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

[Wes Stewart-2]

That make no sense to me.

On 6/21/2018 6:54 AM, Jack Brindle wrote:
> To the last question - Yes. The KAT500 and KPA500 do not communicate through the AUX bus. Further, KAT500 is listen only, KPA500 is talk only, and KAT500 cannot listen to the KPA500 data.
>
> Jack, W6FB
>

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

[ANDY DURBIN]

It's clear that both the KPA500 and KAT500 must be RS-232 transmitters as well as RS-232 receivers. If that were not true then the PC utilities could not function. My station data logger has been polling, and receiving responses from, my KPA500 since I first built it.


Now I know that the KAT500 will receive and process the Kenwood command set I think I can see how to implement a band control interface and still be able to receive KPA500 and KAT500 status with my logger.


What is still not clear to me is how the KAT500 uses the single line AUX bus. The KAT500 schematic shows the AUX bus is received as "AUXB" and not just passed from input connector to output connector.


Thanks to all who contributed to the discussion so far.


73,

Andy k3wyc
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

[Don Wilhelm]

Andy and all,

Perhaps the confusion is coming from the similarity of names.
The "AUXBUS" is a proprietary single wire communicaions interface that
is used for communications between various units in the Elecraft gear -
if for no other reason than to test for the presence of a particular device.

The fact that the cable between the K3 and the KAT500/KPA500 is called
the "AUX cable" - it is NOT the AUXBUS even though one of the wires is
for the AUXBUS.

That is quite different and separate from any RS-232 communications.
There are no RS-232 signals in the AUX cable.

73,
Don W3FPR

On 6/21/2018 1:25 PM, ANDY DURBIN wrote:
> It's clear that both the KPA500 and KAT500 must be RS-232 transmitters as well as RS-232 receivers. If that were not true then the PC utilities could not function. My station data logger has been polling, and receiving responses from, my KPA500 since I first built it.
>
>
> Now I know that the KAT500 will receive and process the Kenwood command set I think I can see how to implement a band control interface and still be able to receive KPA500 and KAT500 status with my logger.
>
>
> What is still not clear to me is how the KAT500 uses the single line AUX bus. The KAT500 schematic shows the AUX bus is received as "AUXB" and not just passed from input connector to output connector.
>
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]