Date   

Re: "Leading! " Filter

ND9G Mike
 

I wouldn't do that, which may cause doubling of everything in Club Log. I don't know the capabilities of Club Log for preventing duplicates. I think it would be fine and it would likely match, but that could also be a long process. I personally wouldn't chance it and would clean it up locally to get things the way I want them.

Here is the way I would handle it, assuming that the 19 you identified initially are the only ones that you've changed since the upload..

1. Start by making a backup of your log. (Don't skip this step)
2. Clear any filtering you have in place to have all 160k QSOs displayed on your log page display
3a. Using the Advanced Sorts, Filters, & Modifers window (Click Adv button on the Log Page Display)
3b. At the bottom in the Modify QSOs in Log Page Display set
  • Item Name to APP_DXKeeper_ClubLog
  • Item new value to Y
  • Click the Mod button to set this value to Y for all 160k QSO
4. On the log page display, check the box to display the Auxiliary panel
5a. Locate each of the 19 QSOs that you modified based on your feedback from Club Log's email.
5b. In the Auxiliary panel, set the Club field value to M and save the record

If you then run the query that I sent previously, you should only display the ones you have modified (19)

Now go into QSL config and make sure your Club Log configuration is setup (see: https://www.dxlabsuite.com/dxkeeper/Help/QSLConfiguration.htm#Club%20Log%20Tab)

Once that is done, go to the Check Progress tab of DXKeeper, and you can click the Upload button in the Club Log panel, it will upload only those 19 records to Club Log.

Now in the future, you can periodically click this button to upload a batch of records that will be any you've changed since the last time, or any new ones. There is no need for you to set the Club field manually, DXK will keep track of any that you've changed since it was uploaded before, including if you change the QSl status or sync with LotW.

Please take a look at this section of the manual related to Club Log uploads.



73,
Mike ND9G


On Fri, Mar 27, 2020 at 9:42 AM Pete Smith <n4zr@...> wrote:

Thank you for the fuller explanation, Mike.  As you may have guessed, I wrote an ADIF file from the Export tab, and uploaded it using ClubLog's process.  So I guess that fundamentally I need to do it all again from the Check Progress tab.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 3/27/2020 9:48 AM, ND9G Mike wrote:
Pete,

As I mentioned previously, you don't need to do anything special. DX Keeper is built to handle these cases. If you upload to Club Log from the Check Progress tab of DX Keeper, it will mark every QSO uploaded to Club Log with a Y. Then if at any point you make a change to that QSO in DX Keeper, it will change it to an M. Any new QSOs will have no value in that field. When uploading using the Check Progress tab of DX Keeper, it will upload any QSO that is marked with something other than a Y or N (the N is a value that you can set manually if you don't want that QSO uploaded to Club Log at all. The field I'm referring to is the Club field in the Auxiliary panel of the Log QSOs tab.

This situation covers your initial upload and then any subsequent upload will only upload the batch that has never been uploaded or modified.

If you want to see how many QSOs would be uploaded by a subsequent upload from DX Keeper, run the following SQL query.
APP_DXKeeper_ClubLog NOT IN ('Y','N')

If you run that now, and get the entire 164,000 QSOs (check the title bar of DX Keeper to see how many records are with the filter), then DX Keeper has no indicator that you uploaded anything to Club Log. I would think this would be from you exporting an ADIF File and uploading it to Club Log independently. If you did this and none are marked as Y, then we'll want to address that first, then go back and set the 19 that you needed to edit to modified, so they can be uploaded in your next upload.


73,
Mike ND9G


On Fri, Mar 27, 2020 at 8:02 AM Pete Smith <n4zr@...> wrote:

First of all, "they" is Clublog support.  Sorry for not making that clearer. 

Dave, I'm not asking about QSO by QSO synchronizing, but about a one-time *export* of a few QSOs from my DXKeeper to Clublog.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 3/27/2020 2:09 AM, Dave AA6YQ wrote:
+ AA6YQ comments below

But what about ones where the problem was nothing more than a portable suffix?  For example, I logged AH3C/KH5, when it should have been  AH3C/KH5K according to Clublog.

+ With respect to AH3C/KH5 vs  AH3C/KH5K, I'd be more inclined to see what the station's operator submitted as his or her "Station Callsign" when they submitted their QSOs to LoTW.

They told me just to change it in DXLog, but what if I want to upload a tiny ADIF with only the amended QSOs, rather than re-sending the whole 164,000?

+ Who is "they"?

Is there a way to do that in DXKeeper?

DXKeeper is intended to server as your primary logging application. It provides facilities for importing batches of QSOs  made with specialized logging applications (like N1MM for contest QSOs, or one optimized for county hunting). It does not provide the ability to synchronize QSO-by-QSO with other logging applications.

       73,

              Dave, AA6YQ





Re: "Leading! " Filter

Pete Smith
 

Thank you for the fuller explanation, Mike.  As you may have guessed, I wrote an ADIF file from the Export tab, and uploaded it using ClubLog's process.  So I guess that fundamentally I need to do it all again from the Check Progress tab.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 3/27/2020 9:48 AM, ND9G Mike wrote:

Pete,

As I mentioned previously, you don't need to do anything special. DX Keeper is built to handle these cases. If you upload to Club Log from the Check Progress tab of DX Keeper, it will mark every QSO uploaded to Club Log with a Y. Then if at any point you make a change to that QSO in DX Keeper, it will change it to an M. Any new QSOs will have no value in that field. When uploading using the Check Progress tab of DX Keeper, it will upload any QSO that is marked with something other than a Y or N (the N is a value that you can set manually if you don't want that QSO uploaded to Club Log at all. The field I'm referring to is the Club field in the Auxiliary panel of the Log QSOs tab.

This situation covers your initial upload and then any subsequent upload will only upload the batch that has never been uploaded or modified.

If you want to see how many QSOs would be uploaded by a subsequent upload from DX Keeper, run the following SQL query.
APP_DXKeeper_ClubLog NOT IN ('Y','N')

If you run that now, and get the entire 164,000 QSOs (check the title bar of DX Keeper to see how many records are with the filter), then DX Keeper has no indicator that you uploaded anything to Club Log. I would think this would be from you exporting an ADIF File and uploading it to Club Log independently. If you did this and none are marked as Y, then we'll want to address that first, then go back and set the 19 that you needed to edit to modified, so they can be uploaded in your next upload.


73,
Mike ND9G


On Fri, Mar 27, 2020 at 8:02 AM Pete Smith <n4zr@...> wrote:

First of all, "they" is Clublog support.  Sorry for not making that clearer. 

Dave, I'm not asking about QSO by QSO synchronizing, but about a one-time *export* of a few QSOs from my DXKeeper to Clublog.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 3/27/2020 2:09 AM, Dave AA6YQ wrote:
+ AA6YQ comments below

But what about ones where the problem was nothing more than a portable suffix?  For example, I logged AH3C/KH5, when it should have been  AH3C/KH5K according to Clublog.

+ With respect to AH3C/KH5 vs  AH3C/KH5K, I'd be more inclined to see what the station's operator submitted as his or her "Station Callsign" when they submitted their QSOs to LoTW.

They told me just to change it in DXLog, but what if I want to upload a tiny ADIF with only the amended QSOs, rather than re-sending the whole 164,000?

+ Who is "they"?

Is there a way to do that in DXKeeper?

DXKeeper is intended to server as your primary logging application. It provides facilities for importing batches of QSOs  made with specialized logging applications (like N1MM for contest QSOs, or one optimized for county hunting). It does not provide the ability to synchronize QSO-by-QSO with other logging applications.

       73,

              Dave, AA6YQ





Re: "Leading! " Filter

ND9G Mike
 

Pete,

As I mentioned previously, you don't need to do anything special. DX Keeper is built to handle these cases. If you upload to Club Log from the Check Progress tab of DX Keeper, it will mark every QSO uploaded to Club Log with a Y. Then if at any point you make a change to that QSO in DX Keeper, it will change it to an M. Any new QSOs will have no value in that field. When uploading using the Check Progress tab of DX Keeper, it will upload any QSO that is marked with something other than a Y or N (the N is a value that you can set manually if you don't want that QSO uploaded to Club Log at all. The field I'm referring to is the Club field in the Auxiliary panel of the Log QSOs tab.

This situation covers your initial upload and then any subsequent upload will only upload the batch that has never been uploaded or modified.

If you want to see how many QSOs would be uploaded by a subsequent upload from DX Keeper, run the following SQL query.
APP_DXKeeper_ClubLog NOT IN ('Y','N')

If you run that now, and get the entire 164,000 QSOs (check the title bar of DX Keeper to see how many records are with the filter), then DX Keeper has no indicator that you uploaded anything to Club Log. I would think this would be from you exporting an ADIF File and uploading it to Club Log independently. If you did this and none are marked as Y, then we'll want to address that first, then go back and set the 19 that you needed to edit to modified, so they can be uploaded in your next upload.


73,
Mike ND9G


On Fri, Mar 27, 2020 at 8:02 AM Pete Smith <n4zr@...> wrote:

First of all, "they" is Clublog support.  Sorry for not making that clearer. 

Dave, I'm not asking about QSO by QSO synchronizing, but about a one-time *export* of a few QSOs from my DXKeeper to Clublog.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 3/27/2020 2:09 AM, Dave AA6YQ wrote:
+ AA6YQ comments below

But what about ones where the problem was nothing more than a portable suffix?  For example, I logged AH3C/KH5, when it should have been  AH3C/KH5K according to Clublog.

+ With respect to AH3C/KH5 vs  AH3C/KH5K, I'd be more inclined to see what the station's operator submitted as his or her "Station Callsign" when they submitted their QSOs to LoTW.

They told me just to change it in DXLog, but what if I want to upload a tiny ADIF with only the amended QSOs, rather than re-sending the whole 164,000?

+ Who is "they"?

Is there a way to do that in DXKeeper?

DXKeeper is intended to server as your primary logging application. It provides facilities for importing batches of QSOs  made with specialized logging applications (like N1MM for contest QSOs, or one optimized for county hunting). It does not provide the ability to synchronize QSO-by-QSO with other logging applications.

       73,

              Dave, AA6YQ





Re: Spot Collector stopped working

g4wjs
 

On 27/03/2020 13:01, K4PX K4PX wrote:
Spot Collector has stopped working.  Uninstalled and reinstalled but still not working.
Hi OM,

first thing to check is you PCs clock, did a DST adjustment get missed perhaps.



--
73

Bill

G4WJS.


Re: "Leading! " Filter

Pete Smith
 

First of all, "they" is Clublog support.  Sorry for not making that clearer. 

Dave, I'm not asking about QSO by QSO synchronizing, but about a one-time *export* of a few QSOs from my DXKeeper to Clublog.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 3/27/2020 2:09 AM, Dave AA6YQ wrote:

+ AA6YQ comments below

But what about ones where the problem was nothing more than a portable suffix?  For example, I logged AH3C/KH5, when it should have been  AH3C/KH5K according to Clublog.  

+ With respect to AH3C/KH5 vs  AH3C/KH5K, I'd be more inclined to see what the station's operator submitted as his or her "Station Callsign" when they submitted their QSOs to LoTW.

They told me just to change it in DXLog, but what if I want to upload a tiny ADIF with only the amended QSOs, rather than re-sending the whole 164,000?  

+ Who is "they"?

Is there a way to do that in DXKeeper?

DXKeeper is intended to server as your primary logging application. It provides facilities for importing batches of QSOs  made with specialized logging applications (like N1MM for contest QSOs, or one optimized for county hunting). It does not provide the ability to synchronize QSO-by-QSO with other logging applications.

       73,

              Dave, AA6YQ





Spot Collector stopped working

K4PX K4PX
 

Spot Collector has stopped working.  Uninstalled and reinstalled but still not working.


Warnings and Lock Up

wb6bee
 

I spent about an hour putting all my programs back together on five monitors after a "Call Book Look Up error" appeared.   The call was valid and QRZ brought it up, but the look up error notice locked up the five monitors and I could not find it.   It was buried behind some other window on a different monitor than I had entered the call sign.  By the time I found it, all the programs had minimized or moved off screen into space someplace.

I have now attempted to disable every "write over" or "call book Look up" error.    I hope I found them all.   It's Not because I don't like the notice or think its valuable, but because the error message locks up everything until the error is cleared and it appears where it wants to.   

It would be nice if the error message appeared dead center of the window you were entering the data, not someplace else on the surface of five monitors.

Don
WB6BEE


Re: "Leading! " Filter

Dave AA6YQ
 

+ AA6YQ comments below

But what about ones where the problem was nothing more than a portable suffix? For example, I logged AH3C/KH5, when it should have been AH3C/KH5K according to Clublog.

+ With respect to AH3C/KH5 vs AH3C/KH5K, I'd be more inclined to see what the station's operator submitted as his or her "Station Callsign" when they submitted their QSOs to LoTW.

They told me just to change it in DXLog, but what if I want to upload a tiny ADIF with only the amended QSOs, rather than re-sending the whole 164,000?

+ Who is "they"?

Is there a way to do that in DXKeeper?

DXKeeper is intended to server as your primary logging application. It provides facilities for importing batches of QSOs made with specialized logging applications (like N1MM for contest QSOs, or one optimized for county hunting). It does not provide the ability to synchronize QSO-by-QSO with other logging applications.

73,

Dave, AA6YQ


Re: "Leading! " Filter

Pete Smith
 

But what about ones where the problem was nothing more than a portable suffix?  For example, I logged AH3C/KH5, when it should have been  AH3C/KH5K according to Clublog.  They told me just to change it in DXLog, but what if I want to upload a tiny ADIF with only the amended QSOs, rather than re-sending the whole 164,000?  Is there a way to do that in DXKeeper?

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 3/26/2020 2:59 PM, Scott Stembaugh wrote:

Pete,

Any QSOs you deleted from DXKeeper you will need to manually delete from ClubLog.

73,
--scott N9LJX


On Thu, Mar 26, 2020 at 1:36 PM ve3ki <ve3iay@...> wrote:
Pete,

You don't want to prefix otherwise good log entries with !. A ! before the call sign indicates that the QSO in question is not valid for awards.

The Upload to Club Log button under the Check Progress tab automatically selects QSOs that have either never been uploaded or that have been modified since they were last uploaded. You don't need to select them manually.

73,
Rich VE3KI


On Thu, Mar 26, 2020 at 01:06 PM, Pete Smith wrote:

I recently uploaded my entire 164K QSO DXKeeper log to Clublog.  They responded with 19 exceptions, some of which I have deleted or corrected in DXKeeper, and now I would like to upload just those corrected entries in an ADIF file.  I saw the box for "leading !" in the Export QSOs tab and thought, "Oh goody, this must be the way to select just a few QSOs to export."  I tested this with one QSO from my log, and it didn't work, although DXKeeper did store the leading "!"

I've searched the Help, in vain, so here I am.  Help much appreciated!

-- 
73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.


Re: issue with MANUAL lotw upload

bill steffey NY9H
 

thanks,   you be the man .....

stay well


bill /3

On 3/26/2020 2:47 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

when LOTW was down I stopped automatically uploading , after each qso.
Club log kept working along fine.


I was able to set up the "auto loading" to LOTW after they got it fixed. I must have forgot something ,as I can no longer right click on a log entry and get the option to manually up load to lotw.

"Upload to lotw" is greyed out, while download from lotw is present/

Looks like I forgot to completely restore LOTW capabilities ??? Which box/s did I miss ????

+ On the Main window's QSL tab, are there one or more entries in the QSL Queue? If so, either finish the QSLing operation you have underway, or click the Clear button.

73,

Dave, AA6YQ



Re: Windows 10 Automatic Update Created Issue with Serial Ports

fjk5146
 

Dave (w6de)

Thanks for the information on disabling automatic driver updates.  It is good to know that the V1909 update also caused problems on more than just my system.  I have another computer that I use to monitor and record several security cameras using BlueIris software.  The Windows 10 update deleted my current BlueIris configuration file.  When BlueIris restarted after the Windows 10 update, it fell back to an older version of the configuration file.  I spent several hours trying to figure out why several of my cameras were no longer accessible!  I ended up rebuilding the configuration.  I also saved several backup copies of the corrected configuration to locations Windows cannot access!

I had read somewhere that when this update was first pushed out last year, that some systems were  experiencing data loss.  I think they stopped rolling out the update to correct the problem.  When it showed up on my system earlier this month I didn't anticipate any problems.  I guess I was wrong! 

I've now spent a lot of time documenting the hardware information of each of the serial ports should this happen again.

Thanks again to all that provided helpful information.

--
Fred, KC9QQ


Re: "Leading! " Filter

Scott Stembaugh
 

Pete,

Any QSOs you deleted from DXKeeper you will need to manually delete from ClubLog.

73,
--scott N9LJX


On Thu, Mar 26, 2020 at 1:36 PM ve3ki <ve3iay@...> wrote:
Pete,

You don't want to prefix otherwise good log entries with !. A ! before the call sign indicates that the QSO in question is not valid for awards.

The Upload to Club Log button under the Check Progress tab automatically selects QSOs that have either never been uploaded or that have been modified since they were last uploaded. You don't need to select them manually.

73,
Rich VE3KI


On Thu, Mar 26, 2020 at 01:06 PM, Pete Smith wrote:

I recently uploaded my entire 164K QSO DXKeeper log to Clublog.  They responded with 19 exceptions, some of which I have deleted or corrected in DXKeeper, and now I would like to upload just those corrected entries in an ADIF file.  I saw the box for "leading !" in the Export QSOs tab and thought, "Oh goody, this must be the way to select just a few QSOs to export."  I tested this with one QSO from my log, and it didn't work, although DXKeeper did store the leading "!"

I've searched the Help, in vain, so here I am.  Help much appreciated!

-- 
73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.


Re: K3 and Commander

Dave AA6YQ
 

+ AA6YQ comments below

How can I get the Commander module to not check off the Interrogation square? For some reason my K3 will not work after a while with the Interrogation checked off. I have to do a reset and it will work but soon stop. My KX3 will work all the time with the box checked off. Same parameters.

+ Does "checked off" mean

1. the Interrogation box is checked

or

2. the Interrogation box is unchecked

?

73,

Dave, AA6YQ


Re: issue with MANUAL lotw upload

Dave AA6YQ
 

+ AA6YQ comments below

when LOTW was down I stopped automatically uploading , after each qso.
Club log kept working along fine.


I was able to set up the "auto loading" to LOTW after they got it fixed. I must have forgot something ,as I can no longer right click on a log entry and get the option to manually up load to lotw.

"Upload to lotw" is greyed out, while download from lotw is present/

Looks like I forgot to completely restore LOTW capabilities ??? Which box/s did I miss ????

+ On the Main window's QSL tab, are there one or more entries in the QSL Queue? If so, either finish the QSLing operation you have underway, or click the Clear button.

73,

Dave, AA6YQ


Re: Recurring issue: awards recompute slows down to a crawl

Dave AA6YQ
 

+ AA6YQ comments below

My DXKeeper awards recompute function used to be "instantaneous", but now it is very slow. Here is one data point: QSO ends 13:37:00; recompute finishes 13:40:00. While the recompute is going on, the log is inaccessible. I had this problem before and it seemed to have self-rectified after installing the latest version of all software, but now the problem is back. All the software is up to date and Windows 10 has the latest updates installed.

I don't know if this problem is related to the fact that my JTAlert automatic logging to DXKeeper stopped working after I upgraded to Windows 10 a month or so ago?

I suspect though, that Windows 10 is the culprit here, but I would not know where to start to fix these problems?

+ As a first diagnostic step, reboot Windows into "safe mode with networking", start DXKeeper, and take an action that initiates recomputation; any change in the time required?

73,

Dave, AA6YQ


K3 and Commander

NK6A
 

How can I get the Commander module to not check off the Interrogation square?  For some reason my K3 will not work after a while with the Interrogation checked off.  I have to do a reset and it will work but soon stop. My KX3 will work all the time with the box checked off.  Same parameters.

Thanks,
Don


issue with MANUAL lotw upload

bill steffey NY9H
 

when LOTW was down  I stopped automatically uploading , after each qso. Club log kept working along fine.


I was able to set up the "auto loading" to LOTW after they got it fixed.  I must have forgot something ,as I can no longer right click on a log entry and get the option to manually up load to lotw.

"Upload to lotw" is greyed out, while download from lotw is present/

Looks like I forgot to completely restore LOTW capabilities ??? Which box/s  did I miss ????


stay well all


Re: "Leading! " Filter

ve3ki
 

Pete,

You don't want to prefix otherwise good log entries with !. A ! before the call sign indicates that the QSO in question is not valid for awards.

The Upload to Club Log button under the Check Progress tab automatically selects QSOs that have either never been uploaded or that have been modified since they were last uploaded. You don't need to select them manually.

73,
Rich VE3KI


On Thu, Mar 26, 2020 at 01:06 PM, Pete Smith wrote:

I recently uploaded my entire 164K QSO DXKeeper log to Clublog.  They responded with 19 exceptions, some of which I have deleted or corrected in DXKeeper, and now I would like to upload just those corrected entries in an ADIF file.  I saw the box for "leading !" in the Export QSOs tab and thought, "Oh goody, this must be the way to select just a few QSOs to export."  I tested this with one QSO from my log, and it didn't work, although DXKeeper did store the leading "!"

I've searched the Help, in vain, so here I am.  Help much appreciated!

-- 
73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.


Re: "Leading! " Filter

ND9G Mike
 

You shouldn't need to do anything special to upload the corrected entries.

From the Check Progress tab click the upload button in the Club Log panel. This will upload any newly added or changed entries since your last Club Log upload.

If you want to filter your log display to only show those that would be upload you can filter your log using SQL.
APP_DXKeeper_ClubLog NOT IN ('Y','N')

The Y indicates that DXKeeper knows this has been uploaded to Club Log, and the record hasn't changed since you uploaded it.
The N indicates that DX Keeper has been told to not upload this record to ClubLog, you likely don't have any of these.

Any that you have no uploaded yet should be blank, and any that you've edited since uploading should be set to M. All of these would get uploaded to Club Log if you press the upload button as described above.

Note: The above assumes that you'e configured DX Keeper with your Club Log user credentials in the QSL Config window.

73,
Mike ND9G


On Thu, Mar 26, 2020 at 12:06 PM Pete Smith <n4zr@...> wrote:

I recently uploaded my entire 164K QSO DXKeeper log to Clublog.  They responded with 19 exceptions, some of which I have deleted or corrected in DXKeeper, and now I would like to upload just those corrected entries in an ADIF file.  I saw the box for "leading !" in the Export QSOs tab and thought, "Oh goody, this must be the way to select just a few QSOs to export."  I tested this with one QSO from my log, and it didn't work, although DXKeeper did store the leading "!"

I've searched the Help, in vain, so here I am.  Help much appreciated!

-- 
73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.


Re: "Leading! " Filter

iain macdonnell - N6ML
 

On Thu, Mar 26, 2020 at 10:06 AM Pete Smith <n4zr@...> wrote:

I recently uploaded my entire 164K QSO DXKeeper log to Clublog. They responded with 19 exceptions, some of which I have deleted or corrected in DXKeeper, and now I would like to upload just those corrected entries in an ADIF file.
If you've configured DXKeeper for upload to Club Log [1], you'd just
need to make sure that "Club" is set to 'M' (in the Auxiliary panel)
for those QSOs, then click on "Upload" in the Club Log panel on the
Check Progress tab. Alternatively, you could right-click on each QSO
individually and select "Upload to Club Log".

73.

~iain / N6ML

[1] http://www.dxlabsuite.com/dxlabwiki/ClubLogUpload