Hi all and Steve, It took me 5 seconds or less to solve a partial callsign. As an HF+6m and UP contester and DX hunter i rember well some valid very active callsigns and dxcc prefixes. I cant remember all grid squares but i know when is false or not or field is out of country or continent. It's good to take a look at world wide grid map and rember how are big fields placed b4 posting such question. I see many posts around the net and social media when people post false decodes and similar decoded stuff. Sometimes I laugh and I ask myself how did they get a licence or pass the exam? If i have free time I always try to teach or learn myself something new. And of course try that in practice.
Your decodes are not false, it is the operator fault who did make a mistake. It does happens ;) (leadings space, non supported character, etc..) There is no software on the market which is not Lidsproof ;) joke Wish you all the best, 73 Patrik 9A5CW uto, 18. kol 2020. 16:21 Stephen VK3SIR <vk3...@hotmail.com> je napisao: > Enrico, > > > > Exactly… but how do we know what currently is valid when the rules are > bent by regulators every day? The point of the initial post was to tease > out of the community whether this was designed behaviour or whether this > was bi-product i.e. to draw out understanding of behaviour not only for me > but others. Welcoming discussion has successfully achieved this. > > > > The ”detective” work from Patrick 9A5CW was nothing short of brilliant ! > > But… hidden in my question was the premise that not all nations stick to > the rules i.e.: The recently FIXED VKxFXXX issue here in VK and “Special > event” calls. Not all nations are recognised (i.e. D1) yet they decode. > > > > Report what one sees as an anomaly and the supportive community is here > (though has been very quiet of late) to promote learning, encourage and > welcome others and their contribution. The references to documentation here > (repeated) are extremely helpful to me and others that asked questions of > me. I did not know … so … I asked. > > The environ must always be kept open, free and conducive for contribution. > > > > - little bit of know how should sit behind the monitor > > > > That is a bit harsh; one who purports to know all can be best described as > a fool … Likewise “for every rule there are always exceptions” (refer to > the i.e. above in the case of AR callsigns). > > Our licenses and software that we use (such as WSJT-X) are about > experimentation and learning; teaching – with questioning - is vital to > learning. Some of us came through academic environs where one’s knuckles > were very red if we questioned – as it was seen as an attack on authority > and “superiority”. Yet most Amateurs are subject to vastly different theory > from our modern academic age; in most free questioning is promoted and not > suppressed by the fear and bullying endemic of the past. > > > > I only bite those that suppress and bully others … I bite hard when > someone is bulled for questioning. I also bite-back at ignorance and > intolerance. The bullies should be bitten. > > > > HAM – help All Mankind. This discussion has helped me and others so thanks > to all – especially with the exact references in the docs that I profess to > not have been able to put my fingers on immediately. > > > > 73 > > > > Steve I > > VK3VM / VK3SIR > > > > *From:* Enrico <oe1...@oevsv.at> > *Sent:* Tuesday, 18 August 2020 10:50 PM > *To:* WSJT software development <wsjt-devel@lists.sourceforge.net> > *Subject:* Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that > use DX > > > > Steve, a little bit of know how should sit behind the monitor. > > A callsign is designated as country code + number + minimum 1 letter. So > 5CT is definitely a false decode. > > 73 > > Enrico, OE1EQW > > Holen Sie sich Outlook für Android <https://aka.ms/ghei36> > > > > > > On Tue, Aug 18, 2020 at 2:41 PM +0200, "Stephen VK3SIR" < > vk3...@hotmail.com> wrote: > > Patrick, > > > > - It is F5CT in JN08. > > > Great detective work… and WSJT-X working as it should by blocking an > invalid from being responded to ! > > > 73 > > > Steve I > > VK3VM / VK3SIR > > > [ Ps: Sorry I almost missed the email! ] > > > > *From:* Patrick 9A5CW <pat.9a...@gmail.com> > *Sent:* Tuesday, 18 August 2020 7:35 PM > *To:* WSJT software development <wsjt-devel@lists.sourceforge.net> > *Subject:* Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that > use DX > > > > Hi, > > Nothing wrong with a call ;) > > It is F5CT in JN08. > > He probably messed up his setup in WSJT-X or any other similar problem. > > Best regards and RR73 9A5CW > > > > uto, 18. kol 2020. 10:05 Stephen VK3SIR <vk3...@hotmail.com> je napisao: > > Michael, > > True and very possible. I have just done the polite thing and reported > observations - though I suspect WSJT-X behaviour is more than valid. I have > reported this just in case its not occurring by design as that can lead to > problems later down the track :-) > > [ Yet WSJT-X will also pick up the very common station D1DX - that is not > a recognised DXCC entity ... I am not buying into that argument !!! ]. > > There has been a lot of changes in postfixing and a growth of "prefix-x" > and "prefix-xx" template calls of late (including here in VK where prefix-X > will become available for Club/Contest stations for 12 months max only). > This observation may offer some forewarning (if required) ... > > I was in the midst of working a frenzy of EU contacts on 30m late this > afternoon when PM's (i.e. mostly Skype) went nuts at people trying to get > this supposed "Moroccan" station and could not get WSJT-X to pick up the > call. It is not a false decode as it was seen a number of times (i.e. > around 10 from my log). Morocco is rare and highly desirable in these > parts. > > I verified this behaviour myself. I also run JTAlert ... and even that > would not allow one to notionally grab "5CT" ... > > The JN0 is obviously a truncation and roughly translates to the region - > and I STATE ROUGHLY (but not perfectly); that significantly tips evidence > in the direction that you are suggesting ! > > So yes I have doubt too and had doubt before posting ! My concern more the > fact that it could not be picked up in any shape or form and responded to > that prompted the post ... and also the knowledge of what I have posted in > the 3rd sentence here ! > > 73 > > Steve I > VK3VM / VK3SIR > > -----Original Message----- > From: 5p1kzx Michael <5p1...@gmail.com> > Sent: Tuesday, 18 August 2020 5:35 PM > To: wsjt-devel@lists.sourceforge.net > Subject: Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX > > Hi Steve > > I don't think that 5CT is a valid callsign. A search on the Internet gave > no result. > > 73 de Michael 5p1kzx > > > Den 18-08-2020 kl. 08:06 skrev Stephen VK3SIR: > > Hi Folks, > > > > I am unsure whether this has been reported: > > > > 30m: > > > > 055130 -11 0.2 1626 ~ CQ CO8LY FL20 Cuba > > 055130 -17 0.3 1342 ~ R3BV F1LYV RR73 > > 055130 -19 0.3 618 ~ CQ DX 5CT JN0 Morocco <-- Will not allow > this to be picked this up > > 055200 -12 0.2 1627 ~ CQ CO8LY FL20 Cuba > > > > No matter what you do or how you try to pick up this calling station and > pick up its call (i.e. click on it, double click, even use JTAlert) WSJT-X > will not pick up this call ! > > > > I can see that this is being primarily interpreted as a text message > (i.e. > 13 chars) ... with the call framed in a " bad" format (missing the > final char of the maidenhead). > > > > [ It is fully understandable and understood why the logic will not > > allow this call to be picked up as the truncated maidenhead is > > confusing things ] > > > > Unfortunately I do not have a recording of this to post back ... > > > > The screen is going nuts here with PM's so it needs be reported. > > > > 73 > > > > Steve I > > VK3VM / Vk3SIR > > > > _______________________________________________ > > 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 > > _______________________________________________ > 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
