ⓘ 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
Where do you draw the line between Pico, ESP32 and a Raspberry Pi in a shack automation setup?
Shack automation projects tend to grow in a predictable way. It starts as a CW keyer or an antenna switch, then someone adds CAT control, a rotator interface, an SWR readout, a web page and an APRS gateway. At some point the question is which board should do what, and whether one board should do everything. Here is a framework to argue with.
Hard real-time and electrically "close to the radio" jobs fit a microcontroller well. That means CW keyer timing, PTT sequencing, relay drivers for an antenna switch, reading a rotator potentiometer, and generating a clock with an Si5351. A Pico (RP2040) or an Arduino-class board starts instantly, has no filesystem to corrupt, and behaves the same way every time you power it up. Keyer timing and PTT hang times in particular should not depend on a Linux scheduler.
Anything involving networking, logging, a web UI, or running existing software fits a Raspberry Pi better. Direwolf, Hamlib's rigctld, a logging program and a small web dashboard all run comfortably there. A common split is a Pi handling Direwolf (soundcard in and out, KISS over TCP on 8001 or AGW on 8000, PTT through GPIO or a CM108-type USB audio adapter), while a separate microcontroller handles anything that must be deterministic.
The ESP32 sits in the middle. It has Wi-Fi and Bluetooth built in, which is convenient for a remote antenna switch or a rotator controller in the garden. But the radio is on the same chip as your logic, so you are putting a transmitter next to a rig that may be running 100 W. The ADC is also known for being nonlinear, so if you want a decent SWR or voltage readout, use an external ADC such as an ADS1115 rather than relying on the internal one.
Voltage levels cause more problems than code does. Pico and ESP32 GPIOs are 3.3 V and not 5 V tolerant. Many rigs expose CAT as true RS-232 levels, some as 5 V TTL, and others over USB. Do not wire any of those straight to a GPIO. Use a proper level shifter or a MAX3232-type converter for RS-232, and a transistor or optocoupler for PTT lines. Si5351 modules are fine at 3.3 V logic, but remember the output is a square wave, so it needs a low-pass filter before it goes near an antenna or a mixer.
Then there is RF getting into the electronics. Symptoms include an LCD that fills with garbage when you key up on 40 m, a keyer that sends stray dits, or an I2C bus that hangs. The usual fixes are ferrites on the USB and power leads, short I2C runs, a metal enclosure bonded to the station ground, bypass capacitors at the connectors, and flyback diodes across relay coils. Test it with a dummy load first, then with the real antenna.
So what do you use as your dividing line? Do you keep PTT and keying on a dedicated microcontroller and treat the Pi as optional, or does the Pi own the whole chain? And has anyone settled on a good way to isolate the Pi's USB audio from RF pickup in a crowded shack?
Shack automation projects tend to grow in a predictable way. It starts as a CW keyer or an antenna switch, then someone adds CAT control, a rotator interface, an SWR readout, a web page and an APRS gateway. At some point the question is which board should do what, and whether one board should do everything. Here is a framework to argue with.
Hard real-time and electrically "close to the radio" jobs fit a microcontroller well. That means CW keyer timing, PTT sequencing, relay drivers for an antenna switch, reading a rotator potentiometer, and generating a clock with an Si5351. A Pico (RP2040) or an Arduino-class board starts instantly, has no filesystem to corrupt, and behaves the same way every time you power it up. Keyer timing and PTT hang times in particular should not depend on a Linux scheduler.
Anything involving networking, logging, a web UI, or running existing software fits a Raspberry Pi better. Direwolf, Hamlib's rigctld, a logging program and a small web dashboard all run comfortably there. A common split is a Pi handling Direwolf (soundcard in and out, KISS over TCP on 8001 or AGW on 8000, PTT through GPIO or a CM108-type USB audio adapter), while a separate microcontroller handles anything that must be deterministic.
The ESP32 sits in the middle. It has Wi-Fi and Bluetooth built in, which is convenient for a remote antenna switch or a rotator controller in the garden. But the radio is on the same chip as your logic, so you are putting a transmitter next to a rig that may be running 100 W. The ADC is also known for being nonlinear, so if you want a decent SWR or voltage readout, use an external ADC such as an ADS1115 rather than relying on the internal one.
Voltage levels cause more problems than code does. Pico and ESP32 GPIOs are 3.3 V and not 5 V tolerant. Many rigs expose CAT as true RS-232 levels, some as 5 V TTL, and others over USB. Do not wire any of those straight to a GPIO. Use a proper level shifter or a MAX3232-type converter for RS-232, and a transistor or optocoupler for PTT lines. Si5351 modules are fine at 3.3 V logic, but remember the output is a square wave, so it needs a low-pass filter before it goes near an antenna or a mixer.
Then there is RF getting into the electronics. Symptoms include an LCD that fills with garbage when you key up on 40 m, a keyer that sends stray dits, or an I2C bus that hangs. The usual fixes are ferrites on the USB and power leads, short I2C runs, a metal enclosure bonded to the station ground, bypass capacitors at the connectors, and flyback diodes across relay coils. Test it with a dummy load first, then with the real antenna.
So what do you use as your dividing line? Do you keep PTT and keying on a dedicated microcontroller and treat the Pi as optional, or does the Pi own the whole chain? And has anyone settled on a good way to isolate the Pi's USB audio from RF pickup in a crowded shack?
Link to comment
https://www.hamradiobase.com/forums/topic/10872-where-do-you-draw-the-line-between-pico-esp32-and-a-raspberry-pi-in-a-shack-automation-setup/Share on other sites