One logging workflow for contests and daily operating: N1MM+, WSJT-X, Log4OM, ADIF, Cabrillo, LoTW and QRZ
- Replies 2
- Views 67
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Admin_Lee 1 post
I'm trying to design a logging setup that doesn't turn every contest weekend into a data-cleanup project. The goal is to avoid keeping three or four logs that disagree with each other. Here is the layout I'm considering, and I'd like corrections from people who have run something similar.
Contest logging would live in N1MM Logger+, with a fresh database per contest. N1MM handles dupe checking, the band map, rig CAT, rotator control and Cabrillo export. Everyday operating, including WSJT-X modes, would go into a general-purpose logger such as Log4OM. That logger would be the master log and the source for LoTW, QRZ and Club Log uploads. After a contest, I'd export ADIF from N1MM and merge it into the master log.
These are the points I think will cause trouble:
First, CAT sharing. Only one program can normally open a serial port, so N1MM, WSJT-X and the general logger can't all talk to the radio directly. The usual answers are a rig-control layer (Hamlib rigctld, OmniRig or flrig, depending on the radio and program support) or a virtual COM port splitter. I'd like to know which approach holds up best when WSJT-X and a logger need frequency and mode at the same time.
Second, ADIF mapping. ADIF is a standard, but programs differ in how they write modes, submodes, contest IDs and exchange fields. FT4 is a good example: depending on the ADIF version and the program, it can appear as its own mode or as a submode of MFSK. Before a bulk import into the master log, I plan to test with a small batch and check mode, band, frequency, station callsign and any contest-specific fields. If a mode comes out wrong, LoTW matching can fail even though the QSO itself is fine.
Third, Cabrillo. N1MM can generate the file, but the sponsor's rules decide what is valid: category, operator and power class, club name, and sometimes the soapbox or address lines. I'd rather read the contest's log submission instructions and fix the header fields in N1MM before export than edit the Cabrillo text by hand afterward. I'd also run the file through the sponsor's checker or upload page if one is offered, and keep the original ADIF.
Fourth, uploads. LoTW needs TQSL, a certificate for the callsign, and a station location that matches where the operating happened. A mismatched grid, DXCC entity or callsign is a common reason uploads get rejected or don't match. QRZ and Club Log use their own credentials or API keys. I'd test with a few QSOs first, since a bad bulk upload is annoying to undo. I'd also keep the PC clock accurate, because time errors hurt matching.
Finally, I'm unsure how to handle club operations. If several operators log on the same station, should each use a separate database or one shared one? And what's the cleanest way to hand a log to a club log coordinator without exposing credentials?
What would you change in this plan? I'm especially interested in CAT arrangements, dupe-sheet habits, and any ADIF import problems worth knowing about before the next contest.
Link to comment
https://www.hamradiobase.com/forums/topic/11034-one-logging-workflow-for-contests-and-daily-operating-n1mm-wsjt-x-log4om-adif-cabrillo-lotw-and-qrz/Share on other sites