CQ-Contest
[Top] [All Lists]

Gate 2 at LAST!!

Subject: Gate 2 at LAST!!
From: tad.danley@mail.nextel.com (tad.danley@mail.nextel.com)
Date: Thu Aug 22 12:44:47 1996
     As usual, Ed, K4SB (and Shadow!) are correct!
     
     Per the August 22 issue of the FCC Daily Digest, the Amateur Station 
     Vanity Call Sign System Filing Gate 2 opens September 23, 1996.
     
     This FCC Public Notice contains the following interesting tidbit:
     NOTE: A separate Public Notice will be released providing guidelines 
     for the implementation of electronic filing procedures for FCC Form 
     610-V.
     
     LET THE GAMES BEGIN!
     
     These announcements normally show up on the FCC web page the day after 
     they are released, so you should be able to access a copy of this 
     Public Notice by that means on Friday.
     
     73, 
     Tad Danley, NZ3I (for now!)
     


>From jvl@rfpo1.rfc.comm.harris.com (Lundberg, John V)  Fri Aug 23 11:27:00 1996
From: jvl@rfpo1.rfc.comm.harris.com (Lundberg, John V) (Lundberg, John V)
Subject: No subject
Message-ID: <321DBF37@smtpgate.rfc.comm.harris.com>


set nomail
quit

>From floydjr@Interpath.com (Jimmy R. Floyd)  Fri Aug 23 13:06:08 1996
From: floydjr@Interpath.com (Jimmy R. Floyd) (Jimmy R. Floyd)
Subject: NAQP SSB 96 Scores IV
Message-ID: <2.2.16.19960823120608.356f842a@interpath.com>

NAQP 96 SSB 
Raw Scores


Compiled by
>> WA4ZXA <<
floydjr@interpath.com

Date posted: 08/23/96


CALL                   SCORE       QSO'S      MULTI
------------------------------------------------------------

SINGLE OPERATOR

N4ZZ                 244,404       1116        219
NM5M                 194,135        947        205
K0EJ                 184,625        875        211
AA8AV                184,080        885        208
KF3P                 159,964        812        197
AC10                 150,002        838        179
NA5Q                 143,592        772        186
AA0SQ                125,388        774        162
KA4RRU               123,714        711        174
N4BP                 119,250        750        159
AB5SE                111,931        647        173
AA0OB                110,840        652        170
KE2VB                105,270        605        174
N5FG  (WQ5L)         103,887        679        153
WA8YRS               103,572        548        189
KQ4HC                 99,968        568        176
W7ZRC                 98,552        776        127
WA7BNM                95,776        656        146
KB3AFT                94,114        544        173
K9BG                  93,225        565        165
KJ6HO                 92,796        703        132
N6HC                  92,400        700        132
WB5B                  91,676        559        162
WA6KUI                87,584        544        161
KR4UJ                 86,289        587        147
N6KI                  80,470        619        130
N1PBT                 77,770        505        154
K0WA                  77,655        501        155
K3II  (WB3ESS)        77,520        570        136
KN6DV                 76,956        636        121
W5ASP                 71,736        488        147
AB6FO                 67,298        506        133
KR4DL                 62,205        429        145
AA4UF                 61,962        449        138
N9ITX/7               60,298        511        118
K7C  (KG7TE)          60,000        455        132
KD3GC                 57,323        431        133
WQ5G                  55,440        419        131
WB0OLA                52,785        391        135
K9WIE                 52,326        342        153
N3BDA                 49,440        412        120
KD4HA                 46,854        342        137
VE7CFD                38,720        440         88
AE4EY                 32,336        344         94
WA4ZXA                30,492        363         84
N3ADL  (N3UHZ)        28,086        253        111
W1IHN                 26,800        268        100
WD0T                  25,935        273         95
KS4XG                 25,875        225        115
N4VHK                 22,736        203        112
AE0M                  18,300        245         75
VE6JY                 14,430        185         78
KM9P                   4,061        131         31
KB9NMU                 1,058         46         23
WN3K                     221         17         13


MULIT-OP

NC0P                 421,022       1769        238 
WB5VZL               331,559       1423        233 
W5NN                 308,958       1326        233
KC4ZV                140,097        697        201
AC4ZO                 54,740        391        140
W5EHM                 47,151        403        117


TEAM SCORES

SCCC#1                             425,226


OPERATORS IN MULIT-OP

NC0P           NC0P,WD0GVY,WA0ETC,WA0FLS,WO0V
W5EHM          N1PVB,SQ9DDZ,KA5WSS
AC4ZO          AC4ZO,AD4ZE,KE4DRJ,KE4OQO,KF4EAH,KF4BKM,N4YTO,KT4OC
WB5VZL         AA5RB,WB5VZL
W5NN           K5GA,N5RP,KB5YVT

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PLEASE DO NOT SEND ANY SCORES TO THE CONTEST REFLECTOR FOR ANY CONTEST!!
SEND THEM TO ME DIRECT OR TO THE 3830 REFLECTOR. 

PLEASE NO ATTACHED FILES!!! ALSO NO LOGS AS THESE ARE NOT OFFICIAL
SCORES!! 

YOUR OFFICIAL LOGS GO TO WHERE EVER THE SPONSOR OF THE CONTEST SAYS THEY
DO. I HAVE NOTHING TO DO WITH THE CONTEST EXCEPT TO PARTICIPATE AND DO
THESE SCORES FOR EVERYONE ON INTERNET. CHECK YOUR RULES FOR THE CONTEST
FOR THAT INFORMATION.

73's Jim
           ********************************************************** 
           * Jimmy R. Floyd  (Jim)   Thomasville, NC                *
           *                                                        *
           * Amateur Call:              >> WA4ZXA <<                *
           * Packet Node:               >> N4ZC <<                  *
           * Internet Address:          >> floydjr@interpath.com << *
           **********************************************************


>From floydjr@Interpath.com (Jimmy R. Floyd)  Fri Aug 23 13:06:11 1996
From: floydjr@Interpath.com (Jimmy R. Floyd) (Jimmy R. Floyd)
Subject: SARTG RTTY 96 Scores IV
Message-ID: <2.2.16.19960823120611.356f898e@interpath.com>

SARTG 96 RTTY
RAW SCORES

Compiled by
>>WA4ZXA<<
floydjr@interpath.com


Date Posted: 08/23/96


CALL                   SCORES       QSO'S      PTS     DIST     DX
------------------------------------------------------------------------


SINGLE OP/ALL BAND

9H0A                1,589,180        779      8780          181
SM3KOR              1,302,225        659      7275      28      151
YL2KF               1,169,520        624      6645      30      146
OH2BP               1,066,725        583      6495      26      139
SM5FUG              1,059,520        563      6160      27      145
OH2GI                 850,680        501      5560      21      132
PA3ERC                726,440        434      5080      26      117
OH2LU                 570,240        411      4455      18      110
SM3BJV                569,420        375      4010      17      125
IK7APK  (IK0HBN)      478,020        366      3855      23      101
SM3LBN                289,945        252      2815     103       87
IK0CHU                224,020        240      2435       9       83
SM5EIT                185,500        207
G3YJQ                 124,605        164      1755      11       60
E8SFG                  83,490        127      1815      13       33

AB5KD               1,039,700        663      7025          148
NO2T                  736,440        458      5415      47       89
N1RCT                 693,750        482      5550      49       76
KQ4GC                 547,995        409      4605      57       62
NF6L                  520,840        414      4490      66       50
WA4VQD                417,450        353      3795      49       61
WA6VZI                355,000        321      3550      53       47
WA0ACI                229,900        292      3025      42       34
N6GG                  215,275        250      2725           79
KE1FO                 212,000        224      2650      29       51
WA4ZXA                181,335        215      2355      33       44
KE7GH                 178,640        314      3190      34       22
NA2M                  155,520        202      2160      34       38
KA2CYN                155,420        177      2045      35       41
KD8FS                 152,130        217      2305      36       30
KC4HW                 137,280        189      2080      34       32
K0RC                  111,910        183      1805      38       24
AA9RR                 111,825        163      1775      39       24
W6/G0AZT              108,160        159      1690      36       28
K0BX                  101,500        159      1750      28       30
KF3P                   83,260        152      1810      17       29
K8UNP                  76,950        123      1425      21       33
W7RSJ                  66,005        152      1535      24       19
VE7QO                  65,095        126      1385      25       22
N2CQ                   56,240
AC6DR                  52,750        111      1055      33       17
W2JGR/0                52,080        107      1085      29       19
NS1Z                   46,320         83       965      26       22
KC4ZHQ                 46,295         97       985      27       20
KA1IXG                  9,430         38       410      14        9


SINGLE OP/SINGLE BAND

40M
PJ8MI                  88,440        137      2010      14       13
PA3EWP                 47,730        122      1290       6       31

W2UP                  108,100        192      2300      15       32
KF3P                   83,260        152      1810      17       29
KF4BU                  41,700        143      1390      14       16

20M
SM5AAY                 84,870        168      1845      14       32

WF1B                  280,840        333      4130      16       52
WA4JQS                110,414        190      2165      17       34
N2CQ                   48,960        


MULTI SINGLE

PI4CC                 823,200        489      5600      32      115

AA5AU                 775,520        462      5240      73       75
AF4Z                  362,780        337      3740      41       56
VE6KRR                311,055        329      3575      46       41
VE3FJB                244,900        262      3100      31       48

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PLEASE DO NOT SEND ANY SCORES FOR ANY CONTEST TO THE CONTEST REFLECTOR!!
SEND THE RTTY SCORES TO WF1B REFLECTOR OR TO ME DIRECT!!!

Please no attached files or logs!! Also remember these scores are not 
official!!!

73's Jim
           ********************************************************** 
           * Jimmy R. Floyd  (Jim)   Thomasville, NC                *
           *                                                        *
           * Amateur Call:              >> WA4ZXA <<                *
           * Packet Node:               >> N4ZC <<                  *
           * Internet Address:          >> floydjr@interpath.com << *
           **********************************************************


>From k5na@bga.com (Richard L. King)  Fri Aug 23 16:41:30 1996
From: k5na@bga.com (Richard L. King) (Richard L. King)
Subject: New 160 meter contest rules
Message-ID: <199608231541.KAA17204@zoom.bga.com>

First off, thanks to Tree and Bill for putting this together. We applaud
your effort. Now to my comments.
 *****************************************************************************

>                               RULES (draft)
>                        STU PERRY DISTANCE CHALLENGE
>
>1. Contest period:  1500Z December 28th to 1500Z December 29th, 1996.
>   Operate for a maximum of 14 hours with one time off period.

START/STOP TIME - Isn't the west coast sunrise a little after 15Z that time
of year. Wouldn't it be better to start it at 16Z or later when the sunrise
is over open water? It would be a shame to start and stop the contest with
the sunrise occuring at a peak population area.

DURATION - On December 29, 1996 I have about 13 hours and 50 minutes of
darkness. Since the sunset peak and sunrise peaks can last for 15 minutes
before and after darkness (in some cases much longer), I need about 14 hours
and 20 minutes to work the entire contest for the entire night. I personally
would have liked to see the operating at least an hour longer. I ran a check
on San Francisco and found they will have about 14 hours and 15 minutes of
darkness and with the add-ons, they will have 14 hours and 45 minutes of
good operating time.

Other parts of the world (that I checked) varied from EI (Ireland - 16 hours
and 34 minutes of darkness) to VK6 (Perth - 9 hours and 48 minutes of
darkness). Was there any specific reason for choosing the 14 hours of
operating time?

TIME OFF - If it is daylight before and after the contest for me and if I
take those times off, does that count as two off times? They probably don't
count, but it would be better to make that point clear. Do you specifically
mean one off period during the nighttime operating time?

For some who have more than 14 hours of darkness, how do you stop them from
taking a retroactive break of non-productive operating time in order to
extend their operating time to their sunrise? I guess this would be called
"rubber breaking". 

>2. Bands and mode: 160 meters CW only.
>
>3. Categories: Single operator or multi-operator. Only one signal may
>be transmitted at a time.  Packet spotting may not be used (W1BB didn't
>use packet).  Transmitting and receiving antennas must be located at
>the same QTH.

I find the computer log requirement and the exclusion of packet to be
contradictory. To the best of my knowledge W1BB did not use computer logging.

>3. Exchange: RST and four digit grid square (ie: CN85).  Participants 
>are encouraged to send real signal reports instead of the same report
>for each contact.  Those who send the same RST for each QSO will be suitably 
>embarrassed when they see the results.

Since my software doesn't support sending variable RSTs, how embarrassed am
I going to be for sending 5NN the entire contest. Many of us feel we don't
have a choice. What if I sent 579? Would I be less embassased?

>4. QSO Points: The number of QSO points for each contact depends on the
>distance between the two stations.  This is computed by taking the distance
>between the centers of the two grid squares.  Count a minimum of one point
>per QSO and an additional point for every 500 kilometers distance.  For 
>example, a QSO with a station 1750 kilometers away will count for 4 QSO 
>points.  No additional distance for long path is allowed.
>
>If you are unable to obtain the grid square of a station during the contest,
>you must still obtain the RST and count the QSO for only one point.  You 
>are not permitted to determine the grid square in any method other than 
>receiving it from the station.

How do you handle this situation. I am S&Ping and work LU1DEN. He doesn't
give me a grid square. So I log him with only the RST. Later I tune across
him and he is now giving his grid square. Someone obviously explained the
exchange to him since I worked him. Do I go back and enter his grid square
in my log or do I enter the fray to work him again? 

If I work him the second time and the second QSO is a dupe, will your log
checking software give QSO points only for the first QSO and distance points
only for the second QSO?

>5. Score: Final score equals the total number of QSO points.  There is 
>no mutliplier for different grids worked.  Stations running 5 to 100 watts
>output may multipliy their score by 2.  Stations running less than 5 watts 
>multiply their score by 4.  Separate score listing for single ops and
>multi-single.  Please NO PACKET.
>
>6. Awards: TBD.  We are working on tee shirts and other awards.
>
>7. Reporting: You log can be sent via the internet to TBDC@CONTESTING.COM 
>or via diskette to KM9P.  Logs should be in ASCII format.
>
>Logs will be checked using computer techinques to detect busted callsigns 
>and not-in-log QSOs.  CT, NA and TR software will support this contest 
>complete with QSO point calculation.  Busted QSOs will be removed from 
>both logs. Unique percentages will be reported in the results.

Since you wont be accepting paper logs, then many of the 160M DX stations
worked will not be submitting a log because they don't use computers. This
will diminish the effectivness of your fancy computer techniques to check
the logs. Perhaps if enough volunteers were found to enter the paper logs,
we could include them. I would be willing to enter one or two fair-sized DX
logs into ASCII format.

Otherwise, the winner of this contest (activity, QSO party, whatever) could
be an operator who works a lot of non-cross-checked DX QSOs. I am not saying
the winner will be doing something wrong. Just that his log might be the
hardest to verify. 

73, Richard
K5NA@BGA.COM
http://www.realtime.net/~k5na


>From tree@lady.axian.com (Larry Tyree)  Fri Aug 23 17:38:00 1996
From: tree@lady.axian.com (Larry Tyree) (Larry Tyree)
Subject: 160 rules
Message-ID: <199608231638.JAA19613@lady.axian.com>

> First off, thanks to Tree and Bill for putting this together. We applaud
> your effort. Now to my comments.

Thanks.

> >                        STU PERRY DISTANCE CHALLENGE

We have found it that W1BB's name was Stew.

> >
> >1. Contest period:  1500Z December 28th to 1500Z December 29th, 1996.
> >   Operate for a maximum of 14 hours with one time off period.
>
> START/STOP TIME - Isn't the west coast sunrise a little after 15Z that time
> of year. Wouldn't it be better to start it at 16Z or later when the sunrise
> is over open water? It would be a shame to start and stop the contest with
> the sunrise occuring at a peak population area.

I don't see that as a problem.  So we get to have an early lead by working 
one JA.  The band is pretty much gone by 1500.

> DURATION - On December 29, 1996 I have about 13 hours and 50 minutes of
> darkness. Since the sunset peak and sunrise peaks can last for 15 minutes
> before and after darkness (in some cases much longer), I need about 14 hours
> and 20 minutes to work the entire contest for the entire night. I personally
> would have liked to see the operating at least an hour longer. I ran a check
> on San Francisco and found they will have about 14 hours and 15 minutes of
> darkness and with the add-ons, they will have 14 hours and 45 minutes of
> good operating time.

The goal here was to do some equalizing compared to those who are closer
to the equator than you are.

> Other parts of the world (that I checked) varied from EI (Ireland - 16 hours
> and 34 minutes of darkness) to VK6 (Perth - 9 hours and 48 minutes of
> darkness). Was there any specific reason for choosing the 14 hours of
> operating time?

It just felt right.  12 seemed kinda harsh, 16 was too long.

> TIME OFF - If it is daylight before and after the contest for me and if I
> take those times off, does that count as two off times? They probably don't
> count, but it would be better to make that point clear. Do you specifically
> mean one off period during the nighttime operating time?

The time off wording is very difficult!  Can some lawyer out there help 
me with it?  Simple put off/on/off is okay, on/off/on is okay and I
think we don't want on/off/on/off or off/on/off/on.  Does that make
sense?

> For some who have more than 14 hours of darkness, how do you stop them from
> taking a retroactive break of non-productive operating time in order to
> extend their operating time to their sunrise? I guess this would be called
> "rubber breaking". 

I don't think this is really possible with the limited number of breaks.

> I find the computer log requirement and the exclusion of packet to be
> contradictory. To the best of my knowledge W1BB did not use computer logging.

Computer logging is just easier for most everyone.  We will accept paper
logs, but they will be indicated as not checked in the results.  PACKET
is not appropriate for this type of contest.  Hopefully I don't have to
say more than that.  I would rather everyone find the QSOs themselves,
even the multi-ops.  It helps eliminate endless CQing.

> >3. Exchange: RST and four digit grid square (ie: CN85).  Participants 
> >are encouraged to send real signal reports instead of the same report
> >for each contact.  Those who send the same RST for each QSO will be suitably 
> >embarrassed when they see the results.
>
> Since my software doesn't support sending variable RSTs, how embarrassed am
> I going to be for sending 5NN the entire contest. Many of us feel we don't
> have a choice. What if I sent 579? Would I be less embassased?

I don't think software should control how we operate contests!!!!!!  It
is a reasonable request to ask for actual signal reports.  This can
be done with CT, NA and TR.  I understand it isn't EASY with CT or NA,
but it can be done.  Call up K1EA or K8CC and let them know you want this
feature.  This is plenty of time for them to respond.

We are going to do a histogram on your RST sent.  Anyone sending the
same report more than 50 percent of the time is fair game for whatever
the log checkers want to do.

> >4. QSO Points: The number of QSO points for each contact depends on the
> >distance between the two stations.  This is computed by taking the distance
> >between the centers of the two grid squares.  Count a minimum of one point
> >per QSO and an additional point for every 500 kilometers distance.  For 
> >example, a QSO with a station 1750 kilometers away will count for 4 QSO 
> >points.  No additional distance for long path is allowed.
> >
> >If you are unable to obtain the grid square of a station during the contest,
> >you must still obtain the RST and count the QSO for only one point.  You 
> >are not permitted to determine the grid square in any method other than 
> >receiving it from the station.
>
> How do you handle this situation. I am S&Ping and work LU1DEN. He doesn't
> give me a grid square. So I log him with only the RST. Later I tune across
> him and he is now giving his grid square. Someone obviously explained the
> exchange to him since I worked him. Do I go back and enter his grid square
> in my log or do I enter the fray to work him again? 

I don't know...  you are almost getting too serious for this contest.
Do what your conscience tells you to do.

> If I work him the second time and the second QSO is a dupe, will your log
> checking software give QSO points only for the first QSO and distance points
> only for the second QSO?

I don't know - we haven't written it yet.

> Since you wont be accepting paper logs, then many of the 160M DX stations
> worked will not be submitting a log because they don't use computers. This
> will diminish the effectivness of your fancy computer techniques to check
> the logs. Perhaps if enough volunteers were found to enter the paper logs,
> we could include them. I would be willing to enter one or two fair-sized DX
> logs into ASCII format.

Great!  We can use help like that.  

> Otherwise, the winner of this contest (activity, QSO party, whatever) could
> be an operator who works a lot of non-cross-checked DX QSOs. I am not saying
> the winner will be doing something wrong. Just that his log might be the
> hardest to verify. 

Well, maybe - but typically contests are won by people with the best 
looking logs from a unique percentage viewpoint.  I have no idea who
will have the advantage in this contest and it will be very interesting
to see who it will be.  Is 100 watts from TI1C the ticket?

Tree N6TR
tree@contesting.com

>From tree@lady.axian.com (Larry Tyree)  Fri Aug 23 17:40:08 1996
From: tree@lady.axian.com (Larry Tyree) (Larry Tyree)
Subject: Real RSTs
Message-ID: <199608231640.JAA19628@lady.axian.com>


And this just in from WW6D:

> Just a quick note -- I have NA version 9.2x something and it allows
> "real" RST's.

So, are we going to make contest rules comply to the limitations of
one of the three most used logging programs?

Tree N6TR
tree@contesting.com

>From davep@mylexboulder.com (David Palmer)  Fri Aug 23 17:41:08 1996
From: davep@mylexboulder.com (David Palmer) (David Palmer)
Subject: 40/80 Phased verticals
Message-ID: <321DDF24.3E7B@mylexboulder.com>

Don, WA8YRS writes:

> ... It would be nice to keep the HF2V,  add another
> and have a 2 element phased array on 80/40.  [...]
> I could easily feed this
> multiband system in phase just by cutting the coax to equal lengths...

Don, you might call the Butternut Company (don't have their 
phone number handy, but check any recent ham mag) and ask for 
their free Technical Note 100 (T-100).  This is just a one sheet of 
some notes on this subject on this very topic.  Also see the 
Low Band DXing book by ON4UN and the recent ARRL Antenna Book.

I have an HF6VX in the back yard which has been begging me to 
install another and phase the two...  I was figuring on just feeding
them either in phase, or relay selecting a delay line. Naturally 
this single delay line would cause different patterns for 40 vs. 80, 
but you could select the line length to be a compromise which would
do something useful for either case. The ARRL Antenna Book has two
pages of graphs of vertical spacings and phase delays.  

Your 180 degree delay line on 40 becomes about 90 degrees on 80...  
Your 3/4 wave spacing on 40 becomes 3/8 wave spacing on 80...

I think feeding in phase should work easily and result in some gain.
When attempting to add phase delays, someone can correct me if 
I'm wrong, but my sense is that if you don't get perfect phasing, 
your front-back ratios suffer but you still get some useful forward
gain (well going forward in *some* direction...).  From a domestic
contesting standpoint, from here in the middle of the USA, I don't see as 
I care much about front-back-side...that helps my signal get weaker
somewhere...I need to be LOUDER somewhere (anywhere really)...
hence if I can get some forward gain then it's a win.  Thus I'm 
inclined to try it and see what happens. Let me know what you decide
on doing.

Last November I tried using the "tuned guy" approach to add some
directivity to my HF6VX per some articles in the ARRL Antenna Compendium.
The article assumed you'd be using a tower as your vertical, and 
you tune a grounded guy to form a reflector.  I tied a #14 wire 
to a grounded loading coil and then to the top of the HF6VX in some 40 meter 
experiments.  I could switch the "guy" to ground from the shack via 
12VDC relay.   I didn't have time to run extensive tests, but never 
noticed any significant nulls or gains on receive.  Wonder if anyone
has successfully used the tuned guy approach on a non-tower installation.

Regarding the visual impacts... you could do what I do and get 
something like the Lance Johnson Engineering GP-1 radial bus:
you can then tie all your radials to the GP-1, and then the HFnV
attaches to the GP-1 with just 3 screws.  My HF6VX is only up when
I am going to be operating...takes about 3 minutes to plop it into
the GP-1 and install...the buried radials and coax are always 
installed and ready.  This scheme saves on CC&R problems, lightning 
problems, etc.  When I get the second vertical, I'll call the 
system the "stealth phased array antenna system".   Sounds like 
a DoD project, eh?  

For more info on the GP-1 see: http://www.QTH.com/lowband
 
Anyhow, have fun!  
73, 
Dave Palmer, N6KL/0
Boulder * Niwot * Longmont Colorado

* I'd rather be surfing the ionosphere! *

>From k5na@bga.com (Richard L. King)  Fri Aug 23 17:51:04 1996
From: k5na@bga.com (Richard L. King) (Richard L. King)
Subject: 160 rules
Message-ID: <199608231651.LAA28060@zoom.bga.com>


>> TIME OFF - If it is daylight before and after the contest for me and if I
>> take those times off, does that count as two off times? They probably don't
>> count, but it would be better to make that point clear. Do you specifically
>> mean one off period during the nighttime operating time?
>
>The time off wording is very difficult!  Can some lawyer out there help 
>me with it?  Simple put off/on/off is okay, on/off/on is okay and I
>think we don't want on/off/on/off or off/on/off/on.  Does that make
>sense?

You don't need a lawyer to word this. Change the rule to say that one off
period will be allowed between the first and last QSO of the contest. You
HAVE to have the rules allow the operator to work both his sunrise and
sunset. Other wording would prevent this.

>> For some who have more than 14 hours of darkness, how do you stop them from
>> taking a retroactive break of non-productive operating time in order to
>> extend their operating time to their sunrise? I guess this would be called
>> "rubber breaking". 
>
>I don't think this is really possible with the limited number of breaks.

You said breaks (plural)? I thought only one break was allowed. With one
break, my question stands.

73, Richard
K5NA@BGA.COM
http://www.realtime.net/~k5na


>From David_B_Curtis@ccm.sc.intel.com (David B Curtis)  Fri Aug 23 18:04:00 1996
From: David_B_Curtis@ccm.sc.intel.com (David B Curtis) (David B Curtis)
Subject: How to find out your gird square simply...
Message-ID: <Fri, 23 Aug 96 10:19:05 PDT_4@ccm.hf.intel.com>

Simple... ask a local VHF contester.  He'll know.  Just call CQ on 
50.125, CW if you like, or 1296.1 works too... :-)

You guys are making this *far* harder than it needs to be.  Cripes, try 
*roving* sometime if you want practice figuring out your grid square. 
Unless you are near a grid boundary, the ARRL grid map is all you need, 
grids are 60 nautical miles tall, for heavens sake, and quite a bit 
wider. (I mean, really, can you guys find your QRP equipment without a 
flashlight? :-) For more detail, I usually use the DeLorme atlases... 
they have maybe 1/3 of the states covered now.  They are coarse topo 
maps, about 30 minutes tall per tabloid size page.  Very nice.  (I'm not 
associated with DeLorme, etc)

Here's an offer: Any one in California, Oregon, or Washington that is in 
doubt about their grid square, send me e-mail and I'll look it up for 
you.  (That is if you can't get on 1296.1 .... :-)

73, Dave NG0X CM87xi
              ^^^^^^ when I'm not roving

david_b_curtis@ccm.sc.intel.com

<Prev in Thread] Current Thread [Next in Thread>
  • Gate 2 at LAST!!, k4sb@avana.net
    • Gate 2 at LAST!!, tad.danley@mail.nextel.com <=