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 pick a path (Icom LAN, Yaesu SCU-LAN10, RigPi, Flex, RemoteHams) without creating a security or compliance headache

ci_cover.jpg

Remote operation is no longer exotic. Plenty of radios ship with a network interface, and Raspberry Pi servers, SDR receivers and hosted-station services cover the rest. The options overlap enough to cause confusion, so this thread is for comparing architectures rather than brands. I'll start with a rough framework and everyone can pick it apart.

1. Decide what you are actually remoting. There are four different jobs people lump together:

Receive-only monitoring: WebSDR and KiwiSDR nodes are public receivers. They are useful for checking whether your signal is being heard, or what a band is doing in a region, but they cannot transmit and say nothing about your own station.

Full remote control of your own station: CAT plus audio plus PTT, with you as the licensee and control operator. This is the case for Icom RS-BA1 or wfview with an IC-7610, FlexRadio SmartSDR/SmartLink, a Yaesu radio behind an SCU-LAN10, or a DIY chain such as a RigPi running Hamlib with an audio path.

Remote base or shared access: someone else's station that you operate, such as club stations or services like RemoteHams.com. Check who the control operator is, what privileges apply, and the host's terms before you key up.

Linking: repeater or net linking over the internet. This is a different set of rules and tools from point-to-point station control, though it shares the same latency and security concerns.

2. Radio-specific notes (verify against current manuals). The IC-7610 has a LAN port and is supported by Icom's RS-BA1 remote software, and wfview is an open-source alternative that speaks Icom's network protocol. Compatibility depends on model and firmware, so check Icom's current list. The Yaesu SCU-LAN10 is a network bridge for the radio's USB connection. Which Yaesu models it supports, and how audio is handled, depends on the radio and the software on the far end, so read the compatibility documentation first. FlexRadio's approach is different: the radio is already a network SDR, so the client software is the transceiver front end, and SmartLink handles access from outside the LAN. A RigPi-style server adds a web-managed Linux box between the radio and the network, which gives flexibility but means you maintain the OS, Hamlib version and audio chain.

3. Latency and jitter. Mean latency matters less than variation. A steady 80 ms feels fine for SSB, while a connection that swings between 30 and 400 ms causes clipped audio and awkward break-in. Things to plan for:

CW: sending keying over the network character by character is unforgiving. Prefer a keyer at the radio end driven by text or a protocol that buffers, and use sidetone locally. Full break-in over a long path is hard.

Digital modes: run WSJT-X or similar at the radio end and remote the computer desktop or the logs, not the audio. FT8 timing depends on the PC clock, and network audio adds nothing useful.

PTT: a dropped link must not leave you transmitting. Use a TX timeout and a heartbeat or watchdog that drops PTT if the client disappears.

4. Network security. Do not port-forward CAT or raw radio ports to the internet. A sensible baseline is a VPN into the home network (WireGuard or similar) with the radio on its own VLAN or at least a restricted segment, strong unique passwords on every device, current firmware, and no default credentials on the Pi, switch or router. Some vendor cloud features, like SmartLink, are designed for remote access, but you should still understand what they open and who authenticates. Treat the radio like any other IoT device: it has a network stack that was not built to survive the open internet.

5. Safety and failover. Think about what happens when the link dies mid-transmission, the antenna switch sticks, or the PA overheats while you are 500 km away. A remote-controlled power strip on a separate path (for example LTE), SWR and temperature monitoring, and a manual way to disable the transmitter locally are all worth having. For anything beyond low power, consider a camera on the amplifier and the tuner.

6. Rules. This varies by country, so please check your regulator. In general terms, a remote station still needs a control operator who can turn the transmitter off and is within their license privileges. Some jurisdictions treat the control point as the operator's location, and others tie privileges to where the transmitter sits. Cross-border remote use is where problems arise: your home license may not be valid for a station in another country. Contest and award rules (CQ, ARRL, DXCC and others) add their own requirements about where the station, receivers and operator may be, so read the current rule sets for the specific event rather than relying on forum summaries, including this one.

Questions for the thread: what is your split between vendor software and open-source tools, how do you handle CW and keying delay, and where do you draw the line on what is exposed to the internet?

  • Replies 2
  • Views 23
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the "what are you remoting" split, I'd add a fifth category: remote receive sites you own. A cheap KiwiSDR or similar at your own QTH, on a quiet antenna, is a useful reference for judging your own transmitted signal and local noise. It also gives you a way to check whether your station is on the air without logging into the radio. It doesn't replace a proper control path, but it makes a handy second opinion when the main link is misbehaving.

On security, the VPN-first rule is the one to stress. The most common mistake with these setups is treating the radio's LAN port as a service meant for the internet. A VPN tunnel with the radio, the Pi and the PC all behind it is far easier to audit than a list of forwarded ports. And if you do use a vendor relay service, read how it authenticates the client and the radio, and what you lose if that vendor's service is down.

One practical point on latency: measure it in both directions and under load. A path that looks fine on a ping test may suffer when the same uplink is busy with video or backups. A bit of QoS on the router for the radio traffic can matter more than any radio setting.

  • Moderators

Worth separating the audio chain from the CAT chain when you troubleshoot. With an IC-7610 over RS-BA1 or wfview, with a RigPi and Hamlib, or with an SCU-LAN10 setup, symptoms often look like "the radio is laggy" when the cause is a mismatch in audio sample rate, buffer size or codec settings at one end. Change one thing at a time and write it down. Also confirm what the software does with compression: some paths trade bandwidth for latency, and the default is not always right for a weak mobile or satellite uplink.

For CW, I'd test the keying path with a sidetone at the operator end and a monitor at the station end, and compare what each hears. If the remote end is adding a visible delay or distortion, shorten the chain, use a keyer near the radio, or move to a text-sending approach. A decent paddle feel over a long, jittery path is not realistic for fast CW.

For the rules side, keep a one-page document for each station: who is the licensee, who is the control operator, what call sign is used, which country the transmitter is in, and how the transmitter can be shut off by someone on site. If you ever share access with others, that page is also where you record who may transmit, on what bands, and under what license class. It saves arguments later, and it helps if a regulator or contest committee ever asks how the station is controlled.

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.