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 options compared: Icom LAN, Yaesu SCU-LAN10, Flex SmartLink, RigPi, and where latency, security and rules bite

ci_cover.jpg

Let's compare the main ways to run a station remotely and the problems that show up whichever route you take. The tools are quite different, so it helps to sort them by what they do.

Receive-only tools such as WebSDR and KiwiSDR let you hear conditions near your remote site, or check how your signal is getting out, without touching your own radio. A KiwiSDR is a wideband HF receiver that shares its spectrum with several listeners, and WebSDR does something similar with different software. Neither transmits, so neither raises control-operator questions. They are still useful companions to a remote station, because they tell you whether a silent band is closed or whether your receive chain has a problem.

For full remote operation, the radio families differ in architecture. A FlexRadio is network-native: the radio is a network device, SmartSDR clients talk to it over IP, and SmartLink handles the WAN side. The Icom IC-7610 has an Ethernet port and works with Icom's RS-BA1 software, and some people use third-party tools instead. The Yaesu SCU-LAN10 is a bridge unit that puts CAT and audio on the network for supported radios. Check Yaesu's compatibility list for your exact model and read the manual for what the client side needs. Then there is the DIY or appliance route: a RigPi or other Raspberry Pi-based controller, or a small PC at the remote site running Hamlib-based software, with audio and CAT passed through. RemoteHams.com sits in a different category again, since it is aimed at connecting operators with remote stations. Read their current documentation before assuming how it fits your setup.

Three questions decide most designs. First, latency: what does round-trip delay do to your mode? Second, security: what exactly is exposed to the internet? Third, rules: who is the control operator, and what happens when the link drops?

For the first, SSB tolerates a few hundred milliseconds, but jitter is more annoying than steady delay. CW and QSK are harder. For the second, the main principle is that rig control ports should never be reachable directly from the open internet. Where do you all land on VPN versus vendor relay versus port forwarding?

  • Replies 2
  • Views 51
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On security, I'd rank the options roughly like this. Best is a VPN or private overlay network terminating at the remote site, so the radio, RigPi and any PC are only reachable from inside it. Next is a vendor-managed relay service, where you are trusting that vendor's authentication and update practice. Worst is port forwarding the radio's native ports straight to the internet. Many radio network stacks were designed for a trusted LAN, so assume that firmware doesn't get the same scrutiny as a router or a hardened server.

Some practical hygiene: put the radio gear on its own VLAN or at least its own subnet, turn off UPnP on the router so nothing opens ports without you knowing, change every default password, and keep firmware current on the router, the Pi, and the radio. Use key-based SSH on a RigPi or any Linux box, and don't leave a web interface open without authentication. Also remember that network security protects against intruders but not against mistakes, so you want a hardware answer to 'what if I can't reach it?'. A remote-switchable power strip on a separate path, a transmitter timeout, and a watchdog that drops PTT if the control session disappears all matter more than most people expect. A stuck carrier into a mistuned antenna is a bigger practical risk than a hacker.

  • Moderators

On latency and modes, it helps to separate delay from jitter and to decide where the timing-critical work happens. FT8 and other timed digital modes should have decoding and encoding at the remote end, with that machine's clock disciplined by NTP or similar, instead of streaming audio across the internet and hoping the timing holds. The same logic applies to CW: if you send keying events in real time over a variable connection, element timing can wobble. A local keyer at the radio, fed text or buffered timing information, usually sounds cleaner than raw key-down/key-up over the WAN. Full break-in is the hardest case and may not be pleasant on a long path.

For phone, compressed audio codecs keep the bandwidth modest, but the buffer size is a trade-off. A small buffer reduces delay and risks dropouts; a larger one is smoother but makes conversation feel stilted. Wired Ethernet at both ends and an uncongested uplink matter more than which brand of box you use. Mobile hotspots and busy Wi-Fi are where most bad experiences start.

On rules, the details depend on your country, so read your regulator's text. In the US the relevant material is the telecommand provisions of Part 97, around §97.213. The general ideas are that there must be a control operator, the station must be protected against unauthorized operation, and there must be a means to end transmission if the control link fails. Operating privileges follow the licence of the control operator for that station and band. Contests and awards often have their own rules about remote operation and station location, so check them separately before assuming a remote contact counts. Also keep in mind that encrypting the control link is a different matter from what goes out on the air, where the emission must still comply with the rules on obscured meaning.

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.