WSJT and duplicate QSO's

Need help? - Post here and we will find a solution for you.
Post Reply
User avatar
G4POP
Moderator
Posts: 5568
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

WSJT and duplicate QSO's

Post by G4POP » 11 Sep 2017, 11:01

Log4OM users need to be aware that WSJT and possibly other JT65 programs are logging to their internal WSJT logbook using the end time as the start time in their ADIF file.

The ADIF format provides facility for Time on and Time off but WSJT and similar programs are not using those fields in the conventional manner.

JTAlert however logs your WSJT-X, JT65, FT8 etc QSO's to Log4OM using the correct Time on and Time off

Up to this point everything is fine and dandy!

The problem with duplicates being imported into Log4OM from WSJT software is caused when a user perhaps makes some contacts without JTAlert or Log4OM running and decides later to update his Log4OM logbook by importing the WSJT ADIF Log file.

Because the ADIF file from the WSJT software uses the end time as the start time Log4OM cannot match the data and has to assume these are different QSO's and creates duplicates


THE MESSAGE IS THIS:

LOG4OM REQUIRES AN EXACT MATCH OF START TIME, DATE, BAND, MODE AND CALL SIGN - NO MATCH AND YOU WILL GET DUPLICATES


So please ensure that you only import QSO's from WSJT software that do not already exist in your Log4OM logbook! This is easily achieved by editing the WSJT ADIF file prior to import using either Windows Notepad or ADIFMaster software

Users could of course request that the authors of these other programs start to apply the ADIF format correctly and use the actual start and end times the same as the excellent JTAlert software from VK3AMA Laurie
73 Terry G4POP

Post Reply