In reply to HB9DST:
I do not understand why these QSOs might not be considered valid.
I don’t think that anyone is asserting that the QSOs might not be considered valid. People were wondering why my RBNGate software automatically spotted both HB9HST and HB9HST/P to Sotawatch several times (the automatic spotting happens when Reverse Beacon Network hears a station calling CQ within X hours before or Y hours after the time in a corresponding SOTAWatch alert, with X=2 and Y=3 at the time of the HB9HST spots).
The explanation for why that happened is over in this rather long thread regarding Automatic SOTA Spotting, down near the bottom:
To save you from having to dig through it, I’ll quote the most relevant parts below. From Rick M0LEP:
The system caused a bit of confusion this morning following this alert:
10:00 HB9HST on HB/BE-138 7.032-cw,10.118-cw
The alert didn’t include the “/P”, and the 11 RBNGate spots aren’t unreasonable under the circumstances:
Thu 12:06 HB9HST on HB/BE-138 7.009 cw
Thu 12:02 HB9HST on HB/BE-138 10.1191 cw
Thu 11:07 HB9HST on HB/BE-138 10.115 cw
Thu 11:02 HB9HST/P on HB/BE-138 7.032 cw
Thu 10:51 HB9HST/P on HB/BE-138 7.033 cw
Thu 10:34 HB9HST on HB/BE-138 10.12 cw
Thu 10:33 HB9HST on HB/BE-138 10.123 cw
Thu 10:05 HB9HST/P on HB/BE-138 7.0321 cw
Thu 09:44 HB9HST on HB/BE-138 21.0178 cw
Thu 09:16 HB9HST on HB/BE-138 7.014 cw
Thu 08:01 HB9HST on HB/BE-138 7.027 cw
The explanation from me. Note that I wasn’t aware of there being two different stations signing HB9HST and HB9HST/P as you explained above, so I was referring to what I believed to be a single station as “he” and “him” rather than “they”:
RBNGate ignores portable designators such as “/P” in both the alert and the spot when doing a callsign comparison between alerts and spots. In all of the cases you listed, the callsign was treated as “HB9HST” for the comparison and for duplicate spot checking, but he was spotted using whatever RBN heard him send with his CQ.
In each of the cases you listed, HB9HST either changed bands or changed frequency by more than 1 kHz, so RBNGate sent the spot in to Sotawatch. I see numerous cases in my software log where an RBN spot of him was rejected and not sent because it would have been a dupe to a spot already in Sotawatch.
All of the spots were within 2 hours of his 1000z alert time. However, not long after the first RBNGate spot of him at 0801z, HB9CGA sent in a spot of him at 0808z with this comment: “no SOTA, says later”.
In response to an NA activator’s request for the spot window to extend to 3 hours after the alert time rather than 2 hours, I have since modified the software to allow the time window before and after the alert time to be independently configured. It might be better for me to reduce the before-alert-time window from 2 hours to 1 hour (or even shorter), especially if HB9HST was indeed not yet on the summit at 0801z.
As always, opinions and suggestions for improvement are welcomed!
Correction: I forgot that I had actually changed the after-alert-time window to 3 hours in response to the request from an NA activator, so his 1202z and 1206z were within that 3-hour window rather than the 2-hour window I mentioned (the before-alert-time window was still set to the original 2 hours when he was spotted at 0801z).
In the interest or preventing further confusion since your event is still ongoing, I have temporarily added HB9HST to the RBNGate software’s excluded activator list. This will prevent RBNGate from spotting HB9HST, HB9HST/P, F/HB9HST/P or any other form of the HB9HST callsign, even if a corresponding activation alert exists in Sotawatch. I can remove HB9HST from the exclusion list after your event concludes (or leave it in at your preference).
Hopefully this information clears up the mystery.
Free SOTA Spot Monitor Software: