Remote station design compared: radio-native LAN (IC-7610/RS-BA1, SCU-LAN10), Flex, RigPi and SDR receivers, plus security, latency and licensing
- Replies 2
- Views 26
- 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 questions usually start with "which box do I buy?", but the choice makes more sense once you split the problem into layers. A remote station has a control path (CAT/frequency/mode/PTT), an audio path (RX and TX), station support (power switching, antenna switching, amplifier, rotator, cameras, SWR and temperature monitoring), and a network path that connects it all to you. Different products handle these layers differently, so this thread is a place to compare approaches and sort out which layer each one covers.
Radio-native LAN control. The Icom IC-7610 has a network port and works with Icom's RS-BA1 remote software, so the radio itself serves control and audio over IP. Third-party clients such as wfview also speak Icom's network protocol. Icom has used a small group of UDP ports (commonly listed as 50001 to 50003 for control, serial and audio), but check your radio's menu and manual instead of trusting a forum post. Yaesu's SCU-LAN10 takes a different route: it is a separate interface unit that puts supported radios' control and audio onto a LAN. Compatibility is model-specific, so verify your exact radio and firmware before you buy. In both cases the radio's remote features were designed for a trusted network, which matters for the security section below.
Flex. SmartSDR with SmartLink is the usual remote route for FlexRadio's networked radios. The radio is effectively a server and the client can be anywhere, so the radio's own panadapter and slices are available remotely. That is a real advantage over a CAT-and-audio-only link, because you see the same spectrum you would see locally. Confirm what your radio generation and licensing require, and what SmartLink needs from your router.
RigPi and similar Raspberry Pi controllers. A Pi-based station server (RigPi is one example) sits between the radio and the network and typically uses Hamlib-style rig control with a web interface and some station-accessory control. Its value is less about audio magic and more about giving you one consistent place for rig control, relays and accessories, independent of the radio brand. Audio transport and the TX/RX workflow depend on the software you pair it with.
Receive-only helpers: KiwiSDR and WebSDR. A KiwiSDR is a wideband HF receiver (roughly 0 to 30 MHz) shared through a browser. WebSDR is a separate system, originally from the University of Twente, with many independent sites. Neither transmits, so they are not a remote base. They are useful for something else: checking your own signal. If a public receiver near your remote site hears you, you have an independent check on audio quality, frequency and propagation, so you are not relying only on the link you built. Also respect each site's user limits and etiquette.
Hosted and shared services. RemoteHams.com and similar services are about connecting operators with remote-capable stations or SDR access. Details such as availability, who controls the transmitter, and what an operator needs to be licensed for differ by service and change over time, so read the current documentation instead of relying on a summary here.
Network security. Please do not just forward the radio's UDP ports to the internet. A safer pattern is a VPN (WireGuard, OpenVPN or an overlay network) so only an authenticated device can reach the radio network. This also helps if your ISP uses CGNAT and port forwarding is impossible. Put the shack gear on its own VLAN or subnet, disable UPnP, change default passwords, keep firmware current, and log connections. Remember that a compromised remote link can mean unauthorized transmissions under your callsign.
Latency and jitter. One-way latency of tens to a couple of hundred milliseconds is workable for SSB, but jitter and packet loss do the damage: choppy audio, PTT hang, delayed unkey. CW is the tricky case because keying over a delayed link ruins timing. Send CW as text or keyer commands to a keyer at the remote end, not as raw key-down events. FT8 and other timed digital modes should run the decoder and clock at the radio site so network delay doesn't matter. Pileups and QSK-style work are where the delay is most noticeable.
Rules. The legal answers depend on where the station is and where you are. Generally the control operator must be able to turn the transmitter off, and the station must be identified and operate within the licence of whoever is in control. In many countries remote control is allowed but may carry extra conditions, and operating a remote station in a different country can raise licence issues. Contests and awards (including DXCC-style programs) have their own rules about remote stations, so read the current version for the one you care about. Ask your national regulator if the wording is unclear.
What combination are you weighing, and where are you most worried: security, latency or the rules?
Link to comment
https://www.hamradiobase.com/forums/topic/11349-remote-station-design-compared-radio-native-lan-ic-7610rs-ba1-scu-lan10-flex-rigpi-and-sdr-receivers-plus-security-latency-and-licensing/Share on other sites