Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ 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 — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

Shack controllers that glitch or reset when you transmit: ESP32, Pico and CAT builds

ci_cover.jpg

A common pattern in shack automation projects: the ESP32 or Pico board works perfectly on the bench, then misbehaves as soon as the rig is keyed into a real antenna. Typical symptoms are the display filling with garbage, the CAT link dropping, a rotator controller reading the wrong bearing, or the board rebooting on SSB peaks but not on CW. Since many of these builds share the same weak points (USB cables, long sensor leads, unfiltered I/O), it seems worth collecting what actually helps.

The usual suspects are common-mode current on the cables, not RF radiating straight into the chip. A USB cable between the rig and a Pi or PC, a CAT lead, a PTT line and a rotator control cable can each act as part of the antenna system, especially on 80/40 m with a end-fed or poorly choked feedline. If the problem changes when you move the coax or change bands, that points to common-mode current rather than a software bug.

The other half is the logic-level side. A Pico or ESP32 uses 3.3 V GPIO and is not 5 V tolerant. Icom CI-V is a single-wire open-collector bus, some Yaesu rigs use TTL-level serial, and some Kenwood radios use RS-232 voltage levels. Check the manual for your specific rig before wiring anything. What are you using for level shifting and isolation on CAT and PTT lines, and what ended up making the biggest difference?

  • Replies 2
  • Views 28
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

I would sort out the RF path before touching code. Start by running the rig into a dummy load. If the glitches vanish, you are dealing with RF getting into the system via the antenna or feedline, not a power supply or firmware fault. Then go back to the antenna and add one change at a time so you can tell which one helped.

The usual order is a proper common-mode choke on the coax at the shack entry, ferrites on the USB and CAT cables (several turns through a suitable mix for the band, not a single pass), and then bypassing on the board itself. A 100 nF capacitor plus a small value like 1 nF to ground on each exposed I/O line, with a series resistor, helps a lot on slow signals such as PTT sense or a sensor input. Keep the leads short, because a capacitor with long leads stops working as a bypass at HF/VHF.

A grounded metal enclosure also matters more than most people expect. A bare ESP32 dev board in a plastic box with a 1 m sensor lead is nearly an ideal pickup. Feed cables through bulkhead connectors, bond the shield at the entry point, and avoid ground loops from multiple USB connections where possible. For a rotator controller that reads a pot, the ESP32 ADC is also nonlinear and noisy even without RF, so averaging in software or using an external ADC like an ADS1115 is worth doing in any case. With Wi-Fi active on the ESP32, ADC2 pins are not usable, so plan the pin assignment around that.

  • Moderators

On the CAT side, I would treat the interface as its own small module, not wire the rig straight to the microcontroller. For CI-V, the shared bus usually needs a transistor or buffer arrangement that works with 3.3 V logic. For RS-232-level rigs, use a MAX3232 type converter powered from 3.3 V. For TTL-level rigs, check the voltage in the manual and use a level shifter if it is 5 V. Wiring a 5 V signal straight into a Pico or ESP32 pin is a common way to kill a board slowly or all at once.

For PTT, an optocoupler or small transistor driver keeps the rig's keying circuit separate from the microcontroller. If you drive a relay, put a flyback diode across the coil. For Direwolf on a Pi, the same applies: a GPIO PTT line should go through a transistor or opto stage, and a USB sound card with CM108 GPIO PTT is often cleaner than driving the radio from the Pi directly. Set TX audio level carefully, because overdriving the mic or data input gives a wide, distorted APRS signal that decodes worse.

For Si5351 projects, remember the outputs are square waves, so harmonics need a low-pass filter before an antenna or amplifier, and the frequency needs calibration against the crystal. The breakout board's I2C is 3.3 V, so keep the lines short and the pull-ups correct. If a display on the same I2C bus corrupts when you transmit, shortening that bus, or dropping to 100 kHz, is a good first test before assuming the chips are faulty.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.