SO2R Antenna/Band Information

[Matthew Cook]

I'm currently trying to get my head around where to get antenna band
information for a K-line SO2R setup using a Microham MK2R+.

I believe I can pick up band information useful for making antenna
selections from the following two locations;

   - back of the Microham MK2R+... or
   - from the 15-pin ACC (between K3 and KPA500 via Y-Cable)

I'm wondering if there are any pitfalls or hidden gotchya's in either of
these two locations.

To me it seems more sensible to slave the antenna section to the KPA500's
since it knows where it will be transmitting when PTT is engaged; where as
the back of the Microham MK2R+ is where "it thinks" or "has told" the radio
and amp should be...   Logically the same but time differences or local
user input can make the two different.

Any suggestions or guidance gratefully appreciated.

The Microham MK2R+ that arrived today certainly has a steep learning curve !

73

Matthew
VK5ZM
______________________________________________________________
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]

[Joe Subich, W4TV-4]

On 5/25/2017 3:22 AM, Matthew Cook wrote:
> I'm wondering if there are any pitfalls or hidden gotchya's in either
> of these two locations.

No.  Each will require a binary (BCD) to one of 16 (10) decoder to drive
"one line per antenna" switches.  The K3 will provide encoded band info,
the MK2R+ can provide either encoded band info or encoded antenna info
depending on data source.

MK2R+ can derive data from transceiver frequency with a customizable
band table (Router | Options | Band Map) that would allow one to
define separate "bands" - for example 80 and 75 meters - or can derive
either band or antenna based on the SO2R protocol commands generated by
the logging software.  The choice is made on the ACC tab in Router
(assignments for pins 6-9 and pins 10-13) as well as in the way the
logging software is configured.

Using the "Band Data" from the K3 is probably more simple while using
MK2R+ is more flexible.

> Logically the same but time differences or local user input can make
> the two different.

There is no time difference with CAT derived band data.  The logger
command driven antenna select data is sent when the loggers change
transmit focus, when the user selects an alternate antenna from the
logger, or the logger senses a manual band change on either transceiver
(bad idea - get used to changing bands from your software).  In any
case, any antenna/band changes should be sensed long before the logger
initiates any transmission.

73,

    ... Joe, W4TV


On 5/25/2017 3:22 AM, Matthew Cook wrote:

> I'm currently trying to get my head around where to get antenna band
> information for a K-line SO2R setup using a Microham MK2R+.
>
> I believe I can pick up band information useful for making antenna
> selections from the following two locations;
>
>     - back of the Microham MK2R+... or
>     - from the 15-pin ACC (between K3 and KPA500 via Y-Cable)
>
> I'm wondering if there are any pitfalls or hidden gotchya's in either of
> these two locations.
>
> To me it seems more sensible to slave the antenna section to the KPA500's
> since it knows where it will be transmitting when PTT is engaged; where as
> the back of the Microham MK2R+ is where "it thinks" or "has told" the radio
> and amp should be...   Logically the same but time differences or local
> user input can make the two different.
>
> Any suggestions or guidance gratefully appreciated.
>
> The Microham MK2R+ that arrived today certainly has a steep learning curve !
>
> 73
>
> Matthew
> VK5ZM
> ______________________________________________________________
> 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]

[Matthew Cook]

Thanks to everyone that emailed me with responses, this learning curve for
SO2R is steep !

73

Matthew
VK5ZM

On 25 May 2017 at 16:52, Matthew Cook <[hidden email]> wrote:

> I'm currently trying to get my head around where to get antenna band
> information for a K-line SO2R setup using a Microham MK2R+.
>
> I believe I can pick up band information useful for making antenna
> selections from the following two locations;
>
>    - back of the Microham MK2R+... or
>    - from the 15-pin ACC (between K3 and KPA500 via Y-Cable)
>
> I'm wondering if there are any pitfalls or hidden gotchya's in either of
> these two locations.
>
> To me it seems more sensible to slave the antenna section to the KPA500's
> since it knows where it will be transmitting when PTT is engaged; where as
> the back of the Microham MK2R+ is where "it thinks" or "has told" the radio
> and amp should be...   Logically the same but time differences or local
> user input can make the two different.
>
> Any suggestions or guidance gratefully appreciated.
>
> The Microham MK2R+ that arrived today certainly has a steep learning curve
> !
>
> 73
>
> Matthew
> VK5ZM
>

______________________________________________________________
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]