开云体育

WI QSO Party

Gary Mattson All Messages By This Member #64058 Running the latest version. I noted the dupe checking stopped, likely around 0000 hours. I don't believe the rules allowed for dupe contacts in the same band/mode during all of the event. At the very least someone noted my call was a dupe. A find function lookup verified a contact with the station earlier in the afternoon.? It seemed dupe checking was reset as the new day started.? Did I miss something in the rules for find a bug? ? ?
Dean Holste All Messages By This Member #64059 Gary, ? I had the same thing happen several times. I would put a call in and even though I knew it was a dupe after I typed it in, it didn't flag it as such. Dean KC9EOQ toggle quoted message Show quoted text On Mon, Mar 10, 2025 at 9:40?PM Gary Mattson via <cheech88=[email protected]> wrote: Running the latest version. I noted the dupe checking stopped, likely around 0000 hours. I don't believe the rules allowed for dupe contacts in the same band/mode during all of the event. At the very least someone noted my call was a dupe. A find function lookup verified a contact with the station earlier in the afternoon.? It seemed dupe checking was reset as the new day started.? Did I miss something in the rules for find a bug? ? ?
Scott Davis All Messages By This Member #64060 Hi Gary, Thanks for your e-mail.? If you click Settings > Allow Duplicates, you will be able to log them, but the software will still warn you.? There isn't a way to disable it entirely. Make sure you didn't long the station on a different band or mode, or indicate he was in a different county (or you were). Enjoy! 73, Scott N3FJP Serving the Amateur Radio community with contesting and general logging software since 1997. 1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give . But do this with gentleness and respect... On Monday, March 10, 2025 at 10:40:32 PM EDT, Gary Mattson via groups.io <cheech88@...> wrote: Running the latest version. I noted the dupe checking stopped, likely around 0000 hours. I don't believe the rules allowed for dupe contacts in the same band/mode during all of the event. At the very least someone noted my call was a dupe. A find function lookup verified a contact with the station earlier in the afternoon.? It seemed dupe checking was reset as the new day started.? Did I miss something in the rules for find a bug? ? ?
Scott Davis All Messages By This Member #64061 Hi Dean, Thanks for the report.? On what band, mode and county was the previous QSO?? On what band, mode and county was the current contact occurring? 73, Scott N3FJP Serving the Amateur Radio community with contesting and general logging software since 1997. 1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give . But do this with gentleness and respect... On Tuesday, March 11, 2025 at 12:17:31 AM EDT, Dean Holste via groups.io <kc9eoq@...> wrote: Gary, ? I had the same thing happen several times. I would put a call in and even though I knew it was a dupe after I typed it in, it didn't flag it as such. Dean KC9EOQ toggle quoted message Show quoted text On Mon, Mar 10, 2025 at 9:40?PM Gary Mattson via <cheech88=[email protected]> wrote: Running the latest version. I noted the dupe checking stopped, likely around 0000 hours. I don't believe the rules allowed for dupe contacts in the same band/mode during all of the event. At the very least someone noted my call was a dupe. A find function lookup verified a contact with the station earlier in the afternoon.? It seemed dupe checking was reset as the new day started.? Did I miss something in the rules for find a bug? ? ?
Dean Holste All Messages By This Member #64063 Hi Scott, ? ?I'm sorry I did not write down the band, county, etc. I should have paid attention more closely to that. I do remember it was the same band and mode. I was picking call signs off the band strip ( I forget the true name) off to the side. It only happened a couple of times and did not hinder me at all.? 73' Dean KC9EOQ toggle quoted message Show quoted text On Tue, Mar 11, 2025 at 6:38?AM Scott Davis via <SNKDavis=[email protected]> wrote: Hi Gary, Thanks for your e-mail.? If you click Settings > Allow Duplicates, you will be able to log them, but the software will still warn you.? There isn't a way to disable it entirely. Make sure you didn't long the station on a different band or mode, or indicate he was in a different county (or you were). Enjoy! 73, Scott N3FJP Serving the Amateur Radio community with contesting and general logging software since 1997. 1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give . But do this with gentleness and respect... On Monday, March 10, 2025 at 10:40:32 PM EDT, Gary Mattson via <cheech88=[email protected]> wrote: Running the latest version. I noted the dupe checking stopped, likely around 0000 hours. I don't believe the rules allowed for dupe contacts in the same band/mode during all of the event. At the very least someone noted my call was a dupe. A find function lookup verified a contact with the station earlier in the afternoon.? It seemed dupe checking was reset as the new day started.? Did I miss something in the rules for find a bug? ? ?
Gary Mattson All Messages By This Member #64074 While those factors may be part of this, I am suspicous the dupe counter started over at 0000 hours.? I typed in plenty of dupe calls and saw the flags and then noticed after I worked a couple dupes again and the operator pointed it out that I was not seeing dupe flags. The event ran from March 9, 2025 from 1800Z to 0100Z March 10 (1:00PM CDT to 8:00PM CDT on March 9) spanning 2 days.? I think the program was allowing same call, same band; like POTA logging would allow same call, same park, same band, when the clock rolled over 0000. WIQP doesn't allow dupes for same call, same band for the whole period of the event at least as I see it in the rules.? ? I did have a period? when the program lost contact with the 7300 and I restarted the radio to recover, but I do not think I was not seeing dupe flags after that. So I can not speak with certainty.? My point is if the clock can reset the dupe counter, it should not for the WIQP. Regardless the event is already over? Thanks NG9P
Scott Davis All Messages By This Member #64075 Hi Gary, Thanks for your follow up.? The date and time isn't relevant for dupe checking.? The dupe checking code is identical in all our contest programs (aside from contest specific details like once per band, oncer per contest, etc.), has been used unchanged for years and does not evaluate date and time for the check. Enjoy! 73, Scott N3FJP Serving the Amateur Radio community with contesting and general logging software since 1997. 1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give . But do this with gentleness and respect... On Wednesday, March 12, 2025 at 12:26:12 PM EDT, Gary Mattson via groups.io <cheech88@...> wrote: While those factors may be part of this, I am suspicous the dupe counter started over at 0000 hours.? I typed in plenty of dupe calls and saw the flags and then noticed after I worked a couple dupes again and the operator pointed it out that I was not seeing dupe flags. The event ran from March 9, 2025 from 1800Z to 0100Z March 10 (1:00PM CDT to 8:00PM CDT on March 9) spanning 2 days.? I think the program was allowing same call, same band; like POTA logging would allow same call, same park, same band, when the clock rolled over 0000. WIQP doesn't allow dupes for same call, same band for the whole period of the event at least as I see it in the rules.? ? I did have a period? when the program lost contact with the 7300 and I restarted the radio to recover, but I do not think I was not seeing dupe flags after that. So I can not speak with certainty.? My point is if the clock can reset the dupe counter, it should not for the WIQP. Regardless the event is already over? Thanks NG9P
Gary Mattson All Messages By This Member #64076 Thanks for the response. I will attribute the error to the interuption in connection to the 7300 that occured.? I only operated phone, but noted after the fact that some entries were noted as PHN while others were SSB. Again maybe due to the interuption.
Fred, W9KEY All Messages By This Member #64077 Echoing other's comments ..... I participated in the Wisconsin QSO Party (in-state). ? I worked one mobile rover 5 times during the day.? Four of those were on the same Band.? He was roving through various Counties and apparently could hear me pretty well. ? The software (using Super Check Partial) will complain and warn you when entering a previously worked Call.? But once the new County was added, it was happy.

Previous Topic Next Topic