Duplicate QSOs

So it doesn’t only happen to me! - on CW, chasers calling in for a second QSO. Of course, the reason for a second call could be one of many things - confusion, chaser unsure the first contact was good, chaser thinking that the activation was a different one, etc.

As I write I am listening to an activator on 7MHz CW who has had to advise of a repeat QSO attempt. I heard both times that the chaser called in. Signals between the two were good and there was no confusion when the error was advised. I must admit that my approach is avoid any issues and to work the chaser a second time. Later I check the database for which contact has been logged by the chaser and submit my activation log accordingly. While this may have the advantage of causing less disruption to the pile up and covering all potential reasons for being called a second time, is it really the best approach?

Any thoughts?

Gerald G4OIG

Work them all. Log them all. Let the database sort it out.

1 Like

If someone calls me for a second or more time, I say GM AGN 599 AGN 73 - and I don’t log it. The log that goes in my activator log is the first one as logged by me in my logbook. I acknowledge repeat calls with a report but I don’t log or enter them.

You can ask from the chaser QRU? Have you anything for me?

The extra QSO might help the other chasers to notice that you are on the frequency. So it is not always a bad thing.

73, Jaakko OH7BF/F5VGL

I agree. Work them all, log them all, upload them all to the database. Why filter, there is no penalty for dupes?

Malcolm VE2DDZ

[quote=“MM0FMF, post:2, topic:9693”]Work them all. Log them all.[/quote]…and then evidence of multiple calling will be in the database, too.

I sometimes do it on different bands, when the activator is not busy to compare my/his/her signals, or when the activator is calling CQ without answer, to let him/her it’s being listen

I work them and log them all.
If individually we are separately applying filters, we may end up to a point where the activator doesn’t log the second QSO because it’s a DUPE for him and the chaser doesn’t log the first one because he thought it wasn’t good contact due to QSB, too weak signal or whatever.
Should this happen, none of the QSOs (neither activator’s nor chaser’s) will get the confirmation *.
It’s not terrible, but I think that having no penalties for working DUPES it’s better working them all rather than denying the 2nd QSO or applying filters unilaterally.
Best 73 de Guru - EA2IF

I agree - work and log all. Just because I was certain of the report on my end doesn’t mean that some momentary anomaly didn’t take it out on his and, and he wanted a verification.

Of course, this assumes it isn’t a different band, or after UTC midnight. But I get a few that contacts me on as many bands as possible. It is interesting to see how signals change from 40m th 30m to 20m as I go up the bands.

Vy73 - Mike - KD5KC.
El Paso, Texas - DM61rt.
W5-SOA Association Manager.

[quote=“KD5KC, post:9, topic:9693”]a different band[/quote]Indeed, having reports on different bands and modes from one caller is often informative, and as soon as there’s a difference in mode or band it’s no longer a duplicate anyway.

73, Rick M0LEP