On 31 Jan 2019 at 6:14, Gene H wrote: > Yes, we have noticed this routinely with compound callsigns. It likely > is related to the complexity of compound callsigns and lack of number of > bits to send all information. I noticed if you hover your mouse over the > *Settings > General* tab on top of the *Station Details* "Message > generation for type 2 compound callsign holders:" there is some > information that might be helpful. Hopefully others will provide more > details.
Hi Gene, thanks for the reply. As far as I can tell the issue doesn't arise because of a shortage of bits in the message payload - I've just looked in my ALL.TXT file for my recent QSO with FG/F6ITD and can see that ALL.TXT includes the following line: 232400 -13 0.1 1635 ~ G0HDB <FG/F6ITD> -12 So, a report was received but for some reason the -12 figure didn't get inserted into the 'Rpt Rcvd' field in the 'Log QSO' window, and the report figure wasn't included in the ADIF record for the QSO when the wsjtx_log.adi file was written. I remember I had to manually edit the wsjtx_log.adi file to change the <rst_rcvd:0> field that had been written by the software to become <rst_rcvd:3>-12. -- 73, Martin G0HDB --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
