[Skimmertalk] Help--What's Going On?
w6sx at arrl.net
Sat Jul 21 07:59:20 PDT 2012
Thanks to everyone who responded. TV Bob and Dave nailed it I think. WS6SX
is showing up more often now. Thanks to all who added +ws7@@.
On Wed, Jul 18, 2012 at 3:58 PM, K1TTT <K1TTT at arrl.net> wrote:
> Correct, on win7 here it is in
> I added +ws7@@ to mine and restarted so you can see if it shows up here
> David Robbins K1TTT
> e-mail: mailto:k1ttt at arrl.net
> web: http://wiki.k1ttt.net
> AR-Cluster node: 145.69MHz or telnet://k1ttt.net
> -----Original Message-----
> From: Bob Wilson, N6TV [mailto:n6tv at arrl.net]
> Sent: Wednesday, July 18, 2012 22:37
> To: SkimmerTalk Reflector
> Subject: Re: [Skimmertalk] Help--What's Going On?
> On Wed, Jul 18, 2012 at 9:29 AM, David Robbins <k1ttt at verizon.net> wrote:
> > maybe there is something in the call validation logic that is more
> > sensitive to the 2x2 call
> Actually the logic is *insensitive* to WS7*xx* callsigns in particular,
> though this can easily be corrected.
> The callsign recognition algorithm is based on callsign patterns in a file
> named *Patt3Ch.lst*, which on my XP system is found in:
> C:\Documents and Settings\[userid]\Application Data\Afreet\Reference\
> (it will probably be in a different location on a Vista or Windows 7
> maybe under
> Inside that file you can see the problem. Any callsign beginning with WS7
> expected to have just *one* letter after the prefix, not two:
> + WS1@
> + WS7@
> + WS9@
> A plus sign in front of a pattern in the file means that the calls that
> match the pattern are "most likely correct," that is they will be spotted
> faster by the Skimmers.
> Apparently there were too few WS7*xx* callsigns in use at the time that the
> pattern file was created, so it was not included.
> If you feel strongly about this, you try to ask all Skimmer ops to add WS7@
> to the list. :-) Then WS7SX will be spotted by Skimmers.
> Bob, N6TV
More information about the Skimmertalk