This release 

- adds a new CQZen field to each Spot Database Entry that indicates whether "CQ WAZ Mixed" is being pursued

- after a WSJT-X restart, ensures that CQs in the "Band Activity" window are correctly colored, if so enabled

- informs the user if a QSO logged via WSJT-X is not added to DXKeeper's log within 15 seconds (tnx to Robie AJ4F)

- recognizes FT4 in spot notes, and adds FT4 to the Mode Filter window

- includes a file named "BandModes 2019-05-02.txt" with FT4 sub-band definitions, as described in the Notes below

- accepts connections from up to 16 instances of WSJT-X, either local instances or instances running on network-connected machines (tnx to Bill G4WJS and Carl WC4H)

- with the WSJT-X spot source configured to direct DXKeeper to lookup a new "DX Call" in WSJT-X, if the WSJT-X "DX Call" is cleared, removes all filtering from DXKeeper's Log Page Display and clears its Filter panel textbox (tnx to Carl WC4H)

- updates the ConfigurationDatabase.htm, ConfigurationNotifications.htm, Configuration Sources, and SpotDatabase.htm documentation files



Notes:


1. The first time you run SpotCollector 8.3.3, you will be prompted to initiate a Recompute so that the new CQZen field will be correctly initialized in each existing Spot Database Entry. 


2. As Bill G4WJS has pointed out, there is no need to specify an IP address in the WSJT-X panel on the "Spot Sources" tab of SpotCollector's Configuration window, so this textbox has been removed.


3. Assuming you've set the WSJT-X panel's Port to 2237 in the WSJT-X panel on the "Spot Sources" tab of SpotCollector's Configuration window, then

- to connect a single local instance of WSJT-X to SpotCollector, set WSJT-X's "UDP Server" to 127.0.0.1 and its "UDP Server port number" to 2237

- to connect a network-connected instance of WSJT-X to SpotCollector, set WSJT-X's "UDP Server" to the IP address of the machine hosting SpotCollector and set WSJT-X's "UDP Server port number" to 2237

- if more than one instance of WSJT-X is running on the same computer, each instance must have distinct IDs; this can be accomplished by specifying a unique "rig name" in a command line used to start WSJT-X, for example:

wsjtx --rig-name=TS2000


4. This version includes a new sub-band definition file 

BandModes 2019-05-02.txt

in which many changes have been made to accomodate sub-bands recommended in the FT4 Protocol document. Before configuring SpotCollector to reference this sub-band definition file via the "Sub-band Definition" panel on the Configuration window's General tab, review the changes in this file; FT4 operations do not appear to be conforming to the recommended sub-bands.


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


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


7. Because of the added CQZen field, after you run SpotCollector 8.3.3, you won't be able to revert to a previous version of SpotCollector without first deleting the Spots.mdb file in SpotCollector's Databases folder.


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


9. Thanks to Chris NJ5N, Björn SM7IUN, Dave W6DE, Ghassan AC2RA, and Carl WC4H for their help in testing this version.


SpotCollector 8.3.4 is available via the DXLab Launcher, and via 

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


      73,

               Dave, AA6YQ