Pi, Pico or ESP32 for shack automation? Where to split the work between CAT, PTT, relays and Direwolf
- Replies 2
- Views 60
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
I'd like to compare notes on architecture before committing to a design. The goal is one coherent shack-automation setup rather than five unrelated gadgets. The wish list is CAT rig control, a Direwolf TNC for APRS, an antenna switch, a rotator controller, and maybe a Si5351-based signal source or a small CW keyer. All of it needs to behave when a few hundred watts are running nearby.
There are two obvious approaches. One is a single Raspberry Pi doing everything: Direwolf, rigctld (Hamlib), logging, a web UI, and GPIO for relays and PTT. The other is a Pi for the heavy software (Direwolf, logging, network access) plus one or more microcontrollers (Pico, Pico W or ESP32) that own the hardware-facing jobs: relay drivers, ADC readings for rotator position or forward and reflected power, and keyer timing.
The split makes sense to me because Linux is not a real-time system. A CW keyer or a PTT sequencer that has to open a relay before RF appears should not depend on a Pi's scheduler, an SD card, or a USB audio device re-enumerating. A microcontroller can enforce hard rules in firmware, such as never switching the antenna relay while PTT is asserted, and it keeps working if the Pi hangs.
Here are the specific points I'd like opinions on:
1. Voltage levels on CAT. The Pico and ESP32 are 3.3 V devices and their GPIOs are not meant to see 5 V. Rig CAT ports vary: some are TTL-level serial, some are true RS-232, and Icom's CI-V is a single-wire open-collector bus. Each needs a different interface. What do people use for level shifting and isolation so they don't have to guess per rig?
2. PTT and keying. Between optocouplers, small transistors and relays, what is the best way to key a rig without creating a ground loop? Direwolf can use GPIO, serial RTS/DTR, or CM108-style USB audio GPIO for PTT, so there are several clean options on the Pi side.
3. Analog measurements. The ESP32's built-in ADC is known for its non-linearity, and the Pico's ADC is only as quiet as its supply and layout. For a rotator potentiometer or an SWR bridge detector, is an external ADC like the ADS1115 worth it?
4. RF immunity. Sooner or later a transmitter will make a microcontroller reset, corrupt an LCD, or turn an I2C bus into an antenna. What actually helps: ferrites, bypass caps, shielded boxes, shorter I2C runs, watchdogs?
Link to comment
https://www.hamradiobase.com/forums/topic/10954-pi-pico-or-esp32-for-shack-automation-where-to-split-the-work-between-cat-ptt-relays-and-direwolf/Share on other sites