Date   

Distance calculation for imported ADIF, distance update for old QSOs

Ady, YO2NAA
 

Hello,

the distance calculation feature is very nice and useful, thank you, Bob.
Would it be possible to have an option for distance calculation during ADIF import? (even if the import will take a longer time)
I recently imported some VHF QSOs from the contest log. It would be great to have also the distance in Logger32.

Also, I have a lot of old QSOs with QRA field present but without distance, would it be possible to have the distance inserted in the log?
For now, the workaround is to delete the QRA (CTRL-X), hit TAB, click on QRA cell, paste the QRA (CTRL-V) and hit tab again...
I would appreciate a feature like this: if the distance field is empty and QRA is filled, a click inside the distance cell would calculate and write the distance in the log.
The problem here can be that OLD QSOs were made from a different location, but the my_gridsquare ADIF field can be used for distance calculation, if present...

Thank you,
73 Ady YO2NAA


Re: LOTW credit granted is not updating

Bob
 

If you like, send me (to k4cy@...) zip a copy of your log in ADIF format and the 'junk' file and I will take a peek. 73.

On July 10, 2019 at 8:08 AM Chuck Kraly K0XM <ckraly@...> wrote:

Bob and Gary,
I took a look at my "junk" file and cannot see any reason they are kicked back. Everything SEEMS to be correct, but for some reason the program is not liking them. I will look into it more today.
Thanks guys
Chuck K0XM

On Tue, Jul 9, 2019 at 5:44 PM Bob < k4cy@...> wrote:

Gary, you'll figure it out. Go tend the sheep (and remember it's the ones with a red bandana that kick). It's Famous Grouse time for me. SeventyThree(s) .... but wait, is it the ones without the red bandana that kick? You'll figure that one out soon enough too 👿

On July 9, 2019 at 6:27 PM Gary Hinson < Gary@...> wrote:

Hmmm, OK.  I click a mismatched QSO on the left and as if by magic one or more logged QSOs with that station appear on the right.

 

Clicking through several mismatches on the left, I find most of them match to QSOs with my contest call ZM4G, so it looks as if that’s a leading cause.  If there was previously an option to select QSOs under ZL2IFB and ZM4G for my DXCC awards, it seems I missed it.  I suspect it relates to the earlier cryptic “First select a DXCC” message: perhaps I should have entered ZM4G as well as ZL2IFB then.  Silly me.

 

Having found a matching QSO in my log, it’s not at all clear what to do next … but I’ve discovered that clicking a QSO line on the right makes both it and the mismatched QSO on the left magically disappear … so I guess that has made the connection and set the GRANTED flag/s appropriately.  Well, I hope so anyway.  It’s a good thing I didn’t randomly click the wrong QSO.  Well I hope not anyway.

 

A few mismatched QSOs do not pull up any similar logged QSOs – zilch, nada, nothing at all, no error, no feedback, no “Tough luck Gary”!  Yet again, it’s unclear what to do next.  The options along the bottom to ignore band, mode or DXCC don’t seem relevant since there are no QSOs shown.  If there was a “Find QSOs with a vaguely similar callsign” option it might help, or a “Show a chunk of log around the time of the selected mismatching QSO” maybe.  As a last resort, how about “[Re]Log this QSO” since it must at some point have been logged, signed and uploaded to LoTW in order to match and end up being credited to DXCC. 

 

Clicking the enticing Let me try button made this popup:

 

 

A classic, Bob, but I don’t understand it.  The first sentence is self-contradictory and makes no sense to me: if you have found/matched them, how come they ‘could not be matched’??  The second sentence is patently false (clearly it was paying attention!).  The third sentence tells me to do what I’ve already done … I think … so I don’t know what that would achieve.  I learnt long ago to stop banging my head against walls when it starts to hurt.

 

And as for the window title, well I’d be reaching for the bottle of Famous Grouse too if it weren’t 10am on a workday.

 

Sorry Bob, I’m stumped for now.  More later.  Lambs a-bleatin’

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 10 July 2019 09:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Click on a QSO on the left side of the window. You better hurry up, it's 17:30 here, and I have a glass of Famous Grouse waiting. SeventyThree(s).

On July 9, 2019 at 5:27 PM Gary Hinson <Gary@...> wrote:

OK, the batch updater is done, ending with this popup, same as yesterday:

 

 

The batch updater window does list mismatched QSOs in alphabetical sequence but not the details of why they mismatched e.g.:

 

 

You suggested checking for QSO mismatch errors in LoTW-mismatch.txt … but (judging by the file date) that file was not changed by the batch updater, so I think that was a red herring Bob:

 

  … etc.

 

Right now, LoTW-mismatch.txt appears to show errors from the last time I downloaded confirmations from LoTW – nothing to do with the batch updater:

 

   … etc.

 

As happened yesterday, the file ZL2IFB_junk_from_the_ARRL.txt contains QSO records with no indication of the errors that put them there:

 

… etc.

 

So, now ‘m trying out the “Correct errors” function … which opens to this:

 

 

Errr, I’m not sure what to do here so I’ll explore … QRX (again again).   Animals to feed, fire to poke, tea to brew, work piling up …

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 10 July 2019 08:04
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Gary, found it ... On this window click the CORRECT ERRORS menu. Never tried it, so you're on your own. SeventyThree(s).

 

On July 9, 2019 at 3:46 PM Bob <k4cy@...> wrote:

Gary, coincidence ... You mentioned the error "Unable to match QSL credit with ..." errors, and you showed a picture that included a couple of QSOs with 3B9WR. Now you say the first record in the junk_from_ARRL file is a 3B9WR QSO and the QSO is in the logbook all OK ... but, is the QSO logged as DXCC #207 Rodriguez Island? I did say the "Unable to match QSL credit with ..." was probably as a result of DXCC number mismatch between the LoTW and Logger32.

 

I seem to remember when writing all this silly code, that I had a couple of windows that compared the LoTW_junk with the logbook QSOs side by side, and you could select the junk QSOs one by one and map them to the correct QSO in the logbook (the correct mapping was saved so that next time you did this it would be remembered and not error out) ... What happened to all that stuff?

 

SeventyThree(s).

On July 9, 2019 at 3:28 PM Gary Hinson <Gary@...> wrote:

Hi Bob.

 

I hate loose ends and care about the integrity of my log so I will indeed slog through the 151 exceptions, in due course.  No can-kicking.

 

Yesterday, short of time, I fell at the first hurdle: the first record in the ZL2IFB_junk_from_the_ARRL.txt file reads:

 

3B9WR|207|2010/03/13|16:46:11|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=272161077

 

No clue – there – about why it errored.   

 

I found a 3B9WR QSO in my log at that date, time, mode and band, and it is shown as confirmed on LoTW and (I think) credited to/granted for my DXCC Mixed, CW and 40m awards.   So it looks good to me.   No obvious error.  I gave up.

 

It hadn’t occurred to me to check the LoTW-mismatch.txt file as well, so that’s what I’ll do next – assuming it hasn’t already been overwritten by a LoTW download.

 

By chance, I have a screengrab on my website from a previous run of this process, showing an error message generated by the Batch credit granted update function: see https://www.g4ifb.com/assets/images/auto_generated_images/L32-DXCC-credits-updating.gif   I wasn’t paying close attention but I didn’t notice any of those errors this time around, not one, so I guess something may have changed.

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 09 July 2019 23:56
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Good job Batman. You're hired ... The error message to show "Unable to match QSL credit ..." is as a result of the record from the ARRL/LoTW DXCC number does not match the DXCC number of the QSO in the Logbook. Not a new message. Sorry to be such a PITA, but every detailed must be checked and verified ... No kicking the can down the road here.  Try the built in Club Log option to sanitize your logbook DXCCs with their 560M+ QSO database.

 

Regarding the missing information about how/why the LoTW data could not be matched with your logbook, look in the LoTW-mismatch.txt file. Is that what you need?

 

SeventyThree(s).

On July 8, 2019 at 10:12 PM Gary Hinson <Gary@...> wrote:

Step-by-step, this process worked for me.

 

1.       I started from here: Logger32’s DXCC award report shows 330 current DXCCs confirmed but only 329 granted …

 

 

I’m not sure which confirmed country isn’t marked as Granted in Logger32 as I don’t have any pending DXCC applications on the go, and LoTW shows I have 330 (current) for the Mixed DXCC:



So I decided it’s time to update Logger32.

2.       I ran C:\Logger32\ARRL scraper.exe, entered my LoTW credentials and clicked Start.

3.       The minimalist feedback from ARRL scraper shows it first systematically checking each of my DXCC awards in turn, then removing any pending credits …

 

 

… then downloading the individual QSOs granted for each award, one-by-one, steadily turning the progress bar blue …

 

 

 

It writes granted QSOs to a data file C:\Logger32\ZL2IFB_1_granted_credits scraped data.txt, where ZL2IFB is my callsign and 1 is the LoTW account number I’m using.  My scraped data starts like this:

 

1A0C|246|2012/07/03|20:47:27|SSB|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459625

1A0C|246|2012/07/03|21:16:43|CW|12M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459626

1A0C|246|2012/07/04|01:59:56|CW|20M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459630

1A0C|246|2012/07/04|02:30:43|RTTY|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459631

1A0C|246|2012/07/04|04:08:05|SSB|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459632

1A0C|246|2012/07/04|22:25:47|RTTY|17M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432832487

1A0KM|246|2011/01/29|18:31:49|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=322537469

2M0YIO|279|2011/09/23|10:15:56|RTTY|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=365696173

3A/DL3OCH|260|2008/03/21|18:32:20|CW|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=163312492

 

Each QSO line contains the following fields:

Callsign | DXCC country code | QSO date YYYY/MM/DD UTC | QSO time HH:MM:SS UTC| Mode | Confirmed by a match in LoTW or by QSL card | URL for the QSO record at LoTW

This part of the process is slow (taking about 1 second per QSO) but as the same QSO info appears on the ARRL scraper screen as each record is downloaded and written to the data file (less the URL field and sometimes truncated for space), it is possible to guess which DXCC award is being processed at that point.  Be patient.  It would be much more tedious and error prone to do the lookups and updates manually!

 

Eventually, the blue bar reaches the end sand ARRL scraper stops – no message, no clue, it just disappears in a puff of logic.  Data file written.  Job done.

 

4.       Now I need to import the data file into Logger32.  First, find and run the QSL update function on the Awards menu:

 

Next, click “Update from ARRL file” then read the warning:

 


OK that, then browse to find and select the data file, then fiddle around to get my callsign into the Primary callsign field (there’s a message in the box initially. Click the down arrow to select the next <empty> row.  Then type the callsign in to the box.  This appears to be Turing test.  I think I passed.)

 

 

 

 

Then click Start to set the granted update process running.  It’s another tediously slow process, slightly faster perhaps with the Cluster disconnected and UDP bandmap closed for good measure.  Hard to tell.

 

 

The QSO record currently being processed is at the bottom of the window – not the QSO data line this time but just the callsign, enough to see stuff happening anyway.  Logger32’s main screen blue progress bar also extrudes itself across the screen, slowly, like an uncapped tube of blue toothpaste sitting on the dashboard in bright sunshine.  Yes, the mind wanders.

Also new “Error: Unable to match QSL credits” messages appear sporadically, in my case anyway.  Don’t worry: the errors are written to a data file so we can sort them out afterwards, eventually, when the granted update process completes.

 

5.       Eventually, after about an hour, the granted update completed:



Aside from naming the error file I mentioned, the file itself is opened in a text editor:

… etc.

So those are the QSO lines in the same format as before.  No clue about why they caused errors though, oh no*, so now I have 151 QSOs to check in my log against LoTW. 

* I think something has changed since I last ran this process.  Previously, the error messages indicated what the errors were e.g. country mismatch.  Now, nothing.

6.       Now my DXCC report in Logger32 shows this:




The mysteriously missing credit is now shown as granted.  Maybe I’ll find more things to update among those 151 error’d QSOs … but not today.  This has taken my whole morning!

73 GL,

Gary   ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Chuck Kraly K0XM
Sent: 09 July 2019 06:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Agreed, and this is showing both my present call K0XM, and old call N0BIW

 

 


 


 

 

 


 


 


 

 

 


 


 

 



 


 

 

 


Re: LOTW credit granted is not updating

Chuck Kraly K0XM
 

Bob and Gary,
I took a look at my "junk" file and cannot see any reason they are kicked back. Everything SEEMS to be correct, but for some reason the program is not liking them. I will look into it more today.
Thanks guys
Chuck K0XM


On Tue, Jul 9, 2019 at 5:44 PM Bob <k4cy@...> wrote:

Gary, you'll figure it out. Go tend the sheep (and remember it's the ones with a red bandana that kick). It's Famous Grouse time for me. SeventyThree(s) .... but wait, is it the ones without the red bandana that kick? You'll figure that one out soon enough too 👿

On July 9, 2019 at 6:27 PM Gary Hinson <Gary@...> wrote:

Hmmm, OK.  I click a mismatched QSO on the left and as if by magic one or more logged QSOs with that station appear on the right.

 

Clicking through several mismatches on the left, I find most of them match to QSOs with my contest call ZM4G, so it looks as if that’s a leading cause.  If there was previously an option to select QSOs under ZL2IFB and ZM4G for my DXCC awards, it seems I missed it.  I suspect it relates to the earlier cryptic “First select a DXCC” message: perhaps I should have entered ZM4G as well as ZL2IFB then.  Silly me.

 

Having found a matching QSO in my log, it’s not at all clear what to do next … but I’ve discovered that clicking a QSO line on the right makes both it and the mismatched QSO on the left magically disappear … so I guess that has made the connection and set the GRANTED flag/s appropriately.  Well, I hope so anyway.  It’s a good thing I didn’t randomly click the wrong QSO.  Well I hope not anyway.

 

A few mismatched QSOs do not pull up any similar logged QSOs – zilch, nada, nothing at all, no error, no feedback, no “Tough luck Gary”!  Yet again, it’s unclear what to do next.  The options along the bottom to ignore band, mode or DXCC don’t seem relevant since there are no QSOs shown.  If there was a “Find QSOs with a vaguely similar callsign” option it might help, or a “Show a chunk of log around the time of the selected mismatching QSO” maybe.  As a last resort, how about “[Re]Log this QSO” since it must at some point have been logged, signed and uploaded to LoTW in order to match and end up being credited to DXCC. 

 

Clicking the enticing Let me try button made this popup:

 

 

A classic, Bob, but I don’t understand it.  The first sentence is self-contradictory and makes no sense to me: if you have found/matched them, how come they ‘could not be matched’??  The second sentence is patently false (clearly it was paying attention!).  The third sentence tells me to do what I’ve already done … I think … so I don’t know what that would achieve.  I learnt long ago to stop banging my head against walls when it starts to hurt.

 

And as for the window title, well I’d be reaching for the bottle of Famous Grouse too if it weren’t 10am on a workday.

 

Sorry Bob, I’m stumped for now.  More later.  Lambs a-bleatin’

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 10 July 2019 09:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Click on a QSO on the left side of the window. You better hurry up, it's 17:30 here, and I have a glass of Famous Grouse waiting. SeventyThree(s).

On July 9, 2019 at 5:27 PM Gary Hinson <Gary@...> wrote:

OK, the batch updater is done, ending with this popup, same as yesterday:

 

 

The batch updater window does list mismatched QSOs in alphabetical sequence but not the details of why they mismatched e.g.:

 

 

You suggested checking for QSO mismatch errors in LoTW-mismatch.txt … but (judging by the file date) that file was not changed by the batch updater, so I think that was a red herring Bob:

 

  … etc.

 

Right now, LoTW-mismatch.txt appears to show errors from the last time I downloaded confirmations from LoTW – nothing to do with the batch updater:

 

   … etc.

 

As happened yesterday, the file ZL2IFB_junk_from_the_ARRL.txt contains QSO records with no indication of the errors that put them there:

 

… etc.

 

So, now ‘m trying out the “Correct errors” function … which opens to this:

 

 

Errr, I’m not sure what to do here so I’ll explore … QRX (again again).   Animals to feed, fire to poke, tea to brew, work piling up …

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 10 July 2019 08:04
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Gary, found it ... On this window click the CORRECT ERRORS menu. Never tried it, so you're on your own. SeventyThree(s).

 

On July 9, 2019 at 3:46 PM Bob <k4cy@...> wrote:

Gary, coincidence ... You mentioned the error "Unable to match QSL credit with ..." errors, and you showed a picture that included a couple of QSOs with 3B9WR. Now you say the first record in the junk_from_ARRL file is a 3B9WR QSO and the QSO is in the logbook all OK ... but, is the QSO logged as DXCC #207 Rodriguez Island? I did say the "Unable to match QSL credit with ..." was probably as a result of DXCC number mismatch between the LoTW and Logger32.

 

I seem to remember when writing all this silly code, that I had a couple of windows that compared the LoTW_junk with the logbook QSOs side by side, and you could select the junk QSOs one by one and map them to the correct QSO in the logbook (the correct mapping was saved so that next time you did this it would be remembered and not error out) ... What happened to all that stuff?

 

SeventyThree(s).

On July 9, 2019 at 3:28 PM Gary Hinson <Gary@...> wrote:

Hi Bob.

 

I hate loose ends and care about the integrity of my log so I will indeed slog through the 151 exceptions, in due course.  No can-kicking.

 

Yesterday, short of time, I fell at the first hurdle: the first record in the ZL2IFB_junk_from_the_ARRL.txt file reads:

 

3B9WR|207|2010/03/13|16:46:11|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=272161077

 

No clue – there – about why it errored.   

 

I found a 3B9WR QSO in my log at that date, time, mode and band, and it is shown as confirmed on LoTW and (I think) credited to/granted for my DXCC Mixed, CW and 40m awards.   So it looks good to me.   No obvious error.  I gave up.

 

It hadn’t occurred to me to check the LoTW-mismatch.txt file as well, so that’s what I’ll do next – assuming it hasn’t already been overwritten by a LoTW download.

 

By chance, I have a screengrab on my website from a previous run of this process, showing an error message generated by the Batch credit granted update function: see https://www.g4ifb.com/assets/images/auto_generated_images/L32-DXCC-credits-updating.gif   I wasn’t paying close attention but I didn’t notice any of those errors this time around, not one, so I guess something may have changed.

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 09 July 2019 23:56
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Good job Batman. You're hired ... The error message to show "Unable to match QSL credit ..." is as a result of the record from the ARRL/LoTW DXCC number does not match the DXCC number of the QSO in the Logbook. Not a new message. Sorry to be such a PITA, but every detailed must be checked and verified ... No kicking the can down the road here.  Try the built in Club Log option to sanitize your logbook DXCCs with their 560M+ QSO database.

 

Regarding the missing information about how/why the LoTW data could not be matched with your logbook, look in the LoTW-mismatch.txt file. Is that what you need?

 

SeventyThree(s).

On July 8, 2019 at 10:12 PM Gary Hinson <Gary@...> wrote:

Step-by-step, this process worked for me.

 

1.       I started from here: Logger32’s DXCC award report shows 330 current DXCCs confirmed but only 329 granted …

 

 

I’m not sure which confirmed country isn’t marked as Granted in Logger32 as I don’t have any pending DXCC applications on the go, and LoTW shows I have 330 (current) for the Mixed DXCC:



So I decided it’s time to update Logger32.

2.       I ran C:\Logger32\ARRL scraper.exe, entered my LoTW credentials and clicked Start.

3.       The minimalist feedback from ARRL scraper shows it first systematically checking each of my DXCC awards in turn, then removing any pending credits …

 

 

… then downloading the individual QSOs granted for each award, one-by-one, steadily turning the progress bar blue …

 

 

 

It writes granted QSOs to a data file C:\Logger32\ZL2IFB_1_granted_credits scraped data.txt, where ZL2IFB is my callsign and 1 is the LoTW account number I’m using.  My scraped data starts like this:

 

1A0C|246|2012/07/03|20:47:27|SSB|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459625

1A0C|246|2012/07/03|21:16:43|CW|12M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459626

1A0C|246|2012/07/04|01:59:56|CW|20M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459630

1A0C|246|2012/07/04|02:30:43|RTTY|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459631

1A0C|246|2012/07/04|04:08:05|SSB|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459632

1A0C|246|2012/07/04|22:25:47|RTTY|17M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432832487

1A0KM|246|2011/01/29|18:31:49|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=322537469

2M0YIO|279|2011/09/23|10:15:56|RTTY|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=365696173

3A/DL3OCH|260|2008/03/21|18:32:20|CW|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=163312492

 

Each QSO line contains the following fields:

Callsign | DXCC country code | QSO date YYYY/MM/DD UTC | QSO time HH:MM:SS UTC| Mode | Confirmed by a match in LoTW or by QSL card | URL for the QSO record at LoTW

This part of the process is slow (taking about 1 second per QSO) but as the same QSO info appears on the ARRL scraper screen as each record is downloaded and written to the data file (less the URL field and sometimes truncated for space), it is possible to guess which DXCC award is being processed at that point.  Be patient.  It would be much more tedious and error prone to do the lookups and updates manually!

 

Eventually, the blue bar reaches the end sand ARRL scraper stops – no message, no clue, it just disappears in a puff of logic.  Data file written.  Job done.

 

4.       Now I need to import the data file into Logger32.  First, find and run the QSL update function on the Awards menu:

 

Next, click “Update from ARRL file” then read the warning:

 


OK that, then browse to find and select the data file, then fiddle around to get my callsign into the Primary callsign field (there’s a message in the box initially. Click the down arrow to select the next <empty> row.  Then type the callsign in to the box.  This appears to be Turing test.  I think I passed.)

 

 

 

 

Then click Start to set the granted update process running.  It’s another tediously slow process, slightly faster perhaps with the Cluster disconnected and UDP bandmap closed for good measure.  Hard to tell.

 

 

The QSO record currently being processed is at the bottom of the window – not the QSO data line this time but just the callsign, enough to see stuff happening anyway.  Logger32’s main screen blue progress bar also extrudes itself across the screen, slowly, like an uncapped tube of blue toothpaste sitting on the dashboard in bright sunshine.  Yes, the mind wanders.

Also new “Error: Unable to match QSL credits” messages appear sporadically, in my case anyway.  Don’t worry: the errors are written to a data file so we can sort them out afterwards, eventually, when the granted update process completes.

 

5.       Eventually, after about an hour, the granted update completed:



Aside from naming the error file I mentioned, the file itself is opened in a text editor:

… etc.

So those are the QSO lines in the same format as before.  No clue about why they caused errors though, oh no*, so now I have 151 QSOs to check in my log against LoTW. 

* I think something has changed since I last ran this process.  Previously, the error messages indicated what the errors were e.g. country mismatch.  Now, nothing.

6.       Now my DXCC report in Logger32 shows this:




The mysteriously missing credit is now shown as granted.  Maybe I’ll find more things to update among those 151 error’d QSOs … but not today.  This has taken my whole morning!

73 GL,

Gary   ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Chuck Kraly K0XM
Sent: 09 July 2019 06:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Agreed, and this is showing both my present call K0XM, and old call N0BIW

 

 


 


 

 

 


 


 


 

 

 


 


 

 



 


 


Re: LOTW credit granted is not updating

Bob
 

Gary, you'll figure it out. Go tend the sheep (and remember it's the ones with a red bandana that kick). It's Famous Grouse time for me. SeventyThree(s) .... but wait, is it the ones without the red bandana that kick? You'll figure that one out soon enough too 👿

On July 9, 2019 at 6:27 PM Gary Hinson <Gary@...> wrote:

Hmmm, OK.  I click a mismatched QSO on the left and as if by magic one or more logged QSOs with that station appear on the right.

 

Clicking through several mismatches on the left, I find most of them match to QSOs with my contest call ZM4G, so it looks as if that’s a leading cause.  If there was previously an option to select QSOs under ZL2IFB and ZM4G for my DXCC awards, it seems I missed it.  I suspect it relates to the earlier cryptic “First select a DXCC” message: perhaps I should have entered ZM4G as well as ZL2IFB then.  Silly me.

 

Having found a matching QSO in my log, it’s not at all clear what to do next … but I’ve discovered that clicking a QSO line on the right makes both it and the mismatched QSO on the left magically disappear … so I guess that has made the connection and set the GRANTED flag/s appropriately.  Well, I hope so anyway.  It’s a good thing I didn’t randomly click the wrong QSO.  Well I hope not anyway.

 

A few mismatched QSOs do not pull up any similar logged QSOs – zilch, nada, nothing at all, no error, no feedback, no “Tough luck Gary”!  Yet again, it’s unclear what to do next.  The options along the bottom to ignore band, mode or DXCC don’t seem relevant since there are no QSOs shown.  If there was a “Find QSOs with a vaguely similar callsign” option it might help, or a “Show a chunk of log around the time of the selected mismatching QSO” maybe.  As a last resort, how about “[Re]Log this QSO” since it must at some point have been logged, signed and uploaded to LoTW in order to match and end up being credited to DXCC. 

 

Clicking the enticing Let me try button made this popup:

 

 

A classic, Bob, but I don’t understand it.  The first sentence is self-contradictory and makes no sense to me: if you have found/matched them, how come they ‘could not be matched’??  The second sentence is patently false (clearly it was paying attention!).  The third sentence tells me to do what I’ve already done … I think … so I don’t know what that would achieve.  I learnt long ago to stop banging my head against walls when it starts to hurt.

 

And as for the window title, well I’d be reaching for the bottle of Famous Grouse too if it weren’t 10am on a workday.

 

Sorry Bob, I’m stumped for now.  More later.  Lambs a-bleatin’

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 10 July 2019 09:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Click on a QSO on the left side of the window. You better hurry up, it's 17:30 here, and I have a glass of Famous Grouse waiting. SeventyThree(s).

On July 9, 2019 at 5:27 PM Gary Hinson <Gary@...> wrote:

OK, the batch updater is done, ending with this popup, same as yesterday:

 

 

The batch updater window does list mismatched QSOs in alphabetical sequence but not the details of why they mismatched e.g.:

 

 

You suggested checking for QSO mismatch errors in LoTW-mismatch.txt … but (judging by the file date) that file was not changed by the batch updater, so I think that was a red herring Bob:

 

  … etc.

 

Right now, LoTW-mismatch.txt appears to show errors from the last time I downloaded confirmations from LoTW – nothing to do with the batch updater:

 

   … etc.

 

As happened yesterday, the file ZL2IFB_junk_from_the_ARRL.txt contains QSO records with no indication of the errors that put them there:

 

… etc.

 

So, now ‘m trying out the “Correct errors” function … which opens to this:

 

 

Errr, I’m not sure what to do here so I’ll explore … QRX (again again).   Animals to feed, fire to poke, tea to brew, work piling up …

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 10 July 2019 08:04
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Gary, found it ... On this window click the CORRECT ERRORS menu. Never tried it, so you're on your own. SeventyThree(s).

 

On July 9, 2019 at 3:46 PM Bob <k4cy@...> wrote:

Gary, coincidence ... You mentioned the error "Unable to match QSL credit with ..." errors, and you showed a picture that included a couple of QSOs with 3B9WR. Now you say the first record in the junk_from_ARRL file is a 3B9WR QSO and the QSO is in the logbook all OK ... but, is the QSO logged as DXCC #207 Rodriguez Island? I did say the "Unable to match QSL credit with ..." was probably as a result of DXCC number mismatch between the LoTW and Logger32.

 

I seem to remember when writing all this silly code, that I had a couple of windows that compared the LoTW_junk with the logbook QSOs side by side, and you could select the junk QSOs one by one and map them to the correct QSO in the logbook (the correct mapping was saved so that next time you did this it would be remembered and not error out) ... What happened to all that stuff?

 

SeventyThree(s).

On July 9, 2019 at 3:28 PM Gary Hinson <Gary@...> wrote:

Hi Bob.

 

I hate loose ends and care about the integrity of my log so I will indeed slog through the 151 exceptions, in due course.  No can-kicking.

 

Yesterday, short of time, I fell at the first hurdle: the first record in the ZL2IFB_junk_from_the_ARRL.txt file reads:

 

3B9WR|207|2010/03/13|16:46:11|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=272161077

 

No clue – there – about why it errored.   

 

I found a 3B9WR QSO in my log at that date, time, mode and band, and it is shown as confirmed on LoTW and (I think) credited to/granted for my DXCC Mixed, CW and 40m awards.   So it looks good to me.   No obvious error.  I gave up.

 

It hadn’t occurred to me to check the LoTW-mismatch.txt file as well, so that’s what I’ll do next – assuming it hasn’t already been overwritten by a LoTW download.

 

By chance, I have a screengrab on my website from a previous run of this process, showing an error message generated by the Batch credit granted update function: see https://www.g4ifb.com/assets/images/auto_generated_images/L32-DXCC-credits-updating.gif   I wasn’t paying close attention but I didn’t notice any of those errors this time around, not one, so I guess something may have changed.

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 09 July 2019 23:56
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Good job Batman. You're hired ... The error message to show "Unable to match QSL credit ..." is as a result of the record from the ARRL/LoTW DXCC number does not match the DXCC number of the QSO in the Logbook. Not a new message. Sorry to be such a PITA, but every detailed must be checked and verified ... No kicking the can down the road here.  Try the built in Club Log option to sanitize your logbook DXCCs with their 560M+ QSO database.

 

Regarding the missing information about how/why the LoTW data could not be matched with your logbook, look in the LoTW-mismatch.txt file. Is that what you need?

 

SeventyThree(s).

On July 8, 2019 at 10:12 PM Gary Hinson <Gary@...> wrote:

Step-by-step, this process worked for me.

 

1.       I started from here: Logger32’s DXCC award report shows 330 current DXCCs confirmed but only 329 granted …

 

 

I’m not sure which confirmed country isn’t marked as Granted in Logger32 as I don’t have any pending DXCC applications on the go, and LoTW shows I have 330 (current) for the Mixed DXCC:



So I decided it’s time to update Logger32.

2.       I ran C:\Logger32\ARRL scraper.exe, entered my LoTW credentials and clicked Start.

3.       The minimalist feedback from ARRL scraper shows it first systematically checking each of my DXCC awards in turn, then removing any pending credits …

 

 

… then downloading the individual QSOs granted for each award, one-by-one, steadily turning the progress bar blue …

 

 

 

It writes granted QSOs to a data file C:\Logger32\ZL2IFB_1_granted_credits scraped data.txt, where ZL2IFB is my callsign and 1 is the LoTW account number I’m using.  My scraped data starts like this:

 

1A0C|246|2012/07/03|20:47:27|SSB|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459625

1A0C|246|2012/07/03|21:16:43|CW|12M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459626

1A0C|246|2012/07/04|01:59:56|CW|20M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459630

1A0C|246|2012/07/04|02:30:43|RTTY|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459631

1A0C|246|2012/07/04|04:08:05|SSB|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459632

1A0C|246|2012/07/04|22:25:47|RTTY|17M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432832487

1A0KM|246|2011/01/29|18:31:49|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=322537469

2M0YIO|279|2011/09/23|10:15:56|RTTY|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=365696173

3A/DL3OCH|260|2008/03/21|18:32:20|CW|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=163312492

 

Each QSO line contains the following fields:

Callsign | DXCC country code | QSO date YYYY/MM/DD UTC | QSO time HH:MM:SS UTC| Mode | Confirmed by a match in LoTW or by QSL card | URL for the QSO record at LoTW

This part of the process is slow (taking about 1 second per QSO) but as the same QSO info appears on the ARRL scraper screen as each record is downloaded and written to the data file (less the URL field and sometimes truncated for space), it is possible to guess which DXCC award is being processed at that point.  Be patient.  It would be much more tedious and error prone to do the lookups and updates manually!

 

Eventually, the blue bar reaches the end sand ARRL scraper stops – no message, no clue, it just disappears in a puff of logic.  Data file written.  Job done.

 

4.       Now I need to import the data file into Logger32.  First, find and run the QSL update function on the Awards menu:

 

Next, click “Update from ARRL file” then read the warning:

 


OK that, then browse to find and select the data file, then fiddle around to get my callsign into the Primary callsign field (there’s a message in the box initially. Click the down arrow to select the next <empty> row.  Then type the callsign in to the box.  This appears to be Turing test.  I think I passed.)

 

 

 

 

Then click Start to set the granted update process running.  It’s another tediously slow process, slightly faster perhaps with the Cluster disconnected and UDP bandmap closed for good measure.  Hard to tell.

 

 

The QSO record currently being processed is at the bottom of the window – not the QSO data line this time but just the callsign, enough to see stuff happening anyway.  Logger32’s main screen blue progress bar also extrudes itself across the screen, slowly, like an uncapped tube of blue toothpaste sitting on the dashboard in bright sunshine.  Yes, the mind wanders.

Also new “Error: Unable to match QSL credits” messages appear sporadically, in my case anyway.  Don’t worry: the errors are written to a data file so we can sort them out afterwards, eventually, when the granted update process completes.

 

5.       Eventually, after about an hour, the granted update completed:



Aside from naming the error file I mentioned, the file itself is opened in a text editor:

… etc.

So those are the QSO lines in the same format as before.  No clue about why they caused errors though, oh no*, so now I have 151 QSOs to check in my log against LoTW. 

* I think something has changed since I last ran this process.  Previously, the error messages indicated what the errors were e.g. country mismatch.  Now, nothing.

6.       Now my DXCC report in Logger32 shows this:




The mysteriously missing credit is now shown as granted.  Maybe I’ll find more things to update among those 151 error’d QSOs … but not today.  This has taken my whole morning!

73 GL,

Gary   ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Chuck Kraly K0XM
Sent: 09 July 2019 06:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Agreed, and this is showing both my present call K0XM, and old call N0BIW

 

 


 


 

 

 


 


 


 

 

 


 


 

 



 


 


Re: LOTW credit granted is not updating

Gary Hinson
 

Hmmm, OK.  I click a mismatched QSO on the left and as if by magic one or more logged QSOs with that station appear on the right.

 

Clicking through several mismatches on the left, I find most of them match to QSOs with my contest call ZM4G, so it looks as if that’s a leading cause.  If there was previously an option to select QSOs under ZL2IFB and ZM4G for my DXCC awards, it seems I missed it.  I suspect it relates to the earlier cryptic “First select a DXCC” message: perhaps I should have entered ZM4G as well as ZL2IFB then.  Silly me.

 

Having found a matching QSO in my log, it’s not at all clear what to do next … but I’ve discovered that clicking a QSO line on the right makes both it and the mismatched QSO on the left magically disappear … so I guess that has made the connection and set the GRANTED flag/s appropriately.  Well, I hope so anyway.  It’s a good thing I didn’t randomly click the wrong QSO.  Well I hope not anyway.

 

A few mismatched QSOs do not pull up any similar logged QSOs – zilch, nada, nothing at all, no error, no feedback, no “Tough luck Gary”!  Yet again, it’s unclear what to do next.  The options along the bottom to ignore band, mode or DXCC don’t seem relevant since there are no QSOs shown.  If there was a “Find QSOs with a vaguely similar callsign” option it might help, or a “Show a chunk of log around the time of the selected mismatching QSO” maybe.  As a last resort, how about “[Re]Log this QSO” since it must at some point have been logged, signed and uploaded to LoTW in order to match and end up being credited to DXCC. 

 

Clicking the enticing Let me try button made this popup:

 

 

A classic, Bob, but I don’t understand it.  The first sentence is self-contradictory and makes no sense to me: if you have found/matched them, how come they ‘could not be matched’??  The second sentence is patently false (clearly it was paying attention!).  The third sentence tells me to do what I’ve already done … I think … so I don’t know what that would achieve.  I learnt long ago to stop banging my head against walls when it starts to hurt.

 

And as for the window title, well I’d be reaching for the bottle of Famous Grouse too if it weren’t 10am on a workday.

 

Sorry Bob, I’m stumped for now.  More later.  Lambs a-bleatin’

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 10 July 2019 09:33
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Click on a QSO on the left side of the window. You better hurry up, it's 17:30 here, and I have a glass of Famous Grouse waiting. SeventyThree(s).

On July 9, 2019 at 5:27 PM Gary Hinson <Gary@...> wrote:

OK, the batch updater is done, ending with this popup, same as yesterday:

 

 

The batch updater window does list mismatched QSOs in alphabetical sequence but not the details of why they mismatched e.g.:

 

 

You suggested checking for QSO mismatch errors in LoTW-mismatch.txt … but (judging by the file date) that file was not changed by the batch updater, so I think that was a red herring Bob:

 

  … etc.

 

Right now, LoTW-mismatch.txt appears to show errors from the last time I downloaded confirmations from LoTW – nothing to do with the batch updater:

 

   … etc.

 

As happened yesterday, the file ZL2IFB_junk_from_the_ARRL.txt contains QSO records with no indication of the errors that put them there:

 

… etc.

 

So, now ‘m trying out the “Correct errors” function … which opens to this:

 

 

Errr, I’m not sure what to do here so I’ll explore … QRX (again again).   Animals to feed, fire to poke, tea to brew, work piling up …

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 10 July 2019 08:04
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Gary, found it ... On this window click the CORRECT ERRORS menu. Never tried it, so you're on your own. SeventyThree(s).

 

On July 9, 2019 at 3:46 PM Bob <k4cy@...> wrote:

Gary, coincidence ... You mentioned the error "Unable to match QSL credit with ..." errors, and you showed a picture that included a couple of QSOs with 3B9WR. Now you say the first record in the junk_from_ARRL file is a 3B9WR QSO and the QSO is in the logbook all OK ... but, is the QSO logged as DXCC #207 Rodriguez Island? I did say the "Unable to match QSL credit with ..." was probably as a result of DXCC number mismatch between the LoTW and Logger32.

 

I seem to remember when writing all this silly code, that I had a couple of windows that compared the LoTW_junk with the logbook QSOs side by side, and you could select the junk QSOs one by one and map them to the correct QSO in the logbook (the correct mapping was saved so that next time you did this it would be remembered and not error out) ... What happened to all that stuff?

 

SeventyThree(s).

On July 9, 2019 at 3:28 PM Gary Hinson <Gary@...> wrote:

Hi Bob.

 

I hate loose ends and care about the integrity of my log so I will indeed slog through the 151 exceptions, in due course.  No can-kicking.

 

Yesterday, short of time, I fell at the first hurdle: the first record in the ZL2IFB_junk_from_the_ARRL.txt file reads:

 

3B9WR|207|2010/03/13|16:46:11|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=272161077

 

No clue – there – about why it errored.   

 

I found a 3B9WR QSO in my log at that date, time, mode and band, and it is shown as confirmed on LoTW and (I think) credited to/granted for my DXCC Mixed, CW and 40m awards.   So it looks good to me.   No obvious error.  I gave up.

 

It hadn’t occurred to me to check the LoTW-mismatch.txt file as well, so that’s what I’ll do next – assuming it hasn’t already been overwritten by a LoTW download.

 

By chance, I have a screengrab on my website from a previous run of this process, showing an error message generated by the Batch credit granted update function: see https://www.g4ifb.com/assets/images/auto_generated_images/L32-DXCC-credits-updating.gif   I wasn’t paying close attention but I didn’t notice any of those errors this time around, not one, so I guess something may have changed.

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 09 July 2019 23:56
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Good job Batman. You're hired ... The error message to show "Unable to match QSL credit ..." is as a result of the record from the ARRL/LoTW DXCC number does not match the DXCC number of the QSO in the Logbook. Not a new message. Sorry to be such a PITA, but every detailed must be checked and verified ... No kicking the can down the road here.  Try the built in Club Log option to sanitize your logbook DXCCs with their 560M+ QSO database.

 

Regarding the missing information about how/why the LoTW data could not be matched with your logbook, look in the LoTW-mismatch.txt file. Is that what you need?

 

SeventyThree(s).

On July 8, 2019 at 10:12 PM Gary Hinson <Gary@...> wrote:

Step-by-step, this process worked for me.

 

1.       I started from here: Logger32’s DXCC award report shows 330 current DXCCs confirmed but only 329 granted …

 

 

I’m not sure which confirmed country isn’t marked as Granted in Logger32 as I don’t have any pending DXCC applications on the go, and LoTW shows I have 330 (current) for the Mixed DXCC:



So I decided it’s time to update Logger32.

2.       I ran C:\Logger32\ARRL scraper.exe, entered my LoTW credentials and clicked Start.

3.       The minimalist feedback from ARRL scraper shows it first systematically checking each of my DXCC awards in turn, then removing any pending credits …

 

 

… then downloading the individual QSOs granted for each award, one-by-one, steadily turning the progress bar blue …

 

 

 

It writes granted QSOs to a data file C:\Logger32\ZL2IFB_1_granted_credits scraped data.txt, where ZL2IFB is my callsign and 1 is the LoTW account number I’m using.  My scraped data starts like this:

 

1A0C|246|2012/07/03|20:47:27|SSB|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459625

1A0C|246|2012/07/03|21:16:43|CW|12M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459626

1A0C|246|2012/07/04|01:59:56|CW|20M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459630

1A0C|246|2012/07/04|02:30:43|RTTY|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459631

1A0C|246|2012/07/04|04:08:05|SSB|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459632

1A0C|246|2012/07/04|22:25:47|RTTY|17M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432832487

1A0KM|246|2011/01/29|18:31:49|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=322537469

2M0YIO|279|2011/09/23|10:15:56|RTTY|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=365696173

3A/DL3OCH|260|2008/03/21|18:32:20|CW|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=163312492

 

Each QSO line contains the following fields:

Callsign | DXCC country code | QSO date YYYY/MM/DD UTC | QSO time HH:MM:SS UTC| Mode | Confirmed by a match in LoTW or by QSL card | URL for the QSO record at LoTW

This part of the process is slow (taking about 1 second per QSO) but as the same QSO info appears on the ARRL scraper screen as each record is downloaded and written to the data file (less the URL field and sometimes truncated for space), it is possible to guess which DXCC award is being processed at that point.  Be patient.  It would be much more tedious and error prone to do the lookups and updates manually!

 

Eventually, the blue bar reaches the end sand ARRL scraper stops – no message, no clue, it just disappears in a puff of logic.  Data file written.  Job done.

 

4.       Now I need to import the data file into Logger32.  First, find and run the QSL update function on the Awards menu:

 

Next, click “Update from ARRL file” then read the warning:

 


OK that, then browse to find and select the data file, then fiddle around to get my callsign into the Primary callsign field (there’s a message in the box initially. Click the down arrow to select the next <empty> row.  Then type the callsign in to the box.  This appears to be Turing test.  I think I passed.)

 

 

 

 

Then click Start to set the granted update process running.  It’s another tediously slow process, slightly faster perhaps with the Cluster disconnected and UDP bandmap closed for good measure.  Hard to tell.

 

 

The QSO record currently being processed is at the bottom of the window – not the QSO data line this time but just the callsign, enough to see stuff happening anyway.  Logger32’s main screen blue progress bar also extrudes itself across the screen, slowly, like an uncapped tube of blue toothpaste sitting on the dashboard in bright sunshine.  Yes, the mind wanders.

Also new “Error: Unable to match QSL credits” messages appear sporadically, in my case anyway.  Don’t worry: the errors are written to a data file so we can sort them out afterwards, eventually, when the granted update process completes.

 

5.       Eventually, after about an hour, the granted update completed:



Aside from naming the error file I mentioned, the file itself is opened in a text editor:

… etc.

So those are the QSO lines in the same format as before.  No clue about why they caused errors though, oh no*, so now I have 151 QSOs to check in my log against LoTW. 

* I think something has changed since I last ran this process.  Previously, the error messages indicated what the errors were e.g. country mismatch.  Now, nothing.

6.       Now my DXCC report in Logger32 shows this:




The mysteriously missing credit is now shown as granted.  Maybe I’ll find more things to update among those 151 error’d QSOs … but not today.  This has taken my whole morning!

73 GL,

Gary   ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Chuck Kraly K0XM
Sent: 09 July 2019 06:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Agreed, and this is showing both my present call K0XM, and old call N0BIW

 

 


 


 

 

 


 


 


 

 

 


 


 


Re: LOTW credit granted is not updating

Bob
 

Click on a QSO on the left side of the window. You better hurry up, it's 17:30 here, and I have a glass of Famous Grouse waiting. SeventyThree(s).

On July 9, 2019 at 5:27 PM Gary Hinson <Gary@...> wrote:

OK, the batch updater is done, ending with this popup, same as yesterday:

 

 

The batch updater window does list mismatched QSOs in alphabetical sequence but not the details of why they mismatched e.g.:

 

 

You suggested checking for QSO mismatch errors in LoTW-mismatch.txt … but (judging by the file date) that file was not changed by the batch updater, so I think that was a red herring Bob:

 

  … etc.

 

Right now, LoTW-mismatch.txt appears to show errors from the last time I downloaded confirmations from LoTW – nothing to do with the batch updater:

 

   … etc.

 

As happened yesterday, the file ZL2IFB_junk_from_the_ARRL.txt contains QSO records with no indication of the errors that put them there:

 

… etc.

 

So, now ‘m trying out the “Correct errors” function … which opens to this:

 

 

Errr, I’m not sure what to do here so I’ll explore … QRX (again again).   Animals to feed, fire to poke, tea to brew, work piling up …

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 10 July 2019 08:04
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Gary, found it ... On this window click the CORRECT ERRORS menu. Never tried it, so you're on your own. SeventyThree(s).

 

On July 9, 2019 at 3:46 PM Bob <k4cy@...> wrote:

Gary, coincidence ... You mentioned the error "Unable to match QSL credit with ..." errors, and you showed a picture that included a couple of QSOs with 3B9WR. Now you say the first record in the junk_from_ARRL file is a 3B9WR QSO and the QSO is in the logbook all OK ... but, is the QSO logged as DXCC #207 Rodriguez Island? I did say the "Unable to match QSL credit with ..." was probably as a result of DXCC number mismatch between the LoTW and Logger32.

 

I seem to remember when writing all this silly code, that I had a couple of windows that compared the LoTW_junk with the logbook QSOs side by side, and you could select the junk QSOs one by one and map them to the correct QSO in the logbook (the correct mapping was saved so that next time you did this it would be remembered and not error out) ... What happened to all that stuff?

 

SeventyThree(s).

On July 9, 2019 at 3:28 PM Gary Hinson <Gary@...> wrote:

Hi Bob.

 

I hate loose ends and care about the integrity of my log so I will indeed slog through the 151 exceptions, in due course.  No can-kicking.

 

Yesterday, short of time, I fell at the first hurdle: the first record in the ZL2IFB_junk_from_the_ARRL.txt file reads:

 

3B9WR|207|2010/03/13|16:46:11|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=272161077

 

No clue – there – about why it errored.   

 

I found a 3B9WR QSO in my log at that date, time, mode and band, and it is shown as confirmed on LoTW and (I think) credited to/granted for my DXCC Mixed, CW and 40m awards.   So it looks good to me.   No obvious error.  I gave up.

 

It hadn’t occurred to me to check the LoTW-mismatch.txt file as well, so that’s what I’ll do next – assuming it hasn’t already been overwritten by a LoTW download.

 

By chance, I have a screengrab on my website from a previous run of this process, showing an error message generated by the Batch credit granted update function: see https://www.g4ifb.com/assets/images/auto_generated_images/L32-DXCC-credits-updating.gif   I wasn’t paying close attention but I didn’t notice any of those errors this time around, not one, so I guess something may have changed.

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 09 July 2019 23:56
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Good job Batman. You're hired ... The error message to show "Unable to match QSL credit ..." is as a result of the record from the ARRL/LoTW DXCC number does not match the DXCC number of the QSO in the Logbook. Not a new message. Sorry to be such a PITA, but every detailed must be checked and verified ... No kicking the can down the road here.  Try the built in Club Log option to sanitize your logbook DXCCs with their 560M+ QSO database.

 

Regarding the missing information about how/why the LoTW data could not be matched with your logbook, look in the LoTW-mismatch.txt file. Is that what you need?

 

SeventyThree(s).

On July 8, 2019 at 10:12 PM Gary Hinson <Gary@...> wrote:

Step-by-step, this process worked for me.

 

1.       I started from here: Logger32’s DXCC award report shows 330 current DXCCs confirmed but only 329 granted …

 

 

I’m not sure which confirmed country isn’t marked as Granted in Logger32 as I don’t have any pending DXCC applications on the go, and LoTW shows I have 330 (current) for the Mixed DXCC:



So I decided it’s time to update Logger32.

2.       I ran C:\Logger32\ARRL scraper.exe, entered my LoTW credentials and clicked Start.

3.       The minimalist feedback from ARRL scraper shows it first systematically checking each of my DXCC awards in turn, then removing any pending credits …

 

 

… then downloading the individual QSOs granted for each award, one-by-one, steadily turning the progress bar blue …

 

 

 

It writes granted QSOs to a data file C:\Logger32\ZL2IFB_1_granted_credits scraped data.txt, where ZL2IFB is my callsign and 1 is the LoTW account number I’m using.  My scraped data starts like this:

 

1A0C|246|2012/07/03|20:47:27|SSB|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459625

1A0C|246|2012/07/03|21:16:43|CW|12M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459626

1A0C|246|2012/07/04|01:59:56|CW|20M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459630

1A0C|246|2012/07/04|02:30:43|RTTY|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459631

1A0C|246|2012/07/04|04:08:05|SSB|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459632

1A0C|246|2012/07/04|22:25:47|RTTY|17M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432832487

1A0KM|246|2011/01/29|18:31:49|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=322537469

2M0YIO|279|2011/09/23|10:15:56|RTTY|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=365696173

3A/DL3OCH|260|2008/03/21|18:32:20|CW|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=163312492

 

Each QSO line contains the following fields:

Callsign | DXCC country code | QSO date YYYY/MM/DD UTC | QSO time HH:MM:SS UTC| Mode | Confirmed by a match in LoTW or by QSL card | URL for the QSO record at LoTW

This part of the process is slow (taking about 1 second per QSO) but as the same QSO info appears on the ARRL scraper screen as each record is downloaded and written to the data file (less the URL field and sometimes truncated for space), it is possible to guess which DXCC award is being processed at that point.  Be patient.  It would be much more tedious and error prone to do the lookups and updates manually!

 

Eventually, the blue bar reaches the end sand ARRL scraper stops – no message, no clue, it just disappears in a puff of logic.  Data file written.  Job done.

 

4.       Now I need to import the data file into Logger32.  First, find and run the QSL update function on the Awards menu:

 

Next, click “Update from ARRL file” then read the warning:

 


OK that, then browse to find and select the data file, then fiddle around to get my callsign into the Primary callsign field (there’s a message in the box initially. Click the down arrow to select the next <empty> row.  Then type the callsign in to the box.  This appears to be Turing test.  I think I passed.)

 

 

 

 

Then click Start to set the granted update process running.  It’s another tediously slow process, slightly faster perhaps with the Cluster disconnected and UDP bandmap closed for good measure.  Hard to tell.

 

 

The QSO record currently being processed is at the bottom of the window – not the QSO data line this time but just the callsign, enough to see stuff happening anyway.  Logger32’s main screen blue progress bar also extrudes itself across the screen, slowly, like an uncapped tube of blue toothpaste sitting on the dashboard in bright sunshine.  Yes, the mind wanders.

Also new “Error: Unable to match QSL credits” messages appear sporadically, in my case anyway.  Don’t worry: the errors are written to a data file so we can sort them out afterwards, eventually, when the granted update process completes.

 

5.       Eventually, after about an hour, the granted update completed:



Aside from naming the error file I mentioned, the file itself is opened in a text editor:

… etc.

So those are the QSO lines in the same format as before.  No clue about why they caused errors though, oh no*, so now I have 151 QSOs to check in my log against LoTW. 

* I think something has changed since I last ran this process.  Previously, the error messages indicated what the errors were e.g. country mismatch.  Now, nothing.

6.       Now my DXCC report in Logger32 shows this:




The mysteriously missing credit is now shown as granted.  Maybe I’ll find more things to update among those 151 error’d QSOs … but not today.  This has taken my whole morning!

73 GL,

Gary   ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Chuck Kraly K0XM
Sent: 09 July 2019 06:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Agreed, and this is showing both my present call K0XM, and old call N0BIW

 

 


 


 

 

 


 


 


 

 



 


 


Re: LOTW credit granted is not updating

Gary Hinson
 

OK, the batch updater is done, ending with this popup, same as yesterday:

 

 

The batch updater window does list mismatched QSOs in alphabetical sequence but not the details of why they mismatched e.g.:

 

 

You suggested checking for QSO mismatch errors in LoTW-mismatch.txt … but (judging by the file date) that file was not changed by the batch updater, so I think that was a red herring Bob:

 

  … etc.

 

Right now, LoTW-mismatch.txt appears to show errors from the last time I downloaded confirmations from LoTW – nothing to do with the batch updater:

 

   … etc.

 

As happened yesterday, the file ZL2IFB_junk_from_the_ARRL.txt contains QSO records with no indication of the errors that put them there:

 

… etc.

 

So, now ‘m trying out the “Correct errors” function … which opens to this:

 

 

Errr, I’m not sure what to do here so I’ll explore … QRX (again again).   Animals to feed, fire to poke, tea to brew, work piling up …

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 10 July 2019 08:04
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Gary, found it ... On this window click the CORRECT ERRORS menu. Never tried it, so you're on your own. SeventyThree(s).

 

On July 9, 2019 at 3:46 PM Bob <k4cy@...> wrote:

Gary, coincidence ... You mentioned the error "Unable to match QSL credit with ..." errors, and you showed a picture that included a couple of QSOs with 3B9WR. Now you say the first record in the junk_from_ARRL file is a 3B9WR QSO and the QSO is in the logbook all OK ... but, is the QSO logged as DXCC #207 Rodriguez Island? I did say the "Unable to match QSL credit with ..." was probably as a result of DXCC number mismatch between the LoTW and Logger32.

 

I seem to remember when writing all this silly code, that I had a couple of windows that compared the LoTW_junk with the logbook QSOs side by side, and you could select the junk QSOs one by one and map them to the correct QSO in the logbook (the correct mapping was saved so that next time you did this it would be remembered and not error out) ... What happened to all that stuff?

 

SeventyThree(s).

On July 9, 2019 at 3:28 PM Gary Hinson <Gary@...> wrote:

Hi Bob.

 

I hate loose ends and care about the integrity of my log so I will indeed slog through the 151 exceptions, in due course.  No can-kicking.

 

Yesterday, short of time, I fell at the first hurdle: the first record in the ZL2IFB_junk_from_the_ARRL.txt file reads:

 

3B9WR|207|2010/03/13|16:46:11|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=272161077

 

No clue – there – about why it errored.   

 

I found a 3B9WR QSO in my log at that date, time, mode and band, and it is shown as confirmed on LoTW and (I think) credited to/granted for my DXCC Mixed, CW and 40m awards.   So it looks good to me.   No obvious error.  I gave up.

 

It hadn’t occurred to me to check the LoTW-mismatch.txt file as well, so that’s what I’ll do next – assuming it hasn’t already been overwritten by a LoTW download.

 

By chance, I have a screengrab on my website from a previous run of this process, showing an error message generated by the Batch credit granted update function: see https://www.g4ifb.com/assets/images/auto_generated_images/L32-DXCC-credits-updating.gif   I wasn’t paying close attention but I didn’t notice any of those errors this time around, not one, so I guess something may have changed.

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 09 July 2019 23:56
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Good job Batman. You're hired ... The error message to show "Unable to match QSL credit ..." is as a result of the record from the ARRL/LoTW DXCC number does not match the DXCC number of the QSO in the Logbook. Not a new message. Sorry to be such a PITA, but every detailed must be checked and verified ... No kicking the can down the road here.  Try the built in Club Log option to sanitize your logbook DXCCs with their 560M+ QSO database.

 

Regarding the missing information about how/why the LoTW data could not be matched with your logbook, look in the LoTW-mismatch.txt file. Is that what you need?

 

SeventyThree(s).

On July 8, 2019 at 10:12 PM Gary Hinson <Gary@...> wrote:

Step-by-step, this process worked for me.

 

1.       I started from here: Logger32’s DXCC award report shows 330 current DXCCs confirmed but only 329 granted …

 

 

I’m not sure which confirmed country isn’t marked as Granted in Logger32 as I don’t have any pending DXCC applications on the go, and LoTW shows I have 330 (current) for the Mixed DXCC:



So I decided it’s time to update Logger32.

2.       I ran C:\Logger32\ARRL scraper.exe, entered my LoTW credentials and clicked Start.

3.       The minimalist feedback from ARRL scraper shows it first systematically checking each of my DXCC awards in turn, then removing any pending credits …

 

 

… then downloading the individual QSOs granted for each award, one-by-one, steadily turning the progress bar blue …

 

 

It writes granted QSOs to a data file C:\Logger32\ZL2IFB_1_granted_credits scraped data.txt, where ZL2IFB is my callsign and 1 is the LoTW account number I’m using.  My scraped data starts like this:

 

1A0C|246|2012/07/03|20:47:27|SSB|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459625

1A0C|246|2012/07/03|21:16:43|CW|12M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459626

1A0C|246|2012/07/04|01:59:56|CW|20M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459630

1A0C|246|2012/07/04|02:30:43|RTTY|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459631

1A0C|246|2012/07/04|04:08:05|SSB|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459632

1A0C|246|2012/07/04|22:25:47|RTTY|17M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432832487

1A0KM|246|2011/01/29|18:31:49|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=322537469

2M0YIO|279|2011/09/23|10:15:56|RTTY|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=365696173

3A/DL3OCH|260|2008/03/21|18:32:20|CW|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=163312492

 

Each QSO line contains the following fields:

Callsign | DXCC country code | QSO date YYYY/MM/DD UTC | QSO time HH:MM:SS UTC| Mode | Confirmed by a match in LoTW or by QSL card | URL for the QSO record at LoTW

This part of the process is slow (taking about 1 second per QSO) but as the same QSO info appears on the ARRL scraper screen as each record is downloaded and written to the data file (less the URL field and sometimes truncated for space), it is possible to guess which DXCC award is being processed at that point.  Be patient.  It would be much more tedious and error prone to do the lookups and updates manually!

 

Eventually, the blue bar reaches the end sand ARRL scraper stops – no message, no clue, it just disappears in a puff of logic.  Data file written.  Job done.

 

4.       Now I need to import the data file into Logger32.  First, find and run the QSL update function on the Awards menu:

 

Next, click “Update from ARRL file” then read the warning:


OK that, then browse to find and select the data file, then fiddle around to get my callsign into the Primary callsign field (there’s a message in the box initially. Click the down arrow to select the next <empty> row.  Then type the callsign in to the box.  This appears to be Turing test.  I think I passed.)

 

 

 

 

Then click Start to set the granted update process running.  It’s another tediously slow process, slightly faster perhaps with the Cluster disconnected and UDP bandmap closed for good measure.  Hard to tell.

 

The QSO record currently being processed is at the bottom of the window – not the QSO data line this time but just the callsign, enough to see stuff happening anyway.  Logger32’s main screen blue progress bar also extrudes itself across the screen, slowly, like an uncapped tube of blue toothpaste sitting on the dashboard in bright sunshine.  Yes, the mind wanders.

Also new “Error: Unable to match QSL credits” messages appear sporadically, in my case anyway.  Don’t worry: the errors are written to a data file so we can sort them out afterwards, eventually, when the granted update process completes.

 

5.       Eventually, after about an hour, the granted update completed:



Aside from naming the error file I mentioned, the file itself is opened in a text editor:

… etc.

So those are the QSO lines in the same format as before.  No clue about why they caused errors though, oh no*, so now I have 151 QSOs to check in my log against LoTW. 

* I think something has changed since I last ran this process.  Previously, the error messages indicated what the errors were e.g. country mismatch.  Now, nothing.

6.       Now my DXCC report in Logger32 shows this:




The mysteriously missing credit is now shown as granted.  Maybe I’ll find more things to update among those 151 error’d QSOs … but not today.  This has taken my whole morning!

73 GL,

Gary   ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Chuck Kraly K0XM
Sent: 09 July 2019 06:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Agreed, and this is showing both my present call K0XM, and old call N0BIW

 

 


 


 

 

 


 


 


 


Re: LOTW credit granted is not updating

Gary Hinson
 

OK Bob, QRX (again!).  I’m running the Batch credit granted update thing again and after about an hour the blue bar is nearly all the way to the right …

 

Meanwhile, I’m pretty sure I checked that the 3B9 QSO in question was correctly identified in my log as Rodriguez but I’ll re-check shortly, and I’ll try out the Correct errors thing too.   It’s on the list.

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 10 July 2019 08:04
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Gary, found it ... On this window click the CORRECT ERRORS menu. Never tried it, so you're on your own. SeventyThree(s).

 

On July 9, 2019 at 3:46 PM Bob <k4cy@...> wrote:

Gary, coincidence ... You mentioned the error "Unable to match QSL credit with ..." errors, and you showed a picture that included a couple of QSOs with 3B9WR. Now you say the first record in the junk_from_ARRL file is a 3B9WR QSO and the QSO is in the logbook all OK ... but, is the QSO logged as DXCC #207 Rodriguez Island? I did say the "Unable to match QSL credit with ..." was probably as a result of DXCC number mismatch between the LoTW and Logger32.

 

I seem to remember when writing all this silly code, that I had a couple of windows that compared the LoTW_junk with the logbook QSOs side by side, and you could select the junk QSOs one by one and map them to the correct QSO in the logbook (the correct mapping was saved so that next time you did this it would be remembered and not error out) ... What happened to all that stuff?

 

SeventyThree(s).

On July 9, 2019 at 3:28 PM Gary Hinson <Gary@...> wrote:

Hi Bob.

 

I hate loose ends and care about the integrity of my log so I will indeed slog through the 151 exceptions, in due course.  No can-kicking.

 

Yesterday, short of time, I fell at the first hurdle: the first record in the ZL2IFB_junk_from_the_ARRL.txt file reads:

 

3B9WR|207|2010/03/13|16:46:11|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=272161077

 

No clue – there – about why it errored.   

 

I found a 3B9WR QSO in my log at that date, time, mode and band, and it is shown as confirmed on LoTW and (I think) credited to/granted for my DXCC Mixed, CW and 40m awards.   So it looks good to me.   No obvious error.  I gave up.

 

It hadn’t occurred to me to check the LoTW-mismatch.txt file as well, so that’s what I’ll do next – assuming it hasn’t already been overwritten by a LoTW download.

 

By chance, I have a screengrab on my website from a previous run of this process, showing an error message generated by the Batch credit granted update function: see https://www.g4ifb.com/assets/images/auto_generated_images/L32-DXCC-credits-updating.gif   I wasn’t paying close attention but I didn’t notice any of those errors this time around, not one, so I guess something may have changed.

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 09 July 2019 23:56
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Good job Batman. You're hired ... The error message to show "Unable to match QSL credit ..." is as a result of the record from the ARRL/LoTW DXCC number does not match the DXCC number of the QSO in the Logbook. Not a new message. Sorry to be such a PITA, but every detailed must be checked and verified ... No kicking the can down the road here.  Try the built in Club Log option to sanitize your logbook DXCCs with their 560M+ QSO database.

 

Regarding the missing information about how/why the LoTW data could not be matched with your logbook, look in the LoTW-mismatch.txt file. Is that what you need?

 

SeventyThree(s).

On July 8, 2019 at 10:12 PM Gary Hinson <Gary@...> wrote:

Step-by-step, this process worked for me.

 

1.       I started from here: Logger32’s DXCC award report shows 330 current DXCCs confirmed but only 329 granted …

 

 

I’m not sure which confirmed country isn’t marked as Granted in Logger32 as I don’t have any pending DXCC applications on the go, and LoTW shows I have 330 (current) for the Mixed DXCC:



So I decided it’s time to update Logger32.

2.       I ran C:\Logger32\ARRL scraper.exe, entered my LoTW credentials and clicked Start.

3.       The minimalist feedback from ARRL scraper shows it first systematically checking each of my DXCC awards in turn, then removing any pending credits …

 

 

… then downloading the individual QSOs granted for each award, one-by-one, steadily turning the progress bar blue …

 

 

It writes granted QSOs to a data file C:\Logger32\ZL2IFB_1_granted_credits scraped data.txt, where ZL2IFB is my callsign and 1 is the LoTW account number I’m using.  My scraped data starts like this:

 

1A0C|246|2012/07/03|20:47:27|SSB|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459625

1A0C|246|2012/07/03|21:16:43|CW|12M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459626

1A0C|246|2012/07/04|01:59:56|CW|20M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459630

1A0C|246|2012/07/04|02:30:43|RTTY|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459631

1A0C|246|2012/07/04|04:08:05|SSB|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459632

1A0C|246|2012/07/04|22:25:47|RTTY|17M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432832487

1A0KM|246|2011/01/29|18:31:49|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=322537469

2M0YIO|279|2011/09/23|10:15:56|RTTY|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=365696173

3A/DL3OCH|260|2008/03/21|18:32:20|CW|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=163312492

 

Each QSO line contains the following fields:

Callsign | DXCC country code | QSO date YYYY/MM/DD UTC | QSO time HH:MM:SS UTC| Mode | Confirmed by a match in LoTW or by QSL card | URL for the QSO record at LoTW

This part of the process is slow (taking about 1 second per QSO) but as the same QSO info appears on the ARRL scraper screen as each record is downloaded and written to the data file (less the URL field and sometimes truncated for space), it is possible to guess which DXCC award is being processed at that point.  Be patient.  It would be much more tedious and error prone to do the lookups and updates manually!

 

Eventually, the blue bar reaches the end sand ARRL scraper stops – no message, no clue, it just disappears in a puff of logic.  Data file written.  Job done.

 

4.       Now I need to import the data file into Logger32.  First, find and run the QSL update function on the Awards menu:

 

Next, click “Update from ARRL file” then read the warning:


OK that, then browse to find and select the data file, then fiddle around to get my callsign into the Primary callsign field (there’s a message in the box initially. Click the down arrow to select the next <empty> row.  Then type the callsign in to the box.  This appears to be Turing test.  I think I passed.)

 

 

 

 

Then click Start to set the granted update process running.  It’s another tediously slow process, slightly faster perhaps with the Cluster disconnected and UDP bandmap closed for good measure.  Hard to tell.

 

The QSO record currently being processed is at the bottom of the window – not the QSO data line this time but just the callsign, enough to see stuff happening anyway.  Logger32’s main screen blue progress bar also extrudes itself across the screen, slowly, like an uncapped tube of blue toothpaste sitting on the dashboard in bright sunshine.  Yes, the mind wanders.

Also new “Error: Unable to match QSL credits” messages appear sporadically, in my case anyway.  Don’t worry: the errors are written to a data file so we can sort them out afterwards, eventually, when the granted update process completes.

 

5.       Eventually, after about an hour, the granted update completed:



Aside from naming the error file I mentioned, the file itself is opened in a text editor:

… etc.

So those are the QSO lines in the same format as before.  No clue about why they caused errors though, oh no*, so now I have 151 QSOs to check in my log against LoTW. 

* I think something has changed since I last ran this process.  Previously, the error messages indicated what the errors were e.g. country mismatch.  Now, nothing.

6.       Now my DXCC report in Logger32 shows this:




The mysteriously missing credit is now shown as granted.  Maybe I’ll find more things to update among those 151 error’d QSOs … but not today.  This has taken my whole morning!

73 GL,

Gary   ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Chuck Kraly K0XM
Sent: 09 July 2019 06:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Agreed, and this is showing both my present call K0XM, and old call N0BIW

 

 


 


 

 

 


 


 


 


Re: LOTW credit granted is not updating

Bob
 

Gary, found it ... On this window click the CORRECT ERRORS menu. Never tried it, so you're on your own. SeventyThree(s).



On July 9, 2019 at 3:46 PM Bob <k4cy@...> wrote:

Gary, coincidence ... You mentioned the error "Unable to match QSL credit with ..." errors, and you showed a picture that included a couple of QSOs with 3B9WR. Now you say the first record in the junk_from_ARRL file is a 3B9WR QSO and the QSO is in the logbook all OK ... but, is the QSO logged as DXCC #207 Rodriguez Island? I did say the "Unable to match QSL credit with ..." was probably as a result of DXCC number mismatch between the LoTW and Logger32.


I seem to remember when writing all this silly code, that I had a couple of windows that compared the LoTW_junk with the logbook QSOs side by side, and you could select the junk QSOs one by one and map them to the correct QSO in the logbook (the correct mapping was saved so that next time you did this it would be remembered and not error out) ... What happened to all that stuff?


SeventyThree(s).

On July 9, 2019 at 3:28 PM Gary Hinson <Gary@...> wrote:

Hi Bob.

 

I hate loose ends and care about the integrity of my log so I will indeed slog through the 151 exceptions, in due course.  No can-kicking.

 

Yesterday, short of time, I fell at the first hurdle: the first record in the ZL2IFB_junk_from_the_ARRL.txt file reads:

 

3B9WR|207|2010/03/13|16:46:11|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=272161077

 

No clue – there – about why it errored.   

 

I found a 3B9WR QSO in my log at that date, time, mode and band, and it is shown as confirmed on LoTW and (I think) credited to/granted for my DXCC Mixed, CW and 40m awards.   So it looks good to me.   No obvious error.  I gave up.

 

It hadn’t occurred to me to check the LoTW-mismatch.txt file as well, so that’s what I’ll do next – assuming it hasn’t already been overwritten by a LoTW download.

 

By chance, I have a screengrab on my website from a previous run of this process, showing an error message generated by the Batch credit granted update function: see https://www.g4ifb.com/assets/images/auto_generated_images/L32-DXCC-credits-updating.gif   I wasn’t paying close attention but I didn’t notice any of those errors this time around, not one, so I guess something may have changed.

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 09 July 2019 23:56
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Good job Batman. You're hired ... The error message to show "Unable to match QSL credit ..." is as a result of the record from the ARRL/LoTW DXCC number does not match the DXCC number of the QSO in the Logbook. Not a new message. Sorry to be such a PITA, but every detailed must be checked and verified ... No kicking the can down the road here.  Try the built in Club Log option to sanitize your logbook DXCCs with their 560M+ QSO database.

 

Regarding the missing information about how/why the LoTW data could not be matched with your logbook, look in the LoTW-mismatch.txt file. Is that what you need?

 

SeventyThree(s).

On July 8, 2019 at 10:12 PM Gary Hinson <Gary@...> wrote:

Step-by-step, this process worked for me.

 

1.       I started from here: Logger32’s DXCC award report shows 330 current DXCCs confirmed but only 329 granted …

 

 

I’m not sure which confirmed country isn’t marked as Granted in Logger32 as I don’t have any pending DXCC applications on the go, and LoTW shows I have 330 (current) for the Mixed DXCC:



So I decided it’s time to update Logger32.

2.       I ran C:\Logger32\ARRL scraper.exe, entered my LoTW credentials and clicked Start.

3.       The minimalist feedback from ARRL scraper shows it first systematically checking each of my DXCC awards in turn, then removing any pending credits …

 

 

… then downloading the individual QSOs granted for each award, one-by-one, steadily turning the progress bar blue …

 

 

It writes granted QSOs to a data file C:\Logger32\ZL2IFB_1_granted_credits scraped data.txt, where ZL2IFB is my callsign and 1 is the LoTW account number I’m using.  My scraped data starts like this:

 

1A0C|246|2012/07/03|20:47:27|SSB|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459625

1A0C|246|2012/07/03|21:16:43|CW|12M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459626

1A0C|246|2012/07/04|01:59:56|CW|20M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459630

1A0C|246|2012/07/04|02:30:43|RTTY|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459631

1A0C|246|2012/07/04|04:08:05|SSB|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459632

1A0C|246|2012/07/04|22:25:47|RTTY|17M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432832487

1A0KM|246|2011/01/29|18:31:49|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=322537469

2M0YIO|279|2011/09/23|10:15:56|RTTY|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=365696173

3A/DL3OCH|260|2008/03/21|18:32:20|CW|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=163312492

 

Each QSO line contains the following fields:

Callsign | DXCC country code | QSO date YYYY/MM/DD UTC | QSO time HH:MM:SS UTC| Mode | Confirmed by a match in LoTW or by QSL card | URL for the QSO record at LoTW

This part of the process is slow (taking about 1 second per QSO) but as the same QSO info appears on the ARRL scraper screen as each record is downloaded and written to the data file (less the URL field and sometimes truncated for space), it is possible to guess which DXCC award is being processed at that point.  Be patient.  It would be much more tedious and error prone to do the lookups and updates manually!

 

Eventually, the blue bar reaches the end sand ARRL scraper stops – no message, no clue, it just disappears in a puff of logic.  Data file written.  Job done.

 

4.       Now I need to import the data file into Logger32.  First, find and run the QSL update function on the Awards menu:

 

Next, click “Update from ARRL file” then read the warning:


OK that, then browse to find and select the data file, then fiddle around to get my callsign into the Primary callsign field (there’s a message in the box initially. Click the down arrow to select the next <empty> row.  Then type the callsign in to the box.  This appears to be Turing test.  I think I passed.)

 

 

 

 

Then click Start to set the granted update process running.  It’s another tediously slow process, slightly faster perhaps with the Cluster disconnected and UDP bandmap closed for good measure.  Hard to tell.

 

The QSO record currently being processed is at the bottom of the window – not the QSO data line this time but just the callsign, enough to see stuff happening anyway.  Logger32’s main screen blue progress bar also extrudes itself across the screen, slowly, like an uncapped tube of blue toothpaste sitting on the dashboard in bright sunshine.  Yes, the mind wanders.

Also new “Error: Unable to match QSL credits” messages appear sporadically, in my case anyway.  Don’t worry: the errors are written to a data file so we can sort them out afterwards, eventually, when the granted update process completes.

 

5.       Eventually, after about an hour, the granted update completed:



Aside from naming the error file I mentioned, the file itself is opened in a text editor:

… etc.

So those are the QSO lines in the same format as before.  No clue about why they caused errors though, oh no*, so now I have 151 QSOs to check in my log against LoTW. 

* I think something has changed since I last ran this process.  Previously, the error messages indicated what the errors were e.g. country mismatch.  Now, nothing.

6.       Now my DXCC report in Logger32 shows this:




The mysteriously missing credit is now shown as granted.  Maybe I’ll find more things to update among those 151 error’d QSOs … but not today.  This has taken my whole morning!

73 GL,

Gary   ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Chuck Kraly K0XM
Sent: 09 July 2019 06:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Agreed, and this is showing both my present call K0XM, and old call N0BIW

 

 


 


 

 



 


 


 


Re: LOTW credit granted is not updating

Bob
 

Gary, coincidence ... You mentioned the error "Unable to match QSL credit with ..." errors, and you showed a picture that included a couple of QSOs with 3B9WR. Now you say the first record in the junk_from_ARRL file is a 3B9WR QSO and the QSO is in the logbook all OK ... but, is the QSO logged as DXCC #207 Rodriguez Island? I did say the "Unable to match QSL credit with ..." was probably as a result of DXCC number mismatch between the LoTW and Logger32.


I seem to remember when writing all this silly code, that I had a couple of windows that compared the LoTW_junk with the logbook QSOs side by side, and you could select the junk QSOs one by one and map them to the correct QSO in the logbook (the correct mapping was saved so that next time you did this it would be remembered and not error out) ... What happened to all that stuff?


SeventyThree(s).

On July 9, 2019 at 3:28 PM Gary Hinson <Gary@...> wrote:

Hi Bob.

 

I hate loose ends and care about the integrity of my log so I will indeed slog through the 151 exceptions, in due course.  No can-kicking.

 

Yesterday, short of time, I fell at the first hurdle: the first record in the ZL2IFB_junk_from_the_ARRL.txt file reads:

 

3B9WR|207|2010/03/13|16:46:11|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=272161077

 

No clue – there – about why it errored.   

 

I found a 3B9WR QSO in my log at that date, time, mode and band, and it is shown as confirmed on LoTW and (I think) credited to/granted for my DXCC Mixed, CW and 40m awards.   So it looks good to me.   No obvious error.  I gave up.

 

It hadn’t occurred to me to check the LoTW-mismatch.txt file as well, so that’s what I’ll do next – assuming it hasn’t already been overwritten by a LoTW download.

 

By chance, I have a screengrab on my website from a previous run of this process, showing an error message generated by the Batch credit granted update function: see https://www.g4ifb.com/assets/images/auto_generated_images/L32-DXCC-credits-updating.gif   I wasn’t paying close attention but I didn’t notice any of those errors this time around, not one, so I guess something may have changed.

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 09 July 2019 23:56
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Good job Batman. You're hired ... The error message to show "Unable to match QSL credit ..." is as a result of the record from the ARRL/LoTW DXCC number does not match the DXCC number of the QSO in the Logbook. Not a new message. Sorry to be such a PITA, but every detailed must be checked and verified ... No kicking the can down the road here.  Try the built in Club Log option to sanitize your logbook DXCCs with their 560M+ QSO database.

 

Regarding the missing information about how/why the LoTW data could not be matched with your logbook, look in the LoTW-mismatch.txt file. Is that what you need?

 

SeventyThree(s).

On July 8, 2019 at 10:12 PM Gary Hinson <Gary@...> wrote:

Step-by-step, this process worked for me.

 

1.       I started from here: Logger32’s DXCC award report shows 330 current DXCCs confirmed but only 329 granted …

 

 

I’m not sure which confirmed country isn’t marked as Granted in Logger32 as I don’t have any pending DXCC applications on the go, and LoTW shows I have 330 (current) for the Mixed DXCC:



So I decided it’s time to update Logger32.

2.       I ran C:\Logger32\ARRL scraper.exe, entered my LoTW credentials and clicked Start.

3.       The minimalist feedback from ARRL scraper shows it first systematically checking each of my DXCC awards in turn, then removing any pending credits …

 

 

… then downloading the individual QSOs granted for each award, one-by-one, steadily turning the progress bar blue …

 

 

It writes granted QSOs to a data file C:\Logger32\ZL2IFB_1_granted_credits scraped data.txt, where ZL2IFB is my callsign and 1 is the LoTW account number I’m using.  My scraped data starts like this:

 

1A0C|246|2012/07/03|20:47:27|SSB|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459625

1A0C|246|2012/07/03|21:16:43|CW|12M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459626

1A0C|246|2012/07/04|01:59:56|CW|20M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459630

1A0C|246|2012/07/04|02:30:43|RTTY|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459631

1A0C|246|2012/07/04|04:08:05|SSB|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459632

1A0C|246|2012/07/04|22:25:47|RTTY|17M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432832487

1A0KM|246|2011/01/29|18:31:49|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=322537469

2M0YIO|279|2011/09/23|10:15:56|RTTY|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=365696173

3A/DL3OCH|260|2008/03/21|18:32:20|CW|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=163312492

 

Each QSO line contains the following fields:

Callsign | DXCC country code | QSO date YYYY/MM/DD UTC | QSO time HH:MM:SS UTC| Mode | Confirmed by a match in LoTW or by QSL card | URL for the QSO record at LoTW

This part of the process is slow (taking about 1 second per QSO) but as the same QSO info appears on the ARRL scraper screen as each record is downloaded and written to the data file (less the URL field and sometimes truncated for space), it is possible to guess which DXCC award is being processed at that point.  Be patient.  It would be much more tedious and error prone to do the lookups and updates manually!

 

Eventually, the blue bar reaches the end sand ARRL scraper stops – no message, no clue, it just disappears in a puff of logic.  Data file written.  Job done.

 

4.       Now I need to import the data file into Logger32.  First, find and run the QSL update function on the Awards menu:

 

Next, click “Update from ARRL file” then read the warning:


OK that, then browse to find and select the data file, then fiddle around to get my callsign into the Primary callsign field (there’s a message in the box initially. Click the down arrow to select the next <empty> row.  Then type the callsign in to the box.  This appears to be Turing test.  I think I passed.)

 

 

 

 

Then click Start to set the granted update process running.  It’s another tediously slow process, slightly faster perhaps with the Cluster disconnected and UDP bandmap closed for good measure.  Hard to tell.

 

The QSO record currently being processed is at the bottom of the window – not the QSO data line this time but just the callsign, enough to see stuff happening anyway.  Logger32’s main screen blue progress bar also extrudes itself across the screen, slowly, like an uncapped tube of blue toothpaste sitting on the dashboard in bright sunshine.  Yes, the mind wanders.

Also new “Error: Unable to match QSL credits” messages appear sporadically, in my case anyway.  Don’t worry: the errors are written to a data file so we can sort them out afterwards, eventually, when the granted update process completes.

 

5.       Eventually, after about an hour, the granted update completed:



Aside from naming the error file I mentioned, the file itself is opened in a text editor:

… etc.

So those are the QSO lines in the same format as before.  No clue about why they caused errors though, oh no*, so now I have 151 QSOs to check in my log against LoTW. 

* I think something has changed since I last ran this process.  Previously, the error messages indicated what the errors were e.g. country mismatch.  Now, nothing.

6.       Now my DXCC report in Logger32 shows this:




The mysteriously missing credit is now shown as granted.  Maybe I’ll find more things to update among those 151 error’d QSOs … but not today.  This has taken my whole morning!

73 GL,

Gary   ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Chuck Kraly K0XM
Sent: 09 July 2019 06:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Agreed, and this is showing both my present call K0XM, and old call N0BIW

 

 


 


 

 



 


 


Re: LOTW credit granted is not updating

Gary Hinson
 

Hi Bob.

 

I hate loose ends and care about the integrity of my log so I will indeed slog through the 151 exceptions, in due course.  No can-kicking.

 

Yesterday, short of time, I fell at the first hurdle: the first record in the ZL2IFB_junk_from_the_ARRL.txt file reads:

 

3B9WR|207|2010/03/13|16:46:11|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=272161077

 

No clue – there – about why it errored.   

 

I found a 3B9WR QSO in my log at that date, time, mode and band, and it is shown as confirmed on LoTW and (I think) credited to/granted for my DXCC Mixed, CW and 40m awards.   So it looks good to me.   No obvious error.  I gave up.

 

It hadn’t occurred to me to check the LoTW-mismatch.txt file as well, so that’s what I’ll do next – assuming it hasn’t already been overwritten by a LoTW download.

 

By chance, I have a screengrab on my website from a previous run of this process, showing an error message generated by the Batch credit granted update function: see https://www.g4ifb.com/assets/images/auto_generated_images/L32-DXCC-credits-updating.gif   I wasn’t paying close attention but I didn’t notice any of those errors this time around, not one, so I guess something may have changed.

 

73
Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 09 July 2019 23:56
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Good job Batman. You're hired ... The error message to show "Unable to match QSL credit ..." is as a result of the record from the ARRL/LoTW DXCC number does not match the DXCC number of the QSO in the Logbook. Not a new message. Sorry to be such a PITA, but every detailed must be checked and verified ... No kicking the can down the road here.  Try the built in Club Log option to sanitize your logbook DXCCs with their 560M+ QSO database.

 

Regarding the missing information about how/why the LoTW data could not be matched with your logbook, look in the LoTW-mismatch.txt file. Is that what you need?

 

SeventyThree(s).

On July 8, 2019 at 10:12 PM Gary Hinson <Gary@...> wrote:

Step-by-step, this process worked for me.

 

1.       I started from here: Logger32’s DXCC award report shows 330 current DXCCs confirmed but only 329 granted …

 

 

I’m not sure which confirmed country isn’t marked as Granted in Logger32 as I don’t have any pending DXCC applications on the go, and LoTW shows I have 330 (current) for the Mixed DXCC:



So I decided it’s time to update Logger32.

2.       I ran C:\Logger32\ARRL scraper.exe, entered my LoTW credentials and clicked Start.

3.       The minimalist feedback from ARRL scraper shows it first systematically checking each of my DXCC awards in turn, then removing any pending credits …

 

 

… then downloading the individual QSOs granted for each award, one-by-one, steadily turning the progress bar blue …

 

 

It writes granted QSOs to a data file C:\Logger32\ZL2IFB_1_granted_credits scraped data.txt, where ZL2IFB is my callsign and 1 is the LoTW account number I’m using.  My scraped data starts like this:

 

1A0C|246|2012/07/03|20:47:27|SSB|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459625

1A0C|246|2012/07/03|21:16:43|CW|12M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459626

1A0C|246|2012/07/04|01:59:56|CW|20M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459630

1A0C|246|2012/07/04|02:30:43|RTTY|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459631

1A0C|246|2012/07/04|04:08:05|SSB|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459632

1A0C|246|2012/07/04|22:25:47|RTTY|17M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432832487

1A0KM|246|2011/01/29|18:31:49|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=322537469

2M0YIO|279|2011/09/23|10:15:56|RTTY|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=365696173

3A/DL3OCH|260|2008/03/21|18:32:20|CW|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=163312492

 

Each QSO line contains the following fields:

Callsign | DXCC country code | QSO date YYYY/MM/DD UTC | QSO time HH:MM:SS UTC| Mode | Confirmed by a match in LoTW or by QSL card | URL for the QSO record at LoTW

This part of the process is slow (taking about 1 second per QSO) but as the same QSO info appears on the ARRL scraper screen as each record is downloaded and written to the data file (less the URL field and sometimes truncated for space), it is possible to guess which DXCC award is being processed at that point.  Be patient.  It would be much more tedious and error prone to do the lookups and updates manually!

 

Eventually, the blue bar reaches the end sand ARRL scraper stops – no message, no clue, it just disappears in a puff of logic.  Data file written.  Job done.

 

4.       Now I need to import the data file into Logger32.  First, find and run the QSL update function on the Awards menu:

 

Next, click “Update from ARRL file” then read the warning:


OK that, then browse to find and select the data file, then fiddle around to get my callsign into the Primary callsign field (there’s a message in the box initially. Click the down arrow to select the next <empty> row.  Then type the callsign in to the box.  This appears to be Turing test.  I think I passed.)

 

 

 

 

Then click Start to set the granted update process running.  It’s another tediously slow process, slightly faster perhaps with the Cluster disconnected and UDP bandmap closed for good measure.  Hard to tell.

 

The QSO record currently being processed is at the bottom of the window – not the QSO data line this time but just the callsign, enough to see stuff happening anyway.  Logger32’s main screen blue progress bar also extrudes itself across the screen, slowly, like an uncapped tube of blue toothpaste sitting on the dashboard in bright sunshine.  Yes, the mind wanders.

Also new “Error: Unable to match QSL credits” messages appear sporadically, in my case anyway.  Don’t worry: the errors are written to a data file so we can sort them out afterwards, eventually, when the granted update process completes.

 

5.       Eventually, after about an hour, the granted update completed:



Aside from naming the error file I mentioned, the file itself is opened in a text editor:

… etc.

So those are the QSO lines in the same format as before.  No clue about why they caused errors though, oh no*, so now I have 151 QSOs to check in my log against LoTW. 

* I think something has changed since I last ran this process.  Previously, the error messages indicated what the errors were e.g. country mismatch.  Now, nothing.

6.       Now my DXCC report in Logger32 shows this:




The mysteriously missing credit is now shown as granted.  Maybe I’ll find more things to update among those 151 error’d QSOs … but not today.  This has taken my whole morning!

73 GL,

Gary   ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Chuck Kraly K0XM
Sent: 09 July 2019 06:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Agreed, and this is showing both my present call K0XM, and old call N0BIW

 

 


 


 


Re: LOTW credit granted is not updating

Gary Hinson
 

😊

 

Good point!

 

Logger32 is pretty good at backing itself up automatically before making significant changes … but additional manual backups won’t hurt and might help.  A lot.

 

73
Gary    ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of n5kd
Sent: 09 July 2019 17:53
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Good job Gary.

 

I’d add “BACKUP EVERYTHING” Before starting.

 

Cheers,

 

Pete, N5KD.

 

Sent from my mobile


On Jul 8, 2019, at 21:12, Gary Hinson <Gary@...> wrote:

Step-by-step, this process worked for me.

 

1.       I started from here: Logger32’s DXCC award report shows 330 current DXCCs confirmed but only 329 granted …

 

<image001.png>

 

I’m not sure which confirmed country isn’t marked as Granted in Logger32 as I don’t have any pending DXCC applications on the go, and LoTW shows I have 330 (current) for the Mixed DXCC:

<image005.png>

So I decided it’s time to update Logger32.


2.       I ran C:\Logger32\ARRL scraper.exe, entered my LoTW credentials and clicked Start.


3.       The minimalist feedback from ARRL scraper shows it first systematically checking each of my DXCC awards in turn, then removing any pending credits …

 

<image003.png>

 

… then downloading the individual QSOs granted for each award, one-by-one, steadily turning the progress bar blue …

 

<image004.png>

 

It writes granted QSOs to a data file C:\Logger32\ZL2IFB_1_granted_credits scraped data.txt, where ZL2IFB is my callsign and 1 is the LoTW account number I’m using.  My scraped data starts like this:

 

1A0C|246|2012/07/03|20:47:27|SSB|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459625

1A0C|246|2012/07/03|21:16:43|CW|12M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459626

1A0C|246|2012/07/04|01:59:56|CW|20M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459630

1A0C|246|2012/07/04|02:30:43|RTTY|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459631

1A0C|246|2012/07/04|04:08:05|SSB|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459632

1A0C|246|2012/07/04|22:25:47|RTTY|17M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432832487

1A0KM|246|2011/01/29|18:31:49|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=322537469

2M0YIO|279|2011/09/23|10:15:56|RTTY|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=365696173

3A/DL3OCH|260|2008/03/21|18:32:20|CW|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=163312492

 

Each QSO line contains the following fields:

Callsign | DXCC country code | QSO date YYYY/MM/DD UTC | QSO time HH:MM:SS UTC| Mode | Confirmed by a match in LoTW or by QSL card | URL for the QSO record at LoTW


This part of the process is slow (taking about 1 second per QSO) but as the same QSO info appears on the ARRL scraper screen as each record is downloaded and written to the data file (less the URL field and sometimes truncated for space), it is possible to guess which DXCC award is being processed at that point.  Be patient.  It would be much more tedious and error prone to do the lookups and updates manually!

 

Eventually, the blue bar reaches the end sand ARRL scraper stops – no message, no clue, it just disappears in a puff of logic.  Data file written.  Job done.

 

4.       Now I need to import the data file into Logger32.  First, find and run the QSL update function on the Awards menu:

<image006.png>

 

Next, click “Update from ARRL file” then read the warning:


<image007.png>


OK that, then browse to find and select the data file, then fiddle around to get my callsign into the Primary callsign field (there’s a message in the box initially. Click the down arrow to select the next <empty> row.  Then type the callsign in to the box.  This appears to be Turing test.  I think I passed.)

 

 

 

 

Then click Start to set the granted update process running.  It’s another tediously slow process, slightly faster perhaps with the Cluster disconnected and UDP bandmap closed for good measure.  Hard to tell.

 

<image008.png>


The QSO record currently being processed is at the bottom of the window – not the QSO data line this time but just the callsign, enough to see stuff happening anyway.  Logger32’s main screen blue progress bar also extrudes itself across the screen, slowly, like an uncapped tube of blue toothpaste sitting on the dashboard in bright sunshine.  Yes, the mind wanders.

Also new “Error: Unable to match QSL credits” messages appear sporadically, in my case anyway.  Don’t worry: the errors are written to a data file so we can sort them out afterwards, eventually, when the granted update process completes.

 

5.       Eventually, after about an hour, the granted update completed:

<image009.png>

Aside from naming the error file I mentioned, the file itself is opened in a text editor:

<image010.png>… etc.


So those are the QSO lines in the same format as before.  No clue about why they caused errors though, oh no*, so now I have 151 QSOs to check in my log against LoTW. 

* I think something has changed since I last ran this process.  Previously, the error messages indicated what the errors were e.g. country mismatch.  Now, nothing.


6.       Now my DXCC report in Logger32 shows this:


<image011.png>

The mysteriously missing credit is now shown as granted.  Maybe I’ll find more things to update among those 151 error’d QSOs … but not today.  This has taken my whole morning!


73 GL,

Gary   ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Chuck Kraly K0XM
Sent: 09 July 2019 06:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Agreed, and this is showing both my present call K0XM, and old call N0BIW
<image002.png>


Re: LOTW credit granted is not updating

Tom Wylie
 

Probably a stupid question but I assume you have synced your log with your LOTW downloaded report?


Tom

On Mon, 8 Jul 2019, 19:22 Chuck Kraly K0XM, <ckraly@...> wrote:
Agreed, and this is showing both my present call K0XM, and old call N0BIW


Re: LOTW credit granted is not updating

Bob
 

Good job Batman. You're hired ... The error message to show "Unable to match QSL credit ..." is as a result of the record from the ARRL/LoTW DXCC number does not match the DXCC number of the QSO in the Logbook. Not a new message. Sorry to be such a PITA, but every detailed must be checked and verified ... No kicking the can down the road here.  Try the built in Club Log option to sanitize your logbook DXCCs with their 560M+ QSO database.


Regarding the missing information about how/why the LoTW data could not be matched with your logbook, look in the LoTW-mismatch.txt file. Is that what you need?


SeventyThree(s).

On July 8, 2019 at 10:12 PM Gary Hinson <Gary@...> wrote:

Step-by-step, this process worked for me.

 

  1. I started from here: Logger32’s DXCC award report shows 330 current DXCCs confirmed but only 329 granted …

 

 

I’m not sure which confirmed country isn’t marked as Granted in Logger32 as I don’t have any pending DXCC applications on the go, and LoTW shows I have 330 (current) for the Mixed DXCC:



So I decided it’s time to update Logger32.

  1. I ran C:\Logger32\ARRL scraper.exe, entered my LoTW credentials and clicked Start.

  2. The minimalist feedback from ARRL scraper shows it first systematically checking each of my DXCC awards in turn, then removing any pending credits …

 

 

… then downloading the individual QSOs granted for each award, one-by-one, steadily turning the progress bar blue …

 

 

It writes granted QSOs to a data file C:\Logger32\ZL2IFB_1_granted_credits scraped data.txt, where ZL2IFB is my callsign and 1 is the LoTW account number I’m using.  My scraped data starts like this:

 

1A0C|246|2012/07/03|20:47:27|SSB|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459625

1A0C|246|2012/07/03|21:16:43|CW|12M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459626

1A0C|246|2012/07/04|01:59:56|CW|20M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459630

1A0C|246|2012/07/04|02:30:43|RTTY|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459631

1A0C|246|2012/07/04|04:08:05|SSB|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459632

1A0C|246|2012/07/04|22:25:47|RTTY|17M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432832487

1A0KM|246|2011/01/29|18:31:49|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=322537469

2M0YIO|279|2011/09/23|10:15:56|RTTY|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=365696173

3A/DL3OCH|260|2008/03/21|18:32:20|CW|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=163312492

 

Each QSO line contains the following fields:

Callsign | DXCC country code | QSO date YYYY/MM/DD UTC | QSO time HH:MM:SS UTC| Mode | Confirmed by a match in LoTW or by QSL card | URL for the QSO record at LoTW

This part of the process is slow (taking about 1 second per QSO) but as the same QSO info appears on the ARRL scraper screen as each record is downloaded and written to the data file (less the URL field and sometimes truncated for space), it is possible to guess which DXCC award is being processed at that point.  Be patient.  It would be much more tedious and error prone to do the lookups and updates manually!

 

Eventually, the blue bar reaches the end sand ARRL scraper stops – no message, no clue, it just disappears in a puff of logic.  Data file written.  Job done.

 

  1. Now I need to import the data file into Logger32.  First, find and run the QSL update function on the Awards menu:

 

Next, click “Update from ARRL file” then read the warning:


OK that, then browse to find and select the data file, then fiddle around to get my callsign into the Primary callsign field (there’s a message in the box initially. Click the down arrow to select the next <empty> row.  Then type the callsign in to the box.  This appears to be Turing test.  I think I passed.)

 

 

 

 

Then click Start to set the granted update process running.  It’s another tediously slow process, slightly faster perhaps with the Cluster disconnected and UDP bandmap closed for good measure.  Hard to tell.

 



The QSO record currently being processed is at the bottom of the window – not the QSO data line this time but just the callsign, enough to see stuff happening anyway.  Logger32’s main screen blue progress bar also extrudes itself across the screen, slowly, like an uncapped tube of blue toothpaste sitting on the dashboard in bright sunshine.  Yes, the mind wanders.

Also new “Error: Unable to match QSL credits” messages appear sporadically, in my case anyway.  Don’t worry: the errors are written to a data file so we can sort them out afterwards, eventually, when the granted update process completes.

 

  1. Eventually, after about an hour, the granted update completed:



    Aside from naming the error file I mentioned, the file itself is opened in a text editor:

    … etc.

So those are the QSO lines in the same format as before.  No clue about why they caused errors though, oh no*, so now I have 151 QSOs to check in my log against LoTW. 

* I think something has changed since I last ran this process.  Previously, the error messages indicated what the errors were e.g. country mismatch.  Now, nothing.

  1. Now my DXCC report in Logger32 shows this:




The mysteriously missing credit is now shown as granted.  Maybe I’ll find more things to update among those 151 error’d QSOs … but not today.  This has taken my whole morning!

73 GL,

Gary   ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Chuck Kraly K0XM
Sent: 09 July 2019 06:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Agreed, and this is showing both my present call K0XM, and old call N0BIW

 



 


 


Re: LOTW credit granted is not updating

Chuck Kraly K0XM
 

Thanks Gary, I missed or just plain was "Cranial Flatulent" on the batch update import. Once I did that i worked just as you showed with 47 mismatches which I will look into.
Thanks again.


Re: LOTW credit granted is not updating

n5kd
 

Good job Gary.

I’d add “BACKUP EVERYTHING” Before starting.

Cheers,

Pete, N5KD.


Sent from my mobile

On Jul 8, 2019, at 21:12, Gary Hinson <Gary@...> wrote:

Step-by-step, this process worked for me.

 

  1. I started from here: Logger32’s DXCC award report shows 330 current DXCCs confirmed but only 329 granted …

 

<image001.png>

 

I’m not sure which confirmed country isn’t marked as Granted in Logger32 as I don’t have any pending DXCC applications on the go, and LoTW shows I have 330 (current) for the Mixed DXCC:

<image005.png>

So I decided it’s time to update Logger32.

  1. I ran C:\Logger32\ARRL scraper.exe, entered my LoTW credentials and clicked Start.

  2. The minimalist feedback from ARRL scraper shows it first systematically checking each of my DXCC awards in turn, then removing any pending credits …

 

<image003.png>

 

… then downloading the individual QSOs granted for each award, one-by-one, steadily turning the progress bar blue …

 

<image004.png>

 

It writes granted QSOs to a data file C:\Logger32\ZL2IFB_1_granted_credits scraped data.txt, where ZL2IFB is my callsign and 1 is the LoTW account number I’m using.  My scraped data starts like this:

 

1A0C|246|2012/07/03|20:47:27|SSB|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459625

1A0C|246|2012/07/03|21:16:43|CW|12M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459626

1A0C|246|2012/07/04|01:59:56|CW|20M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459630

1A0C|246|2012/07/04|02:30:43|RTTY|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459631

1A0C|246|2012/07/04|04:08:05|SSB|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459632

1A0C|246|2012/07/04|22:25:47|RTTY|17M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432832487

1A0KM|246|2011/01/29|18:31:49|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=322537469

2M0YIO|279|2011/09/23|10:15:56|RTTY|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=365696173

3A/DL3OCH|260|2008/03/21|18:32:20|CW|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=163312492

 

Each QSO line contains the following fields:

Callsign | DXCC country code | QSO date YYYY/MM/DD UTC | QSO time HH:MM:SS UTC| Mode | Confirmed by a match in LoTW or by QSL card | URL for the QSO record at LoTW

This part of the process is slow (taking about 1 second per QSO) but as the same QSO info appears on the ARRL scraper screen as each record is downloaded and written to the data file (less the URL field and sometimes truncated for space), it is possible to guess which DXCC award is being processed at that point.  Be patient.  It would be much more tedious and error prone to do the lookups and updates manually!

 

Eventually, the blue bar reaches the end sand ARRL scraper stops – no message, no clue, it just disappears in a puff of logic.  Data file written.  Job done.

 

  1. Now I need to import the data file into Logger32.  First, find and run the QSL update function on the Awards menu:

    <image006.png>

 

Next, click “Update from ARRL file” then read the warning:

<image007.png>


OK that, then browse to find and select the data file, then fiddle around to get my callsign into the Primary callsign field (there’s a message in the box initially. Click the down arrow to select the next <empty> row.  Then type the callsign in to the box.  This appears to be Turing test.  I think I passed.)

 

 

 

 

Then click Start to set the granted update process running.  It’s another tediously slow process, slightly faster perhaps with the Cluster disconnected and UDP bandmap closed for good measure.  Hard to tell.

 

<image008.png>

The QSO record currently being processed is at the bottom of the window – not the QSO data line this time but just the callsign, enough to see stuff happening anyway.  Logger32’s main screen blue progress bar also extrudes itself across the screen, slowly, like an uncapped tube of blue toothpaste sitting on the dashboard in bright sunshine.  Yes, the mind wanders.

Also new “Error: Unable to match QSL credits” messages appear sporadically, in my case anyway.  Don’t worry: the errors are written to a data file so we can sort them out afterwards, eventually, when the granted update process completes.

 

  1. Eventually, after about an hour, the granted update completed:

    <image009.png>

    Aside from naming the error file I mentioned, the file itself is opened in a text editor:

    <image010.png>… etc.

So those are the QSO lines in the same format as before.  No clue about why they caused errors though, oh no*, so now I have 151 QSOs to check in my log against LoTW. 

* I think something has changed since I last ran this process.  Previously, the error messages indicated what the errors were e.g. country mismatch.  Now, nothing.

  1. Now my DXCC report in Logger32 shows this:


<image011.png>

The mysteriously missing credit is now shown as granted.  Maybe I’ll find more things to update among those 151 error’d QSOs … but not today.  This has taken my whole morning!

73 GL,

Gary   ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Chuck Kraly K0XM
Sent: 09 July 2019 06:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Agreed, and this is showing both my present call K0XM, and old call N0BIW
<image002.png>


Re: LOTW credit granted is not updating

Gary Hinson
 

Step-by-step, this process worked for me.

 

  1. I started from here: Logger32’s DXCC award report shows 330 current DXCCs confirmed but only 329 granted …

 

 

I’m not sure which confirmed country isn’t marked as Granted in Logger32 as I don’t have any pending DXCC applications on the go, and LoTW shows I have 330 (current) for the Mixed DXCC:



So I decided it’s time to update Logger32.

  1. I ran C:\Logger32\ARRL scraper.exe, entered my LoTW credentials and clicked Start.

  2. The minimalist feedback from ARRL scraper shows it first systematically checking each of my DXCC awards in turn, then removing any pending credits …

 

 

… then downloading the individual QSOs granted for each award, one-by-one, steadily turning the progress bar blue …

 

 

It writes granted QSOs to a data file C:\Logger32\ZL2IFB_1_granted_credits scraped data.txt, where ZL2IFB is my callsign and 1 is the LoTW account number I’m using.  My scraped data starts like this:

 

1A0C|246|2012/07/03|20:47:27|SSB|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459625

1A0C|246|2012/07/03|21:16:43|CW|12M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459626

1A0C|246|2012/07/04|01:59:56|CW|20M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459630

1A0C|246|2012/07/04|02:30:43|RTTY|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459631

1A0C|246|2012/07/04|04:08:05|SSB|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432459632

1A0C|246|2012/07/04|22:25:47|RTTY|17M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=432832487

1A0KM|246|2011/01/29|18:31:49|CW|40M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=322537469

2M0YIO|279|2011/09/23|10:15:56|RTTY|15M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=365696173

3A/DL3OCH|260|2008/03/21|18:32:20|CW|30M|LoTW|https://lotw.arrl.org/lotwuser/qsodetail?qso=163312492

 

Each QSO line contains the following fields:

Callsign | DXCC country code | QSO date YYYY/MM/DD UTC | QSO time HH:MM:SS UTC| Mode | Confirmed by a match in LoTW or by QSL card | URL for the QSO record at LoTW

This part of the process is slow (taking about 1 second per QSO) but as the same QSO info appears on the ARRL scraper screen as each record is downloaded and written to the data file (less the URL field and sometimes truncated for space), it is possible to guess which DXCC award is being processed at that point.  Be patient.  It would be much more tedious and error prone to do the lookups and updates manually!

 

Eventually, the blue bar reaches the end sand ARRL scraper stops – no message, no clue, it just disappears in a puff of logic.  Data file written.  Job done.

 

  1. Now I need to import the data file into Logger32.  First, find and run the QSL update function on the Awards menu:

 

Next, click “Update from ARRL file” then read the warning:


OK that, then browse to find and select the data file, then fiddle around to get my callsign into the Primary callsign field (there’s a message in the box initially. Click the down arrow to select the next <empty> row.  Then type the callsign in to the box.  This appears to be Turing test.  I think I passed.)

 

 

 

 

Then click Start to set the granted update process running.  It’s another tediously slow process, slightly faster perhaps with the Cluster disconnected and UDP bandmap closed for good measure.  Hard to tell.

 



The QSO record currently being processed is at the bottom of the window – not the QSO data line this time but just the callsign, enough to see stuff happening anyway.  Logger32’s main screen blue progress bar also extrudes itself across the screen, slowly, like an uncapped tube of blue toothpaste sitting on the dashboard in bright sunshine.  Yes, the mind wanders.

Also new “Error: Unable to match QSL credits” messages appear sporadically, in my case anyway.  Don’t worry: the errors are written to a data file so we can sort them out afterwards, eventually, when the granted update process completes.

 

  1. Eventually, after about an hour, the granted update completed:



    Aside from naming the error file I mentioned, the file itself is opened in a text editor:

    … etc.

So those are the QSO lines in the same format as before.  No clue about why they caused errors though, oh no*, so now I have 151 QSOs to check in my log against LoTW. 

* I think something has changed since I last ran this process.  Previously, the error messages indicated what the errors were e.g. country mismatch.  Now, nothing.

  1. Now my DXCC report in Logger32 shows this:




The mysteriously missing credit is now shown as granted.  Maybe I’ll find more things to update among those 151 error’d QSOs … but not today.  This has taken my whole morning!

73 GL,

Gary   ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Chuck Kraly K0XM
Sent: 09 July 2019 06:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Agreed, and this is showing both my present call K0XM, and old call N0BIW


Re: LOTW credit granted is not updating

Gary Hinson
 

I’m running an update right now, documenting the whole process step-by-step.  QRX ….

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Richard M. Gillingham
Sent: 09 July 2019 06:35
To: hamlogger@groups.io
Subject: Re: [hamlogger] LOTW credit granted is not updating

 

Strange indeed.   Mine is populated correctly.  Hope you can find a solution.  

 

 

On Monday, July 8, 2019, 02:22:17 PM EDT, Chuck Kraly K0XM <ckraly@...> wrote:

 

 

Agreed, and this is showing both my present call K0XM, and old call N0BIW


Re: LOTW credit granted is not updating

Bob
 

Chuck, I don't QSL, so I've never actually attempted to synchronize LoTW or QSL cards with/between Logger32 and the ARRL, but here's what I'd do ...


Make a dummy CW QSO with K4CY. When it appears in the Logbook Page, right click on the QSO. On the menu click SET/SHOW AWARD CREDITS. You will see eight lists. The third one on the top row is the one you want Check DXCC_MIXED and DXCC_CW. Now click APPLY. Now your DXCC stats should show 1 country submitted. Go back to the Logbook Page Window and right click on the dummy QSO again. and click the same menu item again. This time it is the tight has list in the top row that is of interest.  Check DXCC_MIXED and DXCC_CW and check the LoTW RECEIVED option at the bottom of the Window. Click APPLY. Back to your DXCC stats. 1 Country granted?  Delete the dummy QSO.  


If everything worked as expected, then you are not completing the synchronization process. You apparently have downloaded the information to your PC, but havent imported it into Logger32. Those little checkboxes aren't getting checked. Your best bet is to post step by step what you're doing on here and someone will spot the step you're missing. Good luck, SeventyThree(s).

On July 8, 2019 at 2:08 PM Chuck Kraly K0XM <ckraly@...> wrote:

Agreed, and this is showing both my present call K0XM, and old call N0BIW


 


 


Re: LOTW credit granted is not updating

Richard M. Gillingham
 

Strange indeed.   Mine is populated correctly.  Hope you can find a solution.  


On Monday, July 8, 2019, 02:22:17 PM EDT, Chuck Kraly K0XM <ckraly@...> wrote:


Agreed, and this is showing both my present call K0XM, and old call N0BIW

9461 - 9480 of 86281