Forum Replies Created
Correction of these errors may not be possible under the new WWFF policy that logs are final.
Indeed that is the case… wink, wink…
Incidentally, VK2ATC has 10 other contacts besides the two cited… you might like to check whether any of those are typos – although VK2ATC appears to be a valid callsign
PS: I’ve mapped your existing QSOs so tonight’s run should show you a consolidated status
It’s quite easy…
All you have to do is include <OPERATOR:6>SM5CBN in your ADIF for each SE5B contact… most loggers support both the STATION_CALLSIGN and OPERATOR fields so can auto-generate this.
Alternatively, for your SE5B activities, request the Log Manager specifies the Operator during upload.
This guidance applies to anyone operating Club, Vanity or Special Event callsigns
- This reply was modified 1 year, 10 months ago by Andrew M0YMA.
Apologies… those four are now back on your score 🙂
Since I am only 11 years old, my Dad had to tell me who big bird was.
Poor deprived child 🙂
Enjoy your radio, and listen out for M0YMA (YorkshireMan, Andrew) 🙂
- This reply was modified 1 year, 11 months ago by Andrew M0YMA.
the problem is the recognition of the club’s activation under the SES
Funny how SP500YFF was fully supported as an SP9YFF activity – and other multi-call activities.
“Coming soon” is a placeholder for any awards that are not routinely run…
Logged as part of Issue 79
I’ve added them to the list to be processed – please check back tomorrow for the results.
- This reply was modified 2 years ago by Andrew M0YMA.
The perils of callsign re-use, I’m afraid 🙁
I’ve migrated them to ‘ex-VK2APC’ until the previous holder of the call claims them
Given that, as of last night’s calculations, there are 119,478 regular WWFF hunter callsigns (with 10+ WWFF references worked), it would be impractical to show everyone.
The apply_for_awards privilege is granted by an automated check
It looks like it was granted overnight, so you should be able to apply now?!
Pleased advise the correct reference, and it can be corrected
By default me…
This suggests that your profile is incomplete…
If, when logged in, you click on “WWFF Logsearch” in the black bar at the top of the screen, you get your “My Logsearch” page
Under notifications, it should advise what’s missing.
A combination of a double suffix, and a short callsign has caused the prefix- and suffix-stripper to get confused.
Out of curiousity, is /4/P a normal double-suffix? I’m used to seeing just /n
If only the Log Upload had clear instructions as to what to do in this situation…