Discussion in 'Contests, DXpeditions and Special Events' started by WD5JTZ, Feb 7, 2020.
But we STILL do not have flying cars!!
Yeah, well.... it won't be long now
Just a little additional info:
Logging programs use your computers internal clock to time and date stamp entries in the log. Make sure your PC clock is reasonably close to the correct time. Then you have to use the correct setting in log program to set your time offset for UTC time (the current label for GMT or Zulu time). If you operate FT-8 you probably already have some method to calibrate your PC clock on a regular basis. If not, use one of the many free online aps to keep your PC clock set to the correct time. I use Dimension 4 which is available at :
Add me to the list of ham who recommend N1MM+ contest logging software. It's free and is regularly updated to reflect contest rules changes and adding new contests. If N1MM is your first jump into logging software it can be a little overwhelming. Fortunately there are some good tutorial videos on the N1MM website:
However, for some contests I prefer N3FJP contest logs (Field Day, State QSO Parties, November Sweepstakes). They are not free, but are reasonably priced. I have been using N3FJP general log for years and bought the entire suite of logs years ago and it has saved me quite a bit of $$. After every contest I import the ADIF contest log in to my N3FJP log, so all of my QSO's whether contest or not, can be found in on PC log. Saves time responding to QSL requests. You don't have to search through a dozen contest log files looking for the QSO. For just about every other contest I use N1MM+.
N3FJP logs can be found at:
See you in contests soon.
yes, you hit it on the head. I bought a n3jfp AFTER the WFD, not knowing any better, and had to correct all 164 times. I didn't understand that exact freq are no more just general band. Working with it after the fact, I thought about buying another....BUT, I have downloaded the N1mm and you said whats my problem right now....work with it. But, I like that fact it does more...what that is is yet to be read!!!!, but for general qso party for la. coming up...I need to read more. Thanks.
yes, I think the n3fjp is a last minute...if I cant get passed first page for my next qso party in Louisiana. I did use it after the fact from WFD, and kind of liked it after I understood the time stamp issue...and just putting 40 meter instead of 7.125. Thanks....and I do ft8 only to amuze myself from time to time. THAT WAS A BOOGER FOR WEEKS TO GET WORKING. 73
Welcome back to the hobby and back to contesting. I don't have any any advice that hasn't already been given here regarding logging. I do agree with the others that N1MM is a great choice.ñ and I hope to work you in an upcoming contest.
Steve, if you have a minute....I want to get ready for the Louisiana QSO party coming up. Can you tell me in YOUR logger, if Louisiana is listed? On mine, its not...and that may tell me that I may have to update from somewhere?
For the Michigan QSO Party I use N3FJP logging program. They have individual programs for each state QSO party. Find the list here:
I think if you buy one state QSO party registration key from N3FJP it works on all the state QSO party logs so you don't have to buy each state QSO party log. They are $8.99
N1MM can also be used for state QSO parties but I prefer N3FJP for QSO parties and Field Day, and N1MM for everything else.
Good luck and have fun.
After spending a couple days looking at N1MM, I think its more than I think I will ever use. If I am seeing it correctly, if I connect the computer to the radio...it would do all the calling on CW as well as Phone.
And while I think I would have the option to do that or not with N1MM. …….I think it must be a super program for those people that do a lot of contesting and spend plenty of time on the computer and like that
kind of stuff.........……...I think I may just go with the N3Fjp program... For me it is a fair price and I might even get the field day as well.
I appreciate your help. Hope to work you one day ...thanks again. mike