Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base -Powered By Ham CQ DX

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Solar
SFI 125
SN 50
A 7
K 0 Quiet
X-Ray C1.1
Wind 443.9 km/s
Aurora 1
Updated 13:30 UTC HamQSL · N0NBH
Day 80/40m Fair 30/20m Good 17/15m Good 12/10m Fair
Night 80/40m Good 30/20m Good 17/15m Good 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ 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 — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots
Select a band above to load spots
Ready — select a band to fetch live spots

N1MM vs Log4OM for contest logging — am i missing something with the WSJT-X integration

 Loading...

so ive been using Log4OM for general logging for maybe two years now and i really like it for day to day stuff, the interface is clean and it syncs with LOTW and clublog without much fuss. but every time contest season rolls around i end up switching back to N1MM and it feels like im living a double life with my logbook. dupes everywhere, had to manually merge logs twice last year and the second time i definitely lost a few contacts somewhere in the process.

the thing thats really bugging me now is WSJT-X. i have it talking to Log4OM just fine via UDP and that works great for FT8 on a normal weekend. but when i tried to run a contest last month — it was the ARRL DX CW actually — i had N1MM open at the same time and i think both programs were trying to grab the UDP packets from WSJT-X and it turned into a mess. not sure if i had the ports wrong or what but half my FT8 contacts just didnt show up anywhere.

is there a clean way to run these together or do most people just pick one and commit to it for the whole operating event? feels like theres probably a smarter way to do this that im not seeing.

  • Replies 1
  • Views 13
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah the UDP thing will absolutely bite you if both programs are listening on the same port, WSJT-X only broadcasts to one destination at a time by default. what some people do is run something like JTAlert in the middle which can rebroadcast to multiple apps but honestly for a serious contest i just close Log4OM completely and let N1MM handle everything. you can import the ADIF back into Log4OM after the contest is over and it merges pretty cleanly as long as you dont have overlapping contacts from other modes that weekend.

the other thing worth knowing is N1MM has gotten a lot better with FT8 support through the contest modules, its not perfect but for something like ARRL DX where youre mixing CW and digital it handles the dupe checking way better than trying to keep two logs in sync live. i tried the two-program thing for about one contest and never again.

cant speak to Log4OM much since i went all in on N1MM years ago and never looked back for anything contest related, but the WSJT-X port conflict thing is a known headache. pretty sure you can set a secondary UDP address in the WSJT-X settings under reporting, so you could theoretically have it send to two IPs or ports but i havent personally tested that setup. theres a thread on the N1MM reflector about it from like 2022 that went into a lot of detail if you can find it in the archives.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.