Log4OM uploading QSOs that are LOTW duplicates

Post Reply
N4APR
New user
Posts: 1
Joined: 20 May 2020, 18:08

Log4OM uploading QSOs that are LOTW duplicates

Post by N4APR »

Log4OM V2 potential problems handling the uploading of QSOs to LOTW when the QSOs have already been loaded to LOTW by a different Application

If only a single Call Sign’s QSOs are uploaded…all works well,, (Did not try more than two QSOs for the call… 11 QSOs for the call may be a problem as LOTW may go into "suppression" mode.)

If multiple duplicate calls are uploaded, once LOTW goes into “suppression” mode (after 10th duplicate), Log4OM ceases action. In “suppression” mode LOTW does not reply for each QSO.

Due to LOTW choice to “suppress” further processing of a portion of the calls (after 10th), Log4OM fails to take any action…Likely because it does not know which calls to work with.

Log4OM stops processing and continues to think the link to LOTW is still active..

Attached is the log4OM temp files listing, Upload screen, and the corresponding LOTW activity Record
for a of 96 call signs.


Log4OM Temp file
Screen Shot 2021-08-27 at 10.08.35 PM.png
Screen Shot 2021-08-27 at 10.08.35 PM.png (53.27 KiB) Viewed 1153 times
Shown on LogOM screen
Screen Shot 2021-08-27 at 10.03.02 PM.png
Screen Shot 2021-08-27 at 10.03.02 PM.png (54.41 KiB) Viewed 1153 times

Logbook Activity RecordLogbook Activity Record

Date/Time: 2021-08-28 03:09:00
User: n4apr
File: LOTW_UPLOAD_20210828020237.tq8
Messages:
2021-08-28 03:09:00 LOTW_QSO: Processing file: 20210828025454.24947
2021-08-28 03:09:00 LOTW_QSO: User file: LOTW_UPLOAD_20210828020237.tq8
2021-08-28 03:09:00 LOTW_QSO: Certificate found for N4APR - UNITED STATES OF AMERICA (291)
2021-08-28 03:09:00 LOTW_QSO: WARNING in tSTATION record field ITUZ: ITU value "6" treated as "08"
2021-08-28 03:09:00 LOTW_QSO: QSO duplicates existing record, ignored: 2021-07-12 15:57:45Z N4APR KF0AIJ 20M FT8
2021-08-28 03:09:00 LOTW_QSO: QSO duplicates existing record, ignored: 2021-07-12 19:37:45Z N4APR VE3WWR 17M FT8
2021-08-28 03:09:00 LOTW_QSO: QSO duplicates existing record, ignored: 2021-07-12 19:44:45Z N4APR OX3LX 17M FT8
2021-08-28 03:09:00 LOTW_QSO: QSO duplicates existing record, ignored: 2021-07-12 19:49:30Z N4APR HC3RJ 17M FT8
2021-08-28 03:09:00 LOTW_QSO: QSO duplicates existing record, ignored: 2021-07-12 19:51:45Z N4APR W1AW/KL7 17M FT8
2021-08-28 03:09:00 LOTW_QSO: QSO duplicates existing record, ignored: 2021-07-12 19:55:15Z N4APR OK1UU 17M FT8
2021-08-28 03:09:00 LOTW_QSO: QSO duplicates existing record, ignored: 2021-08-21 18:47:15Z N4APR Y5NA 20M SSB
2021-08-28 03:09:00 LOTW_QSO: QSO duplicates existing record, ignored: 2021-08-21 19:03:44Z N4APR W1FJ 20M SSB
2021-08-28 03:09:00 LOTW_QSO: QSO duplicates existing record, ignored: 2021-08-21 19:08:28Z N4APR K4ZW 40M SSB
2021-08-28 03:09:00 LOTW_QSO: QSO duplicates existing record, ignored: 2021-08-21 19:11:51Z N4APR KW8N 40M SSB
2021-08-28 03:09:00 LOTW_QSO: [Additional existing-record warnings suppressed]
2021-08-28 03:09:01 LOTW_QSO: Successfully processed 96 QSO records in 1.139707 seconds
2021-08-28 03:09:01 LOTW_QSO: 96 records were duplicates
2021-08-28 03:09:01 LOTW_QSO: No errors encountered


Log4OM stops processing and continues to think the link to LOTW is still active..
Sent fields do not get changed from "Requested" to "Sent".
User avatar
IW3HMH
Site Admin
Posts: 2926
Joined: 21 Jan 2013, 14:20
Location: Quarto d'Altino - Venezia (ITA)
Contact:

Re: Log4OM uploading QSOs that are LOTW duplicates

Post by IW3HMH »

That's a weird thing... why LOTW enters a "suppression mode" if the output is intended to deal with an application?
Crap...
i'll search for a solution, thanks for the info
Daniele Pistollato - IW3HMH
Post Reply