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?”
Here’s what changed:
That’s when I discovered the quiet power of connecting to Log4OM . gridtracker log4om
So if you’re still copying and pasting between windows or manually typing in grids from a map, stop. Set up the GridTracker → Log4OM pipeline. Your future self — the one chasing Worked All States or that last elusive DXCC entity — will thank you.
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. GridTracker’s alert system pings me when a rare
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.
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. Later, when I run a “Missing Grids” report
Then I stumbled on the integration. One toggle. One TCP port. One “aha” moment.