It's not nearly as bad as one might think, Jim. I operate my mountain station both locally and remotely. When I leave that location, I have a little checklist. Well, it's not completely little, but most of it is stuff that rarely changes. I don't have to move ANY cables to convert from local to remote operation. Here's how:
- The local speaker at the remote site connects to SPKR on the K3. The RRC audio in connects to PHONES. The local headset and speaker are in parallel but the powered speaker has an Off switch. - The local mic and the RRC Mic Out connect to K3 Mic In, in parallel. - The local external keyer and the RRC key out line connect to K3 Key In, in parallel. - The local PTT line and the RRC PTT out line connect to K3 PTT In, in parallel. - The K3 RS232 connects to a two position rotary DB9 switch. One side goes to the P3 for local operation only. The other side goes to the RRC for remote operation only. The Go Remote checklist says "Set RS232 Switch to Remote." These switches are abundant and cheap online. Mine is called "QVS SureGrip Commercial Dataswitch." I think it cost about $10. - The checklist reminds me to set K3 AF gains to 9:00. This isn't critical but my logger often sends commands to the K3 that cause it to reset to the physical position of those knobs. (Yes, that's weird.) If they're fully CCW, the audio goes dead until I twiddle the control side K3 (or K3-0) AF gain control(s). - I use N1MM Logger Plus at either end, only one at a time. Operating locally, the computer connects to the P3 and is set to the appropriate COM port number. At the control site, the computer connects to the control RRC and is set to the COM port number corresponding to what the RRC confusingly calls its own "COM1." - My control site is a K3 which can operate either as a control head for the remote K3 or as a local radio. Switching is similar to what I describe above, including an RS232 switch, although Mic, Audio, and PTT circuits are in the opposite directions. That's all there is to it except for extra added attractions: - Amplifier control is via KPA500 Remote, KAT500 Remote and Alpha Remote. The Elecraft apps run in client/server config with the server side on a dedicated shack computer ($250) at the remote site. I access Alpha Remote via a remote desktop facility to the same server. - Antenna switching is automated at the remote site using Top Ten decoders, diode matrix, and WX0B Six Pak. - A remotely controlled relay board controls which amp to use, which band segments are set on my 80M rotary dipole, and whether the SteppIR or tribander is in use on the high bands. This is complicated but imminently achievable. - Rotator control is via PstRotatorAz, running client/server. - All 120V AC power is controlled via a remote AC switch box from Digital Loggers. Older versions work fine and are reasonably priced at closeout stores. I set mine up with two user IDs. The usual ID only controls the shack 12VDC PS and the rotor. A special Admin ID can also power cycle things that usually stay on like the server computer, cable modem, and router. - If you choose to use a local server computer like I do, make sure to get one that reboots after a power failure! Most laptops don't. Most old, surplus machines intended for server use have this as an optional feature. In total, it's a lot of integration. But I also have a lot of flexibility. I still don't have remote panadapter display, dang it. But there is some good work going on with tools like Win4K3Suite, LP-PAN, external SDRs, etc. that may help here once I make time to learn them. GL & 73, /Rick N6XI On Sun, Aug 13, 2017 at 5:08 PM, Jim Miller <[email protected]> wrote: > I have a K3s, P3 (and someday a KPA1500) and I'm considering a RemoteRig > and K3/Mini for remote operation. > > I realize the P3 access and KPA1500 if any will need to come from some > other source like Teamviewer or VNC. I need that for controlling the > rotator and power switching anyway. > > I'm told that RR/K3-mini performance is like "being there." > > One issue I have is the amount of disconnecting and reconnecting of cables > when switching from local operation of the K3s to setting up for remote > operation. > > Nothing I've seen in the documentation leads me to believe that this > reconfiguration of cabling for the K3s is any simpler that what is needed > for the original K3. > > For those of you who have RR and a K3s: did I miss something? Does the > cleaned up wiring on the K3s via USB for normal local operation offer any > advantages when it comes to RR configuration? > > Thanks > > jim ab3cv > ______________________________________________________________ > 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 > Message delivered to [email protected] > -- Rick Tavan Truckee, CA ______________________________________________________________ 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 Message delivered to [email protected]
