Basic Functions

When using the program there are some standard routines like changing frequency, band and mode. Next to reading this chapter also read the Key Assignments, Setting up the Program, Entry Window and the Quick Tour to have basic program information. There are also some features which will be explained in this chapter like 'Running' mode, Search and Pounce' mode and 'Enter Sends message' mode etc. Operating tips and tricks can be found in the Tips and Tricks chapter.

1. Help

Almost every window has a Help function. All Help currently is on-line, so you will need an Internet connection. To get to the Help, right click on a window and select 'Help', or click on the Help button. The Entry window help can be accessed from the Help menu at the top, or by pressing Alt+H. Also note that the Key Assignments help can be accessed directly from the Help menu on the Entry Window. If you do not have an Internet connection, the best solution is to download the complete documentation in PDF format here.

Searching through the Help can be done on the web site, using its built-in search functions, or by using the Find function in Adobe Reader and the PDF version of the documentation. If you use the web site, it's worthwhile to read this page. The Advanced Search function is very powerful, while the basic search is handy for single word and acronym searches.

2. Understanding How N1MM Logger Uses Databases

N1MM Logger uses databases in Microsoft Access format to store logs and all other data used during operation. Let's say you just installed the program. You open the default database (ham.mdb), and create your first contest (CQWWCW, for example). When you "OK" out of the Contest Setup dialog, you'll notice that a number of things seem to have been set up for you. This is because these things are stored in the database.

In addition to your QSOs, there are a number of tables in the database that contain data that may, and probably will vary from one contest to the next. These include such things as multiplier lists for particular contests, function key definitions for CW, SSB and digital modes, the contents of the last wl_cty.dat file that you loaded, and a Call History table (if one has been loaded).

Why should you care? For several reasons:

  • If you modify the function key definitions while operating, that modification applies only to the current database. Each database only has space for one set of function keys for each mode, one Call history file, one set of Telnet buttons, and a pointer to one master.dta file in the program directory.
  • When you switch to another database, those definitions (and in particular, any changes you made) are left behind. That's why the program provides for exporting function key definitions (among other things) to text files, which can then be loaded into the database as needed. You can label these text files in a contest-specific way so that it will be easy to find when you set up for the next time.
  • Master.dta files may change from contest to contest, too. You don't have to load them into the database, but you do have to make sure that you have pointed to the appropriate file for each contest. For example, the master file MASUSVE.DTA, which contains only US and VE callsigns, would be useless to a US station in the ARRL DX Contest or CQWW. That is one reason for the Associated Files tab in the Contest Setup dialog - so that when you switch contests within the same database, the files you need (or pointers to them) are automatically loaded.
  • The same thing applies to Call History files. One common error that Call History users often make is to forget to load the appropriate file into the database (you can only have one at a time loaded). They set up a contest and find they are getting the wrong information about stations they work.

The takeaway is this - when you change contests within a database, or change databases, your function keys, master.dta file, Call History file, and Telnet buttons will still be those from the last contest you worked using that database, UNLESS you have identified the appropriate files on the Associated Files tab while setting up the new contest.

3. Going Through the Entry Window Fields

Space is preferred, rather than the Tab key, for advancing through fields in the Entry window. Space avoids fields (like RST) that don't normally need to be changed and prefills other fields. Spacebar operation is described in detail in Key Assignments. You can use the Tab and Shift+Tab keys to move the cursor forward or backward to rarely changed fields such as RST. There are a couple of contest types where the exchange field can contain a space (the "Name" and "Comment" fields in the general DX contest, or the Sweepstakes exchange, for example), and in these cases once the cursor has moved into one of these fields, you must use the Tab or Shift+Tab key to move to another field, but in 99% of cases the Space key will do the job.

4. Resizing Windows

Logger's windows can be located where ever the user chooses and most can be made any size. The Bandmap has a minimum width, and the Entry windows have a minimum size below which some data items are not displayed. The new dimensions and positions of the windows are stored when the program is closed. Closing the Entry window will close the application.

5. Selecting a New Contest

To select a new contest go to the Contest Setup dialog ( >File >New Log in Database ). On the upper left of the screen a contest can be selected by clicking on it. Fill in the details for your specific situation. Which contests are supported can be found in the chapter Supported Contests. Check the contest's website for the latest rules and check the contest setup information in the Contest Setup Instructions chapter.

6. Selecting an Existing Contest "Instance"

You can make as many "instances" of a contest as you want, in any given database. To get back to an "instance" that you previously created, go to the Contest Setup Dialog through Open Log in Database on the Entry Window's File menu. Scroll to find the one you want and double click on the contest name to open it, or single click to modify any of the setup variables, and then click "OK."

7. Deleting a Contest "Instance"

Go to the Contest Setup dialog ( >File >Open Log in Database ) and highlight the contest in the Contest pane. Then press the Delete key.

8. Downloading a Country File and Loading it into Database

When a new Country File is made available (thanks to AD1C at this site), download the file to your program directory using the "Download latest country file" option on the Tools Menu. Once you have done so, you will be reminded each time you open the program that the file is newer than the country information that is loaded into the current database. To load the information from the new file into the database, just select "Import country list from downloaded file" on the Tools menu.

When downloading, be sure to choose the file named wl_cty.dat because it has extra country info that is useful.

9. Downloading Master.scp files

The Super Check Partial file (otherwise known as Master.scp) is commonly used by contest logging programs. It contains the callsigns of a huge number of stations active in contests, and is used to help the operator copy calls under adverse conditions. In N1MM Logger, possible callsigns are displayed in the Check window.

This file is typically updated before each major contest, and may be downloaded from this site. Assuming you are connected to the Internet, Use the Download and Install Latest Check Partial file option on the Tools menu. If you need to do it manually (on another computer, for example), Do so and copy the file to C:\Users\login\My Documents\SupportFiles.

10. Changing Frequency

Changing frequency can be done in many ways. Here is a short list with some alternatives

  • Just turn the dial or change band on your radio, the program will follow if the radio is connected
  • Enter a frequency in kHz into the Entry window < Callsign > field. For example, 14205 will jump to 14205 kHz. If the Configurer >Mode Control >Settings tab has been set to follow the band plan, the mode will be changed when needed following the bandmap rules
  • If the frequency you enter has 3 digits or fewer, it will be treated as an offset from the beginning of the band. For example, if the current frequency is 14200 kHz and you enter 76, the frequency will change to 14076 kHz
  • Enter an offset in kHz preceded by a + or - sign into the Entry window < Callsign > field. For example, if current frequency = 14200 and you enter +3, the frequency will jump to 14203 kHz
  • Placing a/ in front of the frequency or offset will set the second VFO (B), e.g. /7040 will set VFO B to 7040 kHz .
  • Click on a spot in one of the bandmap windows
  • Click on a spot in the Packet/Telnet window
  • In the Log window, right click and select 'Jump to this frequency' to go to the logged QRG
  • Click on one of the callsigns in the list of multipliers below the 'Available Mult's and Qs' window
  • Push one of the buttons in the 'Available Mult's and Qs' window to change band
  • Enter an offset in the Entry window < Callsign > field and press Ctrl+Enter to go 'split'. See the Split Operation section of the manual
  • Use one of the many keys below to change frequency, band or vfo/radio. Go look in the Key Assignments section to read what they all do!

Ctrl+Alt+Down ArrowCtrl+Shift+Page Down Ctrl+Down Arrow Ctrl+Alt+Q Ctrl+Left Alt+Q
Ctrl+Alt+Up Arrow Ctrl+Shift+Page Up Ctrl+Page Up Page Up Ctrl+Right Alt+F8
Ctrl+Shift+Up Arrow Ctrl+Shift+Down Arrow Ctrl+Page Down Page Dn Alt+F10 Alt+F11
Ctrl+Shift+Alt+Up Arrow Ctrl+Shift+Alt+Down Arrow Ctrl+Up Arrow Shift+Alt+Q Alt+F11 Up Arrow
  • Need any more?

When no radio is attached and PgUp/PgDn is pressed nothing will happen. I.e. if the frequency is inaccurate, don't allow the operator to move out of band by inadvertently pressing PgUp/PgDn.

When a frequency is chosen outside an amateur band a warning dialog will be shown when trying to enter information. This could happen making a typo when entering the frequency or when no radio is connected, so a kind of "radio is not working" message.


11. Changing Band

Below some of the possibilities how to change band.

  • Change the band on your radio, the program will follow if connected
  • Ctrl+PgUp - Go up one band. WARC bands are skipped when logging a contest
  • Ctrl+PgDn - Go down one band. WARC bands are skipped when logging a contest
  • Enter a frequency in the Entry window 'callsign' field on another band. For example: 14205 will jump to 14205 kHz
  • Push one of the band buttons in the 'Available Mult's and Qs' window to change band
  • Click on one of the callsigns in the list of multipliers below the 'Available Mult's and Qs' window on another band
  • Click on a spot in the Packet/Telnet window on another band

12. Changing Mode

  • Change the mode on your radio, the program will follow if the radio is connected. Because digital modes may also be sent with the radio in USB or LSB, switching the radio to USB or LSB with the Digital Interface window open can be ambiguous. If you are using digital modes you need to go to the Configurer's Mode Control tab and set the "Mode recorded in log" depending on the contest and the mode(s) you wish to use
  • Change the mode in the top part of the Bandmap windows by clicking on the mode name at the top right. This will cycle through the modes available on the radio
  • Change the mode by typing CW, LSB, USB, RTTY, AM, FM or PSK in the 'Entry window' callsign field
    • Many transceivers do not have PSK or RTTY as a selectable mode on the radio. To control the radio's mode correctly when one of these modes is selected, you have to go to the Configurer's Mode Control tab and set the "Mode sent to radio" appropriately for your radio

 Setting Mode Control

How the mode will be controlled on the radio and how contacts will be logged needs to be set in Configurer >Mode Control

13. Changing Operator

  • Ctrl+O changes the callsign of the operator. If you are multi-user, you will be prompted for the operator at startup. The default is the callsign in the station information dialog. A callsign is required to be entered
  • Entering "OPON" in the callsign field will also prompt for an operator callsign

14. Setting CW Speed


Setting CW speed can be done using the Entry window speed control (only shown when CW is selected) for each radio or VFO. Use PgUP and PgDn or click on the arrows beside the speed box to change CW speed.

15. Running Mode

Running mode means that you are calling CQ and stations are coming back to you. The frequency you are on is 'fixed' and you are not searching for stations, you are letting them search for you. The program marks this frequency with the text CQ-frequency in the Bandmap window and the 'Running' indicator is marked on the 'Entry Window'. A part of this feature is that 'Running' mode has its own set of Function keys. They will be automatically called up by the F1 to F12 keys. There is also a set of function keys for Search and Pounce' mode, these function keys will swap to Shift+F1 until Shift+F12 so they are still available.

The "Running" switch is automatically marked when:

  • The operator clicks on CQ-frequency in the Bandmap window
  • You were previously running on that band but you are now searching and pouncing, and the frequency of the radio is moved within the tuning range of your CQ-frequency. This feature can be disabled by checking the Config > Do not run on CQ frequency menu item in the Entry window
  • Pressing the CQ-key, even when you are in S&P mode (normally this is F1, but it can be changed using the Configurer's Function keys tab)

When moving away from the 'Running' frequency the program will place you automatically in Search and Pounce mode. The indicator on the 'Entry Window' will be unmarked and the Function keys will be swapped for F1 to F12 in the 'Search and Pounce' keys.

Going back to the 'Running' frequency will automatically select 'Running' mode unless the "Do not run on CQ frequency" menu item has been selected. Clicking on 'CQ-frequency' in the bandmap will also place the program in 'Running' mode. An exception is when working split i.e. transmit on one VFO and receive on the other. Moving around will not change 'Running' mode into Search and Pounce mode.

There is only one CQ-Frequency per band. In SO2R and SO2V, it is possible for the two VFOs to be in in different 'Running' and 'Search & Pounce' modes.

Often used keys in Running mode (CW)

  • Insert or ; - Sends His Call key followed by the Exchange key
  • ' - Sends TU message and enter in log
  • F4 - Sends my call

16. Search and Pounce Mode (S&P)

'Search and Pounce' mode (S&P) is the opposite of 'Running' mode. The program is always in one or in the other. S&P mode means searching for stations on the bands and not calling CQ. The frequency used is not 'fixed'. The 'Running' indicator is not marked on the 'Entry Window'. The function keys under F1 to F12 are the keys programmed for Search and Pounce' mode; the 'Running' mode function keys are swapped to Shift+F1 to Shift+F12 so they are still available.

 Function Keys Change for Run vs S&P

If "Running" is checked, the Run messages are shown on the Function Keys. Otherwise, the Search and Pounce messages are shown on the Function Keys.

When pressing Shift, the labels will change (when made different) and the text from the "Running" keys become the text from the "Search & Pounce" keys and vice versa. SHIFT REVERSES THE MEANING OF THE ABOVE RULE.

When in Search and Pounce mode, to call CQ, the CQ-key as configured is used (normally F1). Pressing F1 will send the S&P F1 message and place the program in Run mode. From that point on F1 will send the Running mode F1 message. Normally, you would program your CQ message into the Running mode F1, and either a CQ message or a QRL? message into the S&P mode F1.

There are two options in the Config menu, one called "QSYing wipes the call & spots QSO in bandmap (S&P)" and the other called "Show non-workable spots". If you use both of these options (recommended), when entering a call in the S&P mode and the call is a dupe, changing frequency (QSY) will automatically enter the dupe callsign into the band map and clear the Entry Window. This lets you know that the frequency is being held by a dupe station so you can skip past it the next time you tune up or down the band.


When a frequency is busy it can be marked with Mark (Alt+M). This could be used when the station on that frequency is not in the contest, may not be worked in the contest or seldom says his callsign to have the frequency marked in the bandmap. Press Alt+M, and move on. That frequency is busy, so you won't want to stop there again.

16.1. How to check if you are in Running mode or in S&P mode?

* Running checkbox checked/unchecked.
* Textboxes are white in running, yellow in S&P and blue in quickedit.
* The green ball shows "Ru" for running, "SP" for S&P.
* You can put different labels on the textboxes for Running & S&P.
* "CQ-Frequency" will show on the callframe if you are Running.
* "CQ-Frequency" appears next to the frequency arrow on the bandmap when going into Running mode.

Another possibilitiy is to is give F1 Running and F1 S&P different names. For example, in the F1 title put the caption "F1 - RUN", and in the F1 for S&P (F13..) put the caption "F1 - S/P". This way the first macro location will tell which set of macros are enabled. Because F1 is always the CQ key (when defined) there is no need for CQ in the title to make that clear.

17. CQ Key

The program uses the CQ Key as defined under the Configurer's Function Key tab to initiate a Run. Normally this is F1. This means that when F1 is pushed it will send the F1 message (either Run F1 or S&P F1, depending on the mode the program is in currently), and then it will place the program into Run mode. This happens both when in Run and in S&P mode. Pressing the CQ key always switches the program to Run mode.

If you wish to use F1 in S&P mode to call a station while staying in S&P (so the content of the S&P F1 key holds your own callsign), then use the {S&P} macro in this function key to stay in S&P mode. Conversely, if you wish to use a different key (not the CQ Key) in the S&P set to switch to Run mode, you can put a {RUN} macro into that key.

18. Set up the Sent exchange message(s)

Every contest has it's own specific exchange. The sent exchange could be fixed (CQWW - zone), a serial number (001 etc.) a combination and sometimes very exotic.
What to set up in the 'Sent exchange' can be found in the manual in the chapter Setup Contests. Sometimes some creativity is needed to get it all working and more than one solution is often possible. For some contest a special sent exchange macro has been added (like TIME2 for some digital contests).

Below an example how to set up a serial number exchange followed by a fixed exchange (in the same exchange). Example 599 023 40 (serial number 023 and zone 40).

There's more than one way to do this. In your exchange message (usually F2), you can use 599 {EXCH}, which will send what you have entered into the "Sent exchange" box (001 will be converted into a serial number and the rest will be sent literally), OR you can instead program F2 to include the individual elements of the exchange, e.g. 599 # # 04 (e.g. if you wanted to send the serial number twice and the zone only once).

Some things to watch for:

1. The {EXCH} macro does not include the 599, so you need to program that into your exchange message(s). The "Sent exchange" box is used to generate the Cabrillo file regardless of whether you use the {EXCH} macro. Therefore you can't put the 599 in the "Sent exchange" box because that will screw up your Cabrillo file. In stead of hard coding 599 in the exchange message(s) also the macro {SENTRST} or {SENTRSTCUT} could be used.

2. If you like to send a slightly different message when S&Ping than when you are running, then you will need to program the Run F2 (2nd message in the list) and the S&P F2 (14th message in the list) with separate messages. For example, you might program the Run F2 with: {TX} 599 # # 04 {RX} and the S&P F2 with: {TX}{ENTER} ! TU 599 # # # 04 {RX}
Note that in Run mode, the exchange is actually sent as F5 and F2 in succession; F5 normally contains the other station's call sign (!) and F2 normally contains just the exchange. In S&P mode, the exchange is sent only as F2, so if you want your S&P exchange to include the other station's call sign (some people do, some don't) you have to include a ! in the S&P message.

3. If you want to always send three-digit serial numbers, go to >Config >Configure Port, Telnet Address, Other >Function Keys and check the box "Send leading zeros in serial numbers (e.g. TT7)"

19. Function Key Conventions

There is a function key "convention" used by N1MM logger and most other logging programs. That is: F1=CQ, F2=exchange, F3=TU/QSL/QRZ, F4=your call and F5=his call. ESM is built around this convention.
If you are already using ESM on CW it probably is wise to stay with the same keystroke pattern when you are on SSB. For example:

ESM mode: S&P - CW or SSB ESM mode: Run - CW or SSB
1. <enter> sends F4, your call 1. <enter> sends F1, "CQ"
2. <enter> sends F2, your exchange and logs the QSO 2. type call, <enter> sends F5(his call)+F2(exchange)
*NOTE* - for SSB, put a single blank space in the F5 message - speak the callsign instead - because of the blank, N1MM will skip F5 and send the F2 message
3. type his exchange, <enter> sends F3 (QSL/QRZ/TU) and logs QSO 3. type his exchange, <enter> sends F3 (QSL/QRZ/TU) and logs QSO

"...This whole business of hitting F1 automatically (and unwantedly) putting you in Run mode seems extremely awkward..." - When you understand that F1 is almost universally the "CQ" key in contest logging programs, it becomes very logical. And by definition, when you are "CQing" you are "Running". In other words, if you don't want to be in the "Run" mode, don't call "CQ" (don't hit F1!)
"...is it possible to have DIFFERENT macros in CW? There I do need "agn" and "hiscall" whereas in phone I don't..."

Macros are MODE-specific, not CONTEST-specific. So, yes, you must have different macros on CW and SSB. However, just because you might use 8 or 9 F-keys on CW doesn't mean you have to use 8 or 9 on SSB. Use only what you need for that particular mode (and contest).

73, Ted W4NZ

20. Set Up N1MM to Record Voice Messages (recording on the fly)

The usual way is to route your microphone through the sound card to the radio. Most sound cards support this, as well as a selectable 20 dB pre-amp for Heil and similar mikes.
To set up the program to record and playback voice recordings do the step below:

  1. Plug your microphone into the sound card mic input
  2. Plug your headset into the sound card speaker output
  3. Select default devices on the Configurer Audio setup Tab
  4. Open the windows volume control on the playback controls, set mic audio so you can hear yourself talking through the sound card.
  5. Change the windows volume control to select the recording controls.
    1. Select the microphone as the recording source.
  6. In N1MM logger make sure you are set for SSB, and in Run mode, and have a file name in the F1 key definition
  7. Press Ctrl+Shift+F1, immediately say something, like a short CQ, then immediately press Ctrl+Shift+F1 again. The bottom status line of the entry window should have said 'recording started' then 'recording saved'
  8. Press F1 and the recording should play back in your headset
  9. Adjust audio level on the volume control so when you record it has the same volume as the mic audio when you aren't recording

20.1. Playing WAV Files

The program can play wav files in SSB for giving CQ, sending default reports etc. For this to work wav files have to be made with the text to send. These wav files could be placed anywere on your disk but easy would be to use the wav\ directory under the program directory. To call a wav file edit the SSB function keys as in the examples below. It is also possible to send a callsign by sending it's letters and numbers. NB. The full file path is needed before the wav file.

Use the SSB function keys to send wav files. For example:

  • Play CQ: C:\Program Files\N1MM logger\wav\cq.wav
  • Play default exchange: C:\Program Files\N1MM logger\wav\5905.wav
  • Play the callsign entered in the callsign entry field will be send by the soundcard: !
    • This example uses the macro: ! (Send his call)
  • Play the serial number to sent from Entry window by the soundcard: #
  • Don't play call from station in callsign field: Use a single space (mostly used in F5)
  • Possible are strings like: ##!C:\Program Files\N1MM logger\wav\{operator}\thanks.wav
    • With or without leading zeros specified
    • Only one wav file can be played per string and only at the end of the string

Some examples using the macro {OPERATOR}, let each operator have his own wav files. You can specify wav files like: wav\{OPERATOR}\cq.wav As you change operators in a multi operator contest, the wav files will change as well. You will have to name them consistently. Note that wav directory syntax indicates a subdirectory under the Install directory. You can also fully qualify, like: "C:\wavfiles\cq.wav". {OPERATOR} is a string substitution only implemented for SSB buttons.

  • Play CQ with operators voice: C:\Program Files\N1MM logger\wav\{OPERATOR}\cq.wav
  • Play call with operators voice: {OPERATOR}\! (The wave file should be put it in the directory set in the Files tab for the letters directory in the Configurer)
  • Play default exchange with operators voice: C:\Program Files\N1MM logger\wav\{OPERATOR}\5905.wav

It is possible to play more .wav files right after the other by separating the wav files with a comma.
For example: C:\Program Files\N1MM logger\wav\{operator}\blank.wav,C:\Program Files\N1MM logger\wav\{operator}\number.wav#

More examples can be found in the Macros chapter under {OPERATOR} macro examples and in the Sweepstakes contest setup.

For those with problems with wav files playing from the Function keys... Make sure that under the tab 'Contest' in the >File >Open Log in Database >Mode Category has been set to SSB (or Mixed) and not set to CW. Check out the Audio tab in the Configurer.
When in split please check out the @ macro (which will voice the receive frequency).

20.2. Recording WAV Files

The first thing to try is to plug the microphone (mic) directly into the sound card. Then open the sound playback control panel, make sure the mic channel is displayed and see if you can get the mic to come out the speakers. Once you do that then plug the mic into the rigblaster and the rigblaster into the mic input on the sound card and make sure it still comes out. Then go from the sound card to the rigblaster and make sure you can hear it in the speakers connected to the rigblaster, then go from the rigblaster to the mic on the radio. That all verifies the audio paths. Note that none of this uses the logger yet.

Now change the volume control to show the recording controls. Make sure the mic input is displayed and select it as the recording source. Open the windows 'sound recorder'. Yes, I know it is a dumb program, but its main advantage is that it is simple. Try to record using the sound recorder and then play it back, the trace should show if audio is getting into the recording.

Now you are ready to try the logger. Watch the status line on the bottom of the entry window when pressing Ctrl+Shift+Fx, make sure it says that recording is started and then that the file is saved. Pressing the same keys again (Ctrl+Shift+Fx) to stop recording. Note the confirmation start/saved messages on the status line at the bottom of the Call Entry window.

If the above steps verified the audio paths then the only thing left is to make sure the PTT keys the radio when you send the file. Note, that you can key manually or turn on the VOX just to make sure that the audio is getting to the rig even if the PTT doesn't work.

N1MM logger only supports standard PCM format files. Some editors use ADPCM instead and you have to convert them to standard PCM to have them played.
More info on recording in the chapter Before the contest.

 Use N1MM Logger to Record Your WAV Files

Record with N1MM logger because it will put the file in the same place it expects to play them from, and it records only with the formats that it can also play back.

20.3. Soundcard Control in Configurer

The soundcard has to be set up when playing wav files. This is done in >Config >Configure Port, Telnet Address, Other >Audio tab. Check out the settings for it in the Configurer chapter.

 Common Soundcard Problems

The most common problem occurs when no sound is heard when playing wav files. Check for a non-existent wav file and the correct path in the program. Always check the wav file in a media player so see if it can be heard from the speakers!

When play SSB wav files, the play volume can be adjusted by the Windows play control sliders.

21. Quick Edit

Do you ever log a contact with a mistake in the callsign? Want to bring it back, so you can change it? You can do it with "Edit last contact (Ctrl+Y)", but that dialog is complicated and not the right tool for the heat of a contest.

There is an alternative called "Quick Edit" (Ctrl+Q). Quick edit will return the last entered qso to the entry window to allow you to change it. Pressing enter will log the changes, ESC will abandon them. The Entry window text boxes change to blue to let you know you are in quick edit.

Was the mistake three QSOs ago? Then just press Ctrl+Q three times to get to it. The same rules about saving/abandoning apply here as well.
{REMARKSBOX(type="tip" title="Quick Edit 'Feature"")}There is no check to ensure that the Quick Edit entered contents are valid like is done when a QSO is entered normally. So check thoroughly what you type.{REMARKSBOX}

22. Meaning of Colors

The meaning of the colors is where possible consistent across all windows. The table below will give the meaning per window.


23. Multipliers and QSOs

The program shows at many place if a callsign is a multiplier, a qso or a dupe. Please study the table with the meaning of colors above.

  • The windows
    • Entry Window
      • Callsign in callsign field : the color of the entered call will tell Qso, Dupe or Multiplier(s)
      • Callsign on the call-frame: the color of the entered call will tell Qso, Dupe or Multiplier(s)
    • Available Mults and Qs window - the button colors will tell Qso, Dupe or Multiplier(s)
    • Check window - the callsign colors will tell Qso or Dupe status
      • Mul: - multiplier on this band
      • Q: - qso on this band
        • Example: Mul: 15 20 Q: 160 80 40 10 - multiplier on 15 and 20 meter and a qso on the other bands
    • Bandmap - the callsign colors will tell Qso, Dupe or Multiplier(s)
  • The colors
    • Blue: QSO
    • Red: Single Multiplier Example: CQWW - qso is either zone or country multiplier (one multiplier)
    • Green: Double or better Multiplier Example: CQWW - qso is a zone and a country multiplier (two multipliers)
    • Gray: Dupe

24. Connecting to a Telnet Cluster

  • Select the tab: Telnet in the packet window.
  • Select a telnet cluster from the list in the upper right corner
    • This list can be changed in Configurer at >Config >Configure Ports, Telnet Address, Other >Hardware tab, Select < Edit > next to Telnet Cluster
  • Click the button marked with your callsign, on the far lower right, or type your callsign in the left field at the top of the telnet tab. Do not click the CONN button, that's solely for RF packet

25. How to Save the Log

Well, there isn't a 'save' function because it is not necessary. Every change you make to the database is stored 'on the fly', hence the absence of a 'save log' function. The ham.mdb file (default name) on your hard disk is the database where every contest is stored, along with lots of other information used by the program. Also there is no need to make a new file for each contest. Each new contest is stored in one and the same file. Just go to >File >New Log in Database and pick one out of the list, and you're all set to go. After a couple of years, there are dozens of contests in the database, for a total of a couple of thousand QSOs.

Now, you can make new databases, as many as you want. You can have separate databases for separate calls, separate contests etc. Most users however, only need 1 database. You can copy it to backup etc. Just be sure what you're doing when messing with files...

26. Function Key Macros

You can't skip function key numbers. It is the position of the macro, not the number you identify it with.

The first 12 macros are RUN macros. If you then only fill in 7 S&P macros then 8 thru 12 will be the same macros as the ones you filled in for RUN. So in your example if you set up your {WIPE} macro for F11 in RUN and your S&P F11 was blank then the {WIPE} F11 key would work in both RUN and S&P.

If you want to fill in a blank macro enter the function key comma and a space. You have to put the space as you cannot create a blank macro.

If you want to go from S&P to RUN is a single keystroke then set the first S&P macro to CQ (without F1 in the description) and put the
command QRL? in the macro (Pete's trick). CQ,QRL? So hitting F1 would send QRL? and put you in RUN and start your auto CQ if turned on.

27. Save and Restore Window Positions

Save and Restore window positions is under >Tools >Save Window Positions' and >Tools >Restore Window Positions

For example:
New operator PA1M: Hit Ctrl+O and enter: PA1M and after this he presses 'Save Window Positions' in the Tools menu. The window positions for PA1M are now saved.
Next operator comes in and does the same for his call.
PA1M is again the operator and wants his window positions back: PA1M does Ctrl+O and enters: PA1M and after that selects 'Restore Window Positions'. The window positions will immediately change to the saved positions. PA1M has his window positions back!

 Substituting Mode for Callsign

Instead of inserting your callsign, enter the mode - RTTY, CW, or SSB. This will save / restore window positions based on your preferences for each mode. This obviously won't work in a Multi-op environment but very usable in the single operator multi mode shack.

28. Editing Lookup Tables

Lookup tables are used widely throughout the program. Example tables are the function keys, telnet stations, exchange abbreviations etc. These tables can be updated by the user and mostly lines can be added at the bottom of the list or deleted where needed.

  • To Delete a row, click on the row "handle" - the gray arrowhead - the 'pensil' will move to it and the row will be selected, press Delete
  • To Insert/Add a row, click on the icon with the 'star', a new row will be added. A row can only be added if all columns are filled
    • The column values will automatically be assigned a space so directly adding a new row is possible
  • To edit an entry select the field to update and enter the new information.

29. Backup and Restore

Information used by the program is partly stored in the database, partly in ini files and in some additional subdirectories. Examples are the WAV files (for the function keys) but also in the Letters directory. So when making a backup not only backup the MDB files but also some text files / or sub-directories. The best solution is to backup and restore the whole N1MM logger subdirectory. Backup/restore proposal 2 is a partial backup/restore.

29.1. Method 1: Full backup/restore on same computer - backup and restore the whole N1MM logger subdirectory

  • Backup the whole N1MM logger subdirectory
  • Restore the data is more or less the other way around. Restore the whole N1MM logger subdirectory

29.2. Method 2: Partial backup/restore on same computer - make a partial backup and restore.

Storing all these files (exported text files, wav files etc) and all databases (mdb files) on a diskette, CD/RW or a USB thumb drive is cheap insurance in case of a computer crash.

  • Backup all database (*.mdb) files
    • In the database files are all contests with QSOs but also the function keys content, Station information etc. Compress the database to get them small
    • N1MM Logger.ini
      • Windows Settings, radio settings, port settings, RTTY settings etc. i.e. everything in Configurer but also last contest used are are stored in the N1MM Logger.ini file
    • Wav files
      • Which can be used by the program (SSB mode). They are in the WAV directory (for the function keys) and and in the Letters directory (sending callsigns etc)
      • Recorded QSOs are stored in subdirectories under the N1MM logger program directory (and can become very big)
    • More?

* Restoring on the same computer - Restoring the data is more or less the other way around.
o Restore All database (*.mdb) files
+ Restore the database file(s) back in the program directory (which is the default place but not necessary).
o N1MM Logger.ini
+ Copy the saved file in the Program directory.
o Wav files
+ Create the directories WAV and Letters directory and other directories needed.
+ Copy the wav files in them.
o More?

 Backup and Restore is not a Copy Function

Backup / Restore will not move the program to a new computer. You must always start with a Full Install on a new or different computer

29.3. Installing on a Different Computer

With a new / different computer you first have to perform a Full Install to get all dll , ocx files etc. copied and registered. After that you may overwrite/add all *.mdb files, settings etc. in the N1MM logger program directory by copying and importing settings. See the restore procedure above.

You have to watch out if the settings like serial ports, directory structure, screen resolution etc. are different on the second computer. This could/will give trouble.

Copy, zip, cd/rw etc.

Compressing the database files for backup/restore with a program like WinZip really helps, these databases (but also Word files, Excel files etc.) compress a lot, mostly down to 10-25 percent of it's original size. This means that a 4 MB database fits easily on a diskette.

The database can be also compressed with File/Copy and compact database. This is not a zip compression. It recovers space from deleted rows. Most database engines do not recover deleted rows until a reorganization is done. They just mark them deleted. This is not the same compression as mentioned above when using zip compression. When doing a compact database the database can still be used afterwards by the program. Using zip compression is only for backup/restore purposes.

It is wise to make a regular backup of the whole N1MM logger subdirectory including all subdirectories to a CD recordable. Copying it to another hard disk (in the same computer but better on another computer when you have a network) is also a good idea.

30. Basic Functions for RTTY

Here are 4 RTTY Operating tips from Rick, N2AMG

  1. Use your mouse to grab everything just click on the call sign and it will get passed on to the entry window and click on the exchange it will get sent to the exchange field. Or use the Insert key to grab a call from the grab window and send your call that saves time also

  1. When you click on a callsign do you still need to press the space bar to advance things? You don't! Go to >Window >Digital Interface, then in the digital screen select >Setup >Settings >Send space after callsign click. Turn that setting on and you will be all set. Also select >Setup >'Rt click= Return NOT Menu'

  1. Try turning on >Setup >Rt click= Return NOT Menu. What this does is makes the right click of the mouse button while the mouse pointer is in the RX window act like the ENTER key and will step thru the ESM keys without hitting the keyboard. Your hand never leaves the mouse for the whole Q

  1. Hover mode: Let's you grab the callsign just by pointing your mouse on the callsign, no click... this way. It's faster then to click right to reply. Hover mode can be found in the Digital window >Setup >'Turn Hover Mode On/Off'

Last Modification: 01 November 2014 06:34:22 EDT by n4zr.