Remote station setup: RS-BA1, SCU-LAN10, RigPi, Flex remote and how to keep it safe, low-latency and legal
- Replies 2
- Views 14
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
This thread is for comparing approaches to remote station control, from a simple receive-only link to a full remote base with transmit. The options overlap, but the risks and the rules differ a lot depending on whether you only listen or also key a transmitter.
Receive-only first. WebSDR and KiwiSDR are the easy entry points. Both are receivers shared over the internet through a browser, and neither gives you control of a transmitter. A KiwiSDR is a hardware SDR that covers HF, and many owners make them available publicly. A WebSDR server is software-driven and can serve many listeners at once from a wideband receiver. They are useful for checking whether a band is open in a target area, comparing your own antenna against a distant receiver, or monitoring your own signal. Bear in mind that propagation seen at someone else's receiver is only a rough proxy for what the other end hears from your station.
Remote-capable radios. Several manufacturers now build network control into the radio or into an add-on unit. The Icom IC-7610 has an Ethernet port and works with Icom's RS-BA1 remote software, which carries audio and control between a client PC and the radio. For Yaesu, the SCU-LAN10 is a network unit that bridges CAT and audio over a LAN for supported models. Check Yaesu's compatibility list for your exact radio and firmware before buying. FlexRadio's approach is built around SmartSDR, with SmartLink available for access from outside your home network. In all three cases, the vendor's own path is usually the least fiddly. A radio with no network feature at all can still be remote-controlled with a small server PC and a third-party audio and CAT bridge.
Roll-your-own. RigPi is a Raspberry Pi based controller with a web interface and Hamlib underneath. It suits people who already have a radio with a serial or USB CAT interface and want a low-power, always-on box at the station. RemoteHams.com is another route. It is a community and software ecosystem aimed at remote operating, and it includes tools for sharing access to stations. Read what each service actually provides, since some focus on software, some on directories, and some on both.
Security. This is where many remote setups go wrong. Opening a rig's control port directly to the internet by port forwarding is a bad idea. Safer patterns:
Put a VPN such as WireGuard or a similar mesh VPN in front of everything, so the radio only answers to devices on the private tunnel. Put the radio, server PC and any antenna switch on their own VLAN or at least a separate subnet. Use unique strong passwords on the router, the server and any vendor account, and apply firmware updates. Add a remote power switch for the station, plus a way to drop the transmitter if the link dies. Set a PTT timeout or transmit timer in software and in the rig if it supports one. A stuck PTT while the network drops is the failure that matters most.
Latency. SSB conversation tolerates a surprising amount of delay, but it gets tiring when round-trip time becomes large. Wired Ethernet at both ends and a UDP-based audio path generally behave better than Wi-Fi with a congested uplink. Jitter matters as much as raw ping, because buffers get larger to hide it and that adds delay. For CW, sending a keyed stream over the network is much more demanding than sending text to a keyer at the station. For digital modes such as FT8, it is often better to run the decoder and WSJT-X at the radio end and only remote the desktop, which avoids timing problems from audio over the internet. Keep NTP time sync working on whichever machine runs the decoder.
Rules. These vary by country and I will not try to summarize every one. In general, the licensee stays responsible for the transmissions, and a control operator with the proper privileges has to be able to shut the station down. If you operate a remote station in another country, find out what that country's regulator requires, and whether your license or a reciprocal arrangement covers it. Awards and contests have their own rules too, so read the current rules for the specific contest or program before assuming a remote contact counts. Some contests restrict where the receiver, transmitter and antennas may be relative to each other.
What is your setup, and where did you hit the hardest limit: security, latency, or the rules?
Link to comment
https://www.hamradiobase.com/forums/topic/11791-remote-station-setup-rs-ba1-scu-lan10-rigpi-flex-remote-and-how-to-keep-it-safe-low-latency-and-legal/Share on other sites