Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

  • Entries

    7
  • Comments

    0
  • Views

    188

Entries in this blog

A contest weekend can put hundreds of contacts in your log, but a contact only helps your DXCC, WAS, WPX, or IOTA progress once it is confirmed in a form the award sponsor accepts. Many operators finish a contest happy with the score and then let the log sit. A little planning before and after the event turns a pile of QSOs into usable award credit.

Start with the award, not the contest

Different awards reward different things, and a contest can serve several of them at once:

  • DXCC counts entities, so ARRL DX and CQ WW are rich hunting grounds. Each new entity matters more than your hundredth contact with a familiar one.
  • WAS needs all fifty states. State QSO parties and Field Day put many stations in many states on the air, which makes them useful for finding the last few.
  • WPX counts prefixes. Because the prefix is part of the callsign, almost every contest contact has award potential, and CQ WPX is built around it.
  • IOTA depends on island groups. Contest stations on islands often announce this, but you have to notice it and log the contact correctly.

Knowing which award you are working on tells you which contacts are worth a second look in the log, and which are only points for the score.

Set up confirmation before the contest starts

Logbook of The World (LoTW) is the most practical way to confirm many contacts, but it does not work until both operators have uploaded. Do the slow steps well in advance:

  • Install TQSL and request your callsign certificate. Identity verification can take time, so do not leave it for the Friday before a contest.
  • Confirm that your station location in TQSL is correct, including DXCC entity, grid square, and the zone or state details that apply to you. Wrong location data can create confusing matches or rejected credit later.
  • Test your logging program's export. Know where the ADIF file is created and how to feed it into TQSL.

Remember that Cabrillo is the format for submitting a contest entry. ADIF is the format you will normally use for LoTW and other logbook services. They serve different purposes, so do not assume one file does both jobs.

Log cleanly while operating

Confirmation problems often begin at the key or microphone. A few habits help:

  • Check the callsign. A busted call is the most common reason a contact never matches. If a call is partial or uncertain, ask for it again. In a pileup this costs seconds, but it can save a contact that you will never get back.
  • Match band and mode. LoTW matches on band and mode groups, so a contact logged on the wrong band because of a missed frequency change will not match.
  • Keep your computer clock accurate. LoTW matching allows a time window, but a clock that is minutes off can still cause mismatches. Use a reliable time sync, especially if you run digital modes.
  • Log exchange details faithfully. State, zone, serial number, and other exchange data should be what you received, not what you assumed.

Understand the weak points of contest confirmations

A contest does not guarantee that the other station uploads to LoTW. Some operators submit a contest log and never upload to any confirmation service. Others use LoTW regularly. That means your confirmation rate will vary depending on who you worked, how popular LoTW is in their region, and whether the contact was made in a well-organized event.

For rare entities, DXpeditions and island activations often have their own logging and upload practices, and IOTA activators may not always follow the same workflow as mainstream contest stations. Treat any one confirmation channel as helpful but incomplete.

Use a simple post-contest routine

  1. Back up the log in its original form before editing anything.
  2. Fix obvious errors, such as a callsign typo or an incorrect band, before you upload anything. Do this carefully and only when you are sure of the correction.
  3. Export ADIF and sign it with TQSL, then upload. Check the confirmation message so you know the file was accepted.
  4. Wait for matches over the following days and weeks. Confirmations do not all arrive at once.
  5. Look for award-critical contacts. Flag new entities, new states, new island groups, or new prefixes that are still unconfirmed.

Chase the gaps, not the whole log

Once uploads settle, build a short list of unconfirmed contacts that matter. For DXCC, those might be new entities that appeared only once. For WAS, they might be the states you still need. For WPX, you may care less about any single prefix, since a large number of them will arrive over time, but you can still check for missing ones near an award threshold.

For each gap you can try several options. Check the callsign for a typo. Look at the station's published QSL information, if there is any. Send a polite follow-up with your log details if the operator accepts them. Paper QSLs and bureau cards are slower, but they can still be useful for contacts that never reach LoTW and for awards that accept those cards. Always check the current rules and accepted confirmation types for the specific award before spending time or money on cards.

Keep an award tracker

A simple spreadsheet or the tracking tools built into many logging programs can keep your progress visible. Record the entity, state, prefix, or island group, the date, the band and mode, and the confirmation status. Separate columns for LoTW, paper QSL, and other methods make it easier to see where a contact stands.

Do not rely only on memory or on how many contacts you remember making. Award programs have specific rules, and your own tracker should reflect what has actually been confirmed, not what you hope to get credit for.

Beginner lessons that pay off

  • You do not need to win the contest to benefit from it. A few hours of focused operating can add several new entities or states.
  • Accuracy beats speed when award credit is the goal. A clean log is more valuable than a large one with many busted calls.
  • Prepare your accounts and software before the weekend. Waiting until after the contest to learn TQSL is stressful and risks delays.
  • Choose contests that match what you need. If your WAS list is short, a state QSO party may be better for you than a worldwide event.
  • Be patient. Confirmation is a long game, and many matches arrive well after the contest ends.

Contests are great for making contacts quickly. Award chasing is about making those contacts count. If you handle the logging and confirmation steps with the same care you give to tuning and calling, each contest weekend will do more for your long-term progress.

Every contest weekend, you decide between two ways of operating, often without noticing. You can run, which means parking on a frequency and calling CQ so others come to you. Or you can search and pounce (S&P), tuning the band and calling stations you find. Neither one is better in general. The right choice depends on your antennas, your power, the contest, and what you want out of the weekend: a score, a new multiplier, or progress toward an award.

What each style is good at

Running builds rate, the number of contacts per hour. A steady run frequency can produce long strings of QSOs with very little tuning. It works best when you can be heard reliably. That usually means a decent antenna, a clean signal, and a band that is open to a populated area. It also puts you in front of stations you would never have found by tuning.

Search and pounce builds variety. You can work a station once, log it, and move on. That makes S&P a good way to collect multipliers, such as new countries, zones, states, or prefixes. It is also the practical choice with modest power or a small antenna, because a strong station calling CQ is far easier to work than being the weak one calling.

Most good contest strategies mix the two. You run when the band is giving you rate, then switch to S&P to pick up multipliers that your run frequency never produced.

Rate and multipliers: how they trade off

Contest scoring generally combines points from QSOs with a multiplier count. That creates a tension. A new multiplier is worth more late in the contest than early, because it multiplies a bigger QSO total. Meanwhile, hunting for a rare multiplier can cost you minutes of rate.

A few rules of thumb help:

  • Early on, focus on rate and let the multipliers come naturally.
  • When your run slows, use the downtime to tune for multipliers instead of calling CQ into silence.
  • On each new band, a quick sweep for multipliers can be worth more than the same minutes spent running.
  • Check the rules for your contest. Multiplier definitions differ, and some count per band while others count once overall.

Match the contest to the style

Different events reward different habits.

  • ARRL Field Day is more of an operating event than a pure race. It rewards activity, emergency-style setups, and a wide mix of modes. Many groups run stations around the clock and rotate operators. It is also a friendly place to learn logging and exchange procedures.
  • CQ WW (separate SSB and CW weekends) is a worldwide event where DX is the point. Zones and countries are the multipliers, so it suits anyone chasing DXCC entities. Because the whole world is on the air, even a small station can find multipliers by S&P.
  • ARRL International DX Contest has a different shape depending on where you live. Stations outside the US and Canada work US and Canadian stations, and the reverse applies for those in the US and Canada. Check the current rules for your side of the exchange.
  • State QSO parties are a good source of WAS contacts. In-state stations often work everyone, while out-of-state stations may chase counties or the local multipliers. These contests can fill in the awkward states that never seem to show up on ordinary band days.
  • CQ WPX uses prefixes as multipliers, which suits people building a WPX tally. Each new prefix is a multiplier and a step toward the award.

Always confirm dates, categories, and exchanges from the official rules. They change from year to year.

SO2R without the hype

SO2R (single operator, two radios) lets you use one radio to call CQ while the other tunes for the next contact. In practice you are filling dead time. Each CQ gap on radio one becomes a chance to search on radio two.

It is not a beginner requirement, and it can hurt more than it helps if the station is not ready. The usual problems are:

  • Receiver overload: a nearby transmitter can swamp the second receiver unless you have filtering and good antenna separation.
  • Audio switching: you need to know which radio you are hearing and transmitting on, or you will send an exchange on the wrong one.
  • Logging errors: two radios double the chance of a mismatched callsign or frequency.

A reasonable first step is a simple version. Run on one radio and use the second only to listen for multipliers. Add transmit control later, after you are comfortable with the single-radio flow.

Logging habits that protect your score and your awards

Good logging does two jobs. During the contest it speeds up your exchanges. Afterward, it feeds your award records.

  • Use contest logging software that handles the exchange and checks for duplicates.
  • Confirm your CAT or rig-control setup before the contest starts, so the log records the right band, mode, and frequency.
  • Fix callsign errors immediately. A bad call is a lost QSO and often a penalty.
  • Keep your station location details consistent, because award software and confirmation services match on those fields.

Turning contacts into confirmed progress

A contact only counts toward most awards once it is confirmed. For DXCC, WAS, WPX, and IOTA, the details of what is accepted depend on the sponsor, so read the current award rules. In general:

  • Logbook of The World (LoTW) confirms a contact when both stations upload matching logs. Both sides need to be valid, and the details must agree closely enough to match, including band, mode, date, and time.
  • Paper or electronic QSL cards still matter for some awards, particularly where an operation is not on LoTW.
  • Contest logs and award tracking work best when you upload promptly. A stale log leaves you with unconfirmed contacts you could have had weeks earlier.

Track your progress by category as well as by total. DXCC is about entities, WAS is about states, WPX is about prefixes, and IOTA is about island groups. A single weekend can move several of those counts at once, but only if you note which contacts are new for each award.

Beginner lessons that pay off quickly

  1. Enter for a few hours. You do not need the whole weekend. A short session teaches the exchange and the pace.
  2. Listen first. Hear a few exchanges before you call, so yours matches what people expect.
  3. Keep your exchange short and clear. Repeat only what is needed. Clarity beats speed when the band is crowded.
  4. Have a goal. A new state, a new zone, or ten more prefixes is easier to chase than a vague aim to do well.
  5. Mix running and S&P. Try both and notice which one fits your station.
  6. Upload your log and check your confirmations. Contest activity only turns into award progress once the matches show up.

Choosing between running and S&P is really a question about your station, your time, and your goals. Start with the style that fits your antenna and your pace, and add the other when it makes sense. After a few weekends, you will know where your rate comes from, which multipliers you are missing, and which awards each weekend moved forward.

Most operators treat the final minute of a contest as the finish line. The log is where the lessons are. A short review routine after Field Day, CQ WW, ARRL DX, or a state QSO party can improve next year's rate, clean up your submission, and push your DXCC, WAS, WPX, and IOTA records forward. None of it needs fancy software.

Step 1: Check the log before you submit it

Open your logging program and look for obvious problems before you export anything. Common ones include:

  • Wrong contest settings. Check the category, power level, operator class, and exchange format. A misconfigured exchange can make an entire log harder to score.
  • Time and band errors. Make sure the clock was right and that QSOs sit on the bands you actually used. If you use CAT control, confirm the logged frequency and mode matched the radio.
  • Missing or odd exchanges. Scan for blank fields, suspicious zones or sections, and callsigns with unusual characters.
  • Duplicate contacts. Read the rules for the event. Some contests count a repeat contact on the same band and mode as a dupe, and some have other rules. Do not assume.

Then follow the sponsor's instructions for the log format. Many contests use Cabrillo, but the exact header fields and submission method come from the current rules, so read them each time rather than relying on memory.

Step 2: Hunt for busted calls

A busted call is a contact logged with a callsign that is slightly wrong. It costs you the QSO and may cost a penalty depending on the contest's checking. The fix is simple: scan for calls that appear only once and look unfamiliar, and compare them with what you remember hearing. A call-history or call-check feature in your logger can help, but treat it as a hint, not proof.

When you spot a likely error, fix it only if you are confident from your own notes or audio. If you are unsure, leave the entry as logged or follow the contest's guidance on uncertain contacts. Never edit a log to make it look better than what actually happened.

Step 3: Study rate and multipliers

A raw QSO total hides the story. Break the weekend into hours and ask a few questions:

  • When did my rate peak? If your best hours were on one band, note when it opened and whether you were on it.
  • Where did I lose time? Long stretches of calling CQ with no replies, slow band changes, and hunting a single weak station are all worth noting.
  • How did multipliers arrive? Look at when you picked up new zones, sections, states, or prefixes. Multipliers often come in bursts after a band change or a switch from calling CQ to search-and-pounce.
  • What was my balance? Running a frequency tends to produce steady rate, while tuning around often finds multipliers. Most scores benefit from mixing the two.

A one-page note with two or three changes for next time is more useful than a long spreadsheet. For example: "Move to 15 meters earlier," or "Set up a memory keyer for the exchange."

Step 4: Turn the contest log into award progress

Contests are efficient for award chasing because so many stations are on the air at once. After the event, check your log against what you need:

  • DXCC: Look for new entities, and band or mode entries if you track those. The award is based on confirmed contacts with entities on the DXCC list, so a new-sounding prefix is not automatically a new entity. Verify it against the current list.
  • WAS: State QSO parties and ARRL DX (where W/VE stations work DX) are strong hunting grounds, depending on your location and the event format. Mark states that still need confirmation.
  • WPX: Prefix variety matters. Your contest log is a record of which prefixes you worked, but check the award rules for how the program counts and what documentation it needs.
  • IOTA: Island stations can be sparse in ordinary operating but may appear in contests. Make sure the reference number was actually part of the exchange or confirmed some other way, because IOTA credit depends on proper identification.

Each program has its own rules about which confirmations count. Review the current requirements before you decide how to chase a particular credit.

Step 5: Handle confirmations

Submitting a Cabrillo log to the contest sponsor is not the same as confirming contacts for awards. LoTW (Logbook of The World) is a separate system. To use it, you generally need a certificate, a signing tool (TQSL), and an upload of your station data. A confirmation appears only when the other station has also uploaded a matching QSO.

Practical tips:

  • Check that your station location in TQSL matches where you operated. Field Day or portable operation may need a separate location entry.
  • Upload soon after the contest. Many stations upload quickly, so matches may arrive within days or weeks. Others never upload.
  • For stations you really need and who are not on LoTW, a paper or electronic QSL card may be an option. Check the preferred method for that station and the rules of the award you are pursuing.
  • Keep your logs backed up in ADIF form so you can re-import them if you change software.

Step 6: Consider SO2R only when the basics are stable

SO2R (single operator, two radios) means using two transceivers so that one can listen or call while the other is transmitting or searching. It can raise your rate, but it adds complexity: audio switching, interlock between radios, headphone routing, and software support. If your single-radio log still shows frequent exchange errors, a missed multiplier plan, or long dead stretches, solve those first. Many operators start by learning to run efficiently and search-and-pounce effectively before adding the second radio.

A short checklist for beginners

  1. Read the rules and exchange format a week before the event.
  2. Test your logging software, including time sync and CAT control.
  3. Decide whether you want a casual or competitive approach. Both are legitimate. Even a few hours on the air teaches a lot.
  4. After the event, review busted calls, rate, and multipliers.
  5. Submit the log as required, then upload your QSOs to LoTW and check award needs.
  6. Write down two or three improvements to try next time.

Treat each contest weekend as a cycle: operate, review, confirm, and improve. After a few cycles, you will see your rate grow and your award lists fill in without feeling like extra work.

Digital ham radio can feel like alphabet soup. Many of these modes use the same sound card, the same computer, and sometimes the same radio, but they solve very different problems. Choosing the right one first saves hours of fiddling with settings for a mode that was never going to do what you wanted.

This guide groups the common tools by what they are good at, then covers the shared plumbing that makes almost all of them work: audio, timing, rig control, and logging.

Start with the goal, not the mode

Ask what you are trying to accomplish:

  • Make contacts with weak signals and a modest station: FT8 (or its relatives in the WSJT-X family).
  • Have a slower, keyboard-style conversation with weak-signal tolerance: JS8Call.
  • Share position, weather, or short messages on a map: APRS.
  • Send real email or formatted forms over radio: Winlink.
  • Move data between stations over VHF/UHF links: packet radio.
  • Talk by voice through a digital network: DMR, D-STAR, or System Fusion.
  • See what the bands are doing: an SDR, plus PSK Reporter and the Reverse Beacon Network.

FT8 and the WSJT-X family

FT8 uses fixed 15-second transmit/receive cycles and a highly structured, compact message format. That structure is why it can decode signals well below the noise floor, and why it needs accurate clocks. Your computer time should be within about a second of true time, and a network time sync tool or a reliable GPS-based source is worth setting up before you blame anything else.

The settings that matter most in WSJT-X:

  • Audio input and output: select the right device for your radio interface, not the computer's built-in microphone.
  • Receive level: aim for a moderate reading on the WSJT-X level meter rather than pinning it at either end.
  • Transmit level: set the output so the radio shows little or no ALC action. A clean, lower-power signal beats a splattery strong one. Overdriven digital signals are wider than they should be and bother neighbors.
  • Rig control: choose CAT, or PTT through a serial line or VOX if that is what your interface supports. CAT lets the software read and set frequency and mode.
  • Split operation: using the rig's split mode or the software's fake-it option helps keep audio tones in a clean part of the passband.

If a decode problem persists, check the basics in order: time, audio device, radio mode (typically USB with data options if your radio has them), filters, and then CAT.

JS8Call: a different feel

JS8Call builds on FT8's modulation but is designed for keyboard-style messaging, directed calls, relay between stations, and heartbeat-style presence. It is slower than FT8 and rewards patience. Setup is similar: accurate time, correct audio, and sensible levels. It suits casual conversation and low-power experimentation. It is not a replacement for a formal emergency communication system, though it can be a useful tool in a larger plan.

APRS and packet

APRS runs on AX.25 packet. In North America, the common VHF frequency is 144.390 MHz, using 1200 baud AFSK. Stations send beacons, positions, weather data, and short messages, and digipeaters or internet gateways carry them farther. A basic setup might be a handheld or mobile radio with a tracker, or a software TNC on a computer using the sound card.

Beyond APRS, general packet radio lets you build point-to-point links, bulletin boards, and node networks. It is a good place to learn how addressing, retries, and acknowledgments work. Many hams find a Raspberry Pi is a handy small host for these projects, since it can run a software TNC, a digipeater, or a monitoring station in a small, low-power box.

Winlink for email over radio

Winlink lets you send and receive email-style messages through radio gateways, with a client such as Winlink Express on the computer. It can use several transport methods, including packet, and HF modes like VARA, ARDOP, or Pactor, depending on your hardware. Before you rely on it, practice:

  1. Set up your account and confirm the client works over a normal internet connection first.
  2. Move to a radio connection and test with a nearby gateway.
  3. Learn which gateways are reachable at your location and which bands propagate to them at different times of day.
  4. Keep messages short, since bandwidth over radio is limited.

The advantage is a familiar email workflow even when the internet is unavailable. The cost is more setup than weak-signal modes.

DMR, D-STAR, System Fusion, and hotspots

These are digital voice systems, and they are not interoperable with each other without a gateway or bridge. Each has its own radios, codec, and network approach. Many people join them using a hotspot, a small personal low-power access point connected to the internet, often built around a Raspberry Pi or similar board with a modem board.

When setting one up:

  • Confirm the hotspot's mode and frequency on a clear spot, away from repeater channels you use locally.
  • Align the frequency offset between hotspot and radio. A small error can cause garbled audio or no connection.
  • For DMR, you generally need a registered ID and correct color code and talkgroup settings. For D-STAR and Fusion, the callsign routing and reflector or room settings matter.
  • Keep the hotspot's power low, as it is meant for local coverage.

SDR, PSK Reporter, and RBN

A software-defined radio gives you a waterfall view of what is actually on the band. That is excellent for diagnosing a weak signal, seeing interference, or checking your own transmitted bandwidth with a second receiver.

PSK Reporter and the Reverse Beacon Network collect reception reports from many stations. They answer a simple question: who heard me, and where? If you call CQ on FT8 and nobody answers, a quick look at PSK Reporter tells you whether your signal is being heard. Zero spots from a busy band might point to antenna, power, or timing issues, while a good spread of spots suggests propagation or a crowded frequency. RBN does a similar job for CW and RTTY, which is useful for checking your signal during contests.

Logging and rig control

Logging software ties the operating tools together. Log4OM is a general logger with strong support for digital modes and award tracking, and it can receive logged contacts from WSJT-X automatically. N1MM Logger+ is a staple for contesting, with fast entry, rate displays, and integrated radio control. Whatever you choose, think through three things:

  • One source of truth: decide which program holds the master log and which ones only forward contacts.
  • One owner for the CAT port: a serial port can usually be opened by only one program at a time. If two programs fight over it, use a rig control sharing tool or a virtual serial port pair.
  • Consistent frequency and mode data: mismatches here can cause confirmation problems later with online logbooks.

Common interface and sound card pitfalls

  • Operating system audio enhancements or auto-gain settings can distort digital tones. Turn them off.
  • System sounds mixed into the transmit audio can cause an accidental noisy transmission. Use a dedicated sound device or mute alerts.
  • Ground loops cause hum and RF feedback into audio. Ferrite chokes and good grounding practice often help.
  • USB devices can change port numbers after a reboot, so recheck COM or device paths when CAT suddenly fails.
  • Baud rate, stop bits, and handshake settings must match between software and radio.

A sensible learning order

If you are building out a digital station, a gradual path works well: begin with FT8 to get audio, time, and CAT working, add a logger, then explore PSK Reporter to evaluate your signal. From there, pick the next mode based on interest, whether messaging with JS8Call, mapping with APRS, email with Winlink, or voice with a hotspot. Each step reuses skills from the last, and the same discipline applies throughout: clean audio, accurate timing, one program per control port, and a log you trust.

Contest weekends and award goals work well together, but only if you pick the right weekend for the right goal. A big DX contest can fill in a lot of DXCC entities. It will do almost nothing for Worked All States. A state QSO party is the reverse. Before you clear your calendar, decide what you want out of the weekend: more countries, more states, more prefixes, or just practice at running a pileup.

Exact dates and rules change from year to year, so check each sponsor's current rules page. What follows covers how each type of event tends to work and what it is good for.

Match the event to the award

DXCC: ARRL DX and CQ WW

In the ARRL International DX Contest (CW and phone weekends), stations in the US and Canada work stations outside those countries. For someone in the US, nearly every contact is a possible new entity, so it is one of the most efficient ways to chip away at DXCC. In CQ WW (an SSB weekend in October and a CW weekend in November), everyone works everyone. Entities and CQ zones both count as multipliers, so rare stations get called constantly and you hear a wide range of the world in 48 hours.

Remember that a contest contact only helps your award if the other station's log reaches a confirmation system. Contest operators often upload to LoTW after the weekend, but you should not assume it will happen.

WAS: state QSO parties

State QSO parties are where Worked All States gets easier. Stations inside the host state send a county or similar exchange, and many parties are active on several bands over a weekend or part of one. If you are missing a few of the less common states, check the calendar for their QSO parties and plan to be on the air during those hours. Some states are only reliably active during their party.

Mobile and rover stations make these events fun. They change counties constantly, so the same operator can be worth several contacts for county hunters. For WAS, though, you only need each state once per band or mode category you are chasing.

WPX: prefixes as multipliers

The CQ WPX contests (SSB in March, CW in May) use each new callsign prefix as a multiplier. That makes the contest friendly to beginners. You do not need to know country lists or zone maps, just the exchange, which is a signal report and a serial number. Serial numbers also teach you good logging habits, because you have to keep count correctly.

IOTA: islands on purpose

The RSGB IOTA Contest, usually held in late July, encourages activity from islands and island groups. If you are working toward Islands on the Air credit, this is the weekend when many expeditions and island stations are on the air at once. Look up each island's reference group so you know which stations you are hearing. Check the IOTA programme's current rules on what confirmations it accepts.

Field Day: a different animal

Field Day, held in late June, is more of an operating exercise than a pure contest. It is about emergency-style setups, working from temporary sites, and meeting your local club. It can still be a great way to practice rate-oriented operating and logging, and many people enjoy it as a first experience of running a station in a team. Treat it as a skill builder first and an award source second.

Rate and multipliers: the basic trade-off

Rate is how many contacts you make per hour. Multipliers are new countries, zones, states, prefixes, or whatever the contest counts that you have not yet worked on a given band. Most scores come from qualifying contacts multiplied by the number of multipliers, so both matter.

A useful rule of thumb is to keep a good rate when the band is open and strong, then go multiplier hunting when rate slows. In practice that means:

  • Run on a clear frequency and call CQ when stations are plentiful.
  • Search and pounce when you need a new multiplier or the band is quiet. Tune across the band and call stations that are already on the air.
  • Watch your logger's multiplier display so you know what is still needed on each band.

Beginners often start with search and pounce because it feels less exposed than running. That is a good place to start. When you are comfortable with the exchange, try running for a short stretch, even 15 minutes.

Logging habits that protect your awards

Good logs are the basis of everything else. A few habits pay off at every skill level:

  • Check your computer clock. Confirmation systems match contacts by time as well as by callsign, band, and mode. A badly set clock can ruin a match.
  • Use contest-aware logging software that flags duplicates and tracks multipliers automatically.
  • Fix callsign errors immediately. A single wrong letter can produce a busted contact for you and a missed one for the other station.
  • Keep your station information consistent (grid, zone, and so on) so exports and uploads are correct.
  • Back up the log during and after the event.

A Cabrillo file for the contest sponsor is not the same thing as an upload for award confirmations. Check which of these your logging program does and whether you need to do both.

QSL and LoTW confirmations

Logbook of The World (LoTW) is run by the ARRL and is widely used for confirmations toward DXCC and WAS. A confirmation requires both stations to upload logs that match. That is why a contact with a station that never uploads will sit unconfirmed. Paper or electronic QSL cards, or direct requests, are still used when a rare station does not use LoTW.

Some practical points:

  • Upload your own contest logs promptly after the weekend. Other people may be waiting on your side to complete a match.
  • If a confirmation does not appear, compare the band, mode, and time in your record with what the other station would have logged.
  • Keep track of what is confirmed and what is just worked. Award applications use confirmed contacts.

SO2R can wait

SO2R stands for single operator, two radios: one radio runs while the second searches for the next multiplier. It can raise a score a lot, but it needs interfaces, audio switching, headphones, and a lot of practice. A beginner will usually gain more from learning the exchange, getting faster at copying callsigns, and understanding band changes. Come back to SO2R once you can run a rate on one radio without mistakes.

A simple plan for your first award-minded weekend

  1. Pick one award you want to move forward.
  2. Choose a contest that fits it: DX contests for DXCC, state QSO parties for WAS, WPX for prefixes, the IOTA contest for islands.
  3. Read the rules a week ahead, including the exchange, the categories, and the log submission deadline.
  4. Test your logger, CAT control, and audio before the contest starts.
  5. Set a modest goal, such as 50 contacts or a certain number of multipliers.
  6. Upload your log afterward and check your confirmations over the next few weeks.

You do not need to enter all 24 or 48 hours. Operating for a few hours in a well-chosen event, with careful logging, can do more for your awards than a long weekend without a plan.

Contesting and award chasing look like two hobbies, but they feed each other. A contest weekend can hand you dozens of new band-entities, states, or prefixes in a few hours. Awards give you a reason to care about the contacts afterward, when the confirmations arrive. If you are new to either side, understanding how they connect makes both more rewarding.

Know what kind of event you're entering

Different events reward different habits, so it helps to separate them early.

  • ARRL Field Day is more of an operating exercise than a pure race. Groups set up portable or emergency-style stations, and the scoring includes bonus points for things like alternative power and public activities. It is one of the friendliest ways to try contest-style operating, because there is usually a team to learn from.
  • CQ World Wide (CQ WW) is a worldwide event in which the multipliers are based on DX entities and zones. It is held in separate CW and phone weekends. Activity is huge, which makes it a great chance to log new countries.
  • ARRL International DX Contest has a different structure: stations outside the US and Canada work stations in the US and Canada, and vice versa. If you are in North America, you are looking for DX, and the multiplier is typically the ARRL section or country depending on which side you are on. Always read the current rules for exact details.
  • State QSO parties are regional events in which in-state stations try to work everyone, while out-of-state stations chase counties or states. They are excellent for Worked All States (WAS) and for county-hunting awards.

Rules change from year to year, including exchanges, categories, and submission deadlines, so check the sponsor's current rules before you operate rather than relying on memory.

Rate versus multipliers

Two ideas drive almost every contest decision.

Rate is how many contacts you make per hour. Running on a clear frequency and calling CQ is the classic way to build rate, since stations come to you one after another.

Multipliers are the things that multiply your score: countries, zones, states, sections, prefixes, depending on the contest. A new multiplier on a new band is usually worth more than another ordinary contact, because it increases the factor applied to your whole QSO total.

The practical tension is that running builds rate, while searching for multipliers means tuning around, which slows rate. Many operators alternate: run while the band is productive, then "search and pounce" through the band to pick up multipliers when the run slows down. A good rule of thumb is to watch your own results. If nobody is answering your CQs, go hunting. If calls are stacking up, stay put.

What SO2R actually is

SO2R means single operator, two radios. One radio is calling CQ while the other listens elsewhere for multipliers or another run frequency. It uses the gaps in a CQ cycle that would otherwise be dead time.

It is not a beginner requirement, and it is easy to get wrong. It needs hardware or software to switch headphones, audio, and transmit control, and it needs interlock so you never transmit into a receiver or two transmitters at once. It also demands good filtering to avoid interference between the radios. Treat it as a later step after you are comfortable with one radio, a good logger, and decent band strategy.

Logging: the unglamorous skill that wins

Good logging software saves you in several ways:

  • It checks for duplicates, so you do not waste time working the same station on the same band twice.
  • It tracks multipliers and tells you what you still need on each band.
  • It supports sending messages and pre-recorded or keyed exchanges with function keys.
  • It generates the Cabrillo file most contests require for submission, and an ADIF file for award and confirmation tracking.

Practice with your logger before the contest. Many people lose points not because of bad propagation but because they were fighting the software while the band was busy. Set up your callsign, exchange, and radio control in advance, and confirm that your clock is accurate, since time matters for matching logs.

Awards worth knowing about

  • DXCC recognizes confirmed contacts with a large number of DX entities. Entities are not identical to countries, and the official list is maintained by the ARRL. It has multiple tiers and band and mode endorsements.
  • WAS (Worked All States) requires contacts with all fifty US states. State QSO parties and big domestic contests are natural places to fill gaps.
  • WPX relates to working different callsign prefixes, and it pairs naturally with the CQ WPX contests, which count each new prefix as a multiplier.
  • IOTA (Islands on the Air) recognizes contact with islands and island groups that have official reference numbers. Island expeditions often operate in contests, so contest weekends can add progress here too.

Each program has its own rules about eligible dates, modes, and verification, so check the sponsoring organization's current requirements before you plan.

QSL cards and Logbook of the World

A contact only counts toward most awards once it is confirmed. There are a few routes:

  • Logbook of the World (LoTW) is the ARRL's electronic system. You upload signed log data, and when the other station uploads a matching contact, you get a confirmation. It is fast and widely accepted for ARRL awards like DXCC and WAS.
  • Paper QSL cards still matter, especially for some awards and for stations who do not use LoTW. They can be sent direct or through a bureau, which is slower but cheaper.
  • Other online systems exist, and some awards accept them, but acceptance varies by program.

For LoTW to match, details must agree: callsign, band, mode, and date and time within tolerance. Typos in a callsign, a wrong band, or an incorrect time zone setting are common reasons contacts do not match. Upload your log shortly after the contest while you still remember any oddities, and keep your records clean.

Lessons for beginners

  1. Start small. Operate for a couple of hours rather than the whole weekend. Participation is valuable by itself.
  2. Listen first. Spend time hearing how experienced operators send exchanges, so you can copy the pattern quickly.
  3. Keep your exchange short and clean. Send your callsign clearly, confirm only what you need, and move on.
  4. Do not be afraid of a low score. Submitting a log still helps other participants verify contacts.
  5. Plan bands by time of day. Higher bands tend to open during daylight, lower bands at night, but conditions vary, so be flexible.
  6. Take breaks. Fatigue causes mistakes, and a short rest often improves your total.
  7. Review afterward. Compare your log with the rules and note which multipliers you missed, then use that to set a goal for next time.

Putting it together

A sensible path is to pick one contest, learn its exchange, and set one modest goal: perhaps a number of contacts, a few new multipliers, or one new state. Log carefully, upload to LoTW afterward, and use the results to guide your next award target. Over time, the contests supply the contacts and the awards give those contacts lasting meaning. Progress in DXCC, WAS, WPX, and IOTA tends to come in steady steps, and every well-kept log is a step forward.

When FT8 misbehaves, the symptoms are vague: the waterfall looks fine but nothing decodes, the radio keys but nobody answers, or WSJT-X loses the rig halfway through a session. The cause is almost always one of four things: time, audio, CAT/PTT, or reporting. Work through them in that order and most problems disappear.

1. Check your clock first

FT8 runs in fixed 15-second cycles, and both stations must agree on where those cycles begin. If your computer clock is off by more than about a second, you will miss decodes, and other stations will miss you. Look at the DT column in the decode window. Most stations should show values near zero. If nearly everyone shows a similar offset, such as +1.0 or -0.8, the problem is your clock, not theirs.

  • Make sure automatic time sync is enabled in your operating system.
  • Use a dedicated time-sync utility if your OS only syncs occasionally.
  • On a Raspberry Pi, confirm that an NTP service such as chrony or systemd-timesyncd is running and has actually synchronized. Pis have no battery-backed clock, so a headless Pi with no network can drift or start with the wrong time.

2. Get the audio path right

If the waterfall is blank or flat, WSJT-X is listening to the wrong input. Open File > Settings > Audio and select the radio's USB audio device or your external interface for both input and output. Then check these points:

  • Sample format: In your operating system's sound settings, use 48000 Hz, 16-bit for the device if you have the choice.
  • Disable audio extras: Turn off system sounds, enhancements, and anything that might route notifications through the radio's audio device. A stray alert tone going out on the air is a common and embarrassing mistake.
  • Receive level: The WSJT-X level meter should sit roughly around the middle, with the User Guide suggesting about 30 dB. Too low and weak signals vanish. Too high and you risk clipping on strong ones.
  • Radio settings: Use USB or the radio's data mode (often labeled USB-D, DATA, or PKT), keep the receive filter wide enough for the whole 200 to 3000 Hz range, and turn off noise reduction, notch filters, and speech processing. These can damage digital signals.

If the waterfall shows signals but nothing decodes, suspect time first, then confirm you are on the right mode and sideband. FT8 and FT4 are different modes with different sub-bands and timing. A common FT8 frequency on 20 meters is 14.074 MHz, but verify the current band plan for your region before transmitting.

3. Transmit audio: less is more

Many new digital operators overdrive their transmitters. FT8 is a constant-envelope mode, so a clean signal does not need much drive. Set the radio to a modest power level, then adjust the WSJT-X output slider until the ALC meter barely moves or stays at zero. If the ALC is working hard, the signal is being distorted, which creates splatter and lowers your decode rate at the other end.

Also remember that FT8 transmits for most of the cycle, so the duty cycle is far higher than SSB. Running a radio at full rated power for long periods can overheat it. Backing off to a fraction of rated output is good practice and often costs you very little in practical results.

4. CAT control and PTT

CAT lets WSJT-X read and set frequency, mode, and PTT through the radio's serial or USB connection. Under Settings > Radio, choose your rig from the list, select the correct serial port, and match the baud rate to the radio's menu setting. Then click Test CAT. A green button means communication works. Test PTT separately, since a rig can accept frequency commands and still fail to key.

Typical failure points:

  • Port conflicts: Only one program can normally open a serial port. If a logger or rig-control program already has it, WSJT-X cannot connect. Either let one program own the port and share it through Hamlib's rigctld, or use a virtual serial port tool.
  • Wrong port after reboot: USB port numbers can change. Recheck the COM port or /dev/ttyUSB device name if things worked yesterday and fail today.
  • Baud mismatch: The radio and software must use the same rate. Some radios also have a separate CI-V or CAT rate setting for USB.
  • Split operation: Under Radio, choose Rig or Fake It to keep your audio tones in the radio's cleanest range. Avoid None if your transmit audio frequency sits high in the passband, because harmonics may leak outside the intended channel.
  • RF in the shack: If CAT drops out only when you transmit, you probably have RF getting into the USB cable or interface. Ferrite chokes, better grounding, and a decent common-mode choke on the antenna feedline often cure this.

For PTT, CAT PTT is simplest when it works. Otherwise use a serial line (RTS or DTR) on an interface that supports it, or VOX if you must. VOX is less predictable with computer audio, though.

5. Confirm your signal with PSK Reporter

Once you transmit, the easiest reality check is PSK Reporter. In WSJT-X, enable PSK Reporter spotting on the Reporting tab. Then search for your callsign on the PSK Reporter map to see who is hearing you, on which band, and at what signal level. If you transmit for several cycles and nobody reports you, check antenna, band conditions, power, and whether the radio is actually outputting RF.

Do not confuse this with the Reverse Beacon Network. RBN uses skimmer receivers mainly for CW and RTTY, so it is the right tool for those modes, but it will not show your FT8 signal. For FT8, JS8Call, and similar modes, PSK Reporter is the usual feedback tool.

6. Make your logger cooperate

WSJT-X can write an ADIF log and broadcast QSO information by UDP, which loggers such as Log4OM can use. If contacts do not appear in your logger, check that the UDP server address and port match on both sides and that your firewall is not blocking local traffic. For contest software such as N1MM+, there are supported ways to work with digital modes, but setup varies by version, so check the current documentation. Avoid running two programs that both try to control the radio unless you have deliberately planned how they will share the CAT connection.

A quick diagnostic order

  1. Is the clock synchronized, and do DT values cluster near zero?
  2. Does the waterfall show signals, and is the input level reasonable?
  3. Is the radio in the right data mode on a legitimate FT8 frequency?
  4. Does Test CAT pass, and does PTT key the rig?
  5. Is ALC quiet and power conservative?
  6. Does PSK Reporter show you being heard?

The same logic carries over to JS8Call, Winlink soundcard modems, and packet or APRS TNC setups. Time sync, clean audio levels, reliable PTT, and a single owner for the CAT port are the foundation of nearly every digital station. Fix those, and the software side of the hobby becomes much more predictable.


Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.