Further research revealed that as long as MyCall is set as portable call (i.e. with /1, /P, KH6/ or /KH6.);
1. Setting DX call and clicking on "Generate Std Msgs" causes the Tx1 set without GL, which is making the Tx text as <...> and receiver also receives the same message. 2. Double clicking on DX station decode will cause the same problem ( Tx1 set without GL and sent message becomes <...>) 3. Manually putting GL to TX1 field will start making the encode/decode fine. (i.e. receiver receives the message correctly and this confirms Q65 as protocol can deliver information with MyCall set as portable station.) 4. This will work on other modes such as FT8/JT65. This gives me an impression of WSJT-X on Q65 having an issue with generating message for Tx1. Can you work on this one, please? JO1LVZ/Hatt From: Hattori, Yoshihisa <[email protected]> Sent: Tuesday, March 30, 2021 9:45 AM To: WSJT software development <[email protected]> Subject: Re: [wsjt-devel] [EXTERNAL] Re: Q65 bug? Portable caller cannot be decoded. Bill Thank you for your prompt reply. Is that right understanding we lost the ability to call someone by using portable call, with prefix/suffix such as /1, /P and KH6/ only for Q65? FT8 and other modes support those and rc3 was supporting those in Q65, if I recall correctly. From: Bill Somerville <[email protected]<mailto:[email protected]>> Sent: Tuesday, March 30, 2021 12:49 AM To: [email protected]<mailto:[email protected]> Subject: [EXTERNAL] Re: [wsjt-devel] Q65 bug? Portable caller cannot be decoded. [CAUTION] This email originated from outside Travelport. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 29/03/2021 15:52, Hattori, Yoshihisa wrote: Hi all. This is to report a possible issue for Q65. I and some other JA users who are using RC4 realized that portable operator with call/1, call/P and such can NOT reach other stations as long as they are using TX1. Ex. I as a portable operator with call JO1LVZ/P want to make call to JA1RL by using TX1. i.e. TX1 set as JA1RL JO1LVZ/P PM95. This won't be decoded and JA1RL will receive JA1RL <...> PM95. Is this a known issue? Please note that all of non-standard call like KH6/JO1LVZ etc will have the same issue. De JO1lVZ/Hatt. HI Hatt-san, try starting your QSO with either: CQ JO1LVZ/P PM95 or QRZ JO1LVZ/P PM95 or DE JO1LVZ/P PM95 The only way directly call the other station is to use: JA1RL JO1LVZ PM95 and use the /P suffix later in the QSO in one of the following messages: JA1RL JO1LVZ/P RRR or JA1RL JO1LVZ/P RR73 or JA1RL JO1LVZ/P 73 Note that all of the above messages are technically part of the EU Contest Mode message extensions, as such they are not automatically generated in normal QSOs, it is up to the user to edit the messages to be sent appropriately. 73 Bill G4WJS.
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
