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 412.9 km/s
Aurora 1
Updated 14:00 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 design: RS-BA1, SCU-LAN10, RigPi, SmartLink and where the real risks are (latency, security, licensing)

ci_cover.jpg

I'd like to compare approaches to remote station control and talk through the failure modes, not just which box is easiest to set up. The common options seem to fall into three groups.

First, radios with native network support. The Icom IC-7610 has an Ethernet port and works with Icom's RS-BA1 remote software, which carries CAT control and audio. Yaesu's SCU-LAN10 is a network interface for supported Yaesu radios, so check the compatibility list for your exact model and firmware. FlexRadio's SmartSDR is a different design: the radio is already a network device, and SmartLink handles access over the internet. In each case the vendor defines the protocol, so your main jobs are network design and safety.

Second, a controller in front of an ordinary radio. A RigPi-style Raspberry Pi controller, or a PC running Hamlib/rigctld, remote audio software and a remote switch, lets you connect almost any rig that has CAT and audio. It's flexible, but you own more of the integration: audio levels, PTT handling, antenna switching and what happens when something hangs.

Third, services and receive-only networks. RemoteHams.com is oriented toward remote operation, with software and station sharing. Check the site for what is currently offered and how access is managed. WebSDR and KiwiSDR are different: they are receive-only, browser-accessible SDRs run by their owners. They are useful for checking propagation, for seeing whether your own signal is getting out (if you're not using a transmit-capable remote), and for monitoring a band from another place. They are not a remote base, and you have no control over them or their availability.

On latency, bandwidth matters less than jitter and consistency. SSB over a typical Opus-style audio stream is workable with round trips in the tens to low hundreds of milliseconds. The pain shows up in QSK CW, in break-in and in fast-turnaround modes. For CW, a keyer at the station (for example a WinKeyer-type device or a keying path that sends timing to the remote end) avoids shaping elements across a jittery link. For FT8 and FT4, put the decoding software on the station side or ensure the clock is well disciplined on whichever PC runs it, because decode timing depends on accurate time, not on low latency.

On security, don't just forward the radio's control port to the internet. A safer baseline is a VPN into the home network (WireGuard or similar), the radio and controller on a separate VLAN or at least a separate subnet, strong unique credentials, updated firmware, and no default passwords on the controller. Where a vendor offers a relay or authentication service such as SmartLink, understand what it exposes and keep your account secure.

Safety matters as much as security. Think about what happens if the link drops mid-transmission: a hardware or firmware TX timeout, a way to drop PTT, a remote power switch for the amplifier and the radio, an out-of-band way to reach the site (a second ISP or a cellular fallback), and some way to confirm antenna and tuner state before transmitting. A stuck carrier into the wrong antenna is a worse problem than a failed login.

On the rules, remote operation is allowed in many places, but details differ by country. In general, the operator needs a licence and privileges valid where the transmitter is located, the control operator must be able to cease transmission, and unattended or automatic operation has its own conditions. Contest and award sponsors have their own remote rules, such as limits on station location and on where receivers and transmitters can be. Read the current rules for each, and check your national regulator for the exact wording.

Questions for the thread: what are you using to handle PTT failsafe, and how much do you trust the vendor link versus your own VPN? Where do you draw the line for remote operation with no one on site?

  • Replies 2
  • Views 30
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

I'd start with the failsafe, because the rest follows from it. If you can only protect one thing, make it the transmit path. A radio's own TX timeout helps, but it isn't a substitute for a controller that drops PTT when the control session or the audio stream goes away. Remote relays, an amplifier you can power off independently, and an SWR/antenna sanity check before transmitting are all cheap compared with fixing a damaged amp or tuner.

On RS-BA1 versus a Pi-based controller: the vendor software is simpler because audio, CAT and the client are designed together. The trade-off is that you're tied to the supported radios and to that software's own security model. A RigPi or a Hamlib/rigctld setup gives flexibility with older rigs and additional accessories, but you have to test audio levels, PTT sequencing and recovery after power cycles yourself. Neither is better in general. It depends whether you want an appliance or a build.

One more point on KiwiSDR and WebSDR: they're useful as an independent check. If you transmit from a remote station, you can often find a public receiver within a sensible distance and see your signal on it. Just remember it's a convenience, not a controlled test, since the receiver's location, noise and availability aren't yours.

  • Moderators

I'd separate three questions that get mixed up: how do I reach the station, how do I authenticate, and what can an attacker do if they get in? Port forwarding the radio's control port to the internet answers the first question and fails the other two. A VPN into the LAN (WireGuard works well for this) means a single, well-understood entry point. If you use SmartLink or a hosted service instead, check how accounts, keys and permissions are handled, and keep those credentials unique.

For latency, I'd measure rather than guess. Run a continuous ping and look at the variation, not just the average, and test under real conditions such as evening home-network load or a mobile hotspot as the client. Jitter buffers can hide some problems on SSB, but they add delay, and that makes CW and rapid exchanges harder. For CW, local keying at the station is a sensible design. For digital modes, run the decoder on the station side or at least confirm your time source is good.

On licensing, don't assume your home privileges travel with you. The rules usually care about where the transmitter is and which licence you hold for that country, and a contest or an award may add its own requirements. Check each one before you plan a weekend around a remote station.

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.