ⓘ 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
Pico, ESP32 or Pi for shack automation: where do you draw the line with RF and CAT control?
I'm planning a few shack automation projects and want to sort out the architecture before building anything: a rotator controller, a remote antenna switch, an SWR/power meter, CAT logging, and maybe a Direwolf APRS station. The question is what should run on what.
The rough split I'm considering looks like this:
Raspberry Pi (Linux): Direwolf, Hamlib's rigctld and rotctld, logging software, and a web dashboard. It's good for anything that needs a sound card, networking, or several services running at once.
Pi Pico (RP2040): the real-time and I/O work. That means CW keyer timing, relay and band-decoder outputs, ADC reads for the SWR meter, and Si5351 control. It has no radio of its own, which is a plus near HF, and its timing is predictable.
ESP32: only where Wi-Fi or Bluetooth is actually needed, such as a remote antenna switch or a sensor node outside. I'd keep it away from the operating position and the feedline if possible.
The points I most want to get right are these:
1. Logic levels. The Pico and ESP32 are 3.3 V devices, and the RP2040 GPIOs are not 5 V tolerant. Some rigs use 5 V TTL serial, Kenwood and Elecraft ports are typically RS-232 levels (so you need a proper level converter, not just a divider), and Icom CI-V is a single-wire bus. Check the manual for your exact rig before wiring anything directly.
2. RF getting into the electronics. At 100 W, a cheap microcontroller board on a long USB cable can misbehave. Typical symptoms are resets, garbage on the I2C bus, or an LCD that fills with junk when you key up. Ferrite on the cables, a decent shield box, and bypass caps on sensor lines are the usual fixes, but I'd like to hear what actually works.
3. Ground loops and PTT. For Direwolf PTT, I'm leaning toward an optocoupler or a CM108-style GPIO and isolated audio, rather than a straight GPIO to the rig's PTT line.
4. Relays. For the antenna switch I'd use RF-rated relays with a driver like a ULN2003 or a MOSFET, plus flyback diodes. I'd also check isolation between ports at the highest frequency I plan to use, since a relay that's fine on 40 m may leak badly on 2 m.
Does this split make sense? Where would you put the line between Pi, Pico and ESP32, and what's the first RF-hardening step you'd take?
I'm planning a few shack automation projects and want to sort out the architecture before building anything: a rotator controller, a remote antenna switch, an SWR/power meter, CAT logging, and maybe a Direwolf APRS station. The question is what should run on what.
The rough split I'm considering looks like this:
Raspberry Pi (Linux): Direwolf, Hamlib's rigctld and rotctld, logging software, and a web dashboard. It's good for anything that needs a sound card, networking, or several services running at once.
Pi Pico (RP2040): the real-time and I/O work. That means CW keyer timing, relay and band-decoder outputs, ADC reads for the SWR meter, and Si5351 control. It has no radio of its own, which is a plus near HF, and its timing is predictable.
ESP32: only where Wi-Fi or Bluetooth is actually needed, such as a remote antenna switch or a sensor node outside. I'd keep it away from the operating position and the feedline if possible.
The points I most want to get right are these:
1. Logic levels. The Pico and ESP32 are 3.3 V devices, and the RP2040 GPIOs are not 5 V tolerant. Some rigs use 5 V TTL serial, Kenwood and Elecraft ports are typically RS-232 levels (so you need a proper level converter, not just a divider), and Icom CI-V is a single-wire bus. Check the manual for your exact rig before wiring anything directly.
2. RF getting into the electronics. At 100 W, a cheap microcontroller board on a long USB cable can misbehave. Typical symptoms are resets, garbage on the I2C bus, or an LCD that fills with junk when you key up. Ferrite on the cables, a decent shield box, and bypass caps on sensor lines are the usual fixes, but I'd like to hear what actually works.
3. Ground loops and PTT. For Direwolf PTT, I'm leaning toward an optocoupler or a CM108-style GPIO and isolated audio, rather than a straight GPIO to the rig's PTT line.
4. Relays. For the antenna switch I'd use RF-rated relays with a driver like a ULN2003 or a MOSFET, plus flyback diodes. I'd also check isolation between ports at the highest frequency I plan to use, since a relay that's fine on 40 m may leak badly on 2 m.
Does this split make sense? Where would you put the line between Pi, Pico and ESP32, and what's the first RF-hardening step you'd take?
Link to comment
https://www.hamradiobase.com/forums/topic/11725-pico-esp32-or-pi-for-shack-automation-where-do-you-draw-the-line-with-rf-and-cat-control/Share on other sites