Re: [wsjt-devel] Hashed callsign collisions?
Hi Jon and Paul, I repeated the situation using my audio link, but could not repeat the misbehavior from V2.5.4 to V2.6.1 or other way round. The slashed callsign is hashed completely so that cannot be the reason either. I still stand my opinion that it is an operator action, hi! 73, Reino OH3mA PS. I had only two stations in that test, but both recognized the callsigns W1WW/0 and W1WW/7 as hash values. Reino From: Jon Anhold via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: 21. tammikuutata 2023 1:26 To: WSJT software development Cc: Jon Anhold Subject: Re: [wsjt-devel] Hashed callsign collisions? I guess it isn't shown in that screenshot, but after I worked W1AW/0 (when I was calling W1AW/7), W1AW/0 called CQ, I called W1AW/7 again and W1AW/0 answered me, and I suspect it was the software answering thinking I was calling 0. On Fri, Jan 20, 2023 at 6:23 PM Jon Anhold mailto:j...@anhold.com> > wrote: I'm pretty sure, although I can't know for certain, that W1AW/0's WSJT-X auto seq answered me after his CQ when I was calling W1AW/7. On Fri, Jan 20, 2023 at 4:42 PM Reino Talarmo via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net> > wrote: Hi Jon, I don’t see any hash collision in those messages. You should ask what W1WW/0 did? Perhaps operator was waiting a “73” from your, but you sent one to W1WW/3 and W1WW/0 decided to send you a new report. I don’t know whether that station received your message at 205445 as you changed it to W1WW/7 at 205448. Could be possible! In any case both station sent to you “RR73”. 73, Reino OH3mA From: Jon Anhold via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> ] Sent: 20. tammikuutata 2023 22:56 To: WSJT software development mailto:wsjt-devel@lists.sourceforge.net> > Cc: Jon Anhold mailto:j...@anhold.com> > Subject: [wsjt-devel] Hashed callsign collisions? I was just on 20m trying to work W1AW/7, and W1AW/0 answered me, twice - is this a known issue with longer/hashed callsigns? 73 de KM8V Jon ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Hashed callsign collisions?
I would not be surprised if only the main call is used to compute the hash. Then this admittedly rare and apparently unforseen case, the same main call being used by multiple different stations at the same time, distinguished only by their slash "decoration", arises. Result: collisions among W1AW slash whatever calls. 73, Paul K6PO On Fri, Jan 20, 2023 at 1:46 PM George J Molnar via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > I had the same thing happen - as if the hash is the same for both /0 and > /7, so they both respond. > > > > *George J Molnar, KF2T* > FM19ma - Maryland, USA > > > > > > > > On Jan 20, 2023, at 3:56 PM, Jon Anhold via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > I was just on 20m trying to work W1AW/7, and W1AW/0 answered me, twice - > is this a known issue with longer/hashed callsigns? > > > > 73 de KM8V Jon > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Hashed callsign collisions?
I guess it isn't shown in that screenshot, but after I worked W1AW/0 (when I was calling W1AW/7), W1AW/0 called CQ, I called W1AW/7 again and W1AW/0 answered me, and I suspect it was the software answering thinking I was calling 0. On Fri, Jan 20, 2023 at 6:23 PM Jon Anhold wrote: > I'm pretty sure, although I can't know for certain, that W1AW/0's WSJT-X > auto seq answered me after his CQ when I was calling W1AW/7. > > On Fri, Jan 20, 2023 at 4:42 PM Reino Talarmo via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > >> Hi Jon, >> >> I don’t see any hash collision in those messages. You should ask what >> W1WW/0 did? Perhaps operator was waiting a “73” from your, but you sent one >> to W1WW/3 and W1WW/0 decided to send you a new report. I don’t know whether >> that station received your message at 205445 as you changed it to W1WW/7 at >> 205448. Could be possible! In any case both station sent to you “RR73”. >> 73, Reino OH3mA >> >> >> >> *From:* Jon Anhold via wsjt-devel [mailto: >> wsjt-devel@lists.sourceforge.net] >> *Sent:* 20. tammikuutata 2023 22:56 >> *To:* WSJT software development >> *Cc:* Jon Anhold >> *Subject:* [wsjt-devel] Hashed callsign collisions? >> >> >> >> I was just on 20m trying to work W1AW/7, and W1AW/0 answered me, twice - >> is this a known issue with longer/hashed callsigns? >> >> >> >> [image: image.png] >> >> >> >> 73 de KM8V Jon >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Hashed callsign collisions?
I'm pretty sure, although I can't know for certain, that W1AW/0's WSJT-X auto seq answered me after his CQ when I was calling W1AW/7. On Fri, Jan 20, 2023 at 4:42 PM Reino Talarmo via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hi Jon, > > I don’t see any hash collision in those messages. You should ask what > W1WW/0 did? Perhaps operator was waiting a “73” from your, but you sent one > to W1WW/3 and W1WW/0 decided to send you a new report. I don’t know whether > that station received your message at 205445 as you changed it to W1WW/7 at > 205448. Could be possible! In any case both station sent to you “RR73”. > 73, Reino OH3mA > > > > *From:* Jon Anhold via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] > > *Sent:* 20. tammikuutata 2023 22:56 > *To:* WSJT software development > *Cc:* Jon Anhold > *Subject:* [wsjt-devel] Hashed callsign collisions? > > > > I was just on 20m trying to work W1AW/7, and W1AW/0 answered me, twice - > is this a known issue with longer/hashed callsigns? > > > > [image: image.png] > > > > 73 de KM8V Jon > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Hashed callsign collisions?
I had the same thing happen - as if the hash is the same for both /0 and /7, so they both respond. George J Molnar, KF2T FM19ma - Maryland, USA > On Jan 20, 2023, at 3:56 PM, Jon Anhold via wsjt-devel > wrote: > > I was just on 20m trying to work W1AW/7, and W1AW/0 answered me, twice - is > this a known issue with longer/hashed callsigns? > > > > 73 de KM8V Jon > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Hashed callsign collisions?
Hi Jon, I don’t see any hash collision in those messages. You should ask what W1WW/0 did? Perhaps operator was waiting a “73” from your, but you sent one to W1WW/3 and W1WW/0 decided to send you a new report. I don’t know whether that station received your message at 205445 as you changed it to W1WW/7 at 205448. Could be possible! In any case both station sent to you “RR73”. 73, Reino OH3mA From: Jon Anhold via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: 20. tammikuutata 2023 22:56 To: WSJT software development Cc: Jon Anhold Subject: [wsjt-devel] Hashed callsign collisions? I was just on 20m trying to work W1AW/7, and W1AW/0 answered me, twice - is this a known issue with longer/hashed callsigns? 73 de KM8V Jon ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Hashed callsign collisions?
I was just on 20m trying to work W1AW/7, and W1AW/0 answered me, twice - is this a known issue with longer/hashed callsigns? [image: image.png] 73 de KM8V Jon ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
