Log4OM

Might not be related to any issue in Log4OM, but still curious to find an explanation.
I came across a Cluster Spot today of S01WS indicating this call to be a LOTW user.

His QRZ.com profile clearly indicates that he is not an LOTW user.
There must be an error somewhere in the data chain.

HB9VQQ wrote: 24 Jan 2020, 13:13 Might not be related to any issue in Log4OM, but still curious to find an explanation.
I came across a Cluster Spot today of S01WS indicating this call to be a LOTW user.

I see similar cases from time to time. There are a couple of possible reasons. A LoTW certificate has been issued for the callsign but never used, or the last time used exceeded the period set in the logging software.

I have not explored this part of Log4OM yet, but with other packages, one can set 'active' status periods. Let's say, if the DX has not uploaded to LoTW in the last 6 months, consider it inactive.

Lastly the info on QRZ, or whatever page, may be outdated.

73 de Vince

I do not think QRZ has any information of value. That is a user defined option.

If you want real info go to LOTW and check the call.

kd0zv wrote: 24 Jan 2020, 14:04 If you want real info go to LOTW and check the call.

Even this does not mean one will see it confirmed 'automatically' and/or immediately.

There are cases where a QSO is uploaded months after it took place. If one wants it sooner, a 'donation' may be 'needed'.

73 de Vince

va3vf wrote: 24 Jan 2020, 14:12

kd0zv wrote: 24 Jan 2020, 14:04 If you want real info go to LOTW and check the call.

Even this does not mean one will see it confirmed 'automatically' and/or immediately.

There are cases where a QSO is uploaded months after it took place. If one wants it sooner, a 'donation' may be 'needed'.

73 de Vince

No of course not, but it shows the station is a LOTW user and you can tell if they have uploaded recently or not since 2006.

I mean its really the best LOTW evaluator there is.

kd0zv wrote: 24 Jan 2020, 14:20 I mean its really the best LOTW evaluator there is.

Agreed.

Thanks Vince,

The question is how is Log4OM enumerating if a call is a LOTW user ?

I guess the call is checked against the local lotw.txt file which by default is downloaded every 24hrs by the Log4OM scheduler. There I can find a reference to my example with call S01WS, which shows a last upload date of 2020-01-14. So all ok, just funny that S01WS claims not to use LOTW at all on his qrz.com page.

I picked a bad example which confused me a bit. All fine

73
Roland

Well regarding this station, I have worked them a half dozen times and never got LOTW confirmation but I think its just recent they started doing it. I plan to work them again on CW in hopes I make the log as Western Sahara is not a confirmed country.

Note to the Log4OM team. I would love it if the last upload date could be displayed in the logbook along with LOTW USER and save me a trip to LOTW site.

kd0zv wrote: 24 Jan 2020, 14:37 Well regarding this station, I have worked them a half dozen times and never got LOTW confirmation but I think its just recent they started doing it. I plan to work them again on CW in hopes I make the log as Western Sahara is not a confirmed country.

Note to the Log4OM team. I would love it if the last upload date could be displayed in the logbook along with LOTW USER and save me a trip to LOTW site.

I have only one contact with this station, and it's a good one, as it matches on ClubLog, but no LoTW confirmation yet.

Yes, the more info Log4OM could extract from the LoTW file, and make it available, the better.

73 de Vince.

some rather old entries in the lotw.txt which is downloaded from LOTW

But it seems not every call in lotw.txt is automatically considered to be "LOTW user" by Log4OM. I just did a test with spot simulator
Just trying to understand the internal mechanism behind that