[WT-support] Spot bandwidth revisited

[Tõnno Vähk]

I fully agree.

Given the spots are with 100hz it is strange that 200hz is minimum in BandMap properties.

But now that I think about it I am not sure what it means.

If spot of PJ4B is on 1822.2 and SJ2W gets spotted on 1822.3 then will the PJ4B spot be overwritten or not (spot bandwidth is set to minimum of 200Hz)?

If indeed it is overwritten then 100hz should be allowed definitely! I hope this is an easy fix.

And I support the function to disable the spot bandwidth meaning that every spot is listed and only spots on the same call erase old spots on the same call. Can this be done? This is what we really need for CW Multiop!!

tonno

-----Original Message-----
From: support-bounces at win-test.com [mailto:support-bounces at win-test.com] On Behalf Of Mikael Larsmark
Sent: Thursday, October 21, 2010 7:46 PM
To: support at win-test.com
Subject: [WT-support] Spot bandwidth revisited

Hello lads

I know that I have taken this up before and I wish to do it again to 
insure that this is really needed. Right now its possible to edit the 
bandwidth of an spot, it can now be set as low as 200 Hz. This is not 
low enough!

Consider that you are running CQ 160m CW where you have sometimes three 
stations on a single frequency. If PJ4B gets spotted at one frequency 
and right after ES5TV gets spotted 30Hz from that freq the PJ4B spot 
will disappear which can be a big problem. We have noticed this a few 
times in M/S and it is very frustrating knowing that there is a spot to 
work but it went away.

I would like it to be possible to either set the overall spot bandwidth 
to 0 Hz or make it possible to have one bandwidth in the bandmap while 
in the dx announcement window have another, because I realize that for 
example with skimmer the bandmap can be very overpopulated otherwise and 
with skimmer you might want spots to be replaced since there are a lot 
of faulty ones.

So my suggestion is to make it possible to set the spot bandwidth for 
bandmap and for dx announcements and it should be possible to set it to 
0 Hz (disable it).

It would be nice if this was considered a feature for a version released 
before CQWW CW.

PS. This is one of the major reasons some in the SJ2W contest gang want 
us to run N1MM and I don't want to since the crap crashes every now and 
then!

Mike, SM2WMV (SJ2W)
_______________________________________________
Support mailing list
Support at win-test.com
http://www.f5mzn.org/cgi-bin/mailman/listinfo/support