Looks to me like you logged it twice.The times reset after you log it so
logging it a 2nd time without a QSO will use the current time in both.
de Mike W9MDB
On Thursday, September 21, 2017, 10:00:17 AM CDT, Dan Malcolm
<k4...@outlook.com> wrote:
I just noticed that QSO start/stop times are getting logged more as logging
times rather than the times encompassing the QSO. The QSO shown in the screen
capture wasn’t logged until a few minutes later. Checking the Log4OM entry,
both start & stop times were 14:44:00. The WSJT-X log shows two lines, since I
didn’t have Log4OM running the first logging attempt (my bad):
2017-09-21,14:30:15,2017-09-21,14:31:15,VE1JS,FN64,14.074968,FT8,+03,-02,,,
2017-09-21,14:44:13,2017-09-21,14:44:13,VE1JS,FN64,14.074968,FT8,+03,-02,,,
The first line has the correct start/stop times, but the second line is
obviously wrong, and that’s what got sent to Log4OM.
__________
Dan – K4SHQ
------------------------------------------------------------------------------
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
------------------------------------------------------------------------------
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
