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.5
Wind 385.0 km/s
Aurora 1
Updated 13: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

Planning a remote station: RS-BA1, SmartLink, SCU-LAN10, RigPi, or a VPN with your own software?

ci_cover.jpg

I'd like to compare notes on how people set up remote HF stations. The options are wide: vendor ecosystems (Icom IC-7610 with RS-BA1, FlexRadio with SmartSDR and SmartLink, Yaesu with the SCU-LAN10 on supported radios), a Raspberry Pi-based controller such as RigPi, or a plain rig plus a PC at the station with remote desktop or VPN. There are also services such as RemoteHams.com that connect operators with remote-capable stations. Check their site for what they offer now, because I don't want to guess at it here.

First, separate two things that often get mixed up. Receive-only remote listening, such as public KiwiSDR and WebSDR nodes, is a different problem from remote transmit control. KiwiSDR and WebSDR are useful for checking propagation, comparing your own receive antenna to someone else's, or seeing whether your signal is getting out. They give you no control over a transmitter, and the legal and safety questions below don't arise for pure listening.

For remote transmit, my checklist starts with the failure modes rather than the features:

1. What happens when the link drops while the transmitter is keyed? You want a hardware or firmware timeout at the station: a TX time-out timer, a watchdog that drops PTT if the control connection goes silent, or a remote power switch you can reach by a separate path. Don't rely on the client software to un-key a radio it can no longer talk to.

2. Network exposure. Avoid forwarding rig control or audio ports straight to the internet. A VPN such as WireGuard, or an overlay network like Tailscale, to a small gateway at the station is a far smaller attack surface. Put the radio gear on its own VLAN or at least its own subnet, change default passwords, keep firmware updated, and know which vendor features open inbound ports or use cloud relay services. Read the documentation and decide whether you're comfortable with that.

3. Latency and jitter. Average ping matters less than how steady it is. SSB is usually tolerable with moderate delay. Full-QSK CW is harder, because you hear your own sidetone locally but the station's response arrives late. Many operators send CW as text or use a keyer at the station end instead of keying over the network. For FT8 and other WSJT-X modes, the cleanest approach is usually to run the decoder at the radio site and remote-desktop to it, which avoids audio timing problems and keeps the clock disciplined by a local time source.

4. Rules. In the US, remote control of an amateur station is allowed under the control-operator rules, but the licensee remains responsible, and you need a reliable way to shut the transmitter off. Other countries differ, particularly when the operator and the transmitter are in different countries, and when you're operating someone else's station. Privileges generally follow the licence terms where the transmitter sits, but check your own regulator and any reciprocal or CEPT arrangements. Contest rules add their own limits on where receivers, transmitters and antennas may be located. Read the rules for the specific contest.

My open questions: for a single-rig home station with a typical consumer ISP, is the vendor path (RS-BA1, SmartLink, SCU-LAN10) good enough on its own, or does wrapping it in a VPN pay off? And has anyone compared wfview and similar tools against the vendor software for Icom LAN radios, in terms of setup effort and audio quality?

  • Replies 2
  • Views 11
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

I'd lean toward the VPN-first approach, for the reason you already gave: it shrinks what you have to trust. Vendor remote tools are convenient, but each one has its own idea of authentication, port requirements and update cadence. If everything sits behind WireGuard, the radio ecosystem only has to work inside a trusted tunnel. One caveat is that some clients are fussy about discovery on a LAN, since they use broadcast or multicast to find the radio. You may need a routed setup with a fixed IP and manual entry rather than auto-discovery, so test that before you travel.

On the rig side, the IC-7610 is a good example of why hardware separation helps. It has both USB and a LAN port, so you can pick whichever control path suits the software you use, but you should confirm in the manual which features (audio, CI-V, spectrum) each path carries. RS-BA1 is Windows software, so factor in a PC at your end. If you're using the SCU-LAN10, check Yaesu's compatibility list for your exact model rather than assuming a similar radio works. That unit's whole purpose is network connection, so firmware versions and the radio's menu settings matter.

And please add a remote power switch on a separate path, like a smart PDU or a small relay board, and that path should not depend on the radio's own network interface. If the radio hangs, you need a way to power-cycle it without a drive to the site. Also consider a second, low-bandwidth way back in, such as a cellular router, in case the main ISP link fails.

  • Administrators

Here's one angle on the RigPi and Pi-based route, and on where the latency really goes. A Pi controller is a good middle ground when your radio has no native network interface. It typically handles CAT through Hamlib, PTT and band-data switching, and it can also manage antenna switches and rotators through the same web interface. That's a big plus over a pure vendor solution, which only talks to the radio. The tradeoff is that you own the integration: audio, a USB sound interface, and keeping the OS patched. Whether you buy it or build it, treat the Pi as an internet-facing device that needs a lock-down plan, not as an appliance.

For latency, measure before buying anything. Run a continuous ping and look at jitter and packet loss over a few days, at different times of day, between where you'll operate and the station. A link with 40 ms steady is nicer than one that averages 25 ms but spikes to 300. Audio streams buffer to hide jitter, and every buffer adds delay. That's why CW and break-in feel better when the station end does the keying, and why digital modes belong on the radio side with a local clock.

On licensing, don't assume. Whether you're allowed to operate remotely from one country into another, or use a club or commercial remote station, depends on the regulator and your licence class. A service like RemoteHams.com may publish its own conditions, so read those and the local regulations before transmitting, and keep your station identification and logging consistent with where the transmitter physically is. For listening-only use, public WebSDR and KiwiSDR nodes are a good way to practise handling remote audio and latency without any of these questions.

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.