Date   
Re: LOTW upload aborted

Bill Stravinsky
 

To me its eenee meenee.  I still have to click things.  It is no big deal to do my uploading using the Select setting to do that in the QSL panel.  Since I do 99% contesting
I use n1mm to do that then just import the adif's and they get the Y status.  Using the add requested to load the queue or using the SEL to filter the log  and load the queue
gets me to the same place.  And I do the QSL requested for labels at other times and wait until I receive cards from the bureau which takes time.  I need those 2 status marks
to be separate as one is for all contacts and the other is when I get enough cards to send to ARRL.

DxLab is versatile so more than one way to accomplish the same thing.  But thanks for pointing out another road to get to the same destination.

Bill

On Wednesday, September 11, 2019, 11:00:08 PM EDT, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below

Its not just for Lotw.  I also upload to EQsl and ClubLog so every contact I either work casually or import from n1mm I have set to "Set select in imported QSO to Y".
I have to manually set select to Y but the majority of my operating is contesting so it gets set automatically when I import.  Then when I have several hundred Q's ready to upload to those 3 sources I just hit Sel to filter the log for all the Y's and do all the uploading.

+ Carl WC4H is right, Bill. After importing an ADIF file, you can

1. On the Main window's QSL tab,

1a. set the "QSL Via" panel to LoTW

1b. click the "Add Requested" button

1c. click the "Upload to LoTW" button

1d. set the "QSL Via" panel to eQSL.cc

1e. click the "Add Requested" button

1f. click the "Upload to eQSL.cc" button

2. On the Main window's "Check Progress" tab, click the "Club Log" panel's Upload button

+ The above procedure will upload your new QSOs to LoTW, eQSL, and Club Log.

+ Note that you can configure DXKeeper to automatically upload each newly-logged QSO to LoTW, eQSL, and Club Log.


Also, I use the QSL status setting to R to mark Q's to make QSL labels so your idea wouldn't work in my case.

+ The above procedure in no way interferes with DXKeeper's ability to print QSL labels.

        73,

                  Dave, AA6YQ



Re: LOTW upload aborted

Dave AA6YQ
 

+ AA6YQ comments below

Its not just for Lotw. I also upload to EQsl and ClubLog so every contact I either work casually or import from n1mm I have set to "Set select in imported QSO to Y".
I have to manually set select to Y but the majority of my operating is contesting so it gets set automatically when I import. Then when I have several hundred Q's ready to upload to those 3 sources I just hit Sel to filter the log for all the Y's and do all the uploading.

+ Carl WC4H is right, Bill. After importing an ADIF file, you can

1. On the Main window's QSL tab,

1a. set the "QSL Via" panel to LoTW

1b. click the "Add Requested" button

1c. click the "Upload to LoTW" button

1d. set the "QSL Via" panel to eQSL.cc

1e. click the "Add Requested" button

1f. click the "Upload to eQSL.cc" button

2. On the Main window's "Check Progress" tab, click the "Club Log" panel's Upload button

+ The above procedure will upload your new QSOs to LoTW, eQSL, and Club Log.

+ Note that you can configure DXKeeper to automatically upload each newly-logged QSO to LoTW, eQSL, and Club Log.


Also, I use the QSL status setting to R to mark Q's to make QSL labels so your idea wouldn't work in my case.

+ The above procedure in no way interferes with DXKeeper's ability to print QSL labels.

73,

Dave, AA6YQ

Re: LOTW upload aborted

Bill Stravinsky
 

Its not just for Lotw.  I also upload to EQsl and ClubLog so every contact I either work casually or import from n1mm I have set to "Set select in imported QSO to Y".
I have to manually set select to Y but the majority of my operating is contesting so it gets set automatically when I import.  Then when I have several hundred Q's
ready to upload to those 3 sources I just hit Sel to filter the log for all the Y's and do all the uploading.

Also, I use the QSL status setting to R to mark Q's to make QSL labels so your idea wouldn't work in my case.  Thanks for the suggestion.

Bill
K3WJV

On Wednesday, September 11, 2019, 6:19:34 PM EDT, Carl - WC4H via Groups.Io <wc4h.dx@...> wrote:


It sounds like you want to do manually stuff that DXKeeper can do for you.

You can set the parameter for LoTW QSL status:
Default it to R when QSO is entered.
Then, in the QSL tab, select LoTW in the QSL via panel and click on the "add requested" button.
Then click on the "Upload to LoTW" button.  This will change the LoTW status from R to U.

Sometime later (it's prudent to wait an hour or two) click on the "Sync LoTW QSOs".  This will Change the LoTW status from U to Y for those that have been processed.

Then click on the Sync LoTW QSLs button to see what has been confirmed.

73.
Carl - WC4H

Re: LOTW upload aborted

Carl - WC4H
 

It sounds like you want to do manually stuff that DXKeeper can do for you.

You can set the parameter for LoTW QSL status:
Default it to R when QSO is entered.
Then, in the QSL tab, select LoTW in the QSL via panel and click on the "add requested" button.
Then click on the "Upload to LoTW" button.  This will change the LoTW status from R to U.

Sometime later (it's prudent to wait an hour or two) click on the "Sync LoTW QSOs".  This will Change the LoTW status from U to Y for those that have been processed.

Then click on the Sync LoTW QSLs button to see what has been confirmed.

73.
Carl - WC4H

Re: RAT (DXKeeper)

Dave AA6YQ
 

+ AA6YQ comments below

I have noticed that the real time award tracking in DXKeeper, doesn't take into account LoTW confirmations for the IOTA score

+ Correct. LoTW confirmations have never counted towards IOTA awards.

while the IOTA program can now load Club Log matched contacts which can be synchronized with LoTW.

+The fact that QSOs can be submitted from Club Log to LoTW does not make LoTW confirmations valid for awards like IOTA that accept
Club Log matches.

+ If you cite a statement on an official IOTA web page indicating that LoTW confirmations count for IOTA, I will update DXKeeper
accordingly.

73,

Dave, AA6YQ

Re: LOTW upload aborted

Bill Stravinsky
 

Dave

First off thanks for the fast responses to all questions on here.  As it turned out the answer to the problem was staring back at me but I didn't notice it right away.
When I had the 1280 contacts loaded into the Lotw queue I happened to scroll to the beginning of the list a few times and all of a sudden it jumped right out. The contacts
I was trying to upload started on Sept 4th and the first 2 contacts were dated Aug 27th.  Apparently when I did a CTRL click on SEL the last time I did my uploading
to change all the Y's to N's it somehow left 2 stragglers with Y's which of course were already uploaded.

So now I make it a habit to hit SEL after changing the Y's to see if any didn't get switched.

By the way, I always try to learn stuff on my own and after you answered me this morning after my 2nd set of questions I played around trying to find a work around
to have another way of identifying a group of Q's other than the Select Y for future reference.  I came up with an SQL to show a U in the Temp box in Auxiliary.  That is how
I was going to try your 2nd fix but luckily found the error.

Thanks again.

Bill
K3WJV

On Wednesday, September 11, 2019, 12:03:02 PM EDT, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below


1. After performing this procedure and it changes the Select status to reflect just the duplicates, will my original 1280 contacts revert back to Y with the rest of the log being N like it was?

+ No.

After the procedure if I click the SEL button will it filter the log again to show just those 1280 contacts being marked Y like they were before step 3?

+ No.


2. Can I just work with the 1280 contacts that are marked Y since that apparently is where the problem is with the duplicates or do I just perform step 3 with no select status (clicking X to reset the filter and doing this procedure for over 100K contacts.  This warning didn't happen until I tried to upload these 1280 contacts. The warning from Lotw says 2 of 1280 contacts are duplicates.

+ The error message from TQSL means 2 of the QSOs your trying to submit have already been submitted before.

+ The duplicate checker checks your entire log for duplicates; there is no way to check for duplicate QSOs within a subset of your log.


+ Try this procedure with the 1280 QSOs having their Select items set to 'Y':

1. Terminate DXKeeper

2. Make a copy of your log file

3. Start DXKeeper

4. Direct DXKeeper to load the new copy of your log file.

5. Delete all QSOs whose Select items are not set to 'Y'.

6. Invoke the duplicate checking function to locate the duplicate QSO, and jot down their call/date/time/band/mode

7. Direct DXKeeper to load your original log file

8. Manually delete the duplicate QSOs found in step 6

        73,

                Dave, AA6YQ



RAT (DXKeeper)

Salvatore Besso
 

hello,

I have noticed that the real time award tracking in DXKeeper, doesn't
take into account LoTW confirmations for the IOTA score while the IOTA
program can now load Club Log matched contacts which can be synchronized
with LoTW.

Is it a not feasible thing that RAT could now take into account LoTW
confirmations for IOTA or is me that I'm doing something wrong?

73 de
Salvatore (I4FYV)

Re: PC broken

Dave AA6YQ
 

+ AA6YQ comments below

the problem remained, no difference with version 15.0.8. The external window can be modified, but the internal window has been cut as before and cannot be modified in size.

+ Please do the following:

1. on the General tab of DXKeeper's Configuration window, check the "Log debugging info" box

2. terminate DXKeeper

3. start DXKeeper

4. wait until the Main window is on-screen

5. on the General tab of DXKeeper's Configuration window, uncheck the "Log debugging info" box

6. attach the errorlog.txt file from your DXKeeper folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

Re: PC broken

ik0rcy@...
 

Hi Dave,

the problem remained, no difference with version 15.0.8. The external window can be modified, but the internal window has been cut as before and cannot be modified in size.

73 de Raoul, ik0rcy

Re: Difficult query

Dave AA6YQ
 

+ AA6YQ comments below

browsing the link that you supplied, I've found this:

https://clublog.freshdesk.com/support/solutions/articles/96841-checking-logs-for-the-existence-of-a-qso

and this:

https://clublog.freshdesk.com/support/solutions/articles/175988-checking-for-log-matches

They could or could not be useful, but I want to put them to your attention.

+ 175988-checking-for-log-matches describes the needed API, thanks. I've added support for this to DXKeeper's enhancement list.

73,

Dave, AA6YQ

Re: PC broken

Dave AA6YQ
 

+ AA6YQ comments below

Too simple: the window is locked, it is not possible to enlarge it.

+ Evidently, the DXKeeper settings stored in the Windows Registry specify a "my QTH" tab size that is larger than your current monitor.

+ I have extended the next version of DXKeeper to detect and correct this situation, and sent you this new version. Please let me know how it goes...

73,

Dave, AA6YQ

Re: LOTW upload aborted

Dave AA6YQ
 

+ AA6YQ comments below


1. After performing this procedure and it changes the Select status to reflect just the duplicates, will my original 1280 contacts revert back to Y with the rest of the log being N like it was?

+ No.

After the procedure if I click the SEL button will it filter the log again to show just those 1280 contacts being marked Y like they were before step 3?

+ No.


2. Can I just work with the 1280 contacts that are marked Y since that apparently is where the problem is with the duplicates or do I just perform step 3 with no select status (clicking X to reset the filter and doing this procedure for over 100K contacts. This warning didn't happen until I tried to upload these 1280 contacts. The warning from Lotw says 2 of 1280 contacts are duplicates.

+ The error message from TQSL means 2 of the QSOs your trying to submit have already been submitted before.

+ The duplicate checker checks your entire log for duplicates; there is no way to check for duplicate QSOs within a subset of your log.


+ Try this procedure with the 1280 QSOs having their Select items set to 'Y':

1. Terminate DXKeeper

2. Make a copy of your log file

3. Start DXKeeper

4. Direct DXKeeper to load the new copy of your log file.

5. Delete all QSOs whose Select items are not set to 'Y'.

6. Invoke the duplicate checking function to locate the duplicate QSO, and jot down their call/date/time/band/mode

7. Direct DXKeeper to load your original log file

8. Manually delete the duplicate QSOs found in step 6

73,

Dave, AA6YQ

Re: LOTW upload aborted

Bill Stravinsky
 

step 3 of that procedure:

in the Advanced Filters, Sorts, and Modifiers window's Duplicates panel, click the Filter button; since this operation will clear the Select item in every logged QSO and then set the Select item to Y in each duplicate QSO, you will be prompted to confirm that you wish to proceed.

I'm not trying to repeat anything but if you read my question it mentions that I have the last 1280 contacts Select status set to Y. Here are my questions:

1. After performing this procedure and it changes the Select status to reflect just the duplicates, will my original 1280 contacts revert back to Y with the rest of the log being N like it was?
After the procedure if I click the SEL button will it filter the log again to show just those 1280 contacts being marked Y like they were before step 3? so I can upload with the Y filter

2. Can I just work with the 1280 contacts that are marked Y since that apparently is where the problem is with the duplicates or do I just perform step 3 with no select status (clicking X to reset the filter
and doing this procedure for over 100K contacts.  This warning didn't happen until I tried to upload these 1280 contacts. The warning from Lotw says 2 of 1280 contacts are duplicates.


Bill
K3WJV


On Wednesday, September 11, 2019, 2:11:03 AM EDT, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below


I just imported logs from n1mm to Dxlab and am trying to upload to Lotw.  When I do this procedure I have Select equal to Y so I know what contacts to upload then after I'm finished with Lotw, EQsl and ClubLog uploads I set the Select to N and wait for more contest logs to do the same procedure.  The upload to Lotw is being aborted and the report says because
2 of 1280 records are duplicates.  How can I find these 2 duplicates to figure out what I have to do with them so I can get these records uploaded and finish my procedure?


+ In TQSL terminology, a "duplicate QSO" is one that's already been submitted to LoTW.

+ If your log contains more than one copy of the same QSO - an actual duplicate QSO - attempting to submit both copies to LoTW will trigger the above error message from TQSL.

+ To determine whether you have duplicate QSOs in your log, see

<https://www.dxlabsuite.com/dxlabwiki/RemovingDuplicates>

      73,

            Dave, AA6YQ



Re: PC broken

ik0rcy@...
 

Too simple: the window is locked, it is not possible to enlarge it.

Re: Difficult query

Salvatore Besso
 

hello again Dave,

browsing the link that you supplied, I've found this:

https://clublog.freshdesk.com/support/solutions/articles/96841-checking-logs-for-the-existence-of-a-qso

and this:

https://clublog.freshdesk.com/support/solutions/articles/175988-checking-for-log-matches

They could or could not be useful, but I want to put them to your attention.

73 de
Salvatore (I4FYV)

Re: Difficult query

Salvatore Besso
 

ok, thank you. So for now it's impossible.

73 de
Salvatore (I4FYV)

Re: LOTW upload aborted

Dave AA6YQ
 

+ AA6YQ comments below

I just imported logs from n1mm to Dxlab and am trying to upload to Lotw. When I do this procedure I have Select equal to Y so I know what contacts to upload then after I'm finished with Lotw, EQsl and ClubLog uploads I set the Select to N and wait for more contest logs to do the same procedure. The upload to Lotw is being aborted and the report says because
2 of 1280 records are duplicates. How can I find these 2 duplicates to figure out what I have to do with them so I can get these records uploaded and finish my procedure?

+ In TQSL terminology, a "duplicate QSO" is one that's already been submitted to LoTW.

+ If your log contains more than one copy of the same QSO - an actual duplicate QSO - attempting to submit both copies to LoTW will trigger the above error message from TQSL.

+ To determine whether you have duplicate QSOs in your log, see

<https://www.dxlabsuite.com/dxlabwiki/RemovingDuplicates>

73,

Dave, AA6YQ

LOTW upload aborted

Bill Stravinsky
 

I just imported logs from n1mm to Dxlab and am trying to upload to Lotw.  When I do this procedure I have Select equal to Y so I know what contacts to upload then after I'm finished
with Lotw, EQsl and ClubLog uploads I set the Select to N and wait for more contest logs to do the same procedure.  The upload to Lotw is being aborted and the report says because
2 of 1280 records are duplicates.  How can I find these 2 duplicates to figure out what I have to do with them so I can get these records uploaded and finish my procedure?

I always do this procedure in the same order so Lotw is first then I do EQsl and then ClubLog.  I don't know what EQsl & ClubLog will do with these duplicates but I need to resolve this.
The notepad report that comes up with the Lotw result says "Final Status: No QSOs written (8)" whatever that means.  I am assuming that is the code for duplicates or the reason for the abort.

I need help, hi.

Bill
K3WJV

Re: Slow Program Response Followup

Dave AA6YQ
 

+ AA6YQ comments below


Congrats on your performance upgrade. Got a similar success story, that others may want to consider.

Because of wicked slow response times + some bizarre stuff from corrupted files, I did a Re-Install of Windows 10.......after first doing a thorough back-up of my personal files + the DXkeeper log, etc.

After the new Windows 10 was loaded, I re-installed all my apps. + my personal files & the DXlab apps. + my DXkeeper log.

Then I did a thorough review & update of all the Drivers. (It's a l-o-n-g list). Many Drivers were out-of-date.

These actions have caused a boisterous W o w ! My PC is perky & nimble again ! Not slow & sluggish anymore.
The Look-up of a call, using DXcapture & DXkeeper, is much faster now. Done in < 2 sec. today... compared to >6 sec. before the Windows 10 Re-install, Driver updates, etc.

The "Microsoft Community" produced 2 Software volunteer experts that were my Chat coaches during this intricate process, where attention to detail is vital. The instructions on this website - and the support from its author - were world-class, and critical to my success.

https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/clean-install-windows-10/1c426bdf-79b1-4d42-be93-17378d93e587.

+ Thanks, Gary! I've added that URL to the top section of

<https://www.dxlabsuite.com/dxlabwiki/WindowsTricks>

73,

Dave, AA6YQ

Re: Slow Program Response Followup

Gary Smetana
 

Hi Mike,

Congrats on your performance upgrade.      Got a similar success story, that others may want to consider.

Because of wicked slow response times + some bizarre stuff from corrupted files,  I did a Re-Install of Windows 10.......after first doing a thorough back-up of my personal files + the DXkeeper log, etc.

After the new Windows 10 was loaded, I re-installed all my apps. + my personal files & the DXlab apps. + my DXkeeper log.

Then I did a thorough review & update of all the Drivers. (It's a l-o-n-g  list).    Many Drivers were out-of-date.

These actions have caused a boisterous  W o w !    My PC is perky & nimble again !       Not slow & sluggish anymore.
The Look-up of a call, using DXcapture & DXkeeper, is much faster now.  Done in < 2 sec. today... compared to >6 sec. before the Windows 10 Re-install, Driver updates, etc.

The "Microsoft Community" produced 2 Software volunteer experts that were my Chat coaches during this intricate process, where attention to detail is vital. The instructions on this website - and the support from its author -  were world-class, and critical to my success.

73,
Gary  de W1EBM



On Mon, Sep 9, 2019 at 8:26 PM na5u mlt <na5u@...> wrote:
I wanted to let the group know that the slow response was solved by a reload of Windows 10. I now have most the programs reloaded, as well as DXLab and all is well.
73,
Mike
NA5U