I saw this email on the N1MM reflector and recalled that there was some confusion about LOGTHENPOP & LOGTHENGRAB during the run up to CQWPX RTTY a couple weeks ago. The first email was cut from one from Rick Ellison, N2AMG, the digital programmer of N1MM, in response to a query on the reflector.
—– Original Message —–
From: “Ken Wagner K3IU” <email@example.com>
To: “Mike McKaughan” <firstname.lastname@example.org>; “Pat Atwood, NG1G” <email@example.com>; “Ed Haskell” <firstname.lastname@example.org>; “W1AN” <email@example.com>
Sent: Sunday, February 19, 2012 9:08 AM
Subject: LOGTHENPOP vs LOGTHENGRAB
This should clarify as explained by the guy who wrote it…
“Log then pop allows more control as it allows the operator click on calls
that they see in the screen and stack them on the bandmap to work in
Log then grab instead of using the bandmap just grabs the next available
call from the grab window on the Digital window. Sometimes you might be
grabbing a garbage callsign as some calls do not decode correctly and still
get placed in the grab window. So the operator needs to be aware of the call
that is being grabbed..
73 Rick N2AMG”
On 2/19/2012 9:19 AM, Pat Atwood, NG1G wrote:
Thank you for that elucidation, Ken. I suspected as much from reading the manual’s description of where the “grabbed” calls came from, but with no direct experience I couldn’t swear to it.
BTW, in the little time I spent working 80M this weekend I used ESM, and found it very helpful as long as I didn’t screw up the sequence by hitting SPACE too early. I just need to better train my brain and hand to the motions.
On 2/19/2012 10:17 PM, Mike McKaughan wrote:
Let’s include Rick in these discussions so he can stay up to speed as he learns N1MM Logger. Does someone want to volunteer to put these e-mails on the Web site so we know where they are? Also, we need to start documenting all the little things we learn about the Logger during contests so we know where all the tricks are stored.
We had trouble this CW weekend with the program freezing on the Windows-7 computer that ran the Yaesu 1000MP or the side of the room where Ken’s K3 was used during the RTTY WPX weekend. I found info on the FAQ (I think) for N1MM about how to install the logger on Windows 7 computers. I didn’t see anything that looked unusual (make sure you’re Administrator when you install the software), but I do not have a Windows-7 machine.
I’ll be in contact via e-mail only through Thursday.
Date: Mon, 20 Feb 2012 05:31:49 -0500
From: Ken K3IU <firstname.lastname@example.org>
To: Mike McKaughan <email@example.com>
CC: “Pat Atwood, NG1G” <firstname.lastname@example.org>,
Ed Haskell <email@example.com>,
W1AN <firstname.lastname@example.org>, KI1G <KI1G@verizon.net>
Subject: Re: LOGTHENPOP vs LOGTHENGRAB
I have seen something somewhere in the last couple of weeks saying that Win7 problems, assuming that N1MM Logger was installed correctly, is probably caused bu RFI. I can’t imagine how RFI would cause problems with the software, but that is what was reported. It was recommended that ALL equipment have chassis’ connected together and to the station ground. It was NOT reported that this cured the problem with crashes.
The special installation instructions for N1MM on a Win7 machine are mainly about “where” to install it because of the Win7 “security” setup that objects to a program writing to a file in the \Program Files folder where N1MM (and virtually everything else) used to be installed. The default installation folder is now in \N1MM Logger folder. Also as Mike says, the installation should be made by right clicking on the installation file and selecting “Run as Administrator.”
73, Ken K3IU
From: “Rick Davenport” <email@example.com>
To: “‘Ken K3IU'” <firstname.lastname@example.org>,
“‘Mike McKaughan'” <email@example.com>
Cc: “‘Pat Atwood, NG1G'” <firstname.lastname@example.org>,
“‘Ed Haskell'” <email@example.com>, “‘W1AN'” <firstname.lastname@example.org>
Subject: RE: LOGTHENPOP vs LOGTHENGRAB
Date: Mon, 20 Feb 2012 08:33:22 -0500
I did not experience any major issues with N1MM this weekend, only a minor
annoyance on the computer connected to the FT-1000, every time I would click
on a spot to go work it, the software would put the rig in dual receive mode
which gives the headphone audio a whole new sound. Probably just a setting
that I need to change somewhere, but finding the somewhere is the hard
part. I did not use ESM mode, just programmed the F-Keys as I have always
used them in Writelog.
Other than that, the weekend started out on record pace and stayed so until
06Z on Sunday when my K3 shut off, the FT-1000 did not hear any signals and
there was an alarm that I have never heard before that was beeping away in
the shack. Needless to say that after being up and on the rig for 30 hours
prior to all this, some mental chaos ensued.
Turns out that the alarm was an overvoltage alarm on my 12V power supply and
it had turned off the DC output. No 12V = no K3 and none of my other
switching widgets were working. I do not have a back up power supply and am
still off the air. Moral of this story is to know your stations Achilles
heel. Once I decide on what to replace the power supply with, I will be
Hope everyone had fun….