Send contacts from N1MM Logger+, WSJT-X, JTDX, and fldigi straight into Field Day Commander.
Your operators already know their favorite programs, and there's no reason to make them give those up for the weekend. Field Day Commander can listen on the local network for contacts sent by N1MM Logger+, digital-mode programs like WSJT-X, JTDX, and fldigi, and anything else that sends ADIF over UDP. Each contact lands in the log a moment after the operator saves it, where it counts toward the score, gets checked for dupes, and shows up on the dashboards. Frequency, reports, grid, name, and comment come through when supplied. Look for frequency, reports, grid, and name in Details, or on the contact card line on a phone. This is optional: stations that don't run any of this software log in Field Day Commander's built-in logger with nothing to configure.
This guide walks through one logging PC from start to finish. Plan on about fifteen minutes for the first PC and a few minutes for each one after that.
N3FJP contest logs connect to Field Day Commander as TCP network clients rather than sending contacts over UDP. Follow Connect N3FJP Contest Logs for that setup.
192.168.1.50 as the server address.UDP has no authentication. Anyone who can reach these ports can send contacts into your log. Only turn the listeners on when Field Day Commander is on a private, firewalled network, and never on a server that is reachable from the internet.
Each program sends a small UDP packet to the server every time a contact is logged. Field Day Commander runs a separate listener for each kind of program, and each listener has its own port:
| Program | Listener | Default port | Station is matched by |
|---|---|---|---|
| N1MM Logger+ | N1MM Logger+ | 12060 | The PC's computer (NetBIOS) name |
| WSJT-X, JTDX | WSJT-X / JTDX | 2237 | The station callsign |
| fldigi and other ADIF senders | UDP ADIF (fldigi, etc.) | 2238 | The station callsign |
When a contact arrives, Field Day Commander works out which station it came from, who was operating, and which band and mode were in use. It then opens an operating session for that station automatically, so the station shows up as Occupied on the Log Contact page just as if someone had signed in through the browser. A session closes on its own after about 30 minutes without a new contact.
The mode the program reports, such as FT8, RTTY, or USB, is saved as the contact's Sub-mode, so the logbook shows entries like "Digital · FT8." Scoring still goes by the CW, Phone, or Digital group, with one exception covered in the Winter Field Day note below.
Some stations chain programs together, such as WSJT-X or fldigi feeding N1MM Logger+. In that case, let N1MM Logger+ send the contacts and leave the other program pointed at N1MM. If both programs send the same contact to Field Day Commander, it will arrive twice and the second copy will be marked as a dupe.
The deploy script opens the web port but not the listener ports. If your server runs UFW, check whether it's active:
sudo ufw status
If the status is active, open the port for each listener you plan to use:
sudo ufw allow 12060/udp # N1MM Logger+ sudo ufw allow 2237/udp # WSJT-X / JTDX sudo ufw allow 2238/udp # fldigi and other ADIF senders
On a server that uses firewalld instead, the equivalent is:
sudo firewall-cmd --permanent --add-port=12060/udp sudo firewall-cmd --reload
Repeat the first command with 2237 and 2238 if you use those listeners.
If neither firewall is active, there's nothing to do here. Raspberry Pi OS doesn't turn one on by default.
The included docker-compose.yml already publishes all three UDP ports. If you change a listener's port in Field Day Commander, set the matching N1MM_PORT, WSJTX_PORT, or UDP_ADIF_PORT value in your .env file to the same number, then run docker compose up -d so the container picks it up.
1 Sign in to Field Day Commander and open Logging > External Loggers.
2 Find the card for your program and flip its toggle on. The status changes from Starting listener... to Listening on port 12060 (or whichever port that listener uses), followed by packet and error counters.
3 Leave the page open. The packet counter is the quickest way to tell whether the logging PC can reach the server, and you'll use it in a moment.
The default ports work for nearly everyone. If you need a different one, turn the listener off first, since the port field is locked while the listener is switched on. Ports from 1024 to 65535 are allowed.
You don't need to babysit the listeners. Field Day Commander checks on them every minute and restarts any that have stopped unexpectedly. If the External Loggers page is open, it restarts them within a few seconds.
Every contact carries an identifier for where it came from. Field Day Commander compares that identifier with the name of each station in your event, then with each station's Hostname (NetBIOS Name) field. Neither comparison cares about capitalization. If nothing matches, Field Day Commander creates a new station named after the identifier, so contacts are never lost, but they may land somewhere you didn't expect. A few minutes of setup here keeps the stations tidy.
N1MM Logger+ identifies itself by the PC's computer name. To find it, open a Command Prompt on the logging PC and run:
echo %COMPUTERNAME% SHACK-PC-2
In Field Day Commander, open Stations, edit the station that PC will run, and enter that name in the Hostname (NetBIOS Name) field. Repeat for each N1MM Logger+ PC.
These programs identify contacts by the station callsign in the log record, which is normally your club or event callsign. That means every digital PC using the same callsign lands on the same Field Day Commander station. Pick the station that should receive those contacts, usually your digital station, and enter the event callsign (for example, W3XYZ) in its Hostname (NetBIOS Name) field.
Contacts are credited to the operator whose callsign the sending program reports. If that callsign belongs to a Field Day Commander user, the contact goes to them. If it doesn't, Field Day Commander creates a callsign-only account for that callsign, with (Imported) as its last name, so the contact still has an operator. A callsign-only account has no password-based login. It shows a No Sign-In badge under Administration > Users, and an admin can turn it into a real login later with Activate Account, which keeps the operator's contacts with them. Inviting your operators before the event, with their callsigns filled in, keeps contacts attached to their existing accounts.
If the sending program doesn't report an operator at all, the contact may end up with no operator, or with a placeholder for whatever callsign the program fills in by default. Each program section below shows where the operator's callsign goes, and it's worth making that part of every operator change.
Follow the section for your program, then come back for Step 5. Repeat this step on every logging PC, since these settings are stored on each PC.
The official N1MM Logger+ UDP documentation explains the Broadcast Data controls, destination format, and contact update/delete messages.
1 In the Entry Window, open Config > Configure Ports, Mode Control, Audio, Other and select the Broadcast Data tab.
2 Check Radio and Contacts. Leave All Computers unchecked, since each PC will report its own contacts. In a networked N1MM setup, misconfigured stations with All Computers turned on can send contacts around in a loop.
3 Enter the server's address and port as the destination, written as 192.168.1.50:12060. To send to more than one program, separate the destinations with a space, as in 127.0.0.1:12060 192.168.1.50:12060. If your version shows a separate address box for Radio and for Contacts, fill in both.
4 Click OK. N1MM Logger+ sends a radio status packet at least every 10 seconds, so the packet counter on the External Loggers page should start climbing almost right away.
5 Make sure the PC is logging in an ARRL Field Day contest log (or the Winter Field Day log for a WFD event), so the received class and section are sent in their own fields.
6 When an operator sits down, have them press Ctrl+O (or type OPON in the callsign box) and enter their own callsign. That's the callsign Field Day Commander uses for operator credit.
If an operator edits or deletes a contact in N1MM Logger+, the change carries over to Field Day Commander.
For the sending side, the WSJT-X project’s UDP integration manual identifies the Reporting > UDP Server settings. Field Day Commander’s listener and station mapping are configured separately below.
These steps match WSJT-X 3.0. Open the settings with File > Settings (or press F2).
1 On the General tab, set My Call to your event callsign.
2 On the Advanced tab, check Special operating activity, choose ARRL Field Day, and enter your own exchange in FD Exch, such as 3A MDC. In this mode, WSJT-X logs the other station's class and section in their own fields. Without it, contacts still arrive, but they won't have a section for the section map.
3 On the Reporting tab, enter the operator's callsign in Op Call. Update it at each operator change, or contacts will be credited to the previous operator.
4 In the UDP Server group on the same tab, set UDP Server to the server's IP address (192.168.1.50) and UDP Server port number to 2237. Use the server's regular address, not a multicast group. The Outgoing interfaces field only appears for multicast addresses, so you won't see it with this setup.
5 Click OK. WSJT-X sends a heartbeat packet every 15 seconds, so the packet counter should start climbing within 15 seconds. Contacts are sent when the operator clicks OK in the Log QSO window.
The UDP Server setting holds a single address. If this PC also runs JTAlert, GridTracker, or N1MM Logger+'s WSJT-X integration, those programs expect WSJT-X's traffic as well. Either point WSJT-X at Field Day Commander and do without the companion program, or leave WSJT-X pointed at the companion program and have it pass contacts along. With N1MM Logger+, that means letting its broadcast carry the contacts, as described above. Some companion programs, such as GridTracker, can rebroadcast WSJT-X traffic to another port; check that program's documentation for details.
The WFDA’s 2027 rules don't allow WSJT modes (FT8, FT4, JT65, Q65, MSK144, and the rest) or satellite contacts. When your event is scored by those rules, the WSJT-X card on the External Loggers page shows a yellow No credit notice. Those contacts still arrive and stay in the log, marked no credit, but they earn no QSO points and count toward no objective. JTTY is the exception and scores as a normal digital contact. The ARRL Field Day activity in WSJT-X is for June Field Day only.
JTDX is built on WSJT-X and sends the same UDP messages, so it uses the same WSJT-X / JTDX listener on port 2237. Its UDP server settings are on the Reporting tab of its Settings window. Enter the server's address and port there, just as you would in WSJT-X.
Use the Digital Modes with fldigi guide for the complete operating setup and a practice-contact test. The official fldigi contesting manual explains its local exchange fields and logbook.
These steps match fldigi 4.2. Open Configure > Config Dialog.
1 On the Operator-Station page, set Station Callsign to your event callsign and Operator Callsign to the current operator's callsign.
2 On the Contests/Field Day page, fill in your class and section.
3 Go to the Logging/Cloud-UDP page. In the Broadcast UDP ADIF record group, set Address to 192.168.1.50 and Port to 2238. fldigi defaults to port 9876, so this one needs changing.
4 Click Select Fields and confirm that the callsign, date, time on, band, frequency, mode, station callsign, operator, class, and section fields are selected. They're all selected out of the box, so this is only a check.
5 Check Enable, then click TEST. The packet counter on the External Loggers page should go up by one. The test packet isn't a real contact, so Last Contact Received won't change.
Any program that can send plain ADIF records over UDP can use the UDP ADIF (fldigi, etc.) listener on port 2238. Field Day Commander needs at least the callsign, date, and time of each contact. Include the band or frequency, mode, station callsign, operator, class, and section for full credit and a complete log.
A climbing packet counter proves the network path works. A test contact proves the whole chain works.
1 Log a contact in the sending program.
2 On the External Loggers page, expand Last Contact Received under that listener. You should see the callsign, band, mode, section, and QSO time.
3 Look at the badge next to it. Accepted means the contact is in the log. outside event window means the contact's time falls outside the event's start and end times, so Field Day Commander turned it away.
Contacts are only accepted between the event's start and end times, so any test you run the week before will show outside event window. This confirms that Field Day Commander received and read the packet, but it does not test whether a contact is accepted into the log.
To test acceptance before the weekend, use a short practice event that covers your test time, as described in Set Up Multi-Station Logging. Check for an Accepted badge and find the contact in the log. Once the real event starts, also check that the station shows as Occupied on the Log Contact page, with the operator's callsign and source program.
.env.Field Day Commander tries to restart it automatically, and you can click Restart Listener. If it keeps crashing, another program on the server is probably using the same port. Pick a different port for the listener and update the logging programs to match.
sudo tail -50 /var/www/fd-commander/storage/logs/laravel.log and look for "packet processing error."The identifier didn't match any station's name or hostname, so Field Day Commander created one. Add the identifier to the Hostname (NetBIOS Name) field of the station it belongs to (Step 3). New contacts will go to the right place from then on. Contacts that already arrived stay on the station that was created for them.
The operator's callsign in the sending program didn't match any Field Day Commander user. Check for typos in N1MM Logger+'s operator login, WSJT-X's Op Call, or fldigi's Operator Callsign, and make sure the operator's Field Day Commander account has their callsign filled in. If the operator should have a personal sign-in, find it with the No Sign-In (callsign only) status filter on Administration > Users and use Activate Account.
WSJT-X only logs the class and section in their own fields when ARRL Field Day is selected under Special operating activity. Turn it on (see the WSJT-X steps above).
Fill this in before Field Day and tape a copy to each logging table:
Server IP: _______________
N1MM Logger+ port: 12060
WSJT-X / JTDX port: 2237
fldigi / ADIF port: 2238
Event callsign: _______________