CW Skimmer and Skimmer Server take the "historical plausibility" of
prefixes into consideration in deciding how rigorously to validate the
callsign. TK5 and EK3 are pretty plausible. Adding an extra half-space
between multiple renditions of the callsign has been reported to be a
good way of avoiding this sort of busts, because Skimmer is quite good
at figuring out when one "word" has ended.
73, Pete N4ZR
Check out the Reverse Beacon Network at
http://reversebeacon.net,
blog at reversebeacon.blogspot.com.
For spots, please go to your favorite
ARC V6 or VE7CC DX cluster node.
On 2/19/2013 10:11 AM, Ward Silver wrote:
You were frequently spotted as TK5GO this weekend...I had no idea you
were vacationing in Corsica, Stan :-)
It's likely due to transmit leading-edge artifacts. The following "E"
(as in K3LRE) is probably artifact-driven as well. These are not even
noticeable to human operators but the software doesn't know to ignore
them. Yet.
73, Ward N0AX (at K3LR on 15 this weekend with K1DG)
On 2/19/2013 8:53 AM, cq-contest-request@contesting.com wrote:
On a secondary note, what causes there to be a huge number of EK3LR
spots from all over the world and not a single EK5GO?
Stan, K5GO
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|