Remote station options compared: Icom RS-BA1, Yaesu SCU-LAN10, FlexRadio, RigPi and Kiwi/WebSDR, and what to get right on security, latency and rules
- Replies 2
- Views 116
- 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 there are at least three different setups. It helps to separate them before arguing about gear.
1. Receive-only remote access. WebSDR and KiwiSDR sites are shared receivers. You tune a browser, nobody needs a control operator, and you cannot transmit. They are still handy for a home station. Pick a Kiwi or WebSDR near your target area and use it to check your own signal or the band conditions. Remember that the stream has its own delay, so it will not tell you much about QSK or timing.
2. Your own rig at your own remote site. This is where the vendor ecosystems differ. The IC-7610 has Ethernet and works with Icom's RS-BA1 remote software. Open-source clients such as wfview also target Icom LAN radios. Yaesu's SCU-LAN10 is a hardware bridge that puts CAT and audio on the network for supported Yaesu radios, so check Yaesu's compatibility list for your exact model. FlexRadio is architected differently. The radio is already a network device, and SmartLink handles remote connections with account authentication. RigPi takes a third approach: a Raspberry Pi acting as a station server, usually with Hamlib-based rig control and a web interface, which you then pair with audio and PTT handling of your choosing.
3. Hosted or shared remote stations. RemoteHams.com is the example in this category. It lists and connects remote-capable stations. Read the host's terms, because the licensing and control-operator questions are different when the station is not yours.
Three topics keep causing trouble, so here is a starting point for each.
Security. Avoid forwarding rig control ports straight to the internet. Icom LAN radios use a small block of UDP ports for control, serial and audio, and those protocols were not designed to be hostile-internet facing. A VPN such as WireGuard into the shack LAN is the conservative approach. Separate the radio gear onto its own VLAN or subnet, change default credentials, keep firmware current, and remember that a Pi running remote desktop is a general-purpose computer on your network.
Latency. SSB tolerates a fair amount of delay, but full break-in CW does not. The usual solution is to run the keyer at the radio end and send text or keying events instead of audio, with the sidetone generated locally. For digital modes, run WSJT-X at the station and remote-desktop to it, so the decode timing doesn't depend on your link.
Rules. The control operator must be able to switch the transmitter off, and the licensee stays responsible. In the US that means looking at Part 97, particularly the station control and telecommand provisions. Other countries differ, and operating a station located in a different country than you may not be covered by your own licence. Awards and contests have their own remote-operation clauses too. Read the current rules for each before assuming your setup counts.
What does a safe failure mode look like for each of these? If the link drops while keyed, what stops the transmitter?
Link to comment
https://www.hamradiobase.com/forums/topic/10909-remote-station-options-compared-icom-rs-ba1-yaesu-scu-lan10-flexradio-rigpi-and-kiwiwebsdr-and-what-to-get-right-on-security-latency-and-rules/Share on other sites