Hi Terry - the moron on this end did not think that there would be a problem (as there had never been one before) so no backup to fall back on. Do you suppose that I can remove *all* FT8 contacts from the log and re-import the WSJT-X adif file to get the right times showing?
BTW, found the reason ...
Search found 3 matches
- 29 Jan 2019, 17:29
- Forum: User Support
- Topic: Odd log entry duplication issue with WSJT-X
- Replies: 7
- Views: 4487
- 29 Jan 2019, 16:57
- Forum: User Support
- Topic: Odd log entry duplication issue with WSJT-X
- Replies: 7
- Views: 4487
Re: Odd log entry duplication issue with WSJT-X
Getting a closer look, it appears that when WSJT-X sends a record to Log4OM, it seems to send the time as "HH:MM:00" rather than the actual seconds on the QSO, so when the import is done Log4OM sees all the entries in the WSJT-X log as new.
Charlie (N4NVD
Charlie (N4NVD
- 29 Jan 2019, 16:18
- Forum: User Support
- Topic: Odd log entry duplication issue with WSJT-X
- Replies: 7
- Views: 4487
Odd log entry duplication issue with WSJT-X
Hi there. I occasionally get a failure to send a log entry from WSJT-X to Log4OM. The logs *are* maintained on the WSJT-X adif file, so I tried to integrate my missing contacts into Log4OM by doing an import of the WSJT-X adif file. Evidently, there's a discrepancy (in seconds) in the log entry ...
