Rules FAQ

Yes, but the second QSO will be considered a dupe for zero points. However, do not remove dupes from your log because this may cause a NIL penalty for your QSO partner. This is considered unsportsmanlike operating behavior.

This means that your callsign was not found in the other log, i.e., it is Not-in-Log (NIL). The penalty for a NIL is one times the QSO point value for that contact, in addition to losing the QSO points. In other words, the total reduction from the raw score is two times the QSO points.

There is no limit on operating time for any of the categories.

One method is to define the TX5 message as <call grid> and interleave that message with your TX6 CQ message and your TX2 SNR message.

No. A single action, such as Enable TX where the software then selects up to three potential QSO partners to send messages to, is sufficient for multi-streaming. In general, automation can occur within a QSO period, e.g., auto-sequencing through the TX messages based on receiving the appropriate RX messages. But, each QSO must have at least one operator action associated with it to avoid robotic operation which is not permitted. One way to think about it that one operator action is required for each “serial” QSO and for up to 3 “parallel” QSOs. After a set of up to 3 multi-streamed QSOs are underway, any future QSO or set of multi-streamed QSOs requires another operator action.

Yes, you may work other bands and still submit your log as a single band entry. First, please make sure your log includes all QSOs made on all bands. This helps us with the log checking. Second, make sure the Cabrillo file header has your category set for the single band you want to enter. (e.g., CATEGORY-BAND: 20M) Only the QSOs on the single band will be used to compute your score.

Please enter only one log containing ALL QSOs! Each log that you submit will overwrite the previously submitted log.

Only one log file may be submitted per callsign so your must combine separate log files into one log file. One way to do this is to combine the ADIF files into one file using a text editor before converting to the Cabrillo file.

The QSOs do not need to be in chronological order in the log. So you can append QSOs from one log to the end of the other.

Log the grid as ZZ00.

Yes! Please log all contacts that you make even if they are duplicates.

For example... XX9XX works K5ZD but logs it as K5ZB. K5ZD logged XX9XX correctly. Later XX9XX works K5ZD again. This time he logs K5ZD correctly. K5ZD logs the second duplicate QSO and scores it as zero points. For this case, the log checking software assigns K5ZD with a good qso and a dupe (no penalty). XX9XX gets a busted callsign (K5ZB) and a good qso (K5ZD).

No, please do not remove any QSOs from your log! This will cause the other station that worked you to lose credit for the contact.

If you want to remove a QSO for any reason, use a text editor to add "X-" to the beginning of the QSO line in the Cabrillo file. For example:

X-QSO: 7023 DG 2009-08-31 2333 AK1W +02 FN42 XX9XX -03 PM45

The log checking software will not count this QSO for you, but will give credit to the other station.

Yes, but only from your own notes or memory, provided that it reflects what was sent over the air. No corrections, additions, deletions to what was sent over the air is allowed.

Rule IX.9 says "9. Correction of logged callsigns and exchanges after the contest by using any database, recordings, email or other methods of confirming QSOs is not allowed." You must not look up callsigns on the DX Cluster, RBN or DX newsletters after the contest. You may not ask via email or telephone for confirmation that a contact occured.

The Cabrillo log format standard has changed over time. v3 is the preferred format for log submissions. The log robot will accept either v2 or v3 format and will automatically convert them to v3. View more information on log submission requirements here.

An extension may be requested by email to <[email protected]>. The request must include the entry callsign, a valid reason for why the extension is needed, and a date by which the log will be submitted. The request must be submitted before the log deadline. Requests can be submitted before the contest. The maximum extension that can be granted is 10 days. All requests for extension must be acknowledged by the Contest Director to be valid.

Most logging software exports an ADIF file. This can be easily converted to the Cabrillo format file required for this contest. Use the ADIF Converter at ww-digi.com/adif/ to do this conversion and it will interface to the Cabrillo Log Upload webpage that uploads your log to the contest server.

Enter ZZ00 for the received Grid Square. Always log a QSO where any information was exchanged. Otherwise, your QSO partner may be unfairly penalized if the QSO is not in your log. This is considered unsportsmanlike conduct.

Yes. All categories are permitted to use QSO finding (spotting) assistance.

Any entry class may post their scores to a live scoreboard (e.g., cq-contest.net or contestonlinescore.org) and view the live scores.

X-QSO is intended for correction of occasional mistakes that happen during the contest. If the committee decides that X-QSO is being used to avoid the 10 minute rule the log will be subject to possible reclassification or other committee action, as deemed appropriate.

When two or more transmitters are present on the same band, a hardware device MUST be used to prevent more than one signal at any one time. It is not permitted to request or solicit QSOs (e.g., call CQ) on more than one frequency at a time. The second interlocked station on the band should only be calling stations and must change frequencies after each QSO.

If you want to start transmitting on a third band, you must stop transmitting on one of the other bands. There is no exception.

The Multi-Single and Multi-Two categories allow each transmitter to make 8 band changes per hour. Here is an example log for one of the transmitters:

QSO: 14082 DG 2012-10-27 0052 K5ZD      -02 FN42 ED8W      +01 IL18 1
QSO: 14082 DG 2012-10-27 0057 K5ZD      -11 FN42 RW1CW     -06 KO59 1
QSO:  7084 DG 2012-10-27 0103 K5ZD      -07 FN42 SV1ELI    +00 KM17 1
QSO:  7086 DG 2012-10-27 0108 K5ZD      +03 FN42 LY7A      +01 KO24 1

The band change is counted in the 0100z hour because it happened at 0103.

Yes, it is permitted for an operator to work from home with his own callsign and then also from a multi-operator station.

No. Only the score of your stated entry category will be applied to the club score.

Single operator entries must indicate only ONE club that will receive their score.

Multi-operator entries may split their score among the clubs of the operators. The split will be by a percentage of the number of club members participating in the operation. The split is defined on the CLUB: line of the log file. Please show the split and then the club name. It is not required that all splits add up to 100%. Here are some examples of club splits:

CLUB: 3/8 WILLAMETTE VALLEY, 1/8 WESTERN WASHINGTON DX CLUB, 4/8 SOUTHERN CALIFORNIA CONTEST CLUB

CLUB: 1/7 NORTHERN CALIFORNIA CONTEST CLUB, 4/7 FRANKFORD RADIO CLUB

Please spell out all club names according to the list of names at http://www.cqww.com/clubnames.htm.

Entering a split will cause the log submission robot to return a warning message that the club name does not match any on the list. You may ignore this message.

OR = Both. The club area is defined as the country where the club is located plus the area within a 400 km radius circle around the club center. This allows a club that is on the border of two countries to have members outside of the club location country.

Each club may select any location to be the center. Once this place is chosen, it must be the same for both modes of the contest. If there is a question, the CQWW Committee will ask the club officers to specify the location.

Yes. Club members living within the club area that go on DXpeditions to other countries can count their score for the club. They must specify the club name in the log.