As a chaser, I log all my QSOs with GMAwatch-3 (GW3). It has an option to automatically upload your SOTA QSOs to the SOTA database. You only have to enter your SOTA password once in the settings.
I log the chase straight onto SW3 page as I go and also write it on my note pad on the bench so I know who I have chased. Is the chase on SOTA so busy you forget who you chased??.
Yes… the answer is that it certainly can be. As an activator I have experienced repeat calls from chasers when I have been handling an extended run of contacts on one band and mode. This is easy to deal with on SSB by referring to the time that the previous contact was made, but not so easy on CW, especially as some operators would not expect plain language during the exchange. SOTA CW contacts can be very basic!
Quite a number of my logs have duplicate contacts instigated by chasers, as on CW I find it easier to work them a second time rather than try to explain the dupe. I then check which of the two contacts they’ve logged so my submitted log tallies… sometimes I have found that both have been logged.
I can sympathise with Remy, but my suggestion would be to simply keep a written list. However, even that is not foolproof when working a large amount of stations, as indeed I have experienced myself during contests. Of course contest working warrants a specific check log system, but this would be overkill for SOTA.
I’m a very occasional chaser, and I’m not familiar with the callsigns of most activators. I mostly just browse the bands to see if I hear someone, and if I do, I make the contact. I’m not trying to keep track of anything or achieve anything, so callsigns and summit references don’t really stick with me, if you see what I mean.
I just realized how useful this feature actually is when chasing from a summit with the Polo app, compared to chasing from home with SW3.
The basic infrastructure to run this is in place, I’ll work on the front end at some point soon, thinking about how to limit the impact on the systems.
