Cabrillo Log Hints

Contesters are advised to read their log before submission.
Common errors:
° Make sure the log is in Cabrillo format, not the logger`s native log file. Excel and MS Word are not Cabrillo logs - they are the worse formats for log submission!
° Do not use MS Word to edit a text file - NotePad and WordPad are on all PCs and made to edit text files. If you edit/save a Cabrillo log in MS Word, check the file in NotePad for Word formatting - possibly missing CRLF after each line. Also, be sure to select the format `Space-delimited text file` when you re-save it, and verify the file has the original file extension.
° Your log should not have slashed zeros or diacritic letters (�á é) anywhere in the file.
° Check callsigns for O vs 0 typos.
° Look for obvious typos - W6AA\ or W6AA' or K`1DS - the adjacent key was also hit. In cross-checking, the other station could get a NIL penalty for your mistake. Logging software should have these unused keys locked-out during log entry.
° The log format is Cabrillo specific. For example:
 - The sent callsign is always at column 31.
 - All data is left-justified, except the frequency column, which is right-justified.
 - A single space is used between all fields up to "column" 31. The number of spaces between exchange fields are decided by the logging program, based on the length of the field. Ex: The callsign is spaced for 12 characters + 1.
 - There are no TABs in Cabrillo, it is a space-delimited text file in "column" format.
 - Format is important. Nov SS example: 0001 A 66 EPA. The serial#, precedence, year licensed and section exchange fields must be space-delimited. If you edit your Cabrillo incorrectly, running the fields together will cause a submissions robot error.
 - The modes must be what the sponsor calls out in their rules - and only these modes. Make sure you change modes in the logger when you change modes on the air, otherwise this will cause dupes and cross-checking errors.
° Do not log incomplete QSOs! I see logs with ? or - for characters not copied. This is a no-brainer - ask for a repeat. If still not copied correctly, tell the station NG and do not QSL and do not log the QSO. If you both log a QSO with a callsign error for example, you could get a `unique` penalty, and the other station could get a NIL penalty.
° Check the information to be logged before you enter the QSO into the log. For example: Callsigns without a number - ask for a repeat. Callsigns that are run together with the exchange - separate them.
° Edit the Cabrillo header to follow the contest rules. If the contest is a US State QSO Party, and your QTH is the US or Canada, put your ARRL section (or state) in the LOCATION: or ARRL-SECTION: field. These fields are for valid abbreviations only, not your grid square, not "MICHIGAN", not "ALLEGHENY COUNTY" !
° If the contest rules specify a `time-on` limit, the log must be in chronological order. It should be in chronological order anyway - why do some logging programs write the log in reverse order? If this is a program setting, why is that option available?
° Make sure the log has all the required fields. Missing RST and serial number fields are most common - your log could score 0 points.

Before the contest:
° Verify that the logging program`s setup follows the contest rules.
° Check the UTC time - using the wrong UTC offset can cause invalid QSOs (outside the contest period) or will cause cross-checking errors that can result in NIL. Download and use the free time syncronization software DIMENSION4 to automatically update the PC clock.
° Verify that the logging program`s time field is 4 digits in the 1234 format, not 12:34 - an invalid UTC time for sure. 5 characters could push the other columns to the right by 1 place.
° When operating portable, use a dash or underscore in place of the slash in the logger`s setup screen. However, keep in mind you cannot use macros that send <yourCall> - enter your portable callsign into an F-key memory as text instead. After writing the Cabrillo, change the OPERATOR: field as necessary. Then make sure your callsign uses the slash in the rest of the log.
° Check that your sent exchange follows the rules. If the exchange is QTH specific, verify that what you are sending is correct. Is the exchange that your logging program sends the same as what goes into the sent field of your log? If not, this can cause cross-check errors for the other station.
° Error in logs since 2013: If your QTH exchange per the contest rules is the Province of Ontario, verify you are sending ON or ONT per the rules, not one of the 4 ARRL sections of Ontario.
° Verify the callsign you are sending and what goes into your log - it should be the station`s call if multiop - not the default callsign in the logging program`s setup ini. Logging program macros must send the callsign that goes into your log. Portable station callsigns are a problem! A station signs PA0AAA/P, but PA0AAA goes into his log - cross checking, ouch!
° Verify the QTH abbreviations you use are those listed in the sponsor`s contest rules.
° Check the contest calendar and be aware of other contests that are taking place on the same date. Announcing the contest in your CQ is helpful to all.

A big problem:
° Is the serial number sent by the logger the same number that goes into the log? If not, this can cause cross-check errors for the other station. I see errors in digital mode logs where the received serial number is different by 1 from the serial number in the sending station`s log. This occurs way too frequently to be coincidental. For example: 004 in received log and 003 in the sent log. This may be a program macro setup problem. Or the reverse situation - 003 actually sent but 004 was the current logged QSO number. This can happen if you hit the wrong F-key - that sends <PREVNRS>.

Remember:
° Many contest sponsors do not use a log submission robot that can flag errors, and return an error message to you.
° Work a dupe station again if requested. Leave dupes in your log, otherwise this can cause NIL in cross-checking.
° If your logging program scores the contest incorrectly, the claimed score does not affect your log submission - the sponsor scores your log. Just make sure your log has the correct exchange data in the correct columns.
° Do not just log what the logging software suggests from its look-up files - always enter into your log and QSL what the other station transmits. This is very evident in contests where the zone is exchanged.
° Make sure your Cabrillo has the serial numbers that you logged, not truncated numbers - 4 digit numbers truncated to 3 in the log.
° When using digital mode software, make sure that the exchange inserted into your log is what you QSL, not some decoded jibberish.
° If an exchange is four characters for example - all entries must be 4 characters - not 3, not 5.
° If 4-digit grids are exchanged, they must be in the format LLNN (letter letter number number). 6-digit grids are LLNNLL.
° The Cabrillo log filename should be the call used in the contest (the sent callsign) - callsign.cbr or callsign.log. Change the slash / to an underscore _ or dash -. Ex`s: UA2FFX_1.cbr   VE-F5LEN.log.
° Set your editor so you can see the difference between O(oh) and 0(zero). Do not use slashed zeros (�). Changing O/0 typos and log editing to insure correct format is allowed post contest. Use only a category listed in the contest rules. Don`t make up your own category and don`t assume the logging program `knows` your category - edit the Cabrillo header.
° Know where on your HD the submission files are written. Open the file you are going to submit to make sure it is the right file - sometimes previous year logs are submitted, or even the wrong contest logs are submitted.
° If you don`t care enough to read your log and check it before submission, don`t even bother submitting it. If your log is incorrect, there is a good chance that the other station will be penalized as well in cross-checking.