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 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. 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. At first, I treated them as separate tools:
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. Missing timestamps
That’s when I discovered the quiet power of connecting to Log4OM .