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 RS-BA1, Yaesu SCU-LAN10, FlexRadio, RigPi and Kiwi/WebSDR, and what to get right on security, latency and rules

ci_cover.jpg

Remote operation gets discussed as if it were one thing, but there are at least three different setups. It helps to separate them before arguing about gear.

1. Receive-only remote access. WebSDR and KiwiSDR sites are shared receivers. You tune a browser, nobody needs a control operator, and you cannot transmit. They are still handy for a home station. Pick a Kiwi or WebSDR near your target area and use it to check your own signal or the band conditions. Remember that the stream has its own delay, so it will not tell you much about QSK or timing.

2. Your own rig at your own remote site. This is where the vendor ecosystems differ. The IC-7610 has Ethernet and works with Icom's RS-BA1 remote software. Open-source clients such as wfview also target Icom LAN radios. Yaesu's SCU-LAN10 is a hardware bridge that puts CAT and audio on the network for supported Yaesu radios, so check Yaesu's compatibility list for your exact model. FlexRadio is architected differently. The radio is already a network device, and SmartLink handles remote connections with account authentication. RigPi takes a third approach: a Raspberry Pi acting as a station server, usually with Hamlib-based rig control and a web interface, which you then pair with audio and PTT handling of your choosing.

3. Hosted or shared remote stations. RemoteHams.com is the example in this category. It lists and connects remote-capable stations. Read the host's terms, because the licensing and control-operator questions are different when the station is not yours.

Three topics keep causing trouble, so here is a starting point for each.

Security. Avoid forwarding rig control ports straight to the internet. Icom LAN radios use a small block of UDP ports for control, serial and audio, and those protocols were not designed to be hostile-internet facing. A VPN such as WireGuard into the shack LAN is the conservative approach. Separate the radio gear onto its own VLAN or subnet, change default credentials, keep firmware current, and remember that a Pi running remote desktop is a general-purpose computer on your network.

Latency. SSB tolerates a fair amount of delay, but full break-in CW does not. The usual solution is to run the keyer at the radio end and send text or keying events instead of audio, with the sidetone generated locally. For digital modes, run WSJT-X at the station and remote-desktop to it, so the decode timing doesn't depend on your link.

Rules. The control operator must be able to switch the transmitter off, and the licensee stays responsible. In the US that means looking at Part 97, particularly the station control and telecommand provisions. Other countries differ, and operating a station located in a different country than you may not be covered by your own licence. Awards and contests have their own remote-operation clauses too. Read the current rules for each before assuming your setup counts.

What does a safe failure mode look like for each of these? If the link drops while keyed, what stops the transmitter?

  • Replies 2
  • Views 116
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the failure mode question, the answer needs to be layered, and the network software shouldn't be the only layer. A transmit timeout in the radio is the first one. Many rigs have a TOT setting, and it is worth setting even though it is crude. Next is a heartbeat or watchdog in the remote software, so that loss of the control connection drops PTT. Finally there is hardware you can reach out of band: a network-controlled power switch for the radio and amplifier, ideally on a different path than the main link, such as a cellular backup or a separate switch on the router. The amplifier is the item people forget. If your remote setup includes a linear, think about what it does when the exciter goes silent, when SWR rises, or when the antenna tuner is in an unknown state.

I would also push back a little on the idea that a VPN settles the matter. It reduces exposure, but it does not fix weak passwords on the Pi or on the radio's own network login, and it does not fix a client PC that is already compromised. Treat the remote client like a key to the shack.

  • Moderators

One thing worth adding on the Flex and Icom comparison is where the trust sits. With SmartLink, authentication goes through a vendor-run service, so you are depending on that service and on how you configure NAT or UPnP. With RS-BA1 or wfview you are usually on your own for how traffic reaches the radio, which is more work but also more control, and it fits neatly with the VPN approach. Neither is automatically better. It depends on whether you want to maintain a VPN or prefer the vendor's account model.

On latency, I would measure before assuming. Ping time to the shack is only part of it, because audio codec settings, buffer sizes and jitter all add to the round trip you perceive. A link that shows a modest ping can still feel sluggish for a net or a pileup if the audio buffer is large. Try different codec and buffer settings, and test with the kind of operating you actually do. A DX pileup, a casual SSB rag chew and a CW contest each stress the link differently.

As for rules, the practical step is to write down where the transmitter, the antenna and the control operator each are, and then check that against your licence terms and any award or contest you care about. Those three locations are what the rules usually ask about, and the answer isn't the same everywhere.

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.