Splitting shack automation between Pi, Pico and ESP32: what belongs where?
- Replies 2
- Views 30
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Mod_Chrissy 1 post
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
A lot of shack-automation projects start as one small gadget and grow into a pile of boards: a CAT interface, a remote antenna switch, a rotator controller, an SWR/power meter, a CW keyer, an APRS tracker or digipeater running Direwolf, and maybe an Si5351 for a VFO or test oscillator. The first design question is usually which board should do which job, and whether one board should do all of them.
Here is a rough framework to argue with.
Linux SBC (Raspberry Pi): good for anything that needs a network stack, a filesystem, USB audio or a lot of software. Direwolf, Hamlib's rigctld, logging software, a web dashboard and an MQTT broker all fit here. It is a poor choice for hard timing (CW keying, PTT sequencing) and for directly driving relays or sensors, because GPIO is 3.3 V with little protection and a Linux userspace process can be delayed by the scheduler.
Pi Pico (RP2040): deterministic timing, cheap, and PIO is useful for odd protocols. It suits a CW keyer, a PTT sequencer, a rotator motor controller or a stepper driver. WiFi is only available on the W variants, and the 12-bit ADC is noisy enough that I would not use it as-is for anything that needs real accuracy.
ESP32: WiFi and Bluetooth built in, so it suits remote nodes such as an antenna switch at the tower base, temperature and voltage monitoring, or a web UI for a rotator. The on-chip ADC is nonlinear and noisy, and ADC2 conflicts with WiFi on the original ESP32. For SWR, power or rotator-position readings, an external ADC such as an ADS1115 is often the cleaner answer.
Some specific points where these projects tend to go wrong:
Questions for the group: do you prefer one central Pi with small microcontroller nodes talking over serial, MQTT or USB, or are independent nodes better so a Pi reboot never leaves a relay stuck? And how are people handling fail-safe states, such as what the antenna switch, PTT line and rotator do if the controller crashes?
Link to comment
https://www.hamradiobase.com/forums/topic/11415-splitting-shack-automation-between-pi-pico-and-esp32-what-belongs-where/Share on other sites