The algorithmfor separating runners from callers is a work in progress.
We're beta-testing a new build now.
Actually, what you're doing is something akin to the original CW
Skimmer, which shows all the signals in its bandpass on the waterfall
and tags any that it sees transmitting "599", so you can tell which
trace is the caller, even if a bunch of yoyos continue calling blindly.
73, Pete N4ZR
Download the new N1MM Logger+ at
<http://N1MM.hamdocs.com>. Check
out the Reverse Beacon Network at
<http://reversebeacon.net>, now
spotting RTTY activity worldwide.
For spots, please use your favorite
"retail" DX cluster.
On 4/16/2016 8:58 AM, Don Hill AA5AU 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
|