Here's some real-world experience from the three of the six remotes we operated this past weekend from WRTC:
Our Network at WRTC HQ: Either 100/9 Mbps WRTC-only or 20/20 Mbps shared with the hotel network. PR1T: ~384 Kbps using multiple technologies Typical ping time: 170-190 mS Number of routing hops to PR1T: >30 (!) Typical jitter: less than 20mS How it worked: We obviously had some router issues between us. When it worked, it worked very well. However, we would have dropouts where we would loose communications completely between the sites for 5-30 seconds. We kept a ping window up all the time so we could test. The RRC boxes allow you to adjust CW sending so that it sounds normal on the other end. In the PR1T case, we used the K3/0 mini for all the audio and rig control, but we used TeamViewer to operate N1MM remotely. We used N1MM to send automated CQs and exchanges... this worked well, as we were sending keystrokes only. SK9HQ@SK3W: ~284 kbps asymmetric DSL Typical ping time: 170-195 mS: Number of routing hops to SK3W: ~15 Typical jitter: lless than 10mS How it worked: Very well. We could send CW from the RRC locally, and it sounded good. I adjusted the RRC to take the transit times into account. We also used TeamViwer to control WinTest locally at SK3W (easy, and it also gave us all the local station control interfaces at SK3W) W1VE@K2LE/1: 1.5/.7 Mbps asymmetric DSL Typical ping time: 50-55 mS; Number of routing hops to K2LE/1: ~10 Typical jitter: less than 10 mS How it worked: Flawlessly. We networked N1MM over a VPN; Andy was at his staiton in Vermont, and the second operating position was at WRTC HQ. All CW was sent from the remote. Note that in all cases, we were able to run very high rates (>200/hr on both CW and SSB); being remote did not affect the ability to make fast QSOs. >From prior experience, I can tell you that attempting to run RemoteRig and a K3 over Multipoint-to-Point Wireless ISPs is very, very difficult. In this case, you are on a TDM half-duplex connection, and there is HUGE opportunity for dropouts and very high jitter. (which is going to be a killer). If you are trying to remote to a mountain top, find someone (like another ham) who has high-speed (Fiber or Coax), and run a point-to-point link on 5 GHz... This can work very well, and there is a lot of cheap gear out there to let you get the job done inexpensively. For portable operation, 4G LTE cellular hotspots/modems work very well -- as long as location is fixed. I've tried it mobile ( from New England) and it is so-so, though we have a lot of mountains in New Hampshire. Bottom line: RemoteRig and K3s run very well over pretty low speed connections. Just make sure jitter is low and fairly consistent. Latency can be fairly high, but you must adjust settings to compensate on CW. 73, Gerry W1VE Gerry Hull, W1VE | Hancock, NH USA | +1-603-499-7373 AKA: VE1RM | VY2CDX | VO1CDX | 6Y6C | 8P9RM <http://www.yccc.org> <http://www.yccc.org/> <http://www.facebook.com/gerryhull> <https://plus.google.com/+GerryHull/posts> <http://www.twitter.com/w1ve> On Sun, Jul 13, 2014 at 9:36 PM, Barry <w...@comcast.net> wrote: > A while back we tried Remoterig with a Kenwood radio and the CW generated > was > poor on the other end. This was presumably from dropped packets and or > latency issues (Comcast on one end and a terrestrial microwave connection > on > the other end). Some dits/dahs were lost and others were prolonged, due to > the lost stop signal. My understanding of the remoterig protocol for CW is > it's not very robust, with no error correction or ACKing. > > We got around the CW problem by using a VNC and the CW is generated at the > host end within the VNC window, using N1MM, directly keying the radio. > > If we were to use a K3 and K3/remote for the radio, would there be > potential > radio control issues due to the flaky internet connection, or is there > redundancy and/or error correction built into the Elecraft remote protocol? > > Barry W2UP > > > > > -- > View this message in context: > http://elecraft.365791.n2.nabble.com/How-reliable-an-internet-connection-is-needed-for-A-K3-remote-to-work-well-tp7591154.html > Sent from the Elecraft mailing list archive at Nabble.com. > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:Elecraft@mailman.qth.net > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to ge...@w1ve.com > ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
