Remote station control: how to pick a path (Icom LAN, Yaesu SCU-LAN10, RigPi, Flex, RemoteHams) without creating a security or compliance headache
- Replies 2
- Views 23
- 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 is no longer exotic. Plenty of radios ship with a network interface, and Raspberry Pi servers, SDR receivers and hosted-station services cover the rest. The options overlap enough to cause confusion, so this thread is for comparing architectures rather than brands. I'll start with a rough framework and everyone can pick it apart.
1. Decide what you are actually remoting. There are four different jobs people lump together:
Receive-only monitoring: WebSDR and KiwiSDR nodes are public receivers. They are useful for checking whether your signal is being heard, or what a band is doing in a region, but they cannot transmit and say nothing about your own station.
Full remote control of your own station: CAT plus audio plus PTT, with you as the licensee and control operator. This is the case for Icom RS-BA1 or wfview with an IC-7610, FlexRadio SmartSDR/SmartLink, a Yaesu radio behind an SCU-LAN10, or a DIY chain such as a RigPi running Hamlib with an audio path.
Remote base or shared access: someone else's station that you operate, such as club stations or services like RemoteHams.com. Check who the control operator is, what privileges apply, and the host's terms before you key up.
Linking: repeater or net linking over the internet. This is a different set of rules and tools from point-to-point station control, though it shares the same latency and security concerns.
2. Radio-specific notes (verify against current manuals). The IC-7610 has a LAN port and is supported by Icom's RS-BA1 remote software, and wfview is an open-source alternative that speaks Icom's network protocol. Compatibility depends on model and firmware, so check Icom's current list. The Yaesu SCU-LAN10 is a network bridge for the radio's USB connection. Which Yaesu models it supports, and how audio is handled, depends on the radio and the software on the far end, so read the compatibility documentation first. FlexRadio's approach is different: the radio is already a network SDR, so the client software is the transceiver front end, and SmartLink handles access from outside the LAN. A RigPi-style server adds a web-managed Linux box between the radio and the network, which gives flexibility but means you maintain the OS, Hamlib version and audio chain.
3. Latency and jitter. Mean latency matters less than variation. A steady 80 ms feels fine for SSB, while a connection that swings between 30 and 400 ms causes clipped audio and awkward break-in. Things to plan for:
CW: sending keying over the network character by character is unforgiving. Prefer a keyer at the radio end driven by text or a protocol that buffers, and use sidetone locally. Full break-in over a long path is hard.
Digital modes: run WSJT-X or similar at the radio end and remote the computer desktop or the logs, not the audio. FT8 timing depends on the PC clock, and network audio adds nothing useful.
PTT: a dropped link must not leave you transmitting. Use a TX timeout and a heartbeat or watchdog that drops PTT if the client disappears.
4. Network security. Do not port-forward CAT or raw radio ports to the internet. A sensible baseline is a VPN into the home network (WireGuard or similar) with the radio on its own VLAN or at least a restricted segment, strong unique passwords on every device, current firmware, and no default credentials on the Pi, switch or router. Some vendor cloud features, like SmartLink, are designed for remote access, but you should still understand what they open and who authenticates. Treat the radio like any other IoT device: it has a network stack that was not built to survive the open internet.
5. Safety and failover. Think about what happens when the link dies mid-transmission, the antenna switch sticks, or the PA overheats while you are 500 km away. A remote-controlled power strip on a separate path (for example LTE), SWR and temperature monitoring, and a manual way to disable the transmitter locally are all worth having. For anything beyond low power, consider a camera on the amplifier and the tuner.
6. Rules. This varies by country, so please check your regulator. In general terms, a remote station still needs a control operator who can turn the transmitter off and is within their license privileges. Some jurisdictions treat the control point as the operator's location, and others tie privileges to where the transmitter sits. Cross-border remote use is where problems arise: your home license may not be valid for a station in another country. Contest and award rules (CQ, ARRL, DXCC and others) add their own requirements about where the station, receivers and operator may be, so read the current rule sets for the specific event rather than relying on forum summaries, including this one.
Questions for the thread: what is your split between vendor software and open-source tools, how do you handle CW and keying delay, and where do you draw the line on what is exposed to the internet?
Link to comment
https://www.hamradiobase.com/forums/topic/11593-remote-station-control-how-to-pick-a-path-icom-lan-yaesu-scu-lan10-rigpi-flex-remotehams-without-creating-a-security-or-compliance-headache/Share on other sites