Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

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 121
SN 99
A 11
K 3 Unsettled
X-Ray B8.6
Wind 423.4 km/s
Aurora 4
Updated 11:30 UTC HamQSL · N0NBH
Day 80/40m Poor 30/20m Good 17/15m Fair 12/10m Fair
Night 80/40m Fair 30/20m Good 17/15m Fair 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 everyday logging when you also do FT8 - how do you guys handle it

so ive been going back and forth on this for a while now and cant really settle on a workflow that doesnt drive me crazy. right now i use WSJT-X for FT8 obviously, and i have it set up to log to Log4OM which works fine most of the time. but then when i actually do a contest i switch over to N1MM and everything is in a different place and i end up with two separate logs that i have to merge after the fact which is kind of a pain.

the adif import into Log4OM from N1MM exports has been hit or miss for me, sometimes the band gets imported wrong or the mode shows up as something weird. not sure if thats a Log4OM thing or how N1MM is exporting. anyone else deal with this or have a cleaner way to do it. i dont want to abandon N1MM for contests because honestly nothing touches it for that, the band map and the rate display and all that is just way better than anything else ive tried. but the post-contest cleanup is getting old

  • Replies 1
  • Views 11
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah this is basically the same situation i was in for like two years. what i ended up doing is just accepting that N1MM is the contest logger and Log4OM is the shack log and treating them as separate things. then after every contest i do a careful adif export from N1MM, open it in a text editor real quick to check the MODE field looks right, and then import. the band issue you mentioned is usually because N1MM uses FREQ in MHz and sometimes the adif parser in Log4OM gets confused if the frequency is slightly off for whatever band - like if you were on 14.074 it should map to 20m fine but ive seen it choke on 60m entries before.

the other thing worth checking is whether your WSJT-X is also trying to log to N1MM over UDP at the same time. if you have that enabled and you're not running a contest it can sometimes create duplicate or weird entries in N1MM that then get exported later. i just disable the N1MM UDP connection in WSJT-X when im not contesting and life got a lot simpler after that

honestly i just use N1MM for everything including regular logging and gave up on Log4OM. probably not helpful but the merging thing sounds like more trouble than its worth to me. N1MM's regular logging mode is fine enough for day to day stuff and it handles the WSJT-X UDP feed pretty reliably in my experience

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

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.