Date   

Re: Undocumented updates

Peter Laws / N5UWY
 

On Fri, Jul 1, 2022 at 3:02 PM k6xt <k6xt@...> wrote:

Referring to our recent IC7300 XFC discussion how can I help you implement the discussed undocumented feature, should you decide to add it to your todo list? If you need one I'll send you my IC7300.

Incidentally my statement that the capability is undocumented referred to the user manual. Not a programmer, I don't know what assets are made available by Icom.
I am an Icom fanboy and I will be the first to say that the company
does not document CI-V well.

On my IC-910H, the CI-V command table is poorly rendered in the docs
and makes it appear that you can't turn on the transmitter via CI-V
... but you can ... and now Commander knows about this feature under
the name "IC-910HA". A fake ID because it's not clear which of the
versions of that radio supports it (910A, 910D, 910H, 911, etc) so
doing it like that is probably the best way to handle it.



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


Re: Undocumented updates

Dave AA6YQ
 

+ AA6YQ comments below
Reading the update notes for Commander 15.4.4 I see an undocumented feature on a Yaesu rig that wasn't ignored..

Referring to our recent IC7300 XFC discussion how can I help you implement the discussed undocumented feature, should you decide to add it to your todo list? If you need one I'll send you my IC7300.

Incidentally my statement that the capability is undocumented referred to the user manual. Not a programmer, I don't know what assets are made available by Icom.

+ "Supports the undocumented FT-757GXII meter reading CAT command" in Commander 15.4.4 was low risk: that radio's functionality cannot be changed via a firmware update, and the change supports a capability that isn't already present. If it were to fail due to a future action by Yaesu, users would be in no worse shape than they were before Commander 15.4.4.

+ Icom radios provide a Split mechanism that works well for working DX stations operating split. Exploiting undocumented commands in an Icom radio that is under active development with firmware updates to replicate functionality that already exists would be risky, and would not be a good use of my development time compared to alternative uses of that time.

          73,

               Dvae, AA6YQ

 


Undocumented updates

k6xt
 

Hi Dave

Reading the update notes for Commander 15.4.4 I see an undocumented feature on a Yaesu rig that wasn't ignored..

Referring to our recent IC7300 XFC discussion how can I help you implement the discussed undocumented feature, should you decide to add it to your todo list? If you need one I'll send you my IC7300.

Incidentally my statement that the capability is undocumented referred to the user manual. Not a programmer, I don't know what assets are made available by Icom.

73 Art K6XT/W7NTA


Re: DXKeeper 16.6.6 is available

Dave AA6YQ
 

+ AA6YQ comments below

Thanks for the MyQTH report button! Would it be possible to add a box letting you know the report is being created with an abort
button and progress bar? I have 99000 QSOs and 311 MyQTHs and it takes about 63 seconds to prepare the report. The first time I
ran it I didn't think it was working and pressed the report button a couple of times which produced a box saying the report couldn't
be created. Finally the report came up.

A box letting me know the report is being created would be really helpful.

73, Alan N5NA

+ That's a defect. In the next version of DXKeeper, the mouse cursor changes to a spinning wheel to indicate that the Report is
being generated, and you won't be able to re-invoke the Report while it's running. Thanks!

73,

Dave, AA6YQ


Re: QSL "R"

Earl Needham
 

Oops, one got away from me!  That blank message was a wild one, I tell ya'!

On Fri, Jul 1, 2022 at 12:16 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below
I have a habit of setting ALL QSL's to "R when I work somebody -- IOW I request QSL via LoTW, card, and eQSL.
 
Two questions -- first, is this ridiculous?

+ There is no log item named "ALL QSLs".

Yes, I've been doing this manually. 

+ DXKeeper's QSL automation is triggered by setting one or more of the "QSL Sent", "LoTW QSL Sent", and/or "eQSL QSL Sent" items to 'R', meaning "Requested". There are options on the appropriate tabs of the "QSL Configuration" window to automate this. 

<snip>

+ I suggest that you review

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

+ and

https://www.dxlabsuite.com/dxlabwiki/QSLing


Headed there now, thanks.

Earl



Re: QSL "R"

Earl Needham
 

On Fri, Jul 1, 2022 at 12:16 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below
I have a habit of setting ALL QSL's to "R when I work somebody -- IOW I request QSL via LoTW, card, and eQSL.
 
Two questions -- first, is this ridiculous?

+ There is no log item named "ALL QSLs".


 

+ DXKeeper's QSL automation is triggered by setting one or more of the "QSL Sent", "LoTW QSL Sent", and/or "eQSL QSL Sent" items to 'R', meaning "Requested". There are options on the appropriate tabs of the "QSL Configuration" window to automate this. 

+ The "Add Requested" function on the Main window's QSL tab employs these items to populate the QSL Queue, as a function of that tab's "QSL Via" panel setting. After an outgoing QSL card or label is printed from the QSL Queue, the "Update Log" function changes that QSO's "QSL Sent" item from 'R' to 'Y'. After submitting a QSO to LoTW, when the "Sync LoTW QSOs" function reports that QSO to have been accepted by LoTW, its "LoTW QSL Sent" item is set to 'Y' and and its "LoTW QSL Rcvd" item is set to 'R'. Submitting a QSO to eQSL sets its "eQSL QSL Sent" item to 'Y' and its "eQSL QSL Rcvd" item to 'R'.

+ The "Sync eQSL QSLs" and "Sync LoTW QSLs" functions automate the updating of a QSO's "eQSL QSL Rcvd" and "LoTW QSL Rcvd" items respectively. You must manually set a QSO's "QSL Rcvd" item to 'R' when you receive a QSL card for that QSO.

And second -- is there an automatic way to set the other two to, say, a blank when I receive a QSL via any method?

+ No. You wouldn't want the receipt of an eQSL confirmation to prevent you from seeking an LoTW confirmation, for example, as eQSL confirmations are not valid for ARRL awards.

+ I suggest that you review

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

+ and

https://www.dxlabsuite.com/dxlabwiki/QSLing

     73,

           Dave, AA6YQ

 

 


Re: QSL "R"

Dave AA6YQ
 

+ AA6YQ comments below
I have a habit of setting ALL QSL's to "R when I work somebody -- IOW I request QSL via LoTW, card, and eQSL.
 
Two questions -- first, is this ridiculous?

+ There is no log item named "ALL QSLs".

+ DXKeeper's QSL automation is triggered by setting one or more of the "QSL Sent", "LoTW QSL Sent", and/or "eQSL QSL Sent" items to 'R', meaning "Requested". There are options on the appropriate tabs of the "QSL Configuration" window to automate this. 

+ The "Add Requested" function on the Main window's QSL tab employs these items to populate the QSL Queue, as a function of that tab's "QSL Via" panel setting. After an outgoing QSL card or label is printed from the QSL Queue, the "Update Log" function changes that QSO's "QSL Sent" item from 'R' to 'Y'. After submitting a QSO to LoTW, when the "Sync LoTW QSOs" function reports that QSO to have been accepted by LoTW, its "LoTW QSL Sent" item is set to 'Y' and and its "LoTW QSL Rcvd" item is set to 'R'. Submitting a QSO to eQSL sets its "eQSL QSL Sent" item to 'Y' and its "eQSL QSL Rcvd" item to 'R'.

+ The "Sync eQSL QSLs" and "Sync LoTW QSLs" functions automate the updating of a QSO's "eQSL QSL Rcvd" and "LoTW QSL Rcvd" items respectively. You must manually set a QSO's "QSL Rcvd" item to 'R' when you receive a QSL card for that QSO.

And second -- is there an automatic way to set the other two to, say, a blank when I receive a QSL via any method?

+ No. You wouldn't want the receipt of an eQSL confirmation to prevent you from seeking an LoTW confirmation, for example, as eQSL confirmations are not valid for ARRL awards.

+ I suggest that you review

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

+ and

https://www.dxlabsuite.com/dxlabwiki/QSLing

     73,

           Dave, AA6YQ

 

 


Re: DXKeeper 16.6.6 is available

Alan N5NA
 


- provides a Report button on the Main window's "My QTHs" tab that generates a myQTH report that shows the number and percentage of
total QSOs made from each myQTH (requester lost in the mists of time)
Thanks for the MyQTH report button!  Would it be possible to add a box letting you know the report is being created with an abort button and progress bar?  I have 99000 QSOs and 311 MyQTHs and it takes about 63 seconds to prepare the report.  The first time I ran it I didn't think it was working and pressed the report button a couple of times which produced a box saying the report couldn't be created.  Finally the report came up.

A box letting me know the report is being created would be really helpful.

73, Alan N5NA


QSL "R"

Earl Needham
 

I have a habit of setting ALL QSL's to "R when I work somebody -- IOW I request QSL via LoTW, card, and eQSL.

Two questions -- first, is this ridiculous?

And second -- is there an automatic way to set the other two to, say, a blank when I receive a QSL via any method?

Tnx,
Earl
KD5XB


Re: DXKeeper 16.6.6 is available

Peter Laws / N5UWY
 

On Fri, Jul 1, 2022 at 11:02 AM Dave AA6YQ <aa6yq@...> wrote:

- what is specified in DXKeeper's "Program Path"?
I have a LOT of windows on my screens. At some point, while
DXKeeper's config dialog was on the screen, it had focus and what I
typed when there, scrambling the path.

All fixed now. When fellow League life member and IRCA member Wayne
said he'd had no issues, I knew I needed to angle the blame mirror a
little differently. :-)

Thanks for requesting methodical data collection as that lead me right
to the (my) error!

Now, off to run up my 50-MHz grid totals ... 250 is within sight.




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


Re: Filtering SC on Tags

Dave AA6YQ
 

+ AA6YQ comments below
I have the 13 Colony Stations in the Special Callsign table with the tag 13-Colonies.  When I enter 13-Colonies in the filter box and strike 'Tag' SC filters appropriately. But when I try to set a filter button with SQL expression "Tags = '13-Colonies' and mode = 'cw'" I get nothing in the display.  I have tried "Tag" and "Tags" with the same result (no errors, just nothing displayed).  I have tried "<>" around 13-Colonies but that throws a SQL error.
 
Since I only have the 13 Colony stations currently in the Special Callsign table, filtering on len(tags)>0 works.  But I would expect Tags like '13*' to work, but it doesn't.
 
I really would like the filter to also only show 13-Colony stations I have not worked this year, but that may be pushing it...

+ If you look at the TAGS field in a Spot Database Entry for a station whose callsign you tagged with 

13-Colonies

+ You will see that it contains

<13-Colonies>

+ Thus to filter the Spot Database Display to contain only entries tagged with

13-Colonies

+ use

TAGS LIKE '*13-colonies*'

+ This shorter expression will also work:

TAGS LIKE '*13*'

 

+ See "Filtering the Spot Database Display to Show Active Stations with Specified Tags" in

https://www.dxlabsuite.com/dxlabwiki/IdentifyLogClubMembers

       73,

              Dave, AA6YQ


Re: DXKeeper 16.6.6 is available

Dave AA6YQ
 

+ AA6YQ comments below
So ... See the New Apps message on launcher, click it, DXKeeper gets
upgraded. But when I start my workspace Launcher complains that I
haven't upgraded DXKeeper

+ What is the exact text of the complaint?

 

that the current version is "blank" but the
new version, in red, is 16.6.6.

+ On the "DXLab Apps" of the Launcher's Configuration window,

- what is specified in DXKeeper's "Program Path"?

- what is specified in DXKeeper's "Installed" version?

- what is specified in DXKeeper's "Available" version?

      73,

            Dave, AA6YQ

 


Re: DXKeeper 16.6.6 is available

Wayne Heinen
 

Interesting, no issues here

73 Wayne N0POH

----- Original Message -----
From: "Peter Laws / N5UWY" <plaws0@...>
To: "DXLab" <DXLab@groups.io>
Sent: Friday, July 1, 2022 9:42:51 AM
Subject: Re: [DXLab] DXKeeper 16.6.6 is available

So ... See the New Apps message on launcher, click it, DXKeeper gets
upgraded. But when I start my workspace Launcher complains that I
haven't upgraded DXKeeper, that the current version is "blank" but the
new version, in red, is 16.6.6.

I am quite certain that I closed the config window after upgrading, as
I have done *hundreds* of times, and that it popped back up its own.
Regardless, I am afraid to either try to run DXKeeper or click Upgrade
again (since it claims it is not installed).

In c:/apps/DXLab/DXKeeper, I see what I expect to see, and
DXKeeper.exe has the same timestamp and file size as DXKeeper1666.exe.

I checked for the DB file and it appears OK (though, once again, it's
backing up locally and not to my Dropbox, but I'm ignoring that for
now).




On Fri, Jul 1, 2022 at 12:17 AM Dave AA6YQ <aa6yq@...> wrote:

Before installing or upgrading to DXKeeper 16.6.6,

if you are using Window Defender Antivirus on Windows 10 or Windows 11, update it to its latest malware definition in

https://www.microsoft.com/en-us/wdsi/definitions


This version

- Correctly parses optional parameters associated with the External Log directive (tnx to Tim K1BR and Joe W4TV)

- provides a Report button on the Main window's "My QTHs" tab that generates a myQTH report that shows the number and percentage of
total QSOs made from each myQTH (requester lost in the mists of time)

- updates the MultipleQTHs.htm documentation file


Notes:

1. Update your firewall and anti-malware applications to consider this new version of DXKeeper to be "safe"

a. JOTTI virus scan: 0 of 15 scanners detected malware in this version's executable

b. VirusTotal: 0 of 67 scanners detected malware in this version's executable

c. submitted to Microsoft for analysis by Windows Defender: no malware detected in this version's executable

2. If this upgrade doesn't work correctly, see the "After an Upgrade" section of

http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking

3. After upgrading, to revert to the previous version of SpotCollector, see

http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion


DXKeeper 16.6.6 is available via the DXLab Launcher and via

http://www.dxlabsuite.com/download.htm

73,

Dave, AA6YQ






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


Re: DXKeeper 16.6.6 is available

Joe Subich, W4TV
 

Check the *PATH* to DXKeeper in DXLab Launcher and confirm it is
what/where you think it is.

If the current version is blank, DXLab Launcher does not see
*exactly* the path and exe file specified in the "Program Path"
box.

If the "Avail" is in red, the file in the "Program Path" is not
the "Available" (most recent) version.

73,

... Joe, W4TV

On 2022-07-01 11:42 AM, Peter Laws / N5UWY wrote:
So ... See the New Apps message on launcher, click it, DXKeeper gets
upgraded. But when I start my workspace Launcher complains that I
haven't upgraded DXKeeper, that the current version is "blank" but the
new version, in red, is 16.6.6.
I am quite certain that I closed the config window after upgrading, as
I have done *hundreds* of times, and that it popped back up its own.
Regardless, I am afraid to either try to run DXKeeper or click Upgrade
again (since it claims it is not installed).
In c:/apps/DXLab/DXKeeper, I see what I expect to see, and
DXKeeper.exe has the same timestamp and file size as DXKeeper1666.exe.
I checked for the DB file and it appears OK (though, once again, it's
backing up locally and not to my Dropbox, but I'm ignoring that for
now).
On Fri, Jul 1, 2022 at 12:17 AM Dave AA6YQ <aa6yq@...> wrote:

Before installing or upgrading to DXKeeper 16.6.6,

if you are using Window Defender Antivirus on Windows 10 or Windows 11, update it to its latest malware definition in

https://www.microsoft.com/en-us/wdsi/definitions


This version

- Correctly parses optional parameters associated with the External Log directive (tnx to Tim K1BR and Joe W4TV)

- provides a Report button on the Main window's "My QTHs" tab that generates a myQTH report that shows the number and percentage of
total QSOs made from each myQTH (requester lost in the mists of time)

- updates the MultipleQTHs.htm documentation file


Notes:

1. Update your firewall and anti-malware applications to consider this new version of DXKeeper to be "safe"

a. JOTTI virus scan: 0 of 15 scanners detected malware in this version's executable

b. VirusTotal: 0 of 67 scanners detected malware in this version's executable

c. submitted to Microsoft for analysis by Windows Defender: no malware detected in this version's executable

2. If this upgrade doesn't work correctly, see the "After an Upgrade" section of

http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking

3. After upgrading, to revert to the previous version of SpotCollector, see

http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion


DXKeeper 16.6.6 is available via the DXLab Launcher and via

http://www.dxlabsuite.com/download.htm

73,

Dave, AA6YQ






Re: DXKeeper 16.6.6 is available

Peter Laws / N5UWY
 

So ... See the New Apps message on launcher, click it, DXKeeper gets
upgraded. But when I start my workspace Launcher complains that I
haven't upgraded DXKeeper, that the current version is "blank" but the
new version, in red, is 16.6.6.

I am quite certain that I closed the config window after upgrading, as
I have done *hundreds* of times, and that it popped back up its own.
Regardless, I am afraid to either try to run DXKeeper or click Upgrade
again (since it claims it is not installed).

In c:/apps/DXLab/DXKeeper, I see what I expect to see, and
DXKeeper.exe has the same timestamp and file size as DXKeeper1666.exe.

I checked for the DB file and it appears OK (though, once again, it's
backing up locally and not to my Dropbox, but I'm ignoring that for
now).

On Fri, Jul 1, 2022 at 12:17 AM Dave AA6YQ <aa6yq@...> wrote:

Before installing or upgrading to DXKeeper 16.6.6,

if you are using Window Defender Antivirus on Windows 10 or Windows 11, update it to its latest malware definition in

https://www.microsoft.com/en-us/wdsi/definitions


This version

- Correctly parses optional parameters associated with the External Log directive (tnx to Tim K1BR and Joe W4TV)

- provides a Report button on the Main window's "My QTHs" tab that generates a myQTH report that shows the number and percentage of
total QSOs made from each myQTH (requester lost in the mists of time)

- updates the MultipleQTHs.htm documentation file


Notes:

1. Update your firewall and anti-malware applications to consider this new version of DXKeeper to be "safe"

a. JOTTI virus scan: 0 of 15 scanners detected malware in this version's executable

b. VirusTotal: 0 of 67 scanners detected malware in this version's executable

c. submitted to Microsoft for analysis by Windows Defender: no malware detected in this version's executable

2. If this upgrade doesn't work correctly, see the "After an Upgrade" section of

http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking

3. After upgrading, to revert to the previous version of SpotCollector, see

http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion


DXKeeper 16.6.6 is available via the DXLab Launcher and via

http://www.dxlabsuite.com/download.htm

73,

Dave, AA6YQ





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


Filtering SC on Tags

Scott Stembaugh
 

I have the 13 Colony Stations in the Special Callsign table with the tag 13-Colonies.  When I enter 13-Colonies in the filter box and strike 'Tag' SC filters appropriately. But when I try to set a filter button with SQL expression "Tags = '13-Colonies' and mode = 'cw'" I get nothing in the display.  I have tried "Tag" and "Tags" with the same result (no errors, just nothing displayed).  I have tried "<>" around 13-Colonies but that throws a SQL error.

Since I only have the 13 Colony stations currently in the Special Callsign table, filtering on len(tags)>0 works.  But I would expect Tags like '13*' to work, but it doesn't.

I really would like the filter to also only show 13-Colony stations I have not worked this year, but that may be pushing it...

Thanks for your help.

73,
--scott


Re: How to enter a date using the 'ADV' --> 'MOD' procedure,

Don Roland
 


Thanks Dave !  Works as advertised.
 
73 Don -VE1AOE-

----- Original Message -----
From: Dave AA6YQ
Sent: Thursday, June 30, 2022 10:19 PM
Subject: Re: [DXLab] How to enter a date using the 'ADV' --> 'MOD' procedure,

# more AA6YQ comments below
+ Which item did you select for modification
 
#### I tried several 'date items' Dave,  the one I was interested in was
####  APP_DXKeeper_LotW_QSLSDATE

+ What are the 7 characters you entered into the "Item new value" box?
 
####  06-27-2022  or  06072022  or  2022-06-27  or  20220627 and I sure others
####  ( on the 8th character on the above 'New Item Value' turns red )

# Enter the date in ISO 8601 format:

YYYY-MM-DD

#Ignore the "Item new value" being displayed in red font as you enter the date; when you enter the 10th character, it should be displayed in black font.

      73,

             Dave, AA6YQ


DXKeeper 16.6.6 is available

Dave AA6YQ
 

Before installing or upgrading to DXKeeper 16.6.6,

if you are using Window Defender Antivirus on Windows 10 or Windows 11, update it to its latest malware definition in

https://www.microsoft.com/en-us/wdsi/definitions


This version

- Correctly parses optional parameters associated with the External Log directive (tnx to Tim K1BR and Joe W4TV)

- provides a Report button on the Main window's "My QTHs" tab that generates a myQTH report that shows the number and percentage of
total QSOs made from each myQTH (requester lost in the mists of time)

- updates the MultipleQTHs.htm documentation file


Notes:

1. Update your firewall and anti-malware applications to consider this new version of DXKeeper to be "safe"

a. JOTTI virus scan: 0 of 15 scanners detected malware in this version's executable

b. VirusTotal: 0 of 67 scanners detected malware in this version's executable

c. submitted to Microsoft for analysis by Windows Defender: no malware detected in this version's executable

2. If this upgrade doesn't work correctly, see the "After an Upgrade" section of

http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking

3. After upgrading, to revert to the previous version of SpotCollector, see

http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion


DXKeeper 16.6.6 is available via the DXLab Launcher and via

http://www.dxlabsuite.com/download.htm

73,

Dave, AA6YQ


Re: How to enter a date using the 'ADV' --> 'MOD' procedure,

Dave AA6YQ
 

# more AA6YQ comments below
+ Which item did you select for modification
 
#### I tried several 'date items' Dave,  the one I was interested in was
####  APP_DXKeeper_LotW_QSLSDATE

+ What are the 7 characters you entered into the "Item new value" box?
 
####  06-27-2022  or  06072022  or  2022-06-27  or  20220627 and I sure others
####  ( on the 8th character on the above 'New Item Value' turns red )

# Enter the date in ISO 8601 format:

YYYY-MM-DD

#Ignore the "Item new value" being displayed in red font as you enter the date; when you enter the 10th character, it should be displayed in black font.

      73,

             Dave, AA6YQ


Re: Error in sound input

Steven
 

Today, home from the doctor, the error was waiting for me.  I makes no difference to have the radio on nor off, as it was today, during an FT8 contact, just monitoring, or about anytime it feels!  No RFI assumed.  I had the System>Sound>Volume Mixer on screen and the input and output was changed.   Worse yet, neither 4 or 5 USB Audio CODEX in/out could be found on the list!  I rebooted and back to 'normal'. 

Just need to figure out how to keep the working CODEX in Win 11 and not let 11 change the in/out on me!!!!!!!!!!!!!

1401 - 1420 of 210237