Planning a remote station: RS-BA1, SmartLink, SCU-LAN10, RigPi, or a VPN with your own software?
- Replies 2
- Views 11
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Mod_Mike 1 post
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
I'd like to compare notes on how people set up remote HF stations. The options are wide: vendor ecosystems (Icom IC-7610 with RS-BA1, FlexRadio with SmartSDR and SmartLink, Yaesu with the SCU-LAN10 on supported radios), a Raspberry Pi-based controller such as RigPi, or a plain rig plus a PC at the station with remote desktop or VPN. There are also services such as RemoteHams.com that connect operators with remote-capable stations. Check their site for what they offer now, because I don't want to guess at it here.
First, separate two things that often get mixed up. Receive-only remote listening, such as public KiwiSDR and WebSDR nodes, is a different problem from remote transmit control. KiwiSDR and WebSDR are useful for checking propagation, comparing your own receive antenna to someone else's, or seeing whether your signal is getting out. They give you no control over a transmitter, and the legal and safety questions below don't arise for pure listening.
For remote transmit, my checklist starts with the failure modes rather than the features:
1. What happens when the link drops while the transmitter is keyed? You want a hardware or firmware timeout at the station: a TX time-out timer, a watchdog that drops PTT if the control connection goes silent, or a remote power switch you can reach by a separate path. Don't rely on the client software to un-key a radio it can no longer talk to.
2. Network exposure. Avoid forwarding rig control or audio ports straight to the internet. A VPN such as WireGuard, or an overlay network like Tailscale, to a small gateway at the station is a far smaller attack surface. Put the radio gear on its own VLAN or at least its own subnet, change default passwords, keep firmware updated, and know which vendor features open inbound ports or use cloud relay services. Read the documentation and decide whether you're comfortable with that.
3. Latency and jitter. Average ping matters less than how steady it is. SSB is usually tolerable with moderate delay. Full-QSK CW is harder, because you hear your own sidetone locally but the station's response arrives late. Many operators send CW as text or use a keyer at the station end instead of keying over the network. For FT8 and other WSJT-X modes, the cleanest approach is usually to run the decoder at the radio site and remote-desktop to it, which avoids audio timing problems and keeps the clock disciplined by a local time source.
4. Rules. In the US, remote control of an amateur station is allowed under the control-operator rules, but the licensee remains responsible, and you need a reliable way to shut the transmitter off. Other countries differ, particularly when the operator and the transmitter are in different countries, and when you're operating someone else's station. Privileges generally follow the licence terms where the transmitter sits, but check your own regulator and any reciprocal or CEPT arrangements. Contest rules add their own limits on where receivers, transmitters and antennas may be located. Read the rules for the specific contest.
My open questions: for a single-rig home station with a typical consumer ISP, is the vendor path (RS-BA1, SmartLink, SCU-LAN10) good enough on its own, or does wrapping it in a VPN pay off? And has anyone compared wfview and similar tools against the vendor software for Icom LAN radios, in terms of setup effort and audio quality?
Link to comment
https://www.hamradiobase.com/forums/topic/11823-planning-a-remote-station-rs-ba1-smartlink-scu-lan10-rigpi-or-a-vpn-with-your-own-software/Share on other sites