[TVARC] Fwd: Using N1MM as logger for FT-8 contacts made via WSJIT

Tue Jun 9 22:35:07 EDT 2026

Tnx George. I've used the WSJT-X integrated with N1MM+ for several of the
digital contests. The problem is that logging should be done through WSJT-X
and not N1MM+. People get fooled into thinking that the N1MM+ logging
window does the logging when in fact the WSJT-X logging window is primary.
I suffered several screw-ups in the early going when doing digital
contests. The logging window for WSJT-X carries the last contest worked
which is confusing when entering the current contest and the logged QSO
gets added.  However, the N1MM+ logging window is current and is the one to
use for post-contest download to your logging program.

Another issue is the number of windows that show up. One needs 2 monitors
or a really big one to separate the windows. I had to go to the windows tab
of N1MM+ to check windows not being displayed.

I managed 75 Qs, mostly in FT4. DX was hard to pull in.

73 de Ed

On Tue, Jun 9, 2026 at 10:35 PM George via TVARC <tvarc at mailman.qth.net>
wrote:

> I sent this to Andy, but I meant to send it to everyone. So, here it is.
> George K2DM
>
> Sent from my iPhone
>
> Begin forwarded message:
>
> *From:* George <k2dm at comcast.net>
> *Date:* June 9, 2026 at 5:26:03 PM EDT
> *To:* Andy McClary <j.a.andy.mcclary at gmail.com>
> *Subject:* *Re: [TVARC] Using N1MM as logger for FT-8 contacts made via
> WSJIT*
>
> Hi Andy, thanks for sending this out. I have been battling the WSJT-X /
> N1MM+ together issue for a few days now after I foolishly committed to a
> couple of TVARC board members to get it working in time for Field Day.
> Research led me to the same steps that you outline in your email. I found
> the steps in the N1MM+ documentation and other sources. The fly in the
> ointment for me has been adding in the Icom IC-7300 into the mix.
> Parameters like baud rate, operating mode and others need to be set
> correctly. I hope to have all the gotchas figured out and documented soon.
> BTW, I am under the impression that rig control is done by WSJT-X, not by
> N1MM+.
> Sadly, the club’s expert on this topic, Rich Erlichman, passed away a few
> years ago.
> 73,
> George K2DM
>
> Sent from my iPhone
>
> On Jun 9, 2026, at 5:06 PM, Andy McClary via TVARC <tvarc at mailman.qth.net>
> wrote:
>
> 
> *Somebody asked this question, but I can't remember who...  so apologies
> for sending this to the reflector instead of directly...*
>
> *Short answer:*  To send QSOs from *WSJT‑X* to *N1MM Logger+*, you enable
> WSJT‑X’s *UDP Broadcast* and N1MM’s *WSJT Decode List* interface. Once
> configured, every completed QSO in WSJT‑X is automatically logged into
> N1MM+.
> Below is the exact, step‑by‑step setup based on the N1MM documentation.
> Citations included.
> *✅ 1. Enable WSJT‑X → N1MM Logging (UDP Broadcast)*
> WSJT‑X sends QSO and decode data to N1MM using UDP packets. N1MM listens
> on *UDP port 2333* for WSJT‑X.
> *WSJT‑X Settings*
>
>    1. Open *WSJT‑X → Settings → Reporting*
>    2. Enable:
>    - *✓ Enable UDP Server*
>       - *✓ Accept UDP Requests*
>       - *✓ Enable Logging*
>       3. Set:
>    - *UDP Server Address:* 127.0.0.1
>       - *UDP Server Port:* 2333 (default for WSJT‑X → N1MM)
>
> *✅ 2. Configure N1MM to Receive WSJT‑X QSOs*
> N1MM must be told to accept WSJT‑X data.
> *N1MM Settings*
>
>    1. Open *N1MM+ → Config → Configure Ports, Mode Control, Audio, Other*
>    2. Go to the *WSJT/JTDX Setup* tab
>    3. Enable:
>    - *✓ Accept UDP packets from WSJT‑X*
>       4. Confirm:
>    - *UDP Port:* 2333
>       - *IP Address:* 127.0.0.1
>       5. Restart N1MM after enabling (required).
>
> *✅ 3. Use the WSJT Decode List Window in N1MM*
> N1MM provides a dedicated interface for WSJT‑X called the *WSJT Decode
> List Window*. This is the bridge between WSJT‑X and N1MM.
> Open it in N1MM: *Window → WSJT Decode List*
> This window:
>
>    - Shows WSJT‑X decodes
>    - Lets you initiate QSOs
>    - Logs QSOs automatically into N1MM
>    - Provides dupe checking, mult highlighting, scoring, etc.
>
> *✅ 4. How Logging Works*
> When WSJT‑X completes a QSO (73 exchanged), it sends an ADIF record to
> N1MM in this format:
> Code
>
> <command:3>Log<parameters:nnnn>ADIF_DATA
>
> N1MM inserts it into the current contest log.
> Supported fields include CALL, QSO_DATE, TIME_ON, MODE, FREQ, RST, GRID,
> etc.
> *🧩 5. CAT Control Note*
> N1MM should control the radio, not WSJT‑X. WSJT‑X reads frequency from
> N1MM through the interface. This avoids CAT conflicts.
> *🎯 Summary*
> To send QSOs from WSJT‑X to N1MM:
>
>    1. *WSJT‑X → Reporting → Enable UDP Server (2333)*
>    2. *N1MM → Config → WSJT/JTDX Setup → Enable UDP input*
>    3. *Open WSJT Decode List Window*
>    4. *Complete QSO in WSJT‑X → Auto‑logged in N1MM*
>
> This is the officially supported method and works reliably for FT8/FT4
> contesting.
>
>
>
>
> Andy McClary
>
> KQ4WWD
>
> 583 Concord Court
>
> The Villages, FL  32162
>
> (740) 777-0817
>
> *j.a.andy.mcclary at gmail.com* <j.a.andy.mcclary at gmail.com>
> <image.png>
>
>
> ______________________________________________________________
> TVARC mailing list
> Home: http://mailman.qth.net/mailman/listinfo/tvarc
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:TVARC at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>
> ______________________________________________________________
> TVARC mailing list
> Home: http://mailman.qth.net/mailman/listinfo/tvarc
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:TVARC at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qth.net/pipermail/tvarc/attachments/20260610/1c97bd99/attachment-0001.html>