Remote station control: choosing between RS-BA1, SCU-LAN10, RigPi, Flex SmartLink and Kiwi/WebSDR, and what to sort out first (security, latency, rules)
- 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.
Remote operation gets discussed as if it were one thing, but it is really several different setups that share the word "remote". Which one you pick decides your security exposure, your latency budget and your regulatory position. I'd like to compare notes by layer.
1. Receive-only remote. WebSDR (the Twente-style software by PA3FWM) and KiwiSDR are browser-based receivers. You aren't controlling your own radio, you are borrowing someone else's receiver and antenna. They are useful for checking propagation, seeing whether your signal is getting out (if you know a receiver near your target path), and for TDoA-style location work with several Kiwis. No transmit means no control-operator questions, but the shared receivers have user limits and you can't choose the antenna.
2. Radios with a network stack built in. FlexRadio is the clearest case, because the radio is already a network device. SmartSDR runs on the client, and SmartLink handles authentication and connection setup over the internet. The IC-7610 is similar in spirit: it has a LAN port, and Icom's RS-BA1 software on the client talks to it directly. As I understand it, RS-BA1 defaults to a small set of UDP ports (commonly documented as 50001 to 50003 for control, serial and audio), but check your own manual before you forward anything. The open-source wfview project is another client for Icom's LAN protocol, so you aren't locked into one program.
3. A server box next to a radio that wasn't designed for it. The Yaesu SCU-LAN10 sits between the radio and your network and carries CAT and audio. A RigPi (Raspberry Pi running Hamlib-style rig control plus a web interface) covers a lot of older radios with a CAT port. In both cases you still need to decide where digital-mode software runs, how audio gets to you, and how PTT behaves if the connection dies mid-transmission.
4. Hosted or shared remote bases. RemoteHams.com is one of the services built around connecting operators to remote stations. Whether you are renting time or sharing your own station, read the service's current terms and licensing requirements yourself. They change, and I'd rather not guess at them here.
Three questions I'd like opinions on:
Security: is a VPN (WireGuard or similar) into the home network the right default, rather than port-forwarding the radio's protocol? Raw CAT or rigctld exposed to the internet has no meaningful authentication.
Latency: for SSB and FT8, a few hundred milliseconds is usually tolerable, but QSK CW and fast contest exchanges are another matter. Where does each of these tools start to hurt?
Rules: the operator's licence privileges, the station's location and the control-point requirements don't always line up. What should people check before they go on the air from a different country or call area?
Link to comment
https://www.hamradiobase.com/forums/topic/11693-remote-station-control-choosing-between-rs-ba1-scu-lan10-rigpi-flex-smartlink-and-kiwiwebsdr-and-what-to-sort-out-first-security-latency-rules/Share on other sites