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 compared: vendor LAN solutions, RigPi-style controllers, SDR receivers, and where the rules and security issues bite

ci_cover.jpg

This thread is for comparing the common ways of running a station you are not sitting next to, and for sorting out which problems are technical and which are regulatory. Remote operation covers several different things, and mixing them up leads to bad design choices.

1. Receive-only remote listening. WebSDR and KiwiSDR sit here. They are shared receivers that you tune from a browser. They help you check propagation, hear how a band sounds from another location, or see whether your own signal is being copied. They don't transmit, so they aren't a remote station. They also aren't a replacement for your own receiver chain, because you are limited by that site's antenna, noise floor, and the number of users sharing the hardware.

2. Vendor-integrated remote control. The IC-7610 with Icom's RS-BA1, FlexRadio's SmartSDR with SmartLink, and Yaesu's SCU-LAN10 for supported radios all work this way. The radio, or a small interface next to it, puts CAT, audio, and sometimes the panadapter data on the network. This is usually the easiest route if the radio is on the supported list. Check the exact model compatibility and software requirements in the manufacturer's documentation before you buy anything, because support differs between models and software versions. Third-party software such as wfview can also talk to some Icom LAN radios, which helps if you prefer a different client or operating system.

3. A general station controller. A Raspberry Pi-based controller such as RigPi, or a DIY box running Hamlib's rigctld, sits between the radio and the network. Its advantage is that it can also handle the things the radio can't: antenna switches, rotators, power control, temperature monitoring, and a remote power switch. The trade-off is that you are now maintaining a small server, with its updates and configuration.

4. Shared or hosted remote stations. Platforms such as RemoteHams.com connect operators with stations they can use. The details of what a given service offers, such as licence requirements, supported radios, and the terms of use, can change, so read them on the site itself. Whether you are hosting a station or using someone else's, the same questions apply: who is the control operator, and under which licence and rules is the transmitter operating?

Latency. Plain SSB tolerates a fair amount of delay, but it makes break-in and rag-chew rhythm awkward. CW is more sensitive. Sending keyed dits and dahs over the internet exposes jitter and is a bad idea. Better to send text to a keyer at the remote end, for example one built into the radio or a WinKeyer-type device. For FT8 and other timed modes, the cleanest approach is usually to run the decoding software at the remote site, so the audio path doesn't affect timing. The remote PC then needs good time sync. Jitter often matters more than raw delay, and a wired connection at the remote end helps.

Security. Don't expose the radio or its control ports directly to the internet. Put it behind a VPN such as WireGuard, or another properly authenticated tunnel, rather than depending on port forwarding. Keep the station on a separate network segment if you can, disable UPnP, use unique strong credentials, and keep the firmware and the controller OS up to date. Plan for failure as well: a remote power switch, a transmit timeout, and a defined behavior if the link drops while the transmitter is keyed. Also think about the PTT line stuck on, SWR protection, and what happens after a power cut.

Rules. This varies by country, so check your own regulator. In general, the issues are whether remote control is allowed for your licence class, who counts as the control operator, whether the operation falls under the rules of the country where the transmitter is, and whether you need a way to shut the station down remotely. Contests and awards have their own rules about station location and remote operation, and these can differ from the licensing rules. Read them before you count on a log being valid.

Which approach have people found best for a home station, and what would you add to the failure-mode list?

  • Replies 2
  • Views 11
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the vendor-versus-controller question, I'd base the decision on how much of the station is actually the radio. If the setup is one transceiver and one antenna, the vendor route (RS-BA1, SmartLink, SCU-LAN10) is usually the shortest path. The radio, the client, and the audio streaming are designed to work together, so there's less to glue together.

Once there are an amplifier, an antenna switch, a rotator, and perhaps a remote ATU, the radio's own network feature only solves a small part of the job. That is where a RigPi-style controller earns its place. It lets you treat the shack as a set of devices behind one login rather than as a radio with some accessories bolted on. Just remember that a controller also becomes an attack surface and something to update. It needs the same VPN-only access as everything else.

One more point on latency: measure it in both directions and watch the jitter, not just a single ping. A link that averages a good number but swings widely is worse for audio than a slightly slower, steady one. Some clients let you adjust the audio buffer. A larger buffer smooths the audio but increases the delay, which is awkward for CW and for tuning the amplifier.

  • Moderators

I'd stress the licensing and control-operator side more, because it's easy to treat it as a footnote. With a hosted or shared remote station, work out first who the control operator is and whose licence the transmission is made under. In many places the rules of the country where the transmitter sits apply, and your own licence may or may not be recognised there. Don't assume that being able to log in means you may transmit. Check the national regulations and the host's terms.

For your own station, the dull safety items matter as much as the software. Have a way to kill transmit and mains power from outside the shack, such as a network power switch on a separate path. Set a transmit timeout, and think about what happens if the VPN drops mid-over. Also decide in advance who can reach the station and how access is revoked, particularly if more than one person uses it.

And a small note on the receive-only side. A KiwiSDR or WebSDR is handy as a second opinion on how you sound, but it's one listener at one location. It tells you whether a signal is propagating there, not whether your remote station is performing well. Treat the result as one data point.

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.