The other (great) thing K5P was doing was sending the guys call, report,
then repeating the call at the END of the report. This way - if the first
part of his transmission is covered up, chances are you will hear your call
at the end, and know who he came back to.
Seemed to work well, and considering the alternative, it certainly kept the
rate up :-)
Tom - VE3CX
On Mon, Jan 18, 2016 at 11:38 AM, Don Kirk <wd8dsb@gmail.com> wrote:
> I was holding back on posting a comment on this topic of continuous calling
> (I actually typed out a response but deleted it twice yesterday) but
> thought I would finally hit the send key in an attempt to should shed some
> light on part of the problem as well as a partial solution (not a complete
> solution as there are many different reasons for the problem which includes
> deep fading, as well as just being totally clueless, desperate, etc).
>
> As a W1AW/9 centennial station and operator (all CW), I found the biggest
> cure for the problem was sending the call sign of the station I picked out
> of the pile up 2 times. My best guess was that operators that have longer
> calls (like myself), and/or send slow, or run "semi break in" often don't
> hear the DXpedition station respond to someone else because they are still
> sending (or muted), and this gets worse when everyone gets out of sync
> (they would really get out of sync from each other when I could not pick
> out even a partial call the first time around and this caused stations to
> start repeating their calls in hopes of being the "chosen one", etc.). I
> would not always use the "sending calls two times" technique, but when the
> problem started to impact my receive capabilities (or just drove me nuts),
> I would implement this technique with great success.
>
> I've heard a few DXpedition operators on 160 meters use the "sending calls
> two times" technique under certain conditions (but not often), and the
> results are normally very impressive. This technique is not often
> discussed (as far as I know), and probably frowned upon by some who might
> think it slows things down, but I certainly found this technique useful
> (and often the most efficient method).
>
> Just some thoughts from my end based on my experience last year.
>
> 73,
> Don (wd8dsb)
>
> On Mon, Jan 18, 2016 at 10:36 AM, Roger D Johnson <n1rj@roadrunner.com>
> wrote:
>
> > The big problem is that this "system" works! It's simple statistics. The
> > more times you
> > send your call, the better chance of the DX picking it out of a pileup.
> >
> > I don't think the people that do this give a rats behind if they're
> > calling on top of
> > someone else. They are like people who cut in line ahead of you. It's all
> > about them!
> >
> > 73, Roger
> >
> >
> > On 1/18/2016 10:00 AM, mstangelo@comcast.net wrote:
> >
> >>
> >> When someone is doing something wrong we should not "out" or embarrass
> >> them.
> >>
> >> You should try to settle the situation offline without leaving any bad
> >> feelings.
> >>
> >> If you know the offender you should discuss it with him (or her) person
> >> to person. Be diplomatic.
> >>
> >> Don't lecture to them, discuss it with them. You have noticed they are
> >> doing something which interferes with good operating practices and also
> >> mention that other listeners have noted the fact.
> >>
> >> If you cannot contact the person you can mention the offense on a
> >> contesting or DX'ing forum such as this
> >>
> >> I find it is better to show them the way.
> >>
> >> Mike N2MS
> >>
> >>
> >>
> >>
> >> _________________
> > Topband Reflector Archives - http://www.contesting.com/_topband
> >
> _________________
> Topband Reflector Archives - http://www.contesting.com/_topband
>
_________________
Topband Reflector Archives - http://www.contesting.com/_topband
|