Topics

L32 LoTW problem


ok1tk
 

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


Gary Hinson
 

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


w5jmw
 

But in lotw to upload.Are you using the same certificate ? If so you may need to set up different accounts so they do notuse the same certificate..john

On 2021-01-11 03:43, ok1tk wrote:
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
Links:
------
[1] https://groups.io/g/hamlogger/message/81940
[2] https://groups.io/mt/79592270/796390
[3] https://groups.io/g/hamlogger/post
[4] https://groups.io/g/hamlogger/editsub/796390
[5] https://groups.io/g/hamlogger/leave/defanged


ok1tk
 

Hello Gary,

thank you for your reply. It is strange for me, because the files for LoTW are generated by Logger32 for both callsigns OK1TK and OK1RJO as well. The only difference is, that for my LoggBook OK1TK I use as operator my calsing OK1TK. For club callsign OK1RJO we use our first names (Jakub, Ondra, Tomas) for the "operator" field in Logger32.
 
What I found out this weekend is that all QSLs for OK1RJO are marked in BAD.ADI as "QSO not found in logbook". We received some new QSLs and they are not accepted by Logger32 as well. For my callsign it is stil the same 10 QSL which are not "found" in my LogBook.
 
My suspiction is that I modifided several QSO in my (OK1TK) logbook manually (the fields LoTW QSL sent/received). And it might be those 10 which are not accepted when uploding the file generated on LoTW webpage.
 
At the beginngin I updated all the QSO in OK1RJO logbook manualy for LoTW Sent and Received.
 
Would it be helpfull if I send my ADIF files and the ADIF genrated from LoTW to compare it ?
--
73! OK1TK


ok1tk
 

I hava separate certificates. One is for OK1TK and one for OK1RJO. The certificates shouldn't cause the problem.
--
73! OK1TK


ok1tk
 

Hello Garry,

I compared the BAD.ADI file and my loogbook.adi files and can't find anything. Pls, see below. The first row is BAD.ADI and the second is my Logbook.ADI export.

OK1TK
BAD: QSO not found in Logbook:  <APP_LoTW_OWNCALL:5>OK1TK<STATION_CALLSIGN:5>OK1TK<CALL:6>UA3RLE<BAND:3>40M<FREQ:7>7.07459<FREQ_RX:7>7.07598<MODE:3>FT8<APP_LoTW_MODEGROUP:4>DATA<QSO_DATE:8>20200118<APP_LoTW_RXQSO:19>2021-01-08 07:45:03 // QSO record inserted/modified at LoTW<TIME_ON:6>155300<APP_LoTW_QSO_TIMESTAMP:20>2020-01-18T15:53:00Z // QSO Date & Time; ISO-8601<QSL_RCVD:1>Y<QSLRDATE:8>20210108<APP_LoTW_RXQSL:19>2021-01-08 07:45:03 // QSL record matched/modified at LoTW<DXCC:2>54<COUNTRY:15>EUROPEAN RUSSIA<APP_LoTW_DXCC_ENTITY_STATUS:7>Current<PFX:3>UA3<APP_LoTW_2xQSL:1>Y<GRIDSQUARE:6>LO02RR<STATE:2>TB // Tambovskaya oblast' (Tambov Oblast)<CQZ:2>16<ITUZ:2>29<eor>
LOG: <DISTANCE:7>1885.00 <BAND:3>40M <CALL:6>UA3RLE <COMMENT:10>/P, OK9ZAM <CONT:2>EU <CQZ:2>16 <DXCC:2>54 <FREQ:8>7.074590 <GRIDSQUARE:6>LO02rr <ITUZ:2>29 <MODE:3>FT8 <NAME:18>Vasiliy Pochechuev <NOTES:24>Yaesu FT-817ND, GR5W, 5W <OPERATOR:7>OK1TK/P <PFX:3>UA3 <QSL_SENT:1>Y <QSLSDATE:8>20210110 <QSO_DATE:8:D>20200118 <TIME_ON:6>155300 <QTH:17>Tambov, Tb 392020 <RST_RCVD:3>-09 <RST_SENT:3>-11 <TIME_OFF:6>155300 <TX_PWR:1>5 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y <APP_LOGGER32_QSO_NUMBER:2>83 <FREQ_RX:8>7.075980 <COUNTRY:15>European Russia <APP_LOGGER32_LAT:16>52.7291666666667 <APP_LOGGER32_LNG:17>-41.4583333333333 <EOR>
 
BAD: QSO not found in Logbook:  <APP_LoTW_OWNCALL:5>OK1TK<STATION_CALLSIGN:5>OK1TK<CALL:6>RX3ASP<BAND:3>40M<FREQ:7>7.07619<MODE:3>FT8<APP_LoTW_MODEGROUP:4>DATA<QSO_DATE:8>20200119<APP_LoTW_RXQSO:19>2021-01-08 07:45:03 // QSO record inserted/modified at LoTW<TIME_ON:6>183700<APP_LoTW_QSO_TIMESTAMP:20>2020-01-19T18:37:00Z // QSO Date & Time; ISO-8601<QSL_RCVD:1>Y<QSLRDATE:8>20210108<APP_LoTW_RXQSL:19>2021-01-08 07:45:03 // QSL record matched/modified at LoTW<DXCC:2>54<COUNTRY:15>EUROPEAN RUSSIA<APP_LoTW_DXCC_ENTITY_STATUS:7>Current<PFX:3>RX3<APP_LoTW_2xQSL:1>Y<GRIDSQUARE:6>KO85VT<STATE:2>MA // Moskva (Moscow)<CQZ:2>16<ITUZ:2>29<eor>
BAD: <DISTANCE:7>1679.00 <BAND:3>40M <CALL:6>RX3ASP <COMMENT:10>/P, OK9ZAM <CONT:2>EU <CQZ:2>16 <DXCC:2>54 <FREQ:8>7.076190 <GRIDSQUARE:6>KO85vt <ITUZ:2>29 <MODE:3>FT8 <NAME:14>Yury Sarkisyan <NOTES:24>Yaesu FT-817ND, GR5W, 5W <OPERATOR:7>OK1TK/P <PFX:3>RX3 <QSL_SENT:1>Y <QSLSDATE:8>20210110 <QSO_DATE:8:D>20200119 <TIME_ON:6>183700 <QTH:26>Moscow, 15th Parkovaya Str <RST_RCVD:3>-01 <RST_SENT:3>-04 <TIME_OFF:6>183800 <TX_PWR:1>5 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y <APP_LOGGER32_QSO_NUMBER:3>119 <FREQ_RX:8>7.076190 <COUNTRY:15>European Russia <APP_LOGGER32_LAT:7>55.8125 <APP_LOGGER32_LNG:17>-37.7916666666667 <EOR>
 
BAD: QSO not found in Logbook:  <APP_LoTW_OWNCALL:5>OK1TK<STATION_CALLSIGN:5>OK1TK<CALL:5>M0GEB<BAND:3>30M<FREQ:8>10.13770<FREQ_RX:8>10.13640<MODE:3>FT8<APP_LoTW_MODEGROUP:4>DATA<QSO_DATE:8>20200119<APP_LoTW_RXQSO:19>2021-01-08 07:45:03 // QSO record inserted/modified at LoTW<TIME_ON:6>114700<APP_LoTW_QSO_TIMESTAMP:20>2020-01-19T11:47:00Z // QSO Date & Time; ISO-8601<QSL_RCVD:1>Y<QSLRDATE:8>20210108<APP_LoTW_RXQSL:19>2021-01-08 07:45:03 // QSL record matched/modified at LoTW<DXCC:3>223<COUNTRY:7>ENGLAND<APP_LoTW_DXCC_ENTITY_STATUS:7>Current<PFX:2>M0<APP_LoTW_2xQSL:1>Y<IOTA:6>EU-005<GRIDSQUARE:6>IO80DV<CQZ:2>14<ITUZ:2>27<eor>
LOG: <DISTANCE:7>1284.00 <BAND:3>30M <CALL:5>M0GEB <COMMENT:10>/P, OK9ZAM <CONT:2>EU <CQZ:2>14 <DXCC:3>223 <FREQ:9>10.137700 <GRIDSQUARE:6>IO80dv <ITUZ:2>27 <MODE:3>FT8 <NAME:14>Graham Beesley <NOTES:24>Yaesu FT-817ND, GR5W, 5W <OPERATOR:7>OK1TK/P <PFX:2>M0 <QSL_SENT:1>Y <QSLSDATE:8>20210110 <QSO_DATE:8:D>20200119 <TIME_ON:6>114700 <QTH:8>Crediton <RST_RCVD:3>-11 <RST_SENT:3>-10 <TIME_OFF:6>115100 <TX_PWR:1>5 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y <APP_LOGGER32_QSO_NUMBER:3>109 <FREQ_RX:9>10.136400 <COUNTRY:7>England <APP_LOGGER32_LAT:16>50.8958333333333 <APP_LOGGER32_LNG:16>3.70833333333334 <EOR>


OK1RJO
BAD: QSO not found in Logbook:  <APP_LoTW_OWNCALL:6>OK1RJO<STATION_CALLSIGN:6>OK1RJO<CALL:5>M7DWW<BAND:3>80M<FREQ:7>3.57457<FREQ_RX:7>3.57439<MODE:3>FT8<APP_LoTW_MODEGROUP:4>DATA<QSO_DATE:8>20210115<APP_LoTW_RXQSO:19>2021-01-16 17:31:14 // QSO record inserted/modified at LoTW<TIME_ON:6>212845<APP_LoTW_QSO_TIMESTAMP:20>2021-01-15T21:28:45Z // QSO Date & Time; ISO-8601<QSL_RCVD:1>Y<QSLRDATE:8>20210116<APP_LoTW_RXQSL:19>2021-01-16 17:31:14 // QSL record matched/modified at LoTW<DXCC:3>223<COUNTRY:7>ENGLAND<APP_LoTW_DXCC_ENTITY_STATUS:7>Current<PFX:2>M7<APP_LoTW_2xQSL:1>Y<GRIDSQUARE:6>IO83QI<CQZ:2>14<ITUZ:2>27<eor>
LOG: <DISTANCE:7>1228.00 <BAND:3>80M <CALL:5>M7DWW <CONT:2>EU <CQZ:2>14 <DXCC:3>223 <FREQ:8>3.574575 <GRIDSQUARE:6>IO83qi <ITUZ:2>27 <MODE:3>FT8 <NAME:16>Duncan C Woodall <OPERATOR:5>JAKUB <PFX:2>M7 <QSO_DATE:8:D>20210115 <TIME_ON:6>212845 <QTH:17>Runcorn, Cheshire <RST_RCVD:3>-20 <RST_SENT:3>-16 <TIME_OFF:6>213029 <eQSL_QSL_SENT:1>Y <LOTW_QSL_SENT:1>Y <APP_LOGGER32_QSO_NUMBER:3>121 <FREQ_RX:8>3.574395 <COUNTRY:7>England <APP_LOGGER32_LAT:16>53.3541666666667 <APP_LOGGER32_LNG:5>2.625 <EOR>
 
BAD: QSO not found in Logbook:  <APP_LoTW_OWNCALL:6>OK1RJO<STATION_CALLSIGN:6>OK1RJO<CALL:5>DM2HK<BAND:3>80M<FREQ:7>3.57424<FREQ_RX:7>3.57401<MODE:3>FT8<APP_LoTW_MODEGROUP:4>DATA<QSO_DATE:8>20210115<APP_LoTW_RXQSO:19>2021-01-16 17:31:13 // QSO record inserted/modified at LoTW<TIME_ON:6>211800<APP_LoTW_QSO_TIMESTAMP:20>2021-01-15T21:18:00Z // QSO Date & Time; ISO-8601<QSL_RCVD:1>Y<QSLRDATE:8>20210116<APP_LoTW_RXQSL:19>2021-01-16 17:31:13 // QSL record matched/modified at LoTW<DXCC:3>230<COUNTRY:27>FEDERAL REPUBLIC OF GERMANY<APP_LoTW_DXCC_ENTITY_STATUS:7>Current<PFX:3>DM2<APP_LoTW_2xQSL:1>Y<GRIDSQUARE:6>JO62TI<CQZ:2>14<APP_LoTW_CQZ_Inferred:1>Y // from DXCC entity<ITUZ:2>28<APP_LoTW_ITUZ_Inferred:1>Y // from DXCC entity<eor>
LOG: <DISTANCE:6>262.00 <BAND:3>80M <CALL:5>DM2HK <CONT:2>EU <CQZ:2>14 <DXCC:3>230 <FREQ:8>3.574245 <GRIDSQUARE:6>JO62ti <ITUZ:2>28 <MODE:3>FT8 <NAME:14>Hartmut Kordus <OPERATOR:5>JAKUB <PFX:3>DM2 <QSO_DATE:8:D>20210115 <TIME_ON:6>211800 <QTH:7>Zeuthen <RST_RCVD:3>-12 <RST_SENT:3>-07 <TIME_OFF:6>212059 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <APP_LOGGER32_QSO_NUMBER:3>119 <FREQ_RX:8>3.574006 <COUNTRY:27>Federal Republic of Germany <APP_LOGGER32_LAT:16>52.3541666666667 <APP_LOGGER32_LNG:7>-13.625 <EOR>
 
BAD: QSO not found in Logbook:  <APP_LoTW_OWNCALL:6>OK1RJO<STATION_CALLSIGN:6>OK1RJO<CALL:6>EA8AIN<BAND:3>40M<FREQ:7>7.07612<FREQ_RX:7>7.07493<MODE:3>FT8<APP_LoTW_MODEGROUP:4>DATA<QSO_DATE:8>20210109<APP_LoTW_RXQSO:19>2021-01-09 22:14:30 // QSO record inserted/modified at LoTW<TIME_ON:6>212046<APP_LoTW_QSO_TIMESTAMP:20>2021-01-09T21:20:46Z // QSO Date & Time; ISO-8601<QSL_RCVD:1>Y<QSLRDATE:8>20210111<APP_LoTW_RXQSL:19>2021-01-11 19:57:48 // QSL record matched/modified at LoTW<DXCC:2>29<COUNTRY:14>CANARY ISLANDS<APP_LoTW_DXCC_ENTITY_STATUS:7>Current<PFX:3>EA8<APP_LoTW_2xQSL:1>Y<IOTA:6>AF-004<GRIDSQUARE:6>IL18CQ<CQZ:2>33<ITUZ:2>36<eor>
LOG: <DISTANCE:7>3599.00 <BAND:3>40M <CALL:6>EA8AIN <CONT:2>AF <CQZ:2>33 <DXCC:2>29 <FREQ:8>7.076120 <GRIDSQUARE:6>IL18cq <ITUZ:2>36 <MODE:3>FT8 <NAME:33>Aurelio Rodriguez Concepcion Aure <OPERATOR:5>ONDRA <PFX:3>EA8 <QSO_DATE:8:D>20210109 <TIME_ON:6>212046 <QTH:22>Santa Cruz De La Palma <RST_RCVD:3>-19 <RST_SENT:3>-18 <TIME_OFF:6>212229 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <APP_LOGGER32_QSO_NUMBER:3>103 <FREQ_RX:8>7.074928 <COUNTRY:14>Canary Islands <APP_LOGGER32_LAT:7>28.6875 <APP_LOGGER32_LNG:16>17.7916666666667 <EOR>


--
73! OK1TK


Gary Hinson
 

Hello OK1TK.

 

I’ve found the problem, looking carefully at the first QSO you sent.

 

I found it by breaking out the ADIF fields to separate lines, then lining up the two records side-by-side, adding blank lines to align the common fields:

 

 

The black entries match, aside from case changes (those don’t matter).

The orange entries are missing from one record or the other, or are formatted differently (e.g. LoTW explicitly uses the ISO 8601 date and time format).

The bold red entries show the problem: LoTW believes this QSO was with OK1TK but you have logged it under OK1TK/P.  Logger32 does not consider that a match, whereas LoTW evidently does (presuming that the record on the right represents what you signed and uploaded to LoTW.

 

I’m not going to check all the other records but if I were you I would compare the operator and station_callsign fields closely.

 

73

Gary  ZL2iFB

 

PS  If it’s OK by you, I would like to use this as a worked example for the v4 User Manual.

PPS  The manual comparison process is a candidate to develop into an automated utility, if any programmers Out There are inspired/bored …

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ok1tk
Sent: 21 January 2021 02:30
To: hamlogger@groups.io
Subject: Re: [hamlogger] L32 LoTW problem

 

Hello Garry,

I compared the BAD.ADI file and my loogbook.adi files and can't find anything. Pls, see below. The first row is BAD.ADI and the second is my Logbook.ADI export.

OK1TK

BAD: QSO not found in Logbook:  <APP_LoTW_OWNCALL:5>OK1TK<STATION_CALLSIGN:5>OK1TK<CALL:6>UA3RLE<BAND:3>40M<FREQ:7>7.07459<FREQ_RX:7>7.07598<MODE:3>FT8<APP_LoTW_MODEGROUP:4>DATA<QSO_DATE:8>20200118<APP_LoTW_RXQSO:19>2021-01-08 07:45:03 // QSO record inserted/modified at LoTW<TIME_ON:6>155300<APP_LoTW_QSO_TIMESTAMP:20>2020-01-18T15:53:00Z // QSO Date & Time; ISO-8601<QSL_RCVD:1>Y<QSLRDATE:8>20210108<APP_LoTW_RXQSL:19>2021-01-08 07:45:03 // QSL record matched/modified at LoTW<DXCC:2>54<COUNTRY:15>EUROPEAN RUSSIA<APP_LoTW_DXCC_ENTITY_STATUS:7>Current<PFX:3>UA3<APP_LoTW_2xQSL:1>Y<GRIDSQUARE:6>LO02RR<STATE:2>TB // Tambovskaya oblast' (Tambov Oblast)<CQZ:2>16<ITUZ:2>29<eor>

LOG: <DISTANCE:7>1885.00 <BAND:3>40M <CALL:6>UA3RLE <COMMENT:10>/P, OK9ZAM <CONT:2>EU <CQZ:2>16 <DXCC:2>54 <FREQ:8>7.074590 <GRIDSQUARE:6>LO02rr <ITUZ:2>29 <MODE:3>FT8 <NAME:18>Vasiliy Pochechuev <NOTES:24>Yaesu FT-817ND, GR5W, 5W <OPERATOR:7>OK1TK/P <PFX:3>UA3 <QSL_SENT:1>Y <QSLSDATE:8>20210110 <QSO_DATE:8:D>20200118 <TIME_ON:6>155300 <QTH:17>Tambov, Tb 392020 <RST_RCVD:3>-09 <RST_SENT:3>-11 <TIME_OFF:6>155300 <TX_PWR:1>5 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y <APP_LOGGER32_QSO_NUMBER:2>83 <FREQ_RX:8>7.075980 <COUNTRY:15>European Russia <APP_LOGGER32_LAT:16>52.7291666666667 <APP_LOGGER32_LNG:17>-41.4583333333333 <EOR>

 

BAD: QSO not found in Logbook:  <APP_LoTW_OWNCALL:5>OK1TK<STATION_CALLSIGN:5>OK1TK<CALL:6>RX3ASP<BAND:3>40M<FREQ:7>7.07619<MODE:3>FT8<APP_LoTW_MODEGROUP:4>DATA<QSO_DATE:8>20200119<APP_LoTW_RXQSO:19>2021-01-08 07:45:03 // QSO record inserted/modified at LoTW<TIME_ON:6>183700<APP_LoTW_QSO_TIMESTAMP:20>2020-01-19T18:37:00Z // QSO Date & Time; ISO-8601<QSL_RCVD:1>Y<QSLRDATE:8>20210108<APP_LoTW_RXQSL:19>2021-01-08 07:45:03 // QSL record matched/modified at LoTW<DXCC:2>54<COUNTRY:15>EUROPEAN RUSSIA<APP_LoTW_DXCC_ENTITY_STATUS:7>Current<PFX:3>RX3<APP_LoTW_2xQSL:1>Y<GRIDSQUARE:6>KO85VT<STATE:2>MA // Moskva (Moscow)<CQZ:2>16<ITUZ:2>29<eor>

BAD: <DISTANCE:7>1679.00 <BAND:3>40M <CALL:6>RX3ASP <COMMENT:10>/P, OK9ZAM <CONT:2>EU <CQZ:2>16 <DXCC:2>54 <FREQ:8>7.076190 <GRIDSQUARE:6>KO85vt <ITUZ:2>29 <MODE:3>FT8 <NAME:14>Yury Sarkisyan <NOTES:24>Yaesu FT-817ND, GR5W, 5W <OPERATOR:7>OK1TK/P <PFX:3>RX3 <QSL_SENT:1>Y <QSLSDATE:8>20210110 <QSO_DATE:8:D>20200119 <TIME_ON:6>183700 <QTH:26>Moscow, 15th Parkovaya Str <RST_RCVD:3>-01 <RST_SENT:3>-04 <TIME_OFF:6>183800 <TX_PWR:1>5 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y <APP_LOGGER32_QSO_NUMBER:3>119 <FREQ_RX:8>7.076190 <COUNTRY:15>European Russia <APP_LOGGER32_LAT:7>55.8125 <APP_LOGGER32_LNG:17>-37.7916666666667 <EOR>

 

BAD: QSO not found in Logbook:  <APP_LoTW_OWNCALL:5>OK1TK<STATION_CALLSIGN:5>OK1TK<CALL:5>M0GEB<BAND:3>30M<FREQ:8>10.13770<FREQ_RX:8>10.13640<MODE:3>FT8<APP_LoTW_MODEGROUP:4>DATA<QSO_DATE:8>20200119<APP_LoTW_RXQSO:19>2021-01-08 07:45:03 // QSO record inserted/modified at LoTW<TIME_ON:6>114700<APP_LoTW_QSO_TIMESTAMP:20>2020-01-19T11:47:00Z // QSO Date & Time; ISO-8601<QSL_RCVD:1>Y<QSLRDATE:8>20210108<APP_LoTW_RXQSL:19>2021-01-08 07:45:03 // QSL record matched/modified at LoTW<DXCC:3>223<COUNTRY:7>ENGLAND<APP_LoTW_DXCC_ENTITY_STATUS:7>Current<PFX:2>M0<APP_LoTW_2xQSL:1>Y<IOTA:6>EU-005<GRIDSQUARE:6>IO80DV<CQZ:2>14<ITUZ:2>27<eor>

LOG: <DISTANCE:7>1284.00 <BAND:3>30M <CALL:5>M0GEB <COMMENT:10>/P, OK9ZAM <CONT:2>EU <CQZ:2>14 <DXCC:3>223 <FREQ:9>10.137700 <GRIDSQUARE:6>IO80dv <ITUZ:2>27 <MODE:3>FT8 <NAME:14>Graham Beesley <NOTES:24>Yaesu FT-817ND, GR5W, 5W <OPERATOR:7>OK1TK/P <PFX:2>M0 <QSL_SENT:1>Y <QSLSDATE:8>20210110 <QSO_DATE:8:D>20200119 <TIME_ON:6>114700 <QTH:8>Crediton <RST_RCVD:3>-11 <RST_SENT:3>-10 <TIME_OFF:6>115100 <TX_PWR:1>5 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y <APP_LOGGER32_QSO_NUMBER:3>109 <FREQ_RX:9>10.136400 <COUNTRY:7>England <APP_LOGGER32_LAT:16>50.8958333333333 <APP_LOGGER32_LNG:16>3.70833333333334 <EOR>



OK1RJO

BAD: QSO not found in Logbook:  <APP_LoTW_OWNCALL:6>OK1RJO<STATION_CALLSIGN:6>OK1RJO<CALL:5>M7DWW<BAND:3>80M<FREQ:7>3.57457<FREQ_RX:7>3.57439<MODE:3>FT8<APP_LoTW_MODEGROUP:4>DATA<QSO_DATE:8>20210115<APP_LoTW_RXQSO:19>2021-01-16 17:31:14 // QSO record inserted/modified at LoTW<TIME_ON:6>212845<APP_LoTW_QSO_TIMESTAMP:20>2021-01-15T21:28:45Z // QSO Date & Time; ISO-8601<QSL_RCVD:1>Y<QSLRDATE:8>20210116<APP_LoTW_RXQSL:19>2021-01-16 17:31:14 // QSL record matched/modified at LoTW<DXCC:3>223<COUNTRY:7>ENGLAND<APP_LoTW_DXCC_ENTITY_STATUS:7>Current<PFX:2>M7<APP_LoTW_2xQSL:1>Y<GRIDSQUARE:6>IO83QI<CQZ:2>14<ITUZ:2>27<eor>

LOG: <DISTANCE:7>1228.00 <BAND:3>80M <CALL:5>M7DWW <CONT:2>EU <CQZ:2>14 <DXCC:3>223 <FREQ:8>3.574575 <GRIDSQUARE:6>IO83qi <ITUZ:2>27 <MODE:3>FT8 <NAME:16>Duncan C Woodall <OPERATOR:5>JAKUB <PFX:2>M7 <QSO_DATE:8:D>20210115 <TIME_ON:6>212845 <QTH:17>Runcorn, Cheshire <RST_RCVD:3>-20 <RST_SENT:3>-16 <TIME_OFF:6>213029 <eQSL_QSL_SENT:1>Y <LOTW_QSL_SENT:1>Y <APP_LOGGER32_QSO_NUMBER:3>121 <FREQ_RX:8>3.574395 <COUNTRY:7>England <APP_LOGGER32_LAT:16>53.3541666666667 <APP_LOGGER32_LNG:5>2.625 <EOR>

 

BAD: QSO not found in Logbook:  <APP_LoTW_OWNCALL:6>OK1RJO<STATION_CALLSIGN:6>OK1RJO<CALL:5>DM2HK<BAND:3>80M<FREQ:7>3.57424<FREQ_RX:7>3.57401<MODE:3>FT8<APP_LoTW_MODEGROUP:4>DATA<QSO_DATE:8>20210115<APP_LoTW_RXQSO:19>2021-01-16 17:31:13 // QSO record inserted/modified at LoTW<TIME_ON:6>211800<APP_LoTW_QSO_TIMESTAMP:20>2021-01-15T21:18:00Z // QSO Date & Time; ISO-8601<QSL_RCVD:1>Y<QSLRDATE:8>20210116<APP_LoTW_RXQSL:19>2021-01-16 17:31:13 // QSL record matched/modified at LoTW<DXCC:3>230<COUNTRY:27>FEDERAL REPUBLIC OF GERMANY<APP_LoTW_DXCC_ENTITY_STATUS:7>Current<PFX:3>DM2<APP_LoTW_2xQSL:1>Y<GRIDSQUARE:6>JO62TI<CQZ:2>14<APP_LoTW_CQZ_Inferred:1>Y // from DXCC entity<ITUZ:2>28<APP_LoTW_ITUZ_Inferred:1>Y // from DXCC entity<eor>

LOG: <DISTANCE:6>262.00 <BAND:3>80M <CALL:5>DM2HK <CONT:2>EU <CQZ:2>14 <DXCC:3>230 <FREQ:8>3.574245 <GRIDSQUARE:6>JO62ti <ITUZ:2>28 <MODE:3>FT8 <NAME:14>Hartmut Kordus <OPERATOR:5>JAKUB <PFX:3>DM2 <QSO_DATE:8:D>20210115 <TIME_ON:6>211800 <QTH:7>Zeuthen <RST_RCVD:3>-12 <RST_SENT:3>-07 <TIME_OFF:6>212059 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <APP_LOGGER32_QSO_NUMBER:3>119 <FREQ_RX:8>3.574006 <COUNTRY:27>Federal Republic of Germany <APP_LOGGER32_LAT:16>52.3541666666667 <APP_LOGGER32_LNG:7>-13.625 <EOR>

 

BAD: QSO not found in Logbook:  <APP_LoTW_OWNCALL:6>OK1RJO<STATION_CALLSIGN:6>OK1RJO<CALL:6>EA8AIN<BAND:3>40M<FREQ:7>7.07612<FREQ_RX:7>7.07493<MODE:3>FT8<APP_LoTW_MODEGROUP:4>DATA<QSO_DATE:8>20210109<APP_LoTW_RXQSO:19>2021-01-09 22:14:30 // QSO record inserted/modified at LoTW<TIME_ON:6>212046<APP_LoTW_QSO_TIMESTAMP:20>2021-01-09T21:20:46Z // QSO Date & Time; ISO-8601<QSL_RCVD:1>Y<QSLRDATE:8>20210111<APP_LoTW_RXQSL:19>2021-01-11 19:57:48 // QSL record matched/modified at LoTW<DXCC:2>29<COUNTRY:14>CANARY ISLANDS<APP_LoTW_DXCC_ENTITY_STATUS:7>Current<PFX:3>EA8<APP_LoTW_2xQSL:1>Y<IOTA:6>AF-004<GRIDSQUARE:6>IL18CQ<CQZ:2>33<ITUZ:2>36<eor>

LOG: <DISTANCE:7>3599.00 <BAND:3>40M <CALL:6>EA8AIN <CONT:2>AF <CQZ:2>33 <DXCC:2>29 <FREQ:8>7.076120 <GRIDSQUARE:6>IL18cq <ITUZ:2>36 <MODE:3>FT8 <NAME:33>Aurelio Rodriguez Concepcion Aure <OPERATOR:5>ONDRA <PFX:3>EA8 <QSO_DATE:8:D>20210109 <TIME_ON:6>212046 <QTH:22>Santa Cruz De La Palma <RST_RCVD:3>-19 <RST_SENT:3>-18 <TIME_OFF:6>212229 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <APP_LOGGER32_QSO_NUMBER:3>103 <FREQ_RX:8>7.074928 <COUNTRY:14>Canary Islands <APP_LOGGER32_LAT:7>28.6875 <APP_LOGGER32_LNG:16>17.7916666666667 <EOR>



--
73! OK1TK


ok1tk
 

Hi Gary,

I do understand what you mean. What is really strange for me: I egenrated an ADIF file in Logger32 -> I uploaded it to LoTW via their SW and the file was accepted -> Then, I downloaded the file from LoTW and tried to upload it to L32 and then the problems appeared. But LoTW received the roginal date from my L32 ADIF file. I am bit confused.

Anyway. I will try to change the operator for 1 or 2 records in my Logger32 from OK1TK/P to OK1TK and the same with OK1RJO records and try if it helps.

It seems you could be right. I am not on my PC now but I checked the records on LoTW for OK1TK and all the QSO made by OK1TK/P were from JAN 2020 (just thrree days I was operating remotly via my friend's equipment). From all QSO made within these days I used as operator OK1TK and I have just 10 QSL on the LoTW web page. ANd there are 10 QSO which are not possible to update with the LoTW file.

All the records done for OK1RJO are with operators (JAKUB, ONDRA, TOMAS....). I tried to use OK1TK as operator while working as club operator of OK1RJO. And then it was not accepted by LoTW so that's why I changed the the op name from OK1TK to TOMAS.


I will test what you mentioned and if it works we will use the comment field for the op. name in Logger32 for OK1RJO. It is a shame that the Operator fidl can't be used for different ops working under one callsign as it is with club stations.

I agree if you use the example above for the user manual.

I thank you very very much for your support and will update you with the results of the test when I am at home this evening..

 
--
73! OK1TK


ok1tk
 

Hi Garry, you are right, when the operator was changed to OK1TK resp. OK1RJO the upload from LoTW passed correctly. Tnx for your help and support.
--
73! OK1TK