Hello.
Is there a way to block particular callsign? Recently, there is a lot of bad decodes from 40m CW station reported as 5n6mew and 5n6aew because of poor operator keying. Can I block them forever somehow? Not for 6 hours.
Thanks, Mike
Hello.
Is there a way to block particular callsign? Recently, there is a lot of bad decodes from 40m CW station reported as 5n6mew and 5n6aew because of poor operator keying. Can I block them forever somehow? Not for 6 hours.
Thanks, Mike
You could add a “Not callsign” condition to your trigger(s).
Specifically, click on Add a condition | Call sign exclusions | not Spotter callsign.
Thank you for reply.
Unfortunately it does not work. Soon gives Ambiguous trigger and it’s disabled.
Any other option?
Thank you. Mike
You need to add this condition to your existing trigger(s), possibly all of them if they also match 40m CW. If you create a separate trigger with only a “not Callsign” condition, what you’re effectively telling HamAlert is that you want all spots (i.e. around 40 million per day), except those for the listed callsigns.
Also note the difference in the two conditions:
From your problem description above, it seems that you probably want a “not Callsign” condition, as the problem is not the spotter (RBN stations), but the poor keying of the operator sending his own callsign.
I’m getting a lot of N0CALL and N0NAME spotters as well as several x5xxx and x0xxx from all over the world. These are of no value as there is no indication of exactly where they are located. They are flooding my Triggers daily. My Spotter CQ Zone is set to 4 and spotter continent set to North America, which does at least reduce the foreign spotters with similar numerical calls.
A couple of Master non-trigger items such as:
I know these functions are available for each INDIVIDUAL trigger already, but MASTER non-triggers would be so much easier to manage.
Otherwise, ithis a great service and has helped me with many new DXCC Challenge Point numbers and a couple of ATNO’s as well.