Digital Modes with fldigi

Work RTTY and PSK at Field Day, log as you go, and send every contact to Field Day Commander.

How-To Guides › Digital Modes with fldigi
Logging · Digital

Digital contacts count two points each at Field Day, the same as CW. With fldigi, operators can read the exchange on screen and log most contacts with a few clicks and button presses.

This walkthrough covers June ARRL Field Day using sound-card RTTY and PSK31. Set up receive audio, transmit audio, and push-to-talk at home before trying it at the site. Menu names can vary between fldigi releases.

Where to Find Digital Signals

Normal Digital Activity Frequencies

These are approximate conventional activity areas in MHz, not exclusive channels. The RTTY ranges describe areas to search; the PSK31 values are common USB dial starting points. Listen and inspect the waterfall before choosing a clear frequency.

BandRTTY search area (MHz)PSK31 USB dial (MHz)Normal FT8 USB dial (MHz)
80m3.580–3.6003.5803.573
40m7.080–7.1007.0707.074
20m14.080–14.10014.07014.074
15m21.080–21.10021.07021.074
10m28.080–28.10028.12028.074

ARRL Field Day Recommended Frequencies (2026)

The normal FT8 dial frequencies above are not the Field Day recommendations below. Field Day activity can differ from everyday operation. The ARRL 2026 Field Day packet recommends these FT4 and FT8 subbands, which overlap several RTTY search areas above:

BandFT4 subband (MHz)FT8 subband (MHz)
80m3.580–3.5903.590–3.600
40m7.080–7.0907.090–7.100
20m14.080–14.09014.090–14.100
15m21.080–21.09021.090–21.100
10m28.080–28.09028.090–28.100

ARRL describes these as recommended subbands, not mandatory or exclusive channels. They do not reserve the spectrum for one mode. Avoid occupied signals, including FT4 and FT8, and check the current year's Field Day packet before the event. Keep clear of the 14.100 MHz international beacon frequency; see the ARRL band plan.

The radio's USB dial frequency is the suppressed carrier, not the frequency of every signal on the waterfall. A PSK31 signal at 1500 Hz audio with a 14.070 MHz dial is centered at 14.0715 MHz. Allow room for the entire transmitted signal when choosing a frequency near a band edge or another signal.

Tuning around on digital is a lot like tuning around on SSB, except you do most of it with the mouse. Select the matching modem first: RTTY 45 with 45.45 baud and 170 Hz shift, or BPSK31 for PSK31. Use the Op Mode menu and check the RTTY settings under Configure > Config Dialog > Modem > RTTY. A RTTY signal looks like two nearby traces; PSK31 is a narrow trace. Click the signal to tune the decoder. This does not automatically select its mode. With transmit lock (Lk or Lck) off and no split configured, transmit follows receive tuning. Confirm that before replying. See fldigi's operating controls.

Use USB, even for RTTY

For the sound-card RTTY and PSK operation described here, use USB or the radio's corresponding USB data mode. fldigi also supports other RTTY arrangements, including LSB with reversed polarity and hardware FSK; those require their own setup. See the fldigi RTTY manual.

What a Digital Contact Looks Like

A digital Field Day contact is the same as a CW one, only on a screen. You send your class and section, they send theirs, and you're done. A club running three transmitters on generator power in Eastern Pennsylvania sends "3A EPA." DX stations send "DX" in place of a section.

Here's a whole contact, with you calling CQ as W3XYZ and K1ABC answering:

CQ FD CQ FD DE W3XYZ W3XYZ K # you K1ABC K1ABC K # them K1ABC 3A EPA 3A EPA K # you TU 2A CT 2A CT K # them K1ABC TU DE W3XYZ FD # you, and it's logged

That's the whole thing. No names, no rig, no weather report. The other operator wants to get to the next station as much as you do, so the friendliest thing you can do is keep it short.

One thing catches people out: Field Day counts every digital mode as the same mode. If your club worked K1ABC on 20m FT8 this morning, they're a dupe on 20m RTTY this afternoon. Work them on 40m instead, or on 20m CW or phone.

That also means your club can only have one digital signal on a band at a time. If the FT8 station is on 20m, you'll need another band until they move. Settle who gets which band before anyone sits down. A dedicated GOTA station is the exception to this band-and-mode restriction. See Run the GOTA Station and ARRL rules 6.3–6.9.

Set Up fldigi for Field Day

Do this at home, or at least before the generator starts. Create a separate event logbook with File > Logs > New logbook so previous events do not trigger duplicate warnings. Then open Configure > Config Dialog.

1 On Operator-Station, put your event callsign in Station Callsign and your own call in Operator Callsign. That second one changes every time someone new sits down, and we'll come back to it.

2 On Contests/General, set Contest to ARRL Field Day. Class and Section boxes show up next to the callsign in the logging area at the top of the main window. That's how you know it took. Enable duplicate checking by Call and Band. Leave mode, time-window, and other criteria out of the comparison so a previous RTTY contact also warns when you switch to PSK31 on the same band. This remains a check of the local log only.

3 On Contests/Field Day, fill in My Class and My Section, like 3A and EPA. Your macros pull your exchange from here, so you'll never have to type it.

4 On Logging/QSO logging, check Clear on save. Confirm single-left-click capture is enabled if you want to follow the click instructions below; otherwise use your configured Shift-click behavior. Without Clear on save, the last station's call and exchange sit in the log boxes after you save, waiting for you to clear them by hand.

5 If you can, connect fldigi to the radio through flrig or CAT under Rig Control. Then fldigi always knows what frequency you're on, and the log gets the right band. Without it, fldigi logs whatever is typed in the frequency box at the top left, and sooner or later somebody changes bands at 3 AM and forgets to update it.

6 Click Save, then Close.

Practice capturing a callsign, class, and section from received text, checking each destination field. Right-click a word and select its field if automatic capture gets it wrong. Test duplicate checking with a practice contact: the same callsign on the same band should warn, including after switching digital modes; the same callsign on another band should not. See the fldigi contesting manual and logging configuration.

Winter Field Day uses different instructions

fldigi's contest list includes ARRL Winter FD, although Winter Field Day is run by the WFDA. This June walkthrough's exchange examples, macros, and scoring discussion are not a Winter Field Day setup. Check the Winter Field Day documentation and the event year's rules before adapting them.

Last, set your transmit audio. This one matters most for how you sound on the air. Turn speech compression off and make initial adjustments into a suitable dummy load. Start with low audio drive, press TUNE, and bring the audio up until ALC just begins to show, then reduce it until ALC stops. Aim for a clean signal at the intended power, following your radio's data-mode guidance. Recheck drive at different audio positions in the passband and after power changes. See fldigi's audio-level setup.

Keep in mind that digital is key-down the whole time you're sending. If the radio is running warm after a long stretch of CQs, turn the power down some.

Macros

Macros save you from typing the same exchange for every contact. Press a button and fldigi fills in the callsign, class, and section, then sends the text.

fldigi doesn't come with a Field Day set, so here's one to start from. Right-click a macro button to edit it. Put <TX> and <RX> on their own lines like this, and use K when handing the conversation back to the other station. The closing TU and DUPE messages instead finish the contact or invite another caller.

When you're calling CQ

ButtonMacro text
CQ<TX>
CQ FD CQ FD DE <MYCALL> <MYCALL> K
<RX>
Exch<TX>
<CALL> <MYCLASS> <MYSECTION> <MYCLASS> <MYSECTION> K
<RX>
TU<TX>
<CALL> TU DE <MYCALL> FD
<RX><LOG>

When you're answering someone else's CQ

ButtonMacro text
Call<TX>
<MYCALL> <MYCALL> K
<RX>
Exch<TX>
TU <MYCLASS> <MYSECTION> <MYCLASS> <MYSECTION> K
<RX><LOG>

For when it gets messy

ButtonMacro text
AGN<TX>
AGN AGN K
<RX>
QRZ<TX>
QRZ? DE <MYCALL> K
<RX>
DUPE<TX>
<CALL> DUPE TU DE <MYCALL> QRZ?
<RX>

Two tags trip people up. <MYCLASS> and <MYSECTION> send your own class and section, using what you entered on the Contests/Field Day page. <CLASS> and <SECTION> (and their twins <FDCLASS> and <FDSECT>) send whatever is in the other station's log fields. If you see your macro sending someone their own exchange back, that's the mix-up.

Sending the exchange twice helps when signals are weak or QRM is heavy. When the band is busy and copy is solid, cut it to once and you'll make more contacts in an hour. AGN is the button you'll use the most, so put it somewhere easy to reach.

<LOG> saves the contact the moment you press the button. It does not wait for the transmission to finish, even when written after <RX>. Verify the received exchange before pressing TU or the answering Exch macro. Clear on save clears the fields immediately; watch that the outgoing message finishes correctly. With UDP sending enabled, check the saved contact in Field Day Commander as well. See the macro reference.

Once you're happy with the set, save it with File > Macros > Save ... as something like fieldday.mdf. Copy it to every digital PC and load it with File > Macros > Open .... That way every operator finds the same buttons in the same places, even at 2 AM.

Logging a Contact in fldigi

Here's the nice part: you barely have to type. With single-click capture configured, click words in the receive pane to fill the log. Otherwise use the configured Shift-click gesture. The contest parser helps assign fields, but always check the callsign, class, and section before saving.

1 Someone answers your CQ. Click their callsign in the receive pane. It pops into the Call box, and fldigi checks it against the log. A duplicate highlight means the call matches your configured criteria. Confirm the band and the earlier log entry before treating it as a dupe. Don't leave them hanging. Press DUPE to let them know they're a dupe and thank them for the call, so they can move on too. Then get back to calling CQ.

2 Press Exch to send your exchange.

3 When their exchange comes back, click their class and then their section. If fldigi puts a word in the wrong box, right-click it and pick Class or Section.

4 Check the callsign, received class, and section before pressing TU. That button logs immediately and starts the closing transmission. Watch it finish before moving to the next caller.

Answering someone's CQ goes the same way in a different order. Click their call off their CQ, press Call, click their class and section when they come back to you, check all three fields, then press the answering Exch macro. It logs immediately as your exchange starts transmitting; make sure the transmission completes.

A word of warning about RTTY: when there's nothing but noise, it prints random letters, and every so often those letters look like a callsign or a section. Only click on text from the station you're working. If you'd rather save by hand, the Save button (the disk icon) next to the log boxes does the same thing as <LOG>, and the broom icon next to it clears them.

If a contact needs correcting, find the existing record in both fldigi and Field Day Commander. Have someone with contact-edit permission correct Field Day Commander's record, and correct fldigi's local copy too. Do not assume a local edit updates the imported contact, and do not save a second QSO as a correction. During practice, check whether editing your installed fldigi version sends another record; inspect Field Day Commander afterward for an unchanged record or an extra copy and reconcile the logs.

Sending Contacts to Field Day Commander

Once fldigi is logging, it can send each contact to Field Day Commander as soon as you save it. That's what puts your digital contacts in the club's score, on the section map, and in the dupe check with every other station. The server side, including firewall ports and how stations are matched, is covered in Connect External Loggers. Configure fldigi, then test a complete contact:

1 In Field Day Commander, open Logging > External Loggers and turn on UDP ADIF (fldigi, etc.). It listens on port 2238.

2 In fldigi, open Configure > Config Dialog > Logging/Cloud-UDP. In the Broadcast UDP ADIF record group, set Address to your Field Day Commander server's IP address and Port to 2238.

3 Use Select Fields to include callsign, date, time on, band or frequency, mode, station callsign, operator, class, and section. Check Enable, then click TEST. A rising packet counter confirms receipt, not a complete or accepted contact.

4 In Field Day Commander, edit your digital station and put your event callsign in its Hostname (NetBIOS Name) field. fldigi identifies itself by the station callsign, and this is how Field Day Commander knows which station the contacts belong to.

Test a Complete Contact Before the Event

Create a short practice event covering the test time, as described in Set Up Multi-Station Logging. Use a separate fldigi practice log and match its station callsign to a station in that event. In a private, firewalled network, enable the listener and save a practice contact without transmitting a fictional exchange on air.

  1. Check Last Contact Received for an Accepted result, then find the contact in Field Day Commander's log.
  2. Compare the received callsign, band, digital sub-mode, class, section, date, and UTC time with fldigi's record.
  3. Confirm the intended station and operator received credit. Check for an unexpected automatically created station or operator account.
  4. Test same-band and different-band duplicate handling, switch between RTTY and PSK31, and test a record correction. Reconcile both logs afterward.
  5. Before real operation, select the real event, restore its station mapping and exchange, and open a fresh event logbook in fldigi.

A contact rejected as outside event window confirms receipt but does not pass this acceptance test. See the external logger guide for station matching and troubleshooting.

With the mapping and fields verified, each contact should show up in Field Day Commander as "Digital · RTTY" or "Digital · PSK31," credited to whoever is in fldigi's Operator Callsign box. fldigi has no idea when operators swap, so that box stays on the last person until somebody changes it. Make it part of the routine when someone new sits down (it's on the Operator-Station page). Otherwise the new operator's contacts all go to the person who just left for the food tent.

Field Day Commander catches what fldigi can't

fldigi checks only its local log using the criteria you configured. Leaving mode out of those criteria catches same-band repeats across RTTY and PSK, but it cannot see contacts made at other stations unless they are also in that log. Field Day Commander checks the whole club's log and treats all digital as one mode. So if K1ABC was worked on 20m FT8 earlier in the day, Field Day Commander will mark your 20m RTTY contact with them as a dupe, even though fldigi didn't flag it. It stays in the log but doesn't earn points.

Troubleshooting

RTTY prints garbage on a strong, clean signal

Check that the modem is RTTY 45 at 45.45 baud / 170 Hz shift, the radio is in USB or USB data mode, and the tuning markers align with the signal. If it still will not decode, try Rv to reverse polarity. If that does not help, check receive audio for clipping and confirm the signal really is RTTY. Restore the working polarity setting afterward.

Random letters fill the screen between contacts

That's RTTY printing the noise. Turn on SQL and slide the squelch up until the junk stops but real signals still print.

Stations say your signal is wide or hard to copy

Too much audio. Turn it down until the ALC stays at zero while you're sending, and check it again any time you change the power.

You're transmitting somewhere other than where you clicked

Look at the Lk button next to the waterfall. When it's lit, your transmit frequency is locked, and fldigi sends there no matter where you click. Click it off.

Contacts aren't showing up in Field Day Commander

Make sure Enable is still checked on the Logging/Cloud-UDP page, then go through the External Loggers troubleshooting steps. If the External Loggers page shows outside event window, the contact got there fine. Compare the QSO timestamp with the event window; it may be before the start or after the end. Use a practice event covering the test time to confirm a contact can actually be accepted.

Quick Reference

Fill this in before Field Day and tape it next to the digital station's keyboard:

Event callsign: _______________

My Class / My Section: _______ / _______

Field Day Commander server IP: _______________ Port: 2238

Operator change: Configure > Config Dialog > Operator-Station > Operator Callsign

Radio mode: USB / USB data; speech compression off.

fldigi modem: RTTY 45 (45.45 baud / 170 Hz) or BPSK31.

Before TU or answering Exch: Check the received exchange; logging is immediate.