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 design: rig-side hardware, latency, security and licensing for a remote-controlled HF setup

ci_cover.jpg

I'd like to compare approaches to remote HF operation, because the options are quite different in architecture even when they look similar from the operating position. Here is how I'd split the field, and then some questions on the parts that tend to go wrong.

Receive-only access. WebSDR and KiwiSDR are shared receivers. WebSDR is the software started at the University of Twente, and KiwiSDR is a GPS-capable wideband SDR (roughly 10 kHz to 30 MHz) with a browser interface. Neither lets you transmit. They are useful for checking propagation from another location, listening to your own signal at a distance, or comparing noise floors. They are not remote bases, but they are often the first thing people reach for when deciding where a remote receive site should go.

Transceivers with built-in network support. The IC-7610 has a LAN port and works with Icom's RS-BA1 remote software. The same radio can also be driven by third-party software such as wfview. FlexRadio's SmartSDR is network-native, and SmartLink handles access from outside the home network. Yaesu's SCU-LAN10 adds network control and audio to some Yaesu models, but compatibility depends on the radio, so check the exact model and firmware before buying. These setups put most of the work in the radio's own ecosystem, which is simpler, but you depend on the vendor's software and its update cycle.

Generic rig-side computer. This is the RigPi (a Raspberry Pi based controller using Hamlib) or a small PC at the station running rig control, audio routing and a remote client. It works with radios that have no LAN port, and you can add a remote power switch, antenna switch control and a keyer. The cost is more integration work and more things to secure.

Hosted or shared remote stations. RemoteHams.com is built around connecting operators to remote stations. Check the current documentation for how access, scheduling and client software work, because terms and features change. Using someone else's station adds questions about who the control operator is, what the station owner permits, and which license privileges apply.

Three areas I'd like input on:

1. Latency. Round-trip time matters less than jitter and buffer size. SSB with a few hundred milliseconds of delay is usable but awkward for rapid break-in. Digital modes such as FT8 are tolerant if decoding happens at the radio end and the station clock is accurate. CW is where things break down. Network-keyed CW with a large audio buffer can sound fine to you while the other station hears distorted timing. Sending text from a keyer at the remote end avoids most of that. What is everyone using for CW, and for SSB break-in?

2. Security. Port forwarding a rig-control or audio port straight to the internet is the thing I'd least want to see. A VPN (WireGuard, OpenVPN or an overlay network) in front of the station network is usually safer than exposing individual services. Beyond that: change default passwords on Pi-based controllers and routers, keep radio and router firmware current, put the station on its own VLAN or subnet, and use accounts that can be revoked. Vendor tools such as SmartLink reduce exposure but are not a replacement for basic network hygiene.

3. Safe failure. A remote transmitter needs a plan for the moment the link drops while keyed. Useful pieces include a TX timeout in the radio or software, a PTT watchdog that drops transmit if the control connection is lost, a remotely switchable power outlet that you can reach by a separate path, SWR and temperature protection on any amplifier, and a way to shut down the antenna system in a storm. What do people use as a hardware backstop rather than relying only on software?

Rules. I won't try to summarize every jurisdiction. In the US, the FCC rules on station control and control operators (Part 97) are the place to start, and other countries differ on remote operation, third-party stations, and operating across borders. Questions to settle before transmitting: does your license allow remote control from your location, who is the control operator, are you operating under the privileges your license grants for the station's location, and does the station need to identify differently? Please check your national regulator rather than relying on forum summaries.

  • Replies 2
  • Views 28
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On latency, I'd treat the whole thing as three separate paths: control (CAT), audio, and spectrum or waterfall data. They behave differently on a bad link. CAT can be slow without hurting much. Audio is the one where you notice jitter. The waterfall can lag and still be usable. If your software lets you set the audio buffer size, start larger and reduce until you hear dropouts, instead of starting small and chasing glitches.

For CW, I'd put the keyer at the radio end if at all possible. Typing or sending text to a local keyer avoids sending key-down and key-up timing across the internet. Paddles over a network work with some systems, but the result depends on the software's timing handling, so test by listening to your own signal on a separate receiver, such as a KiwiSDR near the station. That's a good use for a public receiver: it shows you what the other side hears, not what your monitor audio sounds like.

On security, I agree about not exposing ports. If you must have more than one user, a VPN with separate keys per person is better than one shared password, because you can revoke one person without redoing everything.

  • Moderators

One distinction I'd add is between remote control of your own station and operating a shared or hosted one. The second case gets murky quickly. If a station owner or service provides the equipment, you still need to know whose license is in play, which privileges apply, and what the host's own rules say about modes, power and band use. I would read the host's terms and the regulator's guidance together, and ask the host directly if anything is unclear.

On the hardware question, the IC-7610 with RS-BA1 or wfview and the Flex SmartLink route both keep the rig-side computer out of the picture, which cuts the number of things to patch. The RigPi or PC route gives you flexibility for older rigs, amplifiers and antenna switches, but then you own the operating system updates, user accounts and logging. Neither is wrong, so it depends on how much maintenance you're willing to do remotely.

For the watchdog, I'd want something that does not depend on the same network path as the radio control. A separate switched power outlet on a different connection, or a cellular-connected relay, gives you a way to cut power if the main link is half-alive. Use it as a last resort, since cutting power to a radio or amplifier abruptly isn't ideal, but it's far better than a stuck carrier.

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.