VHFcontesting
[Top] [All Lists]

Re: [VHFcontesting] ARRL/CAC: VHF Contest Proposal(s)

To: Zack Widup <w9sz.zack@gmail.com>
Subject: Re: [VHFcontesting] ARRL/CAC: VHF Contest Proposal(s)
From: Dave <kdcarlso@gmail.com>
Date: Mon, 27 Sep 2021 15:46:41 -0400
List-post: <mailto:vhfcontesting@contesting.com>
Personally I like the idea of three points for analog, one for digital, and
the region one use of six digit grids and a distance multiplier myself.

Dave
N2OA

On Mon, Sep 27, 2021 at 3:08 PM Zack Widup <w9sz.zack@gmail.com> wrote:

> I also have a problem with separate CW and voice QSO's per band. I am
> usually a QRP Portable in ARRL VHF contests. I can very often get through
> on CW but NOT on SSB. That essentially gives me one mode to work with most
> of the time.
>
> 73, Zack W9SZ
>
> On Mon, Sep 27, 2021 at 1:54 PM jimk8mr--- via VHFcontesting <
> vhfcontesting@contesting.com> wrote:
>
> > I will file comments with the CAC, but my suggestion is a variation of
> #3:
> > two contacts per band (analog & digital) but also having two multipliers
> > per grid square per band, i.e. one for analog and one for digital. Keep
> it
> > simpler by having equal QSO point values for digital and analog QSOs,
> while
> > rewarding DX QSOs on analog modes for those people also operating digital
> > modes.
> >
> > I find a problem with having separate CW and Voice QSOs, as I have had
> > many cross mode QSOs over the years. Those would be difficult and/or
> > confusing to score.
> >
> > 73  -  Jim   K8MR
> >
> >
> >
> > -----Original Message-----
> > From: Bob, W3IDT <w3idt@comcast.net>
> >
> > Sent: Mon, Sep 27, 2021 2:05 pm
> > Subject: ARRL/CAC: VHF Contest Proposal(s)
> >
> > All,
> >
> > You are receiving this email via the VHF Contesting Reflector (or PVRC
> > Reflector), or because you received and perhaps commented on my VHF
> > Contest proposal / discussion document of 18 months ago which gathered
> > much interest and email traffic both direct to me and via various
> > reflectors.
> >
> > A "let's wait and see what happens" attitude seemed persuasive at that
> > time. Well, we've waited and we’ve seen: VHF contests have now evolved
> > into mostly 50- and 144-MHz FT8 contests with very little SSB/CW
> > activity nor much activity on the higher bands.
> >
> > The ARRL/Contest Advisory Committee (CAC) is aware of the issues and is
> > considering various options to rejuvenate VHF contests. They are
> > interested in "thoughtful ideas and proposals".
> >
> > Please DO NOT send COMPLAINTS about the loss of the "good old times",
> > and please DO NOT send RANTS about whatever bothers you now about VHF
> > contesting.
> >
> > As stated above, the ARRL/CAC  IS  aware of the issues.
> > They are interested in good and thoughtful ideas.
> >
> > Send any submission to your CAC representative; a listing of CAC members
> > is below the signature block. I would be interested in receiving a copy
> > of any submissions.
> >
> > Attached in PDF format, and in plain text below the CAC members list
> > (losing some bold, italic, and underline formatting), is the proposal I
> > sent to the CAC.
> >
> > The CAC is interested in similar (style, format, tone, etc) ideas,
> > not necessarily the substantive content of my proposal.
> >
> > PLEASE DISTRIBUTE THIS EMAIL WIDELY.
> > The ARRL/CAC will appreciate "thoughtful ideas and proposals".
> >
> > Bob, w3idt
> > 6m op at W3SO, Wopsononock Mountaintop Operators
> > --
> > .......
> > . Robert F. Teitel, W3IDT
> > .
> > . w3idt@comcast.net
> > . w3idt@arrl.net
> >
> > _______________________________________________
> > 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
>
_______________________________________________
VHFcontesting mailing list
VHFcontesting@contesting.com
http://lists.contesting.com/mailman/listinfo/vhfcontesting
<Prev in Thread] Current Thread [Next in Thread>