[amsat-bb] Poor Operators

Tue Apr 7 16:21:52 UTC 2020

I agree that "never" is too strong.  I've used this example before, but--a
few years ago, I set up a sched with a friend in Ontario to talk briefly
with my grandson so the grandson could have a chance to do a satellite and
get a QSL card and maybe plant a seed of interest in amateur radio.  It all
came off, they spent maybe 30 sec talking, and then we signed off and
thanked everyone for making a 8-year-old's day.  Those who were waiting
were kind and considerate.  I would not do that if there was a rover on, of
course, but once in a while, I think it is fair to make an exception for a
kid, a class, a demo, etc.

On Mon, Apr 6, 2020 at 11:13 PM Chris Hoffman, KG6O via AMSAT-BB <
amsat-bb at amsat.org> wrote:

> I agree ‘Never’ is incredibly strong. Perhaps ‘...should be avoided if at
> all possible...’?
>
> In my opinion, the problem is not QRM or congestion. The problem is
> welcomeness.
>
> The problem is that new operators continually hear banter and “... it’s a
> nice morning here, Bob...” then when they try to squeeze in a contact
> —after the conversation is over— they are instead crushed by other
> operators also trying to respect boundaries on an 8min pass.
>
> The problem is that new operators have told me they perceive what are
> obviously repeated contacts as an expression of territory, and they put
> down the antenna for good.
>
> The problem is the assumption that it’s ‘...NOT a busy pass.’ That very
> idea serves to disenfranchise, devalue, and repel new operators, making it
> a self-fulfilling prophecy. Save Repeated Contacts —short or long— for
> EMail or HF: it should ALWAYS be considered to be a ‘busy pass‘ until we
> have available passes every 5 minutes.
>
> I challenge the experienced ‘regular’ operators to stay off the PTT,
> listen for the new contacts that will inevitably show up,  and remember
> that —in the aggregate— any open transponder time is an invitation for new
> operators.
>
> /CH
> KG6O
> kg6o at arrl.net
>
> > On Mar 24, 2020, at 19:06, Bob Liddy (K8BL) via AMSAT-BB <
> amsat-bb at amsat.org> wrote:
> >
> >  It all depends on the situation. If it is a busy pass and others are
> > trying to make a QSO with a specific station since they are a Rover
> > or DX or rare somehow or New, just step aside if you don't need or
> > want that station. If it is NOT a busy pass, there should be no problem
> > with calling any station for any reason as long as you are not QRMing
> > an existing QSO in progress. How easy is it to just LISTEN and hear
> > what is going on and act accordingly? Just like on other Bands or
> > Modes or Repeaters, DON'T transmit on top of a busy frequency. BTW,
> > if you can't hear other stations or the Beacon on a pass, it would not
> > be good to do a lot of transmitting since you may be causing a lot of
> > QRM to other users. Listening to several passes without hearing other
> > stations probably indicates you have a RX problem. When setting up
> > a station, always make sure you are hearing well before ever trying
> > to transmit.
> >
> > GL/73/Enjoy, Bob K8BL
> >     On Tuesday, March 24, 2020, 07:46:00 PM EDT, Brian Wilkins KO4AQF
> via AMSAT-BB <amsat-bb at amsat.org> wrote:
> >
> > I would not make this one a rule either especially since some rove to
> > multiple grids. It has to be handled by the operator on a case by case
> > basis. Also the called operator does not have to respond either if this
> is
> > a problem.
> >
> > Brian Wilkins
> > KO4AQF
> >
> >> On Tue, Mar 24, 2020 at 8:16 AM Roy Dean via AMSAT-BB <
> amsat-bb at amsat.org>
> >> wrote:
> >>
> >>>>
> >>> - problem #2 is about reducing congestion. It was discussed at length
> >>> right here last year or so, and the bottom line was to never work a
> >> station
> >>> if you have already worked them before.  Let others get a chance.
> >>
> >>
> >> "Never" is a powerful word.  There are plenty of passes that I've worked
> >> in the past in which the only operators on the pass are ones that I've
> >> worked plenty of times before.    Weekday morning passes are typical
> >> examples.  I would suggest leaving this rule out, or at least modifying
> it
> >> appropriately (however I think Sean's published work already suggests
> good
> >> operating habits that cover this).
> >>
> >> --Roy
> >> K3RLD
> >> _______________________________________________
> >> Sent via AMSAT-BB at amsat.org. AMSAT-NA makes this open forum available
> >> to all interested persons worldwide without requiring membership.
> Opinions
> >> expressed
> >> are solely those of the author, and do not reflect the official views of
> >> AMSAT-NA.
> >> Not an AMSAT-NA member? Join now to support the amateur satellite
> program!
> >> Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb
> >>
> > _______________________________________________
> > Sent via AMSAT-BB at amsat.org. AMSAT-NA makes this open forum available
> > to all interested persons worldwide without requiring membership.
> Opinions expressed
> > are solely those of the author, and do not reflect the official views of
> AMSAT-NA.
> > Not an AMSAT-NA member? Join now to support the amateur satellite
> program!
> > Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb
> >
> > _______________________________________________
> > Sent via AMSAT-BB at amsat.org. AMSAT-NA makes this open forum available
> > to all interested persons worldwide without requiring membership.
> Opinions expressed
> > are solely those of the author, and do not reflect the official views of
> AMSAT-NA.
> > Not an AMSAT-NA member? Join now to support the amateur satellite
> program!
> > Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb
> _______________________________________________
> Sent via AMSAT-BB at amsat.org. AMSAT-NA makes this open forum available
> to all interested persons worldwide without requiring membership. Opinions
> expressed
> are solely those of the author, and do not reflect the official views of
> AMSAT-NA.
> Not an AMSAT-NA member? Join now to support the amateur satellite program!
> Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb
>