Gridtracker Log4om 'link' -

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.

Here’s what changed:

GridTracker’s alert system pings me when a rare DX entity or a new grid appears. I work the station. Log4OM logs it. Later, when I run a “Missing Grids” report in Log4OM, the data is already there. No reconciliation weekends. No “wait, did I log that?” gridtracker log4om

Subject:

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. It started as a messy pile of digital breadcrumbs

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. Something had to change

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.