Before the Contest

Start of the contest season

With the start of the fall it is time to get ready for the big contests. Here are some suggested steps for your station:

All stations

Assisted or multi-op stations

73, Tom - N1MM

Check the contest rules and if the contest program uses them correct

But of course the program should keep up with all the rules for the contests it logs... but there is just one problem, there are so many of them! And you know what?? If there is an obvious bug like that found during the contest it is there for one, and only one, reason. YOU didn't test the software before the contest! (no Tom, not just you, I'm pointing at all the users out there)

Remember, the N1MM logger is free, written by volunteers, tested as much as we can before it gets out to users, but none of the relatively small group of writers and beta testers has time to try out every contest, all the possible scenarios, and all the combinations of them. Look at the list of contests supported, multiply by something like 1.5 for contests that have different rules 'in state' vs 'out of state' (or country, or continent, or whatever), then multiply by at least 4 or 5 for entry classes with unique rules, then multiply by 3 or 4 again for the different types of multiplier lists, points to assign, qso's that do count or don't count in each set of rules, and then multiply by a couple more things... and you get LOTS of combinations. In the software profession the logger would be considered virtually untestable for a single release, let alone for release after release adding new features, changing contest modules to update for the latest rule changes, updating country lists, county lists, list lists, and there isn't enough time in the year for anyone to even begin to test it all.

So, its up to YOU, the users, to test. Yes, YOU. YOU are the ones that know the rules, YOU are the ones that will be depending on it working for a whole weekend... and if you add up all the YOU's out there who are using the software every weekend it adds up to enough man power to do a reasonable job of covering the critical parts of the program.

The key is, if you are planning to operate in a contest a couple weeks from now, lets say, cqww ssb... Load the latest software NOW, create a dummy database, and sit down with your radio, computer, cluster connection, keyers, and whatever else you use, and log a couple dozen contacts as if you were running(fake them, type and hit function keys as fast as you can and see if it responds reasonably quickly)... then log a few more in S&P mode, make sure your messages and macros work as expected, make sure you can record and playback ssb messages on the fly, make sure the multipliers you think should be counted are scored right, log some contacts that shouldn't be multipliers or points and make sure they aren't. grab some spots, make some spots, make sure the spots show up in the right colors for the contest rules. Use the new feature to save your screen layout so you can get it back later. Then create a Cabrillo file and make sure that looks ok... make detailed notes of problems and put in bug reports well in advance. If everyone did that on some evening, or rainy day, or some morning when you wake up and can't get back to sleep, we would stand a chance of catching simple things like multipliers that aren't counted right BEFORE the contest weekend.

So get out there and TEST!

David Robbins K1TTT

Update the Call History Lookup file

In some contests part of the exchange is known if the callsign is known. So it would be easy to have this information shown (or already prefilled) if the callsign is entered. Lookup examples are names (Friends file in RTTY contests), gridsquares for VHF contests, ages in All Asian DX contests etc. In all cases the possibility to use this lookup function means changes in the contest class by the programmer. A lookup is only done when the cursor is in the callsign field in the Entry window and SPACE or TAB is pressed.

Update the Call History file or create a new one if the contest supports this and the exchange could be/is known.
More information about Call History can be found in the chapter 'Advanced Functions'

Importing and exporting message Function keys

The CW messages and SSB wav file messages are not contest-specific, but rather portable between contests.

When you get the message keys set up for a particular contest do the following: File > Export > Export Function Keys to File > CW Function Keys (for example) This saves the message key setup as a Macro file. Name it after the contest. You can recall that set of function keys any time you like by importing them: File > Import > Import FunctionKeys from File > CW Function Keys (for example) > (select file)

This way you can make and reuse different files for all the different contests.  Just import the message keys for the contest de jour.

Getting ready for CQWW (and other contests)

Top contesters have a checklist of things to do prior to a major contest. Please consider adding these logging program related items to your list:

  1. Make a few dozen test contacts in the contest.
    Make several QSOs in 'running' mode and several QSOs in S&P mode. Press the CQ function key to set yourself to 'running' mode. If it does not, make sure the 'Configurer | Function Keys tab' matches your button setup.
  2. If you plan to use any of the following features, make sure they work as you expect:
  3. Get the latest CTY.DAT and install & test it. The About window will tell you the version you are using.
  4. Get the latest MASTER.DTA and put it in your install directory. The Check window at startup will tell you the version you are using.
  5. Prepare your CW function keys, SSB wav files, or CQ/RTTY messages. Test them!
  6. Make sure that RF does not get into your cabling.
  7. Make sure you have selected the correct options in the contest setup dialog. For CQWW your exchange field should contain only your zone.
    Read the contest rules so you know how to setup the contest, Function keys etc.
  8. Run Cabrillo output and check for proper generation.
  9. Sync your time with an Internet time standard, if possible. I use a freeware program called Dimension 4 and resync periodically (every hour?) during the contest.
  10. Review "Key Assignments" in the help. Print it out or print out a keyboard template which can be found on the N1MM website under 'Downloads', select in the 'Download' menu, 'Other Files'.

73, & GL in the contests

Tom Wagner - N1MM

How to record Wav files for the Function keys used in SSB contests.

By Tom, N1MM.

  1. I use Cool Edit 96, but there are later versions.
  2. Record **all** of the messages on one wav file. Make sure you have a quiet room. Record each message at least TWICE. Sound excited!
  3. Leave 5 seconds of empty space at the beginning of the recording.
  4. Record.
  5. Save the recording as "Raw CQ" or some such.
  6. Use Cool's noise reduction feature. Mark the blank part of the wav, and set the noise reduction, then noise reduce the whole wav file.
  7. Save the recording as "Noise reduced CQ".
  8. Perform bass reduction, treble boost or whatever other transformations and save them as you do them.
  9. You can use compression, but I don't recommend it.
  10. Split the wav file into the separate messages, saving the best of the two recorded.

Recording ALL your messages in one recording and afterwards splitting them up using a wav editor will avoid the pops at the start and end of recording, as well as making it more likely that all the messages will be recorded at the same volume level and sound the same.
Don't ask why you need Cool Edit. Just get it.

Here is what is recommend by Uffe, PA5DD

Another nice program is Audacity and this one is freeware. This program can scale the peak amplitude of all the audio files to be the same. In order to set the audio level out of the computer, I recorded 10 seconds of a 800 Hz tone. Scaled the amplitude (peak = mean) and assigned it to F7. I call it cal.wav. I turn off the speech processor, and turn up the computer volume just until full output is reached. Although not guaranteed, the peak amplitude of my audio files should now be in the dynamic range of my transceiver. Afterwards I turn the processor on again.
P.S. Ok then, I admit to sometimes turning the volume just 1 or 2 ticks higher to be on the safe side.........

Audicity anomaly: When making SSB recording in AUDACITY, sampling rate MUST be set to 44100 HZ. Any sample rate less than that causes the splash to be heard.... on the end of every recording.

Place the Wav files you have made in the N1MM Logger\wav directory and call them  cq.wav   n1mm.wav   59.wav   etc. Just what you like! In the program I specify them as:

CQ   wav\cq.wav
N1MM   wav\n1mm.wav
Exch   wav\59.wav

NOTE THERE IS NO LEADING \ before wav !
This notation means to start looking for the directory at the current directory (N1MM Logger or whatever).

When making also all letters and number wav files these have to be placed in the N1MM Logger\letters directory.

Examples:

letters\1.wav
letters\2.wav etc

? = letters\query.wav
/ = letters\stroke.wav

Below some extra information from Mario, S56A, N1YU

NB. When using WAV files turn off Windows sounds in ' Control Panel - Sound' and select: Scheme : No sounds.

Making the Window Focus More Distinctive

By Pete, N4ZR

The standard Windows XP color scheme does not make the active window (among many) distinctive enough for quick recognition during a contest.  This can be particularly an issue in SO2R operation. Fortunately, this can be fixed.  You can do the same thing with Windows 98 as well, just by right-clicking on the desktop and proceeding as outlined.

In Windows XP the specific process is as follows:

You will probably want to fool around for a while before you settle on what you like best.  Once you have done that, back out to the Themes tab under Display Properties. Click the Save As button and name this theme and save it to your settings.

From now on, all you need to do to switch to your N1MM setup is to right-click somewhere on your desktop, select Properties, and then choose your N1MM theme.

Turn of Windows Sounds when using Wav files

Adding a new font to Windows