Date   

Re: No one is more deserving ...

Dave AA6YQ
 

+ AA6YQ comments below

Mega Kudos Dave..

+ Thanks, Joe!

73,

Dave, AA6YQ


Re: No one is more deserving ...

Joe - W9RF
 

Mega Kudos Dave..



73,

W9RF - Joe




On Monday, February 10, 2020, 11:41:31 AM CST, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below

``The Board conferred the ARRL President s Award on David H.
Bernstein, AA6YQ, in recognition of  exemplary, outstanding, and continuing service  to ARRL and its members as part of the ARRL Logbook of The World team. Bernstein was a charter member of the ARRL Logbook Committee and a  founding, influential, and devoted member  of the Committee on Communication with ARRL Members.''

Sincere congratulations, Dave.

+ Thanks, Peter!

          73,

                Dave, AA6YQ




Re: Spot Collector Spot Data Base Display Font Size Change

wb6bee
 

I am able to use font 11 in DXkeeper and it comes back after application termination.    Further tests on Spot Collector, it would not hold Font 10 either.  Upon termination, went back to font 9.  But, font 12 holds after termination.

This is not a big deal, Dave.     

Thanks

Don


Re: My location problem

Dave AA6YQ
 

+ AA6YQ comments below

But I do have one more burning question..... when the heck do you get the time to play the piano?

+ Sustained performance requires balance.

+ While I do work on DXLab pretty much every day, I also chase DX (mostly on 160m and 30m these days), practice piano (mostly Chopin
and Rachmaninoff) for an hour or two, take pictures, raise blueberries (5 very happy bushes), spend time with my XYL (we both love
watching movies), and (gasp) sleep 7 or 8 hours every night. Seriously, quality sleep is essential to long-term health.

+ What's the trick?

1. provide an online forum where users are comfortable asking questions and seeking help, and where experienced users are motivated
to participate and answer questions

2. provide comprehensive, accessible documentation

3. immediately correct reported defects

4. keep the source code clean and well-organized

5. after making a change, step through execution of the modified code, and then invited motivated users to help with the testing

6. include diagnostic tools that make it possible to see what's happening on the user's system (the errorlog.txt mechanism)

73,

Dave, AA6YQ


Re: reload busted qso to LOTW

Jamie WW3S
 

Thanks Dave, works FB....

On Feb 11, 2020, at 9:28 PM, Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

After I correct a callsign, how can I load that one call to LOTW?

+ Right-click the updated QSO's entry in the Log Page Display, and select "Upload to LoTW" from the popup menu.

73,

Dave, AA6YQ




Re: reload busted qso to LOTW

Dave AA6YQ
 

+ AA6YQ comments below

After I correct a callsign, how can I load that one call to LOTW?

+ Right-click the updated QSO's entry in the Log Page Display, and select "Upload to LoTW" from the popup menu.

73,

Dave, AA6YQ


Re: Importing contest logs rituals

Dave AA6YQ
 

+ AA6YQ comments below

LOTW knows all. Don’t do anything. Just import your N1MM log. Usually I then filter the log with the contest dates, export, and send that file to TQSL. Probably a little more cumbersome than it could be, but foolproof.

+ That's not necessary, Bill. Assuming you have DXKeeper configured as recommended in

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

+ this simple sequence on the Main window's QSL tab is sufficient:

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

2. click the "Add Requested" button

3. click the Upload to LoTW" button

73,

Dave, AA6YQ


Re: Importing contest logs rituals

Dave AA6YQ
 

+ AA6YQ comments below

Hello all....After participating the RTTY test the past weekend, I would like to import my contest log from N1MM to DXKeeper.

I am also currently entering my old paper logs into DxKeeper with the idea that I will apply for some of the basic awards WAS, WAC,
DXCC etc

after I upload all of these logs to LOTW.

My question is therefore, when I am doing the import into DXLab, should I be using the CBA button to fill in all the state info
etc for the American

Hams I just worked (otherwise how will LOTW know where these guys are?) for the sake of WAS??

+ When you submit a QSO to LoTW, it ignores any information you provide about the location of your QSO partner; LoTW exclusively
obtains this information from the "Station Location" that your QSO partner used to submit your QSO to LoTW.

+ After your QSO partner submits a QSOs that matches a QSO you submitted, subsequent execution of DXKeeper's "Sync LoTW QSLs"
function will update your logged QSO with the location information submitted by your QSO partner. Discrepancies between what you
logged and what your QSO partner reported are handled as described in the "Handling of LoTW Detail Inconsistencies" section of

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

+ Thus for QSOs confirmed via LoTW, the "new" information provided by a callbook lookup would be your QSO partner's name, and postal
address, and (for some DXCC entities) a primary and secondary administrative subdivision.

+ Callbook information is more helpful for stations that do not QSL via LoTW, but since some ops relocate, one must be careful about
updating QSOs made "long ago" with current callbook information. A QSO with me prior to 1997 was with Silicon Valley, not the Boston
suburbs - but a callbook update would update the QSO to reflect my current Massachusetts location.

+ Note that you can direct DXKeeper to augment imported QSOs with information obtained from its primary and secondary subdivision
databases, its DXCC database, and the Callbook selected on the Configuration window's Callbook tab. See

<https://www.dxlabsuite.com/dxkeeper/Help/Import.htm#Options>

73,

Dave, AA6YQ


Re: My location problem

Ron KU7Y
 

Many thanks again Dave.

I'll work my way through this and let you know how it goes.

But I do have one more burning question..... when the heck do you get the
time to play the piano?

OK, back in my hole,

Ron, KU7Y
Mountain Home, ID DN23dc
CW Ops #1211
BUG USERS #189
SKCC #4904
QRP ARCI #8829
SOC #2
Idaho DX Association
Ron@...

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Tuesday, February 11, 2020 6:22 PM
To: DXLab@groups.io
Subject: Re: [DXLab] My location problem

+ AA6YQ comments below

Once again I didn't ask the question very clearly!

I have a total of 5 MYQTHIDs and other then this new one, I don't know
either the start or stop dates for the other 4.

I was thinking that I could create another Workspace and import the last
backup that had all the proper MYQTHIDs. Then "import",
somehow, all the QSOs from this new MYQTHIDs into that log.

Does that make sense?

+ I suggest that you

1. Make a copy of your 2015 backup

2. Direct DXKeeper to open the copy of your 2015 backup that you made in
step 1, and then inspect the logged QSOs to determine the
date ranges for each of your myQTHs.

3. To determine the date ranges for your QTHs after the last QSO in your
2015 backup, log in to your LoTW account, and select the
"Your QSOs" tab. The "Select QSOs to List" box's "Start Date" and "End
Date" will enable you to query LoTW for QSOs (not QSLs!)
made during a particular month and year:

<https://lotw.arrl.org/lotw-help/view-accepted-qsos#ViewSpecificQSOs>

+ As illustrated in this screen shot

<https://lotw.arrl.org/lotw-help/data/uploads/qsoqueryresults.jpg>

+ the first column of the results table is a Details hyperlink that when
double clicked will display theeGrid square, State, and
County from which you made the QSO (assuming you included this
information in the "Station Location" you employed to submit the QSO
to LoTW). By probing LoTW in this way, you should be able to determine
date ranges for all of your myQTHs used after the last logged
QSO in your 2015 log backup.

3. When you have date ranges for all your myQTHs, then

3a. direct DXKeeper to open your current log

3b. backup you current log (Configuration window, Log tab, Backup
button)

3c. for each myQTH from which you operated,

3c-I Use the "UTC Filter" panel in the "Advanced Sorts, Filters, and
Modifiers" window to filter the Log Page Display to contain
only QSOs made from a specific myQTH

3c-II Use the "Modify QSOs" panel in the "Advanced Sorts, Filters, and
Modifiers" window to change the MYQTHID of each QSO in the
Log Page Display to the correct myQTHID for that date range

73,

Dave, AA6YQ





--
This email has been checked for viruses by AVG.
https://www.avg.com


reload busted qso to LOTW

Jamie WW3S
 

After I correct a callsign, how can I load that one call to LOTW? 


Re: Windows 10 users: heads up!

Russ Ravella
 

sorry- i replied to a previous post that would have explained the context for this but it didn’t attach for some reason.  It was from Dave’s “how to deal with Windows” documentation, specifically on. how to prevent a Windows update from overwriting current port drivers.

On Feb 11, 2020, at 6:30 PM, Russ Ravella via Groups.Io <rus5@...> wrote:

Hello,

Does anybody know how to do this (prevent Windows from automatically replacing com drivers during updates) with the current Windows 10 version (1909) ?  These instructions are sufficiently outdated that I can't find a way to translate them into current terms.  Also, lots of time trying to find something on the internet proved unsuccessful.  Microsoft, as usual, seems to have removed the option that previously existed but I think it can be done directly in the registry.  I just don't know how to find it there.

Thanks,
Russ, KR6W


Re: Windows 10 users: heads up!

Russ Ravella
 

Hello,

Does anybody know how to do this (prevent Windows from automatically replacing com drivers during updates) with the current Windows 10 version (1909) ?  These instructions are sufficiently outdated that I can't find a way to translate them into current terms.  Also, lots of time trying to find something on the internet proved unsuccessful.  Microsoft, as usual, seems to have removed the option that previously existed but I think it can be done directly in the registry.  I just don't know how to find it there.

Thanks,
Russ, KR6W


Re: Spot Collector Spot Data Base Display Font Size Change

Dave AA6YQ
 

+ AA6YQ comments below

You will figure this out. I proceeded with the logging ritual. I set the font size to 12. When I terminated Spot Collector and re-started it, it came back as 12. Hmmm?

So, I recreated what I was trying to do and set the font size to 11. I terminated it and it came back as 9.

I repeated the test multiple times. Set at 12, terminate, restart and it came back as 12. Set at 11, terminate, restart and it comes back as 9.

It doesn't like font size eleven.

The registry seems ok with 12, so it must be something odd about font 11.

+ I'm guessing that the font you've selected isn't available on your system in size 11, so the next smaller available font is being selected. There's no code in SpotCollector that does this; it's probably the functionality provided by Microsoft to manage fonts.

73,

Dave, AA6YQ


Re: My location problem

Dave AA6YQ
 

+ AA6YQ comments below

Once again I didn't ask the question very clearly!

I have a total of 5 MYQTHIDs and other then this new one, I don't know either the start or stop dates for the other 4.

I was thinking that I could create another Workspace and import the last backup that had all the proper MYQTHIDs. Then "import",
somehow, all the QSOs from this new MYQTHIDs into that log.

Does that make sense?

+ I suggest that you

1. Make a copy of your 2015 backup

2. Direct DXKeeper to open the copy of your 2015 backup that you made in step 1, and then inspect the logged QSOs to determine the
date ranges for each of your myQTHs.

3. To determine the date ranges for your QTHs after the last QSO in your 2015 backup, log in to your LoTW account, and select the
"Your QSOs" tab. The "Select QSOs to List" box's "Start Date" and "End Date" will enable you to query LoTW for QSOs (not QSLs!)
made during a particular month and year:

<https://lotw.arrl.org/lotw-help/view-accepted-qsos#ViewSpecificQSOs>

+ As illustrated in this screen shot

<https://lotw.arrl.org/lotw-help/data/uploads/qsoqueryresults.jpg>

+ the first column of the results table is a Details hyperlink that when double clicked will display theeGrid square, State, and
County from which you made the QSO (assuming you included this information in the "Station Location" you employed to submit the QSO
to LoTW). By probing LoTW in this way, you should be able to determine date ranges for all of your myQTHs used after the last logged
QSO in your 2015 log backup.

3. When you have date ranges for all your myQTHs, then

3a. direct DXKeeper to open your current log

3b. backup you current log (Configuration window, Log tab, Backup button)

3c. for each myQTH from which you operated,

3c-I Use the "UTC Filter" panel in the "Advanced Sorts, Filters, and Modifiers" window to filter the Log Page Display to contain
only QSOs made from a specific myQTH

3c-II Use the "Modify QSOs" panel in the "Advanced Sorts, Filters, and Modifiers" window to change the MYQTHID of each QSO in the
Log Page Display to the correct myQTHID for that date range

73,

Dave, AA6YQ


Re: Importing contest logs rituals

BILL KENNAMER
 

LOTW knows all. Don’t do anything. Just import your N1MM log. Usually I then filter the log with the contest dates, export, and send that file to TQSL. Probably a little more cumbersome than it could be, but foolproof. 

On Tuesday, February 11, 2020, 6:49 PM, Ted Boerkamp <tboerkamp@...> wrote:

Hello all....After participating the RTTY test the past weekend, I would like to import my contest log from N1MM to DXKeeper.

I am also currently entering my old paper logs into DxKeeper with the idea that I will apply for some of the basic awards WAS, WAC, DXCC etc

after I upload all of these logs to LOTW.

 My question is therefore, when I am doing the  import into DXLab, should I be using the CBA button to fill in all the state info etc for the American

Hams I just worked (otherwise how will LOTW know where these guys are?) for the sake of WAS?? Will this then add alot of new info to the DX stations

as well?

I would like opinions on how best I should do this and with which settings checked off in DXLab.

Any advice is welcome. I have looked at the DXLAb wiki already as well.

73 Ted VE3SS


Importing contest logs rituals

Ted Boerkamp
 

Hello all....After participating the RTTY test the past weekend, I would like to import my contest log from N1MM to DXKeeper.

I am also currently entering my old paper logs into DxKeeper with the idea that I will apply for some of the basic awards WAS, WAC, DXCC etc

after I upload all of these logs to LOTW.

 My question is therefore, when I am doing the  import into DXLab, should I be using the CBA button to fill in all the state info etc for the American

Hams I just worked (otherwise how will LOTW know where these guys are?) for the sake of WAS?? Will this then add alot of new info to the DX stations

as well?

I would like opinions on how best I should do this and with which settings checked off in DXLab.

Any advice is welcome. I have looked at the DXLAb wiki already as well.

73 Ted VE3SS


Re: LotW credit download: "Error: no country specified for card#"

steve.masticola@verizon.net
 

On its way. It''s not impossible that the log got corrupted.

73, -Steve WX2S


Re: Spot Collector Spot Data Base Display Font Size Change

wb6bee
 

Dave

You will figure this out.    I proceeded with the logging  ritual.   I set the font size to 12.   When I terminated Spot Collector and re-started it, it came back as 12.   Hmmm?

So, I recreated what I was trying to do and set the font size to 11.   I terminated it and it came back as 9.

I repeated the test multiple times.   Set at 12, terminate, restart and it came back as 12.   Set at 11, terminate, restart and it comes back as 9.

It doesn't like font size eleven.   

The registry seems ok with 12, so it must be something odd about font 11.

Don


Re: My location problem

Ron KU7Y
 

Sorry Dave,

Once again I didn't ask the question very clearly!

I have a total of 5 MYQTHIDs and other then this new one, I don't know
either the start or stop dates for the other 4.

I was thinking that I could create another Workspace and import the last
backup that had all the proper MYQTHIDs. Then "import", somehow, all the
QSOs from this new MYQTHIDs into that log.

Does that make sense?

OK, back in my hole,

Ron, KU7Y
Mountain Home, ID DN23dc
CW Ops #1211
BUG USERS #189
SKCC #4904
QRP ARCI #8829
SOC #2
Idaho DX Association
Ron@...

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Tuesday, February 11, 2020 4:27 PM
To: DXLab@groups.io
Subject: Re: [DXLab] My location problem

+ AA6YQ comments below

I fear that I have shot myself in the foot. :-(

When we moved to this new QTH I added it to the MYATHID with all the
address information and all the other items asked for. So far,
so good.

But then, without realizing it I managed to apply that change to all
17,000+ QSOs in the whole log. In the information area of the
"my QRH" tab I do not see any date to tell when I either started or
ended operation from each different QTH.

Is there any way to tell when I changed to a different QTH?

My fingers are crossed......

I do have backups dated back to 2015 if that will help. But I am unsure
of how to use those while protecting my current log.

Jan 1, 2018 is when I started operating from this QTH.


+ If all QSOs made prior to 2018-01-01 were made from the same myQTH,
then

1. backup your log (Configuration window, Log tab)

2. filter the Log Page Display with

QSO_Begin < #2018-01-01#

3. In the "Advanced Sorts, Filters, and Modifiers" windows, "Modify
QSOs" panel,

3a. set the "Item name" selector to MYQTHID

3b. set the "Item new value" selector to appropriate MYQTHID for the
QSOs you made before 2018-01-01

3c. click the Mod button

73,

Dave, AA6YQ






--
This email has been checked for viruses by AVG.
https://www.avg.com


Re: LotW credit download: "Error: no country specified for card#"

Dave AA6YQ
 

+ AA6YQ comments below

Yes to all. "QSL Rcvd" is unset but "LotW QSL Rcvd" is set to V.

+ Please place your log file in a zip archive, and attach archive to an email message along with the discrepancy report. Then send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

18381 - 18400 of 209542