Ooops I meant to send this to group. I see now that you're asking about all beacons, not just the NCDXF Beacons.

To monitor beacon frequencies on 10m, you have to dedicate a 192 kHz receiver slice to 10m CW 28182~28300 and update SkimSrv.ini or SkimSrv2.ini to look like this:

CenterFreqs192=136750,475000,1885000,3585000,5417000,7085000,10185000,14085000,18153000,21085000,24975000,28085000,28255000,50085000,50255000
SegmentSel192=111010000010110

CwSegments=135700-137800,472000-479000,1800000-2000000,3500000-3600000,5330000-5407000,7000000-7125000,10100000-10130000,14000000-14150000,18068000-18115000,21000000-21200000,24890000-24935000,28000000-28300000,50000000-50200000

73,

Bob, N6TV

On Thu, Dec 29, 2022 at 4:04 PM Bob Wilson, N6TV <n6tv@arrl.net> wrote:

Andy,

Since beacon calls are only sent once, they usually won't get spotted unless you list all the NCDXF Beacon callsigns in this text file

%appdata%\Afreet\UserData\Watch.lst

with proper segment coverage.

Details are as explained in these blog posts:

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

73,
Bob, N6TV

On Thu, Dec 29, 2022 at 8:06 AM Andrew O'Brien <andrewobrie@gmail.com> wrote:
I notice that CWS does not decode many of the beacons on 10M despite strong signals . Is this associated with the slow speed of the beacons ? Weak ham signals get decoded amazingly well when in regular ham QSO sections of the band , they are usually sending much faster .

Andy K3UK

_______________________________________________
Skimmertalk mailing list
Skimmertalk@contesting.com
http://lists.contesting.com/mailman/listinfo/skimmertalk