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 setup: RS-BA1, SCU-LAN10, RigPi, Flex remote and how to keep it safe, low-latency and legal

ci_cover.jpg

This thread is for comparing approaches to remote station control, from a simple receive-only link to a full remote base with transmit. The options overlap, but the risks and the rules differ a lot depending on whether you only listen or also key a transmitter.

Receive-only first. WebSDR and KiwiSDR are the easy entry points. Both are receivers shared over the internet through a browser, and neither gives you control of a transmitter. A KiwiSDR is a hardware SDR that covers HF, and many owners make them available publicly. A WebSDR server is software-driven and can serve many listeners at once from a wideband receiver. They are useful for checking whether a band is open in a target area, comparing your own antenna against a distant receiver, or monitoring your own signal. Bear in mind that propagation seen at someone else's receiver is only a rough proxy for what the other end hears from your station.

Remote-capable radios. Several manufacturers now build network control into the radio or into an add-on unit. The Icom IC-7610 has an Ethernet port and works with Icom's RS-BA1 remote software, which carries audio and control between a client PC and the radio. For Yaesu, the SCU-LAN10 is a network unit that bridges CAT and audio over a LAN for supported models. Check Yaesu's compatibility list for your exact radio and firmware before buying. FlexRadio's approach is built around SmartSDR, with SmartLink available for access from outside your home network. In all three cases, the vendor's own path is usually the least fiddly. A radio with no network feature at all can still be remote-controlled with a small server PC and a third-party audio and CAT bridge.

Roll-your-own. RigPi is a Raspberry Pi based controller with a web interface and Hamlib underneath. It suits people who already have a radio with a serial or USB CAT interface and want a low-power, always-on box at the station. RemoteHams.com is another route. It is a community and software ecosystem aimed at remote operating, and it includes tools for sharing access to stations. Read what each service actually provides, since some focus on software, some on directories, and some on both.

Security. This is where many remote setups go wrong. Opening a rig's control port directly to the internet by port forwarding is a bad idea. Safer patterns:

Put a VPN such as WireGuard or a similar mesh VPN in front of everything, so the radio only answers to devices on the private tunnel. Put the radio, server PC and any antenna switch on their own VLAN or at least a separate subnet. Use unique strong passwords on the router, the server and any vendor account, and apply firmware updates. Add a remote power switch for the station, plus a way to drop the transmitter if the link dies. Set a PTT timeout or transmit timer in software and in the rig if it supports one. A stuck PTT while the network drops is the failure that matters most.

Latency. SSB conversation tolerates a surprising amount of delay, but it gets tiring when round-trip time becomes large. Wired Ethernet at both ends and a UDP-based audio path generally behave better than Wi-Fi with a congested uplink. Jitter matters as much as raw ping, because buffers get larger to hide it and that adds delay. For CW, sending a keyed stream over the network is much more demanding than sending text to a keyer at the station. For digital modes such as FT8, it is often better to run the decoder and WSJT-X at the radio end and only remote the desktop, which avoids timing problems from audio over the internet. Keep NTP time sync working on whichever machine runs the decoder.

Rules. These vary by country and I will not try to summarize every one. In general, the licensee stays responsible for the transmissions, and a control operator with the proper privileges has to be able to shut the station down. If you operate a remote station in another country, find out what that country's regulator requires, and whether your license or a reciprocal arrangement covers it. Awards and contests have their own rules too, so read the current rules for the specific contest or program before assuming a remote contact counts. Some contests restrict where the receiver, transmitter and antennas may be relative to each other.

What is your setup, and where did you hit the hardest limit: security, latency, or the rules?

  • Replies 2
  • Views 14
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

One thing worth adding about latency is where the time-critical pieces live. If the client has to do the keying or the timing, every extra network hop gets into the loop. With CW, a keyer at the station fed by text, or a client protocol that sends keying events with timestamps, usually feels better than streaming a sidetone and hoping for the best. With FT8, the safest layout is to keep WSJT-X on a PC at the radio and use remote desktop or a VPN-connected client only to watch and click. That way a hiccup in your home connection does not cost you a time slot.

For the transmit chain, I would also look at what happens when the control program crashes while the radio is keyed. Many of these bridges rely on the software to send an unkey command. A hardware watchdog or the radio's own timeout is what actually saves you, so test it deliberately with a dummy load before relying on it.

  • Moderators

On the security side, a few people treat vendor cloud login as enough, which is only part of the picture. SmartLink-style services and similar relay setups reduce the need to open ports, but you are still trusting the account and the endpoint device. Use a unique password and two-factor authentication if the service offers it. For radios without that feature, like a Yaesu behind an SCU-LAN10 or an Icom with RS-BA1, a VPN into the home network is usually the cleaner answer than forwarding the radio's ports. The radio's network stack is not designed to be exposed to the public internet.

A practical checklist for a remote base: power control for the radio and amplifier, a separate switch for the antenna so you do not depend on one control path, SWR and temperature alerts, and a log of who connected and when. For a shared station, say through RemoteHams or a club arrangement, write down who is the control operator for each session. That makes the legal side much clearer, because the person with transmit access should hold the privileges for the frequency they are using under the rules that apply where the transmitter sits.

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.