I activated SP-015 last night around 1800z. I returned home, had my tea and went back on the air from home. Unfortunately the RBN link spotted me back on SOTAWATCH. Some chasers worked me. Any QSOs after 1900z last night are not valid for SOTA. Sorry.
73 Richard G3CWI
In reply to G3CWI:
I knew I hadn’t seen you! I began my ascent around 1830z and was QRV 1900 to 2130z. All the same, probably didn’t miss you by much.
Tom M1EYP
In reply to G3CWI:
I have also suffered from this confusion. I have come to the conclusion that RBNgate ought to be more selective in its matches.
If I alert, or self-spot, as G3VQO/P then it should only send an exact matching spot to SOTAwatch. If it finds me sending just G3VQO then it should ignore it. Obviously the same differentiation should apply between other similar but different callsign pairs - F/G3VQO/P and F/G3VQO, F/G3VQO/P and ON/G3VQO/P, etc.
I seriously doubt that many, if any, legitimate SOTA spots will be missed if the change is made, and it will avoid the all-too-regular occurence of people posting on the Reflector to ask enthusiastic chasers to delete false chases.
Yes, I know that clever use of RBNN, RBNY and +s1 can assist, but it is easy to forget, or mistype, when on a summit, and those of us with stone-age phones cannot see the results on SOTAwatch in real time. Of course, chasers should always listen to check that the SOTAwatch information is correct, but how many do?
73 de Les, G3VQO
In reply to G3VQO:
I’ll ask Eric to exclude your call from RBN as that is the simplest fix as you sometimes find it difficult to drive or forget to set it up before going out.
Andy
MM0FMF