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

Where do you draw the line between Pico, ESP32 and a Raspberry Pi in a shack automation setup?

ci_cover.jpg

Shack automation projects tend to grow in a predictable way. It starts as a CW keyer or an antenna switch, then someone adds CAT control, a rotator interface, an SWR readout, a web page and an APRS gateway. At some point the question is which board should do what, and whether one board should do everything. Here is a framework to argue with.

Hard real-time and electrically "close to the radio" jobs fit a microcontroller well. That means CW keyer timing, PTT sequencing, relay drivers for an antenna switch, reading a rotator potentiometer, and generating a clock with an Si5351. A Pico (RP2040) or an Arduino-class board starts instantly, has no filesystem to corrupt, and behaves the same way every time you power it up. Keyer timing and PTT hang times in particular should not depend on a Linux scheduler.

Anything involving networking, logging, a web UI, or running existing software fits a Raspberry Pi better. Direwolf, Hamlib's rigctld, a logging program and a small web dashboard all run comfortably there. A common split is a Pi handling Direwolf (soundcard in and out, KISS over TCP on 8001 or AGW on 8000, PTT through GPIO or a CM108-type USB audio adapter), while a separate microcontroller handles anything that must be deterministic.

The ESP32 sits in the middle. It has Wi-Fi and Bluetooth built in, which is convenient for a remote antenna switch or a rotator controller in the garden. But the radio is on the same chip as your logic, so you are putting a transmitter next to a rig that may be running 100 W. The ADC is also known for being nonlinear, so if you want a decent SWR or voltage readout, use an external ADC such as an ADS1115 rather than relying on the internal one.

Voltage levels cause more problems than code does. Pico and ESP32 GPIOs are 3.3 V and not 5 V tolerant. Many rigs expose CAT as true RS-232 levels, some as 5 V TTL, and others over USB. Do not wire any of those straight to a GPIO. Use a proper level shifter or a MAX3232-type converter for RS-232, and a transistor or optocoupler for PTT lines. Si5351 modules are fine at 3.3 V logic, but remember the output is a square wave, so it needs a low-pass filter before it goes near an antenna or a mixer.

Then there is RF getting into the electronics. Symptoms include an LCD that fills with garbage when you key up on 40 m, a keyer that sends stray dits, or an I2C bus that hangs. The usual fixes are ferrites on the USB and power leads, short I2C runs, a metal enclosure bonded to the station ground, bypass capacitors at the connectors, and flyback diodes across relay coils. Test it with a dummy load first, then with the real antenna.

So what do you use as your dividing line? Do you keep PTT and keying on a dedicated microcontroller and treat the Pi as optional, or does the Pi own the whole chain? And has anyone settled on a good way to isolate the Pi's USB audio from RF pickup in a crowded shack?

  • Replies 2
  • Views 33
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

I'd keep PTT and keying on the microcontroller, and treat the Pi as a convenience layer. If the Pi crashes, hangs during an update, or loses its SD card, you don't want a stuck PTT line. A simple hardware safeguard helps a lot here. A transmit timeout on the microcontroller, or a hardware watchdog that drops the PTT transistor if it stops seeing heartbeats, protects the final amplifier and keeps you from jamming a frequency by accident. Direwolf's GPIO PTT works fine for casual packet use, but for a station that transmits unattended, an independent timeout is worth having.

For the CAT side, a Pico or Arduino can sit between the rig and the Pi as a small serial bridge, and rigctld can talk to the Pi side. That also keeps level shifting and isolation on the radio side, rather than relying on whatever the USB-serial dongle happens to do.

  • Moderators

On the audio question, ground loops and RF pickup are the most common reason a Direwolf setup decodes poorly or sends distorted audio. A cheap USB sound card plugged straight into the rig's data port with a long unshielded lead will often hum or pick up RF. Things that usually help are a 1:1 audio isolation transformer on both the RX and TX audio lines, a ferrite on the USB cable, and keeping the TX audio level low enough that the rig isn't overdriven. Many TNC problems are really level problems, since too much audio into a rig's mic or data input produces splatter and bad packets, even though the software is working correctly.

If you use a CM108-style adapter for PTT, check which GPIO pin your particular adapter exposes, because the pin numbering and wiring differ between boards. And Wi-Fi or Bluetooth radios on the Pi can be disabled in software if you don't need them, which removes one more source of interference near sensitive receive audio.

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.