ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
esc to dismiss
Thanks Joe and Dave for your help. ?I understand now.
73
Stan? KM4HQE
On Thu, Apr 17, 2025 at 10:25 PM, Joe Subich, W4TV < lists@...> wrote:
> So, another guess. Is confirmed cards cards that I've received and
> verified cards cards I had a card checker check and the ARRL granted
> credit for the checked cards?
Yes, "Confirmed" is cards (or LotW credits) you have received.
Verified is credits that have been awarded by ARRL based on a
DXCC (or WAS, VUCC, etc. as applicable) application.
> The summary sections? Please explain.
What I call the "summery" sections are the bottom rows of the
progress report ... "Includes deleted entities" and "Non-deleted
(current) entities only"
73,
... Joe, W4TV
On 2025-04-17 10:39 PM, Stan Gammons via groups.io wrote:
> Hi Joe,
>
> On 4/17/25 21:12, Joe Subich, W4TV wrote:
>> On 2025-04-17 9:46 PM, Stan Gammons via groups.io wrote:
>> > I was wondering what the Card column in the DXCC progress report
>> > denotes?
>>
>> Is confirmed (Y) or verified (V - credit granted by ARRL) by card.
>
> So, another guess.? Is confirmed cards cards that I've received and
> verified cards cards I had a card checker check and the ARRL granted
> credit for the checked cards?
>
>>
>> In the summary sections "Card" indicates the number of countries
>> confirmed/verified by card and "LotW" indicates the number of
>> countries confirmed/verified by LotW credits.
>
> The summary sections?? Please explain.
>
>
> 73
>
> Stan
> KM4HQE
>
>
|
Thanks. That will do it.
73
-.. . / -- .- .-. -.- / -. --... -.-- -..
DE? MARK? N7YD
toggle quoted message
Show quoted text
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Joe Subich, W4TV via
groups.io
Sent: Friday, April 18, 2025 06:23
To: [email protected]
Subject: Re: [DXLab] !
On 2025-04-18 3:16 AM, Mark N7YD wrote:
> Thanks for taking a look at this.
QSL Tab -> QSL Config -> General
*UNCHECK* "Upload QSOs whose callsigns begin with !"
(last line in the"options" box at the top of the tab)
73,
... Joe, W4TV
On 2025-04-18 3:16 AM, Mark N7YD wrote:
Ok. This solves another thing for me. In years past, when we all kept paper logs, we were asked to record station changes and other information in our
logbook. It would go in the log as a comment with none of the QSO
information filled in. I had been trying to figure out how to do that for any
information I wanted to record in the DXKeeper log. I hadn¡¯t yet gotten into
mind how to make the feature request¡
And now I know it isn¡¯t necessary as the support is already there.
However, I just ran into an issue. It appears that logging a comment like this
still tries to upload the ¡°QSO¡± to QRZ and possibly other logging/QSL services. I
got a couple of popups from QRZ, and both the eQSL and LoTW panels are
showing ¡°R¡± for Sent. I would guess that a QSO with a ¡°!¡± in the callsign should
probably prevent the record from being uploaded to those services. Just a
guess, however. ?
Thanks for taking a look at this.
73
-.. . / -- .- .-. -.- / -. --... -.-- -..
DE MARK N7YD
From: [email protected] <[email protected]> On Behalf Of Dave AA6YQ via
groups.io
Sent: Thursday, April 17, 2025 10:27
To: [email protected]
Subject: [DXLab] !
+ AA6YQ comments beloew
Dave's DXKeeper manual (Logging New QSOs with the Capture window) says:
If the first letter of the callsign you enter is an exclamation point, DXKeeper assumes that you are logging a CQ, an unsuccessful call, a test, or some other
transmission that you wish to record but does not represent a QSO. Such log
entries are not assigned a DXCC prefix, do not initiate a Callbook database
lookup, and are not included in award tracking statistics.
+ Exactly right. Click the Capture window's Begin button when you start calling CQ; when you stop calling CQ, click the Capture window's End button
and log the CQ. When calling a station, initially place a ! in front of the callsign
of the station you're calling (in the Capture window's Callsign box), and click the
Begin button. If the station responds, remove the !. If not, log the unsuccessful
call.
73,
Dave, AA6YQ
|
|
| |
toggle quoted message
Show quoted text
On Apr 18, 2025, at 10:31, NS9I via groups.io <ns9i.dgb@...> wrote:
How does one get QRZ to automatically enter the address into addr box when you enter a contact into the log?
thanks 73 Dwight NS9I
How does one get QRZ to automatically enter the address into addr box when you enter a contact into the log?
thanks 73 Dwight NS9I
|
On 2025-04-18 3:16 AM, Mark N7YD wrote: Thanks for taking a look at this. QSL Tab -> QSL Config -> General *UNCHECK* "Upload QSOs whose callsigns begin with !" (last line in the"options" box at the top of the tab) 73, ... Joe, W4TV On 2025-04-18 3:16 AM, Mark N7YD wrote: Ok. This solves another thing for me. In years past, when we all kept paper logs, we were asked to record station changes and other information in our logbook. It would go in the log as a comment with none of the QSO information filled in. I had been trying to figure out how to do that for any information I wanted to record in the DXKeeper log. I hadn¡¯t yet gotten into mind how to make the feature request¡
And now I know it isn¡¯t necessary as the support is already there.
However, I just ran into an issue. It appears that logging a comment like this still tries to upload the ¡°QSO¡± to QRZ and possibly other logging/QSL services. I got a couple of popups from QRZ, and both the eQSL and LoTW panels are showing ¡°R¡± for Sent. I would guess that a QSO with a ¡°!¡± in the callsign should probably prevent the record from being uploaded to those services. Just a guess, however. ?
Thanks for taking a look at this.
73
-.. . / -- .- .-. -.- / -. --... -.-- -..
DE MARK N7YD
From: [email protected] <[email protected]> On Behalf Of Dave AA6YQ via groups.io
Sent: Thursday, April 17, 2025 10:27
To: [email protected]
Subject: [DXLab] !
+ AA6YQ comments beloew
Dave's DXKeeper manual (Logging New QSOs with the Capture window) says:
If the first letter of the callsign you enter is an exclamation point, DXKeeper assumes that you are logging a CQ, an unsuccessful call, a test, or some other transmission that you wish to record but does not represent a QSO. Such log entries are not assigned a DXCC prefix, do not initiate a Callbook database lookup, and are not included in award tracking statistics.
+ Exactly right. Click the Capture window's Begin button when you start calling CQ; when you stop calling CQ, click the Capture window's End button and log the CQ. When calling a station, initially place a ! in front of the callsign of the station you're calling (in the Capture window's Callsign box), and click the Begin button. If the station responds, remove the !. If not, log the unsuccessful call.
73,
Dave, AA6YQ
|
Ok.? This solves another thing for me.? In years past, when we all kept paper logs, we were asked to record station changes and other information in our logbook.? It would go in the log as a comment with none
of the QSO information filled in.? I had been trying to figure out how to do that for any information I wanted to record in the DXKeeper log.? I hadn¡¯t yet gotten into mind how to make the feature request¡
?
And now I know it isn¡¯t necessary as the support is already there.
?
However, I just ran into an issue.? It appears that logging a comment like this still tries to upload the ¡°QSO¡± to QRZ and possibly other logging/QSL services.? I got a couple of popups from QRZ, and both
the eQSL and LoTW panels are showing ¡°R¡± for Sent.? I would guess that a QSO with a ¡°!¡± in the callsign should probably prevent the record from being uploaded to those services.? Just a guess, however.?
?
?
Thanks for taking a look at this.
?
?
73
-.. . / -- .- .-. -.- / -. --... -.-- -..
DE? MARK? N7YD
?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]>
On Behalf Of Dave AA6YQ via groups.io
Sent: Thursday, April 17, 2025 10:27
To: [email protected]
Subject: [DXLab] !
?
Dave's DXKeeper manual (Logging New QSOs with the Capture window) says:
If the first letter of the callsign you enter is an exclamation point, DXKeeper assumes that you are logging a CQ, an unsuccessful call, a test, or some other transmission that you wish to record but does not represent
a QSO. Such log entries are not assigned a DXCC prefix, do not initiate a Callbook database lookup, and are not included in award tracking statistics.
+ Exactly right. Click the Capture window's Begin button when you start calling CQ; when you stop calling CQ, click the Capture window's End button and log the CQ. When calling a station, initially place a ! in front of the callsign of
the station you're calling (in the Capture window's Callsign box), and click the Begin button. If the station responds, remove the !. If not, log the unsuccessful call.?
? ? ?73,
? ? ? ? ? ?Dave, AA6YQ
|
So, another guess. Is confirmed cards cards that I've received and
verified cards cards I had a card checker check and the ARRL granted
credit for the checked cards? Yes, "Confirmed" is cards (or LotW credits) you have received. Verified is credits that have been awarded by ARRL based on a DXCC (or WAS, VUCC, etc. as applicable) application. The summary sections? Please explain. What I call the "summery" sections are the bottom rows of the progress report ... "Includes deleted entities" and "Non-deleted (current) entities only" 73, ... Joe, W4TV On 2025-04-17 10:39 PM, Stan Gammons via groups.io wrote: Hi Joe,
On 4/17/25 21:12, Joe Subich, W4TV wrote:
On 2025-04-17 9:46 PM, Stan Gammons via groups.io wrote:
> I was wondering what the Card column in the DXCC progress report
> denotes?
Is confirmed (Y) or verified (V - credit granted by ARRL) by card. So, another guess.? Is confirmed cards cards that I've received and
verified cards cards I had a card checker check and the ARRL granted
credit for the checked cards?
In the summary sections "Card" indicates the number of countries
confirmed/verified by card and "LotW" indicates the number of
countries confirmed/verified by LotW credits.
The summary sections?? Please explain.
73
Stan
KM4HQE
|
+ AA6YQ comments below
On 2025-04-17 9:46 PM, Stan Gammons via groups.io wrote:
> I was wondering what the Card column in the DXCC progress report
> denotes?
Is confirmed (Y) or verified (V - credit granted by ARRL) by card.
So, another guess.? Is confirmed cards cards that I've received and
verified cards cards I had a card checker check and the ARRL granted
credit for the checked cards?
+ A 'Y' in the Cards column denotes "confirmed via QSL card" + A 'V' in the Cards column denotes "DXCC award credit granted to a QSL card confirmation. A card checker checking a card is QSL card often - but not always - the first step towards received DXCC award credit for that card. For example, when I'm applying for DXCC award credits, I send QSL cards to the ARRL DXCC Desk via registered mail.
In the summary sections "Card" indicates the number of countries
confirmed/verified by card and "LotW" indicates the number of
countries confirmed/verified by LotW credits.
The summary sections?? Please explain.
+ Joe is referring the two 3-line sections at the end of the DXCC Progress report: one labeled "Includes deleted entities",? and the other labeled "Non-deleted entities only"; both sections include Card and LoTW columns. ? ? ? ? 73, ? ? ? ? ? ? ? ? ? Dave, AA6YQ
|
Hi Joe, On 4/17/25 21:12, Joe Subich, W4TV wrote: On 2025-04-17 9:46 PM, Stan Gammons via groups.io wrote:
> I was wondering what the Card column in the DXCC progress report
> denotes?
Is confirmed (Y) or verified (V - credit granted by ARRL) by card. So, another guess.? Is confirmed cards cards that I've received and verified cards cards I had a card checker check and the ARRL granted credit for the checked cards?
In the summary sections "Card" indicates the number of countries
confirmed/verified by card and "LotW" indicates the number of
countries confirmed/verified by LotW credits.
The summary sections?? Please explain. 73 Stan KM4HQE
|
On 2025-04-17 9:46 PM, Stan Gammons via groups.io wrote: I was wondering what the Card column in the DXCC progress report
denotes? Is confirmed (Y) or verified (V - credit granted by ARRL) by card. Similarly in the LotW column, Y = confirmed, V = verified. In the summary sections "Card" indicates the number of countries confirmed/verified by card and "LotW" indicates the number of countries confirmed/verified by LotW credits. 73, ... Joe, W4TV On 2025-04-17 9:46 PM, Stan Gammons via groups.io wrote: I was wondering what the Card column in the DXCC progress report
denotes?? Perhaps I overlooked it on this page
In my report it
shows 191 confirmed and 40 verified.
73
Stan
KM4HQE
|
I was wondering what the Card column in the DXCC progress report
denotes?? Perhaps I overlooked it on this page
In my report it
shows 191 confirmed and 40 verified.
73
Stan
KM4HQE
|
+ AA6YQ comments below
I guess I blew it.? I just received a new computer and am trying to get DXLabs working on it.
?
Honestly, nearly everything was working immediately, just a couple of nits to work out.
?
First, in Commander, when I try to load a file to any of the "command" buttons, I get the following:
?
2025-04-17 17:55:52.618 > program error 52 in module UserCommandSequenceDefinition.LoadCmd_Click: Bad file name or number
I suspect I named a folder incorrectly or something, but I'm not sure.? Help, anyone?
?
+ So that I can see what's going on, please do the following: 1. on the Configuration window's General tab, check the "Log debugging info" box 2. terminate Commander
?
3. start Commander, and wait for it to fully initialize
?
5. attempt to load a User-defined Command Sequence from a file
6. on the Configuration window's General tab, check the "Log debugging info" box
7. attach the errorlog.txt file from your Commander folder to an email message, and send the message to me via
aa6yq (at) ambersoft.com
? ? ? ?73,
? ? ? ? ? ? Dave, AA6YQ
|
I guess I blew it.? I just received a new computer and am trying to get DXLabs working on it.
Honestly, nearly everything was working immediately, just a couple of nits to work out.
First, in Commander, when I try to load a file to any of the "command" buttons, I get the following:
2025-04-17 17:55:52.618 > program error 52 in module UserCommandSequenceDefinition.LoadCmd_Click: Bad file name or number
I suspect I named a folder incorrectly or something, but I'm not sure.? Help, anyone?
Thanks, Earl / KD5XB DM84
e e
|
Re: Logging when transmissions are made
+ AA6YQ comments beloew
Dave's DXKeeper manual (Logging New QSOs with the Capture window) says:
If the first letter of the callsign you enter is an exclamation point, DXKeeper assumes that you are logging a CQ, an unsuccessful call, a test, or some other transmission that you wish to record but does not represent a QSO. Such log entries are not assigned a DXCC prefix, do not initiate a Callbook database lookup, and are not included in award tracking statistics.
+ Exactly right. Click the Capture window's Begin button when you start calling CQ; when you stop calling CQ, click the Capture window's End button and log the CQ. When calling a station, initially place a ! in front of the callsign of the station you're calling (in the Capture window's Callsign box), and click the Begin button. If the station responds, remove the !. If not, log the unsuccessful call.? ? ? ?73, ? ? ? ? ? ?Dave, AA6YQ
|
Re: Logging when transmissions are made
Dave's DXKeeper manual (Logging New QSOs with the Capture window) says:
If the first letter of the callsign you enter is an exclamation point, DXKeeper assumes that you are logging a CQ, an unsuccessful call, a test, or some other transmission that you wish to record but does not represent a QSO. Such log entries are not assigned a DXCC prefix, do not initiate a Callbook database lookup, and are not included in award tracking statistics.
73 de ON6TM,
Tony
|
Logging when transmissions are made
I am interested in having a log of when I make any transmission as a way to track down interference complaints.? Is this something that can be done with the DX Labs SW?? If not, does anyone have any suggestion?
?
Thanks,
?
Bruce
KO4PRE
|
Re: LOTW --- DXKeeper discrepancy
+ AA6YQ comments below
I always upload via DXKeeper. I have been using DXLAbs for more than 10 years, this is the only time this issue has occurred.
+ If it happens again, please let me know. ? ? ? 73, ? ? ? ? ? ? ?Dave, AA6YQ
|
Re: LOTW --- DXKeeper discrepancy
Dave
I always upload via DXKeeper. I have been using DXLAbs for more than 10 years, this is the only time this issue has occurred.
The procedure you outlined worked perfectly!
Thanks for the great?suite of programs and the great support!
Thanks Dan KC2STA
+ AA6YQ comments below
I attempted a LOTW upload today, it aborted due to a duplicate.?
?
Investigation reveals 26 qsos that were uploaded to LOTW, but DXKeeper says Not uploaded.?
?
I have them identified.??
?
I confirmed that are in LOTW.?
+ Did you submit them to LoTW from an application other than DXKeeper?
What is best way to change DXKeeper to LOTW uploaded?
+ Like this:
1. Filter the Log Page Display to contain those 26 QSOs; it's ok if other QSOs are included, if that makes the filtering easier.
2. On the Main window's QSL tab,?
2a. set the "QSL Via" panel to LoTW
2b. click the "Update from LoTW" button
? ? ? ?73,
? ? ? ? ? ? ?Dave, AA6YQ
-- Dan Ziolkowski KC2STA
SKCC #4290T
Ubuntu LINUX
|
Re: LOTW --- DXKeeper discrepancy
+ AA6YQ comments below
I attempted a LOTW upload today, it aborted due to a duplicate.?
?
Investigation reveals 26 qsos that were uploaded to LOTW, but DXKeeper says Not uploaded.?
?
I have them identified.??
?
I confirmed that are in LOTW.?
+ Did you submit them to LoTW from an application other than DXKeeper?
What is best way to change DXKeeper to LOTW uploaded?
+ Like this:
1. Filter the Log Page Display to contain those 26 QSOs; it's ok if other QSOs are included, if that makes the filtering easier.
2. On the Main window's QSL tab,?
2a. set the "QSL Via" panel to LoTW
2b. click the "Update from LoTW" button
? ? ? ?73,
? ? ? ? ? ? ?Dave, AA6YQ
|
Re: Launcher installed but does not appear in task bar or as an Icon
+ AA6YQ comments below
Hello Dave......After writing to the group I turned the computer off and took a break. When I turned the computer back on I went to the Launcher folder and clicked on the Launcher exec. it loaded the Launcher again and the Relocation backup was in the Workspaces. I checked to see if the files I moved were present in the Relocation backup, they were. I clicked Load the Workspace and Windows gave me hell for changing the registry settings, but finally let me load the Workspaces.? I then loaded the files into the locations in the New PC.?
?
I have not yet connected the new PC to the radio. I have not clicked? restore buttons in the Launcher yet.
+ There is no reason to click the Launcher's "Restore" buttons; you've already directed the Launcher to install your DXLab applications.
The Launcher buttons are all red and the Pathways shown in the configuration window of the Launcher show the proper pathways
+ "Red" means "installed but not running", as expected.
?
a) should I connect the radio to the PC at this point before I hit the restore button?
?
I have prevented the USB ports from powering down.
?
All the Path names are the same for the installation and its on a single monitor.
?
I think I am at item 12 once the above is accomplished. not sure what I need to do in item 12 but will endeavor to figure that out once I get that far.
+ I suggest that you direct the Launcher to start DXView. If DXView's Main window appears and it runs correctly, then connect your radio to your PC, and direct the Launcher to start Commander. If that works correctly, then proceed with step 12; if you encounter more questions or concerns, don't hesitate to post them here.
?
I am not sure what caused the Launcher issue but I appears to have rectified itself once I clicked on the Launcher Exec.
?
+ Please attach the errorlog.txt file from your Launcher folder to an email message, and send the message to me via?
?
aa6yq (at) ambersoft.com
?
I was also able to get the Launcher pinned to the Task bar so that is good to go now.
I think I am on the right track.....Thank you I am sure that this is not the last time you all will hear from me.....Thank God for this group and your infinite patience.
?
+ No problem, James; this group is chock full of ops willing and able to help.
? ? ? ?73,
? ? ? ? ? ? ?Dave, AA6YQ
|
