Date   
Re: DXView Rolling display

Rod Greene
 

Thanks Dave, I’ll check that setting. Rod


Sent from Yahoo Mail for iPad

On Thursday, August 13, 2020, 5:21 PM, David Bunte <dpbunte@...> wrote:

Rod -

It sounds to me like you have the option "AUTOMATIC DXVIEW LOOKUP" checked under the GENERAL option of the SC Config tab.

Dave - K9FN

On Thu, Aug 13, 2020 at 6:35 PM Rod Greene via groups.io <w7zrc=yahoo.com@groups.io> wrote:
I just updated my DXLabs apps and now DXView continues to roll with the spots that are coming in via Spot Collector.

I thought DXV used to stay on the spot that was double clicked in Spot Collector. Now DXV jsut continues to change with the spots that come in. I have reviewed the documentation Help and have not found any settings relating to this. Have I missed something?

I would rather DXV stopped and stayed with the information displayed for the spot that I have selected and double clicked in SC.

Thanks and 73, Rod/w7zrc

Re: JTAlert logging to DXKeeper stopped working

Dave AA6YQ
 

+ AA6YQ comments below

I've had WSJT-X --> JTAlert --> DXKeeper logging working for a long time, but it has stopped working recently.

WSJT-X: v2.2.2
JTAlertX 2.10.2
DXKeeper: 15.7.2

Going into JTAlert Settings --> Applications --> DXLab Suite --> Test and clicking "test" shows DXKeeper as "running" and DDE Connect as "connected".

Going into JTAlert Settings --> Logging DXLab DXKeeper shows that "Enable DXLab DXKeeper Logging" is checked, TCP Network Service Port is 5200. Online logs are not checked.

Going into WSJT-X Settings --> Reporting tab shows that none of the "Logging" boxes is checked, UDP Server is set to 127.0.0.1, UDP Server port number is set to 2237, and all three UDP request boxes at the right are checked.

No error message is generated when I click Log QSO in WSJT-X, but no log entry is added in DXKeeper. It fails silently.

Commander is running, and is working correctly switching T/R under direction of WSJT-X. When I manually log the QSO, it successfully reads the frequency from the transceiver.


Any ideas what may have changed to make this stop working?

+ As a first step, I suggest that you review the settings as documented here:

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

73,

Dave, AA6YQ

JTAlert logging to DXKeeper stopped working

Catherine James
 

I've had WSJT-X --> JTAlert --> DXKeeper logging working for a long time, but it has stopped working recently.

WSJT-X:  v2.2.2
JTAlertX 2.10.2
DXKeeper: 15.7.2

Going into JTAlert Settings --> Applications --> DXLab Suite --> Test and clicking "test" shows DXKeeper as "running" and DDE Connect as "connected".

Going into JTAlert Settings --> Logging DXLab DXKeeper shows that "Enable DXLab  DXKeeper Logging" is checked, TCP Network Service Port is 5200.  Online logs are not checked.

Going into WSJT-X Settings --> Reporting tab shows that none of the "Logging" boxes is checked, UDP Server is set to 127.0.0.1, UDP Server port number is set to 2237, and all three UDP request boxes at the right are checked.

No error message is generated when I click Log QSO in WSJT-X, but no log entry is added in DXKeeper. It fails silently.

Commander is running, and is working correctly switching T/R under direction of WSJT-X. When I manually log the QSO, it successfully reads the frequency from the transceiver.


Any ideas what may have changed to make this stop working?

Re: Fixed mouse wheel steps in Commander Spectrum-waterfall display?

Dave AA6YQ
 

+ AA6YQ comments below

I cannot find a way to set a fixed frequency step when using the mouse wheel in the Spectrum-Waterfall display.
The intuitive way of using the mouse is to first click on some interesting signal, and then fine tune with the mouse.
When the only option I seam to have is to select a percentage of the current frequency span visable in the display it gets pretty useless imho.
E.g. if I set a suitable percentage in 40m band, which is 200k wide at most (here in SM) and shift to 10m which is 1M wide at most (due to my radio) the frequency steps are 5 times larger in 10m than in 40m even though the signal I'm trying to tune is still an SSB with a fixed bandwidth of about 2.5k...

The only way I can get a consistent frequency step between different bands is to set the scroll speed to 0.001% as it will hit the smallest possible tune accepted by my radio which is 10hz in my case.

I would really like to be able to set the frequency step for the mouse wheel operation, either a fixed herzt per mode, or per band, och to follow the settings in the commander window, i.e. which decimal is selected in the commander window.

Or am I missing some setting I cannot find?

+ I have extended the next version of Commander to provide a new "fixed frequency" option in the "Mousewheel Motion" panel on the Spectrum-Waterfall Configuration window. When this new "fixed frequency" option is selected, you can specify a fixed frequency (in hertz) for each mode. Your "% of range" settings are preserved; you can return to them by clicking the new "% of range" option.

+ Please let me know how it goes...

73,

Dave, AA6YQ

Re: DXView Rolling display

David Bunte
 

Rod -

It sounds to me like you have the option "AUTOMATIC DXVIEW LOOKUP" checked under the GENERAL option of the SC Config tab.

Dave - K9FN

On Thu, Aug 13, 2020 at 6:35 PM Rod Greene via groups.io <w7zrc=yahoo.com@groups.io> wrote:
I just updated my DXLabs apps and now DXView continues to roll with the spots that are coming in via Spot Collector.

I thought DXV used to stay on the spot that was double clicked in Spot Collector. Now DXV jsut continues to change with the spots that come in. I have reviewed the documentation Help and have not found any settings relating to this. Have I missed something?

I would rather DXV stopped and stayed with the information displayed for the spot that I have selected and double clicked in SC.

Thanks and 73, Rod/w7zrc

DXView Rolling display

Rod Greene
 

I just updated my DXLabs apps and now DXView continues to roll with the spots that are coming in via Spot Collector.

I thought DXV used to stay on the spot that was double clicked in Spot Collector. Now DXV jsut continues to change with the spots that come in. I have reviewed the documentation Help and have not found any settings relating to this. Have I missed something?

I would rather DXV stopped and stayed with the information displayed for the spot that I have selected and double clicked in SC.

Thanks and 73, Rod/w7zrc

Fixed mouse wheel steps in Commander Spectrum-waterfall display?

Björn (SM0SBL)
 

I cannot find a way to set a fixed frequency step when using the mouse wheel in the Spectrum-Waterfall display.
The intuitive way of using the mouse is to first click on some interesting signal, and then fine tune with the mouse.
When the only option I seam to have is to select a percentage of the current frequency span visable in the display it gets pretty useless imho.
E.g. if I set a suitable percentage in 40m band, which is 200k wide at most (here in SM) and shift to 10m which is 1M wide at most (due to my radio) the frequency steps are 5 times larger in 10m than in 40m even though the signal I'm trying to tune is still an SSB with a fixed bandwidth of about 2.5k...

The only way I can get a consistent frequency step between different bands is to set the scroll speed to 0.001% as it will hit the smallest possible tune accepted by my radio which is 10hz in my case.

I would really like to be able to set the frequency step for the mouse wheel operation, either a fixed herzt per mode, or per band, och to follow the settings in the commander window, i.e. which decimal is selected in the commander window.

Or am I missing some setting I cannot find?

--
Björn, SM0SBL

Re: SpotCollector 8.7.3 is available

RIchard Thorne
 

Dave,

Thanks for the additional support of SOTA. Its fun being a chaser.

Rich - N5ZC

On 8/12/2020 2:53 PM, Dave AA6YQ wrote:
If you are using Windows Defender anti-malware, direct it to update its definitions from
https://www.microsoft.com/en-us/wdsi/definitions
before you install SpotCollector 8.7.3. The executables in this version have been submitted to Microsoft for analysis and declared
free of malware. In theory, Window Defender with updated definitions should not consider them harmful - but I have not tested this.
This release
- detects a conflict in UpdateSpotDatabaseEntryWithSNRPrediction and automatically retries
- prevents creation of an errorlog.txt entry from DXCCDatabaseModule.GetOriginStringList when the spotter's callsign is less than 2
characters in length (tnx to Wolf DK1FW)
- tolerates a spot whose date and time are more than 22 days before or after the current date (tnx to Franco F6GCP)
- when a K1JT-mode Spot Database Entry is double-clicked, directs WSTX-J to populate its "DX Call" with the callsign, and generate
standard messages for that callsign (tnx to John W1JA)
- adds a POTA field that is populated with the Parks on the Air code extracted from spot notes and conveys this information to
DXKeeper (15.7.1 or later) and WinWarbler (9.2.9 or later) when a Spot Database Entry is double-clicked (tnx to Tom NQ7R)
- adds a SOTA field that is populated with the Summits on the Air code extracted from spot notes and conveys this information to
DXKeeper (15.7.1 or later) and WinWarbler (9.2.9 or later) when a Spot Database Entry is double-clicked (tnx to Kent N6WT)
- adds a WWFF field that is populated with the Worldwide Flora & Fauna area code extracted from spot notes and conveys this
information to DXKeeper (15.7.1 or later) and WinWarbler (9.2.9 or later) when a Spot Database Entry is double-clicked (tnx to Stan
KM4HQE and Mike W0MU)
- updates the index.htm and SpotDatabase.htm documentation files
Notes:
1. When you double-click a Spot Database Entry whose POTA field specifies a Parks on the Air code with DXKeeper (version 15.7.1 or
later) running, then contents of the POTA field will be placed in the Capture window's User-defined item whose caption is POTA
2. When you double-click a Spot Database Entry whose SOTA field specifies a Summits on the Air code with DXKeeper (version 15.7.1 or
later) running, then contents of the SOTA field will be placed in the Capture window's SOTA item
3. When you double-click a Spot Database Entry whose WWFF field specifies a Worldwide Flora and Fauna code with DXKeeper (version
15.7.1 or later) running, then contents of the WWFF field will be placed in the Capture window's User-defined item whose caption is
WWFF
4. Update your firewall and anti-malware applications to consider this new version of SpotCollector to be "safe"
a. 0/15 Jotti scanners detected malware in SpotCollector.exe or SC_WSJTX.exe
b. 0/70 VirusTotal scanners detected malware in SpotCollector.exe and 1/68 detected malware in SC_WSJTX.exe; I consider the
latter to be a false positive.
c. SpotCollector.exe and SC_WSJTX.exe have been submitted to Microsoft and found free of malware. Updated definitions for Windows
Defender are available here:
<https://www.microsoft.com/en-us/wdsi/definitions>
5. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>
6. After upgrading, to revert to the previous version of SpotCollector, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>
SpotCollector 8.7.3 is available via the DXLab Launcher, and via
<http://www.dxlabsuite.com/download.htm>
73,
Dave, AA6YQ

Before installing or upgrading to Commander 14.6.5 ...

Dave AA6YQ
 

If you are using Window Defender Antivirus (Windows 10), update it to its latest malware definition in

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

before installing or upgrading to Commander 14.6.5

73,

Dave, AA6YQ

Commander 14.6.5 is available

Dave AA6YQ
 

This release

- doesn't issue a <RadioInfo> UDP message if the receive frequency is 0, meaning "frequency not yet received from radio" (tnx to
Larry K8UT)

- when directed by an external application to change mode, doesn't send CAT commands to the radio if the radio is already in the
specified mode

- supports the Icom IC-705 transceiver


Notes

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

- 1 of 70 antivirus scanners accessible via Virus Total detected malware <https://www.virustotal.com/gui/home/upload> (Windows
Defender subsequently reported the executable to be free of malware)

- 0 of 15 antivirus scanners accessible via Jotti detected malware <https://virusscan.jotti.org/>

- submitted for online analysis by Microsoft Windows Defender: no malware detected


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 Commander, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>



Commander 14.6.5 is available via the DXLab Launcher and via

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

73,

Dave, AA6YQ

Re: SpotCollector 8.7.3 is available

Dave AA6YQ
 

+ AA6YQ comments below

Another dumb one coming up ... your release notes on SC include this:

- when a K1JT-mode Spot Database Entry is double-clicked, directs WSTX-J to populate its "DX Call" with the callsign, and generate standard messages for that callsign (tnx to John W1JA)

Is it possible that by "WSTX-J", you meant "WSJT-X" ?

+ Yes, that's a typographical error.

And if that's true, I can't seem to get it to work. I've enabled WSJT-X in SC's config, set the port to WSJT-X's 2334 but it won't connect. I have Laurie's new JTAlert version running which supports multicast so it shouldn't be interfering, right ?

+ No, that's not correct. Either use JT-Alert, or use DXLab's direct interoperation with WSJT-X.

+ Step-by-step instructions for the latter are here:

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

73,

Dave, AA6YQ

Re: SpotCollector 8.7.3 is available

Russ Ravella
 

Hi Dave,

Another dumb one coming up ... your release notes on SC include this:

- when a K1JT-mode Spot Database Entry is double-clicked, directs WSTX-J to populate its "DX Call" with the callsign, and generate
standard messages for that callsign (tnx to John W1JA)

Is it possible that by "WSTX-J", you meant "WSJT-X" ?  And if that's true, I can't seem to get it to work.  I've enabled WSJT-X in SC's config, set the port to WSJT-X's 2334 but it won't connect.  I have Laurie's new JTAlert version running which supports multicast so it shouldn't be interfering, right ?

Thanks as always,
Russ, KR6W 

Re: Commander Config Window problem

Dave AA6YQ
 

* More AA6YQ comments below

OK…I figured it out…

It is a program I have called Dimension 4 that remembers windows positions and sizes…….some home the window height was messed up…

* Dimension 4 doesn't mention any ability to manage window positions and sizes:

<http://www.thinkman.com/dimension4/features.htm>

+ Are you sure it's the culpable application?

      73,

             Dave, AA6YQ

Re: SpotCollector 8.7.3 is available

Steve - N3SL
 

My bad.  I didn't realize the 04-11 version was the downloaded version.  I have since changed the name completely....  Sorry for the bandwidth.


On Wed, Aug 12, 2020 at 5:08 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Is it now "reasonable" to change the BandModes file entry for 14.080 to FT4? 

+ That's your decision.

And I'm not quite sure how my edited file - identified within SpotCollector as the source file - gets changed with an upgrade to SpotCollector.  The file name is something I assigned and NOT a default.

+ The SpotCollector update includes a sub-band definition file named

BandModes 2020-04-11.txt

+ The upgrade procedure does not change any of SpotCollector's settings, which are stored in the Windows Registry; the upgrade provides an updated SpotCollector.exe file and updated documentation files.

+ What pathname have you specified in the "Sub-band Definition" panel at the bottom of the Configuration window's General tab?

      73,

             Dave, AA6YQ






Re: Commander Config Window problem

Dave AA6YQ
 

+ AA6YQ comments below

OK…I figured it out…

It is a program I have called Dimension 4 that remembers windows positions and sizes…….some home the window height was messed up…

+ I wasn't aware that Dimension 4 could adversely impact the windows of other applications. Thanks for letting me know, Tim!

73,

Dave, AA6YQ

Re: SpotCollector 8.7.3 is available

w6de
 

RTTY may be the primary Mode for that band segment. But, it has been captured by FT4 users on a day-to-day usage. Band Modes are thrown out the window in almost all International contests. I have a separate BandMode file for contests. And another BandMode file every day practical use--that matches common use.

Dave, w6de

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Joe Subich, W4TV
Sent: 12 August, 2020 22:02
To: DXLab@groups.io
Subject: Re: [DXLab] SpotCollector 8.7.3 is available



On 2020-08-12 5:17 PM, Steve - N3SL wrote:
Is it now "reasonable" to change the BandModes file entry for 14.080
to FT4?
No. RTTY is still the primary mode in 14.080-14.095 (where the
automatic data garbage generators start) - particularly during
contest weekends and DXpeditions.

73,

... Joe, W4TV


On 2020-08-12 5:17 PM, Steve - N3SL wrote:
Is it now "reasonable" to change the BandModes file entry for 14.080 to
FT4? And I'm not quite sure how my edited file - identified within
SpotCollector as the source file - gets changed with an upgrade to
SpotCollector. The file name is something I assigned and NOT a default.

On Wed, Aug 12, 2020 at 2:53 PM Dave AA6YQ <@AA6YQ> wrote:

If you are using Windows Defender anti-malware, direct it to update its
definitions from

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

before you install SpotCollector 8.7.3. The executables in this version
have been submitted to Microsoft for analysis and declared
free of malware. In theory, Window Defender with updated definitions
should not consider them harmful - but I have not tested this.


This release

- detects a conflict in UpdateSpotDatabaseEntryWithSNRPrediction and
automatically retries

- prevents creation of an errorlog.txt entry from
DXCCDatabaseModule.GetOriginStringList when the spotter's callsign is less
than 2
characters in length (tnx to Wolf DK1FW)

- tolerates a spot whose date and time are more than 22 days before or
after the current date (tnx to Franco F6GCP)

- when a K1JT-mode Spot Database Entry is double-clicked, directs WSTX-J
to populate its "DX Call" with the callsign, and generate
standard messages for that callsign (tnx to John W1JA)

- adds a POTA field that is populated with the Parks on the Air code
extracted from spot notes and conveys this information to
DXKeeper (15.7.1 or later) and WinWarbler (9.2.9 or later) when a Spot
Database Entry is double-clicked (tnx to Tom NQ7R)

- adds a SOTA field that is populated with the Summits on the Air code
extracted from spot notes and conveys this information to
DXKeeper (15.7.1 or later) and WinWarbler (9.2.9 or later) when a Spot
Database Entry is double-clicked (tnx to Kent N6WT)

- adds a WWFF field that is populated with the Worldwide Flora & Fauna
area code extracted from spot notes and conveys this
information to DXKeeper (15.7.1 or later) and WinWarbler (9.2.9 or later)
when a Spot Database Entry is double-clicked (tnx to Stan
KM4HQE and Mike W0MU)

- updates the index.htm and SpotDatabase.htm documentation files


Notes:

1. When you double-click a Spot Database Entry whose POTA field specifies
a Parks on the Air code with DXKeeper (version 15.7.1 or
later) running, then contents of the POTA field will be placed in the
Capture window's User-defined item whose caption is POTA

2. When you double-click a Spot Database Entry whose SOTA field specifies
a Summits on the Air code with DXKeeper (version 15.7.1 or
later) running, then contents of the SOTA field will be placed in the
Capture window's SOTA item

3. When you double-click a Spot Database Entry whose WWFF field specifies
a Worldwide Flora and Fauna code with DXKeeper (version
15.7.1 or later) running, then contents of the WWFF field will be placed
in the Capture window's User-defined item whose caption is
WWFF

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

a. 0/15 Jotti scanners detected malware in SpotCollector.exe or
SC_WSJTX.exe

b. 0/70 VirusTotal scanners detected malware in SpotCollector.exe and
1/68 detected malware in SC_WSJTX.exe; I consider the
latter to be a false positive.

c. SpotCollector.exe and SC_WSJTX.exe have been submitted to Microsoft
and found free of malware. Updated definitions for Windows
Defender are available here:

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

5. If this upgrade doesn't work correctly, see the "After an Upgrade"
section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>

6. After upgrading, to revert to the previous version of SpotCollector, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>



SpotCollector 8.7.3 is available via the DXLab Launcher, and via

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


73,

Dave, AA6YQ






Re: SpotCollector 8.7.3 is available

Dave AA6YQ
 

+ AA6YQ comments below

Is it now "reasonable" to change the BandModes file entry for 14.080 to FT4?

+ That's your decision.

And I'm not quite sure how my edited file - identified within SpotCollector as the source file - gets changed with an upgrade to SpotCollector. The file name is something I assigned and NOT a default.

+ The SpotCollector update includes a sub-band definition file named

BandModes 2020-04-11.txt

+ The upgrade procedure does not change any of SpotCollector's settings, which are stored in the Windows Registry; the upgrade provides an updated SpotCollector.exe file and updated documentation files.

+ What pathname have you specified in the "Sub-band Definition" panel at the bottom of the Configuration window's General tab?

73,

Dave, AA6YQ

Re: SpotCollector 8.7.3 is available

Joe Subich, W4TV
 

On 2020-08-12 5:17 PM, Steve - N3SL wrote:
Is it now "reasonable" to change the BandModes file entry for 14.080
to FT4?
No. RTTY is still the primary mode in 14.080-14.095 (where the
automatic data garbage generators start) - particularly during
contest weekends and DXpeditions.

73,

... Joe, W4TV


On 2020-08-12 5:17 PM, Steve - N3SL wrote:
Is it now "reasonable" to change the BandModes file entry for 14.080 to
FT4? And I'm not quite sure how my edited file - identified within
SpotCollector as the source file - gets changed with an upgrade to
SpotCollector. The file name is something I assigned and NOT a default.
On Wed, Aug 12, 2020 at 2:53 PM Dave AA6YQ <@AA6YQ> wrote:

If you are using Windows Defender anti-malware, direct it to update its
definitions from

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

before you install SpotCollector 8.7.3. The executables in this version
have been submitted to Microsoft for analysis and declared
free of malware. In theory, Window Defender with updated definitions
should not consider them harmful - but I have not tested this.


This release

- detects a conflict in UpdateSpotDatabaseEntryWithSNRPrediction and
automatically retries

- prevents creation of an errorlog.txt entry from
DXCCDatabaseModule.GetOriginStringList when the spotter's callsign is less
than 2
characters in length (tnx to Wolf DK1FW)

- tolerates a spot whose date and time are more than 22 days before or
after the current date (tnx to Franco F6GCP)

- when a K1JT-mode Spot Database Entry is double-clicked, directs WSTX-J
to populate its "DX Call" with the callsign, and generate
standard messages for that callsign (tnx to John W1JA)

- adds a POTA field that is populated with the Parks on the Air code
extracted from spot notes and conveys this information to
DXKeeper (15.7.1 or later) and WinWarbler (9.2.9 or later) when a Spot
Database Entry is double-clicked (tnx to Tom NQ7R)

- adds a SOTA field that is populated with the Summits on the Air code
extracted from spot notes and conveys this information to
DXKeeper (15.7.1 or later) and WinWarbler (9.2.9 or later) when a Spot
Database Entry is double-clicked (tnx to Kent N6WT)

- adds a WWFF field that is populated with the Worldwide Flora & Fauna
area code extracted from spot notes and conveys this
information to DXKeeper (15.7.1 or later) and WinWarbler (9.2.9 or later)
when a Spot Database Entry is double-clicked (tnx to Stan
KM4HQE and Mike W0MU)

- updates the index.htm and SpotDatabase.htm documentation files


Notes:

1. When you double-click a Spot Database Entry whose POTA field specifies
a Parks on the Air code with DXKeeper (version 15.7.1 or
later) running, then contents of the POTA field will be placed in the
Capture window's User-defined item whose caption is POTA

2. When you double-click a Spot Database Entry whose SOTA field specifies
a Summits on the Air code with DXKeeper (version 15.7.1 or
later) running, then contents of the SOTA field will be placed in the
Capture window's SOTA item

3. When you double-click a Spot Database Entry whose WWFF field specifies
a Worldwide Flora and Fauna code with DXKeeper (version
15.7.1 or later) running, then contents of the WWFF field will be placed
in the Capture window's User-defined item whose caption is
WWFF

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

a. 0/15 Jotti scanners detected malware in SpotCollector.exe or
SC_WSJTX.exe

b. 0/70 VirusTotal scanners detected malware in SpotCollector.exe and
1/68 detected malware in SC_WSJTX.exe; I consider the
latter to be a false positive.

c. SpotCollector.exe and SC_WSJTX.exe have been submitted to Microsoft
and found free of malware. Updated definitions for Windows
Defender are available here:

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

5. If this upgrade doesn't work correctly, see the "After an Upgrade"
section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>

6. After upgrading, to revert to the previous version of SpotCollector, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>



SpotCollector 8.7.3 is available via the DXLab Launcher, and via

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


73,

Dave, AA6YQ




Re: SpotCollector 8.7.3 is available

w6de
 

The BandMode you are currently using is indicated, and changeable, in SpotCollector | SpotCollector Configuration | General tab | Sub-band Definition (near bottom of window).  Click select to navigate to the file you have entered your custom definitions.

 

It is probably easiest to copy the existing BandMode.txt save it as a new file with a new name (e.g., BandModes 2020-04-11) then edit your changes into your new file.  Then follow the above procedure to select your new file.

 

73,

Dave, w6de

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Steve - N3SL
Sent: 12 August, 2020 21:17
To: DXLab@groups.io
Subject: Re: [DXLab] SpotCollector 8.7.3 is available

 

Is it now "reasonable" to change the BandModes file entry for 14.080 to FT4?  And I'm not quite sure how my edited file - identified within SpotCollector as the source file - gets changed with an upgrade to SpotCollector.  The file name is something I assigned and NOT a default.

 

On Wed, Aug 12, 2020 at 2:53 PM Dave AA6YQ <aa6yq@...> wrote:

If you are using Windows Defender anti-malware, direct it to update its definitions from

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

before you install SpotCollector 8.7.3. The executables in this version have been submitted to Microsoft for analysis and declared
free of malware. In theory, Window Defender with updated definitions should not consider them harmful - but I have not tested this.


This release

- detects a conflict in UpdateSpotDatabaseEntryWithSNRPrediction and automatically retries

- prevents creation of an errorlog.txt entry from DXCCDatabaseModule.GetOriginStringList when the spotter's callsign is less than 2
characters in length (tnx to Wolf DK1FW)

- tolerates a spot whose date and time are more than 22 days before or after the current date (tnx to Franco F6GCP)

- when a K1JT-mode Spot Database Entry is double-clicked, directs WSTX-J to populate its "DX Call" with the callsign, and generate
standard messages for that callsign (tnx to John W1JA)

- adds a POTA field that is populated with the Parks on the Air code extracted from spot notes and conveys this information to
DXKeeper (15.7.1 or later)  and WinWarbler (9.2.9 or later) when a Spot Database Entry is double-clicked (tnx to Tom NQ7R)

- adds a SOTA field that is populated with the Summits on the Air code extracted from spot notes and conveys this information to
DXKeeper (15.7.1 or later)  and WinWarbler (9.2.9 or later) when a Spot Database Entry is double-clicked (tnx to Kent N6WT)

- adds a WWFF field that is populated with the Worldwide Flora & Fauna area code extracted from spot notes and conveys this
information to DXKeeper (15.7.1 or later)  and WinWarbler (9.2.9 or later) when a Spot Database Entry is double-clicked (tnx to Stan
KM4HQE and Mike W0MU)

- updates the index.htm and SpotDatabase.htm documentation files


Notes:

1. When you double-click a Spot Database Entry whose POTA field specifies a Parks on the Air code with DXKeeper (version 15.7.1 or
later) running, then contents of the POTA field will be placed in the Capture window's User-defined item whose caption is POTA

2. When you double-click a Spot Database Entry whose SOTA field specifies a Summits on the Air code with DXKeeper (version 15.7.1 or
later) running, then contents of the SOTA field will be placed in the Capture window's SOTA item

3. When you double-click a Spot Database Entry whose WWFF field specifies a Worldwide Flora and Fauna code with DXKeeper (version
15.7.1 or later) running, then contents of the WWFF field will be placed in the Capture window's User-defined item whose caption is
WWFF

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

   a. 0/15 Jotti scanners detected malware in SpotCollector.exe or SC_WSJTX.exe

   b. 0/70 VirusTotal scanners detected malware in SpotCollector.exe and 1/68 detected malware in SC_WSJTX.exe; I consider the
latter to be a false positive.

   c. SpotCollector.exe and SC_WSJTX.exe have been submitted to Microsoft and found free of malware. Updated definitions for Windows
Defender are available here:

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

5. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>

6. After upgrading, to revert to the previous version of SpotCollector, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>



SpotCollector 8.7.3 is available via the DXLab Launcher, and via

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


      73,

               Dave, AA6YQ



Re: QSO Selection for QSLing

Dave AA6YQ
 

+ AA6YQ comments below

Thanks! I figured there must be ways to do it!!!

+ There are often multiple ways to do things in DXKeeper. Joe W4TV's recommendation was better than mine.

73,

Dave, AA6YQ