[Elecraft] Unterminated PR6, was RE: PR6 Clarification
Cady, Fred
fcady at ece.montana.edu
Tue Apr 16 14:01:07 EDT 2013
The conditions are:
The PR6 is powered-on (say an external supply or the K3's 12v output) AND you are not on 6 m AND DIGOUT1 is low (if, say, you are using it to disable the KPA500 on some - maybe high swr and you don't want to run the amp) AND RX ANT is not selected.
When this is the case, DIGOUT1 switches the PR6 input to Preamp In and its output to Preamp Out, but without RX ANT selected the main antenna is not routed through the PR6. This leaves the PR6 input and output floating (unlike when DIGOUT1 is high when the input and output of the PR6 are terminated in 50 ohms).
So my question: Is that a problem for the PR6?
Cheers,
Fred
Fred Cady
fcady at ieee dot org
> -----Original Message-----
> From: dseven at dseven.org [mailto:dseven at dseven.org] On Behalf Of iain
> macdonnell - N6ML
> Sent: Tuesday, April 16, 2013 9:50 AM
> To: Cady, Fred
> Cc: Elecraft Reflector
> Subject: Re: [Elecraft] PR6 Clarification
>
> Hi Fred,
>
> I'm not sure I completely understand your question, but my PR6 is on
> all the time (it is not connected to the K3's ACC port), and I just
> use RX ANT on 6m to bring it in-line. This is not a problem for me,
> since I do not have any other RX ants that I need to feed through the
> PR6 for other bands. AFAIK, this is a "supported configuration".
>
> 73,
>
> ~iain / N6ML
>
>
> On Tue, Apr 16, 2013 at 7:44 AM, Cady, Fred <fcady at ece.montana.edu>
> wrote:
> > Hey, Ian (and others),
> > What do you think about having the PR6 powered-up and controlled-on
> with DIGOUT1 while on another band with RX ANT not enabled? It looks
> like the PR6 input and outputs are floating. Do you think that is a
> problem for the PR6?
> >
> > Fred
> >
> >
> > Fred Cady
> > fcady at ieee dot org
> >
> >> -----Original Message-----
> >> From: dseven at dseven.org [mailto:dseven at dseven.org] On Behalf Of iain
> >> macdonnell - N6ML
> >> Sent: Tuesday, April 16, 2013 7:55 AM
> >> To: Jim Miller
> >> Cc: Cady, Fred; Elecraft Reflector
> >> Subject: Re: [Elecraft] PR6 Clarification
> >>
> >> On Tue, Apr 16, 2013 at 5:31 AM, Jim Miller <jim at jtmiller.com>
> wrote:
> >> > It seems like it would be an easy thing to implement in the
> KPA500.
> >> Per
> >> > Band Standby.
> >>
> >> Good idea - why didn't I think of it? Oh, wait, I did :)
> >>
> >> http://elecraft.365791.n2.nabble.com/KPA500-feature-suggestion-band-
> >> bypass-td6247211.html
> >>
> >> Hasn't transpired so-far, though....
> >>
> >> 73,
> >>
> >> ~iain / N6ML
> >>
> >>
> >> > On Mon, Apr 15, 2013 at 11:18 PM, Cady, Fred
> <fcady at ece.montana.edu>
> >> wrote:
> >> >
> >> >> Hi Jim,****
> >> >>
> >> >> What I'd like to be able to do is to disable the amp on some
> bands
> >> (e.g.
> >> >> 30 m), by asserting (low) DIGOUT1 (and setting KPA500 INHIB IN
> to
> >> ENABLE)
> >> >> but to have the amp enabled for 6m when DIGOUT1 is low to turn on
> >> the PR6.
> >> >> I'm just lazy, that's all. Plus it's fun to think about!****
> >> >>
> >> >> Cheers,****
> >> >>
> >> >> Fred****
> >> >>
> >> >> ** **
> >> >>
> >> >> ** **
> >> >>
> >> >> Fred Cady
> >> >> fcady at ieee dot org ****
> >> >>
> >> >> *From:* jtmiller47 at gmail.com [mailto:jtmiller47 at gmail.com] *On
> >> Behalf Of *Jim
> >> >> Miller
> >> >> *Sent:* Monday, April 15, 2013 8:52 PM
> >> >> *To:* Cady, Fred
> >> >>
> >> >> *Cc:* Elecraft Reflector
> >> >> *Subject:* Re: [Elecraft] PR6 Clarification****
> >> >>
> >> >> ** **
> >> >>
> >> >> I'm not getting the importance of a Pin 11 solution. I just
> disable
> >> the
> >> >> KPA500 sensing of that pin by the menu selection. I don't see the
> >> need for
> >> >> it.****
> >> >>
> >> >> ****
> >> >>
> >> >> I'm definitely running the KPA500 on 6m.****
> >> >>
> >> >> ****
> >> >>
> >> >> If for some strange reason Pin 11 is asserted it just causes the
> >> KPA500 to
> >> >> be inhibited, not turned on, which is a failsafe direction.****
> >> >>
> >> >> ****
> >> >>
> >> >> 73****
> >> >>
> >> >> ****
> >> >>
> >> >> jim ab3cv****
> >> >>
> >> >> ** **
> >> >>
> >> >> On Mon, Apr 15, 2013 at 9:50 PM, Cady, Fred
> <fcady at ece.montana.edu>
> >> wrote:
> >> >> ****
> >> >>
> >> >> Ahh, looking back at my notes I see the other solution would be
> to
> >> make
> >> >> the KPA500 INHIBIT IN be per/band. But you would still have to
> take
> >> care of
> >> >> not turning on the PR6 when DIGOUT1 is low with some external
> logic
> >> if you
> >> >> cared about that.
> >> >>
> >> >> KE7X****
> >> >>
> >> >>
> >> >> Fred Cady
> >> >> fcady at ieee dot org****
> >> >>
> >> >> > -----Original Message-----
> >> >> > From: elecraft-bounces at mailman.qth.net [mailto:elecraft-****
> >> >>
> >> >> > bounces at mailman.qth.net] On Behalf Of Cady, Fred
> >> >> > Sent: Monday, April 15, 2013 7:42 PM
> >> >> > To: 'Elecraft Reflector'
> >> >> > Subject: Re: [Elecraft] PR6 Clarification
> >> >> >
> >> >> > K4RX's inhibit line inhibiter for pin 11 is the same idea as
> the
> >> >> > keyline inhibiter for pin 10. However, it is not really needed
> >> because
> >> >> > one can set the KPA500 INHIB IN menu to DISABLE so a low on pin
> 11
> >> will
> >> >> > not inhibit the amp accomplishing the same thing as pulling pin
> 11
> >> from
> >> >> > the connector. Of course pulling the pin is a fail-safe
> solution.
> >> What
> >> >> > is really needed is some logic that blocks pin 11 from the KPA
> for
> >> 6m
> >> >> > (assuming you want the amp on for 6) and passes it for the
> other
> >> bands.
> >> >> > That way you could inhibit the amp on, say, 30 m or other bands
> >> where
> >> >> > there might not be a good match. I worked up a circuit to do
> this
> >> once
> >> >> > upon a time and should dust it off again.
> >> >> > 73,
> >> >> > Fred
> >> >> >
> >> >> >
> >> >> > Fred Cady
> >> >> > fcady at ieee dot org
> >> >> > "The Elecraft K3: Design, Configuration, and Operation Second
> >> Edition"
> >> >> >
> >> >> > BTW, www.Lulu.com has a 20% discount (APRILBOOKS13) good this
> >> month and
> >> >> > 15% off (POURING) until April 19th.
> >> >> >
> >> >> > > -----Original Message-----
> >> >> > > From: elecraft-bounces at mailman.qth.net [mailto:elecraft-
> >> >> > > bounces at mailman.qth.net] On Behalf Of Jim Miller
> >> >> > > Sent: Monday, April 15, 2013 7:25 PM
> >> >> > > To: Terry Posey
> >> >> > > Cc: Elecraft Reflector
> >> >> > > Subject: Re: [Elecraft] PR6 Clarification
> >> >> > >
> >> >> > > I believe the Key line interrupter interrupts pin 10 rather
> than
> >> pin
> >> >> > 11
> >> >> > > after reviewing the K3 and KPA manual. I don't use the Pin 11
> >> option
> >> >> > on
> >> >> > > the
> >> >> > > KPA (it's disabled) rather use the keyline interrupter and
> RCA
> >> jack
> >> >> > > cabling
> >> >> > > to interface all the keying interruption which includes my
> >> antenna
> >> >> > > switch.
> >> >> > >
> >> >> > > Thanks for your concern and don't hesitate to correct me if
> I've
> >> made
> >> >> > > an
> >> >> > > incorrect assessment.
> >> >> > >
> >> >> > > 73
> >> >> > >
> >> >> > > jim ab3cv
> >> >> > >
> >> >> > >
> >> >> > > On Mon, Apr 15, 2013 at 9:06 PM, Terry Posey
> >> <tposey at nettally.com>
> >> >> > > wrote:
> >> >> > >
> >> >> > > > Hi Jim -
> >> >> > > >
> >> >> > > > You are well on your way to 6m success with the
> >> >> > K3/KPA500/KAT500/PR6
> >> >> > > line
> >> >> > > > up. However, there is one more issue you will need to
> address
> >> in
> >> >> > > your
> >> >> > > > cabling system. The K3's Digout1 signal is asserted on the
> >> PIN 11
> >> >> > of
> >> >> > > the
> >> >> > > > AUX cable. That presents a conflict with the KPA500
> INHIBIT
> >> on PIN
> >> >> > > 11 on
> >> >> > > > the cable bus between the K3, PR6, KPA500, and KAT500. PIN
> 11
> >> >> > needs
> >> >> > > to be
> >> >> > > > "interrupted" before passing the Digout1 signal onto the
> >> KPA500 and
> >> >> > > KAT500,
> >> >> > > > yet still sending the PIN 11 Digout1 signal to the PR6.
> >> >> > > >
> >> >> > > > I purchased a HD15 male/female "port saver" adapter from
> the
> >> Web
> >> >> > ($5)
> >> >> > > and
> >> >> > > > removed PIN 11 with pliers. Install the "Y" cable at the
> K3
> >> ACC
> >> >> > > port, then
> >> >> > > > connect the PR6 to one side of the "Y" cable. Install the
> PIN
> >> 11
> >> >> > > > interrupter "port saver" adapter on the other side of the
> "Y"
> >> cable
> >> >> > > and
> >> >> > > > attach the HD15 cable connections to the KPA500 and the
> >> KAT500.
> >> >> > > >
> >> >> > > > I hope this helps.
> >> >> > > >
> >> >> > > > 73,
> >> >> > > > Terry K4RX
> >> >> > > >
> >> >> > > >
> >> >> > > > I'm just getting going on 6m with my K3/KPA500/KAT500. I'm
> >> getting
> >> >> > > ready to
> >> >> > > > order a M2 6M5XHP. My feedline consists of 150ft of LDF5-50
> to
> >> the
> >> >> > > tower
> >> >> > > > then about 40ft of Buryflex in the tower run and various
> >> pigtails.
> >> >> > So
> >> >> > > my
> >> >> > > > feedline losses should be relatively low.
> >> >> > > >
> >> >> > > > Based on various threads I've decided to go ahead and get
> the
> >> PR6
> >> >> > but
> >> >> > > want
> >> >> > > > to make sure I understand how to use it. It appears that it
> is
> >> >> > > bypassed
> >> >> > > > completely by the K3 on the transmit path to the KPA100
> which
> >> then
> >> >> > > goes to
> >> >> > > > the KPA500 and KAT500 then to the antenna.
> >> >> > > >
> >> >> > > > On receive the path back from the KPA/KAT is passed thru
> the
> >> PR6
> >> >> > > > automatically as long as it is powered and the RXAnt is
> >> selected
> >> >> > for
> >> >> > > 6m.
> >> >> > > >
> >> >> > > > So no fancy additional cabling required other than
> >> Power/Digout1
> >> >> > and
> >> >> > > the
> >> >> > > > RXin/RXout pair.
> >> >> > > >
> >> >> > > > My Beverages will just connect now through the PR6 supplied
> >> input.
> >> >> > > >
> >> >> > > > All good?
> >> >> > > >
> >> >> > > > Jim ab3cv
> >> >> > > >
> >> >> > > >
> >> >> > > >
> >> >> > >
> ______________________________________________________________
> >> >> > > 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****
> >> >>
> >> >> ** **
> >> >>
> >> > ______________________________________________________________
> >> > 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