Mode Field Errors in Mixed-Mode Contests: A Guide

17. November 20268 Min. LesezeitContest logging
Mode Field Errors in Mixed-Mode Contests: A Guide

Short answer: In a mixed-mode contest, each QSO line in the Cabrillo file carries a mode code such as CW, PH, RY or DG, and the mode often decides whether a QSO is a dupe, which band-mode slot it fills and how it is scored. Errors come from logger settings that do not follow the radio, from changing mode without telling the logger, from wrong conversion at export and from typing. Check the mode of the first QSOs after every mode change and read the file before submitting.

Where the mode appears

A Cabrillo QSO line contains the frequency or band, the mode, the date, the time, the callsigns and the exchange. The mode is a short code. In Cabrillo 3.0 the usual codes are CW for Morse, PH for phone, FM for frequency modulation, RY for RTTY and DG for digital modes other than RTTY. The exact list and what each contest accepts are given in the specification of the format and in the rules of the contest, and the articles on the Cabrillo QSO line and the frequency field describe the neighbouring columns.

In a contest limited to one mode, the field is the same on every line and rarely causes trouble. In a mixed-mode contest, which allows more than one mode, the field changes during the operation, and each change is an opportunity for an error. The contests page lists several contests with the mode MIXED, and the rules of each tell you how modes are treated.

Why the mode matters

The mode can influence the log in three ways. First, the dupe rule: in some contests, a station may be worked once per band and mode, so a QSO in CW and a QSO in SSB with the same station on the same band are both valid. If the mode is wrong, a valid QSO may look like a dupe, or a dupe may look valid. Second, the points: some contests give different points for different modes. Third, the multipliers: a multiplier may count per band and mode. A wrong mode can therefore change the score, in either direction.

Always check the current official rules to see how your contest treats modes. The article on cross-band dupes explained shows how the same idea applies to bands, and the principle is the same for modes.

Common sources of mode errors

The first source is the logger setting. Many loggers read the mode from the radio through a CAT interface, and some use the mode that you select by hand. If the interface is not working, or if the logger and the radio disagree, the mode in the log can be wrong without any sign on the screen. The second source is a mode change that is not registered: you switch the radio from CW to SSB, but the logger stays on CW until you press a key. The first QSOs in the new mode are then logged as CW.

The third source is the way the logger names the modes. Some programs use their own names, such as USB and LSB, and convert them at export. If the conversion table is wrong, the exported file has a wrong code. The fourth is the digital modes: PSK, FT8 and others can be exported as DG or as something else, depending on the program and on the contest rules. The fifth is typing: in manual entry, a mistyped letter or a wrong choice from a drop-down list gives the wrong code. And the last is a mix of logs, for example when two computers use different mode settings and the logs are merged. The article on merging logs from several computers lists related problems.

Check the mode after every change

The simplest habit is to look at the mode on the screen after every change and to check the first QSO. Say it to yourself: “Mode SSB, logged as phone”. It takes a second. If your logger shows the mode in the entry line or the log window, glance at it. If the logger has a warning for a mismatch between the radio and the log, turn it on. In a mixed-mode contest, build a routine: change the mode on the radio, then in the logger, then the first QSO.

If you operate with two radios, check each radio and each logger window separately. The article on SO2R basics explains how two radios share one log, and a mismatch between the radio and the log is an easy mistake when the focus switches from one to the other.

Check the log during the contest

Every few hours, scroll through the log and look at the mode column. Do the modes follow the pattern of your operation? A block of QSOs in a mode that you were not using, or a single QSO in a different mode among many of the same, is a sign of an error. Correct it at once, while you remember what you did. It is much easier than to find the problem in a file of thousands of lines later.

It also helps to see the log sorted by time with the mode shown, so that mode changes appear as visible steps. If the changes do not match your memory, investigate. The habit costs one minute and can save many points.

Read the exported file

After the contest, export the Cabrillo file and read it in a text editor. Look at the mode column in the first lines, at the places where you changed modes and at the last lines. Search for the mode codes that you did not use: if you worked only CW and SSB, a line with RY or DG is an error. Compare the number of lines per mode with your own records.

The header has its own mode field. The CATEGORY-MODE line states the mode category of your entry: single mode or mixed, according to the rules. Make sure that it agrees with what you operated. The Cabrillo header guide describes the line, and Cabrillo header mistakes lists the typical problems.

Use a log check as a second opinion

Contest Analyzer works with Cabrillo from N1MM Logger+, DXLog and Win-Test and checks every callsign and every zone against official license databases and several independent reference sources, showing only the few QSOs worth a second look. It supports contests with the mode MIXED, as the contests page shows, and each contest has its own period, bands and exchange built in. In the report you can edit calls, zones, time and frequency and download a corrected Cabrillo file. Dupes are listed separately and are not errors. Because the report gives statistics by hour and band, it also helps you see the shape of your operation and spot a block that does not fit.

The check is not a replacement for your own reading of the mode column. Think of it as another view of the log, which can make a pattern visible that you may have overlooked. If something looks odd, compare it with your notes and, if you recorded the contest, with the audio.

An imaginary example

Imagine an operator in a mixed-mode contest who starts on CW, switches to SSB in the afternoon and returns to CW in the evening. During the switch to SSB, the logger fails to read the new mode from the radio because the interface was set to CW only. For the next forty minutes, the QSOs are logged as CW, although they were made on SSB. The operator notices nothing, because the screen shows the frequency and the callsigns, and the mode is displayed in a small field that is easy to miss.

After the contest, the file contains forty SSB QSOs with the mode code for CW. If the contest counts dupes per band and mode, some of them look like dupes of earlier CW QSOs, and the organiser may remove them. If it scores modes differently, the points are wrong. Nobody has made a copying error, and the callsigns are right, but the score is lower than it should be. A look at the mode column at the right moment would have found the problem in the first minute, and a check of the exported file afterwards would have found it before submission. Such errors are easy to fix once seen: you can correct the line in the logger and export the file again. Not seeing them is the real danger.

A checklist for mixed-mode contests

Related reading

The bottom line

The mode field is small but powerful. In a mixed-mode contest it influences dupes, points and multipliers, and it is easy to get wrong when the radio and the logger disagree. Build a habit of checking the mode after each change, read the exported file and use a second view of the log before you submit.

FAQ

What are the mode codes in Cabrillo?

Commonly CW, PH, FM, RY and DG. Check the Cabrillo specification and the contest rules for the codes you should use.

Can a wrong mode make a QSO a dupe?

In contests where the mode counts for dupes, yes. Always read the current rules.

My logger reads the mode from the radio. Is that safe?

It is convenient, but test it for every mode before the contest and keep an eye on the screen.

How can I find mode errors after the contest?

Read the file, search for unexpected codes and compare the counts with your notes.

#Cabrillo#Cabrillo Format#Contest Logging#Dupes#Log Checking
Check your contest log before you submit it.Prüfen. Analysieren. Ihr Contest-Log jedes Jahr verbessern.
Prüfung starten

More from the blog

Alle Artikel →
Ebenfalls von LY4A · kostenlos

Verpassen Sie nie das DX, auf das Sie warten.

LY4A DX Reminder. Geben Sie an, auf welches Rufzeichen Sie warten, auf welchen Bändern und in welcher Betriebsart. Die App beobachtet im Hintergrund fünf DX-Cluster und löst einen echten Alarm aus, sobald dieses Rufzeichen auftaucht — auch wenn Ihr Telefon stummgeschaltet ist.

  • Kostenlos — ohne Werbung, ohne Konto
  • DXScape, DXSummit, DXHeat, PSK Reporter, RBN
  • 160 m bis 70 cm · CW, SSB, FT8, FT4, RTTY
  • iPhone, Android, Windows und Mac

ly4a.com ↗

Vom selben Team

Weitere Tools unseres Teams

Entwickelt von Internet Solutions. Jedes spart Ihnen auf andere Weise Zeit.