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 9.2.9


This release

- prevents an errorlog.txt entry "SpotDatabaseUI.SpotGridNeed WAS Need error" (tnx to Earl KD5XB)

- accurately displays the number of entries in the Spot Queue after an overflow occurs (tnx to Björn SM7IUN)

- prevents an erroneous errorlog.txt entry from LogDatabaseModule.Terminate (tnx to Glenn N0VB)

- eliminates the diagnostic display of queued spot database entries in bold font (tnx to Jim AB3CV)

- on the Configuration window's  "Email Alarm" tab, makes the Help button visible (tnx to Joe W4TV)

- retries when LogDatabaseModule.BandWorkedBefore and LogDatabaseModule.ModeWorkedBefore and LogDatabaseModule.BandModeWorkedBefore
are unable to access the current log file (tnx to Bruce K5WBM and Robie AJ4F)

- enables the "double-click on Spot Database Entry for a station operating in a K1JT-mode" functionality to work when DXKeeper is
not running (tnx to Bertel SM6OES)

- responds more rapidly to user actions on the Spot Database Display (tnx to Björn SM7IUN)

- in response to double-clicking a Spot Database Entry whose mode is a K1JT mode, the only behavior that is contingent on
SpotCollector being connected to WSJT-X as a spot source is using the Entry's band to determine to which WSJT-X instance (if there
are more than one) the Entry's Callsign, mode, and gridsquare should be sent (tnx to Joe W4TV)

- in response to double-clicking a Spot Database Entry whose mode is a K1JT mode, compares the Entry's frequency to the lower and
upper bounds for the Entry's band and mode in the selected Sub-band Definition file (tnx to Joe W4TV)

--- if the Entry's frequency is between those bounds, then Commander is directed to QSY to the lower bound

--- if the BandModes.txt file does not specify bounds, or if the Entry's frequency is not between the specified bounds, then
Commander is directed to QSY to the Entry's frequency rounded down to the next lowest 1 kilohertz

- in response to right-clicking a Spot Database Entry whose mode is a K1JT mode and selecting the QSY command, SpotCollector
compares the Entry's frequency to the lower and upper bounds for the Entry's band and mode in the selected Sub-band Definition file
(tnx to Joe W4TV)

--- if the Entry's frequency is between those bounds, then Commander is directed to QSY to the lower bound

--- if the BandModes.txt file does not specify bounds, or if the Entry's frequency is not between the specified bounds, then
Commander is directed to QSY to the Entry's frequency rounded down to the next lowest 1 kilohertz

- includes an updated Sub-band Definition file named BandModes 2022-12-06.txt that you can configure SpotCollector to use via the
"Sub-band Definition" panel near the bottom of the General tab of SpotCollector's Configuration window (tnx to Joe W4TV)

- updates the ConfigurationGeneral.htm, ConfigurationSpecialCallsigns.htm, and SpotDatabase.htm documentation files



Notes:

1. Update your firewall and anti-malware applications to consider the new version of SpotCollector.exe to be "safe"

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

b. 0/72 VirusTotal scanners detected malware in SpotCollector.exe

c. 0/15 Jotti scanners detected malware in SC_WSJTX.exe

d. 1/68 VirusTotal scanners detected malware in SC_WSJTX.exe

e. SpotCollector.exe and SC_WSJTX.exe have been submitted to "Microsoft Security Intelligence" and found free of malware.

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



SpotCollector 9.2.9 is available via the DXLab Launcher, and via

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


73,

Dave, AA6YQ

+ AA6YQ comments below:

I have noticed, but can't say exactly when it happened: when I go to the QSL Tab in DXKeeper and accomplish a "Sync LOTW QSO's" and/or a "Sync LOTW QSL's" that I no longer get a display showing the progress. There used to be a template showing the progress while the Sync was taking place. Is this an issue at my end or has there been a change?

+ There has been no change; I just checked, and progress windows are being displayed here during those operations.

+ Might you have moved those progress windows to another monitor or off-screen?

73,

Dave, AA6YQ

+ AA6YQ comments below

Even better would be if a double click would also initiate a tx once the std messages are generated.
I know that there has been some discussions that tx is disabled after a 73 to prevent "roboting".
The way I understand things, this goes for repeated CQ'ing.
Responding to a CQ still involves some action from the operator.
Other software like GridTracker does this, just one click on a, say CQ, and You're on the air.
So I can only imagine that the API would allow for that.

+ When using DXLab's direct interoperation with WSJT-X, double-clicking on a Spot Database Entry for a station operating in a K1JT mode, SpotCollector conveys the callsign, band, and mode to WSJT-X, and  directs Commander to QSY your radio to the base of the appropriate sub-band for that mode; if you depressed the CTRL or ALT keys while double-clicking, it also directs DXView to rotate your antenna to the appropriate short-path or long-path heading, respectively. At that point, you should

1. select the appropriate antenna and adjust your antenna tuner settings

2. determine if you can copy the station

3. select a clear frequency on which to transmit

Bypassing these steps by having SpotCollector direct WSJT-X to immediately begin calling the station on whatever the transmit frequency happens to be selected in WSJT-X without knowing if you can actually decode that station would be highly inappropriate.

       73,

                 Dave, AA6YQ

 

 

Hi Dave, and every one.

Yes, that did it...
WSJT-X is now populated as it should be.
Kind of embarrassing, such an easy "fix".
But I was so focused on Commander, Spot Collector and WSJT-X, so I didn't give DXKeeper any thought.
I wasn't really trying to make or log a QSO, just testing how things work.

But it works OK now.

Even better would be if a double click would also initiate a tx once the std messages are generated.
I know that there has been some discussions that tx is disabled after a 73 to prevent "roboting".
The way I understand things, this goes for repeated CQ'ing.
Responding to a CQ still involves some action from the operator.
Other software like GridTracker does this, just one click on a, say CQ, and You're on the air.
So I can only imagine that the API would allow for that.

But thanks for helping me out here, with what turned out to be a VERY simple matter.
Pure operator failure, like in most other cases.

BR
/Bertel

Thank you Dave for the clarification. I shall proceed down the fldigi route.
73
Steve GJ6WRI

Problem Resolution Summary (thanks Dave!):

I had a defined initial command sequence which set the LED's to a correct initial state which worked correctly. However, some of these LED states were overridden to an incorrect state later.

Dave clarified: + When on the MultiRadio tab of Commander's Configuration window, you click the "User-defined Control Set" panel's Edit button for the currently-selected transceiver, Commander loads each of the User-defined Sequences specified in the Control Set. Any of those User-defined Sequences that have their "LED Display" panel's Enabled box checked will have their LED color set to the value specified in the "LED Display" panel's color selector.

When setting up User-defined Sequences, be sure that any associated LED Display panel's Enabled box is checked (or unchecked) as appropriate and that the LED Display panel's color is set appropriately.

--
73, Norm/KC1BMD

# more AA6YQ comments below

+ Thanks, Bertel. The errorlog you sent me shows that DXKeeper was not running when you double-clicked the entry for a station operating in FT8. Please start DXKeeper; after it's up and running, please try double-clicking on a Spot Database Entry for a station operating in FT8.

# In the next version of SpotCollector, the "double-click on SpotDatabase Entry for a station operating in a K1JT-mode" functionality is available when DXKeeper is not running. The current SpotCollector version's requirement that DXKeeper be running, as described above, is unnecessary.

# Of course DXKeeper must be running if you intend to log a QSO.

      73,

             Dave, AA6YQ

+ AA6YQ comments below

This is in the mail.

+ Thanks, Bertel. The errorlog you sent me shows that DXKeeper was not running when you double-clicked the entry for a station operating in FT8. Please start DXKeeper; after it's up and running, please try double-clicking on a Spot Database Entry for a station operating in FT8.

      73,

               Dave, AA6YQ

+ AA6YQ comments below

I left out steps in my problem description, In detail:

Close DXKeeper  (Spot Collector is not running)

Open DXLauncher

Select the "Config" option on the DXLauncher opening window.

Select "Databases" on the DXLauncher Configuration window.

On the DXLauncher Databases window LOTW shows an available upgrade (date displayed in red)

Select "Upgrade" on the DXLauncher Database window.

A window, DXView Configuration, opens to the Database  option.

Select the LOTW "upgrade" option.

The mouse cursor changes to the hourglass symbol. Depressing the "upgrade" button returns no result.

+ Please do the following:

1. close all applications
2. reboot Windows into "Safe mode with networking"
3. start DXView
4. direct DXView to upgrade the LoTW database

+ What happens?

5. terminate DXView
6. reboot Windows normally

        73,

             Dave, AA6YQ

Bob,

I left out steps in my problem description, In detail:

Close DXKeeper  (Spot Collector is not running)

Open DXLauncher

Select the "Config" option on the DXLauncher opening window.

Select "Databases" on the DXLauncher Configuration window.

On the DXLauncher Databases window LOTW shows an available upgrade (date displayed in red)

Select "Upgrade" on the DXLauncher Database window.

A window, DXView Configuration, opens to the Database  option.

Select the LOTW "upgrade" option.

The mouse cursor changes to the hourglass symbol. Depressing the "upgrade" button returns no result.

+ AA6YQ comments below

I have tried unsuccessfully to log QSOs from DM780 to DXKeeper, using DM780-DXLab Suite Bridge.
Rig control works as expected, but I get an error message I assume from DXKeeper saying "Unable to parse command from DM780"
Is this something that is fixable, or is it because it's not compatible with a windows 11 PC, or perhaps a 64bit device. Or is it because it was for a much earlier release on DM780 pehaps.
Is there another solution that anyone is aware of that allows rig control from DXCommander and logging to DXKeeper?
I fully appreciate I could just export and ADIF, but I'm looking for seamless automation.
Thanking you in advance for your participation

+ Simon HB9DRV, the author of HRD, sold it to set of owners many years ago. Those owners burned their ends of the bridges that Simon and I and I had established between DXLab and HRD. One of those owners subsequently attempted to blackmail me into supporting their demand that HRD have two votes on the ADIF committee; the longstanding principle in that committee has been "one application, one vote. I thus have no interest in repairing or creating any interoperation between DXLab and HRD. 

+ DM780 is largely based on the open source code from FLDigi, which can interoperate with DXLab:

http://www.n2amg.com/software/fldigi-dxlabs-gateway/

       73,

              Dave, AA6YQ

 

Good afternoon OM.
I have tried unsuccessfully to log QSOs from DM780 to DXKeeper, using DM780-DXLab Suite Bridge.
Rig control works as expected, but I get an error message I assume from DXKeeper saying "Unable to parse command from DM780"
Is this something that is fixable, or is it because it's not compatible with a windows 11 PC, or perhaps a 64bit device. Or is it because it was for a much earlier release on DM780 pehaps.
Is there another solution that anyone is aware of that allows rig control from DXCommander and logging to DXKeeper?
I fully appreciate I could just export and ADIF, but I'm looking for seamless automation.
Thanking you in advance for your participation
Steve GJ6WRI

Hi.

This is in the mail.
Hope it helps.

BR
/Bertel

On Mon, Dec 19, 2022 at 12:23 AM, Dave AA6YQ wrote:

+ Please make a screen shot showing Commander's Main window before you click the "User-defined Control Set" panel's Edit button for the currently-selected transceiver. Then click the Edit button, and make another screen shot showing Commander's Main window. Attach both screen shots to an email message, and send the message to me via

aa6yq (at) ambersoft.com

Sent.
 
--
73, Norm/KC1BMD

--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop

On Mon, Dec 19, 2022 at 09:44 AM, Gilbert Baron W0MN wrote:

QRZ sems down this AM

OM, I think you are in the wrong thread :)
 
--
73, Norm/KC1BMD