ⓘ Callsign lookups are in real time via the FCC database.
Vanity callsign availability is refreshed daily at 6:00 AM CST.
The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cmvia PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHzDXSpotterInfo
Recent spots—
Select a band above to load spots
Ready — select a band to fetch live spots
One master log or three? Keeping N1MM+, WSJT-X and Log4OM in sync without duplicate uploads
This is a workflow question that comes up whenever a station runs more than one logger. Say you use N1MM Logger+ for contests, WSJT-X for FT8/FT4, and Log4OM (or DXKeeper, HRD Logbook, Logger32) as the everyday log. The mechanics are easy to get wrong in ways that only show up weeks later, as duplicate LoTW records, missing Club Log matches, or a Cabrillo file the sponsor's checker rejects.
The questions I'd like to hash out are these:
1. Should there be one master log, with everything else treated as a feeder? A common design is for the general-purpose logger to hold the permanent record. Contest ADIF exports and WSJT-X's wsjtx_log.adi are imported into it, and only that program uploads to LoTW, QRZ and Club Log. The risk is when two programs upload the same QSO. LoTW will usually just treat it as a duplicate, but QRZ and Club Log behavior varies by how each program matches records.
2. What is the cleanest way to get WSJT-X into the master log? Most people either use the UDP broadcast that WSJT-X sends on "Log QSO" (Log4OM and several other programs can listen for it) or import the ADIF file in batches. Live UDP gives you instant dupe awareness and band-map coloring. Batch import is simpler but means checking for overlap, since re-importing the same file creates doubles unless the import filters on call, band, mode and time.
3. How much should be trusted in ADIF? ADIF is a text format with named, length-prefixed fields, so it moves between programs well, but the semantics differ. Mode and submode are a classic trap: FT8 and FT4 have not always been represented the same way across ADIF versions and programs (FT4 has typically appeared as MFSK with a submode). If an importer maps modes oddly, LoTW and award tracking can break. Contest-specific fields (CONTEST_ID, STX, SRX, SRX_STRING) and APP_ fields can also be dropped or kept depending on the program.
4. What does a sane pre-submission checklist look like? Before exporting Cabrillo I'd want the UTC clock verified, the callsign and operator fields correct, the category and power entered in the header, and any dupes or busted calls reviewed. Does anyone also run the log through a checker or a log-cross-check tool before upload?
I'm also curious how people split CAT control between programs, since that is where many multi-program stations get stuck.
This is a workflow question that comes up whenever a station runs more than one logger. Say you use N1MM Logger+ for contests, WSJT-X for FT8/FT4, and Log4OM (or DXKeeper, HRD Logbook, Logger32) as the everyday log. The mechanics are easy to get wrong in ways that only show up weeks later, as duplicate LoTW records, missing Club Log matches, or a Cabrillo file the sponsor's checker rejects.
The questions I'd like to hash out are these:
1. Should there be one master log, with everything else treated as a feeder? A common design is for the general-purpose logger to hold the permanent record. Contest ADIF exports and WSJT-X's wsjtx_log.adi are imported into it, and only that program uploads to LoTW, QRZ and Club Log. The risk is when two programs upload the same QSO. LoTW will usually just treat it as a duplicate, but QRZ and Club Log behavior varies by how each program matches records.
2. What is the cleanest way to get WSJT-X into the master log? Most people either use the UDP broadcast that WSJT-X sends on "Log QSO" (Log4OM and several other programs can listen for it) or import the ADIF file in batches. Live UDP gives you instant dupe awareness and band-map coloring. Batch import is simpler but means checking for overlap, since re-importing the same file creates doubles unless the import filters on call, band, mode and time.
3. How much should be trusted in ADIF? ADIF is a text format with named, length-prefixed fields, so it moves between programs well, but the semantics differ. Mode and submode are a classic trap: FT8 and FT4 have not always been represented the same way across ADIF versions and programs (FT4 has typically appeared as MFSK with a submode). If an importer maps modes oddly, LoTW and award tracking can break. Contest-specific fields (CONTEST_ID, STX, SRX, SRX_STRING) and APP_ fields can also be dropped or kept depending on the program.
4. What does a sane pre-submission checklist look like? Before exporting Cabrillo I'd want the UTC clock verified, the callsign and operator fields correct, the category and power entered in the header, and any dupes or busted calls reviewed. Does anyone also run the log through a checker or a log-cross-check tool before upload?
I'm also curious how people split CAT control between programs, since that is where many multi-program stations get stuck.
Link to comment
https://www.hamradiobase.com/forums/topic/10769-one-master-log-or-three-keeping-n1mm-wsjt-x-and-log4om-in-sync-without-duplicate-uploads/Share on other sites