Hello all, I'm running WSJT-X v2.0.0 r784f75 on a PC with 32-bit Win 7 Pro.

I've discovered that for a few of my recent QSOs the received-report field 
didn't get populated 
when the QSO was logged.  I first spotted this when I looked at my QSOs as 
picked up via 
UDP by the Logger32 app, and then when I checked the corresponding entries in 
the 
wsjtx_log.adi file I found that the <rst_rcvd:x> ADIF field was also empty, ie. 
the field 
appeared as <rst_rcvd:0> and didn't have the expected 3-digit report eg. -10, 
that I'd received 
during the QSO.

>From what I've observed over the last week or two this only seems to occur 
>when the station 
I've worked has a 'compound' callsign such as VE2/UT3UA, SV1AQY/1, PJ7/IZ5KID 
or 
FG/F6ITD - as far as I've been able to tell, without doing any exhaustive 
observations, the 
received-report field always gets populated and logged correctly when the QSO 
is with a 
station with a standard callsign.

On the occasions I've spotted the absence of a received-report figure in the 
'Rpt Rcvd' field 
shown in the 'Log QSO' dialogue box before the QSO is actually logged, in the 
Logger32 log, 
or in the wsjtx_log.adi file, I've manually entered the report into the log and 
amended the 
<rst_rcvd:0> field in the ADIF file to show the report received, but I've found 
quite a few 
entries in my overall wsjtx_log.adi file that don't show a received-report 
figure.  Some of 
these pre-date the release of v2.0.0 so I don't know what caused them - I 
suspect there could 
be many possible causes including operator finger trouble...!

I'll continue to observe what happens when I do work stations with compound 
callsigns - 
there's only a few of them around - and will try to get a more accurate view on 
whether or not 
the received-report field gets populated correctly when I log such QSOs, but in 
the meantime 
I'll be interested to know if anyone else has observed this effect.  I haven't 
found any 
reference to it in either this email reflector or the Yahoo! group.

--
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

Reply via email to