[Skimmertalk] Please update Watch.lst to spot new NCDXF beacon KH6RS, replacing KH6WO

[David Robbins]

that page that shows frequency range gets easily confused.  I have 2 different skimmers running, one for cw that starts at the bottom of the band and the other for rtty that starts at the higher frequency.  depending on the reporting interval you may see one or the other or some weird mix in that page.

I did search for some of the beacons and it seems that I am reporting them, just not very often.  I see my node spotting the LU beacon, but so far none of the others I have searched for.  it seems that some of the beacons in that list are rarely spotted if at all, so maybe its just a timing thing and I haven't been watching when it heard any of them.


Jan 19, 2016 02:08:47 PM, n6tv at arrl.net wrote:


On Mon, Jan 18, 2016 at 2:40 PM, David Robbins <k1ttt at arrl.net> wrote: 
Hmmm, running skimmer server here, added that list to watch.lst, but not
seeing any beacon spots from my skimmer.  What other settings could stop
them from being spotted??

In the "Telnet" tab of SkimSrv, disable "Post only CQ Spots" and select Normal validation.

Adjust the segments to cover the Skimmer frequencies as described at the bottom of my original post, quoted below.

According to the RBN, the K1TTT skimmer is only covering:



14060~14150

18100~18110

21060~21150

24910~24930

28060~28150


So only the NCDXF 14.100 MHz beacon is in the middle of the covered ranges.

Finally, note that the Aggregator program has a hard-coded list of NCDXF beacons, so the new KH6RS beacon won't show up in the RBN logs until W3OA returns from K5P and updates the Aggregator.


If necessary, adjust the CWSegments in your SkimSrv.ini file to include the
beacon frequencies (14.100, 18.110, 21.150, 24.930, and 28.200).

Details are outlined in two RBN blog posts by N4ZR, here:

http://reversebeacon.blogspot.com/search?q=ncdxf

Look for the .ini files here:

%appdata%\Afreet\Products\SkimSrv\SkimSrv.ini


73,
Bob, N6TV