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 128
SN 73
A 6
K 1 Quiet
X-Ray B7.8
Wind 387.9 km/s
Aurora 3
Updated 01:00 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

UDP Port Conflicts Between N1MM Logger+ and WSJT-X Integration

Having issues getting N1MM Logger+ to properly interface with WSJT-X for upcoming ARRL DX CW. Default port 2237 should match between WSJT-X and N1MM+, but getting intermittent connection drops during busy band periods. Has anyone experienced similar UDP communication issues?

Running N1MM+ 1.0.9789 with WSJT-X 2.6.1 on Windows 11. CAT control works fine through DXLab Commander setting, but the logging integration keeps failing. Mode control is set to AFSK-R for the IC-7300 per documentation.

Are there any known workarounds or specific firewall configurations that resolve this? Really need this stable for contest operation.

  • Replies 2
  • Views 742
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

Check your Windows firewall settings - N1MM+ and WSJT-X both need UDP exceptions. For SO2R setups, Radio #2 needs port 2239 but sounds like you're running SO1R. Also verify you don't have "Enable" checked in the Secondary UDP Server section of WSJT-X - that's only for external logging programs.

I had this exact problem last month! The issue was Windows Defender blocking the UDP broadcast. Add both N1MM+ and WSJT-X to your firewall exceptions, and make sure no antivirus is interfering. Don't check Enable in Secondary UDP Server when WSJT-X runs from inside N1MM+.

Consider using separate INI files for contest operation vs daily WSJT-X use. N1MM+ creates "WSJT-X – ForEW1" instance that's completely separate from your everyday copy. This isolates your contest configuration and prevents conflicts with your regular digital mode setup.

Join the conversation

You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

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.