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

Pico, ESP32 or Pi for shack automation: where do you draw the line with RF and CAT control?

ci_cover.jpg

I'm planning a few shack automation projects and want to sort out the architecture before building anything: a rotator controller, a remote antenna switch, an SWR/power meter, CAT logging, and maybe a Direwolf APRS station. The question is what should run on what.

The rough split I'm considering looks like this:

Raspberry Pi (Linux): Direwolf, Hamlib's rigctld and rotctld, logging software, and a web dashboard. It's good for anything that needs a sound card, networking, or several services running at once.

Pi Pico (RP2040): the real-time and I/O work. That means CW keyer timing, relay and band-decoder outputs, ADC reads for the SWR meter, and Si5351 control. It has no radio of its own, which is a plus near HF, and its timing is predictable.

ESP32: only where Wi-Fi or Bluetooth is actually needed, such as a remote antenna switch or a sensor node outside. I'd keep it away from the operating position and the feedline if possible.

The points I most want to get right are these:

1. Logic levels. The Pico and ESP32 are 3.3 V devices, and the RP2040 GPIOs are not 5 V tolerant. Some rigs use 5 V TTL serial, Kenwood and Elecraft ports are typically RS-232 levels (so you need a proper level converter, not just a divider), and Icom CI-V is a single-wire bus. Check the manual for your exact rig before wiring anything directly.

2. RF getting into the electronics. At 100 W, a cheap microcontroller board on a long USB cable can misbehave. Typical symptoms are resets, garbage on the I2C bus, or an LCD that fills with junk when you key up. Ferrite on the cables, a decent shield box, and bypass caps on sensor lines are the usual fixes, but I'd like to hear what actually works.

3. Ground loops and PTT. For Direwolf PTT, I'm leaning toward an optocoupler or a CM108-style GPIO and isolated audio, rather than a straight GPIO to the rig's PTT line.

4. Relays. For the antenna switch I'd use RF-rated relays with a driver like a ULN2003 or a MOSFET, plus flyback diodes. I'd also check isolation between ports at the highest frequency I plan to use, since a relay that's fine on 40 m may leak badly on 2 m.

Does this split make sense? Where would you put the line between Pi, Pico and ESP32, and what's the first RF-hardening step you'd take?

  • Replies 2
  • Views 15
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

The split sounds sensible. I'd add one rule: anything that can damage something if it hangs should not depend on Linux. Keep the Pico (or a simple hardware path) in charge of PTT lines, relay states and any amplifier or antenna safety interlock. If the Pi is rebooting or a service crashes, the outputs should fall back to a safe state, which usually means receive and antenna grounded or selected by default. A watchdog on the Pico helps a lot here, and so does a pull-down or pull-up on each output so the relay doesn't chatter while the board boots.

For the RF issue, I'd treat the cables as antennas. Common-mode chokes on USB and control leads, short runs to the rig, and a single-point ground at the operating position cover most cases. If you have a long USB run between the Pi and the rig, a USB isolator can also keep ground-loop hum out of Direwolf audio. For an SWR meter, put the detector right at the coupler and send a low-impedance DC voltage down the cable, not RF. Then filter it at the ADC input.

  • Moderators

I'd question the plan for the ESP32. It's useful, but it's easy to overuse. A Wi-Fi-connected antenna switch is convenient, though you're then putting network access on something that switches antennas. At minimum, keep it on a separate VLAN or use a local-only protocol, and don't expose it to the internet. For a remote switch, a wired Ethernet-to-serial or a Pico with an isolated serial link may be more robust than Wi-Fi at the far end of a yard.

For the rig side, Hamlib is worth using even for small projects. Let rigctld own the serial port and have everything else (logger, dashboard, band decoder) talk to it over TCP. That avoids two programs fighting over one CAT port. The same goes for rotators: Hamlib's rotctld can sit between your software and a controller that speaks a common protocol such as GS-232, so you can swap hardware later without rewriting your software.

On Si5351 and APRS trackers, remember the Si5351 outputs a square wave, so any transmit use needs proper low-pass filtering and a check of harmonics. Don't run it into an antenna directly. For a tracker, be sure you know the rules for your license and for power output before you transmit anything.

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.