Introduced on January 2nd, 2019, the WSJT Decode List provides a bi-directional interface between the Band Activity Panel in WSJT-X or JTDX and N1MM+’s contest log.
- QSO initiation, auto-sequencing, and logging from within the WSJT-X or JTDX program
- Contact logging in both the WSJT-X or JTDX ADIF log and the N1MM+ contest database
- Callsign prioritization (normal, mult, double mult) based on contest contacts in the N1MM+ log
- Dupe callsign warnings based on contest rules (bands, modes) and existing contacts in the N1MM+ log
- Instructions for using WSJT-X or JTDX with N1MM+ can also be found in a file called “N1MMWSJTInstructions.pdf” in the Additional Support Files file gallery on the N1MM+ web site
As mentioned in the reflector messages, the WSJT Decode List and the interface between WSJT-X/JTDX and N1MM+ are still undergoing development and testing. There may be issues with the interface that are undiscovered and consequently untested. If problems are encountered, it is always possible to revert to using WSJT-X or JTDX stand-alone and then importing the log in ADIF format from WSJT-X or JTDX into N1MM+ after the contest. If you are using the newer method of running WSJT-X or JTDX from within N1MM+, it may also be possible to revert to the older method using WSJT-X/JTDX stand-alone simultaneously with N1MM+ (in which case rig control will have to be disabled in N1MM+). If problems are encountered, please document them and report them to the N1MM+ Development Team for correction.
Configuring the WSJT Decode List Window
There are several places in the Configurer that need to be set up for WSJT-X interoperation with N1MM+. These include the Broadcast Data page, the Digital Modes page and the Mode Control page in the Configurer window. You also need to ensure that the Contest Setup is configured to include Digital modes (otherwise digital mode contacts will not be given points credit).
To enable logging from WSJT-X to N1MM+, configure per the following settings on the Configurer’s >Broadcast Data page (Note – if you are running WSJT-X stand-alone, or using another program that cannot be run from within N1MM+, you may need to change the UDP port number to 2333):
To enable logging from JTDX to N1MM+, in addition to configuring the UDP port as for WSJT-X, you also need to configure the TCP port for JTDX logging to use port 52001:
If you intend to call WSJT-X/JTDX from within N1MM+ using the Window > Load WSJT/JTDX menu item, which allows N1MM+ to perform all rig control functions on behalf of WSJT-X or JTDX and avoids having to reconfigure rig control every time you make a mode change between WSJT-X/JTDX and CW/SSB/RTTY, then you must also enter the location of the WSJT-X or JTDX program in the Configurer on the >Digital Modes page:
When you are using WSJT-X or JTDX, the radio should be in the same mode as it uses for PSK. Still in the Configurer, on the >Mode Control page, on the right-hand side under Mode sent to radio, you need to set the mode in the PSK row correctly for your radio. On some radios, this might be PSK, or perhaps AFSK-R, or if your radio does not have a separate Data mode for digital modes, it might be USB. Consult the Digital Mode Mapping table in the Supported Radios chapter of this manual for the mapping between mode names on the radio and the mode names that appear in the pull-down list on the Mode Control page of the Configurer.
Note that for duplicate and multiplier information to be recorded and transferred correctly, the correct contest must be selected in N1MM+, and the program must be in Digital logging mode (the easiest way to do this is to type FT8 into the call sign box in the Entry window and press Enter).
Note that the contest Mode category in the contest setup dialog window must contain DIGITAL. If the contest mode is RTTY, contacts in other modes (including FT8) will be assigned zero points. After changing RTTY to DIGITAL or SSB+CW to SSB+CW+DIGITAL in the contest setup window to correct this, you will need to use the Tools > Rescore Current Contest menu item to rescore any FT8 QSOs that had not originally been assigned the correct score.
Configure per the following settings on the >File >Settings page in the UDP Server panel:
You only need to check the Accept UDP Requests checkbox on the right-hand side under UDP Server (see screenshot). The default port number is fine. The “Accept UDP requests” check box (normally on port 2237) is required in order for the WSJT Decode List window to work. It enables the passing of duplicate/multiplier information from N1MM+ to WSJT-X, as well as allowing WSJT-X to use N1MM+ for rig control if it is called up from the N1MM+ Window menu.
If you are running another JT mode program stand-alone instead of from within N1MM+, you may also need to check the Enable check box under “N1MM Logger+ Broadcasts”, and make a corresponding change in the N1MM+ Configurer’s >Broadcast Data tab. In either case, if you encounter difficulties, it is possible that your anti-malware software, firewall, etc. may need to be configured to allow the JT mode program and N1MM+ to accept packets on one or the other of these ports.
If you are running WSJT-X or JTDX from the N1MM+ Window menu, do not check the Enable check box in the N1MM Logger+ Broadcasts area. Instead, under the Radio tab in WSJT-X, change the rig control method to “DX Lab Suite Commander”:
Note that you do not need to run DXLab Suite’s Commander program; N1MM+ uses the same method as Commander to communicate with WSJT-X, so the same Rig setting can be used in WSJT-X. Choose your PTT Method, radio’s Mode and Split Operation method depending on your radio.
If you choose CAT as the PTT method, what that really does is tell WSJT-X that N1MM+ will be handling PTT control. You must have a method of PTT control configured in the N1MM+ Configurer for this to work. You can check the “PTT via Radio Command Digital Mode” check box in the setup window for the radio control port in the Configurer, or configure a serial port in the Configurer for PTT control, or if you are using a Winkeyer, connect a PTT cable from the Winkeyer’s PTT output to the rig’s PTT input jack. Any of these will work with the CAT PTT method selected in WSJT-X when it is run from inside N1MM+. If you are using a SignaLink to perform the PTT function, select VOX as the PTT method in WSJT-X.
The Split Operation pane in the WSJT-X setup controls how WSJT-X handles audio frequencies outside the “ideal” 1500-2000 Hz range. If either Rig or Fake It is chosen, then if an audio frequency outside that range is chosen, whenever WSJT-X commands N1MM+ to put the rig into transmit, it will also request that N1MM+ QSY the radio by a multiple of 500 Hz so as to put the audio frequency back into the “ideal” range. This avoids problems with audio harmonics or with reduced audio gain in other parts of the bandpass. If Rig is chosen, the QSY will be done using the rig’s split operation capability; if Fake It is chosen, the main VFO will be QSYed every time you switch between transmit and receive. With some rigs, there may be an objectionable delay when switching to transmit with the Rig setting chosen; if this happens to you, use the Fake It setting instead.
If you are running WSJT-X from inside N1MM+, the first time you open it you may notice that all of the WSJT-X settings have been restored to default values – for example, your call sign and grid square may not be entered under the General tab. If you want to avoid having to re-enter all of your preferred settings (other than the ones described above), there is an optional way to transfer them over from your stand-alone setup to the setup within N1MM+.
In WSJT-X, use the File > Open log directory menu item to open a Windows File Explorer window open to the directory where WSJT-X stores its settings. If you do this from the stand-alone version of WSJT-X, this will be C:\Users\[yourusername]\Appdata\Local\WSJT-X. If you do it from WSJT-X after it has been called up from within N1MM+, the directory will be C:\Users\[yourusername]\Appdata\Local\WSJT-X – ForEW1 (or ForEW2 for the copy of WSJT-X called up from the second Entry window in SO2V or SO2R). You can navigate to the …\WSJT-X directory, find the file called WSJT-X.ini, copy it and paste the copy into the …\WSJT-X – ForEW1 directory. Then rename the copy to WSJT-X – ForEW1.ini (after deleting or renaming any existing file with that file name). If you had already made the configuration setting changes described earlier on this page, you will have to make them again. From now on the two configurations will be independent; changes made to one will not affect the other.
Configuration for a Specific Contest
- If used during a contest, click the checkbox adjacent to the contest that you intend to operate
- For the ARRL RTTY Roundup – SW/VE stations should insert their two character state/province abbreviation. DX stations should use the expression “DX”, which will enable sequential serial number exchanges.
- For the ARRL Field Day – Enter the exchange information describing your station configuration (e.g. 1D EMA – see ARRL instructions).
Launching WSJT Decode List
If you are running WSJT-X or JTDX from within N1MM+, first use the N1MM+ >Window > Load WSJT/JTDX menu item to start WSJT-X/JTDX. If you are running WSJT-X or JTDX stand-alone, start it in the normal way.
Now open the WSJT Decode List from the N1MM+ >Window >WSJT Decode List menu choice:
Opening this window will automatically initiate the UDP Server communications between WSJT-X/JTDX and N1MM+ for the transfer of duplicate/worked/multiplier status from N1MM+ to WSJT-X or JTDX. Once the window has been opened, do all of your operating from WSJT-X or JTDX, and not from the N1MM Entry Window. In fact you can minimize (but do not close) the WSJT Decode List, and you can also minimize all of the N1MM+ windows temporarily if you want to to free up screen space.
If something (such as anti-malware software, or a configuration error in one or the other of the programs) prevents the transfer of logging information, you need to fix that. DO NOT try to bypass the automated logging by entering exchange data directly into the N1MM+ Entry window and pressing Enter to log it. Doing so may result in incorrect information being logged.
Using WSJT Decode List
With the WSJT Decode List enabled, a list of up to 30 recent callsigns will be displayed with row colors indicating each callsign’s contest priority (grey for dupe or zero points, blue for workable but not a multiplier, red for new multipliers). Callsigns in the corresponding WSJT-X/JTDX Band Activity panel will reflect those same contest color priorities as a background color. The only callsigns that are marked are callsigns of stations calling CQ. Callsigns of stations with QSOs in progress are not marked and do not appear in the WSJT Decode List.
To initiate a contact with a listed station, you may click on a callsign in either location (in the Logger’s WSJT Decode List window, or in the WSJT-X or JTDX Band Activity window). Note that if you click on an “old” callsign, i.e. one that was sending CQ during the 15-second sequence before the most recent one, WSJT-X/JTDX will not start transmitting until the correct time slot for calling that station (e.g. if the other station called CQ on an “even” time slot starting at 0 seconds or 30 seconds, WSJT-X/JTDX will only call that station on an “odd” time slot starting at 15 seconds or 45 seconds).
When you click on a callsign, either in the WSJT Decode List window or in the WSJT-X/JTDX Band Activity window, that call sign will also appear in the N1MM+ Entry window. This is for the purpose of doing a dupe/multiplier check; it is not part of the logging process. Do not enter the exchange into the Entry window. Simply complete the QSO in WSJT-X or JTDX, up to and including the point where the QSO is logged. After completing and logging a contact in WSJT-X or JTDX, that contact will be logged in the WSJT-X or JTDX ADIF log and the N1MM+ contest database simultaneously. At no point is there any need to type anything into any N1MM+ window; in fact, it is possible to operate in FT8 with all of the N1MM+ windows minimized to the Windows Task Bar and still have all of your FT8 QSOs recorded in the N1MM+ log. It is not necessary that the WSJT Decode List window in N1MM+ be visible; it can be minimized to the Task Bar and will still carry out its function of relaying dupe/multiplier status to WSJT-X or JTDX.
When a callsign is listed in the WSJT-X or JTDX DX Call field, the Decode List interface will persistently copy that callsign into the N1MM+ Entry Window callsign field (for example – the call will reappear after using <Wipe> to clear the N1MM+ Entry window). After you have completed a QSO in WSJT-X and it has been safely logged, you can use F4 in WSJT-X to clear the DX Call field while still running WSJT-X. This will clear the callsign field in the Entry window as well. If you are entering a contest that allows multiple modes, having WSJT-X or JTDX put calls into the Entry window, or having it clear the Entry window, is definitely not something you want to have happen while you are using another mode. Therefore, you should always close the WSJT Decode List window and shut down WSJT-X/JTDX before changing to a non-WSJT mode.
To change modes from a WSJT mode to a “normal” N1MM_ mode (CW, SSB, RTTY, PSK31/PSK63), type the name of the mode into the Entry window and press the Enter key. If this does not close the WSJT-X or JTDX program automatically, close it as well. Either way, the WSJT Decode List window should close. Now QSY to the frequency you want to operate the new mode in (for example, by typing the frequency into the Entry window) and carry on operating in that mode. To switch from that mode back to FT8, either use the >Window > Load WSJT/JTDX menu item, or just type FT8 into the Entry window Then use the >Window > WSJT Decode List menu item to open the WSJT Decode List window.
WSJT Decode List FAQs
Rig Control – Can both WSJT-X and N1MM+ control the radio?
Yes, if you are calling up WSJT-X from within N1MM+ using the >Window > Load WSJT/JTDX menu item and N1MM+ and WSJT-X have both been configured appropriately. When you do this, N1MM+ handles rig control on behalf of WSJT-X, using the same technique as is used by the DXLab Suite Commander program (which is why WSJT-X is configured to use “DX Lab Suite Commander” as its rig control method).
However, if you run WSJT-X stand-alone instead of from within N1MM+, the only way that both programs can control the radio is if you are using a port splitter or virtual serial port application. If you do not have some kind of port splitting program to allow two programs to control the radio simultaneously, then plan on disabling rig control from N1MM+ and allowing WSJT-X to “drive” the radio settings whenever it is active. If you want to make contacts in RTTY, you will have to close WSJT-X or disable its rig control, re-enable rig control in N1MM+, and put N1MM+ into RTTY mode. Experimentation prior to the contest is highly recommended – see also FAQ #5.7 below.
There are a number of possibilities for port splitting. If your radio is one of those that supports one of these programs, one of the Win4K3Suite/Win4YaesuSuite/Win4IcomSuite programs may do what you need. N8LP’s LP-Bridge program is another possibility, although with at least one caveat — apparently, WSJT-X might only work with LP-Bridge’s Virtual Serial Port #1, i.e. the leftmost virtual port in the LP-Bridge window. Yet another option may be to use the DXLab Suite’s Commander program for rig control, configure WSJT-X to use Commander instead of controlling the rig directly, configure Commander’s “secondary CAT port” to lead and follow the primary port and use the Kenwood protocol, then configure N1MM+ to use the Kenwood protocol for radio control and connect it to Commander’s secondary CAT port via a connected virtual serial port pair (com0com). This is described in the DXLab Suite Wiki under “Interoperating with Software-Defined Radios”, substituting N1MM+ for the SDR software. Note that the only rig control functions supported by Commander’s secondary CAT port are frequency and mode control. Advanced control functions such as CAT1ASC macros, RIT control, filter width commands and PTT via radio command from N1MM+ will not work using this method.
When using one of these methods, you may encounter problems with N1MM+ changing your radio mode from the setting required by WSJT-X for data versus the mode setting in N1MM+. Generally speaking, the radio mode you use for WSJT-X will be the same as the radio mode you would use for PSK. Therefore, if the Mode sent to radio is set up correctly under the Mode Control tab in the Configurer, then N1MM+ must be put into PSK (digital) mode (from the Entry window) whenever you are operating from WSJT-X. If you leave N1MM+ in RTTY mode (or CW or SSB), it may put the radio into the wrong mode (e.g. FSK or LSB for RTTY instead of USB or USB Digital for PSK/WSJT-X).
If you do share radio control using one of these methods, some of N1MM Logger+’s features may not work. The N1MM+ Development Team is unable to help with such situations, since the port splitting method used is outside our control. If you encounter problems with N1MM+ while using one of these methods, then before reporting a problem, please test to make sure you can reproduce the problem with no port splitting program active or involved. If you cannot reproduce the problem with no port splitting software in the picture, we are not likely to be able to resolve it.
No Rig Control – Does it work without rig control?
Yes. It is possible to use WSJT-X without rig control – but this requires some careful attention to detail when changing bands. You will need to change bands manually in both programs every time you change bands on the rig. Checking for duplicates and multipliers will not work correctly if the N1MM+ program is not set to the band you are operating on. Operating without rig control also means that some of WSJT-X’s features, notably the “Split” or “Fake It” techniques used to keep the sound card audio in the 1500-2000 Hz “sweet spot”, as well as the automatic choice of operating frequency depending on the mode selection, will not work.
Compatibility with JTAlert – Can I run JTAlert at the same time?
No. The current versions of JTAlert and N1MM+ do not permit port sharing. You must close JTAlert for the WSJT Decode List to function. Furthermore, if you enable both the WSJT-X -to- N1MM+ logging interface and the JTAlert logging interface (without using the WSJT Decode List window in N1MM+), your contacts will be double-logged into the N1MM+ contest database.
Supported Contests – Does this only work with specific contests or can I use it with my general log?
You can use the WSJT Decode List with your general DX log or with one of the contests supported by WSJT-X.
For general logging, use WSJT-X in normal non-contest mode and use the DX log in N1MM+. Make sure the Mode category in the Contest Setup window for your DX log is set to SSB+CW+DIGITAL. If you leave it at the default SSB+CW, digital mode contacts made from WSJT-X may not be logged correctly, and the dupe checking will be wrong.
For contest logging, you will need to set the contest mode in WSJT-X under the Advanced tab in the Settings window. Check the check box called “Special operating activity” and then select the applicable contest and if necessary, fill in the contest exchange box. In N1MM+, open a contest log of the appropriate contest type, make sure the Mode category includes DIGITAL, and in the Entry window, put N1MM+ into Digital mode (e.g. by typing FT8 into the call sign box and pressing Enter).
Callsign Colors – What do the callsign colors mean?
The callsign colors displayed by WSJT Decode List are derived from your N1MM+ settings found in the >Config >Manage Skins, Colors, and Fonts >Colors window under 3. Callsign Background Colors. By default those colors are:
- Grey = dupe or non-workable (zero-point contact)
- Blue = normal (new contact but not a new multiplier)
- Red = new multiplier
- Green = double multiplier (not applicable in contests supported by WSJT-X at this time, but may apply in future)
Serial Numbers – Will serial numbers from the two programs be in sequence?
In a word, no. If you make some contacts from N1MM+ (in RTTY, for example) and some contacts from WSJT-X (in FT8), the serial number sequences from the two programs will not be in sequence. There is no way for WSJT-X to know what serial numbers you have used in N1MM+, so it will issue its own serial numbers independently of what N1MM+ does. Don’t try to edit serial numbers to make the sequence look pretty – just accept whatever the two programs generate. What matters most is that your log reflects accurately what your software actually sent.
What do I need to do to switch between CW/SSB/RTTY and FT8?
To go from SSB, CW or RTTY to FT8, if you are running WSJT-X from within N1MM+, open it using the Entry Window’s >Window > Load WSJT/JTDX menu item. If you are running WSJT-X stand-alone, first change the radio’s mode to the mode you use for FT8, then (unless you have some kind of port sharing working) disable rig control in N1MM+ to allow WSJT-X to control the rig (in the Configurer, change the Port column for the rig control port to None) before starting WSJT-X. Make sure the rig’s IF filtering is appropriate for FT8 (wide), and tune it to a frequency where contest FT8 QSOs are taking place (on the HF bands, the regular non-contest FT8 frequencies are not good places to try to make contest QSOs). Open the WSJT Decode List window in N1MM+. Note that if rig control is disabled in N1MM+ in order to run WSJT-X stand-alone, then whenever you change bands in WSJT-X or on the radio, you also have to change bands in N1MM+ to ensure that the band in N1MM+ agrees with the band the radio is on, otherwise dupe and mult checking will be incorrect.
To go from FT8 to RTTY (or any other mode operated from N1MM+), first close the WSJT Decode List window and WSJT-X. If you were running WSJT-X in stand-alone mod and you do not have some kind of port sharing method active to allow both programs to control the rig at the same time, enable rig control in N1MM+ by setting the Port listbox for the rig control port to the port used for rig control. Make sure the rig is set to the correct mode with the appropriate filtering, and tune it to an appropriate frequency (presumably not the frequency you were using for FT8).
Note that if you leave WSJT-X running with the WSJT Decode List window active while you are trying to make RTTY contacts, WSJT-X will take control of the N1MM+ Entry window and you will be unable to log RTTY contacts. WSJT-X is persistent in sending the characters from its DX Call field into N1MM+’s Entry Window callsign field. Even if DX Call is empty (blank) it sends a blank to N1MM+ – wiping out anything you may try to enter in N1MM+. You must close the WSJT Decode List window and the WSJT-X program when operating from N1MM+. Conversely, you must do all of your FT8 operating from WSJT-X. Do not try to enter anything into the N1MM+ Entry window while WSJT-X is active and the WSJT Decode List window is open.
Why are my FT8 contacts being scored with zero points?
If your FT8 contacts are being assigned zero points in the Log and Score Summary windows, it is likely that you have selected the wrong Mode category in the N1MM+ contest setup. Use the File > Open Log in Database… menu item to open the contest setup dialog window, and change the Mode category from RTTY to DIGITAL (ARRL RTTY contest), or from SSB+CW to SSB+CW+DIGITAL (VHF contests, general DX logging).
The logging interface into N1MM+ does not refresh the contest score when you change the contest category. Use the >Tools >Rescore Current Contest menu item to rescore previously-logged QSOs, and the score should be accurate thereafter (as long as you don’t change contest settings again).