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 412.9 km/s
Aurora 1
Updated 14: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

Remote station design: control paths, latency, security and the rules (IC-7610/RS-BA1, SCU-LAN10, Flex, RigPi, Kiwi/WebSDR)

ci_cover.jpg

Remote operating has two parts that get mixed up: the radio's control path and the station's safety and legal wrapper. Most threads jump straight to "which box should I buy" and skip the second part. This is a framework to argue about, so please poke holes in it.

The first question is whether the radio itself speaks network. The Icom IC-7610 has an Ethernet port and works with Icom's RS-BA1 server/client software, so the radio does CAT, audio and (via the software) keying over the LAN. Open-source clients such as wfview target the same Icom network protocol. Yaesu's SCU-LAN10 is a separate network unit that bridges supported radios to a LAN, so check Yaesu's compatibility list for your exact model and firmware before assuming it works. FlexRadio is different because the radio is the SDR. SmartSDR clients talk to it directly, and SmartLink handles access over the internet, so there is no separate audio bridge. If the radio has no network path at all, the usual answer is a small always-on computer at the station running Hamlib/rigctld, a sound interface and a remote desktop or audio-streaming layer. A RigPi-style Raspberry Pi build fits that role: the Pi sits at the radio and you connect to the Pi, not to the radio.

Where the software runs matters a lot for digital modes. For FT8, FT4 and similar, run WSJT-X at the station and remote-desktop into it, rather than streaming audio to a client at home. Those modes depend on accurate computer time and on clean audio levels. Both are easier to keep right locally, and network jitter then only affects your screen, not your decodes.

Latency also differs by mode. For SSB, round-trip delay builds up from the audio codec and buffers, the internet path and any jitter buffer. Once the total gets long enough to disturb turn-taking, it feels like a satellite link. CW is harder, because streaming key-down/key-up over a variable-delay link can mangle the timing. It is generally better to send text or keyer commands to a keyer at the station, or to use the radio's built-in keyer, so the timing is generated locally. Adding VPN and remote-desktop layers on top of audio streaming adds delay at each step, so measure with your actual stack instead of trusting a spec sheet.

On security, I'd treat port-forwarding a radio server straight to the internet as the thing to avoid. Radio network protocols were not designed as hardened internet services. A VPN, such as WireGuard or OpenVPN, or a managed overlay network, lets you reach the LAN without publishing radio ports. Beyond that, keep the radio and Pi on their own VLAN or at least their own subnet, turn off UPnP on the router, use unique credentials, and keep router and OS firmware current. If a vendor's remote feature needs inbound ports, read exactly which ports it needs and what authentication protects them.

Fail-safe behavior is the part people forget. What happens if the link dies while you are transmitting? Use the radio's time-out timer, and add a watchdog or relay that drops PTT when a heartbeat disappears. A remotely switched power strip lets you recover a hung PC. Also think about status feedback for antenna switch position, amplifier state and SWR, since you cannot walk over and look.

On the rules, remote control is generally permitted, but the details depend on your country and licence class, and I'm not going to cite a rule as universal. In the US, remotely controlled stations fall under the Part 97 station-control provisions (control point, control operator, protection against unauthorized control, limits on transmitting if the control link fails). Read the text yourself, starting with 97.109 and 97.213. Operating from or through a station in another country raises separate licensing questions. Contests and awards also set their own remote-operation rules, for example where the station and operator may be located, so check the sponsor's current rules before relying on a remote QSO.

Receive-only networks are useful as an extra tool. WebSDR and KiwiSDR sites let you check how your signal sounds at a distant location or confirm band conditions before you fire up the remote rig. They are not a real-time monitor of your own audio, because the stream delay is large. For services like RemoteHams.com, which offer shared or hosted remote access, read the current terms on licensing responsibility and who counts as the control operator. I'm not going to assume how any particular service handles that.

What does your control chain look like, and which piece has been the weakest link: audio quality, CW timing, network reliability or the security setup?

  • Replies 2
  • Views 43
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the security side I'd go a step further than "use a VPN." Decide what your remote client actually needs to reach, and write that down. With an IC-7610 and RS-BA1 or wfview, that is the radio's control, serial and audio ports, which are commonly documented as UDP 50001 to 50003. Check your own manual, though, because ports can be changed and I wouldn't trust a forum post over the documentation. Once the VPN is up, a firewall rule that allows only your VPN subnet to those ports is much safer than relying on obscurity.

A cheap managed switch or a router with VLAN support is worth it. Radios, Pis and cameras tend to run old firmware and are poor candidates to share a flat network with your laptop and NAS. If something on the radio VLAN gets compromised, it can't easily reach the rest of the house.

On the legal side, I'd add that the person logging in is the control operator at the remote control point, so you need to be sure that only licensed, authorized people can ever key the station. Shared passwords on a family PC are a bad idea for that reason alone.

  • Moderators

On latency, it helps to split the problem into the radio's response and the human feedback loop. Tuning feels sluggish when the panadapter or waterfall data takes a long path, even if the audio is fine. A Flex-style SDR, where the client does the DSP, can feel snappier on tuning than a CAT-polled traditional rig, but only if the bandwidth for the panadapter stream is there. If your upstream at the station is thin, drop the panadapter rate and the audio bit rate before blaming the VPN.

For CW, the local-keyer approach in the opening post is the right one. If you must stream keying, expect to slow the speed down and accept sloppy weighting, or use a keyer at the station with a text interface. For a remote Pi-based setup, I'd run the logging and digital software there as well. A single remote-desktop session into the Pi also gives you fewer moving parts to troubleshoot than separate audio, CAT and PTT streams.

One useful test is to have a KiwiSDR or WebSDR near your station, or at a distance, receive your remote signal and compare it to what you monitor. That catches overdriven audio, a stuck compressor setting and a mis-set TX bandwidth, which are easy to miss when you only hear a processed return stream. Just remember that the Kiwi's own delay means you can't use it to judge round-trip timing.

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.