Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base -Powered By Ham CQ DX

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.
Solar
SFI 147
SN 141
A 10
K 3 Unsettled
X-Ray C1.0
Wind 410.6 km/s
Aurora 4
Updated 03:30 UTC HamQSL · N0NBH
Day 80/40m Poor 30/20m Good 17/15m Good 12/10m Fair
Night 80/40m Fair 30/20m Good 17/15m Good 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

using an arduino to key my radio automatically — ran into a weird issue

 Loading...

so ive been working on this little project for a few weeks now, basically trying to get an arduino uno to key my IC-7300 via the CI-V interface and also trigger the PTT line with a transistor. the idea is to automate some beacon transmissions on 10m while im at work, nothing fancy just ID every 10 minutes or so with a CW message.

anyway everything was going fine, i had the timing worked out and the morse code library was doing its thing, but now whenever the arduino tries to key up i get this nasty voltage spike on the audio line and it ends up with a weird chirp at the start of every transmission. i measured the PTT line and its clean but somewhere between the arduino firing and the final RF going out something is causing that audio artifact. i put a 100 ohm resistor inline thinking it was a grounding issue but no dice.

has anyone dealt with this before? im using a 2N2222 as the switching transistor and the arduino is powered off a separate USB supply from the radio. maybe thats the problem actually, ground loops are the bane of my existence with this stuff.

  • Replies 1
  • Views 14
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah that sounds like a ground loop to me honestly. if your arduino and the radio are on separate supplies and you dont have a common ground between them youll get exactly that kind of garbage on the audio. i had the same thing happen with a raspberry pi zero i was using to control my old 857. what fixed it for me was running a single wire from the arduino ground to the radio chassis ground, not through the USB supply, just directly. the 2N2222 should be fine for PTT switching as long as you have a pulldown on the base, which im assuming you do.

the other thing worth checking is whether the CI-V and PTT are fighting each other timing-wise. if PTT fires like 5ms before the CI-V transaction finishes you can get some weird startup artifacts. i added a 50ms delay in my sketch after the CI-V command before actually pulling PTT low and that cleaned things up a lot.

might also want to throw a small cap across the transistor collector to ground, like 0.1uf ceramic, ive seen that tame some of the switching transients on the PTT line. also are you sure youre not accidentally feeding audio from the arduino into the mic input somehow? some of those boards can leak a tiny bit of signal on the GPIO when they switch states and if thats anywhere near the mic circuit on the 7300 itll pick it up for sure.

  • Guest pinned this topic
Guest
Reply to this topic...

Account

Navigation

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.