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: