Thanks again for your excellent and comprehensive response. Brian
*Brian F. Wruble, C.F.A. *70 is the new 40.* * Mail: 1107 Key Plaza, PMB 447 Key West, FL 33040-4077 Summers: P.O.Box 57, 7400 Augustine Herman Highway, Georgetown, MD 21930 eFax 305.768.0278 On Mon, Jun 24, 2013 at 8:36 AM, Don Wilhelm <[email protected]> wrote: > Brian, > > Yes, the Y-cable supplied by Elecraft will work. The KPAK3AUX cable set > contains that Y-cable. They are also available from other sources with all > 15 pins wired straight through - the more commonly available VGA Y-cables > will NOT work. > I think the instructions for the KPAK3ACC reveal a lot of information > about that cable set. See http://www.elecraft.com/** > manual/E740160%20KPAK3AUX%**20Cable%20Set%20Instructions%**20Rev1c.pdf<http://www.elecraft.com/manual/E740160%20KPAK3AUX%20Cable%20Set%20Instructions%20Rev1c.pdf> > > I have not used the Navigator, but from my perusal of the webpage, it > connects only to the ACC connector, but if it lives up to its advertizing, > it should co-exist with the KRC2 on the ACC connector (using the Y-cable). > > The P3 uses the RS-232 connection, and but not the ACC connector, so no > conflict there. > I can't answer for any potential conflicts between RemoteRig and the > Navigator. > > Changing from KRC2ACC to KRC2 firmware will modify the behavior of the > buttons on the KRC2, and there will be no audible responses from the KRC2. > Whether that is suitable for your proposed operation is your decision - > each operators goals are different. > > Note that the P3 and the K3 communication wants the RS-232 rate set to > 38400 baud - the KRC2 limit is 19200 baud, so that may give some difficulty > in the K3 to P3 communications path. The controller IC in the KRC2 is the > limiting factor and significant re-design (different controller) would be > required to boost the rate to 38400. > > 73, > Don W3FPR > > > > > On 6/24/2013 7:45 AM, Brian F. Wruble wrote: > >> Don, does the "Y" connector Elecraft sells work for this? I have on order >> a KAT500 and a KPA500. I can't quite figure out what the KPAK3AUX does, >> but will that address the problem? >> >> Here is the long-term plan. I want to operate this station (in Maryland) >> remotely from our home in Key West. I will get a K3/0 when the mini >> comes >> out, and the RemoteRig gear. I will not need the P3 hooked up for that, >> so >> maybe that frees up the needed pathway. But while I am in MD, I do need >> the P3. I want the KRC2 only for antenna switching. However, the audible >> feedback was the way I was going to be sure the antennas actually switched >> --- by monitoring the station remotely (including the readout of the >> rotor) >> using a webcam and mike. . If that is the only reason to keep a PC >> running, I can give that up. Of course, I can probably give up the >> Navigator (only when operating remotely) if I am getting audio in/out >> using >> RemoteRig. >> >> So my questions are: >> >> Other than the audible cues, what do I give up by loading the KRC2 >> firmware >> vice the KRCACC firmware? I really only must have antenna switching. >> >> Will the Y cable from Elecraft work with a KRC2 (not ACC) and a P3 and a >> Navigator? >> >> What does the KPAK3AUX do for my eventual station (full remotely >> controlled >> K-Line)? Does the Y cable that comes with that fit my needs? >> >> Thanks so much for your help. >> >> 73 de Brian W3BW >> >> >> >> >> >> >> >> >> >> >> *Brian F. Wruble, C.F.A. >> >> *70 is the new 40.* >> * >> Mail: 1107 Key Plaza, PMB 447 Key West, FL 33040-4077 >> Summers: P.O.Box 57, 7400 Augustine Herman Highway, Georgetown, MD 21930 >> eFax 305.768.0278 >> >> >> >> >> >> >> >> On Mon, Jun 24, 2013 at 12:01 AM, Don Wilhelm <[email protected]> >> wrote: >> >> Brian, >>> >>> The recommended K3 to KRC2 communication is to use the AUXBUS signalling >>> for band signalling. The AUXBUS signal is on pin 2 of the K3 ACC >>> connector >>> with the return path at pin 5 (ground). You can get a "Y" connector to >>> bring the ACC signals out to both the Navigator and the KRC2ACC. Make >>> certain the "Y" cable has all pins connected and no pins connected >>> together >>> - a VGA "Y" cable will NOT work. >>> >>> Please not that the solution above will only provide band selection in >>> the >>> KRC2ACC - other functions will not work. >>> >>> One cannot use a "Y" connector on the RS-232 signals unless one device >>> only listens to the RS-232 data traffic. Both the P3 and the KRC2ACC >>> have >>> drivers on the RS-232 connection and that will cause much chaos and >>> failure >>> of communications for both the KRC2ACC and the P3. >>> >>> In other words, I do not have a workable solution for you. Perhaps Jack >>> Brindle can make some suggestions, but from my knowledge of the RS-232 >>> signalling, they will not work together. >>> >>> My suggestion is to load the KRC2 firmware and forget about the ACC >>> option, then you can use the KRC2 for control of your antenna relays with >>> the connection to the K3 ACC connector (with the "Y" cable). >>> >>> 73, >>> Don W3FPR >>> >>> >>> On 6/23/2013 4:44 PM, Brian F. Wruble wrote: >>> >>> Hi all, >>>> >>>> OK, I have built my KRC2ACC, and it passes all the tests. I have built >>>> the >>>> special cable for use with my K3. Now am stumped again, so I am hoping >>>> someone can "baby-talk" me through this. >>>> >>>> I use a Navigator interface for digital modes. That occupies the ACC >>>> jack >>>> of the K3. I use a P3 Panadaptor, and that occupies the serial (RS232) >>>> port of the K3. The Navigator uses the RS232 port of the P3. There is >>>> no >>>> place left to connect the KRC2ACC. >>>> >>>> The manual makes reference to "daisy-chaining", but always in connection >>>> with the K2, not the K3. So I am stuck again. >>>> >>>> Where do I plug it in, and what jumpers do I set? >>>> >>>> Thanks in advance, >>>> >>>> Brian W3BW >>>> >>>> >>>> >>>> >>>> *Brian F. Wruble, C.F.A. >>>> >>>> *70 is the new 40.* >>>> * >>>> Mail: 1107 Key Plaza, PMB 447 Key West, FL 33040-4077 >>>> Summers: P.O.Box 57, 7400 Augustine Herman Highway, Georgetown, MD 21930 >>>> eFax 305.768.0278 >>>> ______________________________****____________________________**__**__ >>>> Elecraft mailing list >>>> Home: >>>> http://mailman.qth.net/****mailman/listinfo/elecraft<http://mailman.qth.net/**mailman/listinfo/elecraft> >>>> <http**://mailman.qth.net/mailman/**listinfo/elecraft<http://mailman.qth.net/mailman/listinfo/elecraft> >>>> > >>>> Help: >>>> http://mailman.qth.net/mmfaq.****htm<http://mailman.qth.net/mmfaq.**htm> >>>> <http://mailman.qth.net/**mmfaq.htm <http://mailman.qth.net/mmfaq.htm>> >>>> Post: mailto:[email protected].****net <[email protected]> >>>> >>>> >>>> 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<http://mailman.qth.net/mailman/listinfo/elecraft> >> Help: http://mailman.qth.net/mmfaq.**htm<http://mailman.qth.net/mmfaq.htm> >> Post: mailto:[email protected].**net <[email protected]> >> >> 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:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
