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.
Call history is implemented in a separate table in each database. This table is called CallHist. The entry window menu options for Call History Lookup are:
Note: Currently, there is no way to export from a contest log to the call history table yet, filling the callhist table has to be done by importing a text file.
The import function expects a text file with on each line the information as
mentioned in the order below.
Order: Callsign, Name, Grid1, Grid2, Section, State, CK, Birthdate
The delimiter between the fields may be a comma, a semicolon, a space or an equal sign. The delimiters may be mixed in the file but not within one line! The callsign is needed, all other fields
are optional. The
equal sign is introduced so a friends.ini file used by many RTTY contest programs
can be used without converting.
A missing CK must be entered as -1, since any check from 00 through 99 is valid
(ARRL Sweepstakes).
Birthdate is expected to be used for the AA contest to compute the other stations
age. This will obviously be a little tricky to deal with.
Be sure to put birthdates in a universal format, e.g. 1980-12-31
Example call history file:
Only name needed for contest |
Grid Square needed | State needed | |
N1MM,Tom | PI4GN,,JO33II,JO33jf, | N1MM,Tom,,,,CT | |
N2AMG;Rick | PA5DD=Uffe=JO22ic= | K3ZO;Fred;;;;MD | |
WW3S=Jamie | PA1T,Timon,JO33jf, |
Or
K1CC,RICH,FN31,FN32,,,-1,1900-01-01
KG1D,LES,,,,,-1,1900-01-01
N1MM,TOM,FN31,,CT,CT,61,1949-10-01
# this is comments (line starts with a #)
W1RM,PETE,,,,,-1,1900-01-01
Tip 1 by Kenny, K2KW
For those of us with limited dB skills, there is a relatively easy way in Excel to get the data into the right format. Start off by parsing out the data from an old log into different columns. (In Excel, there is a Text to Columns conversion, if your data starts off in one line). Once you get the basic data extracted and parsed, insert additional columns for all the fields as required. Then insert a field for every comma you need, resulting in 8 data fields, separated by 7 fields with single commas in them. By now the data should look exactly as you need it, but in 15 different columns. Then in yet another field, use the Excel Concatenate function:"=concatenate(A1, B1, C1, etc)" You will list every column. This function will then concatenate all the data into one long string, and then just copy and paste all the columns (you can do it all at once) with data into an ASCII file. I had just done this at work last week and it works great. Sounds complicated, but it's quite easy.
Tip 2 by Tom, N1MM
In the log window, choose 'Select All' and use 'Copy Generic Print String' to speed up this approach. The data in the clipboard can then be pasted into Excel.
Tip 3 by Thomas, PA1M
Use 'Thucydides' by Carel, PC5M . Check out the chapter 'Third Party Software' for more info.
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 Message Keys to File > CW 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 Message Keys from File > (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.
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:
73, & GL in the contests
Tom Wagner - N1MM
By Tom, N1MM.
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 guarenteed, 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.........
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. |