Hello Trevor,
if I don't get the exchange properly and cannot manage to get a repeat that I
can decode I will send a NIL NIL (even if the station has left already) and NOT
log the Q. Logging it will prevent me from giving him a call (maybe) later in
the contest and complete the Q. Sometimes this will generate a B4 but as Bill
stated before, there are 'convincing' ways to get the friends to log you again
in their log.
73
Fabi va2up
http://sites.google.com/site/va2upcontesting/
> Date: Mon, 13 Feb 2012 23:51:08 +0000
> From: trevor_dunne@yahoo.com
> To: rtty@contesting.com
> Subject: [RTTY] Dupes now sorted what about busted serial's
>
> Thanks to everyone who answered my Dupes question, It was great to get the
> inside view on what to do, Next problem I have is. On a few of my QSO's I
> didn't get the callers Serial number, be it that I just missed it and he
> moved on or that he kept giving it to me and I just could not decode it.
>
> I hade the problem that was mentioned on N1MM reflector about the funny
> exchanges I got a few QWE and YTE ect's I logged the QSO's with 001 and after
> I found the issue I edited them
>
> But what do I do with QSO's with busted serial numbers more often that not
> the other station has my number and is gone and im sitting there pushing
> buttons trying to get him to try one more time.
>
> Do i log it with 001, 000 or not log it at all. the main problem would be
> what the other station does if he got my NR he is happy but how will it b e
> scored if its not in my log.
>
>
>
> Thanks
> Trevor
> EI2GLB
>
>
> ________________________________
> From: "James C. Hall, MD" <heartdoc@nwtcc.com>
> To: 'RTTY Reflector' <rtty@contesting.com>
> Sent: Monday, 13 February 2012, 20:58
> Subject: Re: [RTTY] Dupes how to handle
>
> This is really hard to take sometimes. I had a dupe rate of 1.7% - in this
> day and age of computer logging, this seems WAY too high. There was one K4
> who was about to get on my last nerve who was a dupe TWICE on one band ! And
> I took the time to type him and tell him he was a dupe AGAIN ! One G3 was
> quite apologetic about being a dupe and others figured it out but only after
> I called them and they disappeared. If more than one is calling and one is a
> dupe, I try to ignore them, but if they're persistent, I go ahead and work
> them - they may have gotten, or I may have gotten, a call wrong the first
> time.
>
> 73, Jamie
> WB4YDL
>
> -----Original Message-----
> From: rtty-bounces@contesting.com [mailto:rtty-bounces@contesting.com] On
> Behalf Of Bill Turner
> Sent: Monday, February 13, 2012 12:27 AM
> To: rtty@contesting.com
> Subject: Re: [RTTY] Dupes how to handle
>
> ORIGINAL MESSAGE:
>
> On 2/12/2012 8:02 AM, trevor dunne wrote:
> > 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
>
> REPLY:
>
> When a dupe calls you, the best approach is to completely ignore the fact he
> is a dupe and work him normally. Don't delete the previous QSO, don't try to
> alter serial numbers, etc, etc. Modern log checking software (Cabrillo) will
> find the dupe, ignore it and give you full credit. I always end up giving
> out higher serial numbers than I have valid QSOs. In the just competerd WPX
> i had 13 dupes in the log. Doesn't matter at all.
>
> I have a macro I use when someone sends me the B4 message:
>
> NOT IN LOG
> PLEASE WORK ME AGAIN W6WRT W6WRT
>
> Works like a charm.
>
> 73, Bill W6WRT
>
> _______________________________________________
> RTTY mailing list
> RTTY@contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
>
> --
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be clean.
>
> _______________________________________________
> 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
|