On 12/02/2017 05:42 PM, John Broughton wrote: Hi John & all,
> My procedure with the .adi file is that I rename it every day > by adding the date to it, e.g. wsjtx_log12-2-2017 will be today's > file's name. I then save it. I began that when I started working > JT65 in Sept. 2015 and kept doing it when I started working FT8 in > Oct. this year. > > That makes it easy to upload to LoTW as I just upload the entire > file every day. Ditto when uploading into eQSL and importing to my > HRD log. I keep my QRZ log in sync with the other logs by simply > downloading my LoTW log to it. Please note that QSO entries in an ADIF file don't remain unchanged after the end of the QSO. The most important changes are the insertion of the received confirmations (paper QSL cards, LoTW, eQSL). But some other additions are not unusual, e.g. QSL_VIA and QSL_SENT. In my opinion, having a log file for every day make it more difficult to perform such insertions. Further, if you want to filter the log in order to find possible confirmations for an award, multiple files make the job harder. At my station, when using WSJT-X and after every QSO, I filter out the last entry of the log file and I add an ADIF header. Then I send this miniaturized ADIF file to eQSL using "curl". For this purpose, I use an very simple batch file. This is similar to the behaviour which can be enabled in fldigi, but which is absent in WSJT-X. Of course, the sent QSO record in the ADIF file is then only the current state of this record. Further additions and changes will probably occur in the locally saved file at a later time in order to make the state current. Best wishes, Claude (DJ0OT) ------------------------------------------------------------------------------ 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 wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
