What do you get when you mix N1MM, Morse Runner, and AutoHotkey? Simulated contesting fun, that’s what! Logging the Qs with N1MM gives you a chance to see how the super check works, tells you what country the call is from, and lets you track all of the multipliers. Given enough time, you could try to blackout all the multipliers. That’s just one of the possibilities.

How it works:

You need AutoHotkey, N1MM, and Morse Runner so download and install them. I configured N1MM to only use one COM port for CW keying. It doesn’t matter what port you pick because no rig should be connected to the COM port. N1MM needs to think it is sending CW.

Create a new CQWPXCW log in N1MM. Use ‘Running CQ’ mode by enabling the ‘Running’ checkbox. Make sure N1MM is in CW mode because the script expects the N1MM entry window to have “CW Manual” in its title. I turned on ESM mode in N1MM but that is not required. The AutoHotkey script (download link below) reads keystrokes as you type and sets the input fields in Morse Runner to whatever is in the corresponding input fields in N1MM. The script intercepts function keys that are for Morse Runner so that they won’t confuse N1MM.

There are Gotchas! I found that sometimes the Q is not saved in N1MM but still makes it to Morse Runner. I suggest setting N1MM to allow dupes for those contacts that need to be repeated after you already saved the Q in N1MM. Only the basic keystrokes are available in N1MM. In other words, I’m sure I didn’t think of every keystroke that would work in N1MM but not Morse Runner. Morse Runner always sends the call as though it had been corrected. I suspect the repeat is a result of how the AutoHotkey script updates the fields. You don’t need to worry if the sent serial numbers in N1MM are out of sync with Morse Runner. The only serial number that is important is the one that you receive not the one you send. Observe this video demonstration:

Nice job Don and excelent functionality. Running at Dell Latitude D600 under WinXP without any problem. N1MM v8. I installed only AHK2EXE and after this converted your source script to exe file. Thanks a lot for your job.

Just found this interesting information, Google pointed to. I’m using Morserunner v1.68 and N1MM Logger 9.1.6 and downloaded you AHK file, but the extra callsign at the end of the qso, also mentioned by VU2PTT (15th AUG 2007) is still there. How can I get rid of that?

Hi, Don. Great job on marrying MorseRunner and N1MM. I have been following with great interest the development of TR4W. Is there a chance that you might followup your success with MR/N1MM with maybe, per chance, TR4W?

Information about your MR/N1MM/autohotkey was given to our field day group members for them to practice on in the weeks before field day. Judging from our scores on CW, I’d say it worked very well getting those not regularly contesting up to speed on FD weekend.

Don, I’ve been playing with the combo setup and it really plays neatly….some dups still linger about. I am improving my contesting skills through the use of this marvelous virtual competition idea of yours.

I happen to comeback to find the AutoHotkey again. Just wanted to mention how much improvement this setup has done to me. I am copying up to 35wpm callsigns!! This has been achieve by a 20 minutes practice on a daily basis.

windows 8.
Downloaded your hotkey for for n1mm/morse runner but i have no control over the function keys in n1mm plus. Here’s what i have done.
Step1. N1mm plus configured for wpx, cw com port 3 for cw
step2. morse runner set for wpx
step3. hotkey script. (logo sitting in my taskbar)
start morse runner, hit return, get lots of calls but no response
from n1mm plus. BTW using sindows 8. would like to use this setup.
Can you help. John