Well there are (at least) two things causing this.
1. The Rtty skimmer seems to work better when set to aggressive. Not all sysops
have
gone to this setting as it is different from what was originally recommended.
You also
can not tell what the rtty setting is from the information shown on the
reversebeacon
website as only the CW skimmer setting is shown. Setting to aggressive really
helps,
please help get the word out.
2. Finding the right decode scheme for rtty just seems to be hard. VE3NEA has
been working
on an improved scheme which continues to evolve as it is being tested.
Mark. N2QT
> On Apr 16, 2016, at 8:58 AM, Don Hill AA5AU <aa5au@bellsouth.net> wrote:
>
> Last night in the EP2A pileup, I was using WriteLog with a bandmap and
> connected to a Packetcluster node with RTTY skimmer spots enabled.
>
> Some skimmers were showing all the callers up above EP2A. I'm not sure why
> this happens (?????) but I was able to find where the DX was listening by
> looking at the call he was working, then clicking on that call on the
> bandmap, which had been skimmer-spotted, and it put my VFO right on the
> caller's frequency. It was pretty slick. It didn't help me make the contact
> but it was interesting to use it that way.
>
> I wonder how all the calls are being spotted without CQ or QRZ or anything
> else other than their callsign being sent. Why does this happen?
>
> Don AA5AU
>
> _______________________________________________
> RTTY mailing list
> RTTY@contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
|