Date   

Re: Meteor scatter

Joe - W9RF
 

Dave,


Since I hop around most of time and don't dedicate a lot of time on MSK144 I think I'll forego the default and just use the pull down window on propagation/meteor scatter.

I just checked LoTW and they do in fact track MSK144, it can be used for an endorsement sticker for the Digital WAS Certificate.

But LoTW tracks from my uploaded mode not from my propagation entry.



thanks..


73,

W9RF - Joe




On Monday, January 4, 2021, 2:59:15 PM CST, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below

I have been working the recent meteor showers and have made a few contacts via MSK144, my question is do I need to enter the name of the meteor shower in the propagation box or is this for my consumption only?

+ I don't know what if any requirements there might be for awards based on MSK144 QSOs. My advice is to select or enter the name of the meteor shower on the Configuration window's Defaults tab at the beginning of a meteor shower session, and then clear it after the session is complete.


The ones that have been confirmed did not populate the propagation box.

+ MSK144 might be used with other propagation modes, like Aircraft Scatter, so DXKeeper does not automatically set a QSO's propagation mode to MS when you set its mode to MSK144.

+ In response to a "Sync LoTW QSLs" operation, LoTW does report the propagation mode reported by your QSO partner, but DXKeeper currently ignores it on the assumption that you're more likely to log this item correctly than your QSO partner.

        73,

              Dave, AA6YQ







Re: Meteor scatter

Dave AA6YQ
 

+ AA6YQ comments below

I have been working the recent meteor showers and have made a few contacts via MSK144, my question is do I need to enter the name of the meteor shower in the propagation box or is this for my consumption only?

+ I don't know what if any requirements there might be for awards based on MSK144 QSOs. My advice is to select or enter the name of the meteor shower on the Configuration window's Defaults tab at the beginning of a meteor shower session, and then clear it after the session is complete.


The ones that have been confirmed did not populate the propagation box.

+ MSK144 might be used with other propagation modes, like Aircraft Scatter, so DXKeeper does not automatically set a QSO's propagation mode to MS when you set its mode to MSK144.

+ In response to a "Sync LoTW QSLs" operation, LoTW does report the propagation mode reported by your QSO partner, but DXKeeper currently ignores it on the assumption that you're more likely to log this item correctly than your QSO partner.

73,

Dave, AA6YQ


Re: Challenges with DXCC/Challenge submission using LOTW confirmations

Dave AA6YQ
 

+ AA6YQ comnents below
with DXCC/Challenge submission using LOTW confirmations


The bottom line is that with DXKeeper and the LOTW webpage using
different selection algorithms, the "assemble submission" path is
difficult to use since the QSOs proposed by DXKeeper are not available
for selection on the application webpage.
Selections are not made on the "application" webpage.

Start by selecting *CLEAR ALL* on the application page. The go to "My QSOs" page, select your DXCC account, search for Confirmations
(QSLs) from each station (or for each country), place a check mark beside those QSLs DXKeeper has selected and click "Submit DXCC Credit Changes".

This process will populate the "Application" web page with (only) those QSLs selected by DXKeeper.

BTW, LotW simply selects confirmations on a "first received" basis.


+ The above procedure is documented here:

"Submitting an LotW DXCC Application from the LotW web site"

https://www.dxlabsuite.com/dxlabwiki/SubmitLotW

+ This is "step 6" in

"Generating an LotW Submission"

https://www.dxlabsuite.com/dxlabwiki/GenerateSubmission

73,

Dave, AA6YQ


Re: B VFO tuning in Commander

Dave AA6YQ
 

+ AA6YQ comments below

Hello everyone, I like the B VFO offset in Commander, and wonder whether it may be possible to make it continuous with a dial rather than discrete with three pushbutton options. Some transceivers lack a separate B VFO tuning knob and this could be a way of adding that desirable feature in software.

+ The 4 buttons above Commander's "VFO B" or "Sub VFO" display provide a "quick split" capability; their purpose is not "general tunning".

+ To continuously tune VFO B, click on its least-significant digit, and rotate your mouse wheel.

73,

Dave, AA6YQ


Re: sent via and rcvd via in DXK

Dave AA6YQ
 

+ AA6YQ comments below

Hi Dave and everyone, I would like to add a "M" option (for "manager") to the "sent via" and "rcvd via" pull-downs in DXK. Is that something I can do myself or does it require Dave's help?

+ ADIF deprecated the use of 'M' in "Sent Via" and "Rcvd Via" fields because the involvement of a QSL Manager is independent of the means (bureau, direct, electronic) by which a QSL was requested and received:

<http://adif.org.uk/311/ADIF_311_annotated.htm#QSLVia_Enumeration>

+ To indicate that a QSL Manager is involved, place the QSL Manager's callsign in the QSO's "via" item.

73,

Dave, AA6YQ


Meteor scatter

Joe - W9RF
 

I have been working the recent meteor showers and have made a few contacts via MSK144, my question is do I need to enter the name of the meteor shower in the propagation box or is this for my consumption only?

The ones that have been confirmed did not populate the propagation box.


73,

W9RF - Joe


Re: Challenges with DXCC/Challenge submission using LOTW confirmations

Dave AA6YQ
 

Your report below is accurate, Björn:

1. LoTW's selection algorithm is suboptimal, submitting more confirmed QSOs than absolutely necessary. However, this is the result of poor programming, not a scheme to increase the collected submission fees.

2. The user must choose between employing DXKeeper's DXCC submission generator, which identifies the minimal set of QSOs to be selected, and then manually selecting each of those QSOs in LoTW, or submitting the QSOs chosen by LoTW, and then either manually setting "LoTW QSL Rcvd" to 'S' in each of those QSOs, or invoking a CTRL+"Sync LoTW QSLs" after the application has been processed and DXCC credit has been granted.

This is not a big deal for a handful of submitted QSOs, but for the DXer pursuing 5-band DXCC or DXCC Challenge and wanting to make an optimal submission of hundreds of new confirmations for DXCC credit, the task is tedious and unpleasant. Been there, done that.

The correct solution is for LoTW to provide an API that allows a logging application like DXKeeper to submit an ADIF file containing confirmed QSOs to be submitted for DXCC credit-- as can be done for QSL card confirmations using the ARRL's "DXCC Online", which DXKeeper directly supports:

<https://p1k.arrl.org/onlinedxcc/about.php>

Sadly, the ARRL's LoTW and DXCC systems are separate, and interoperate poorly. The DXCC system is ancient. In the fall of 2017, all LoTW development resources were re-assigned to work on upgrading the DXCC system after an attempt to outsource that upgrade failed; more than two years later, there is still no sign of an upgraded DXCC system, and LoTW's usability and functionality remain unimproved, other than Rick K1MU's continuing improvements to TQSL.

I have never been less optimistic about LoTW's future prospects than I am today. It's motto should be "grasping defeat from the jaws of victory".

73,

Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Björn SM7IUN
Sent: Monday, January 04, 2021 12:54 PM
To: DXLab Reflector
Subject: [DXLab] Challenges with DXCC/Challenge submission using LOTW confirmations

In the past I have simply used the "check all" option in the LOTW web page and then pressed "Sync LOTW QSL" while holding down Ctrl. An increasingly time consuming process, but simple.

This time I thought I should be a bit smarter and use the LOTW submission mechanics in DXKeeper. I selected "LOTW confirmation", pressed "Assemble submission" and then "Create LOTW Record sheet".

Doing this I found two anomalies.

The first is that the QSO are not listed in the same order. DXKeeper seems to do it from lower bands to higher. LOTW does something else.

This is not a big deal, but the second one is.

When comparing the QSO suggested by DXKeeper and the ones suggested by the "Application" page on the LOTW web server, I find that not the same QSO have been chosen to confirm the same bands and modes. In practice it does not make much difference if I confirm JX on 80m with a CW or FT8 QSO, but I don't feel good about marking the wrong QSO in DXKeeper with "V" (and for purely nostalgic reasons I always prefer using CW QSO to confirm a new band).

But what makes things worse is that LOTW seems to select more than necessary QSL (financial incentives?).

My QSO with JX2US, which is an entirely new DXCC entity for me, are:

JX2US 2020-10-13 20M CW
JX2US 2020-10-15 40M CW
JX2US 2020-10-16 20M FT8
JX2US 2020-10-20 30M FT8
JX2US 2020-10-28 30M CW
JX2US 2020-11-08 80M CW
JX2US 2020-11-10 40M FT8
JX2US 2020-11-12 60M FT8
JX2US 2020-11-23 80M FT8


Below you will find how DXKeeper and LOTW treats the challenge of selecting the fewest QSO that fulfils the DXCC criteria for CW, Digital and DXCC Challenge:

DXKeeper LOTW Record sheet:
...

JX2US 2020-11-08 80m CW
JX2US 2020-10-15 40m CW
JX2US 2020-10-20 30m FT8
JX2US 2020-10-13 20m CW
...
Comment: A minimum size selection of QSO. I still find it strange that the 30m FT8 QSO

was selected to confirm digital since the 20m FT8 QSO was at an earlier date. Perhaps it is because the search is done by band, going up.

LOTW:
...
JX2US 2020-10-16 20m FT8 for "20m"
JX2US 2020-10-28 30m CW for "30m"
JX2US 2020-10-15 40m CW for "40m"
JX2US 2020-11-08 80m CW for "80m"
JX2US 2020-10-20 30m FT8 for "Digital"
...
Comment: This seems to be by band, going down, but in other cases (e.g. my 80, 30, 17, and 15m QSO with D2EB) other orders are used. As you can see one of the 30m QSL is in this case redundant since both 30m and Digital are confirmed without it. This must clearly be a defect.

The bottom line is that with DXKeeper and the LOTW webpage using different selection algorithms, the "assemble submission" path is difficult to use since the QSOs proposed by DXKeeper are not available for selection on the application webpage.


Re: sent via and rcvd via in DXK

ND9G Mike
 

That would require a modification of DXKeeper by Dave.

There is a Via field for QSO, that you can add the manager's call to. This will be printed on the QSL if you use it. You then treat the sent/rcvd options like normal. Setting something to "M" for manager wouldn't tell you if you sent it to the manager direct, via the bureau, or OQRS. Using the fields separately is a better way to store the information.

73,
Mike ND9G


On Mon, Jan 4, 2021 at 2:11 PM devnull8it via groups.io <devnull8it=yahoo.com@groups.io> wrote:
Hi Dave and everyone, I would like to add a "M" option (for "manager") to the "sent via" and "rcvd via" pull-downs in DXK. Is that something I can do myself or does it require Dave's help? Thanks and 73, Mike W2IY


Re: Challenges with DXCC/Challenge submission using LOTW confirmations

Joe Subich, W4TV
 

The bottom line is that with DXKeeper and the LOTW webpage using different selection algorithms, the "assemble submission" path is
difficult to use since the QSOs proposed by DXKeeper are not
available for selection on the application webpage.
Selections are not made on the "application" webpage.

Start by selecting *CLEAR ALL* on the application page. The go to
"My QSOs" page, select your DXCC account, search for Confirmations
(QSLs) from each station (or for each country), place a check mark
beside those QSLs DXKeeper has selected and click "Submit DXCC Credit
Changes".

This process will populate the "Application" web page with (only) those
QSLs selected by DXKeeper.

BTW, LotW simply selects confirmations on a "first received" basis.

73,

... Joe, W4TV


On 2021-01-04 12:54 PM, Björn SM7IUN wrote:
In the past I have simply used the "check all" option in the LOTW web page and then pressed
"Sync LOTW QSL" while holding down Ctrl. An increasingly time consuming process, but simple.
This time I thought I should be a bit smarter and use the LOTW submission mechanics
in DXKeeper. I selected "LOTW confirmation",  pressed "Assemble submission" and
then "Create LOTW Record sheet".
Doing this I found two anomalies.
The first is that the QSO are not listed in the same order. DXKeeper seems to do
it from lower bands to higher. LOTW does something else.
This is not a big deal, but the second one is.
When comparing the QSO suggested by DXKeeper and the ones suggested by
the "Application" page on the LOTW web server, I find that not the same QSO have been
chosen to confirm the same bands and modes. In practice it does not make much difference if
I confirm JX on 80m with a CW or FT8 QSO, but I don't feel good about marking the wrong
QSO in DXKeeper with "V" (and for purely nostalgic reasons I always prefer using CW QSO to
confirm a new band).
But what makes things worse is that LOTW seems to select more than necessary QSL (financial incentives?).
My QSO with JX2US, which is an entirely new DXCC entity for me, are:
JX2US 2020-10-13 20M CW
JX2US 2020-10-15 40M CW
JX2US 2020-10-16 20M FT8
JX2US 2020-10-20 30M FT8
JX2US 2020-10-28 30M CW
JX2US 2020-11-08 80M CW
JX2US 2020-11-10 40M FT8
JX2US 2020-11-12 60M FT8
JX2US 2020-11-23 80M FT8
Below you will find how DXKeeper and LOTW treats the challenge of selecting the fewest QSO
that fulfils the DXCC criteria for CW, Digital and DXCC Challenge:
DXKeeper LOTW Record sheet:
...
JX2US 2020-11-08 80m CW
JX2US 2020-10-15 40m CW
JX2US 2020-10-20 30m FT8
JX2US 2020-10-13 20m CW
...
Comment: A minimum size selection of QSO. I still find it strange that the 30m FT8 QSO
was selected to confirm digital since the 20m FT8 QSO was at an earlier date. Perhaps
it is because the search is done by band, going up.
LOTW:
...
JX2US 2020-10-16 20m FT8 for "20m"
JX2US 2020-10-28 30m CW for "30m"
JX2US 2020-10-15 40m CW for "40m"
JX2US 2020-11-08 80m CW for "80m"
JX2US 2020-10-20 30m FT8 for "Digital"
...
Comment: This seems to be by band, going down, but in other cases (e.g. my 80, 30, 17, and
15m QSO with D2EB) other orders are used. As you can see one of the 30m QSL is in this case
redundant since both 30m and Digital are confirmed without it. This must clearly be a defect.
The bottom line is that with DXKeeper and the LOTW webpage using different selection
algorithms, the "assemble submission" path is difficult to use since the QSOs proposed
by DXKeeper are not available for selection on the application webpage.
Björn SM7IUN


B VFO tuning in Commander

devnull8it
 

Hello everyone, I like the B VFO offset in Commander, and wonder whether it may be possible to make it continuous with a dial rather than discrete with three pushbutton options. Some transceivers lack a separate B VFO tuning knob and this could be a way of adding that desirable feature in software. Thanks for any replies, 73, Mike W2IY


sent via and rcvd via in DXK

devnull8it
 

Hi Dave and everyone, I would like to add a "M" option (for "manager") to the "sent via" and "rcvd via" pull-downs in DXK. Is that something I can do myself or does it require Dave's help? Thanks and 73, Mike W2IY


Re: ADIf export

Dave AA6YQ
 

+ AA6YQ comments below

I am a hunter forr FF-references, SOTAs, Castle awards etc. I received an award WWFF-H-8544.

For BCA (Belgian Castles Award) i am Belgian number one in the Ranking. Very fine hobby!

All of the references from some activator, where always put togheter in the "Comment-box" of DXK.

+ The next version of ADIF will include a field for WWFF; when it's approved, I will add a WWFF item to DXKeeper, as I did for SOTA when it was added to ADIF.

+ Until then, you should configure one of DXKeeper's "user-defined items" to record WWFF tags. This Article shows how to do that, using POTA as an example:

https://www.dxlabsuite.com/dxlabwiki/UserAwardProgressreports


A time ago <GMA> came to birth. I thought the idea was not to bad. All the different sites where to get the different awards came as a fusion, mastered by 1 person, on one site: GMA. (Global Mountain activity)

To receive an award, one had to upload part of the log in ADIF. format.


I exported the selected part of my log in <Standard ADIF>. I noticed there are 6 different ADIFs available.

But as a IT-dummy, i don't know what's the difference between them.

+ Those alternatives are described at the beginning of

https://www.dxlabsuite.com/dxkeeper/Help/Export.htm

+ You should choose "Export standard ADIF",

73,

Dave, AA6YQ


Challenges with DXCC/Challenge submission using LOTW confirmations

Björn SM7IUN
 

In the past I have simply used the "check all" option in the LOTW web page and then pressed 
"Sync LOTW QSL" while holding down Ctrl. An increasingly time consuming process, but simple. 

This time I thought I should be a bit smarter and use the LOTW submission mechanics 
in DXKeeper. I selected "LOTW confirmation",  pressed "Assemble submission" and 
then "Create LOTW Record sheet".

Doing this I found two anomalies. 

The first is that the QSO are not listed in the same order. DXKeeper seems to do 
it from lower bands to higher. LOTW does something else.

This is not a big deal, but the second one is.

When comparing the QSO suggested by DXKeeper and the ones suggested by 
the "Application" page on the LOTW web server, I find that not the same QSO have been 
chosen to confirm the same bands and modes. In practice it does not make much difference if 
I confirm JX on 80m with a CW or FT8 QSO, but I don't feel good about marking the wrong 
QSO in DXKeeper with "V" (and for purely nostalgic reasons I always prefer using CW QSO to 
confirm a new band). 

But what makes things worse is that LOTW seems to select more than necessary QSL (financial incentives?). 

My QSO with JX2US, which is an entirely new DXCC entity for me, are:

JX2US 2020-10-13 20M CW
JX2US 2020-10-15 40M CW
JX2US 2020-10-16 20M FT8
JX2US 2020-10-20 30M FT8
JX2US 2020-10-28 30M CW
JX2US 2020-11-08 80M CW
JX2US 2020-11-10 40M FT8
JX2US 2020-11-12 60M FT8
JX2US 2020-11-23 80M FT8

Below you will find how DXKeeper and LOTW treats the challenge of selecting the fewest QSO 
that fulfils the DXCC criteria for CW, Digital and DXCC Challenge:

DXKeeper LOTW Record sheet:
...
JX2US 2020-11-08 80m CW
JX2US 2020-10-15 40m CW
JX2US 2020-10-20 30m FT8
JX2US 2020-10-13 20m CW
...
Comment: A minimum size selection of QSO. I still find it strange that the 30m FT8 QSO 
was selected to confirm digital since the 20m FT8 QSO was at an earlier date. Perhaps 
it is because the search is done by band, going up.

LOTW:
...
JX2US 2020-10-16 20m FT8 for "20m"
JX2US 2020-10-28 30m CW for "30m"
JX2US 2020-10-15 40m CW for "40m"
JX2US 2020-11-08 80m CW for "80m"
JX2US 2020-10-20 30m FT8 for "Digital"
...
Comment: This seems to be by band, going down, but in other cases (e.g. my 80, 30, 17, and 
15m QSO with D2EB) other orders are used. As you can see one of the 30m QSL is in this case 
redundant since both 30m and Digital are confirmed without it. This must clearly be a defect. 

The bottom line is that with DXKeeper and the LOTW webpage using different selection 
algorithms, the "assemble submission" path is difficult to use since the QSOs proposed 
by DXKeeper are not available for selection on the application webpage. 

Björn SM7IUN


ADIf export

eddy on5jk
 




-------- Doorgestuurd bericht --------
Onderwerp: ADIf export
Datum: Mon, 4 Jan 2021 17:42:29 +0100
Van: Eddy_on5jk <eddy_on5jk@...>
Aan: DXLab-forum <DXLab@groups.io>


Best wishes again Dave.

For so many years i've been very happy with (in my eyes) de most perfect logging program: DXLab.

I am a hunter forr FF-references, SOTAs, Castle awards etc. I received an award  WWFF-H-8544.

For BCA (Belgian Castles Award) i am Belgian number one in the Ranking. Very fine hobby!

All of the references from some activator, where always put togheter in the "Comment-box" of DXK.

Sometimes 6 different ones. So far so good, i collected a bunch of Awards, the way it used to be.

A time ago  <GMA> came to birth. I thought the idea was not to bad. All the different sites where to get the different awards came as a fusion, mastered by 1 person, on one site: GMA. (Global Mountain activity)

To receive an award, one had to upload part of the log in ADIF. format.

I exported the selected part of my log in <Standard ADIF>. I noticed there are 6 different ADIFs available.

But as a IT-dummy, i don't know what's the difference between them.

Greatest desilution!  All of the references "in the comment field" of DXK are not accepted by GMA.

Now i do not know what to do. Quiting GMA ?

Finaly i got a mail from the boss, that i had to install and learn ""ADIF MASTER"". Then i should replace, delete manualy, rename etc. As a dummy i don't see what he wants me to do. Anyway to complicated for me.

I will send you his final conclusion and instructions to AA6YQ at ambersoft. Hope you can clear it out for me and others

Thanks Dave and the Gang.

Eddy ON5JK


Re: Commander waterfall not 'connecting' when use of user defined command for powering on/off IC-7300

Dave AA6YQ
 

+ AA6YQ comments below

I'm obviously really lousy at finding and clicking on the correct links... I now realize the wiki was reachable as the "Getting started" link on the first page...
When I was reminded of the wiki I searched for the word "wiki" in the most obvious places to try to understand why I had missed it. I did not trigger on 'getting started' as the source for information of how to get more unusual tasks done and hence did not check that link.

I remember reading there about how to set up my IC-7300 from the beginning but then forgot about the link.

I hope my conversation above has not been taken as criticism or complaints, that has NOT been my intention.

+ Constructive criticism is always welcome here, and requires no sugar-coating or pre-apology.


My only intention was, and and has always been, to give feedback for possible improvements. In this case improvements in communions.
I decided long time ago to never again complain about anything without having a constructive suggestion or at least admit that I don't know how to improve things as I'm really tired of coworkers and other who only complain and wine but never do anything about it...

+ DXing is a complex problem domain, and DXLab aspires to provide maximum support for DXing. So there's a lot of functionality, some of which is novel with respect to the applications that most DXers already understand. The result is a significant learning curve, the traversal of which requires at least scanning the reference documentation in order to become aware of the available functionality. I'm always interested in smoothing out bumps in this learning curve, but I can't make it go away without compromising on DXLab's primary objective.

73,

Dave, AA6YQ


Re: Commander waterfall not 'connecting' when use of user defined command for powering on/off IC-7300

Björn (SM0SBL)
 

I'm obviously really lousy at finding and clicking on the correct links... I now realize the wiki was reachable as the "Getting started" link on the first page...
When I was reminded of the wiki I searched for the word "wiki" in the most obvious places to try to understand why I had missed it. I did not trigger on 'getting started' as the source for information of how to get more unusual tasks done and hence did not check that link.

I remember reading there about how to set up my IC-7300 from the beginning but then forgot about the link.

I hope my conversation above has not been taken as criticism or complaints, that has NOT been my intention. My only intention was, and and has always been, to give feedback for possible improvements. In this case improvements in communions.
I decided long time ago to never again complain about anything without having a constructive suggestion or at least admit that I don't know how to improve things as I'm really tired of coworkers and other who only complain and wine but never do anything about it... 

In the end, maybe it is ME who need most improvements when it comes to find the information I need :)

I will now back off and read the GettingStarted guide.

Once again; Thank you Dave for an excellent program suite for hams!!! I will NOT give up on DXLabs as it is fantastic!
--
Björn, SM0SBL


Re: Help

Dave AA6YQ
 

+ AA6YQ comments below

Two days away from submitting DX Marathon results....Dave, or others, today, when I went to keeper and realtime...went to generate a report (I was at Norm's W4QN's home for dinner and skpyed back to my computer), the realtime report had zero results tabulated for 2020 dx marathon. I was like there was no connection between keeper and Dx Marathon summary. Went back and tried to look at 2019 results and the same thing...just a bunch of goose eggs.....what am I missing? Help!

+ In the "Marathon Bands & Modes" panel on the Configuration window's Awards tab, what boxes are checked? What is specified in the "Max TX power" box?

73,

Dave, AA6YQ


Help

wc3w
 

Two days away from submitting DX Marathon results....Dave, or others, today, when I went to keeper and realtime...went to generate a report (I was at Norm's W4QN's home for dinner and skpyed back to my computer), the realtime report had zero results tabulated for 2020 dx marathon.  I was like there was no connection between keeper and Dx Marathon summary.  Went back and tried to look at 2019 results and the same thing...just a bunch of goose eggs.....what am I missing?  Help!
Mark
WC3W


Re: Problem between DXKeeper and WSJT-X

David Bunte
 

I'm sorry that I don't know the chap's call right off hand, but when I was chasing 5BWAS I got very excited when I worked a guy in 160 FT8 because JTAlert showed it as ND... which I needed. I messaged him with thanks and he explained that he was in MN at that time, and would be for quite a while. When he uploaded to Lotw the confirmation was for MN. So... whether this is the same station or not, it seems pretty clear that, for the reasons W4TV mentioned, that QSO counts as MN, not ND.

If you want to let me know the station callsign (direct to my email as in QRZ) I'll be glad to check my log to see if it was the same fellow.

Very 73 es Happier New Year to all,

Dave - K9FN

On Sun, Jan 3, 2021 at 5:10 PM Joe Subich, W4TV <lists@...> wrote:

> + However you choose to resolve such inconsistencies, if you're using
> JTAlert,  you should invoke its "Rebuild Alert Database" function
> after the completion of each "Sync LoTW QSLs" operation so that
> DXKeeper's and JTAlert's award tracking systems will be consistent.
In this case the discrepancy can occur because DXKeeper does not treat
the LotW confirmation as valid for WAS while JTAlert simply sees the
confirmation.

DXKeeper knows the confirmation is not valid for WAS (ND) since
"APP_DXKEEPER_LotW_Confirmation" does not contain "S" (state match).
JTAlert, on the other hand, does not take into account the contents
of "APP_DXKEEPER_LotW_Confirmation" so if you have logged *ANY* item
incorrectly (Grid/2/3/4, Submode, State, Zone), that data needs to be
corrected before JTAlert will scan/update correctly.

73,

    ... Joe, W4TV


On 2021-01-03 1:58 PM, Dave AA6YQ wrote:
> + AA6YQ comment below
>
> I hope I can clear up some of the conflict.  The contact I made in WSJT-X reported, via JTAert to DXKeeper, that I worked a ND station.  I then uploaded that contact in DXKeeper to LoTW.  The other station also uploaded his contact to LoTW, but as a MN location, not ND.  When I downloaded the contact information from LoTW to DXKeeper, I think I chose to keep the location as reported from JTAert.  Thus, JTAert shows a confirmed ND QSL.  LoTW shows a MN QSL!
>
> Here’s the problem.  The Awards tab of DXKeeper Log QSO’s shows the station was in ND.  The Realtime Award Tracking shows that for ND 17M I have ND worked but not confirmed and it points to this QSO.  The DXKeeper Log QSO's shows the station confirmed via LoTW as MN.  Looks to me as if DXKeeper sees 2 QSL’s for the same contact.
>
> I have emailed the person and am waiting for a reply.  Therein lies the more general problem!  Do you believe what is reported in the contact or what is reported in LoTW??
>
> + LoTW reports the location information specified by your QSO partner when he or she submitted your QSO. When you invoked DXKeeper's "Sync LoTW QSLs" function, it handles discrepancies between the information in a logged QSO and the information reported by LoTW as configured in the "Handling of LoTW QSL detail inconsistencies" panel on the "QSL Configuration" window's LoTW tab.
>
> + However you choose to resolve such inconsistencies, if you're using JTAlert,  you should invoke its "Rebuild Alert Database" function after the completion of each "Sync LoTW QSLs" operation so that DXKeeper's and JTAlert's award tracking systems will be consistent.
>
>         73,
>
>                   Dave, AA6YQ
>







Re: Problem between DXKeeper and WSJT-X

Joe Subich, W4TV
 

+ However you choose to resolve such inconsistencies, if you're using
JTAlert, you should invoke its "Rebuild Alert Database" function
after the completion of each "Sync LoTW QSLs" operation so that
DXKeeper's and JTAlert's award tracking systems will be consistent.
In this case the discrepancy can occur because DXKeeper does not treat
the LotW confirmation as valid for WAS while JTAlert simply sees the confirmation.

DXKeeper knows the confirmation is not valid for WAS (ND) since
"APP_DXKEEPER_LotW_Confirmation" does not contain "S" (state match).
JTAlert, on the other hand, does not take into account the contents
of "APP_DXKEEPER_LotW_Confirmation" so if you have logged *ANY* item
incorrectly (Grid/2/3/4, Submode, State, Zone), that data needs to be
corrected before JTAlert will scan/update correctly.

73,

... Joe, W4TV


On 2021-01-03 1:58 PM, Dave AA6YQ wrote:
+ AA6YQ comment below
I hope I can clear up some of the conflict. The contact I made in WSJT-X reported, via JTAert to DXKeeper, that I worked a ND station. I then uploaded that contact in DXKeeper to LoTW. The other station also uploaded his contact to LoTW, but as a MN location, not ND. When I downloaded the contact information from LoTW to DXKeeper, I think I chose to keep the location as reported from JTAert. Thus, JTAert shows a confirmed ND QSL. LoTW shows a MN QSL!
Here’s the problem. The Awards tab of DXKeeper Log QSO’s shows the station was in ND. The Realtime Award Tracking shows that for ND 17M I have ND worked but not confirmed and it points to this QSO. The DXKeeper Log QSO's shows the station confirmed via LoTW as MN. Looks to me as if DXKeeper sees 2 QSL’s for the same contact.
I have emailed the person and am waiting for a reply. Therein lies the more general problem! Do you believe what is reported in the contact or what is reported in LoTW??
+ LoTW reports the location information specified by your QSO partner when he or she submitted your QSO. When you invoked DXKeeper's "Sync LoTW QSLs" function, it handles discrepancies between the information in a logged QSO and the information reported by LoTW as configured in the "Handling of LoTW QSL detail inconsistencies" panel on the "QSL Configuration" window's LoTW tab.
+ However you choose to resolve such inconsistencies, if you're using JTAlert, you should invoke its "Rebuild Alert Database" function after the completion of each "Sync LoTW QSLs" operation so that DXKeeper's and JTAlert's award tracking systems will be consistent.
73,
Dave, AA6YQ

7241 - 7260 of 205931