VHFcontesting
[Top] [All Lists]

Re: [VHFcontesting] Lunch box roving

To: frank bechdoldt <k3uhf@hotmail.com>
Subject: Re: [VHFcontesting] Lunch box roving
From: Steve Clifford <k4gun.r@gmail.com>
Date: Mon, 9 Feb 2009 12:18:59 -0500
List-post: <vhfcontesting@contesting.com">mailto:vhfcontesting@contesting.com>
I agree completely, but would also add a few comments (surprise, right?
LOL).  This practice is no different than what the multi-op contest groups
do.  In a large contest club, its usually a few key guys that buy, maintain,
set up and test all the equipment.  Those guys are really the ones who do
all the heavy lifting.  On contest weekend, the rest of the club shows up to
operate the radios.  Its a remarkable feat.  They do a great job of
coordinating between stations.  They have superior stations, a good plan and
make a lot of noise.

They also have a great time.  There is often a camaraderie that is not known
to single op guys.  Its fun.  Its also a great education for those that are
new to the contesting scene.

There is also nothing at all wrong with it.  The multi-op stations compete
against other multi-op stations.  The rules were well thought out to
segregate multi-ops from single ops.  A single op guy can't make contacts
with a multi-op group if he later operates with that multi-op group.

To me, it just indicates that the rules just need a little more tweaking to
make sure multi-op groups are not put into the same category as lone
rovers.  Let the multi-op grid group have their fun.  I have nothing against
them at all, except that they have exposed a weakness in the current rules.

I have more thoughts on this and I'll share them in due course.  The N6NB
soapbox really made a few things very clear to me and I just need to
organize a few more thoughts on it.

Steve
K4GUN/R

On Mon, Feb 9, 2009 at 12:00 PM, frank bechdoldt <k3uhf@hotmail.com> wrote:

>
>
> What does it accomplish when a bunch of hams borrow one of 8 millionaire's
> lunch box stations and activate the bands by repetitively contacting each
> other?
>
> The ARRL uses contests to create activity to justify the frequency
> allocations we now enjoy.  I would imagine that a group of 8 rovers in 3
> roving categories could generate about 25 percent of the total QSOs of the
> entire QSO count of the whole contest.
>
> If Verizon, AT&T, ect…  knew that the ARRL is using data collected from the
> use of Wayne's lunchboxes to block them from purchasing this spectrum they
> would have a legal field day.
>
> Their posting http://www.arrl.org/contests/soapbox/?con_id=171 proves what
> I have said all along. The only way to fix the roving system is to disallow
> rover to rover contacts unless both rovers are unlimited.  Otherwise Wayne
> is going to keep buying more lunch boxes find more people we have never seen
> in our VHF log books to complete larger teams  and stick his finger in the
> ARRL's and VUAC's eye.
>
> That being said, if this was done only in the unlimited class, it would be
> appropriate and quite remarkable. But I think by buying 8 lunch boxes Wayne
> and handing some of them off to repeater operators is his way of saying the
> current system is broken too.
>
> I only hope that his effort converted some FMer to true weak signal work.
> In fact if he was truly concerned in boosting the activity levels e would
> let those operators mount the equipment at their home QTH's.  Otherwise this
> contest has turned into a function of Wayne's ego.
>
> If I'm wrong, publish the logs.
>
> k3uhf
> _________________________________________________________________
> Windows Live™: E-mail. Chat. Share. Get more ways to connect.
> http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t2_allup_explore_022009
> _______________________________________________
> VHFcontesting mailing list
> VHFcontesting@contesting.com
> http://lists.contesting.com/mailman/listinfo/vhfcontesting
>
_______________________________________________
VHFcontesting mailing list
VHFcontesting@contesting.com
http://lists.contesting.com/mailman/listinfo/vhfcontesting

<Prev in Thread] Current Thread [Next in Thread>