JN0 is not a valid grid (you should enter at least four characters). Even so, 2.2.2 will allow you to enter both an “invalid” call and grid in the DX Call and DX Grid boxes, press Generate Std Msgs, and call the station. Yo may need to manually step through the QSO cycle, but it WILL work.
5CT is NOT a valid callsign format, but N7C is. It’s not the length, it’s the format that counts. Looking through DX spots lately, I don’t see a 5CT operation spotted anywhere. Is it possible you had a false decode? George/KF2T > On Aug 18, 2020, at 7:51 AM, Stephen VK3SIR <[email protected]> wrote: > > Frode, > > Thanks … By not “picking up” I was meaning you could not click, double-click > or even use a third-party product via the UDP interface to force WSJT-X to > place WSJT-X into a Tx2 mode that should have responded to the call. It’s a > damn shame that I could not catch the call quickly enough (again) to get a > recording of the stream. > > Recorders are on now … Hopefully someone else out there has seen this, has it > and can supply? > > I had no problem sending any of the Tx1 - Tx5 messages with 5CT in the DX > Call field and JN0 in the DX Grid field. > > The problem is not sending; it’s the program being able to RESPOND through > WSJT-X to 5CT sent as an attempted Tx1 ! It was not just me seeing this - > which is why I responded with a report here. > > First of all 5CT is not a valid call sign. > > It may or it may not be … It COULD have been allocated. But I have been > responding to a number of calls that now fit this template i.e. N7C ( > https://www.qrz.com/db/n7c <https://www.qrz.com/db/n7c> ) is a VERY valid and > sought after call. I was able to make contact with that station but not this > one ! > > 73 > > Steve I > VK3VM / Vk3SIR > > > From: Frode Igland <[email protected] <mailto:[email protected]>> > Sent: Tuesday, 18 August 2020 9:08 PM > To: WSJT software development <[email protected] > <mailto:[email protected]>> > Subject: Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX > > Steve, I guess that your statement "WSJT-X will not pick up this call" means > that WSJT-X will not automatically enter this call into the "DX Call" field, > nor the locator into the "DX Grid" field. That is true, but WSJT-X will > certainly pick up the call and grid as decoded if you enter it manually into > the two fields. WSJT-X does not care how the call and grid arrives in the two > fields, but once they are there they are used as entered. > I had no problem sending any of the Tx1 - Tx5 messages with 5CT in the DX > Call field and JN0 in the DX Grid field. > > Secondly, and all important here, it 5CT is not in accordance with the WSJT-X > defintions and algorithms for what constitutes a call sign as defined in > https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.2.2.html#PROTOCOL_OVERVIEW > > <https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.2.2.html#PROTOCOL_OVERVIEW> > . Consequently, all my messages were sent as free text messages truncated at > 13 characters, which is just right. > > 73 Frode LA6VQ > > tir. 18. aug. 2020 kl. 08:11 skrev Stephen VK3SIR <[email protected] > <mailto:[email protected]>>: > 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 > [email protected] <mailto:[email protected]> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>_______________________________________________ > wsjt-devel mailing list > [email protected] <mailto:[email protected]> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
