Remote station design: rig-side hardware, latency, security and licensing for a remote-controlled HF setup
- Replies 2
- Views 28
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Mod_Chrissy 1 post
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.
Link to comment
https://www.hamradiobase.com/forums/topic/11465-remote-station-design-rig-side-hardware-latency-security-and-licensing-for-a-remote-controlled-hf-setup/Share on other sites