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

Building a remote station: IC-7610/RS-BA1 vs SCU-LAN10 vs Flex vs RigPi, and how to handle latency, security and the rules

ci_cover.jpg

I'd like to compare approaches to remote station control. Mixing receive-only tools like WebSDR and KiwiSDR with full transmit-capable remote bases tends to blur some important differences, so here is how I'd split the field.

WebSDR and KiwiSDR are receive-only. A WebSDR (the Twente-style software) and a KiwiSDR (a 0-30 MHz SDR cape with a browser interface) let you listen from a distance, check propagation, or use someone else's quiet receive site. They are useful for checking whether your signal is being heard, but they do not involve remote transmitter control, so licensing and control-operator issues mostly don't apply.

Then there are the transmit-capable options. Icom's IC-7610 has a network connection and works with Icom's RS-BA1 software for remote control and audio. Yaesu's SCU-LAN10 is a network interface for certain Yaesu radios, so check Yaesu's current compatibility list for your model. FlexRadio is a different architecture. The radio is already a network device, and SmartSDR with SmartLink is built around remote use. RigPi is a Raspberry Pi-based station controller that talks to the rig through Hamlib-style control and can also manage things like rotators and switching. Services such as RemoteHams.com sit on the community side, listing or brokering access to remote stations. Check their current terms and supported setups before relying on them.

The questions I'd like to discuss are these. Where should the intelligence live: in the radio, in a small computer at the remote site, or in a vendor application? How much latency is acceptable for SSB, CW and digital modes? What is the minimum safe network design? And what does your licence actually require when you are not in the shack?

I'm interested in practical design notes more than brand loyalty. If you have a setup with a failure mode worth knowing about, such as a stuck PTT, a dropped VPN or a firmware surprise, please describe it in general terms.

  • Replies 2
  • Views 36
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On latency, it helps to separate what each mode actually needs. SSB tolerates a fairly large round-trip delay because the conversation is half-duplex in practice. The annoying part is usually jitter, not the average delay. A jittery connection forces a larger audio buffer, and then the delay creeps up. Wired internet at both ends beats Wi-Fi or a congested mobile link almost every time, and codec and buffer settings in the remote software often matter as much as raw ping time.

CW is the harder one. Streaming your audio sidetone back from the remote radio means you hear the delayed version of your own keying, which is disorienting. Better designs send keying as timed events to a keyer at the radio end, or let you monitor a local sidetone while the remote radio does the real keying. Full break-in is realistic only with a very low and stable round-trip time, so many operators accept semi-break-in for remote CW.

For FT8 and other timed digital modes, run the decoder and the software at the remote site, either on a PC beside the radio or on something like a RigPi-style controller, and remote into that machine's desktop. Then the timing-sensitive part (clock sync, audio to the rig) stays local and only the screen traffic crosses the internet. If you stream audio from the remote end into a PC at home instead, the added delay and clock drift can cost you decodes. Keep NTP or another time source healthy at whichever end runs the mode.

One architecture point on the radio options. With the IC-7610 and RS-BA1 or the SCU-LAN10, the vendor software is the glue, and you depend on it for audio, CAT and PTT behavior. With a Flex, the radio itself handles network streaming and SmartLink handles the connection setup. With a Pi-based controller, you have more flexibility and more to maintain. None of them is automatically best. Match the choice to how much maintenance you want to do at a site you may not be able to visit.

  • Moderators

On security, the main rule is not to expose a radio's control port directly to the internet. Most rigs and network adapters were not designed to face hostile traffic. Plain port-forwarding to a transceiver, a Pi or a desktop with VNC or RDP open is the classic way to get scanned and attacked within hours. A VPN into the remote site is the safer baseline. WireGuard or a mesh VPN such as Tailscale are common choices, and a router with a VPN server works too. Then you reach the radio, controller and PDU over a private tunnel instead of publishing them. If a vendor feature does require inbound connectivity, read exactly which ports and protocols it uses and restrict them as tightly as you can.

Beyond that: put station gear on its own VLAN or at least its own subnet, use unique strong passwords and change defaults on the router, Pi and any web interface, keep firmware and OS updates current, and turn off services you don't use. Also plan for the day the link dies mid-transmission. Use the radio's transmit time-out timer, a watchdog that drops PTT or power if the control session disappears, an SWR and power protection plan for the amplifier, and a remote power switch on separate out-of-band access, such as a cellular backup, so you can reboot or cut power to a stuck system.

On the rules, I can't give a universal answer, because they depend on your country and licence class. The common principles tend to be these: the licensee or control operator remains responsible for the emissions, you need a reliable way to stop the transmitter if something goes wrong, identification and band-plan rules still apply, and your privileges are those of your licence at the location of the transmitter. Operating a station in another country can raise additional issues. Reciprocal or CEPT-style arrangements may not clearly cover remote operation, and some regulators have specific remote-control provisions. If you are lending out your station or using a third-party remote base through a service like RemoteHams.com, you should also check who counts as the control operator and what the host or service requires. Read your regulator's current text rather than relying on forum summaries, including this one, and ask the regulator or your national society if something is ambiguous.

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.