[Moon] ARRL contest and more! cheating

Mon Nov 2 22:33:47 CET 2015

I used to check into the 2m EME Net on 14.345 
when Lionel - VE7BQH ran it and it was mostly 
tech-talk or making future skeds.  I never observed real-time eme assistance.

Like Craig states 20m prop was often not amenable 
for all to hear each other.  It worked well for 
me to check-in due to the 1300 mi distance to 
Lionel. Trying to check-in when Steve-N4PZ tried 
resurrecting the Net was very "iffy" at our distance.

That would not preclude one using HF or VHF for a 
liaison channel for testing or coordination, but 
I never witnessed this. My impression was that 
the eme link was frequently more reliable than a 
coordination channel.  Mw folks use coordination 
by radio at 144 or 432 (even HF) but often the 
prop is worse then the mw circuit.  Heard often 
that they made 10-GHz and then coordinated the coordinating freq link up<smile>

Internet has no prop issue so works very well for 
coordination.  But it is also tempting to use 
improperly for initial contacts.  I see this not 
a functional issue but one of education and discipline. <and enough about that>

73, Ed - KL7UW
Good WE for me even with first night Murphy 
attack: 144 worked 34; 1296 worked 14.  Will do 
better next time now that I am "learning" 1296 
differences.  Promise CW will be used for 1296 
next WE; miss out on too many contacts otherwise.

At 06:54 AM 11/2/2015, craig wrote:
>Well Stephen, â€œsuspectingâ€ how things worked 
>in the old days is NOT the same as actually being there.
>Being on 3 EME bands myself back then; I have a 
>different version (actual) of what you wrongly â€œsuspectâ€.
>
>You see, 20m is not open to the whole world at 
>the same time. Therefore, we had net controls 
>which controlled the conversations and therefore the scheduling.
>Often times, Station A could not chat directly with Station B.
>So the net control coordinated the schedules. 
>This worked quite well; but NOT for chatting 
>about contacts after they happened (or didnâ€™t)
>
>In closing, it was NOT the same thing.
>
>Craig, N8DJB
>
>
>From: <mailto:eme at kc4sw.com>Stephen Hanselman
>Sent: Sunday, November 01, 2015 10:00 PM
>To: <mailto:qstdemb at yahoo.com>R M Barlow
>Cc: <mailto:moon at moonbounce.info>moon at moonbounce.info
>Subject: Re: [Moon] ARRL contest and more! cheating
>
>Ron,
>
>I must be using a different web site.
>
>What I saw was "CQ ###, seq"., "thanks for QSO, here's what I received" etc.
>
>I suspect in the old days it went something like 
>"hey, fill in call here, let's make a schedule 
>on ### at ##:##."  And after the contact I 
>suspect there was a lot of chatting about what 
>happened, went right, and more importantly wrong.
>
>Sounds the same to me
>
>What I really see here is the same rant we beat 
>into the ground 6 months ago.  If you don't like 
>it, change it don't flap your jaws. Put a like 
>minded group together and present a plan, start your own contest, etc.
>
>
>73's
>
>
>
>Stephen Hanselman, KC4SW
>
>Datagate Systems, LLC
>
><x-apple-data-detectors://0/0>3107 North Deer Run Road #24
>
><x-apple-data-detectors://0/0>Carson City, Nevada, 89701
>
><tel:(775)%20882-5117>(775) 882-5117 office
>
><tel:(775)%20720-6020>(775) 720-6020 mobile
>
><mailto:s.hanselman at datagatesystems.com>s.hanselman at datagatesystems.com
>
>www.datagatesystems.com
>
>a Service Disabled, Veteran Owned Small Business
>
>DISCLAIMER:
>This e-mail and any attachments are intended 
>only for use by the addressee(s) named herein 
>and may contain legally privileged and/or 
>proprietary information. If you are not the 
>intended recipient, any dissemination, 
>distribution or copying of this e-mail and any 
>attachments is strictly prohibited. If you have 
>received this e-mail in error, please 
>immediately notify me and permanently delete the 
>original and all copies and printouts of this e-mail and any attachments.
>
>Sent from my iPad
>
>On Nov 1, 2015, at 16:45, R M Barlow 
><<mailto:qstdemb at yahoo.com>qstdemb at yahoo.com> wrote:
>
>>20m was used to make schedules, NOT as a chat 
>>room type forum to exchange signal reports, and "rogers".
>>                                              73 de Ron  n4gjv
>>
>>
>>
>>--------------------------------------------
>>On Sun, 11/1/15, Stephen Hanselman 
>><<mailto:eme at kc4sw.com>eme at kc4sw.com> wrote:
>>
>>Subject: Re: [Moon] ARRL contest and more! cheating
>>To: "Lars Pettersson" <<mailto:sm4ive at telia.com>sm4ive at telia.com>
>>Cc: <mailto:moon at moonbounce.info>moon at moonbounce.info
>>Date: Sunday, November 1, 2015, 7:17 PM
>>
>>From
>>talking to some of the real old time EMEers (mostly SK now)
>>they used 20M to "coordinate" those
>>QSOs.
>>Hmmmm,
>>
>>73's  Stephen Hanselman,
>>KC4SWDatagate
>>Systems, LLC3107 North Deer Run
>>Road #24Carson City, Nevada,
>>89701(775)
>>882-5117 office(775)
>>720-6020 
>><mailto:mobiles.hanselman at datagatesystems.comwww.datagatesystems.coma>mobiles.hanselman at datagatesystems.comwww.datagatesystems.coma 
>>Service Disabled, Veteran Owned
>>Small BusinessDISCLAIMER:This e-mail
>>and any attachments are intended only for use by the
>>addressee(s) named herein and may contain legally privileged
>>and/or proprietary information. If you are not the intended
>>recipient, any dissemination, distribution or copying of
>>this e-mail and any attachments is strictly prohibited. If
>>you have received this e-mail in error, please immediately
>>notify me and permanently delete the original and all copies
>>and printouts of this e-mail and any
>>attachments.
>
>----------
>_______________________________________________
>Moon mailing list
>Moon at moonbounce.info
>http://lists.moonbounce.info/listinfo/moon
>_______________________________________________
>Moon mailing list
>Moon at moonbounce.info
>http://lists.moonbounce.info/listinfo/moon

73, Ed - KL7UW
http://www.kl7uw.com
     "Kits made by KL7UW"
Dubus Mag business:
     dubususa at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.moonbounce.info/pipermail/moon/attachments/20151102/c1e1fb00/attachment-0001.html>