Remote station control compared: vendor LAN solutions, RigPi-style controllers, SDR receivers, and where the rules and security issues bite
- Replies 2
- Views 11
- Created
- Last Reply
Top Posters In This Topic
-
Mod_Chad 1 post
-
Mod_Chrissy 1 post
This thread is for comparing the common ways of running a station you are not sitting next to, and for sorting out which problems are technical and which are regulatory. Remote operation covers several different things, and mixing them up leads to bad design choices.
1. Receive-only remote listening. WebSDR and KiwiSDR sit here. They are shared receivers that you tune from a browser. They help you check propagation, hear how a band sounds from another location, or see whether your own signal is being copied. They don't transmit, so they aren't a remote station. They also aren't a replacement for your own receiver chain, because you are limited by that site's antenna, noise floor, and the number of users sharing the hardware.
2. Vendor-integrated remote control. The IC-7610 with Icom's RS-BA1, FlexRadio's SmartSDR with SmartLink, and Yaesu's SCU-LAN10 for supported radios all work this way. The radio, or a small interface next to it, puts CAT, audio, and sometimes the panadapter data on the network. This is usually the easiest route if the radio is on the supported list. Check the exact model compatibility and software requirements in the manufacturer's documentation before you buy anything, because support differs between models and software versions. Third-party software such as wfview can also talk to some Icom LAN radios, which helps if you prefer a different client or operating system.
3. A general station controller. A Raspberry Pi-based controller such as RigPi, or a DIY box running Hamlib's rigctld, sits between the radio and the network. Its advantage is that it can also handle the things the radio can't: antenna switches, rotators, power control, temperature monitoring, and a remote power switch. The trade-off is that you are now maintaining a small server, with its updates and configuration.
4. Shared or hosted remote stations. Platforms such as RemoteHams.com connect operators with stations they can use. The details of what a given service offers, such as licence requirements, supported radios, and the terms of use, can change, so read them on the site itself. Whether you are hosting a station or using someone else's, the same questions apply: who is the control operator, and under which licence and rules is the transmitter operating?
Latency. Plain SSB tolerates a fair amount of delay, but it makes break-in and rag-chew rhythm awkward. CW is more sensitive. Sending keyed dits and dahs over the internet exposes jitter and is a bad idea. Better to send text to a keyer at the remote end, for example one built into the radio or a WinKeyer-type device. For FT8 and other timed modes, the cleanest approach is usually to run the decoding software at the remote site, so the audio path doesn't affect timing. The remote PC then needs good time sync. Jitter often matters more than raw delay, and a wired connection at the remote end helps.
Security. Don't expose the radio or its control ports directly to the internet. Put it behind a VPN such as WireGuard, or another properly authenticated tunnel, rather than depending on port forwarding. Keep the station on a separate network segment if you can, disable UPnP, use unique strong credentials, and keep the firmware and the controller OS up to date. Plan for failure as well: a remote power switch, a transmit timeout, and a defined behavior if the link drops while the transmitter is keyed. Also think about the PTT line stuck on, SWR protection, and what happens after a power cut.
Rules. This varies by country, so check your own regulator. In general, the issues are whether remote control is allowed for your licence class, who counts as the control operator, whether the operation falls under the rules of the country where the transmitter is, and whether you need a way to shut the station down remotely. Contests and awards have their own rules about station location and remote operation, and these can differ from the licensing rules. Read them before you count on a log being valid.
Which approach have people found best for a home station, and what would you add to the failure-mode list?
Link to comment
https://www.hamradiobase.com/forums/topic/11734-remote-station-control-compared-vendor-lan-solutions-rigpi-style-controllers-sdr-receivers-and-where-the-rules-and-security-issues-bite/Share on other sites