RTTY
[Top] [All Lists]

Re: [RTTY] Dupes how to handle

To: "'Alejandro V. XE1EE'" <xe1ee@telmexmail.com>, <k0rc@citlink.net>
Subject: Re: [RTTY] Dupes how to handle
From: "Ed Muns" <ed@w0yk.com>
Reply-to: ed@w0yk.com
Date: Mon, 13 Feb 2012 23:11:40 -0400
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
There is no "limit" to the number of dupes you can have in your log.  There
is no disqualification or any consequence at all for having any number of
dupes in your log.

In the days before electronic log files and before computer log checking
there were some contests that disqualified a log with more than, say, 3%
dupes.  But this is no longer the case in today's electronic world.

The only thing that matters about dupes is to leave them in your log.
Furthermore, sending "QSO B4" and refusing to work dupes is only hurting
yourself.  It is just as fast to work dupes as it is to break rhythm and
tell the station you aren't going to work him.

Moreover, I am delighted when a "dupe" calls me because he may be saving me
a NIL penalty.  Instead of being annoyed that the dupe is wasting my time, I
am thankful a problem is being fixed (that I didn't know I had).  Yes, I
know there are a few dupe situations where the other station is not keeping
a log and has a poor memory and just keeps working me.  But that is rare and
shouldn't cause us to get all caught up in the "QSO B4" nonsense.  

This one of the simplest parts of radiosport:  WORK DUPES.

Ed - P49X



> -----Original Message-----
> From: rtty-bounces@contesting.com [mailto:rtty-bounces@contesting.com] On
> Behalf Of Alejandro V. XE1EE
> Sent: Monday, February 13, 2012 7:23 PM
> To: k0rc@citlink.net; rtty@contesting.com
> Subject: Re: [RTTY] Dupes how to handle
> 
> Well, my logic is to avoid dupes on my log, however it's a good point what
> you state about the guy loosing his log.
> 
> So you think is better to work dupes instead of ignore them?.. will the
> penalties worth?, of course i know there's a limit of dupes before i have
> a
> disqualification and the common sense will tell me when there are too many
> dupes.
> 
> If I work dupes will have no more than 5 in a whole contest, that macro
> does
> not triggers too often
> 
> Tnx!
> 
> *********************
> XE1EE
> Alejandro Valdez O.
> DXCC RTTY, SSB & CW
> Mixed, 10, 15, 20 & 40
> WAS, TPA & WAC
> www.dxxe.org
> www.qsl.net/xe1ee
> Twiter: @xe1ee
> ***********************
> 
> +++++ No mas SPAM ++++++
> No me envíes cadenitas, oraciones y demás correos sin mi autorización.
> Do not send me prays, chain letters and others without my permission.
> ** No trees were killed in the sending of this message but a large number
> of
> electrons were terribly inconvenienced**
> 
> 
> --------------------------------------------------
> From: "Robert Chudek - K0RC" <k0rc@citlink.net>
> Sent: Monday, February 13, 2012 5:01 PM
> To: <rtty@contesting.com>
> Subject: Re: [RTTY] Dupes how to handle
> 
> > "I never work dupes."
> >
> > What is your logic behind this?
> >
> > What happens if the fellow who calls you the second time lost his log
> > from the first day?
> >
> > You will get a NIL and penalty when log checking is done. And if he was
> > a unique multiplier, you will loose that credit too.
> >
> > How do we convince you that by not working dupes it will cost you points
> > and/or multipliers in the long run?
> >
> > 73 de Bob - KØRC in MN
> >
> > ------------------------------------------------------------------------
> >
> > On 2/13/2012 4:33 PM, Alejandro V. XE1EE wrote:
> >> Hello Trevor
> >>
> >> Well, I have a macro who checks the call against the current contest
> log,
> >> if
> >> it is a dupe sends Call QSO B4 XE1EE QRZ, if not just sends the serial
> >> number and I keep going, I never work dupes.
> >>
> >> By the way..  you where here 5/9 (on 15 meters) and never heard me :(
> and
> >> I
> >> was running 300 watts.
> >>
> >> Here's the macro I use (on Writelog)
> >>
> >> %R%C %BQSO B4%RXE1EE QRZ%E%B 599 %N3 %N3%E
> >>
> >> 73!
> >>
> >> *********************
> >> XE1EE
> >> Alejandro Valdez O.
> >> DXCC RTTY, SSB&  CW
> >> Mixed, 10, 15, 20&  40
> >> WAS, TPA&  WAC
> >> www.dxxe.org
> >> www.qsl.net/xe1ee
> >> Twiter: @xe1ee
> >> ***********************
> >>
> >> +++++ No mas SPAM ++++++
> >> No me envíes cadenitas, oraciones y demás correos sin mi autorización.
> >> Do not send me prays, chain letters and others without my permission.
> >> ** No trees were killed in the sending of this message but a large
> number
> >> of
> >> electrons were terribly inconvenienced**
> >>
> >>
> >> --------------------------------------------------
> >> From: "trevor dunne"<trevor_dunne@yahoo.com>
> >> Sent: Sunday, February 12, 2012 10:02 AM
> >> To: "RTTY-reflektorn"<rtty@contesting.com>
> >> Subject: [RTTY] Dupes how to handle
> >>
> >>> Whats the correct procedure to handle dupe in any contest but mainly
> WPX
> >>> RTTY
> >>>
> >>> I have a few QSO's that I thought were good but the other station
> called
> >>> me again and when I said QSO B4, I wasn't in there log,
> >>>
> >>> Do I just delete the first bad QSO and log the 2nd one ???
> >>>
> >>> How does that affect my serial number count as there will be missing
> >>> QSO's
> >>> in the log ???
> >>>
> >>>
> >>> Thanks
> >>> Trevor
> >>> EI2GLB
> >>>
> >>>
> >>> ________________________________
> >>> _______________________________________________
> >>> RTTY mailing list
> >>> RTTY@contesting.com
> >>> http://lists.contesting.com/mailman/listinfo/rtty
> >>>
> >> _______________________________________________
> >> RTTY mailing list
> >> RTTY@contesting.com
> >> http://lists.contesting.com/mailman/listinfo/rtty
> >>
> > _______________________________________________
> > RTTY mailing list
> > RTTY@contesting.com
> > http://lists.contesting.com/mailman/listinfo/rtty
> >
> _______________________________________________
> RTTY mailing list
> RTTY@contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty

_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

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