[WT-support] FLAGGING BAND EDGES

[John Warburton G4IRN]

Bob

There is something already in WT that may help you - I use SEGMENT files to indicate band plans. You define your band plan in the segment file and then load it in the Options/Data Files/Segment Files menu. The band plan displays on the band-map. I use this in the RSGB 80m CC contests to remind me of my limits.

Hope that's of help. I don't know if a TX can be disabled through the CAT port or not, to be honest I would rather my radio not be disabled.

John G4IRN.

============================
The RSGB has just announced that as part of the RSGB IOTA contest that if
any one enters and makes QSO?s in segments of the band that have been
identified as part of the rules to NOT be used then points for any contacts
made within these areas will be lost. 
* On a real out of band scenario i.e. 13.999MHZ then the RADIO WILL
NOT TX, as I would expect but there is NO INDICATION on the SCREEN to tell
the operator that he has now gone out of Band. When we used to use NA for
contesting it flagged the operator with a message telling them they were now
out of band.
* CAN THIS OPTION BE ADDED to WIN-TEST?
* Back to areas within the bands that are being identified as
un-usable for the contest. Could this be set ?up within Win-Test to flag the
operator that he has now entered an area that he can?t use for this contest.
For example in the 2007 RSGB IOTA rules stated that the following areas were
not to be used during the contest ? 3560 to 3600MHz, 3650 to 3700MHz , 14060
to 14125MHz and lastly 14300 to 14350MHz. 
* COULD A MESSAGE BE DISPLAYED ON THE SCREEN IDENTIFYING USABLE AREA?
* COULD WIN-TEST DISABLE THE TX IN THESE AREAS?
Personally I think in the future that all contest rules will be stating band
edges for the modes being allowed during the contest so it might help if the
facilities were added now.
Hopefully this can be looked into before the RSGB IOTA contest in July?.
======================

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.f5mzn.org/pipermail/support/attachments/20080107/443ad1ff/attachment.htm