Hi Take san, It's not you English, but a protocol challenge.
The reason for not receiving the RR73 from a fox depends on the S/N at the hound station and the detection probability of various messages. The S/N depends on the propagation, but also strongly on the number of carriers fox is using. Quite often fox uses more carriers, when it responses to users meaning less S/N per carrier. Another issue is decoding probability of the message such as K1ABC RR73; W9XYZ -08 is a bit less than normal RR73 or R+rpt messages to a single user, when the hound uses AP decoding. Now your proposal is to change the +rpt to a Hound to DUPE in the case the hound has started a new QSO attempt after some time, not because fox receives repeated R+rpt from the Hound. At least I understood it that way. So on the protocol point of view fox uses one timeslot less resources than is normal QSO, if the Hound receives the DUPE message. BUT even that DUPE message is a lost timeslot as the QSO is already in the log. The detection probability of the DUPE message would be the same as for R+rpt or RR73 messages. So how many times the fox should repeat it to make the Hound happy? On the fox point of view that Hound is not a problem as long as it can decode other new stations. There is another possibility for fox to send the RR73 using less carriers or even a RR73 to that Hound without combining it with a report to some other station (again a lost message option). That method could be more effective due to better S/N and detection probability. I just doubt whether a DX station would apply either it or your proposal as long as he is completing new QSOs at "full" speed, hi! 73, Reino OH3mA _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
