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: how to choose between RS-BA1, SCU-LAN10, RigPi, Flex remote and receive-only SDRs without creating a security or rules problem

ci_cover.jpg

This thread is for comparing the common ways to reach an HF station over the internet, and for sorting out which problems are technical and which are regulatory. "Remote operation" covers several different things, and mixing them up makes planning harder.

First, receive-only listening. WebSDR and KiwiSDR sites let you listen to a distant receiver through a browser. They are useful for checking whether a band is open at a remote location or for comparing your own noise floor with a quieter site. You cannot transmit through them, and they do not replace a remote base. Most public receivers are shared, so bandwidth, the number of simultaneous users and the operator's rules all limit what you can do.

Second, a remote base you own or have permission to use. This is where radio-specific tools come in. The IC-7610 has a built-in network interface, and Icom's RS-BA1 software is the usual route to remote audio and control. Yaesu's SCU-LAN10 is a network unit for supported Yaesu radios, so check the compatibility list for your exact model and firmware before buying. FlexRadio's SmartSDR approach is different because the radio is already a network device, and the client mostly receives a stream and sends commands. RigPi-style builds use a small Linux computer next to the radio to handle rig control, audio, keying and sometimes power switching, and you connect to that instead of to the radio itself.

Third, shared remote stations, such as those listed through RemoteHams.com. These are subject to the host's terms, the licensing rules of the country where the station sits, and any award or contest rules that apply. Read the host's rules before assuming a contact will count for anything.

Latency is the technical issue that catches the most people. Phone and digital modes tolerate an extra few hundred milliseconds, but the delay shows up in the PTT-to-audio chain, in monitoring your own voice, and in operating habits like breaking in on a pileup. CW is harder. Keying a real-time paddle over a variable-latency link makes timing sound uneven, so the better practice is to send text or keyer commands to a keyer at the station and let it generate the elements locally. For FT8 and similar modes, running the decoding software at the station side avoids audio-stream timing and clock problems. Use a wired connection at both ends where you can, and watch for jitter as well as raw ping time.

On security, the main rule is to avoid putting a radio's control port directly on the public internet with a port forward. A VPN to your home network (WireGuard or a similar tool), a separate VLAN or subnet for radio gear, strong unique credentials, and regular firmware updates are safer starting points. Think about failure modes too: what happens if the link drops mid-transmission? A hardware transmit timeout, a remote-controllable power switch for the PA and the radio, and a way to see SWR and temperature remotely are as important as the software.

On the rules, the details depend on your country. In the US, for example, FCC Part 97 treats remote control as a form of control operation, with specific requirements for the control point and control link, and the licensee remains responsible for the station's emissions. Elsewhere you may need a licence valid for the country where the transmitter is located, and CEPT-style arrangements do not automatically cover remote operation. Contests and awards also set their own rules, so check the sponsor's current text instead of relying on forum summaries.

To keep this concrete, tell us what you are trying to do: operate your own home station from work, access a station at a second location, listen to remote receivers, or use a shared remote base. Mention your radio model, what network you have at each end, and which modes you care about most.

  • Replies 2
  • Views 28
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

One thing worth splitting out early is where the audio and control actually terminate. With a radio-native option like RS-BA1 or Yaesu's network unit, you are trusting the manufacturer's protocol and the firmware on the radio. With a RigPi-style server, the Linux box becomes the thing you have to patch and secure, but you get more flexibility: you can add a keyer, a web power switch, antenna switch control and logging, all behind one VPN connection.

For Flex, the radio is built around being driven over a network, so the question becomes less "can it be remote?" and more "how do I expose it safely?" Their own remote-access service is the convenient path, but a VPN into your LAN is a reasonable alternative if you want to control exactly what is reachable. Whichever you choose, test with a dummy load first and deliberately pull the network cable mid-transmit to see what the station actually does.

I would also keep a short written checklist for the remote end: power cycle method, who can reach the station physically if something sticks, and what the default state is after a reboot. That list matters more than a slightly lower latency figure.

  • Administrators

On the listening side, a KiwiSDR or WebSDR is a good way to gauge latency expectations before committing money. Both stream audio and a waterfall to a browser, so you get a feel for the delay, buffering and dropouts of a typical internet path. That is not identical to the traffic of a full-duplex remote base, but it will tell you quickly whether your connection has jitter problems.

The caveat is that public receivers have their own policies, user limits and sometimes frequency or time limits. Treat them as a reference tool for checking propagation, not as a substitute for a receiver you control. For comparisons, note the receiver's antenna and noise environment, because a quiet site can make a band look far better than it will sound at your own QTH.

Also, for anyone planning to operate remotely in contests, make sure the rules say remote operation is permitted for your category. Some events require the transmitter, receiver, antennas and operator to be at a single location, while others allow a remote setup if it follows specific conditions. This varies between sponsors and between years, so read the current rules rather than assuming.

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.