Subject:
At first, I treated them as separate tools: GridTracker for the live, dopamine‑hit visual of chasing grids on a world map, and Log4OM for the serious business of archival logging. But running them in parallel felt like driving with two steering wheels. Duplicate entries. Missing timestamps. The occasional logged QSO that never made it to my master log. gridtracker log4om
Now, every FT8 decode that I double‑click to answer in WSJT‑X sends a complete QSO packet to GridTracker. GridTracker, in turn, forwards it to Log4OM instantly . Grid, signal report, timestamp, frequency, mode — all captured without me touching a single log field. Subject: At first, I treated them as separate
Then I stumbled on the integration. One toggle. One TCP port. One “aha” moment. Missing timestamps
Here’s what changed:
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.
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.