Topics

L32 Log sync problem with WSJT-X UDP logging


Alex Dolgosh
 

I just added the LOTWsync utility, and  it has been working seamlessly - except it would randomly miss an automatic LOTW upload of a new Q, which was automatically logged from WSJT-X via UDP.

The miss-outs were instantly recognizable since weren’t flagged as sent. I was doing an automatic Logger32 log backup after every QSO, so I am suspecting a timing issue.  Now I just automatically perform a backup on Logger32 shutdown, and everything is being handled properly after only this change.

Has anyone else seen these symptoms?  Rick?

Al - K8EUR 


On Jan 11, 2021, at 12:36 PM, Gary Hinson <Gary@...> wrote:

Hello OK1TK

 

I get ‘QSO not found’ errors during the LoTW sync process, but very rarely – mostly (if I remember correctly) the issues relate to stations signing, worked, logged and uploaded as portables, but confirmed without the /P.   Anyway, the point is that those situations are rare – maybe 10 out of my 70,000 LoTW confirmations.

 

As you are getting lots of them, that clearly suggests something going wrong with the process.

 

The good news is that your LoTW confirmation rate is about right, meaning the problem does not appear to be your original log: roughly half of your signed and uploaded QSOs are matched, so you and your QSO partners agree on the fundamental details of those logged QSOs (i.e, both callsigns, dates & times within tolerance, bands and modes).

 

Beyond that, it is hard to tell why the sync process isn’t matching up the confirmations with the QSOs in your log.  If you say the QSOs are there in the log and should be found, I would suggest looking very closely at BOTH callsigns – the stations you worked AND your ‘Operator’ callsign.  Are there any differences?

 

Perhaps you could give us some examples of the QSOs in question e.g. view the BAD.ADI file in ADIFmaster and give us a screen shot of that, plus screen shots of some of the QSOs in your log that are not being found.

 

73 GL

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ok1tk
Sent: 11 January 2021 22:43
To: hamlogger@groups.io
Subject: [hamlogger] L32 LoTW problem

 

Hi Guys,

I started to use LoTW several days ago for my personal callsign and for club callsign. For both callsignes I use separate Logbooks in L32. My callsign = 1 operator, club = 3 ops now including me (I found, that the export file for LoTW is not happy if my callsign is used as op for the club logs so I changed to my name).

But all the upload to LoTW are done and the current state on LoTW is:

OK1TK
750 QSO
256 QSL

OK1RJO
117QSO
56QSL

When I download the file FROM LoTW and I am tring to SYNC it wit L32 I am getting the following errors:

OK1TK
10 errors (BAD.ADI syas the QSO was not found in logbook for all the 10 QSO)

OK1RJO
56 errors (BAD.ADI syas the QSO was not found in logbook for all the 10 QSO) - so all QSL

The QSO from BAD.ADI exists in the Logbooks and can be found.

The through is and I think it migh be my problem, I updated some LoTW QSL Sent/Recievd statuses in Logger manualy before I found the possibility to do it via the file.

Any idea how to slove this issue ? It seems it will not affect another QSO but not sure with that.




--
73! OK1TK


Rick Ellison
 

I have not seen this but have not really been doing much radio. I will check it out tho. When the qso gets logged Logger32 sends a message to LogSync. So it should not matter where the qso is being logged from.

Will let you know what I find..

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Alex Dolgosh via groups.io
Sent: Monday, January 11, 2021 3:47 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] L32 Log sync problem with WSJT-X UDP logging

 

I just added the LOTWsync utility, and  it has been working seamlessly - except it would randomly miss an automatic LOTW upload of a new Q, which was automatically logged from WSJT-X via UDP.

 

The miss-outs were instantly recognizable since weren’t flagged as sent. I was doing an automatic Logger32 log backup after every QSO, so I am suspecting a timing issue.  Now I just automatically perform a backup on Logger32 shutdown, and everything is being handled properly after only this change.

 

Has anyone else seen these symptoms?  Rick?

 

Al - K8EUR 


On Jan 11, 2021, at 12:36 PM, Gary Hinson <Gary@...> wrote:

Hello OK1TK

 

I get ‘QSO not found’ errors during the LoTW sync process, but very rarely – mostly (if I remember correctly) the issues relate to stations signing, worked, logged and uploaded as portables, but confirmed without the /P.   Anyway, the point is that those situations are rare – maybe 10 out of my 70,000 LoTW confirmations.

 

As you are getting lots of them, that clearly suggests something going wrong with the process.

 

The good news is that your LoTW confirmation rate is about right, meaning the problem does not appear to be your original log: roughly half of your signed and uploaded QSOs are matched, so you and your QSO partners agree on the fundamental details of those logged QSOs (i.e, both callsigns, dates & times within tolerance, bands and modes).

 

Beyond that, it is hard to tell why the sync process isn’t matching up the confirmations with the QSOs in your log.  If you say the QSOs are there in the log and should be found, I would suggest looking very closely at BOTH callsigns – the stations you worked AND your ‘Operator’ callsign.  Are there any differences?

 

Perhaps you could give us some examples of the QSOs in question e.g. view the BAD.ADI file in ADIFmaster and give us a screen shot of that, plus screen shots of some of the QSOs in your log that are not being found.

 

73 GL

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ok1tk
Sent: 11 January 2021 22:43
To: hamlogger@groups.io
Subject: [hamlogger] L32 LoTW problem

 

Hi Guys,

I started to use LoTW several days ago for my personal callsign and for club callsign. For both callsignes I use separate Logbooks in L32. My callsign = 1 operator, club = 3 ops now including me (I found, that the export file for LoTW is not happy if my callsign is used as op for the club logs so I changed to my name).

But all the upload to LoTW are done and the current state on LoTW is:

OK1TK
750 QSO
256 QSL

OK1RJO
117QSO
56QSL

When I download the file FROM LoTW and I am tring to SYNC it wit L32 I am getting the following errors:

OK1TK
10 errors (BAD.ADI syas the QSO was not found in logbook for all the 10 QSO)

OK1RJO
56 errors (BAD.ADI syas the QSO was not found in logbook for all the 10 QSO) - so all QSL

The QSO from BAD.ADI exists in the Logbooks and can be found.

The through is and I think it migh be my problem, I updated some LoTW QSL Sent/Recievd statuses in Logger manualy before I found the possibility to do it via the file.

Any idea how to slove this issue ? It seems it will not affect another QSO but not sure with that.




--
73! OK1TK


Virus-free. www.avast.com