During last year’s ARRL RTTY Roundup, I worked 400 stations in a weekend. Normally, I’d spend Monday morning cleaning up logs. Instead, I opened Log4OM on Monday, filtered by the contest, and saw every single QSO already tagged, timed, and confirmed via GridTracker’s real‑time feed. I exported the Cabrillo in 30 seconds and went back to bed.
That’s when I discovered the quiet power of connecting to Log4OM . gridtracker log4om
GridTracker and Log4OM aren’t competitors. They’re complementary engines. GridTracker is your real‑time radar and adrenaline. Log4OM is your digital filing cabinet and award‑tracking brain. Connecting them isn’t just about saving keystrokes — it’s about freeing your mind to focus on the one thing that matters: making the next QSO. During last year’s ARRL RTTY Roundup, I worked
It started as a messy pile of digital breadcrumbs. After every contest or casual FT8 session, I’d have a half‑empty ADIF file here, a manual pencil note there, and a GridTracker map full of colorful blips that vanished the moment I closed the window. My logging was a leaky bucket. Something had to change. I exported the Cabrillo in 30 seconds and went back to bed
Because a QSO you don’t log is a QSO you never made. And a grid you don’t track is a grid you’ll work twice.
In GridTracker → Preferences → Logging, I pointed it to Log4OM’s built‑in UDP server (default port 2333). On the Log4OM side, I enabled “External Services” and allowed incoming connections. Five minutes of config ended two years of friction.