The big problem is even knowing there are two stations listening on the same
freq. Most times one would not know this was happening, so there's nothing
"special" one can do.
Sending the other station's call seems the only thing one can do, and for it
to be effective, it seems it must be done whenever there's a high likelihood
of this happening (like ALL the time on 40 phone in a DX contest).
However, if somehow you *know* there are two guys listening on one freq.,
and both come back to you, I would just log them both. Two QSOs for one
"over" is quite efficient. Doesn't work quite so well in a serial number
contest, though... Regardless, this is pretty rare, IMO.
Now, something that is less rare... suppose you are on 40SSB in CQWW, and
call IR4T and he says QSO B4, and he isn't in your log, nor is there
anything close. He tells you that you worked at 03:44Z the previous day,
and you were on 40 then, but still cannot find a match. Two things can
happen:
1.0) He does the smart thing and works you "again" and now you are in each
other's logs.
2.0) He gives you a hard time and won't work you again. So, you can either:
2.1) go away and not log him. You lose one QSO, but <hand wringing> he
loses four.
2.2) log him anyway - is that not the "smart" thing since "logged QSO
time" seems to not be an issue in log checking (yet)?
73 Mike N2MG
K4JRB wrote:
> If say D44TD and IR4T are both listening on the same frequency how do you
> stop this duplication? Sometimes it is not prudent to start with their
> call ( D44TD this is K4JRB) but its the only way I know to stop the B4.
---------------------------------------------------------------
The world's top contesters battle it out in Finland!
THE OFFICIAL FILM of WRTC 2002 now on professional DVD and VHS!
http://home1.pacific.net.sg/~jamesb/
---------------------------------------------------------------
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|