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

Planning a remote HF station: IC-7610 vs Flex vs SCU-LAN10 vs RigPi, plus security, latency and licensing

ci_cover.jpg

I'm sketching out a remote HF setup. The radio and antennas would sit at a quiet site with a decent tower, and I'd operate from a city apartment with a noisy RF environment. Before buying anything I want to compare the main approaches and work out where each one breaks down. This is a planning thread, not a report of something I've already built, so corrections are welcome.

The first split is between radios with network support built in and a generic server in front of any rig. The IC-7610 has an Ethernet port and works with Icom's RS-BA1 software, and the open-source wfview project can also talk to Icom LAN radios. FlexRadio is architecturally different. The radio is the server, SmartSDR runs on the client, and SmartLink handles the internet side. Yaesu's SCU-LAN10 is a network interface for supported radios, so check Yaesu's compatibility list for your exact model and firmware. RigPi and similar Raspberry Pi or PC based servers sit between any CAT-controllable rig and the network. They use something like Hamlib for control and a separate audio path, which makes them flexible but means more moving parts to maintain.

Then there is the other group of tools: WebSDR, KiwiSDR and RemoteHams.com. WebSDR and KiwiSDR are receive-only, shared SDR servers. They are useful as a second set of ears to check whether a band is open at a distant location, or whether the noise you hear is local or everywhere. They are not a way to transmit. RemoteHams.com is aimed at connecting remote station owners and users, so check the site for the current software, supported rigs and access rules before relying on any feature I describe here.

My open questions are these. How do you keep the station safe if the link drops while you are transmitting? What is the sane way to expose this to the internet? What latency can you tolerate for SSB, CW and FT8? And what do the licensing rules say when the station and the operator are in different places?

On safety, I think the radio should never be the only thing protecting itself. A remotely switchable power supply, a timeout timer, SWR and temperature monitoring, and a known antenna switch state all seem like the minimum. I would also want a way to reach the site's router and power control that does not depend on the radio software working.

On security, my instinct is to avoid port-forwarding a rig server directly and put a VPN in front of everything. That means WireGuard or a similar tunnel, a separate VLAN for the radio gear, unique passwords, and keeping firmware and the OS on any Pi up to date. Does that match what people consider sensible, or is it overkill for a hobby station?

On rules, I understand that remote control is generally permitted in many places, but the details differ. These include who counts as the control operator, which license privileges apply, whether the operator must be in the same country, and what a contest sponsor accepts. I will check the regulator's current text and the specific contest rules rather than assume. If anyone has pointers to where these questions are usually answered, I'd appreciate it.

  • Replies 2
  • Views 34
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

One thing that helps in the comparison is to separate the control path from the audio path. With RS-BA1, SmartLink or the SCU-LAN10, the vendor or software handles both. With a RigPi or a home-built server you choose the CAT method, the audio codec and the PTT scheme yourself, so more can go wrong, but you can often fix it yourself too. If you want one radio and minimal fuss, the integrated routes are easier. If you expect to swap radios or add an amplifier and antenna switch controller later, a server-based design ages better.

For latency, the type of operation matters more than the raw number. SSB is usually comfortable with moderate delay as long as it is consistent. Jitter is worse than a steady delay, because it produces choppy audio. For CW, send the text or keying to a keyer at the station rather than keying in real time over the internet, otherwise the timing suffers. For FT8 and similar modes, run the decoder at the station or make sure both ends are well synchronised to time, since the protocol cares about timing, not just the audio.

I'd also add a plain-language failsafe: if the control connection drops, the transmitter should go to receive on its own. Check how your chosen software behaves when the client disappears mid-transmit, and test it deliberately with a dummy load first.

  • Moderators

On security, a VPN in front is the right default. Many ham remote setups put the radio on the same network as everything else and then forward a port, which exposes the radio's control service to the whole internet. Giving the station its own subnet or VLAN and allowing only the VPN endpoint inbound is a much smaller attack surface. Use key-based authentication where the VPN supports it, and make sure the Pi or PC running the server is not also used for general browsing.

If you use a vendor service like SmartLink, read how it handles authentication and which ports or UPnP behaviour it needs, and decide whether you are comfortable with that on your router. Whichever route you pick, keep a second way into the site, such as a cellular backup or a remotely switchable router. You will otherwise be stuck the first time the network needs a reboot.

For the rules question, I would not rely on forum summaries, including this one. Look up your regulator's current text on remote control, the control operator's obligations, and whether the operator's location matters for the privileges they use. If you plan to enter contests, read the specific rules for remote operation in that contest, because some have category or location definitions that apply. Local clubs or the national society often have a remote-operation FAQ that points to the actual rule text.

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.