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

Pi vs ESP32 vs Pico for shack automation: where do you draw the line, and how do you keep RF out of it?

ci_cover.jpg

A lot of shack automation projects start with the question of which board to use, but a better question is which jobs belong on which board. Antenna switches, rotator control, CAT bridges, SWR/power metering, APRS and CW keying all end up on a bench next to a transmitter, and that environment is harder on cheap microcontroller boards than most tutorials admit.

Here is a rough split worth arguing about. A Raspberry Pi running Linux suits jobs that need a real OS: Direwolf as a software TNC, a logging server, a rigctld instance, or a web dashboard. Direwolf wants a sound interface (a USB sound card or a CM108-type adapter), and it can handle PTT through a GPIO line, a serial RTS/DTR line, or a CM108 GPIO pin. It exposes KISS over TCP (port 8001 by default) and AGW (port 8000), so other software can talk to it over the network instead of needing direct hardware access.

A Pico or an ESP32 suits the deterministic, close-to-the-metal jobs: relay drivers, a CW keyer with proper timing, reading a rotator potentiometer, generating a clock with an Si5351, or polling a temperature sensor. The ESP32 adds Wi-Fi and Bluetooth, which is useful for a remote switch box but also means periodic RF bursts at 2.4 GHz, plus a noisy switching supply, sitting near your receive antenna lines.

The first practical trap is logic levels. The Pico and ESP32 are 3.3 V devices and their GPIO is not 5 V tolerant. Rig CAT ports vary: some are TTL-level serial, some are RS-232 levels, and Icom CI-V is a single-wire open-collector bus. Check the manual for your rig before wiring anything directly. A proper level shifter, or an RS-232 transceiver such as a MAX3232 where the rig needs one, costs very little compared with a dead rig port.

The second trap is RF getting into everything. Common-mode current on USB cables, I2C runs, and relay control leads is the usual culprit, rather than RF coupling into the board itself. Ferrite chokes on cables, short I2C runs with bypass capacitors close to each device, a metal enclosure bonded to station ground, and a decent power supply all help. Spurious resets or phantom button presses during transmit usually point to common-mode problems rather than software bugs.

A few specific items to compare notes on:

Si5351: the outputs are square waves with strong harmonics, so a low-pass filter is needed before using it as a transmit source. Frequency accuracy depends on the reference crystal, so calibration in software matters. Keep the I2C wires short and the supply clean.

SWR meters: a directional coupler with diode detectors works, but the response is non-linear at low power. A log detector such as the AD8307 gives a much wider dynamic range, though either approach needs calibration against a known load and power level.

Rotator controllers: the ESP32's built-in ADC is noticeably non-linear and noisy, so an external ADC (an ADS1115, for example) with some averaging usually gives steadier azimuth readings from a feedback potentiometer. Drive the motor through relays or a driver stage rather than from a GPIO line.

Antenna switches: put flyback diodes across relay coils, use a driver such as a ULN2003 or MOSFETs instead of GPIO pins, and think about whether you ever want the switch to change state while transmitting. Port isolation also falls off with frequency, so check how a relay is rated for the band you care about.

Where do you draw the line between the Linux box and the microcontroller? And what has actually worked for keeping RF out of the control electronics?

  • Replies 2
  • Views 29
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

My rule of thumb is to put anything with a hard timing or safety requirement on a microcontroller and keep Linux out of that path. A CW keyer or a PTT sequencer should still behave if the Pi is rebooting or an SD card has gone read-only. So the Pico or ESP32 does the keying and relay sequencing, and the Pi just sends it commands over serial or the network.

On the PTT side, it's worth adding a hardware timeout so a stuck-high line can't hold the transmitter keyed forever. A simple watchdog or a monostable that must be retriggered will do that. It also means a crashed script doesn't end up with a carrier on the air.

For the CAT bridge, rigctld on the Pi is hard to beat if everything on the network can already talk Hamlib. It lets logging software, digital mode software and a rotator or band-decoder app share one serial connection. Just check that the baud rate and CI-V or CAT address settings match the rig, and avoid two programs polling the radio directly at the same time.

  • Moderators

One thing I'd add on the RF side: treat every cable leaving the box as an antenna and decide up front what happens to it. For a switch box that means a filter or ferrite on each control line, a bypass capacitor where the line enters the enclosure, and a single clear grounding scheme. Daisy-chained grounds that wander around the bench are a common source of ground loops and hum on audio lines too, especially with a Direwolf setup.

For Direwolf specifically, audio level matters more than people expect. Overdriven transmit audio gives wide, splattery packets, and a receive level that's too hot or too low costs decodes. The Direwolf documentation describes using its audio level reporting to set the radio's output and the sound card input, so use that rather than guessing. Isolation transformers on the audio lines between the radio and the sound card are cheap insurance against ground loop noise.

For APRS trackers on an ESP32 or Pico, the main design decisions are the GPS module, the modulation method (many use a PWM or DAC-generated AFSK tone), and how you couple the audio into the radio's mic input with proper attenuation. The usual limits on beacon rate and path settings matter just as much as the electronics, since a badly configured tracker can clog a local frequency.

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.