locked Re: Necessity for Logic to prevent "RR73 Loops" #EnhancementReqest
|
Snip>>I will use the OFTEN SEEN example below that was recorded in VK3 on 6m FT8 "segment" 2022-12-03. The actual op call has been obscured as identifying the op would be bad practise.
230345 -15 -0.2 2254 ~ PJ4MM VK3?? RR73 °Australia 230415 -11 0.2 2254 ~ PJ4MM VK3?? RR73 •Australia 230445 -10 0.2 2254 ~ PJ4MM VK3?? RR73 °Australia 230515 -9 0.2 2254 ~ PJ4MM VK3?? RR73 °Australia 230545 -10 0.2 2254 ~ PJ4MM VK3?? RR73 °Australia 230615 -9 0.2 2254 ~ PJ4MM VK3?? RR73 °Australia 230645 -9 0.2 2254 ~ PJ4MM VK3?? RR73 °Australia<<Snip Stephen, It would seem to me if you are sending the RR73 over and over then perhaps he didn't receive your signal report correctly. Why not go back up and resend that a few times and see if that kickstarts the process... -- K4SOW ( https://www.qrz.com/lookup/k4sow )
|
|
|