Date   

Lost control wioth logging from WSJT-X

Knut Meland
 

I occasionally have problems with logging from WSJT-X (FT8/FT4) into DXKeeper.
Usually the call I just worked remains in the filter (lower line in DXKeeper Log window.) When e new call comes up in WSJT-X, it replaces the old call in the filter. That is normal. But now it refuses to do so. The old call still is in the filter.
Trying to erase the old call does not help. 
When I log in WSJT-X, the QSO does not appear in DXKeeper.
Then I manually log the QSO using Capture window.
This results in double or triple entries in DXKeeper.
I feel that I have lost control with this logging procedure.
I have not made any changes in my seup.
Commander, DXKeeper and Sport Collector are all updated an latest version.
Windows 10 latest update.
73 de Knut LA9RY


Re: Where is FD section supposed to go, and why doesn't it get logged from WSJT-X

Derek Chauran
 

Aha, that may be the missing key, I will try and get back to you!


Re: Where is FD section supposed to go, and why doesn't it get logged from WSJT-X

Derek Chauran
 

Thanks, I have seen the info on modifying QSOs, but each QSO for FD has a different combination of class and section, so I can't really bulk edit them, I have to go 1 at a time.

I have also read the info on logging for FD which doesn't have a suggestion as to where to store the FD specific info (again, I like my logs to be accurate and consistent. When I enable contest mode, the second I enter the call and hit tab it auto populates everything, without the info I need for the contest (my tx entered in the contest info doesn't seem to go anywhere) saves the QSO, and starts a new log. I then have to delete the new log, unlock the QSO for editing and enter the data I was trying to capture, or remember  that the workflow is different, don't hit tab. Except if i want the time logged accurately (I'm anal about my logs) I have to note that time, enter the call, enter the exchange, then go back to the call, hit tab or it won't let me enter the time, go back and delete the new log it auto creates, and then edit the old log time to the correct time.

As far as  I can tell, WSJT-X and JTAlert are sending the info 3 times, and 1 of those 3 contains the full info, and that doesn't get logged anywhere:



Thanks,
Derek


Re: Where is FD section supposed to go, and why doesn't it get logged from WSJT-X

HamApps Support (VK3AMA)
 

On 28/06/2020 7:09 am, Derek Chauran wrote:
it doesn't seem to get logged anywhere when using JTAlert

Have you enabled the logging of Contest Exchanges in JTAlert?
You need to enable the "Log WSJT-X Contest Exchanges" option in the JTAlert Settings, Logging section. You will need to scroll the "Logging Options" check-boxes display down to reveal the checkbox for this option, it is 4th from the bottom.

Also, WSJT-X needs to be in Contest mode AND you have to use Tab 1.

de Laurie VK3AMA


Re: Where is FD section supposed to go, and why doesn't it get logged from WSJT-X

Dave AA6YQ
 

+ AA6YQ comments below

I'm pretty confused about using DXKeeper for FD. Using WSJT-X/JTAlert/DXKeeper, I am not sure where in DXKEEPER I should be putting the section info, and it doesn't seem to get logged anywhere when using JTAlert.

+ When you log QSOs via JTAlert, DXKeeper records the information it receives from JTAlert.

Given that it's painfully slow to edit entries in DXKeeper, I am very worried that I will have to go back and hand edit them all.

+ It's painfully slow to edit entries in DXKeeper? You could insert your section in to the RX# item of ten thousand logged Field Day QSOs in ten seconds:

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

+ For Field Day QSOs logged from DXKeeper, see

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

73,

Dave, AA6YQ


Re: Pathfinder Lookup Errors

Dave AA6YQ
 

+ AA6YQ comments below

Not all the time but enough to be a nuisance, when I enter a call sign in DXKeeper capture window and hit Enter, I get either
- a small window saying Call sign not found even though the lookup info is entered in the Capture window and shows in the Pathfinder window

+ What's an example of a callsign that produces the above behavior?

- OR I get a msg saying "An error has occurred in the Script on this page"
- More often it is the msg about a script error that appears in the Pathfinder page. Sometimes if I select either Y or N on that error page and hit lookup again, the lookup succeeds

In the Pathfinder Config page - I am running IE v11 and have checked hide errors -but still seeing them

+ Pathfinder is a thin veneer over Internet Explorer. If you followed the directions in

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

+ but the "hide script error notification" setting is being ignored, that's a defect in Internet Explorer.

73,

Dave, AA6YQ


Where is FD section supposed to go, and why doesn't it get logged from WSJT-X

Derek Chauran
 

I'm pretty confused about using DXKeeper for FD. Using WSJT-X/JTAlert/DXKeeper, I am not sure where in DXKEEPER I should be putting the section info, and it doesn't seem to get logged anywhere when using JTAlert. Given that it's painfully slow to edit entries in DXKeeper, I am very worried that I will have to go back and hand edit them all.

tnx 73
af7ux


Pathfinder Lookup Errors

w2eck
 

Not all the time but enough to be a nuisance, when I  enter a call sign in DXKeeper capture window and hit Enter, I get either
- a small window saying Call sign not found even though the lookup info is entered in the Capture window and shows in the Pathfinder window
- OR I get a msg saying "An error has occurred in the Script on this page"
- More often it is the msg about a script error that appears in the Pathfinder page. Sometimes if I select either Y or N on that error page and hit lookup again,  the lookup succeeds

In the Pathfinder Config page - I am running IE v11 and have checked hide errors -but still seeing them

Otherwise didn't find anything in the Wiki to match this problem

Tnx & 73
Paul
w2eck


new "Getting Started" article: Pre-filtering the Spot Database

Dave AA6YQ
 


Re: SpotCollector 8.6.9 is available

Dave AA6YQ
 

+ AA6YQ comments below

Updated to 8.6.9 about 5 min ago. (Saturday, 27 June 1715z)

I did not do any special update of Windows Defender, and SpotCollector upgraded just fine, no issues.

I assume that the reason it worked is that I waited about 24 hours from the initial upgrade notice with the Windows Defender warning, and my copy of Defender was/is always as up to date as possible.

+ I don't know how frequently Windows Defender downloads updated malware definitions from

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

+ The Release Note (below) suggests manually directing Windows Defender to perform this update before upgrading.

+ Dave W6DE reported that Windows Defender immediately quarantined early versions of this release; based on your report, Hasan, it would seem that pre-clearing new application versions with Microsoft is effective. Thanks!

73,

Dave, AA6YQ

On Fri, Jun 26, 2020 at 5:33 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.6.9. 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

- when reporting that the Spot Database file cannot be read, reports the pathname of the Spot Database file (tnx to Pete N4ZR)

- correctly restores the Spot Database Display font size between operating sessions (tnx to Don WB6BEE)

- provides the ability to pre-filter incoming spots by band, mode family, and origin (tnx to Rick K8GI, Rick WR0H, Rod W7ZRC, Björn
SM7IUN, and Ian VK6DW)

- increases the size of the buffer used for UDP messages from WSJT-X (tnx to Joe KC2TN and Bill G4WJS)

- saves changes to the WSJT-X UDP port between operating sessions

- correctly sets a Spot Database Entry's DXGridSource item when configured to inspect spot notes, but the spot notes don't specify
a grid square (tnx to Iain N6ML)

- correctly identifies WSJT-X windows so they can be "raised" (tnx to Steve W5GP)

- prevents the incorrect display of the "No Spot Database specified; spots will not be collected" message on shutdown (tnx to
Franco 3A2MW)

- reduces the impact on interactive responsiveness with the "Enable SNR & Probability prediction" option enabled

- updates each Spot Database Entry's OMDX field when recomputing

- provides a "Discard spots from spotting stations callsigns ending in -@" option on the Configuration window's "Special Callsigns"
tab (tnx to George AT6C and Iain N6ML)

- accepts decoded MSK144 and WSPR callsigns from WSJT-X (tnx to Hasan N0AN)

- with the Lookup option enabled in the WSJT-X panel on the Configuration window's "Spot Sources" tab, when the contents of the
WSJT-X "DX Call" textbox transitions from more than one character to no characters, directs DXKeeper to remove the Log Page Display
filter

- provides an SC_WSJTX.exe bridge application that compensates for the retraction of WSJT-X "Highlight Callsigns in all decoding
periods" functionality (tnx to Bill G4WJS and Dave W6DE for their help with testing)

- adds the Prefiltering.htm documentation file

- updates the ConfigurationDatabase.htm, ConfigurationSources.htm, ConfigurationSpecialCallsigns.htm, index.htm, SpotDatabase.htm,
SourceConnection.htm, and WebBrowser.htm documentation files


Notes:

1. To pre-filter by band, mode, or origin, click the new Pre-filter button in the lower-right corner of the Configuration window's
"Spot Database" tab; information from spots discarded by pre-filtering is not added to the Spot Database.

2. When the Enable box is checked in the WSJT-X panel on the Configuration window's "Spot Sources" tab, SpotCollector starts am
included bridge application called SC_WSJTX that closely interacts with WSJT-X in order to color-code information displayed in the
WSJT-X "Band Activity" panel.

a. Callsigns decoded for the first time may require multiple seconds to be color-coded in the WSJT-X "Band Activity" panel for
need and LoTW/eQSL participation; subsequent decodings should be immediately color-coded

a. When running, SC_WSJTX displays a bridge icon in the Windows Task Bar

b. SC_WSJTX displays small window displaying its connection status with SpotCollector and WSJT-X, its version number, and a
Dismiss button

i. clicking the Dismiss button will minimize (hide) the SC_WSJTX window

ii. if dismissed, the SC_WSJTX window will re-appear in "always on top" mode if an error occurs that merits your immediate
attention

c. unchecking the Enable box is checked in the WSJT-X panel on the Configuration window's "Spot Sources" tab or terminating
SpotCollector will automatically terminate the SC_WSJTX bridge application

3. For unknown reasons, when running on Windows 8, depressing the CTRL key while clicking the circular WSJT-X indicator in the Main
window's "Spot source status" panel does not raise the WSJT-X Main and "Wide graph" windows; this function works correctly on
Windows 7 and Windows 10.

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/71 VirusTotal scanners detected malware in SpotCollector.exe and 2/72 (including Windows Defender) detected malware in
SC_WSJTX.exe; I consider the latter to be false positives.

c. SpotCollector.exe and SC_WSJTX.exe have both 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.6.9 is available via the DXLab Launcher, and via

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


73,

Dave, AA6YQ








<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>


Re: SpotCollector 8.6.9 is available

Hasan Schiers N0AN
 

Updated to 8.6.9 about 5 min ago. (Saturday, 27 June 1715z)

I did not do any special update of Windows Defender,  and SpotCollector upgraded just fine, no issues.

I assume that the reason it worked is that I waited about 24 hours from the initial upgrade notice with the Windows Defender warning,  and my copy of Defender was/is always as up to date as possible.

As always, Dave, much appreciated including the msk144 note.

73, N0AN

Hasan


On Fri, Jun 26, 2020 at 5:33 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.6.9. 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

 - when reporting that the Spot Database file cannot be read, reports the pathname of the Spot Database file (tnx to Pete N4ZR)

 - correctly restores the Spot Database Display font size between operating sessions (tnx to Don WB6BEE)

 - provides the ability to pre-filter incoming spots by band, mode family, and origin (tnx to Rick K8GI, Rick WR0H, Rod W7ZRC, Björn
SM7IUN, and Ian VK6DW)

 - increases the size of the buffer used for UDP messages from WSJT-X (tnx to Joe KC2TN and Bill G4WJS)

 - saves changes to the WSJT-X UDP port between operating sessions

 - correctly sets a Spot Database Entry's DXGridSource item when configured to inspect spot notes, but the spot notes don't specify
a grid square (tnx to Iain N6ML)

 - correctly identifies WSJT-X windows so they can be "raised" (tnx to Steve W5GP)

 - prevents the incorrect display of the "No Spot Database specified; spots will not be collected" message on shutdown (tnx to
Franco 3A2MW)

 - reduces the impact on interactive responsiveness with the "Enable SNR & Probability prediction" option enabled

 - updates each Spot Database Entry's OMDX field when recomputing

 - provides a "Discard spots from spotting stations callsigns ending in -@" option on the Configuration window's "Special Callsigns"
tab (tnx to George AT6C and Iain N6ML)

 - accepts decoded MSK144 and WSPR callsigns from WSJT-X (tnx to Hasan N0AN)

 - with the Lookup option enabled in the WSJT-X panel on the Configuration window's "Spot Sources" tab, when the contents of the
WSJT-X "DX Call" textbox transitions from more than one character to no characters, directs DXKeeper to remove the Log Page Display
filter

 - provides an SC_WSJTX.exe bridge application that compensates for the retraction of WSJT-X "Highlight Callsigns in all decoding
periods" functionality (tnx to Bill G4WJS and Dave W6DE for their help with testing)

 - adds the Prefiltering.htm documentation file

 - updates the ConfigurationDatabase.htm, ConfigurationSources.htm, ConfigurationSpecialCallsigns.htm, index.htm, SpotDatabase.htm,
SourceConnection.htm, and WebBrowser.htm documentation files


Notes:

1. To pre-filter by band, mode, or origin, click the new Pre-filter button in the lower-right corner of the Configuration window's
"Spot Database" tab; information from spots discarded by pre-filtering is not added to the Spot Database.

2. When the Enable box is checked in the WSJT-X panel on the Configuration window's "Spot Sources" tab, SpotCollector starts am
included bridge application called SC_WSJTX that closely interacts with WSJT-X in order to color-code information displayed in the
WSJT-X "Band Activity" panel.

   a. Callsigns decoded for the first time may require multiple seconds to be color-coded in the WSJT-X "Band Activity" panel for
need and LoTW/eQSL participation; subsequent decodings should be immediately color-coded

   a. When running, SC_WSJTX displays a bridge icon in the Windows Task Bar

   b. SC_WSJTX displays small window displaying its connection status with SpotCollector and WSJT-X, its version number, and a
Dismiss button

      i. clicking the Dismiss button will minimize (hide) the SC_WSJTX window

      ii. if dismissed, the SC_WSJTX window will re-appear in "always on top" mode if an error occurs that merits your immediate
attention

   c. unchecking the Enable box is checked in the WSJT-X panel on the Configuration window's "Spot Sources" tab or terminating
SpotCollector will automatically terminate the SC_WSJTX bridge application

3. For unknown reasons, when running on Windows 8, depressing the CTRL key while clicking the circular WSJT-X indicator in the Main
window's "Spot source status" panel does not raise the WSJT-X Main and "Wide graph" windows; this function works correctly on
Windows 7 and Windows 10.

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/71 VirusTotal scanners detected malware in SpotCollector.exe and 2/72 (including Windows Defender) detected malware in
SC_WSJTX.exe; I consider the latter to be false positives.

   c. SpotCollector.exe and SC_WSJTX.exe have both 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.6.9 is available via the DXLab Launcher, and via

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


      73,

               Dave, AA6YQ





Re: SpotCollector 8.6.9 is available

Dave AA6YQ
 

+ AA6YQ comments below

On Sat, Jun 27, 2020 at 09:04 AM, iain macdonnell - N6ML wrote:

Is there a place to enable prefiltering of the SC database? I assume this means incoming spots not meeting the criteria are discarded, correct?
Read the notes in Dave's announcement (all the way to the end). It's
all explained there.

+ The reference documentation is here:

<https://www.dxlabsuite.com/spotcollector/Help/Prefiltering.htm>

      73,

            Dave, AA6YQ


Re: SpotCollector 8.6.9 is available

iain macdonnell - N6ML
 

On Sat, Jun 27, 2020 at 5:19 AM Jim Miller, AB3CV <jtmiller47@...> wrote:

Is there a place to enable prefiltering of the SC database? I assume this means incoming spots not meeting the criteria are discarded, correct?
Read the notes in Dave's announcement (all the way to the end). It's
all explained there.

73,

~iain / N6ML


Re: Finding a QSO by QSL#

Charles N2SO
 

Thank you Mike.

On Sat, Jun 27, 2020 at 8:12 AM ND9G Mike <mike.nd9g@...> wrote:
You can use a SQL expression to filter your log.

APP_DXKeeper_QSL_Number=1

Replace the 1 with whichever number you're looking for.

Put that query in the filter textbox at the bottom of the log page display and press Ctrl and S to execute the query.

73,
Mike ND9G


On Sat, Jun 27, 2020 at 6:42 AM Charles N2SO <charlestropp@...> wrote:
Hi,
Is it possible to find a QSO by looking up the specific QSL# assigned to the card?
--
73, Charles N2SO



--
73, Charles N2SO
 

--
73, Charles N2SO


Re: Finding a QSO by QSL#

ND9G Mike
 

You can use a SQL expression to filter your log.

APP_DXKeeper_QSL_Number=1

Replace the 1 with whichever number you're looking for.

Put that query in the filter textbox at the bottom of the log page display and press Ctrl and S to execute the query.

73,
Mike ND9G


On Sat, Jun 27, 2020 at 6:42 AM Charles N2SO <charlestropp@...> wrote:
Hi,
Is it possible to find a QSO by looking up the specific QSL# assigned to the card?
--
73, Charles N2SO


Finding a QSO by QSL#

Charles N2SO
 

Hi,
Is it possible to find a QSO by looking up the specific QSL# assigned to the card?
--
73, Charles N2SO


Re: how to setup dxkeeper for arrl fd?

Dave AA6YQ
 

+ AA6YQ comments below

Thanks Dave! I really appreciate it. This is my first FD using DXKeeper, I kept feeling like I was missing something - since many other loggers have explicit fields for this data for the event.

+ The "RX #" item I recommended is DXKeeper's explicitly documented item for logging a received contest exchange. See

<https://www.dxlabsuite.com/dxkeeper/Help/Items.htm#rx%20#>

73,

Dave, AA6YQ


Re: how to setup dxkeeper for arrl fd?

Nicholas K7DSG
 

Thanks Dave! I really appreciate it. This is my first FD using DXKeeper, I kept feeling like I was missing something - since many other loggers have explicit fields for this data for the event. 


Re: how to setup dxkeeper for arrl fd?

Dave AA6YQ
 

+ AA6YQ comments below

I have a more specific question on this topic... Where is the appropriate location to record the received exchange for field day? Comments? I cannot find answer to this question...

+ As stated in

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

"The ARRL does not process submitted logs or "dupe sheets"; they simply seek evidence that the operator made a good faith effort to avoid working and counting dupes"

+ Thus there is no requirement that you record received exchanges. You can log them if you like, wherever and however you like; when logging QSOs with DXKeeper's Capture window, I'd record received exchanges in the Capture window's RX# item.

73,

Dave, AA6YQ


Re: how to setup dxkeeper for arrl fd?

Nicholas K7DSG
 

I have a more specific question on this topic... Where is the appropriate location to record the received exchange for field day? Comments? I cannot find answer to this question...