LoTW Mystery

[K1JX]

Something new!

Starting today, when I click LoTW in, I get a perfectly good download of LoTW entries.

The difference is that now, I get the very same download of LoTW entries every time. It's as if the LoTW server doesn't know that it's already downloaded those entries.

The LoTW site has been acting funny of late, so the problem could be at their end.

Has anybody else seen this? Anything I can fix at my end?

[DL2RUM]

Here the same.
I noticed this behaviour before temporary for a short time. But now it persists for few days. I guess there is a problem on the server side.
In the downloaded file LoTW provides a special ADIF tag <APP_LoTW_LASTQSL>. This should show the date and time, when the server has received the last confirmation for your callsign. This date is saved by RUMlog and the next query asks for confirmations after this time only. See the example which I have just downloaded: It shows QSOS (J69DS, 9Y4DG) definitely made and confirmed after the LASTQSL date.

<APP_LoTW_LASTQSL:19>2020-03-30 21:52:28
<QSO_DATE:8>20200331
<QSLRDATE:8>20200331

I will observe this for few more days and drop a note later to the ARRL.

You could manually edit the Last LoTW QSL In Date in the LoTW Preferences.

Code: Select all

ARRL Logbook of the World Status Report
Generated at 2020-04-01 09:33:34
for dl2rum
Query:
   OWNCALL: DL2RUM
   QSL ONLY: YES
   QSL SINCE: 2020-03-30 21:52:29

<PROGRAMID:4>LoTW
<APP_LoTW_LASTQSL:19>2020-03-30 21:52:28

<APP_LoTW_NUMREC:1>4

<eoh>

<CALL:5>J69DS
<BAND:3>17M
<FREQ:8>18.10160
<MODE:3>FT8
<APP_LoTW_MODEGROUP:4>DATA
<QSO_DATE:8>20200331
<TIME_ON:6>172500
<QSL_RCVD:1>Y
<QSLRDATE:8>20200331
<DXCC:2>97
<COUNTRY:11>SAINT LUCIA
<APP_LoTW_DXCC_ENTITY_STATUS:7>Current
<PFX:3>J69
<APP_LoTW_2xQSL:1>Y
<IOTA:6>NA-108
<GRIDSQUARE:6>FK94MA
<CQZ:2>08
<ITUZ:2>11
<eor>

<CALL:5>9Y4DG
<BAND:3>17M
<FREQ:8>18.10140
<MODE:3>FT8
<APP_LoTW_MODEGROUP:4>DATA
<QSO_DATE:8>20200331
<TIME_ON:6>173100
<QSL_RCVD:1>Y
<QSLRDATE:8>20200331
<DXCC:2>90
<COUNTRY:17>TRINIDAD & TOBAGO
<APP_LoTW_DXCC_ENTITY_STATUS:7>Current
<PFX:3>9Y4
<APP_LoTW_2xQSL:1>Y
<GRIDSQUARE:6>FK90GF
<CQZ:2>09
<ITUZ:2>11
<eor>

<CALL:5>VP8PJ
<BAND:3>40M
<FREQ:7>7.05690
<MODE:3>FT8
<APP_LoTW_MODEGROUP:4>DATA
<QSO_DATE:8>20200229
<TIME_ON:6>210814
<QSL_RCVD:1>Y
<QSLRDATE:8>20200331
<DXCC:3>238
<COUNTRY:20>SOUTH ORKNEY ISLANDS
<APP_LoTW_DXCC_ENTITY_STATUS:7>Current
<PFX:3>VP8
<APP_LoTW_2xQSL:1>Y
<IOTA:6>AN-008
<GRIDSQUARE:4>GC79
<CQZ:2>13
<ITUZ:2>73
<eor>

<CALL:5>ON5SV
<BAND:3>40M
<FREQ:7>7.04400
<MODE:4>RTTY
<APP_LoTW_MODEGROUP:4>DATA
<QSO_DATE:8>20170701
<TIME_ON:6>185320
<QSL_RCVD:1>Y
<QSLRDATE:8>20200331
<DXCC:3>209
<COUNTRY:7>BELGIUM
<APP_LoTW_DXCC_ENTITY_STATUS:7>Current
<PFX:3>ON5
<APP_LoTW_2xQSL:1>Y
<GRIDSQUARE:6>JO10WK
<CQZ:2>14
<ITUZ:2>27
<eor>

<APP_LoTW_EOF>

[K1JX]

OK. I guess they are having their share of bumps with everything that is going on. The "Find Call" service on the LoTW web page has been out of order for a few days now, at least for me.

Thanks!

[K1JX]

I manually set the last download time to earlier this morning when I checked LoTW this morning.

Just now, LoTW in got me 526 LoTW verifications. Most were not new.

The time in LoTW Prefs always gets reset to 31 3 2020 whenever there is an actual download. Which I then fix manually.

I think they have some server problems...

[DL2RUM]

No answer from the ARRL yet, but it is working correct again!

[K1JX]

I just tried an "LoTW in" update. The date and time as posted to LoTW Prefs is now correct, but I got 30 verifications. Most are not new.

Perhaps some sort of buffer that's fixed now?

Guess we'll see!

[DL2RUM]

It will take affect with the next download.