so ive been using WSJT-X for FT8 stuff for a while now and it logs to its own file which is fine but i want something that ties everything together - like i want one master log that has my FT8 contacts, my SSB ragchews, AND my contest stuff all in one place without having to manually import ADIFs every time i remember to do it

right now im kind of bouncing between N1MM for contests because honestly nothing touches it for that, and then Log4OM for day to day stuff because it looks nicer and has all the award tracking built in. but the two dont really talk to each other cleanly and i end up with duplicate entries sometimes when i forget what ive already imported

has anyone actually gotten WSJT-X feeding into Log4OM in real time while also keeping N1MM set up for when a contest weekend rolls around? or is the answer just pick one and deal with the limitations. i looked at the Log4OM docs and it says it can do UDP from WSJT-X but i couldnt get it working right, kept missing contacts or logging them twice

not looking to switch away from N1MM for contesting, that part works great, just wondering if theres a cleaner workflow that people have actually figured out

yeah the UDP thing with WSJT-X and Log4OM is a bit fiddly to set up the first time. you need to make sure WSJT-X is broadcasting on the right port and that Log4OM is listening on the same one - by default i think WSJT-X sends on 2237 but double check your settings because i forget if that changed in a recent version. also make sure you dont have N1MM running at the same time when youre trying to set this up because N1MM will grab that UDP stream too and it gets messy

what i do personally is just accept that N1MM is my contest logger and Log4OM is everything else. after a contest i export the Cabrillo and also save an ADIF, then import the ADIF into Log4OM manually. takes like two minutes. duplicates are easy to spot if you sort by date. not elegant but it works and i stopped stressing about having a perfect automated pipeline because half the time those break anyway when software updates

i ran into the exact same duplicate problem last winter during CQ WW. what finally worked for me was setting up WSJT-X to log to its own ADIF file and NOT trying to do the real-time UDP feed to Log4OM at the same time as anything else. then after each session i just drag the ADIF into Log4OM and it flags the dupes pretty well if you have the dupe checking settings turned on properly

for contests i close Log4OM entirely and just run N1MM standalone, thats honestly the cleanest way. N1MM doesnt really need a companion app anyway, it does everything you need during the contest itself. the only thing i wish it had was better award tracking outside of contest mode but thats not really what its designed for

one thing worth mentioning - if youre doing digital modes other than FT8, like JS8Call or something, the logging situation gets even more annoying because JS8Call has its own log format too. i just ended up keeping a little spreadsheet for the weird one-off stuff which probably defeats the whole purpose but here we are