Frequently Asked Questions

Honest answers for hams who've been doing Field Day just fine without this, thank you very much.

Why Bother
My favorite Field Day logging software works fine. Why would I switch?
You don't have to switch. Field Day Commander has its own built-in logger, but it doesn't force anyone off the software they know. It shares the event log with N3FJP contest logs over TCP, receives contacts over UDP from N1MM Logger+ and from digital-mode programs like WSJT-X, JTDX, and fldigi, and can import ADIF files if you'd rather bring contacts in after the fact. The reason to bring Field Day Commander in is everything else Field Day involves: volunteer scheduling, equipment tracking, safety checklists, guestbooks, NTS message handling, and scoring with all 18 ARRL bonus categories (or the Winter Field Day objectives). If your club coordinates all of that with spreadsheets, paper sign-ups, and group texts, Field Day Commander puts it in one place. Operators who prefer their own software can keep using it.
My club uses paper logs and a spreadsheet. We do fine.
Plenty of clubs do, and there's nothing wrong with that. But if your club has ever had duplicate contacts across stations that nobody caught until Cabrillo review, or an empty operator chair at 2 AM because two people thought the other one had that shift, or the safety checklist didn't get done because everyone assumed someone else handled it... those are the problems Field Day Commander solves. If none of that has ever happened to you, you're either very organized or very lucky.
Is this just another Field Day logger with a web UI?
No. It includes a fast multi-station logger, but that's one piece of it. Field Day Commander also handles pre-event planning (stations, equipment, schedules, safety checklists), contact intake from N1MM Logger+ and digital-mode software like WSJT-X and fldigi (via UDP, plus ADIF file import), a visitor guestbook, NTS radiogram tracking, photo uploads, role-based access control, and live scoring with the full ARRL bonus point formula. The logging part is intentionally simple: a single-field entry flow designed for speed. The rest of the platform is what makes it different.
How is this different from cloud-based logging services?
Cloud loggers work well for individual operators and for sites with dependable internet. Field Day Commander is built for the Field Day site itself. Every station connects to a server on your own network, so multi-station logging and cross-station dupe checking keep working with no internet or cell service. Operators sign in on a shared station computer with their callsign, or with their own account on their own device, and the same system runs the schedule, equipment, safety checklist, guestbook, and bonus tracking. Your log stays on hardware your club controls.
Technical Concerns
What do I need to run it?
Operators can use it from any device with a web browser: Windows, Mac, Linux, a tablet, a phone, whatever. It's just a website on your local network. The server runs on Linux, which is only one machine. That could be a Raspberry Pi, the old PC in the ham shack, or any spare box. Linux is free, runs on nearly anything, and most hams with any tech background have touched it. The deploy script supports Ubuntu, Debian, 64-bit Raspberry Pi OS, and RHEL-family distros such as Rocky and AlmaLinux, and setup takes about 5 minutes.
Do I need to know Linux to set it up?
You need to be able to clone a git repo and run a shell script. The deploy command is sudo ./deploy.sh --domain YOUR_SERVER_HOSTNAME: replace YOUR_SERVER_HOSTNAME with a hostname your station devices can resolve. For example, fd-commander.local only applies to a device named fd-commander with working mDNS. The installation guide explains how to choose the address. The script handles everything: dependencies, database, web server. You don't need to configure Apache, edit PHP files, or touch a database. But if the phrase "SSH into the Pi" makes you uncomfortable, you'll want to recruit your club's tech person.
Can it actually run on a Raspberry Pi?
Yes. It's been tested on a Raspberry Pi 4 with 2 GB of RAM running off a battery pack. FrankenPHP and Laravel Octane keep the memory footprint small. A Pi is actually a great Field Day server: low power draw, fits in a pelican case, and you can prep it at home weeks before the event.
What happens if the server goes down during the event?
Operators keep logging. If a browser loses its connection to the server, contacts will queue locally on the device. When the connection comes back, they'll sync automatically. You don't lose contacts because someone tripped over the ethernet cable. If the server goes down entirely and you need to log on paper for a while, Field Day Commander has a paper log transcription feature so you can enter those contacts with the correct timestamps once you're back up. Either way, bring a spare SD card with a known-good image, and a recent backup to restore onto it.
Does it need internet access?
To deploy: yes. The install script downloads dependencies, so do this at home on your regular internet connection before the event.

To run: no. Once deployed, it runs entirely on your LAN with no cloud dependencies. The weather page is the only feature that uses the internet, and the rest of the app works without it. Many Field Day sites have no internet at all.
Can I put it on the internet so remote operators can log in?
Yes. Field Day Commander is a full Laravel application with role-based authentication, CSRF protection, and input validation. It's built the same way any production web app is, so exposing it to the internet is fine if your setup calls for it. This is especially useful in the weeks before the event: club members can register their equipment, sign up for operating shifts, and review station assignments from home instead of waiting until setup day. During the event, people who can't make it to the site can follow the live score, and you can make the guestbook accessible from a public URL.

If you do this, use TLS. Running over plain HTTP on a LAN is one thing. Running over plain HTTP on the open internet means passwords and session tokens travel in cleartext, which anyone on the path can read. Set up a TLS certificate (Let's Encrypt is free) and make sure all traffic goes through HTTPS. The deploy script supports this. There is no good reason to skip it.
Does it do CAT control or talk to my radio?
No. Field Day Commander doesn't key your radio, decode digital modes, or read frequency from CAT today. It works alongside software that talks to the radio, including N3FJP, N1MM Logger+, WSJT-X, JTDX, and fldigi, so each contact reaches the shared log as it's logged. Stations without that software use the built-in logger.
Logging & Scoring
Do I need separate logging software to use Field Day Commander?
No. Field Day Commander has a built-in logger. Operators open a browser on any laptop, tablet, or phone on the network and log contacts directly, with dupes checked across every station, live scoring, and Cabrillo export at the end. Connecting other software is optional: N3FJP contest logs share the event log over TCP. N1MM Logger+, WSJT-X, JTDX, and fldigi can send contacts into the same log over UDP.
Does it export Cabrillo?
Yes. Cabrillo export is a core feature. When the event ends, you can generate a Cabrillo file ready to upload to the ARRL submission page. For Winter Field Day, the file uses the WFDA's Cabrillo header, and you also get an Event Summary PDF with your objectives and score worksheet.
Does it support ADIF?
Import: yes. Field Day Commander can receive ADIF data in real time over UDP from N1MM Logger+ and digital-mode software such as WSJT-X and fldigi, and it has a file import wizard for uploading .adi/.adif files with station mapping and record validation.

Export: yes. The Reports page has an ADIF Log download alongside the Cabrillo file. It includes every credited, non-dupe contact with the band, mode, sub-mode, class, section, and operator, so you can load the weekend into the club's logging software.
Can I use my own logging software and still have contacts show up in Field Day Commander?
Yes. Field Day Commander can act as the TCP network server for N3FJP contest logs. It also has UDP listeners for N1MM Logger+, WSJT-X / JTDX, and a generic ADIF endpoint that works with fldigi and others. Turn on the server or listener for your program, then point the program at the server's IP and port. Dupe checking, scoring, and Cabrillo export all work the same whether a contact was logged in Field Day Commander's built-in logger or received from another program. You can also import an ADIF file after the fact through a guided wizard that lets you map stations and review every record before it's committed.
Can I use N3FJP with Field Day Commander?
Yes. N3FJP's ARRL Field Day Contest Log and Winter Field Day Contest Log can connect to Field Day Commander as TCP network clients. Each PC downloads the whole event log when it connects. New contacts, edits, and deletes go both ways, so contacts logged in Field Day Commander or on another N3FJP PC reach every connected N3FJP log within about a second for dupe checking. N3FJP networking doesn't have a password. Anyone who can reach the port can add, edit, and delete contacts, so keep it on your club LAN and never forward it from the internet. See Connect N3FJP Contest Logs for setup.
How does dupe checking work across multiple stations?
All contacts go into a single shared database in real time. When an operator enters a callsign, Field Day Commander checks it against every contact logged by every station. The same callsign on the same band and mode is a dupe, and it's flagged instantly before the contact is saved. No post-event deduplication needed.
Is a browser-based logger fast enough for a busy station?
It's a single input field. Type the callsign, the exchange info populates, hit Enter, and you're on to the next one. Dupe checks and section validation happen as you type, not after you submit. It's not going to beat dedicated contest software at a multi-multi, but for Field Day rates it's more than fast enough.
How does scoring and bonus point tracking work?
Scoring is automatic. Each contact is weighted by mode (CW and digital are 2 points, phone is 1). For ARRL Field Day, the power multiplier is applied based on your configured power source, and all 18 ARRL bonus categories are built in, including variable-point bonuses like Emergency Power (per transmitter), GOTA (per contact), Youth Participation, and NTS Messages. Some are tracked automatically (like safety checklist completion, NTS messages, or a verified guestbook entry from an elected official), others are claimed manually by the event manager (like media publicity or satellite QSO). Each bonus shows its status (claimed, verified, or unclaimed) so you can see at a glance what points you're leaving on the table. Winter Field Day works differently, and the app follows along. See the next question.
Does it really handle Winter Field Day, or is that an afterthought?
It handles it. Set the event type to Winter Field Day and the app picks the right scoring rules for the event. The score is QSO points × (objective multiplier + 1). There's no power multiplier and no GOTA, and the exchange uses the H, I, O, and M categories with MX and DX for stations outside the US and Canada. Each objective shows its multiplier and status. Band, mode, and QRP objectives are earned from your log automatically, and copying the WFD bulletin earns that one when you save it. For 2027, contacts in WSJT modes like FT8 and satellite contacts are still logged but marked "no credit," since the rules don't count them. At the end you get a WFDA-format Cabrillo log, an ADIF file, and an Event Summary PDF that follows the WFDA summary form.
Operations
Do operators need accounts?
Not to log. If a computer stays at a station and operators take turns on it, put it in station mode. A station captain binds the computer to its station, and operators sign in by typing their callsign, with no password. If the callsign is new, they'll be asked for a first and last name, and the app will create a placeholder account that an admin can turn into a real login later. At a GOTA station, the coach signs in with their own callsign and enters each GOTA operator on the logging screen.

Accounts are still worth having for everything else. They're how operators sign up for shifts, add their gear to the equipment catalog, and get the permissions that go with their role. An admin can create accounts ahead of time, or operators can register themselves before the event.
What about visitors? Do they need accounts too?
No. The guestbook is open. Visitors sign in with just a name and optionally a callsign. No account, no password. You can hand someone a tablet and they can sign themselves in. Each visitor picks a category (general public, ham club member, youth, media, elected official, and so on), and elected official and agency visits count toward their ARRL bonuses.
Can I use this for contests other than Field Day?
Field Day Commander supports ARRL Field Day and Winter Field Day (run by the Winter Field Day Association), each scored under its own published rules. The scoring, bonus categories and objectives, exchange format, and Cabrillo export are specific to those events. If you're looking for a general contest logger, this isn't it. Focus is a feature, not a limitation.
How many simultaneous operators can it handle?
More than you'll need. The server uses persistent workers (Laravel Octane on FrankenPHP) and a dedicated WebSocket process (Laravel Reverb) for real-time updates. Even on a Raspberry Pi 4, the stack can handle dozens of simultaneous connections without breaking a sweat. A typical Field Day site runs maybe 5 to 15 stations. That's nowhere near the limit.
Trust & Project
Is it really free? What's the catch?
It's free and open source under the GPL v3 license. No paid tiers, no "premium" features, no telemetry, no accounts on someone else's server. The code is on GitHub. The catch is that it's maintained by a ham in their spare time, not a company with a support department. File issues on GitHub, and be patient.
Who maintains this?
K3CPK. Licensed for over 10 years, organizer for several Field Day events, and tired of Field Day software that felt outdated and only ran on one OS. Field Day Commander grew out of fdlogdb, an earlier Field Day logging tool that proved the concept but hit its limits. Field Day Commander is the full rebuild with everything that project taught him. It's open source and the code is on GitHub for anyone to fork, contribute to, or audit.
What if it breaks during Field Day and there's no support?
This is a real concern with any self-hosted open-source tool. Mitigate it: test your deployment at home well before the event, do a dry run with your club, keep a backup SD card imaged and ready, schedule automatic backups with the included backup.sh script (see Back Up and Restore), and make sure at least one person in the club is comfortable reading a log file. If all else fails, you can always fall back to paper for a while. When the server comes back up, Field Day Commander has a paper log transcription feature that lets you enter those contacts with the correct timestamps so nothing is lost.

If you find a bug, please open an issue on GitHub. Say what you were doing, what you expected, and what happened instead, and include any error message. That's the quickest way to get it fixed.

See for yourself

Clone the repo, deploy it on a spare Pi or any Linux box, and kick the tires before Field Day.