Occasional Contesting - Observations
Posted: 28 Mar 2022, 09:10
Hi, I'm happy with Log4OM2 as an occasional HF contest logger and appreciate that's not it's forte. Just two observations from this weekend's WW WPX contest:
In contest mode, you can tab forward from callsign to the Contest Rcvd field, but you can't tab back to the callsign field (or I couldn't anyway). I'm not sure where the active field is, as the cursor just seems to disappear.
I've seen previous comments about slow callsign checking when contest logging. I experienced this too. I am using a new laptop (Intel Core i7-1195G7 Quad Core 2.90Ghz, 16Gb RAM). I disabled QRZ lookup, cluster display and I don't export QSO information. I'm not sure if it is QSO count or elapsed time related, but an occasional close down and restart of Log4OM2 did the trick. Without this, the few second DUPE checking becomes an issue and slows the QSO up. After a restart of Log4OM, it's instant lookup again (I'm amazed how fast this new laptop closes and restarts the app...didn't realise my old one was so slow!). In 24 hours I logged 900+ QSOs, so nothing too taxing for the application. I had the contest start & end parameters set correctly. At a guess, I would say 3 hours of operation highlights the issue.
Hope this info helps!
Thanks.
Ian.
In contest mode, you can tab forward from callsign to the Contest Rcvd field, but you can't tab back to the callsign field (or I couldn't anyway). I'm not sure where the active field is, as the cursor just seems to disappear.
I've seen previous comments about slow callsign checking when contest logging. I experienced this too. I am using a new laptop (Intel Core i7-1195G7 Quad Core 2.90Ghz, 16Gb RAM). I disabled QRZ lookup, cluster display and I don't export QSO information. I'm not sure if it is QSO count or elapsed time related, but an occasional close down and restart of Log4OM2 did the trick. Without this, the few second DUPE checking becomes an issue and slows the QSO up. After a restart of Log4OM, it's instant lookup again (I'm amazed how fast this new laptop closes and restarts the app...didn't realise my old one was so slow!). In 24 hours I logged 900+ QSOs, so nothing too taxing for the application. I had the contest start & end parameters set correctly. At a guess, I would say 3 hours of operation highlights the issue.
Hope this info helps!
Thanks.
Ian.