This event anomaly started with me using WSJT-X RC3. A new FT8 DXCC country popped up today, 3XY4D. When I double clicked on his CQ call, it did not populate the message boxes. Thinking that he had manually typed in a non-standard format message, I typed "3XY4D" in the 'DX Call' box and generated a set of standard messages. So far so good.
I started calling him but noticed that even though my Tx1 message was set to "3XY4D K1HTV FM18" what I was sending him was "3XY4D K1HTV F". So for my next transmissions calling him I send the TX2 message "3XY4D K1HTV -10". But that message was truncated so what I was sending was "3XY4D K1HTV -" After a number of calls he finally answered me but instead of receiving from him a normal "K1HTV 3XY4D -nn" report, all I saw was "K1HTV 3X4D -" . Hmmmm. Assuming that he was sending some kind of dB report I followed up with calls and RRR, But instead of my Tx3 box message "3XY4D K1HTV R-10" my transmission to him instead was truncated to "3XY4D K1HTV R". Instead of me receiving from him a "K1HTV 3XY4D RRR" all I received was "K1HTV 3XY4D R". I sent Tx5 message "3XY4D K1HTV 73" and what came out was "3XY4D K1HTV 7". After completing the QSO with 3XY4D, country #176 with 75W, I thought I'd restart WSJT-X RC3. After I did I noticed that he was still sending CQ. When I double clicked on his CQ line, I still couldn't populate the message boxes. Also noticed 3XY4D working others, also with truncated messages, but the messages varied in length, depending on the number of characters in the call sign of the station he was working. OK, thought I'd better download the latest WSJT-X development build and did so. Using "WSJT-X v1.7-develop r8195", I ran the same tests with the same results. Then I replaced the "3XY4D" call with the same format call "3DA4D" (Swaziland) and ran tests of my generating and sending messages with the K3 in the TEST mode and everything came out normal. Next I simulated using "3XY4D" in Settings/General "My Call" and ran more tests. Here is what I found while simulating 3XY4D as my call. When I clicked on a station calling CQ, all of the standard message boxes were correctly populated. But... when I made simulated transmissions using 3XY4D as my call sign, the actual messages being send varied, depending on the length of the call sign of the other station. Using the TX6 CQ message "call 3XY4D IJ39": A 3 character call resulted in "call 3XY4D IJ3" being transmitted. A 4 character call resulted in "call 3XY4D IJ" A 5 character call resulted in "call 3XY4D I" A 6 character call resulted in "call 3XY4D " It appears that any "3XY" callsign being used is treated as a non standard call and is limited to the 13 character maximum limit. The Users Guide states "A standard amateur callsign consists of a one- or two-character prefix, at least one of which must be a letter, followed by a digit and a suffix of one to three letters." Looks like the prefix length needs to be expanded to include the 3-character prefix "3XY". The CTY.DAT file only has "3X" and not "3XY" as the prefix for Guinea so all WSJT-X users will be affected. So it looks like for now, Luc Jean Pierre THIBAUDAT, 3XY4D, and all "3XY" stations appear to be victims of the reported problem. 73, Rich - K1HTV cc:3XY4D ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
