ⓘ 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 — 70cmvia PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHzDXSpotterInfo
Recent spots—
Select a band above to load spots
Ready — select a band to fetch live spots
Which microcontroller for shack automation? Pico vs ESP32 vs Arduino, and keeping RF out of it
I'm planning a batch of small shack projects and want to settle on a platform before I build a pile of incompatible boards. The list: a CAT bridge for an HF rig, an antenna switch with relay control, a forward/reflected power meter, a Si5351 VFO/beacon source, and eventually an APRS tracker and a Direwolf node on a Pi. I'd like to hear how others split the work between an Arduino-class board, a Pi Pico, an ESP32 and a full Raspberry Pi.
Here is my current thinking, and please correct it where it's wrong. A Pi (running Linux) makes sense where you want an audio interface and network services: Direwolf with a USB sound card or CM108-type adapter, KISS over TCP on port 8001, and Hamlib's rigctld/rotctld to share rig and rotator control over the LAN. A microcontroller makes more sense for anything timing-sensitive or hardware-facing: keyer timing, relay sequencing, reading a detector voltage, driving an LCD, or generating a clock with a Si5351.
Between the microcontrollers, the Pico looks attractive for deterministic I/O, and its PIO blocks are handy for odd serial protocols. The ESP32 gives Wi-Fi and Bluetooth for free, but I'm wary of putting a Wi-Fi radio inches from a receiver. The classic 5 V Arduino boards are easy to work with, but I keep having to remind myself that the Pico and ESP32 are 3.3 V devices and their GPIOs are not 5 V tolerant.
That last point matters for CAT. Rigs differ a lot: some older Yaesu radios use 5 V TTL-level serial, Icom CI-V is a single-wire open-collector bus with an address byte for each radio, and many Kenwood and Elecraft rigs offer true RS-232 levels on a DB9. Those levels shouldn't go straight into a 3.3 V pin, and RS-232 shouldn't go into any logic pin at all. A MAX3232 handles RS-232, while a transistor or a proper level shifter handles TTL and CI-V. Check your rig's manual for the voltage and polarity before you connect anything.
The other big question is RF immunity. What's your approach to enclosures, ferrites on USB and control lines, and bypassing relay and sensor wiring, so the controller doesn't reset or report nonsense when you key up on 80 m into a marginal antenna?
I'm planning a batch of small shack projects and want to settle on a platform before I build a pile of incompatible boards. The list: a CAT bridge for an HF rig, an antenna switch with relay control, a forward/reflected power meter, a Si5351 VFO/beacon source, and eventually an APRS tracker and a Direwolf node on a Pi. I'd like to hear how others split the work between an Arduino-class board, a Pi Pico, an ESP32 and a full Raspberry Pi.
Here is my current thinking, and please correct it where it's wrong. A Pi (running Linux) makes sense where you want an audio interface and network services: Direwolf with a USB sound card or CM108-type adapter, KISS over TCP on port 8001, and Hamlib's rigctld/rotctld to share rig and rotator control over the LAN. A microcontroller makes more sense for anything timing-sensitive or hardware-facing: keyer timing, relay sequencing, reading a detector voltage, driving an LCD, or generating a clock with a Si5351.
Between the microcontrollers, the Pico looks attractive for deterministic I/O, and its PIO blocks are handy for odd serial protocols. The ESP32 gives Wi-Fi and Bluetooth for free, but I'm wary of putting a Wi-Fi radio inches from a receiver. The classic 5 V Arduino boards are easy to work with, but I keep having to remind myself that the Pico and ESP32 are 3.3 V devices and their GPIOs are not 5 V tolerant.
That last point matters for CAT. Rigs differ a lot: some older Yaesu radios use 5 V TTL-level serial, Icom CI-V is a single-wire open-collector bus with an address byte for each radio, and many Kenwood and Elecraft rigs offer true RS-232 levels on a DB9. Those levels shouldn't go straight into a 3.3 V pin, and RS-232 shouldn't go into any logic pin at all. A MAX3232 handles RS-232, while a transistor or a proper level shifter handles TTL and CI-V. Check your rig's manual for the voltage and polarity before you connect anything.
The other big question is RF immunity. What's your approach to enclosures, ferrites on USB and control lines, and bypassing relay and sensor wiring, so the controller doesn't reset or report nonsense when you key up on 80 m into a marginal antenna?
Link to comment
https://www.hamradiobase.com/forums/topic/11009-which-microcontroller-for-shack-automation-pico-vs-esp32-vs-arduino-and-keeping-rf-out-of-it/Share on other sites