I am one of those user types who install every single RC# for the
last 8 years. Each time I reinstall wsjtx, I change to a new appdata folder
using the wsjtx --rig-name= <myRigName><wsjtx-vers-number>.
Over time, I have deleted a number of those older appdata folders.
Therefore, my WSJT-X log.adi is very small, and my worked B4 status is
incomplete.
In reading the WSJT-X user docs, I see that I can import my
full 10 year ADIF file from my other logging sources, and then
click the rescan button in WSJT-X. This was only partially
effective, as some callsigns that are clearly in my log several
times are not showing up in the WSJT-X activity window as
"Worked Before". Others do show worked B4. In trying to diagnose
this issue, I have the following questions to hopefully expand my knowledge;
1. WSJT-X writes it's wsjtx_log.adi entries as a horizontal line
ending with the expected <eor>.
Example: ...<my_gridsquare:4>DM03 <comment:25>50W <operator:5>N6YFM *<eor>*
However, when I download my full entire log ADIF from either ACLOG or
QRZ,
each QSO record is a vertically stacked set of ADIF fields, ending
in the <eor>
on the last line all by itself. Example:
...
<Gridsquare:6>FM19
<Mode:4>FT8
<OPERATOR:5>N6YFM
<TX_PWR:4>30.0
<State:2>MD
*<eor>*
Does WSJT-X know how to deal with this for the re-scan for B4
status?
Or do I first need to edit my full ADIF log and make each QSO one
long horizontal
line ending in <eor>, before I place it in the wsjtx log directory
and rename it to
wsjtx_log.adi?
2. Using the latest pre-release for wsjtx v2.7-rc6, when I go into
SETTINGS -> COLORS, and click the rescan ADIF log button, there is no
feedback (unless I am missing something). I tested after rescan,
and tried a few
QSOs. For two QSOs in search and pounce, the band activity window
did NOT show
that I worked them before. However, my logging software in both QSOs
showed I had
worked each callsign 2 or 3 times before. Other QSOs properly showed
worked B4
status. So something is incomplete for worked B4 status.
QUESTION:
What does the rescan actually do? Are there some changes added to
the log file,
or is some data written to another file? I would like to know what
to look for, so I
can diagnose this issue with worked-B4 status.
Sincere Thanks,
Neal
N6YFM
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
