Date   

VUCC report query

Phil Cooper
 

Hi Dave and the group,

Simply because my compromise antenna seems to be doing better than expected, mainly because of the improving conditions on 6m, I am starting to chase DXCC, and also keeping an eye on my VUCC total on LoTW.

Currently, LoTW shows that I have 200 grids confirmed on 6m.
However, when I check the VUCC report in DXKeeper, it says 214 worked and 186 confirmed.

Looking at the report, there are quite a few that show MISSING under the LoTW Confirm heading, but are confirmed on LoTW and show up in my VUCC total.
Is it because they were RTTY, rather than FT8, where the grid is usually logged, whist in RTTY, it usually isn't?

I also notice that the VUCC report brings up contacts where there is no card, and no LoTW confirmation, so I would really like to get a VUCC report for just those grids confirmed on LoTW. is that possible?

I'm also very surprised at the number of stations using 6m that use LoTW, but do not have a grid set in whatever it is they use to upload to LoTW! Sadly, most are Italian stations, but there are others too.

73 de Phil GU0SUP


Re: Windows 11

Gilbert Baron W0MN
 

Two things. First I got 2 copies of this post but one had no text. They came at the same time. Very strange.
As for W11, my worry is not the possibility of trouble with W11 and the coding tools used buy Dave. So far it seems there is o problem.

My worry is that when W10 support ends I will be out of luck since I cannot switch to W11 under the 3rd gen processor in this machine. Everything I have is running well and do not wat to be forced to buy a new machine. If the current information that you will need an 8th gen processor to run W11 is true it is a worry. On the other hand I would not be surprised if things force me to buy new machines. At least it is 4 years away you say.

Outlook Laptop Gil W0MN
Hierro candente, batir de repente
44.08226N 92.51265W EN34rb

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Al Groff via groups.io
Sent: Monday, July 19, 2021 13:08
To: DXLab@groups.io
Subject: Re: [DXLab] Windows 11

FWIW..
DXLAB and my other ham apps have been running without any issue unique to Windows 11.

BUT your mileage may vary! And Windows 11 could still change before release.

AL, K0VM


On 7/19/2021 12:57 PM, Peter Laws / N5UWY wrote:
The currently published "retirement" date for Windows 10 is 2025-10-14.

The current guess for Windows 11 general availability is "October 2021".

If you are concerned/upset/excited about W11, go here
https://github.com/rcmaehl/WhyNotWin11 and click "Download latest
stable release" and run it. That will tell you if your system meets
*today's* list of W11 requirements.

SO FAR, my particular CPU is "not supported" (only non-green box on
the tool). I expect that this will change before (or even after) W11
ships and if it *doesn't*, I am likely to have replaced the system by
the time of W10's "retirement" anyway given that it's approaching 4
years old.

IOW, I don't spend a lot of time thinking about it. Besides, 50 MHz
is still quite open, so my time is better spent adding grids.










--
W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


Re: DXK DXCC Submission Question

Dave AA6YQ
 

+ AA6YQ comments below

I have generated a DXCC submission in DXK, based on QSL cards received, that resulted in 139 QSO's being selected for submission. I only want to include 100 of those QSO's. If I go into my log and change the QSL received status for the 39 QSO's that I don't want to submit from "S" back to "Y" and I then generate the ADIF file for online submission will the ADIF file only include the 100 QSO's I want to submit? Assuming my DXCC application QSO's are later all verified by DXCC, if I select "Verify Submission" will DXK only change the QSL received status to "V" for the 100 QSO's I submitted?

+ Yes.

I know the answer may seem obvious but I want to check with the experts before I mess things up if I'm wrong. I already messed up my log by changing QSO's in the QSL Queue a while back and I don't want a repeat.

+ To alleviate your anxiety, I strongly suggest that you make a backup copy of your log before starting the above process. Then you'll be able to "undo" if things don't go as expected.

73,

Dave, AA6YQ


Re: Windows 11

Ed W2LCQ
 

Great focus Dave. Thanks for those replies.

73, de Ed Jones W2LCQ

Frankford Radio Club
BUG CWops SKCC FISTS LICWC QCWA

On Jul 19, 2021, at 2:08 PM, Al Groff via groups.io <al.k0vm@...> wrote:

FWIW..
DXLAB and my other ham apps have been running without any issue unique to Windows 11.

BUT your mileage may vary! And Windows 11 could still change before release.

AL, K0VM


On 7/19/2021 12:57 PM, Peter Laws / N5UWY wrote:
The currently published "retirement" date for Windows 10 is 2025-10-14.

The current guess for Windows 11 general availability is "October 2021".

If you are concerned/upset/excited about W11, go here
https://github.com/rcmaehl/WhyNotWin11 and click "Download latest
stable release" and run it. That will tell you if your system meets
*today's* list of W11 requirements.

SO FAR, my particular CPU is "not supported" (only non-green box on
the tool). I expect that this will change before (or even after) W11
ships and if it *doesn't*, I am likely to have replaced the system by
the time of W10's "retirement" anyway given that it's approaching 4
years old.

IOW, I don't spend a lot of time thinking about it. Besides, 50 MHz
is still quite open, so my time is better spent adding grids.







Re: Windows 11

Al Groff
 

FWIW..
  DXLAB and my other ham apps have been running without any issue unique to Windows 11.

BUT your mileage may vary!  And Windows 11 could still change before release.

AL, K0VM

On 7/19/2021 12:57 PM, Peter Laws / N5UWY wrote:
The currently published "retirement" date for Windows 10 is 2025-10-14.

The current guess for Windows 11 general availability is "October 2021".

If you are concerned/upset/excited about W11, go here
https://github.com/rcmaehl/WhyNotWin11 and click "Download latest
stable release" and run it. That will tell you if your system meets
*today's* list of W11 requirements.

SO FAR, my particular CPU is "not supported" (only non-green box on
the tool). I expect that this will change before (or even after) W11
ships and if it *doesn't*, I am likely to have replaced the system by
the time of W10's "retirement" anyway given that it's approaching 4
years old.

IOW, I don't spend a lot of time thinking about it. Besides, 50 MHz
is still quite open, so my time is better spent adding grids.



Re: Windows 11

Peter Laws / N5UWY
 

The currently published "retirement" date for Windows 10 is 2025-10-14.

The current guess for Windows 11 general availability is "October 2021".

If you are concerned/upset/excited about W11, go here
https://github.com/rcmaehl/WhyNotWin11 and click "Download latest
stable release" and run it. That will tell you if your system meets
*today's* list of W11 requirements.

SO FAR, my particular CPU is "not supported" (only non-green box on
the tool). I expect that this will change before (or even after) W11
ships and if it *doesn't*, I am likely to have replaced the system by
the time of W10's "retirement" anyway given that it's approaching 4
years old.

IOW, I don't spend a lot of time thinking about it. Besides, 50 MHz
is still quite open, so my time is better spent adding grids.



--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


Re: Windows 11

Dave AA6YQ
 

+ AA6YQ comments below

I see this morning that W11 will not install on any processor that is not at least an 8th generation I assume that means W10 will stay with us

+ That's Microsoft's call.

and that DXLab will live on with my 3rd generation processor, right?

+ The last time I checked, DXLab applications could still run on Windows 98.

73,

Dave, AA6YQ


DXK DXCC Submission Question

Dale Drake
 

I have generated a DXCC submission in DXK, based on QSL cards received, that resulted in 139 QSO's being selected for submission.  I only want to include 100 of those QSO's.  If I go into my log and change the QSL received status for the 39 QSO's that I don't want to submit from "S" back to "Y" and I then generate the ADIF file for online submission will the ADIF file only include the 100 QSO's I want to submit?  Assuming my DXCC application QSO's are later all verified by DXCC, if I select "Verify Submission" will DXK only change the QSL received status to "V" for the 100 QSO's I submitted?

I know the answer may seem obvious but I want to check with the experts before I mess things up if I'm wrong.  I already messed up my log by changing QSO's in the QSL Queue a while back and I don't want a repeat.

Thanks,

Dale AA1QD


Windows 11

Gilbert Baron W0MN
 

I see this morning that W11 will not install on any processor that is not at least an 8th generation I assume that means W10 will stay with us and that DXLab will live on with my 3rd generation processor, right? 😊

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


Re: DXKeeper 16.0.7 is available

Dave AA6YQ
 

+ AA6YQ comments below

"responds to a double-click of a Spot Database Entry in SpotCollector with SpotCollector's "Log Filter" option set to "Call" and
DXKeeper's "Display previous QSOs on Lookup" option disabled by setting the Filter panel textbox to the Spot Database Entry's
callsign, making it possible to quickly display previous QSOs with that callsign by clicking the Filter panel's Call button (tnx to
Joe W9RF)"

=======

I just came across this enhancement today, and find it incredibly useful. Then, I found myself wanting just a little more. Could this feature be extended to the Spots/callsigns displayed in the Bandspread window?

+ I've sent you a new version of DXKeeper with the requested functionality; please let me know how it goes...

73,

Dave, AA6YQ


Re: Problem Printing QSL Labels

Dave AA6YQ
 

+ AA6YQ comments below
'm trying to print QSL labels for the first time and when I hit the PRINT QSL LABELS button on the DXKeeper (16.1.9) QSL tab I run into this error message: "unable to configure printer: paper size not selected"

Is that a DXKeeper error or is it coming from the printer?  The printer is loaded with sheets of Avery 8160 labels, and the QSL via selection is 3-column labels.  There are 86 QSOs in the QSL Queue, and each of them is selected in the QSL column.

The printer is a HP42EEB4 (HP Officejet 7500 E910) on my home network.   Managing that printer from WIndows 10 reveals that the paper source is Tray 1 (the only option shown) and paper size is Letter (the correct size for the Avery sheets).

What am I missing?

+ Did you set the appropriate Size selector on the "QSL Configuration" window's Printer tab?

      73,

           Dave, AA6YQ


Problem Printing QSL Labels

Walter Miller, AJ6T
 

I'm trying to print QSL labels for the first time and when I hit the PRINT QSL LABELS button on the DXKeeper (16.1.9) QSL tab I run into this error message: "unable to configure printer: paper size not selected"

Is that a DXKeeper error or is it coming from the printer?  The printer is loaded with sheets of Avery 8160 labels, and the QSL via selection is 3-column labels.  There are 86 QSOs in the QSL Queue, and each of them is selected in the QSL column.

The printer is a HP42EEB4 (HP Officejet 7500 E910) on my home network.   Managing that printer from WIndows 10 reveals that the paper source is Tray 1 (the only option shown) and paper size is Letter (the correct size for the Avery sheets).

What am I missing?

73, Walt, AJ6T


Re: DXKeeper 16.0.7 is available

Jim McPhee
 

On Sat, Mar 13, 2021 at 11:33 PM, Dave AA6YQ wrote:
"responds to a double-click of a Spot Database Entry in SpotCollector with SpotCollector's "Log Filter" option set to "Call" and
DXKeeper's "Display previous QSOs on Lookup" option disabled by setting the Filter panel textbox to the Spot Database Entry's
callsign, making it possible to quickly display previous QSOs with that callsign by clicking the Filter panel's Call button (tnx to
Joe W9RF)"
=======

Dave,

I just came across this enhancement today, and find it incredibly useful. Then,  I found myself wanting just a little more. Could this feature be extended to the Spots/callsigns displayed in the Bandspread window?

I know, I know. Are your users never satisfied!

73,
 
--
Jim McPhee
Placitas, NM
W5ABA


Re: harvesting information from duplicate QSOs

Mike - W1MI
 

Thanks for the explanation Dave.  Now that I understand it, no I don't have a '"real world scenario" in which either form of the above new functionality could be tested'.
73, Mike - W1MI


On Sun, Jul 18, 2021 at 08:46 PM, Dave AA6YQ wrote:
+ No, that would require a separate project. Also, there is no way for a DXLab application to know whether the information provided by a callbook lookup is accurate or outdated.

OK, but after the Qs are in DXKeeper, this filter could be used?

+ Only if the QSOs were duplicates.

Does "duplicates" (in your original message) mean QSOs with the same call, but not necessarily the same date, mode, band?

+ Same callsign, same band, same mode, same date-and-time within the range specified in the Range box in the Duplicates panel on the "Advanced Sorts, Filters, and Modifiers" window. See

https://www.dxlabsuite.com/dxkeeper/Help/FilterLog.htm#Duplicate%20filter

+ When you're logging new a new QSO with callsign C from DXKeeper or WinWarbler, you can arrange for previous QSOs C to be displayed in DXKeeper's Log Page Display, and for the following information to be harvested from those previous and included in the new QSO if not already specified: DXCC entity, name, QSL via, QTH, Grid 1, IOTA, QSL address, Primary Administrative Subdivision, Secondary Administrative Subdivision, ITU, CQ, continent, eQSL.cc member and LotW member. See, for example

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

73,

Dave, AA6YQ


Re: Broken Link-"Display callsign progress on Lookup"

Dave AA6YQ
 

+ AA6YQ comments below

Broken Link

file:///C:/DXLab/DXKeeper/Help/ViewEditLog.htm

Under "Viewing Previous QSO Information"

Two links to "Display callsign progress on Lookup" at:

C:/Program Files (x86)/DXLab Suite/DXKeeper/Help/Configuration.htm#Display callsign progress on Lookup

Are broken.

+ Corrected. Thanks, Jim!

73,

Dave, AA6YQ


Re: SpotCollector web server stopped working

g4wjs
 

On 18/07/2021 21:30, Dave AA6YQ wrote:
+ AA6YQ comments below

I wonder if anyone else has experienced this issue, on both Chrome on my smart phone and Firefox on my PC I get an error response from the SpotCollector web server like this:

<HTML><HEAD><TITLE>SpotCollector Web Server</TITLE></HEAD><BODY><font face="Arial"><B>GET </B> is not supported</font></BODY></HTML>

As far as I know this started spontaneously, the server was working fine a week or two ago.

+ SpotCollector's web server accepts 3 commands:

GET SPOTS

GET SMALLSPOTS

GET FAVICON.ICO

+ Your error message above indicates that SpotCollector received a GET command with no argument.

73,

Dave, AA6YQ
Hi Dave,

oops, a case of RTFM needed. Apologies for the bandwidth.



--
73

Bill

G4WJS.


Re: harvesting information from duplicate QSOs

Dave AA6YQ
 

+ No, that would require a separate project. Also, there is no way for a DXLab application to know whether the information provided by a callbook lookup is accurate or outdated.

OK, but after the Qs are in DXKeeper, this filter could be used?

+ Only if the QSOs were duplicates.

Does "duplicates" (in your original message) mean QSOs with the same call, but not necessarily the same date, mode, band?

+ Same callsign, same band, same mode, same date-and-time within the range specified in the Range box in the Duplicates panel on the "Advanced Sorts, Filters, and Modifiers" window. See

https://www.dxlabsuite.com/dxkeeper/Help/FilterLog.htm#Duplicate%20filter

+ When you're logging new a new QSO with callsign C from DXKeeper or WinWarbler, you can arrange for previous QSOs C to be displayed in DXKeeper's Log Page Display, and for the following information to be harvested from those previous and included in the new QSO if not already specified: DXCC entity, name, QSL via, QTH, Grid 1, IOTA, QSL address, Primary Administrative Subdivision, Secondary Administrative Subdivision, ITU, CQ, continent, eQSL.cc member and LotW member. See, for example

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

73,

Dave, AA6YQ


Re: SpotCollector web server stopped working

Dave AA6YQ
 

+ AA6YQ comments below

I wonder if anyone else has experienced this issue, on both Chrome on my smart phone and Firefox on my PC I get an error response from the SpotCollector web server like this:

<HTML><HEAD><TITLE>SpotCollector Web Server</TITLE></HEAD><BODY><font face="Arial"><B>GET </B> is not supported</font></BODY></HTML>

As far as I know this started spontaneously, the server was working fine a week or two ago.

+ SpotCollector's web server accepts 3 commands:

GET SPOTS

GET SMALLSPOTS

GET FAVICON.ICO

+ Your error message above indicates that SpotCollector received a GET command with no argument.

73,

Dave, AA6YQ


Re: harvesting information from duplicate QSOs

Mike - W1MI
 

+ No, that would require a separate project. Also, there is no way for a DXLab application to know whether the information provided by a callbook lookup is accurate or outdated.

OK, but after the Qs are in DXKeeper, this filter could be used?

Does "duplicates" (in your original message) mean QSOs with the same call, but not necessarily the same date, mode, band?

Thanks, Mike - W1MI


Broken Link-"Display callsign progress on Lookup"

Jim McPhee
 

Broken Link

file:///C:/DXLab/DXKeeper/Help/ViewEditLog.htm

Under "Viewing Previous QSO Information"

Two links to "Display callsign progress on Lookup" at:

C:/Program Files (x86)/DXLab Suite/DXKeeper/Help/Configuration.htm#Display callsign progress on Lookup

Are broken.
--
Jim McPhee
Placitas, NM
W5ABA

7081 - 7100 of 209562