1.9.4 The Most Frequently Asked Questions

We have tried to pull together here the most frequently asked questions. As issues come and go, we anticipate changing this section, hopefully frequently, so if it comes up in a search of the web site, it could be worthwhile to check here first. Each answer also contains a link or links to the manual sections that address the issue in much more detail. The MFAQ is not intended as a substitute for the manual.

1. Installation and Updating

1.1. Q. I just downloaded the latest update and my virus software told me that it is infected. Is this true?

A. No. Software that accesses the outside world (DX clusters, the N1MM web site, contest sponsors' rules) is frequently mis-identified by anti-virus software. Depending on which one you have, you may have to disable it, or simply tell it that the program is OK, but there's no way that N1MM Logger is infected.

1.2. Q. I just installed the program for the first time, and it won't install or won't start. Why?

A. Did you install the Latest Update after you installed the Base Install? Both are necessary. Did you reboot your computer after the Full Install? The minimum platform is Win XP/SP3 with 4 gb memory. Win 7 or later is recommended. Installation on some Win XP/SP3 configurations will fail. (This problem is usually (always?) associated with AMD processors.) We have investigated, but not found a solution. Please upgrade to a later operating system. XP has been out of maintenance since April 2014.

1.3. Q. I haven't updated in a while. Do I need to apply each update in order? If I apply the latest one, and it doesn't work for some reason, can I go back?

A. You can simply download and install the latest update. If not, you will need to redo the Base Install and then install ONLY the latest update. You can generally revert to a recent update from the latest one without any problem. In fact, this is the recommended procedure if you run into a problem, since you may be able to pinpoint exactly which update introduced it.

1.4. Q. Shouldn't I install a stable version? What if the latest one has a bug I can't live with?

A. Each new version is a complete update from the (non-operational) base version, so there is no benefit to installing or keeping an older one. If the new release has a bug that you can't live with, and you need a fix before the following week, you can easily reinstall the last previous version.

2. Operating

2.1. Q. The program won't let me log a contact. It keeps insisting that something is wrong with the exchange. What can I do?

A. Ctrl+Alt+Enter will force logging any contact, and open a note window, where you can put something to remind you to fix the QSO after the contest is over, when you've discovered what was wrong.

2.2. Q. Why doesn't F1 send my call properly in S&P mode? I can program it into the key, but when I use it the program switches to Run mode and I get crossed up.

A. In N1MM Logger+ the F1 key has special attributes; in particular it automatically switches from S&P to Run mode, which make it problematic to use it, as some are used to doing, for your own callsign. F4 is customarily used for this in N1MM Logger+. Note that if you use ESM (Enter Sends Messages), then in S&P mode the program will send your callsign (F4) when you press <Enter>; in Run mode it sends your CQ message, which is stored in F1.

2.3. Q. I see spots coming in on the Packet/Telnet window, but they aren't appearing on the Bandmap or in the Available Mults and Qs window. What to do?

A. On the Packet/Telnet Window's right-click menu, there is a "Why don't I see Spots?" selection. Choose it, then follow its suggestions and set up the Packet Filters options, which control which spots are passed to the Bandmap and Available windows. You must select at least one frequency range (HF, WARC, VHF) option or nothing will go through.

2.4. Q. I've lost my Bandmap window (or Check, or Available Mults & Qs, or ...). How do I get it back?

A. Most likely, the window is invisible because its saved location is outside the dimensions of your screen. In version 1.0.6753 or later, to move a lost window on screen, hold Ctrl+Shift while clicking the window name in the Entry window's Window menu. For windows that are not part of the N1MM Logger+ program itself, such as digital engine windows, use the Windows Task Bar. Find the icon for the missing window on the Task Bar and right-click on it. If the Move option is greyed out, use Restore to try to restore the window; if Move is not greyed out, press one of the arrow keys on your keyboard two or three times. Enough of the window should appear on screen to let you move it around with the mouse and then left-click when the window is where you want it.
There is one special case:
Rotor: Edit N1MM Rotor.ini and change Top & Left to 0 (zero) to bring the window to the top left corner. The N1MM Rotor program must not be running while you do this. This method also works as a last-ditch method with N1MM Logger.ini - you need to find the section in the ini file that controls the window you are looking for and set its Top & Left to zero to force that window to open at the top left corner of the display when you restart the Logger.

2.5. Q. I know that TO7M is in Martinique, but the program says otherwise. How do I fix this?

A. Callsigns are identified by country files, which are produced and updated by AD1C. You probably need to update your wl_cty.dat file from his website, and then load it into your database. If you run into this problem during a contest, your best move is to log it and go on, placing a note in the log with Ctl+N to remind yourself to fix the log before you submit it. After you load the wl_cty.dat with the corrected country data, run Tools > Rescore Current Contest to update your Score Summary and multiplier counts.

2.6. Q. When I enter my callsign in the Entry Window, the Check Window says "Unique". Why?

A. The program checks entered callsigns against a master.scp file, and that message means that the callsign was not found. These files are prepared and updated by WA1Z, based on people's past contest logs. Check the Super Check Partial website for the latest version and download it into your N1MM Logger+ user files area in the Support Files folder. These do not need to be loaded into your database; you specify which file to use under the Associated Files tab in the Contest Setup dialog. If you have the latest version and your call doesn't appear, you just need to be more active in contests.

2.7. Q. I can't find a contest that I want to operate in N1MM Logger+.

A. Over 250 contests and QSO parties are supported directly by N1MM Logger+. You can look them up here. In addition, over 100 contests have been defined using our User Defined Contest editor, developed by NA3M. To use one of these, you will need to copy the relevant UDC file from this file gallery on the web site into the UDC folder in the user files area, and then re-start the program - the UDC will now show up on the list of possible contests in the Contest Setup Dialog. A final option, if you don't find your contest in either place, is to write your own UDC. It's not terribly hard if you thoroughly understand the contest's rules.

2.8. Q. What is the difference between SO2R and SO2V?

A. SO2R is the "single operator two radios" mode of contesting, where you control two radios from one logging program. SO2V (single operator two VFOs) is a technique for using two VFOs on a single radio to approximate the benefit of SO2R. Because you cannot listen on the same radio you are transmitting on, it will never be as flexible as SO2R, but you can use the second VFO to work stations S&P while continuing to run on the first VFO, particularly when things are slow. A fuller explanation is found here.

3. Interfacing

3.1. Q. PTT or CW isn't working properly. Why not?

A. The program has a lot of different ways to "key" PTT, to accommodate the wide variety of radios and operator preferences. From within the program, you can assert PTT (another, more accurate verb) by the RTS or DTR pins of a serial port, via pins on a parallel port, or through serial radio control, for radios that can do that. CW can be sent through a serial or a parallel port, or by the use of Winkey. Here are some things to check:

  • Make sure you have only one PTT and one CW method set for each radio. The program will always use the first such method it finds, reading down through the list of serial and parallel ports that have the "Other" checkbox checked, so if you have set more than one, unpredictable things may happen.
  • If you are using a Winkey, and you have it configured to control PTT (yet another way to do it), it will do so for stored messages on all modes, not just CW. If you want something else, the easiest thing is simply to pull the PTT line out of the PTT jack on the back of the Winkey to disable it.

3.2. Q. My Icom radio gets out of sync with the program on things like split frequencies, and I wind up spotting the wrong frequency sometimes, which is embarrassing. What is wrong?

A. Icom radios only send the frequency of the active (selected) VFO to the program. If you set split frequency operation on the radio, the program is not informed, and so it will spot your transmit frequency instead of the received frequency as it should. The solution is simple - use the keyboard to enter the split receive frequency (Alt+F7, frequency or split, e.g. 7067 or +5, Enter) .

3.3. Q. My CW seems to stutter or have bad weight sometimes. Why?

A. N1MM Logger+'s serial and parallel port CW options are a simple and easy way to generate CW, but if your computer is slow, you may find the CW is not always smooth, particularly when receiving spots from a Telnet cluster in a busy contest. If this happens with serial keying, try using a parallel port if you have one. If you don't, or if you want to put an end to CW issues once and for all, the answer is K1EL's Winkeyer USB, which handles CW and all-mode PTT by offloading these functions from the computer entirely. It is also an excellent stand-alone keyer with 4 built-in memories.

  • Always do these:
    • Turn off Computer sounds. (Control Panel/Sounds)
    • Do NOT change the weight. It's never weight. If you have it set to anything other than 50, change it back before trying anything else
    • Do NOT use a usb-to-serial adapter with the Prolific chip set. Many are counterfeit, and finding a driver that will work is very, very difficult or impossible. Use one with an FTDI chip set or use an Edgeport adapter. If you are wondering why your Prolific adapter works with Brand X logging program and not N1MM+, it is probably because the other program does not use MSCOMM.OCX or the .Net SerialPort class. Prolific has had problems with support of Microsoft serial port support. You are much better off using an alternative. An FTDI USB to serial adapter is $15 at Newegg.com.
    • Real serial ports always work. If you have a desktop, this is your best choice.
  • If the above fails, do these:
    • Turn off virus programs - if this is a cause, find another program
    • Turn off packet - your computer might be overloaded by packet
    • Turn off call lookup
    • Less severe, close multiplier windows and turn off Available window counting of mults & Qs
    • Try a contest with a less complex multiplier - WPX is one of the worst
    • Close other programs and processes. Use Ctl+Shift+Esc to see which ones are using the most
    • Get a processor with multiple cores (but not a Core2 Duo). See Passmark CPU Benchmarks for ratings.
    • Get more memory

3.4. Q. I interfaced for CW, but I get nothing but oddly spaced all dots or all dashes. Why?

A. Turn off the built-in keyer in your radio. The program sends the dots & dashes. You have it set up to use paddles as input.

3.5. Q. My CW weight is way off. I'm using a USB-to-serial adapter and keying with RTS or DTR. Why?

A. Some adapters have a lot of latency and will mangle your CW. Usually this can be corrected by finding a better driver for the adapter. Make sure you are running the latest vendor-provided driver for your operating system, not the one the OS picks. Some adapters allow you to set the latency in control panel. See this article.

USB to serial adapters that use the Prolific chip set are NOT recommended. There are many counterfeit chips and even the genuine ones can have problems. For Prolific chipsets run this program: http://n1mmplus.hamdocs.com/tiki-download_file.php?fileId=2203 This will check your Prolific adapter for compatibility and install the latest driver, which has worked for some users. Note that the problem can return if your OS installs an old driver.

FTDI and Edgeport USB to serial adapters have proven to create the fewest problems.

A Winkeyer is the best choice for keying - http://k1el.tripod.com/wkusb_smt.html

If all the dits and dahs are the same length, you may have set the radio to expect paddles rather than a straight key. Turn off the "electronic keyer" function in the radio.

4. Other

4.1. Q. I'm having trouble importing an ADIF file. Some of the information seems to be missing or in the wrong place.

A. ADIF implementations vary widely, and it is quite common for an ADIF file produced by another logging program to contain ADIF "tags" that N1MM Logger does not recognize. Here's how we suggest proceeding, to avoid these problems:
1. Create an instance of the contest you want to import in your current N1MM Logger database.
2. Log a "dummy" QSO. If there are different types of QSOs, e.g. different exchanges from W/VE vs. DX stations, log at least one QSO of each type.
3. Export an ADIF file.
4. Compare the ADIF file produced by N1MM Logger with the one you want to import. Each data item in an ADIF file is preceded by a "tag" including a number denoting the length of the data item. Here are some examples, part of a QSO record from a general logging program:
<TIME_ON:6>003039 <CALL:6>YC6JRT <MODE:3>SSB <BAND:3>10m <RST_SENT:2>59 <RST_RCVD:2>59 <CQZ:2>28
If the "tag" is different than N1MM Logger uses for the same content, use a word processor or other editor to change it as needed.
5. Make sure the ADIF file you want to import contains a field tagged with the CONTEST_ID tag, and with the same contest name as in the ADIF file exported from N1MM Logger.
6.Then go ahead and do the import, and everything should be fine.
You can reverse this process to export an ADIF file, for example to a general logging program.

4.2. Q. I want to use N1MM Logger+ as my general logging program, but I can't find out how to track my DXCC, or whether I have sent or received QSLs. Why not?

A. N1MM Logger+ is a contest logger. While it has "DX" and "DX Serial" generic "contests" that can be used for general logging, it does not have many of the features needed in a general logging program. The best solution is to export your contest QSOs from N1MM, using ADIF, and import them into one of the many excellent general loggers that are available.

4.3. Q. I got a cryptic error message. What do I do?

A. Make a detailed note of the error message number AND message as accurately as possible. We need that information, together with the sequence of program operations that resulted in the error, in order to trouble-shoot and solve the problem.

4.4. Q. I posted a problem on the reflector, but it never got fixed. Should I do something else?

A. Yes. Go to the web site and file a Bug Report. Same goes for Feature Requests. While we try to respond to every problem that is reported on the reflector, the structure of these two systems helps us keep track of what's been fixed and what still needs to be.

4.5. Q. A window has a very large or small font and changing the fonts with "Manage Skins, Colors and Fonts...:" doesn't change it much.

A. Most windows have a "Font Sizer" in the upper right-hand corner. This is an up/down control that you can click on to adjust this windows font size up or down from the default.

Last Modification: 12 October 2017 08:39:16 EDT by VE3KI.