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 .
Then I stumbled on the integration. One toggle. One TCP port. One “aha” moment. gridtracker log4om
GridTracker gives me the story of the band — propagation paths, greyline openings, who’s hearing me. Log4OM gives me the truth — awards progress, QSL status, notes, and a unified log I can sync to QRZ, eQSL, and LoTW with one click. Together, they transformed operating from reactive button‑clicking into strategic grid hunting.
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
Here’s what changed:
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. I exported the Cabrillo in 30 seconds and went back to bed
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.