G0HIO/P is activating 4 G/WB summits today, but RBNGate is generating spots for each activation - all referenced to the FIRST summit he activated!
D’0h!
73,
Walt (G3NYY)
G0HIO/P is activating 4 G/WB summits today, but RBNGate is generating spots for each activation - all referenced to the FIRST summit he activated!
D’0h!
73,
Walt (G3NYY)
In reply to G3NYY:
As there is only one alert (G/WB-019 at 08:00) how can RBNGate know any different? It will hear G0HIO/P and decide it is within the parameters of the posted alert (minus one hour to plus three hours) and send it to SOTAwatch.
It appears to be case of user error …
73 de Les, G3VQO
Yeah, unfortunately the single alert specifies one summit in the summit reference field and lists the others in the comment. I’m guessing than the alert summit reference should probably have ended “???”…
In reply to M0LEP:
Indeed. GIGO.
Andy
MM0FMF
In reply to MM0FMF:
This is yet another reason why I never post alerts.
I was able to read and understand Michael’s alert for multiple activations with no problem. Unfortunately, computers are not yet as smart as humans!
73,
Walt (G3NYY)
In reply to G3NYY:
Unfortunately, computers are not yet as
smart as humans!
Some humans are too dim to be able to interact with computers effectively.
In reply to G3CWI:
Well designed applications do not require the end users to be accomplished computer programmers.
73 de G3NYY
In reply to G3NYY:
Stop trolling Walt and tell us how to solve the issue.
Andy
MM0FMF
In reply to MM0FMF:
Perhaps + 2 hours is too long a slot, even to allow for unavoidable lateness of an activation. I suggest plus or minus 1 hour is sufficient leeway.
BTW, I am not trolling. Merely making a considered observation.
73,
Walt (G3NYY)
In lieu of posting alerts for all the summits, a single alert of G/WB-???, as M0LEP suggested, would have generated similar RBNGate spots and alert chasers to follow up each WB-??? spot with the current summit spot.
The RBNGate system works quite well and is flexible.
73, Barry N1EU
In reply to G3NYY:
Perhaps + 2 hours is too long a slot, even to allow for unavoidable
lateness of an activation. I suggest plus or minus 1 hour is
sufficient leeway.
… which is why there are various user options within the program to cater for different styles of planned activation. The options, and additional information, are available at RBNGate by KU6J - Automatic SOTA Spotting
Of course, if users fail to avail themselves of the full facilities, it’s no good trying to blame the program. GIGO indeed!
Les, G3VQO
In reply to G3VQO:
The options, and
additional information, are available at
RBNGate by KU6J - Automatic SOTA Spotting
That is the first time I have seen that link posted.
I think the best advice is in the very last line of that file!
73 de G3NYY
Nonsense Walt.
I had no EE coverage on my phone this morning, and Jimmy’s on Vodaphone was very patchy for mobile data. RBNGate spotting was very helpful.
Thanks for calling and working me this morning. I assume it was the RBNGate spot that brought you to my frequency?
73, Tom MI1EYP
In reply to M1EYP:
Thanks for calling and working me this morning. I assume it was the
RBNGate spot that brought you to my frequency?
Thanks for the QSO, Tom. An all-time new summit for me.
No, it was not the RBNGate spot. I was not monitoring Sotawatch at the time. I heard you work another /P station S2S, then heard you calling CQ about 1 kHz higher.
Hope the WX is being kind to you!
73,
Walt (G3NYY)
In reply to M0LEP:
… the single alert specifies one summit in the summit reference field and lists the others in the comment. I’m guessing than the alert summit reference should probably have ended “???”…
Well it doesn’t take long to post 4 separate alerts… and the summits had been decided upon in this instance.
??? in my opinion is for when the summits have not been determined.
I for one certainly welcome the link to SOTAwatch, particularly as mobile coverage is still below what I consider to be acceptable in the UK. I had to have three attempts to speak to a Client this morning, getting repeatedly cut off. Well, I suppose he was out in the sticks, driving down the M1 between Northampton and London.
73, Gerald G4OIG
In reply to G4OIG:
??? in my opinion is for when the summits have not been determined.
Or when you don’t know how long you will be on any summit.
Andy
MM0FMF
In reply to G3NYY:
That is the first time I have seen that link posted.
I imagine that it will form part of the eagerly awaited SOTA FAQ?
73 Richard G3CWI
In reply to M1EYP:
Nonsense Walt.
Surely not?
In reply to G3CWI:
That is the first time I have seen that link posted.
I imagine that it will form part of the eagerly awaited SOTA FAQ?
We live in hope!
Michael’s single alert for 4 activations would have been perfectly correct and acceptable for Sotawatch until the advent of RBNGate; then the rules changed overnight (apparently). The fragmented documentation certainly needs to be brought together and kept up to date.
In any case, I have never been entirely sold on the idea of “spotting” systems such as DX Clusters, skimmers, reverse beacon networks … even Sotawatch to some extent. I feel they can often create new problems, e.g. uncontrolled pile-ups, incorrect recording of callsigns and locations, and the increasing phenomenon of people calling “blind” when they cannot actually hear the target station. There are advantages and disadvantages.
73,
Walt (G3NYY)
In reply to G3NYY:
Well well, I have been away for a few days to finish of the welsh borders and come back to see this. The alert was for one summit in the summit field and the comments were information for the chasers,in the comment field. Not sure how comments become summit alerts!
Its a good job I didn’t say I had my dog R2D2 with me. Thanks as always to everyone.
73 Mike G0HIO