[WT-support] Disappearing Multipliers

Olof Lundberg olof at rowanhouse.com
Wed Nov 28 12:04:28 CET 2012


Firstly, as Bob suggested, limit (=filter) incoming spots to skimmers
relevant to your region. Secondly, in bandmap properties, set CW bandwidth
to 0 Hz.This would minimize the problem but there is still an issue.

What is needed is some more intelligence in the software: you would as an
option like the bandmap to show the "frequency owner" only, the station who
is running on the frequency. This can be done by retaining the recent spot
history on that frequency and disregard spurious entries thus showing who
has been "dominating" the frequency for the last [20?] minutes.

It is very important that this kind of filtering is not built into skimmers
and RBN - we want RBN to produce as many spots as possible because there
are so many other uses for those spots. This extra optional filtering
should be built either into the WinTest Bandmap or be added as an optional
functionality in the WtDXTelnet client.

73 Olof G0CKV - M5E




On 28 November 2012 05:41, Bob Wilson, N6TV <n6tv at arrl.net> wrote:

> First, as OH6XX mentioned, make sure the spots bandwidth in the Bandmap
> Properties is set to the minimum value (100 Hz).
>
> One issue that can happen if you display all skimmers from all over the
> world with no filtering by location is that two guys can be CQing on the
> same frequency at the same time, totally unaware of each other.  The ZL2HAM
> skimmer may spot a local DX station on 21026.2 at the same time that the
> W3LPL skimmer spots a completely different DX station on 21026.2.  It's
> "last one wins" as far as the band map goes.
>
> In other cases it's a busted skimmer spot like EW3LPL that quickly gets
> spotted correctly as W3LPL by other skimmers.  If you're using the "List"
> view, and select the "Hide dupes and invalids" option, or "Multipliers
> only," the spot will disappear from the list view when it is corrected.
>
> I'm not sure how Win-Test defines "Invalid" -- maybe it uses the callsign
> pattern checking algorithm?
>
> Another issue is that sometimes Skimmer gets fooled and incorrectly spots
> a DX station's callsign if he sends it twice, even if he is just doing S&P.
>
> Having said all that, I'm working on new LUA script that will read the
> bottom of the .dxc file that is saved when Incoming Spots Logging is
> enabled, and display the contents in a pop-up window.  But I'm not really
> sure if that script will help or not, or if enabling spot logging is really
> a good idea.
>
> Let me know if you'd like to beta test it.
>
> 73,
> Bob, N6TV
>
> On Tue, Nov 27, 2012 at 8:39 PM, Kevin Stockton <n5dx2005 at yahoo.com>wrote:
>
>> We ran Win-Test for the first time in the CQWW CW contest this last
>> weekend at K5GO.  During the contest we noticed many spots that would
>> appear in the list and bandmap for a brief second and then disappear, never
>> to be found again.  Can anyone guide me to diagnosing the problem?  The
>> spots were always from an incoming packet or skimmer spot.  The packet spot
>> time out was set on 30 minutes on each computer on the network.  It
>> appeared to be a random event.  Some spots would stay for the full 30
>> minutes, or until we worked them.  Others would appear for a few seconds or
>> minutes and then disappear.
>>
>> Any help would be appreciated.
>>
>> Thanks,
>> Kevin, N5DX
>>
>>
>> _______________________________________________
>> Support mailing list
>> support at win-test.com
>> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>>
>>
>
> _______________________________________________
> Support mailing list
> support at win-test.com
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20121128/a85cea15/attachment.html>


More information about the Support mailing list