ⓘ 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
Splitting shack automation between a Raspberry Pi and microcontrollers: what goes where?
I'm planning a shack controller and want to settle the architecture before I solder anything. The wish list: CAT rig control, a rotator controller, a relay-based antenna switch, a simple SWR/power readout, a CW keyer, and a Direwolf APRS station for VHF. Possibly a Si5351 as a test signal source later.
My current idea is a Raspberry Pi running Hamlib (rigctld), Direwolf and logging software, with one or two microcontrollers (Pi Pico or ESP32) handling the hardware-facing jobs. The Pi would talk to them over USB serial or MQTT. I'd like opinions on a few points:
1. Is it sensible to keep anything timing-critical (CW keying, relay sequencing, PTT interlocks) off the Pi entirely?
2. For CAT, is it better to give the rig one owner, such as rigctld, and have everything else talk to that?
3. How do you keep RF out of the microcontrollers when running power on HF? Pico or ESP32, I'm thinking of a metal enclosure plus ferrites, but I'm not sure that's enough.
4. For the rotator and SWR meter, is the built-in ADC good enough, or should I use an external one?
Any gotchas on levels, grounding or Direwolf PTT are welcome too.
I'm planning a shack controller and want to settle the architecture before I solder anything. The wish list: CAT rig control, a rotator controller, a relay-based antenna switch, a simple SWR/power readout, a CW keyer, and a Direwolf APRS station for VHF. Possibly a Si5351 as a test signal source later.
My current idea is a Raspberry Pi running Hamlib (rigctld), Direwolf and logging software, with one or two microcontrollers (Pi Pico or ESP32) handling the hardware-facing jobs. The Pi would talk to them over USB serial or MQTT. I'd like opinions on a few points:
1. Is it sensible to keep anything timing-critical (CW keying, relay sequencing, PTT interlocks) off the Pi entirely?
2. For CAT, is it better to give the rig one owner, such as rigctld, and have everything else talk to that?
3. How do you keep RF out of the microcontrollers when running power on HF? Pico or ESP32, I'm thinking of a metal enclosure plus ferrites, but I'm not sure that's enough.
4. For the rotator and SWR meter, is the built-in ADC good enough, or should I use an external one?
Any gotchas on levels, grounding or Direwolf PTT are welcome too.
Link to comment
https://www.hamradiobase.com/forums/topic/11512-splitting-shack-automation-between-a-raspberry-pi-and-microcontrollers-what-goes-where/Share on other sites