QRZ automatic upload

[G6UQI]

I have installed V 1.18.0.0 and now use the automatic facility to upload my QSO's to QRZ.com but I have spotted an anomaly. Prior to V 1.18.0.0 I had to upload my QSO's via an adif file upload which when uploaded shows the QSO start time in the time column in my QRZ logbook. Yesterday I uploaded my logbook to QRZ to update things like LOTW and eQSL's received and found that the Log4OM automatic upload displays the QSO end time in the time column of my QRZ logbook and hence all QSO's since the upgrade to V 1.18.0.0 were duplicated in my QRZ logbook. I have looked through what documentation I could find and cannot find a solution to stop the duplication of QSO's. Am I missing something fundamental or is this an undocumented feature? Any help would be appreciated.

[G4POP]

The new QRZ upload only automatically uploads QSO's as they are logged so I can't see how you are getting duplicates!

Please explain in detail what steps you are following for upload

[G6UQI]

Hi Terry, it's not the automatic upload that is causing the duplicates, that works perfectly and uploads my QSO's as I log them. The duplication is caused if I subsequently upload an ADIF file to my QRZ logbook, created by Log4OM, to update items held in my QRZ logbook like eQSL's received etc. The QSO's automatically uploaded by Log4OM show the QSO 'end' time in the Time column of my QRZ logbook. An ADIF file upload shows the QSO 'start' time in the Time column of the QRZ logbook and hence if the times are significantly different, by several minutes, QRZ treats them as two different QSO's even if all the details are exactly the same, hence the duplication. I would hazard a guess that the QSO 'start' and 'end' times are sent differently in the automatic upload file to those sent in the ADIF file and that is why the QRZ logbook displays 'end' time for the auto upload and 'start' time for the ADIF upload. I hope that now makes sense!

[G4POP]

Are your QSO's normal SSB QSO's recorded in Log4OM or are they QSO's sent to Log4OM by FLDigi

I have just tested using my own logbook and the last four QSO's that I have recorded and can't find a problem

Below are a few images

1. My log entries
2. The result of an ADIF export of the last 4 entries displayed in ADIFMaster
3. The G4POP QRZ Logbook list showing the same QSO's as they were uploaded automatically and live as the QSO's were logged in Log4OM
4. The G4POP QRZ logbook list after a manual ADIF upload of those same four QSO's
5. The ADIF upload list to prove the upload was done

You will notice the start times are identical as are the end times and there are no duplicates in the QRZ logbook subsequent to the manual ADIF upload

My actual ADIF export of the 4 QSO's is also attached for you to check the results yourself

..
..

[G6UQI]

Hi Terry, sorry to confuse you and my last reply had dissipated into the ether so I'll try again. I've resolved the problem and it was self induced. I'm using WSJT-X and JTAlert-X to log my JT-65/JT-9 QSO's via Log4OM. Log4OM defaults to a 1 minute QSO time, so after I press the log button in WSJT-X and fill in the missing details in the popup I then go into Log4OM and reset the start time to the actual time the QSO started and normally add a QSL message and a request for eQSL and LoTW. Unfortunately by that time Log4OM has done it's thing and sent the QSO details far and wide. I appreciate that the software doesn't do a bulk upload to QRZ. I do that by creating an ADIF file after I've received several eQSL's or validations from LoTW to upload to QRZ so that the operators who use QRZ logbooks can see the results.

[G4POP]

The real issue here is that unlike LOTW, EQSL, HRDLOG and most logging software QRZ only allows a 1 minute time error where others allow 2, 3, 5, 10, 15 & 30 minute margins.

Also updating QSO's with QSL information should be a merge not an overwrite, which is what QRZ do

I am pleased that you have now identified your problem