Date   

Re: Why is DXKeeper changing some imported Grids?

Stewart Wilkinson
 

On Sun, Jul 3, 2022 at 10:33 PM, Dave AA6YQ wrote:
+ On the Configuration window's "Callbook" tab, do you have the QRZ panel's "Ignore geocoded grid squares" enabled? If not, consider enabling it, as doing so will eliminate a source of inaccurate location information.
Yes that is already selected.
 
--
Stewart G0LGS


Re: APP_DXKeeper_LotW_QSL_SENT incorrectly set to U

Steve K8JQ
 

A section of the web page referenced below reads " . . . check your LotW account to determine whether they've simply not yet been processed, or been processed and generated errors."

Where on the LoTW web site do I look to find QSOs that "
been processed and generated errors"?

Steve, K8JQ



On 7/3/2022 2:02 PM, Dave AA6YQ wrote:

+ AA6YQ comments below
I notice that many DXKeeper entries that have been uploaded to LoTW have APP_DXKeeper_LotW_QSL_SENT set to U. These entries have a date in the APP_DXKeeper_LotW_QSLSDATE field and many of them have a date in the APP_DXKeeper_LotW_QSLRDATE field. If I do an update from LoTW, APP_DXKeeper_LotW_QSL_SENT will be set to Y.

There are thousands of such entries. I do not know how APP_DXKeeper_LotW_QSL_SENT is changed from Y to U sometime after they are initially uploaded to LoTW and have the variable set to Y. Probably of my own doing.

+ I suggest that you review

https://www.dxlabsuite.com/dxkeeper/Help/QSL.htm#Updating_Logged_QSOs_to_their_Reflect_Acceptance_and_Confirmation_by_LotW

+ If you still have questions or concerns, don't hesitate to post them here.

 

Is APP_DXKeeper_LotW_QSL_SENT being incorrectly set to U something to be concerned about? Is it OK to just leave it that way?
+ You should correct this.using the automation that DXKeeper provides. 

        73,

               Dave, AA6YQ


Re: Transferring eQSLcc contact confirmations that have been moved to Archive into DXKeeper

Bob Frostholm
 

Thank you Joe,

This worked

73

Bob

Ko6Lu

On 7/3/2022 5:03 PM, Joe Subich, W4TV via groups.io wrote:

If you hold the Ctrl key while clicking on Sync eQSL.cc QSLs, that
will download *all* QSLs in your account/nickname.

I regularly download QSLs on my office laptop (my "QSL" system)
and then archive any QSLs.  One it a while (every week or two)
I sync eQSL on my shack computer - the shack computer gets QSLs
that have been archived because DXKeeper asks for all QSLs "since"
the last download date.

73,

   ... Joe, W4TV


On 2022-07-03 6:52 PM, Bob Frostholm wrote:
I have successfully downloaded eQSLcc full inbox + archive in a .txt file

There are 16,421 records.

Is there a way I can sync this .txt file to DX Keeper so that these confirmations appear correctly as eQSLcc confirmations?

73

Bob

Ko6Lu

On 7/3/2022 2:52 PM, Dave AA6YQ via groups.io wrote:
+ AA6YQ comments below

    Over the years I've been periodically moving QSOs from my in box
    to Archive in eQSLcc.

    When I Sync eQSLcc QSLs, it seems to sync to my Inbox, as I
    suspect it should. Now I want to collect my old eQSLcc
    confirmations from the Archives... Is there a way to do that with
    DXKeeper or do I need to find a way to move eQSLc QSLs from
    Archive back to my Inbox and resync as previous?

+ As far as I know, there is no programmatic access to eQSL.cc archives that an application like DXKeeper could utilize.

          73,

                  Dave, AA6YQ





updated eQSL AG, LoTW, and RDA databases are available...

Dave AA6YQ
 

...via the Databases tab of DXView's Configuration window.

Terminate DXKeeper and SpotCollector before directing DXKeeper to upgrade these databases.

73,

Dave, AA6YQ


Re: Transferring eQSLcc contact confirmations that have been moved to Archive into DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below
If you hold the Ctrl key while clicking on Sync eQSL.cc QSLs, that
will download *all* QSLs in your account/nickname.

I regularly download QSLs on my office laptop (my "QSL" system)
and then archive any QSLs. One it a while (every week or two)
I sync eQSL on my shack computer - the shack computer gets QSLs
that have been archived because DXKeeper asks for all QSLs "since"
the last download date.
+ If you point me at the eQSL.cc documentation stating that this procedure will report archived QSLs, I will update the DXKeeper documentation accordingly. Thanks!

          73,

                Dave, AA6YQ


Re: Transferring eQSLcc contact confirmations that have been moved to Archive into DXKeeper

Joe Subich, W4TV
 

If you hold the Ctrl key while clicking on Sync eQSL.cc QSLs, that
will download *all* QSLs in your account/nickname.

I regularly download QSLs on my office laptop (my "QSL" system)
and then archive any QSLs. One it a while (every week or two)
I sync eQSL on my shack computer - the shack computer gets QSLs
that have been archived because DXKeeper asks for all QSLs "since"
the last download date.

73,

... Joe, W4TV

On 2022-07-03 6:52 PM, Bob Frostholm wrote:
I have successfully downloaded eQSLcc full inbox + archive in a .txt file
There are 16,421 records.
Is there a way I can sync this .txt file to DX Keeper so that these confirmations appear correctly as eQSLcc confirmations?
73
Bob
Ko6Lu
On 7/3/2022 2:52 PM, Dave AA6YQ via groups.io wrote:
+ AA6YQ comments below

    Over the years I've been periodically moving QSOs from my in box
    to Archive in eQSLcc.

    When I Sync eQSLcc QSLs, it seems to sync to my Inbox, as I
    suspect it should. Now I want to collect my old eQSLcc
    confirmations from the Archives... Is there a way to do that with
    DXKeeper or do I need to find a way to move eQSLc QSLs from
    Archive back to my Inbox and resync as previous?

+ As far as I know, there is no programmatic access to eQSL.cc archives that an application like DXKeeper could utilize.

          73,

                  Dave, AA6YQ


Re: Transferring eQSLcc contact confirmations that have been moved to Archive into DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

I have successfully downloaded eQSLcc full inbox + archive in a .txt file

There are 16,421 records.

Is there a way I can sync this .txt file to DX Keeper so that these confirmations appear correctly as eQSLcc confirmations?

+ There is not.

      73,

            Dave, AA6YQ


Re: Transferring eQSLcc contact confirmations that have been moved to Archive into DXKeeper

Bob Frostholm
 

I have successfully downloaded eQSLcc full inbox + archive in a .txt file

There are 16,421 records.

Is there a way I can sync this .txt file to DX Keeper so that these confirmations appear correctly as eQSLcc confirmations?

73

Bob

Ko6Lu
On 7/3/2022 2:52 PM, Dave AA6YQ via groups.io wrote:

+ AA6YQ comments below
Over the years I've been periodically moving QSOs from my in box to Archive in eQSLcc.

When I Sync eQSLcc QSLs, it seems to sync to my Inbox, as I suspect it should. Now I want to collect my old eQSLcc confirmations from the Archives... Is there a way to do that with DXKeeper or do I need to find a way to move eQSLc QSLs from Archive back to my Inbox and resync as previous?

+ As far as I know, there is no programmatic access to eQSL.cc archives that an application like DXKeeper could utilize.

          73,

                  Dave, AA6YQ


Re: Transferring eQSLcc contact confirmations that have been moved to Archive into DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below
Over the years I've been periodically moving QSOs from my in box to Archive in eQSLcc.

When I Sync eQSLcc QSLs, it seems to sync to my Inbox, as I suspect it should. Now I want to collect my old eQSLcc confirmations from the Archives... Is there a way to do that with DXKeeper or do I need to find a way to move eQSLc QSLs from Archive back to my Inbox and resync as previous?

+ As far as I know, there is no programmatic access to eQSL.cc archives that an application like DXKeeper could utilize.

          73,

                  Dave, AA6YQ


Transferring eQSLcc contact confirmations that have been moved to Archive into DXKeeper

Bob Frostholm
 

Over the years I've been periodically moving QSOs from my in box to Archive in eQSLcc.

When I Sync eQSLcc QSLs, it seems to sync to my Inbox, as I suspect it should. Now I want to collect my old eQSLcc confirmations from the Archives... Is there a way to do that with DXKeeper or do I need to find a way to move eQSLc QSLs from Archive back to my Inbox and resync as previous?

--
73

Bob

Ko6Lu


Re: Why is DXKeeper changing some imported Grids?

Dave AA6YQ
 

+ AA6YQ comments below
If my imported log is wrong then that is my fault and I can (should I wish) go back and fix it - at the moment it is using the wrong data from QRZ because it thinks that is better ! - NOT what I wanted to log.

+ No, DXKeeper is using the latitude and longitude reported by the callbook you've selected because you configured DXKeeper to do so.

+ On the Configuration window's "Callbook" tab, do you have the QRZ panel's "Ignore geocoded grid squares" enabled? If not, consider enabling it, as doing so will eliminate a source of inaccurate location information.

        73,

               Dave, AA6YQ


Re: Why is DXKeeper changing some imported Grids?

Stewart Wilkinson
 
Edited

If my imported log is wrong then that is my fault and I can (should I wish) go back and fix it - at the moment it is using the wrong data from QRZ because it thinks that is better ! - NOT what I wanted to log.

--
Stewart G0LGS


Re: Why is DXKeeper changing some imported Grids?

Stewart Wilkinson
 
Edited

 

+ There is no way for DXKeeper to know whether the gridsquare specified in the QSO record came from an accurate source or a potentially inaccurate source - like a Callbook record or a previously logged QSO.

So allow me to STOP DXKeeper from using the wrong one !

--
Stewart G0LGS


Re: Why is DXKeeper changing some imported Grids?

Stewart Wilkinson
 

At least give me the choice of wether I want to use the Grid from the Callbook  or the one from my Log - until a few days ago it used the one from my Log which was fine - now it changes it without asking me and I have to got back to each record and fix it.

--
Stewart G0LGS


Re: Why is DXKeeper changing some imported Grids?

Dave AA6YQ
 

+ AA6YQ comments below
If I type a Grid into the log it is becasue that is the one I was given as part of the QSO - typcially a VHF or UHF contest QSO that gets logged by the contest logging program I happen to use for the given contest - the one I mostly use does NOT query any online log book or other external source to get missing information, so it does not put name, placename or any other information into into exported ADIF.

+ There is no way for DXKeeper to know whether the gridsquare specified in the QSO record came from an accurate source or a potentially inaccurate source - like a Callbook record or a previously logged QSO.

Surely it would be better to use the Grid given in the ADIF if there is one and use the Callbook one when there is none in the ADIF
+ I disagree, for the reason stated immediately above.

- or give us the option to decide if we want to use the one from the Callbook source without breaking the import of other data.

+ DXKeeper informs you when it imports a gridsquare other than the one specified in the QSO record. If you consider the imported grid square to be more accurate, you can restore it. In the two cases you cited, the first 4 characters of the gridsquare were unchanged, meaning there would be no adverse impact on VUCC or Maidenhead Squares award progress as a result of an inaccurate latitude and longitude in the Callbook record..

     73,

             Dave, AA6YQ


Re: Why is DXKeeper changing some imported Grids?

Stewart Wilkinson
 
Edited

If I type a Grid into the log it is becasue that is the one I was given as part of the QSO - typcially a VHF or UHF contest QSO that gets logged by the contest logging program I happen to use for the given contest - the one I mostly use does NOT query any online log book or other external source to get missing information, so it does not put name, placename or any other information into into exported ADIF.

Surely it would be better to use the Grid given in the ADIF if there is one and use the Callbook one when there is none in the ADIF - or give us the option to decide if we want to use the one from the Callbook source without breaking the import of other data.

--
Stewart G0LGS


Re: Why is DXKeeper changing some imported Grids?

Dave AA6YQ
 

+ AA6YQ comments below
So what happens if other items are missing  i.e: name, place name etc.

If I untick the box you suggested it will fail to import those, but if I leave it ticked it replaces a perfectly good grid reference with a wrong one

+ if you provide me with a function that separates accurate callbook information from inaccurate callbook information, I will incorporate it.

    73,

             Dave, AA6YQ

 


Re: Why is DXKeeper changing some imported Grids?

Stewart Wilkinson
 

So what happens if other items are missing  i.e: name, place name etc.

If I untick the box you suggested it will fail to import those, but if I leave it ticked it replaces a perfectly good grid reference with a wrong one.

--
Stewart G0LGS


Re: FST4 export

N4EIS
 

You guys aren't alone. For me, I logged QSOs in FT4 mode. FT8 mode shows up in the Mode column, but for FT4, MFSK shows up in Mode and FT4 shows up in SubMode, but only in the QSO Export for tab-delimited file. On the Log QSOs tab, there is no SubMode. However, there is an FT4 mode and an MFSK mode in the pull-down. 

If this is the problem  VE3KI found, then the correction is probably in place. I would like to see the update also.
Thanks to ALL who have invested time and sweat into this software. It is a bit challenging for a newbie like me, but I can appreciate growing into it.

73's
Jeff, N4EIS


Re: Why is DXKeeper changing some imported Grids?

Dave AA6YQ
 

+ AA6YQ comments below
No:

+ If the imported record did not specify a latitude and longitude, and if the "Query callbook and DXCC database for missing items" option was enabled on the Main window's "Import QSOs" tab, then DXKeeper correctly obtained the latitude and longitude from the Callbook you specified on the Configuration window's Callbook tab, computed the grid square that contains that latitude and longitude, and compared the computed grid square to the imported grid square. Since the imported grid square was 6 characters in length and didn't match the computed grid square, the imported grid square was replaced. Had the imported grid square been 4 characters in length, and had those 4 characters matched the first 4 characters of the computed grid square, the imported grid square would not have been replaced.

de AA6YQ

2221 - 2240 of 211124