Date   

Re: LoTW database updates and purges !

Andrew OBrien
 

Thanks Dave , the callsign in question was VP8LP.

Andy

On Dec 13, 2019, at 2:51 PM, Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

Just wondering how the LoTW database gets purged occasionally? When we do an update is the database just a list of stations with
current certificates ?

+ Each Sunday, the ARRL updates its list of callsigns to which an active Callsign Certificate has been issued, along with the "date
of last update" for each. I try to generate an LoTW database from this list every other week.

+ When you type a callsign into DXView and strike the Enter key, it displays the date of last upload to LoTW.

+ DXKeeper ("QSL Configuration window's LoTW tab) and SpotCollector (Configuration window's Spot Database tab) each let you specify
a maximum age of last LoTW upload for a station to be considered a participant in LoTW.

I worked a station today that has not uploaded to LoTW since 2012 . He shows in DX View as LOTW , so does that mean he has a
certificate and simply has not bothered to upload ?

+ It's not possible to answer your question from the information provided. The station's op may have uploaded all his or her QSOs
made with that callsign, and then switched to another callsign. I haven't uploaded any 8P9RY QSOs since 2016 because I haven't been
in 8P since then.

73,

Dave, AA6YQ




Re: LOTW Credits

Julio Peralta
 

I can't find any QSO records anywhere in my log
that have a V in the LOTW rcvd box.

Julio

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On
Behalf Of Dave AA6YQ
Sent: Friday, December 13, 2019 2:55 PM
To: DXLab@groups.io
Subject: Re: [DXLab] LOTW Credits

+ AA6YQ comments below

So even though all the numbers in the "New LOTW
QSL's" column and there are all zero's in the
"LOTW QSL's in Process" column the
ARRL hasn't caused the QSO's to be Verified!

+ I can only interpret the results you report,
Julio. In your DXCC account, check one of the
entities, entity-band, or entity-mode
for which you just submitted an LoTW confirmation
for DXCC credit. Is a credit now present?

73,

Dave, AA6YQ


LOTW Download DXK message "no matching QSO in LOG"

Jim Miller, AB3CV
 

Just did a download for a new DXLabs user from LOTW and got about a dozen such messages of "no matching QSO in Log".

I failed to allow the reporting to a file for later inspection. (dummy me...)

Not sure how to get the info again.

Should I do a full sync (ctrl-Synch) with a report to a file?

I never have this problem on my own logs so I'm a bit adrift here.

Thanks

Jim ab3cv


Re: LOTW Credits

Dave AA6YQ
 

+ AA6YQ comments below

So even though all the numbers in the "New LOTW QSL's" column and there are all zero's in the "LOTW QSL's in Process" column the
ARRL hasn't caused the QSO's to be Verified!

+ I can only interpret the results you report, Julio. In your DXCC account, check one of the entities, entity-band, or entity-mode
for which you just submitted an LoTW confirmation for DXCC credit. Is a credit now present?

73,

Dave, AA6YQ


Re: Modifying Records

Phil & Anne Irons
 

Hi Rod...

If you already have QSL information for those 95K contacts, you might find this website useful:


It asks for an address, city & state or zip; or a callsign--if your contact has moved since the QSO, the address from his QSL info at the time will give you the grid info you seek, which negates downside B of Dave's reply.  However, (and there's always one of those, isn't there?) entering 95k callsigns or addresses will take a little while...perhaps if you group them by city & state that may simplify things a bit.

Hope this helps!

73 & Season's Greetings

Phil Irons/VE1BVD
Sydney, NS (FN96vd) 


On Fri, Dec 13, 2019 at 1:19 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

I've checked several of the records with JJ00aa and none of them have Latitude and Longitude. And no, I do not have the original file that I imported. It was several months ago that I made the import.

+ If that's the situation, your only recourse would be to filter the Log Page Display to contain all QSOs whose Gridsquare items are now set to JJ00aa

1. clear the Gridsquares items of all QSOs in the Log Page Display

2. Perform a callbook update on all QSOs in the Log Page Display


+ There are two potential downsides to step 2

A. If your callbook is "QRZ.com via Pathfinder", the update will proceed at the rate of 1 QSO every 4 seconds (pacing required by QRZ management)

B. Callbook updates for older QSOs may populate the QSO with information that is obsolete (e.g. QSO partner relocated since you worked them)

       73,

              Dave, AA6YQ






--
Phil & Anne Irons
Sydney, Nova Scotia


Re: LoTW database updates and purges !

Dave AA6YQ
 

+ AA6YQ comments below

Just wondering how the LoTW database gets purged occasionally? When we do an update is the database just a list of stations with
current certificates ?

+ Each Sunday, the ARRL updates its list of callsigns to which an active Callsign Certificate has been issued, along with the "date
of last update" for each. I try to generate an LoTW database from this list every other week.

+ When you type a callsign into DXView and strike the Enter key, it displays the date of last upload to LoTW.

+ DXKeeper ("QSL Configuration window's LoTW tab) and SpotCollector (Configuration window's Spot Database tab) each let you specify
a maximum age of last LoTW upload for a station to be considered a participant in LoTW.

I worked a station today that has not uploaded to LoTW since 2012 . He shows in DX View as LOTW , so does that mean he has a
certificate and simply has not bothered to upload ?

+ It's not possible to answer your question from the information provided. The station's op may have uploaded all his or her QSOs
made with that callsign, and then switched to another callsign. I haven't uploaded any 8P9RY QSOs since 2016 because I haven't been
in 8P since then.

73,

Dave, AA6YQ


Re: LOTW Credits

Julio Peralta
 

So even though all the numbers in the "New LOTW
QSL's" column and there are all zero's in the
"LOTW QSL's in Process" column the ARRL hasn't
caused the QSO's to be Verified!

Julio

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On
Behalf Of Dave AA6YQ
Sent: Friday, December 13, 2019 12:22 PM
To: DXLab@groups.io
Subject: Re: [DXLab] LOTW Credits

+ AA6YQ comments below

Dave I've looked at more than 100 Q's in my log
that are LOTW and none of them are showing a V in
the LOTW rcvd box. I'm not 100%
sure that is what you wanted me to try to find.

In addition right clicking on the log entry
without the V and selecting Update from LOTW
doesn't change anything in the log record.

I hope I did that right.

+ A QSO whose "LoTW QSL Rcvd" item is set to 'Y'
has been confirmed for DXCC via LoTW, but has not
received DXCC award credit for
its LoTW confirmation.

+ If you right-click the Log Page Display entry
for a QSO whose "LoTW QSL Rcvd" item is set to
'Y', select "update from LoTW", and
see that its "LoTW QSL Rcvd" item is still set to
'Y' after the operation completes, then that QSO
has still not been granted DXCC
award credit for its LoTW confirmation.

73,

Dave, AA6YQ


LoTW database updates and purges !

Andrew OBrien
 

Just wondering how the LoTW database gets purged occasionally ? When we do an update is the database just a list of stations with current certificates ? I worked a station today that has not uploaded to LoTW since 2012 . He shows in DX View as LOTW , so does that mean he has a certificate and simply has not bothered to upload ?
Andy


Re: Can't sync LotW QSLs in DXKeeper

Dave AA6YQ
 

The behavior reported in the post below is the result of a regression defect inadvertently introduced in DXKeeper 15.3.0 earlier this week: if a user has never before executed the "Sync LotW QSOs", "Sync LoTW QSLs", or "Sync eQSL QSLs" function, an attempted invocation will result in DXKeeper informing them that the date-and-time of last synchronization is invalid. This defect has been corrected in DXKeeper 15.3.1, which I will release later today.

73,

Dave, AA6YQ

I'm using JTAlert for logging to LotW (and eQSL.cc). When I loggin to my account in LotW it shows my uploaded QSOs, In DXKeeper, the QSL tab and with LotW selected, below "Upload to LotW", is shown the latest upload date/time.
For example 2019-12-13 12:37:25, and valid Station Location and Station Callsign.

When I click om Sync Lotw QSOs or Sync LotW QSLs a error message is shown:
the date-and-time of last LoTW QSL synchronization shown beneath 'Sunc LoTW QSLs' button is invalid. double click the date-and-time to correct it

But no date/time is shown below the sync buttons!


Re: Can't sync LotW QSLs in DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

I'm using JTAlert for logging to LotW (and eQSL.cc). When I loggin to my account in LotW it shows my uploaded QSOs, In DXKeeper, the QSL tab and with LotW selected, below "Upload to LotW", is shown the latest upload date/time.
For example 2019-12-13 12:37:25, and valid Station Location and Station Callsign.

When I click om Sync Lotw QSOs or Sync LotW QSLs a error message is shown:
the date-and-time of last LoTW QSL synchronization shown beneath 'Sunc LoTW QSLs' button is invalid. double click the date-and-time to correct it

But no date/time is shown below the sync buttons!

+ Please double-click in the area midway between the "Sync LoTW QSLs" button and the "Update from LoTW" button. Does a small "LoTW QSL Synchronization" window appear?

73,

Dave, AA6YQ


Re: LOTW Credits

Dave AA6YQ
 

+ AA6YQ comments below

Dave I've looked at more than 100 Q's in my log that are LOTW and none of them are showing a V in the LOTW rcvd box. I'm not 100%
sure that is what you wanted me to try to find.

In addition right clicking on the log entry without the V and selecting Update from LOTW doesn't change anything in the log record.

I hope I did that right.

+ A QSO whose "LoTW QSL Rcvd" item is set to 'Y' has been confirmed for DXCC via LoTW, but has not received DXCC award credit for
its LoTW confirmation.

+ If you right-click the Log Page Display entry for a QSO whose "LoTW QSL Rcvd" item is set to 'Y', select "update from LoTW", and
see that its "LoTW QSL Rcvd" item is still set to 'Y' after the operation completes, then that QSO has still not been granted DXCC
award credit for its LoTW confirmation.

73,

Dave, AA6YQ


Re: Modifying Records

Dave AA6YQ
 

+ AA6YQ comments below

I've checked several of the records with JJ00aa and none of them have Latitude and Longitude. And no, I do not have the original file that I imported. It was several months ago that I made the import.

+ If that's the situation, your only recourse would be to filter the Log Page Display to contain all QSOs whose Gridsquare items are now set to JJ00aa

1. clear the Gridsquares items of all QSOs in the Log Page Display

2. Perform a callbook update on all QSOs in the Log Page Display


+ There are two potential downsides to step 2

A. If your callbook is "QRZ.com via Pathfinder", the update will proceed at the rate of 1 QSO every 4 seconds (pacing required by QRZ management)

B. Callbook updates for older QSOs may populate the QSO with information that is obsolete (e.g. QSO partner relocated since you worked them)

73,

Dave, AA6YQ


Can't sync LotW QSLs in DXKeeper

Markku SM5FLM
 

I'm using JTAlert for logging to LotW (and eQSL.cc). When I loggin to my account in LotW it shows my uploaded QSOs,
In DXKeeper, the QSL tab and with LotW selected, below "Upload to LotW", is shown the latest upload date/time.
For example 2019-12-13 12:37:25, and valid Station Location and Station Callsign.

When I click om Sync Lotw QSOs or Sync LotW QSLs a error message is shown:
the date-and-time of last LoTW QSL synchronization shown beneath 'Sunc LoTW QSLs' button is invalid. double click the date-and-time to correct it

But no date/time is shown below the sync buttons!


Re: LOTW Credits

Julio Peralta
 

Dave I've looked at more than 100 Q's in my log
that are LOTW and none of them are showing a V in
the LOTW rcvd box. I'm not 100% sure that is what
you wanted me to try to find.

In addition right clicking on the log entry
without the V and selecting Update from LOTW
doesn't change anything in the log record.

I hope I did that right.

Julio, W4HY

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On
Behalf Of Dave AA6YQ
Sent: Thursday, December 12, 2019 12:10 PM
To: DXLab@groups.io
Subject: Re: [DXLab] LOTW Credits

In the message below, I meant to say

"Identify a QSO to whose LoTW confirmation you
believe DXCC award credit has newly been granted".

73,

Dave, AA6YQ


I have completed the transaction of buying the
LOTW credits and see on the LOTW site the credits
have been moved over to I believe
the DXCC credits Awarded column.

However when I have done Sync LoTW QSLs I haven't
seen any indication that DXK has updated the data
base with that information.
Shouldn't the popup box that shows how many QSO's
have been updated show that hundreds of QSO have
been changed at some point?

+ Identify a QSO whose LoTW confirmation you
believe is newly-granted. Select the Log Page
Display entry for this QSO.

1. what is the current value of this QSO's "LoTW
QSL Confirmed" item

2. right-click the Log Page Display entry, and
select "Update from LoTW" in the pop-up menu

3. what is now the current value of this QSO's
"LoTW QSL Confirmed" item

73,

Dave, AA6YQ





--
This email has been checked for viruses by AVG.
https://www.avg.com


Re: Modifying Records

Rod Greene
 

I've checked several of the records with JJ00aa and none of them have Latitude and Longitude. And no, I do not have the original file that I imported. It was several months ago that I made the import.

Thanks and 73, Rod/w7zrc

On Thursday, December 12, 2019, 4:28:52 PM MST, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below

I've got a lot of records with an incorrect grid square in my DXK log. This incorrect grid square happened, I think, due to the way I exported from my old log or something I did not set correctly on import. Anyway, I want to get rid of the incorrect grid square and put in something that would indicate a grid square was not recorded. The incorrect grid square value is "JJ00aa".

So my question is this good thinking? ie, put in something in the Grid Square field that would indicate a grid was not recorded...
Second question if the above question is answered yes, then what is my process?


I already have a SQL filter to select all the bad grid square records.


From the documentation and the "DXKeeper Advanced Sorts, Filters & Modifiers" page, it looks like the change-to field should just be left blank.


I tested that modifier change and it seemed to work okay, but before I change >95,000 records I'd like to have some affirmation that is a good procedure.

+ Clearing the Grid item is certainly an improvement over leaving it set to a known-erroneous value. But before you do that, it might be possible to obtain the correct grid square. Do the QSOs with an incorrect grid square specify a latitude and longitude?

+ How long ago did you import the ADIF file from your "old log"? Do you still have that file?


          73,


              Dave, AA6YQ






Re: SC problem

David Bunte
 

Dave -

Many thanks... that fixed it.

73 de Dave - K9FN

On Thu, Dec 12, 2019 at 10:13 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

I got back home last night after a short vacation and did all of the upgrades that had accumulated over the past 10 or 12 days.

I then rebooted my machine and fired up Launcher, followed by CMD, DXK, DXV, SC and WW.

I made a couple of QSOs today and then noted a spot for TO9W, with a '?' rather than FS, since I did not have an override for that one. Usually I manually enter overrides, but this time decided to let SC do that for me. I selected the ClubLog tab and after it was back up, when it then directed SC to launch I got the following message:

"Band-Mode file C:\DXLab\SpotCollector\bandModes 2017-12-27.txt does not exist; spot database entries will be missing Band and Mode fields."

+ In the "Sub-band Definition" panel at the bottom of the General tab of SpotCollector's Configuration window, you have specified the pathname

C:\DXLab\SpotCollector\bandModes 2017-12-27.txt

+ Evidently, this file does not exist.

+ Each SpotCollector update includes a sub-band definition file; the most recent is named

BandModes 2019-05-02.txt

+ and includes definitions for the FT4 sub-bands. To use this sub-band definition file,

1. in SpotCollector's "Sub-band Definition" panel, click the Select button, and use the "Open" window to navigate to your SpotCollector folder and select the file

BandModes 2019-05-02.txt

2. terminate and restart SpotCollector

           73,

                  Dave, AA6YQ






Re: SC problem

Dave AA6YQ
 

+ AA6YQ comments below

I got back home last night after a short vacation and did all of the upgrades that had accumulated over the past 10 or 12 days.

I then rebooted my machine and fired up Launcher, followed by CMD, DXK, DXV, SC and WW.

I made a couple of QSOs today and then noted a spot for TO9W, with a '?' rather than FS, since I did not have an override for that one. Usually I manually enter overrides, but this time decided to let SC do that for me. I selected the ClubLog tab and after it was back up, when it then directed SC to launch I got the following message:

"Band-Mode file C:\DXLab\SpotCollector\bandModes 2017-12-27.txt does not exist; spot database entries will be missing Band and Mode fields."

+ In the "Sub-band Definition" panel at the bottom of the General tab of SpotCollector's Configuration window, you have specified the pathname

C:\DXLab\SpotCollector\bandModes 2017-12-27.txt

+ Evidently, this file does not exist.

+ Each SpotCollector update includes a sub-band definition file; the most recent is named

BandModes 2019-05-02.txt

+ and includes definitions for the FT4 sub-bands. To use this sub-band definition file,

1. in SpotCollector's "Sub-band Definition" panel, click the Select button, and use the "Open" window to navigate to your SpotCollector folder and select the file

BandModes 2019-05-02.txt

2. terminate and restart SpotCollector

73,

Dave, AA6YQ


Re: Satellite Tracking and reaction tuning using Commander

W8DSB
 

Thank you to John and Dave I got it working. The radio and PC stop once in a while but it trackers about 85% of the time. I will figure out the rest.


SC problem

David Bunte
 

I got back home last night after a short vacation and did all of the upgrades that had accumulated over the past 10 or 12 days. 

I then rebooted my machine and fired up Launcher, followed by CMD, DXK, DXV, SC and WW. 

I made a couple of QSOs today and then noted a spot for TO9W, with a '?' rather than FS, since I did not have an override for that one. Usually I manually enter overrides, but this time decided to let SC do that for me. I selected the ClubLog tab and after it was back up, when it then directed SC to launch I got the following message:

"Band-Mode file C:\DXLab\SpotCollector\bandModes 2017-12-27.txt does not exist; spot database entries will be missing Band and Mode fields."

There was a button that said "OK", which I selected, then SC launched, and at first glance looked normal... However, I saw no spots come in during the next 90 minutes or so, and decided to shut down the entire suite, reboot again and then launch. When SC launched I got that same error message... and now, 30 minutes later, still no spots... all three of my spot sources loaded as usual.

My first assumption is that I have done something that I should not have done, but am at a loss to figure out what that might have been.

I need and welcome assistance.

Dave - K9FN


Re: Modifying Records

Dave AA6YQ
 

+ AA6YQ comments below

I've got a lot of records with an incorrect grid square in my DXK log. This incorrect grid square happened, I think, due to the way I exported from my old log or something I did not set correctly on import. Anyway, I want to get rid of the incorrect grid square and put in something that would indicate a grid square was not recorded. The incorrect grid square value is "JJ00aa".

So my question is this good thinking? ie, put in something in the Grid Square field that would indicate a grid was not recorded...
Second question if the above question is answered yes, then what is my process?


I already have a SQL filter to select all the bad grid square records.


From the documentation and the "DXKeeper Advanced Sorts, Filters & Modifiers" page, it looks like the change-to field should just be left blank.


I tested that modifier change and it seemed to work okay, but before I change >95,000 records I'd like to have some affirmation that is a good procedure.

+ Clearing the Grid item is certainly an improvement over leaving it set to a known-erroneous value. But before you do that, it might be possible to obtain the correct grid square. Do the QSOs with an incorrect grid square specify a latitude and longitude?

+ How long ago did you import the ADIF file from your "old log"? Do you still have that file?

73,

Dave, AA6YQ

20021 - 20040 of 209579