G4BKI N1MM+ Logger tips page

Windows releases before Windows 7 are not recommended for use with N1MM Logger+
Latest information, support and questions can be found on the N1MM Logger+ groups.io [with 5158 members]
Group use: If you are using N1MM Classic, make it clear! It isn't supported. Always refer to newer version as N1MM Logger+, not just 'N1MM'. Give your platform, Windows version and all other important information. XP will not update some files automatically, as SSL (https://) is more fully rolled out during mid-2018.
Latest updates are announced on the group every Tuesday morning, or more frequently if required for bug fixes.
It helps everyone if you test a new version between Tuesday & the weekend when you are going to operate. Report any problems so that they can be fixed [from Tom, N1MM].
ONLY REVERT TO AN OLDER VERSION IF THERE IS NO FIX BY THE TIME YOU CAN WAIT NO LONGER.
**** DO NOT 'SYNC' N1MM+ DATABASES with remote files**** In other words, don't use OneDrive, Dropbox or Google Drive!
N1MM+ Logger latest version number. N1MM+ home site. N1MM+ latest update(s). N1MM+ PDF Help files N1MM+ HTML Help files
N1MM+ Experimental versions

Running N1MM Logger+ on Linux (Ubuntu, LinuxMint and Debian) with WINE

N1MM Logger+ is fast becoming the 'go-to' software for small and large DXpeditions. If you are running a small operation, I would recommend you use DX mode. It contains differences in comment, look-up and other features. For larger operations, use DXpedition mode to minimise satellite data upload sizes, etc.

USB/RS-232 interface: If you have a Prolific chipset I/F, throw it out. Many, many others before you have gone through this. Best solution is to get an FTDI chipset I/F.
Be careful. Some people refer to the program as NL+. This is very confusing. The official name is N1MM+ Logger, but is most commonly referred to as 'N1MM+'.
If your rotator no longer works through Alt-J and Alt-L: Configure->Configure Ports, select the Broadcast Data tab. The Rotator line should be: 127.0.0.1:12040.
Time sync: Use Dimension4, Tardis2000 [$$], NetTime, etc. Don't use the built-in Windows time sync service. It's overloaded & can be 45s 'out'.
Did you know that N1MM+ is one of the fastest updated Windows application programs at the rate of 50+ times per year? Keep it updated so that bugs can be addressed.
Installing or re-installing? Do not launch N1MM immediately after FullInstall is made. Download and run the Latest Update, THEN launch the program.
Don't you just love it when somebody posts to a Group (forum) "Please remove me from this forum"? Hint: There's a link for this in EVERY message.
While there has been a significant improvement with N1MM Logger+ CW generation, there are several things the Windows user can do to help eliminate 'choppy CW generation'.

The first thing is to go into Windows audio configuration and TURN OFF Windows sound generation. There is a good technical reason for this if you are using the PC's serial port for keying the transmitter.

The second thing is to slightly reconfigure the COM ports. Go into Windows Device Manager [if using Win 10, select Control Panel/All Control Panel Items/Systems/Device Manager], select Ports(COM & LPT), then at each Com port, select Properties/Port Settings/Advanced.

Then find Rcvr (bytes) and set it to 64; then select Tx (bytes) and also set it to 64. Change 'Latency Timer' to 1ms [NOTE! This depends on the specific RS-232 COM type device, some have it and some don’t]. This will improve the speed of your USB/Serial devices and help eliminate CW stutter.

Many utilities can help you out debugging USB and other devices/programs. Try checking at the Applications - Utilities section of my Applications - Latest Versions page.
Make sure that rig firmware is up to date. Watch out for Icom rigs, such as the IC-7300 (BTW: rig ID 94), which auto speed detect and can get it wrong.
Watch out for unexpected Windows 10 updates! Recently 'network not connected' [meaning Ethernet] suddenly caused 100% CPU load. Go to task bar at right hand side, left click on up arrow icon, right click on Windows Defender (Shield with a tick in it icon) left click on Open. Click on Firewall & Network protection then click on 'Restore Firewalls to Default'. Restart PC. You will be asked as you use various programs whether to allow or block access through the firewall, so click as appropriate.
Many errors are caused by a corrupted .ini file. Exit the program. Rename the N1MM Logger.ini file in the C:\Users\username\My Documents\N1MM Logger+ directory. Install the latest program update. Start the program. If this eliminates the error it was probably the .ini file. You'll almost certainly have to do some window location redefining, etc.
Tread carefully. Before each update back up to a USB stick. Bart makes it easy. Karen's Replicator is similar, but the author has passed away and there's no support.
You increase your chances of problems by running interfaces 'to the max'. Don't talk with your rig at 115200 baud rate, drop it to something sensible like 38400. Remember that you must change your rig to match and that some [TS-590S(G)] must be fully powered off before the change is actually made.
IC-7610 owners are using N1MM+. Check for and install the latest Icom drivers before connecting the radio to the computer.
Select the correct COM port. Open Device Manager expand Ports, with the radio power supply turned off, note the COM ports. Turn on the radio power supply. The additional virtual COM ports are associated with the radio. There are two that will show up. The first should be the radio control.
Set the radio menu baud rate to the fixed rate that you want to use. Auto selection can make mistakes when searching. Use 19200 with the CI-V interface and 115200 baud with the USB interface if the spectrum scope in Logger+ is to be used. The IC-7610 rig ID is 96. [IC-7600 was/is ID 7A].
If you can't find the contest you need in the 'normal' list within N1MM+ Logger, try going to the UDC area of the N1MM+ Logger Tiki-Wiki site [includes ARRL Grid Chase 2018].
Prevent Windows from turning off USB devices to save power here (ancient) or here (2017) or by W4TV.
If Windows 10 changes your drivers without warning, go here for instructions.
When you have a problem DO NOT keep removing N1MM+ Logger and re-installing it. You will probably not succeed and it makes troubleshooting harder!
Other COM port issues? In Device Manager / View enable 'Show hidden Devices'. Then, Device Manager / Ports, see if there are duplicate devices accessing the same COM port.
If you can't change bands using the Band buttons in the Entry Window go to the blank area and right click. Make sure "Band Button Left Click Enabled" is checked.
An HQ station lost contacts in IARU Radiosport. The reason? They used multiple computers with the same computer name. DO NOT DO THIS. Why? The program uses the computer 'name' to determine which computer is the "book of record" for a set of QSOs. When you connect to the network with another computer with the same name, but an empty log, you are telling the system that all of the QSOs logged by ANY computer with that name have been legitimately deleted! MAKE SURE ALL YOUR COMPUTERS HAVE UNIQUE NAMES. NetBios names are the ones used and they are limited to 15 characters. The names must be unique in the first 15 characters.
Some (K3) macro tips from PA1M.
The N1MM+ has a very limited implementation of OTRSP. N1MM sends AUX commands on antenna switching (e.g. AUX101, AUX215) and sends RX1/RX2/TX1/TX2 commands but no more. N1MM does not respond to any requests from OTRSP device (software), does not send PTT status, etc. The current OTRSP code has a some bugs and you need to be very careful. GS 232-A/B protocol seems to OK. UDP protocol seems OK, but again no PTT status. I have an Arduino based controller for my station and I can share some code if you need. Current version support antenna switching, PA/BPF control, Yaesu rotor emulation. [Andy - YL2QN]
You can use multiple startup configurations by using different .ini files. Details are given here.
microHAM devices seem to be a constant 'bother' for a lot of users with configuration or Win10 updates. You can fix your problems by following the examples exactly.
The *.ini file is not changed during a program update. The *.ini file is not opened during a program update.
There are two examples that allow you to log contacts in two contests during a given weekend:
1. Many of the QSO parties have agreements whereby they accept submissions of combined logs that contain contacts for their contest as well as other QSO party contests. By examining the logs and looking at the exchanges (which by agreement are distinct from each other) they identify which contacts in the combined log apply to their contest and its score. When you operate in contests that share a combined log, all of your contacts go in the same log file.
2. N1MM also allows you to hot-switch between two contests that you are running at the same time. You begin by defining these two contests on the >File >New Log in Database dialog. You can toggle between the two contests by typing <alt>F and pressing 2. This will toggle you between the currently open contest log and the other contest log.
**** DO NOT SYNC N1MM+ DATABASES ****. Sync programs (e.g. OneDrive) do not understand SQLite databases and will corrupt them. N1MM Logger+ SQLite databases consist of 3 files when open and one file when closed. If you mix and match from different times (which a sync program can do), you will end up with a corrupt database.

W4/VP9KF - CW keying hints

CW keying hints
How to make your logging program work with CW.

The K1EL WinKeyer needs to have the correct FTDI USB driver loaded on the PC. Use Device Manager to confirm it is there and to see what COM port it is on. It may have changed.
If the keyer 'disappears', go into Device Manager, right click on the USB port and deselect "allow USB to sleep when inactive".
Download the WKxMGR software from K1EL and confirm you can talk to the WinKeyer. It is useful to configure the WinKeyer, update the firmware and for trouble shooting. Note there are different versions depending on the WinKeyer you have.

Early WK2USBs had a problem of getting locked up if they had internal batteries installed and the PC's USB port went to sleep. To unlock the WK2USB you need to disconnect the WinKeyer's internal batteries. There is a firmware update that fixes this problem. If you are operating while connected to a PC, leave the batteries out anyway. Memories will be retained.

W4/VP9KF - some fixes for N1MM+ Logger

N1MM+ Logger Fixes
All software has some niggles, these are some easily fixable things in the source code.

Interface with new web page was VERY, VERY SCREWED UP!!!!
As of 2019-12-12, the following things were not working correctly:
Pretty pathetic troubleshooting

Has the 'feature' hard-written into WAE CW S&P mode that forces a send of 'QTC?' been fixed before it gets forgotten?????????????

WHY is the 'Rotor Control' (sic.) Window not part of the N1MM+ window normal behaviour, yet sits on top and in the way all the time? It's a PITA!
Why can't it be integrated and popped-up as needed?

Everybody I've talked to recently (and the manufacturers) always use the term ROTATOR, not rotor

Similarly, why can't a call from the .ini file be made to open a true N1MM+ Logger window which can call another program such as a browser? [Hint: to show a lightning page]

Why are new version announcements on the groups.io Group always made with 'Re:' at the beginning of the subject, as though it was a comment about a missed previous message?

Please remember that the N1MM+ Logger code is written and maintained by a group of volunteers. It's tough because of the vast number of transceivers, support devices, modes and versions of PCs and Windows that are supported all at once. Some troubleshooting is recurring and is not easy to find in the [transferred] Yahoo Group 'archives'. Hence these notes. Some problems are difficult to reproduce without many hours of their time.