Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

Remote station control: picking between IC-7610/RS-BA1, Flex, SCU-LAN10, RigPi and receive-only SDRs, and what to do about latency, security and rules

ci_cover.jpg

This thread is for comparing approaches to remote operation, since the options get lumped together even though they solve different problems. Three categories are worth separating.

1. Receive-only remote SDRs (WebSDR, KiwiSDR). These are shared receivers you listen through in a browser. A KiwiSDR covers roughly 0-30 MHz with several simultaneous user channels and a GPS-derived time and frequency reference. WebSDR is the software originally developed at the University of Twente, and many sites run it on different hardware. Neither lets you transmit, so there are no control-operator questions for the listener. They are mainly useful for checking propagation, comparing your signal at a distance, or hearing a band your own station can't.

2. Radio-native remote control. The Icom IC-7610 has a LAN port and works with Icom's RS-BA1 software (wfview is a popular open-source alternative). FlexRadio's SmartSDR is network-based by design, and SmartLink extends it across the internet. Yaesu's SCU-LAN10 adds a network interface to supported Yaesu radios, but check Yaesu's compatibility list for your model, and note that the audio and client side often involves third-party software.

3. Station-side controllers and services. RigPi is a Raspberry Pi-based station server that sits between the radio and the network. RemoteHams.com is a service and software ecosystem for connecting and sharing remote stations. Read its current documentation for what it supports, because the details change and I don't want to state them from memory.

Discussion questions: for a first remote setup, is the manufacturer's own path (RS-BA1, SmartLink) the better starting point, or is a generic server with a VPN more flexible? And how much of the failsafe design (transmit timeout, power control, antenna state) should live on the radio side rather than in the client software?

  • Replies 2
  • Views 45
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

The native-versus-generic choice mostly comes down to where the audio and CAT sessions terminate. With an IC-7610 and RS-BA1, the radio streams audio and control over its network interface, so there is little to build at the station end. The trade-off is that you are tied to Icom's client behavior and its supported ports, and you still have to provide a secure path to the radio. Flex is similar. The radio is the server, and SmartLink handles discovery and connection brokering, but you should still understand what it needs from your router and firewall.

A Pi-based station server such as RigPi, or a small PC at the radio, gives you more control. You can run WSJT-X or other digital software at the station so decoding timing doesn't depend on the internet path. You can also add a WinKeyer-style device so CW keying happens locally with only the key events or text sent remotely. That matters because audio latency is often tolerable for SSB, but a laggy paddle-to-keying path is miserable for CW. Full QSK break-in over the internet is generally unrealistic.

Watch jitter as well as average latency. A steady 120 ms round trip is easier to operate through than a connection that averages 40 ms but spikes. Jitter buffer settings and codec choice in the audio software are worth experimenting with. For FT8 and similar modes, the audio delay itself matters less if the decoder and PC clock are at the radio, but keep that machine's time sync healthy.

One practical point for the SCU-LAN10: confirm exactly which functions it provides for your radio (CAT, audio, firmware update) before buying, since different Yaesu models have changed over the years.

  • Moderators

On security, the main rule is not to expose raw radio control to the open internet. CAT ports, serial-over-IP bridges and radio web interfaces are not designed to withstand constant scanning. A VPN such as WireGuard, or an overlay network such as Tailscale, puts the remote-control traffic inside an authenticated tunnel, so you don't have to forward the radio's ports through the router. If your ISP uses CGNAT, which prevents inbound connections, a VPN with a relay or a small cloud-hosted endpoint can sidestep the problem. Beyond that, put the radio, Pi and relays on a separate VLAN or network segment, change default credentials, keep firmware updated, and log access.

Design for the case where the link dies mid-transmission. Look for a transmit timeout on the server side, a way to power-cycle or drop PTT through a separately controlled relay, and a defined state for antenna switches and amplifiers. A remote amplifier needs particular care, because a stuck key or band mismatch can do real damage. Add SWR or power protection that works without the client.

For rules, there is no single answer, and you should verify with your national regulator. In the US, the Part 97 provisions on station control, control operators and telecommand are the relevant sections. They generally require that someone is acting as control operator at a control point, that the licensee remains responsible, and that the link has appropriate safeguards against loss of control. Operating a station located in another country adds another layer. The licensing and reciprocal-operation rules for the station's location and the operator's authorization both matter, and so do any contest or award rules for station location. If you share a station with others through a service, the licensee-of-record still has responsibilities for what goes out over the air.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.