Page 1 of 1
Contest Mode Questions
Posted: 06 Mar 2022, 21:58
by G4IUA
This weekend I took part in the ARRL SSB contest - simply for fun rather than seriously. I know Log4OM doesn’t pretend to match anything like the N1MM software which is dedicated to contesting rather than general logging. One thing I found is that entering a callsign there was a delay of perhaps 2 – 3 seconds before it reported whether I had worked the station before or not. Even though I wasn’t seriously contesting it was an annoying delay. I’m not sure why such a delay; it must be looking up my logbook for a ‘worked before’ status but with a fast PC I thought that would be almost instantaneous. It soon displays information presumably obtained from qrz.com (name, address etc) which would be interesting during a normal QSO but during a contest this isn’t really necessary. Is it this lookup that is what is taking the time? If so, is there an option to disregard this lookup to speed up the process? The logging function itself works well. My other thought is that I have about 5000 contacts in the database. Does it check all these contacts rather than just those made during the contest?
The computer is very up to date (latest generation i5 CPU, SSD, 16Gb RAM etc.). Clean installation of Windows 11 just a week ago. In other words the PC isn’t the bottleneck.
The other question is that in the contest mode what is the difference between a station shown as a Dupe and a Dupe Emission?
Jeff - G4IUA
Re: Contest Mode Questions
Posted: 17 Mar 2022, 17:15
by G4IUA
A follow on question: is it taking time to look back through ALL logbook entries, which in my case is well over 5000. Presumably that would take a considerable amount of time, even with a fast PC. Is it possible to force it to look at just those contacts made during the contest? Then it would have relatively few to check.
Any ideas would be welcome.
Jeff - G4IUA
Re: Contest Mode Questions
Posted: 17 Mar 2022, 23:42
by G4POP
G4IUA wrote: 06 Mar 2022, 21:58
This weekend I took part in the ARRL SSB contest - simply for fun rather than seriously. I know Log4OM doesn’t pretend to match anything like the N1MM software which is dedicated to contesting rather than general logging. One thing I found is that entering a callsign there was a delay of perhaps 2 – 3 seconds before it reported whether I had worked the station before or not. Even though I wasn’t seriously contesting it was an annoying delay. I’m not sure why such a delay; it must be looking up my logbook for a ‘worked before’ status but with a fast PC I thought that would be almost instantaneous. It soon displays information presumably obtained from qrz.com (name, address etc) which would be interesting during a normal QSO but during a contest this isn’t really necessary. Is it this lookup that is what is taking the time? If so, is there an option to disregard this lookup to speed up the process? The logging function itself works well. My other thought is that I have about 5000 contacts in the database. Does it check all these contacts rather than just those made during the contest?
The computer is very up to date (latest generation i5 CPU, SSD, 16Gb RAM etc.). Clean installation of Windows 11 just a week ago. In other words the PC isn’t the bottleneck.
The other question is that in the contest mode what is the difference between a station shown as a Dupe and a Dupe Emission?
Jeff - G4IUA
No its only checking the QSO's during the duration of the contest that you set up, not your complete logbook so the issue lies elsewhere, perhaps your on line call sign lookup provider!
You did set up the contest date and time parameters didn't you?