开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

LoTW Application query


 

Hi Dave and the group,

?

Last week, I made an LoTW application (88 slots), but since then, I have had some new slots confirmed via LoTW.

Because I have an application pending, I am unable to add these via LoTW, and also, I can't set these to "S" in the LoTW rcvd box, as when my application is granted, those with the S set since would be changed to V when I verify the current submission.

?

Is there a way within DXKeeper to handle this? I currently just have a "Sticky Notes" on screen with notes about these QSO's.

?

73 de Phil GU0SUP


 

Hi Phil,
The newly confirmed QSOs should be left set to 'C' until you generate a new submission. Just because they were confirmed while you have an application pending, the new QSOs will not be processed in addition to the original 88. I'm guessing you assumed they would be added and that is why you want to set them to 'S'? So, no sticky note needed, DXK will handle the new confirmations as part of your next submission.

73, Chuck KM3V


 

Hi Chuck,

?

Thanks for the answer, but there isn't an option to set the LoTW recvd to 'C'. I only have R, Y, S, V, I or X to choose from, so they are currently set at Y.

?

73 de Phil GU0SUP

?

?

-----Original Message-----
From: "Chuck, KM3V via groups.io" <chuck.hartley@...>
Sent: Monday, 24 March, 2025 15:50
To: [email protected]
Subject: Re: [DXLab] LoTW Application query

Hi Phil,
The newly confirmed QSOs should be left set to 'C' until you generate a new submission. Just because they were confirmed while you have an application pending, the new QSOs will not be processed in addition to the original 88. I'm guessing you assumed they would be added and that is why you want to set them to 'S'? So, no sticky note needed, DXK will handle the new confirmations as part of your next submission.

73, Chuck KM3V






 

Thanks for the answer, but there isn't an option to set the LoTW recvd to 'C'. I only have R, Y, S, V, I or X to choose from, so they
are currently set at Y.
Which, at present, is the correct answer for - both LotW and Card -
confirmations received while an application is pending (about two
months these days). Then one must use the DXKeeper submission
generator to find those "new" confirmations in the future.

It would be handy if ADIF/Dave were to defined a 'P' (pending) status
for those of us who prefer to manually prepare submissions as the
confirmations arrive.

73,

... Joe, W4TV

On 2025-03-24 12:24 PM, Phil Cooper via groups.io wrote:
Hi Chuck,
Thanks for the answer, but there isn't an option to set the LoTW recvd to 'C'. I only have R, Y, S, V, I or X to choose from, so they are currently set at Y.
73 de Phil GU0SUP
-----Original Message-----
From: "Chuck, KM3V via groups.io" <chuck.hartley@...>
Sent: Monday, 24 March, 2025 15:50
To: [email protected]
Subject: Re: [DXLab] LoTW Application query
Hi Phil,
The newly confirmed QSOs should be left set to 'C' until you generate a new submission. Just because they were confirmed while you have an application pending, the new QSOs will not be processed in addition to the original 88. I'm guessing you assumed they would be added and that is why you want to set them to 'S'? So, no sticky note needed, DXK will handle the new confirmations as part of your next submission.
73, Chuck KM3V


 

Hi Phil,
Yes, you are correct. It should be 'Y' in the LOTW status box. I was thinking of the DXCC progress display, where that entity would show as confirmed using the 'C'. So the new QSOs should show a LOTW received status of 'Y', which is set automatically when you update your QSL status from LOTW. When you use DXK to assemble your next submission, the confirmed QSOs you you select will have their LOTW status set to 'S' - you don't have to do it manually.

73, Chuck KM3V


 

+ AA6YQ comments below
It would be handy if ADIF/Dave were to defined a 'P' (pending) status
for those of us who prefer to manually prepare submissions as the
confirmations arrive.
+ You can setup a user-defined item named "Pending" and use whatever codes you like to represent the states of your manually-managed award submissions.

? ? ?73,

? ? ? ? ? ? ?Dave, AA6YQ


 

How does one set up a user defined code within QSL_RCVD and
APP_DXKEEPER_LotW_QSL_RCVD that is treated as 'Y' for filling
the Progress (RAT) Tables?

A separate database field is overkill for this application.

73,

... Joe, W4TV

On 2025-03-24 1:54 PM, Dave AA6YQ wrote:
+ AA6YQ comments below


It would be handy if ADIF/Dave were to defined a 'P' (pending) status
for those of us who prefer to manually prepare submissions as the
confirmations arrive.
+ You can setup a user-defined item named "Pending" and use whatever codes you like to represent the states of your manually-managed award submissions.
73,
Dave, AA6YQ


 

+ AA6YQ comments below
How does one set up a user defined code within QSL_RCVD and
APP_DXKEEPER_LotW_QSL_RCVD that is treated as 'Y' for filling
the Progress (RAT) Tables?
+ I didn't suggest setting up user-defined codes for QSL_RCVD and LotW_QSL_RCVD because that's not supported. Providing a practical means by which a user could specify how every aspect of DXLab's Realtime Award Tracking for 7 award families should respond to each new user-defined code for QSL_RCVD and LotW_QSL_RCVD is not technically feasible, at least for this developer.?
A separate database field is overkill for this application.
+ The separate database fields that support user-defined items are already in place; their use with single-character codes would not result in any significant additional overhead.?

? ? ? ?73,

? ? ? ? ? ? ? Dave, AA6YQ


 

开云体育

Hi Dave,

On 3/24/25 12:54, Dave AA6YQ wrote:
+ AA6YQ comments below
It would be handy if ADIF/Dave were to defined a 'P' (pending) status
for those of us who prefer to manually prepare submissions as the
confirmations arrive.
+ You can setup a user-defined item named "Pending" and use whatever codes you like to represent the states of your manually-managed award submissions.


Using these instructions??


73

Stan
KM4HQE


 

# AA6YQ comments below

It would be handy if ADIF/Dave were to defined a 'P' (pending) status
for those of us who prefer to manually prepare submissions as the
confirmations arrive.

# You can setup a user-defined item named "Pending" and use whatever codes you like to represent the states of your manually-managed award submissions.

Using these instructions?

# No. This has nothing to do with user-defined award progress reports.

# Here's the scenario:

1. You've used DXKeeper to generate a DXCC award application, so you have QSOs whose "QSL Rcvd" and "LoTW QSL Rcvd" items are set to 'S' ( for "submitted").

2. You're waiting for the ARRL's DXCC desk to process that application which can take months. When they notify you that your submitted QSOs have been granted DXCC Award Credit, you'd direct DXKeeper to "Verify" your submission to reflect the granting of DXCC award credit by change each 'S' in a "QSL Rcvd" and "LoTW QSL Rcvd" item to 'V'.

3. However, before you receive notice that your application has been processed, several more confirmations for previously unconfirmed DXCC entities, entity-bands, or entity-modes arrive. Instead of waiting until the DXCC desk finishes processing the application you've already submitted to complete step 2 and then direct DXKeeper to generate a new submission, the request to make it possible to manually generate a second application that includes then new LoTW confirmation. This can be done by defining a user-defined item called "Pending", and setting it to 'C' in each of those QSOs newly confirmed by QSL card, and to 'L' in each of those QSOs newly confirmed by LoTW.

4. At that point, you would

4a. make a copy of your log file

4b. direct DXKeeper to "Verify" the current submission

4c. direct DXKeeper to generate a new DXCC submission, which would automatically include those new confirmations (the ones their Pending items set to 'C' and 'L') and produce the documents needed to submit a second application

4d. revert to the Log file created in step 4a

4e. when you receive notice that your first DXCC application has been processed, you would direct DXKeeper to Verify it, changing each 'S' in a "QSL Rcvd" and "LoTW QSL Rcvd" item to 'V'

4f. then you would

4.f.1 filter the Log Page Display to contain all QSOs whose Pending item is set to 'C' and use the "Modify QSOs" function to set their "QSL Rcvd" items to 'S' and clear their Pending items

4.f.2 filter the Log Page Display to contain all QSOs whose Pending item is set to 'L' and use the "Modify QSOs" function to set their "LoTW QSL Rcvd" items to 'S' and clear their Pending items

5. when your receive notice that your second DXCC application has been processed, , you would direct DXKeeper to Verify it, changing each 'S' in a "QSL Rcvd" and "LoTW QSL Rcvd" item to 'V'

Thus you will have worked around the limitation in DXKeeper's automation of DXCC award applications that only one submission can be outstanding at a time.

73,

Dave, AA6YQ


 

Hi Dave,

On 3/24/25 21:52, Dave AA6YQ wrote:
# AA6YQ comments below

It would be handy if ADIF/Dave were to defined a 'P' (pending) status
for those of us who prefer to manually prepare submissions as the
confirmations arrive.

# You can setup a user-defined item named "Pending" and use whatever codes you like to represent the states of your manually-managed award submissions.

Using these instructions?

# No. This has nothing to do with user-defined award progress reports.

# Here's the scenario:

1. You've used DXKeeper to generate a DXCC award application, so you have QSOs whose "QSL Rcvd" and "LoTW QSL Rcvd" items are set to 'S' ( for "submitted").

2. You're waiting for the ARRL's DXCC desk to process that application which can take months. When they notify you that your submitted QSOs have been granted DXCC Award Credit, you'd direct DXKeeper to "Verify" your submission to reflect the granting of DXCC award credit by change each 'S' in a "QSL Rcvd" and "LoTW QSL Rcvd" item to 'V'.

3. However, before you receive notice that your application has been processed, several more confirmations for previously unconfirmed DXCC entities, entity-bands, or entity-modes arrive. Instead of waiting until the DXCC desk finishes processing the application you've already submitted to complete step 2 and then direct DXKeeper to generate a new submission, the request to make it possible to manually generate a second application that includes then new LoTW confirmation. This can be done by defining a user-defined item called "Pending", and setting it to 'C' in each of those QSOs newly confirmed by QSL card, and to 'L' in each of those QSOs newly confirmed by LoTW.

4. At that point, you would

4a. make a copy of your log file

4b. direct DXKeeper to "Verify" the current submission

4c. direct DXKeeper to generate a new DXCC submission, which would automatically include those new confirmations (the ones their Pending items set to 'C' and 'L') and produce the documents needed to submit a second application

4d. revert to the Log file created in step 4a

4e. when you receive notice that your first DXCC application has been processed, you would direct DXKeeper to Verify it, changing each 'S' in a "QSL Rcvd" and "LoTW QSL Rcvd" item to 'V'

4f. then you would

4.f.1 filter the Log Page Display to contain all QSOs whose Pending item is set to 'C' and use the "Modify QSOs" function to set their "QSL Rcvd" items to 'S' and clear their Pending items

4.f.2 filter the Log Page Display to contain all QSOs whose Pending item is set to 'L' and use the "Modify QSOs" function to set their "LoTW QSL Rcvd" items to 'S' and clear their Pending items

5. when your receive notice that your second DXCC application has been processed, , you would direct DXKeeper to Verify it, changing each 'S' in a "QSL Rcvd" and "LoTW QSL Rcvd" item to 'V'

Thus you will have worked around the limitation in DXKeeper's automation of DXCC award applications that only one submission can be outstanding at a time.
Thanks for the detailed explanation.? Having to do all that makes my
head hurt.? I'll pass and stay with the way I've been doing it.


73

Stan
KM4HQE


 

+ AA6YQ comments below
Thanks for the detailed explanation.? Having to do all that makes my
head hurt.? I'll pass and stay with the way I've been doing it.
+ Understood. It's only appropriate if you don't want to wait for one DXCC award application to be processed by the ARRL's DXCC desk before generating the next one.

? ? ?73,

? ? ? ? ? Dave, AA6YQ


 

Hi to Dave and Stan,

?

Like Stan, that process is OK, but I think I will stick to my "Sticky Notes" on screen, where I keep a list of new ones worked until they are confirmed.

For the (now) two new ones that have confirmed since my LoTW application, I have marked them as "rcvd" and made them bold and in Italics.

?

Now I will just wait until my application is processed, and I will know which ones I need to check in the awards application.

?

73 de Phil GU0SUP

?

?

-----Original Message-----
From: "Stan Gammons via groups.io" <buttercup11421@...>
Sent: Tuesday, 25 March, 2025 03:06
To: [email protected]
Subject: Re: [DXLab] LoTW Application query

Hi Dave,

On 3/24/25 21:52, Dave AA6YQ wrote:
> # AA6YQ comments below
>
> It would be handy if ADIF/Dave were to defined a 'P' (pending) status
> for those of us who prefer to manually prepare submissions as the
> confirmations arrive.
>
> # You can setup a user-defined item named "Pending" and use whatever codes you like to represent the states of your manually-managed award submissions.
>
> Using these instructions? https://dxlabsuite.com/dxlabwiki/UserAwardProgressreports
>
> # No. This has nothing to do with user-defined award progress reports.
>
> # Here's the scenario:
>
> 1. You've used DXKeeper to generate a DXCC award application, so you have QSOs whose "QSL Rcvd" and "LoTW QSL Rcvd" items are set to 'S' ( for "submitted").
>
> 2. You're waiting for the ARRL's DXCC desk to process that application which can take months. When they notify you that your submitted QSOs have been granted DXCC Award Credit, you'd direct DXKeeper to "Verify" your submission to reflect the granting of DXCC award credit by change each 'S' in a "QSL Rcvd" and "LoTW QSL Rcvd" item to 'V'.
>
> 3. However, before you receive notice that your application has been processed, several more confirmations for previously unconfirmed DXCC entities, entity-bands, or entity-modes arrive. Instead of waiting until the DXCC desk finishes processing the application you've already submitted to complete step 2 and then direct DXKeeper to generate a new submission, the request to make it possible to manually generate a second application that includes then new LoTW confirmation. This can be done by defining a user-defined item called "Pending", and setting it to 'C' in each of those QSOs newly confirmed by QSL card, and to 'L' in each of those QSOs newly confirmed by LoTW.
>
> 4. At that point, you would
>
> 4a. make a copy of your log file
>
> 4b. direct DXKeeper to "Verify" the current submission
>
> 4c. direct DXKeeper to generate a new DXCC submission, which would automatically include those new confirmations (the ones their Pending items set to 'C' and 'L') and produce the documents needed to submit a second application
>
> 4d. revert to the Log file created in step 4a
>
> 4e. when you receive notice that your first DXCC application has been processed, you would direct DXKeeper to Verify it, changing each 'S' in a "QSL Rcvd" and "LoTW QSL Rcvd" item to 'V'
>
> 4f. then you would
>
> 4.f.1 filter the Log Page Display to contain all QSOs whose Pending item is set to 'C' and use the "Modify QSOs" function to set their "QSL Rcvd" items to 'S' and clear their Pending items
>
> 4.f.2 filter the Log Page Display to contain all QSOs whose Pending item is set to 'L' and use the "Modify QSOs" function to set their "LoTW QSL Rcvd" items to 'S' and clear their Pending items
>
> 5. when your receive notice that your second DXCC application has been processed, , you would direct DXKeeper to Verify it, changing each 'S' in a "QSL Rcvd" and "LoTW QSL Rcvd" item to 'V'
>
> Thus you will have worked around the limitation in DXKeeper's automation of DXCC award applications that only one submission can be outstanding at a time.

Thanks for the detailed explanation.? Having to do all that makes my
head hurt.? I'll pass and stay with the way I've been doing it.


73

Stan
KM4HQE