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: comparing RS-BA1, SCU-LAN10, RigPi, SmartLink and receive-only SDRs, plus security, latency and rules

ci_cover.jpg

I'd like to pull the scattered remote-operation topics into one thread. The tools overlap, but they solve different problems, and people often mix them up. Treat the product details below as a starting point and check the current manufacturer documentation. Firmware and software compatibility change.

1. Three different jobs

Receive-only remote tools are one job. A public KiwiSDR or WebSDR gives you a wideband receiver in someone else's location through a browser. That is useful for checking whether your signal is being heard, or for seeing band conditions from another place. You are not controlling a transmitter, and you are not operating a station.

Remote control of your own station is another job. Here you are the control operator, and you are responsible for what goes out of the antenna. Examples are an IC-7610 with Icom's RS-BA1 software, a Yaesu radio with a SCU-LAN10 network interface unit, a FlexRadio with SmartSDR and SmartLink, or a Raspberry Pi based controller such as RigPi. Each handles CAT, audio, PTT and sometimes the panadapter differently.

Shared or hosted remote stations are the third job. RemoteHams.com is an example of a service for connecting to remote stations. Check its own pages for how access, scheduling and operator licensing are handled, because I won't guess at the details here.

2. Hardware notes

The IC-7610 has a network port and is the radio most commonly paired with RS-BA1. Not every Icom radio has native LAN, so check the radio model against Icom's compatibility list before buying. The open-source wfview project is an alternative client for some Icom radios.

The SCU-LAN10 is Yaesu's way to put supported radios on the network. It is a separate box that talks to the radio over USB and provides the network side. Again, check the supported-radio list and the software you intend to use.

FlexRadio's approach is built in. The radio is a network device, and SmartLink is the remote access layer. This is the least bolted-on of the options, but it ties you to that ecosystem.

With a RigPi or a similar Pi controller, you build the chain from a computer, rig control, audio interfaces and remote desktop or web control. It is flexible and a bit more work to harden.

3. Latency

Round-trip delay matters differently by mode. SSB is usually workable with moderate delay, though it feels awkward in a pileup if the delay is large. Jitter, meaning variation in delay, often hurts audio more than a steady delay. CW is harder: sending key-down and key-up events over the internet distorts timing. A better approach is to send text to a keyer at the radio end. For FT8 and other timed digital modes, run the decoding software at the station and remote-desktop to it, so the network only carries screen updates and not audio. Check your own station clock regardless of where the software runs.

4. Security

Please don't just forward a port on your router to a radio's LAN service. A safer pattern is a VPN into the home network (WireGuard or a mesh VPN are common choices), with the radio and controllers on a separate VLAN or at least not reachable from the open internet. Use unique strong passwords, keep router and Pi firmware current, and disable UPnP if you don't need it. Remember that a compromised remote station can transmit.

5. Station safety

Plan for the link dropping while you are transmitting. That means a transmit timeout, a remote-controlled power switch for the radio and amplifier, SWR and temperature monitoring, and a way to disable PTT locally. Without this, a stuck transmitter can run until someone physically gets there.

6. Rules

Rules vary by country, so don't assume. In many places, the control operator must hold a valid license, the station must meet the rules for the transmitter's location, and you must be able to shut it down when needed. In the US, the FCC rules on control points and remote control apply to a station you operate remotely. Contests and awards also set their own rules about where the transmitter must be relative to the operator. Read the sponsor's rules and your national regulations before you rely on a remote setup for credit.

What combination are you considering, and is the goal contesting, DXing from a noisy city lot, or just reaching your home station while traveling?

  • Replies 2
  • Views 37
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

A practical point on the audio side: the radio-to-network leg and the client-to-network leg are two separate things to tune. With RS-BA1 style setups, a bigger audio buffer will remove choppiness on a bad connection, but it adds delay. For ragchewing that is a fine trade. For working a pileup you will want it as small as the connection allows.

I'd also test the failure mode before depending on it. Start a transmission, pull the client's network connection and see what the radio does. If it keeps transmitting until a timeout, set that timeout shorter. Whatever the software promises, it is worth confirming on your own hardware.

Also, if you only want to listen from away from home, a KiwiSDR near you can tell you whether the band is open, but it's not a substitute for operating. You can't hear your own signal path the way your receive antenna does.

  • Administrators

On security, I'd split the question into reachability and authentication. A VPN fixes reachability: nothing from the open internet can talk to the radio's ports. Authentication then still matters inside the VPN, because a laptop on the same network can be compromised too. Keep the remote PC and the radio network separate where you can.

One thing people forget is the remote power switch and router themselves. If the web interface of a smart power strip is exposed, it is an easy way in. Put the strip behind the VPN as well, and make sure there is a way to cut power to the amplifier if all else fails.

On the rules side, the license question depends on where the transmitter is, not only where you are sitting. If you travel and operate your home station from another country, check whether your license and that country's rules are compatible. Local regulations may be different from what the equipment vendor's guide assumes.

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.