Date   

Re: Cant Get JTAlert B4 and DXK log in Synch

 

Dave

TU for reply. Not worrying about awards, just trying to get JTAlert /WSJT-X B4 using DXK file as basis consistent. 
As I have told u b4, love DXLab!!!!!!!!!!!!!!!!!

73  Roger N3RC


Re: Cant Get JTAlert B4 and DXK log in Synch

Dave AA6YQ
 

+ AA6YQ comments below

I am running all the DXLab programs, WSJT-X, and JTAlert on vy fast w10 64b computer, all current versions. This may a JTAlert issue but since I am much
more familiar with DXLab thought I would try here first.

My understanding is that when running JTAlert, using DXK for logging, that all B4 lookups use the DXK file ( my case 100k contacts, 5k WSJT-X), and the results are 
color coded and  displayed in the WSJT-X Band Activity window as well as the JTAlert window according to the JTAlert Alert setup. 

I cannot get the WSJT-X main Band Activity window, the JTAlert window and DXKeeper to give same B4 results. Using the DXK file as
the file of record, I often find I have to search DXK to see if a B4 by band/mode is correct and often they are not the same as the WSJT-x
Band Activity window. In all cases they are in DXK but not reflected as B4 in WSJT-X. I have read the JTAlert documentation and have in an effort
to identify the problem have reduced my
Alerts to:  Own Call
                 CQ
                  Worked B4

and still get inconsistent results.  I tried setting JTAlert Alerts/Filters 'Do Not show B4 callsigns"  and still get many B4 errors.

I thought about going back to just using the WSJT-X system using the WSJT-X adif file as fthef ile of record but will miss all the great features
of JT-Alert. If I dont understand this B4 problem there is no use in using the more advanced Alert features of JTAlert.

Anyone got ideas? Probably some of my assumptions are incorrect.

+ JTAlert's award tracking does not using DXLab's Realtime Award Tracking mechanism. I suggest that you describe this issue in the JT-Alert support group.

       73,

             Dave, AA6YQ


Cant Get JTAlert B4 and DXK log in Synch

 

I am running all the DXLab programs, WSJT-X, and JTAlert on vy fast w10 64b computer, all current versions. This may a JTAlert issue but since I am much
more familiar with DXLab thought I would try here first.

My understanding is that when running JTAlert, using DXK for logging, that all B4 lookups use the DXK file ( my case 100k contacts, 5k WSJT-X), and the results are 
color coded and  displayed in the WSJT-X Band Activity window as well as the JTAlert window according to the JTAlert Alert setup. 

I cannot get the WSJT-X main Band Activity window, the JTAlert window and DXKeeper to give same B4 results. Using the DXK file as
the file of record, I often find I have to search DXK to see if a B4 by band/mode is correct and often they are not the same as the WSJT-x
Band Activity window. In all cases they are in DXK but not reflected as B4 in WSJT-X. I have read the JTAlert documentation and have in an effort
to identify the problem have reduced my
Alerts to:  Own Call
                 CQ
                  Worked B4

and still get inconsistent results.  I tried setting JTAlert Alerts/Filters 'Do Not show B4 callsigns"  and still get many B4 errors.

I thought about going back to just using the WSJT-X system using the WSJT-X adif file as fthef ile of record but will miss all the great features
of JT-Alert. If I dont understand this B4 problem there is no use in using the more advanced Alert features of JTAlert.

Anyone got ideas? Probably some of my assumptions are incorrect.

73  Roger N3RC


Re: DXKeeper 15.6.6 is available

Dave AA6YQ
 

+ AA6YQ comments below

Has a side note I was also not able to backup my log file until I compacted it and then backup was achieved and auto backup when

Shutting dxkeeper down worked as it should also. I did not know it had to be compacted and reopen for the program not to have a error file

+ Compaction is not a pre-requisite for backup or for anything else; it reclaims space lost when a significant number of logged QSOs are deleted. Please attach the "error file" to an email message, and send the message to me via

aa6yq (at) ambersoft.com

            73,

                  Dave, AA6YQ


Re: DXKeeper 15.6.6 is available

Jacob Derenne
 

I also had a few issues with the bottom of log window being cutoff from the taskbar setting which was changed with win 10 update and

Had to hide the ask bar, which I usually do or re-size the dxkeeper window

Has a side note I was also not able to backup my log file until I compacted it and then backup was achieved and auto backup when

Shutting dxkeeper down worked as it should also. I did not know it had to be compacted and reopen for the program not to have a error file

 

All is  ok now

Jake – W9BLI

 

Sent from Mail for Windows 10

 

From: Dave AA6YQ
Sent: Friday, June 26, 2020 5:11 PM
To: DXLab@groups.io
Subject: Re: [DXLab] DXKeeper 15.6.6 is available

 

+ AA6YQ comments below

Hi Dave.  I am missing the old bottom line in DXK with fillters. LOTW, etc, etc.

+ Are you reporting that the Filter panel at the bottom of DXKeeper's Main window is missing? If so, please make a screen shot showing DXKeeper's Main window, attach the screen shot to an email message, and send the message to me via

aa6yq (at) ambersoft.com


I am currently running FT8 logging via JTAlert to DXK. DXK sends it to LOTW.  DXK shows the Q as U.

+ Assuming that you're referring to the QSO's "LoTW QSL Rcvd" item, that is correct: a 'U' means "uploaded to LoTW, but not yet accepted".


I do not see how I get display out of LOTW. to display all Q'sI must have done something wrong

+ What does "get display out of LoTW" mean? If you're asking how to view accepted QSOs in LoTW, step-by-step instructions are here:

<https://lotw.arrl.org/lotw-help/view-accepted-qsos/>

+ If you're asking how to update your logged QSO to reflect acceptance by LoTW, do the following on the Main window's QSL tab:

1. set the "QSL Via" panel to LoTW

2. click the "Sync LoTW QSOs" button

+ Note that depending upon the length of LoTW's processing queue, it can take a few minutes (and sometimes longer) for LoTW to accept your QSO after you upload it.

       73,

            Dave, AA6YQ



 


SpotCollector 8.6.9 is available

Dave AA6YQ
 

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: DXKeeper 15.6.6 is available

Dave AA6YQ
 

+ AA6YQ comments below

Hi Dave. I am missing the old bottom line in DXK with fillters. LOTW, etc, etc.

+ Are you reporting that the Filter panel at the bottom of DXKeeper's Main window is missing? If so, please make a screen shot showing DXKeeper's Main window, attach the screen shot to an email message, and send the message to me via

aa6yq (at) ambersoft.com


I am currently running FT8 logging via JTAlert to DXK. DXK sends it to LOTW. DXK shows the Q as U.

+ Assuming that you're referring to the QSO's "LoTW QSL Rcvd" item, that is correct: a 'U' means "uploaded to LoTW, but not yet accepted".


I do not see how I get display out of LOTW. to display all Q'sI must have done something wrong

+ What does "get display out of LoTW" mean? If you're asking how to view accepted QSOs in LoTW, step-by-step instructions are here:

<https://lotw.arrl.org/lotw-help/view-accepted-qsos/>

+ If you're asking how to update your logged QSO to reflect acceptance by LoTW, do the following on the Main window's QSL tab:

1. set the "QSL Via" panel to LoTW

2. click the "Sync LoTW QSOs" button

+ Note that depending upon the length of LoTW's processing queue, it can take a few minutes (and sometimes longer) for LoTW to accept your QSO after you upload it.

73,

Dave, AA6YQ


Re: DXKeeper 15.6.6 is available

Jim Denneny
 

Hi Dave.  I am missing the old bottom line in DXK with fillters. LOTW, etc, etc.  I am currently running FT8 logging via JTAlert to DXK. DXK sends it to LOTW.  DXK shows the Q as U. I do not see how I get display out of LOTW. to display all Q'sI must have done something wrong

73, Jim K7EG


Re: DXView trying to talk to DX Atlas

g4wjs
 

On 25/06/2020 17:07, Dave AA6YQ wrote:
+ AA6YQ comments below

since a few days ago, when I start DXView I get a Dxatlas Automation 
error message box and another saying the DX Atlas trial period has 
expired. This is odd as I don't have DX Atlas integration turned on in 
DXView and have not had that for a couple of Years or so. If I dismiss 
the errors DXView starts normally with its own World Map window that I 
have used for Years.
uninstalling the expired DX Atlas application resolves this issue, although I'm not sure that should be necescary.

+ That's an unfortunate side effect of the interoperation mechanism employed by DX Atlas. Alex VE3NEA, the author of DX Atlas, acknowledges this behavior, but declines to change it.

        73,

                Dave, AA6YQ

Hi Dave and Iain,

thanks for that. I must have re-installed DX Atlas an expiration period ago. I don't recall that, hi hi.


--
73

Bill

G4WJS.


Re: DXView trying to talk to DX Atlas

Dave AA6YQ
 

+ AA6YQ comments below

since a few days ago, when I start DXView I get a Dxatlas Automation
error message box and another saying the DX Atlas trial period has
expired. This is odd as I don't have DX Atlas integration turned on in
DXView and have not had that for a couple of Years or so. If I dismiss
the errors DXView starts normally with its own World Map window that I
have used for Years.
uninstalling the expired DX Atlas application resolves this issue, although I'm not sure that should be necescary.

+ That's an unfortunate side effect of the interoperation mechanism employed by DX Atlas. Alex VE3NEA, the author of DX Atlas, acknowledges this behavior, but declines to change it.

73,

Dave, AA6YQ


Re: DXView trying to talk to DX Atlas

iain macdonnell - N6ML
 

On Thu, Jun 25, 2020 at 7:29 AM g4wjs <bill.8@...> wrote:

On 25/06/2020 15:08, g4wjs wrote:
Hi Dave and all,

since a few days ago, when I start DXView I get a Dxatlas Automation
error message box and another saying the DX Atlas trial period has
expired. This is odd as I don't have DX Atlas integration turned on in
DXView and have not had that for a couple of Years or so. If I dismiss
the errors DXView starts normally with its own World Map window that I
have used for Years.
Hi again Dave and all,

uninstalling the expired DX Atlas application resolves this issue,
although I'm not sure that should be necescary.
Explained here:

https://groups.io/g/DXLab/message/41192

73,

~iain / N6ML


Re: DXView trying to talk to DX Atlas

g4wjs
 

On 25/06/2020 15:08, g4wjs wrote:
Hi Dave and all,

since a few days ago, when I start DXView I get a Dxatlas Automation error message box and another saying the DX Atlas trial period has expired. This is odd as I don't have DX Atlas integration turned on in DXView and have not had that for a couple of Years or so. If I dismiss the errors DXView starts normally with its own World Map window that I have used for Years.
Hi again Dave and all,

uninstalling the expired DX Atlas application resolves this issue, although I'm not sure that should be necescary.



--
73

Bill

G4WJS.


DXView trying to talk to DX Atlas

g4wjs
 

Hi Dave and all,

since a few days ago, when I start DXView I get a Dxatlas Automation error message box and another saying the DX Atlas trial period has expired. This is odd as I don't have DX Atlas integration turned on in DXView and have not had that for a couple of Years or so. If I dismiss the errors DXView starts normally with its own World Map window that I have used for Years.



--
73

Bill

G4WJS.


DXKeeper 15.6.6 is available

Dave AA6YQ
 

This release

- with the "Deduce missing items..." option enabled on the Main window's "Import QSOs" tab, when importing a VE2 QSO that specifies
a grid square but doesn't specify a CQ zone, correctly determines the CQ zone (tnx to Rich VE3KI)

- ignores confirmed satellite QSOs when reporting changes in DXCC award progress in the after-action report generated by "Sync LoTW
QSLs" and "Update from LoTW" (tnx to Dave N9FN)

- correctly processes an LoTW confirmation that specifies more than one grid square (tnx to Iain N6ML)

- extends the Duplicate filter to clear the Select item in all logged QSOs before checking for duplicates among the QSOs in the Log
Page Display

- when the "Sync LoTW QSO" or "Sync LoTW QSL" functions are initiated with the Log Page Display filtered, offers a Cancel option in
the "do you want the filtering removed?" dialog (tnx to Steve K8JQ)

- improves the after-action report generated by the "Update from LoTW" function

- provides a Units panel on its "QSL Configuration" window's Envelopes tab so that you can specify envelope dimensions in
millimeters as well as inches (tnx to Knut LA9RY)

- when generating an IOTA submission, chooses an LoTW-confirmed QSO whose QSO partner submitted IOTA designator matches the IOTA
designator in your logged QSO in preference to an LoTW-confirmed QSO that lacks the IOTA designator match

- provides an EntityCount.txt script that shows the number of logged QSOs with each DXCC entity prefix (tnx to Rich K1HTV)

- updates the FilterLog.htm, Items.htm, Progress.htm, QSL.htm, and QSLConfiguration.htm documentation files


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


DXKeeper 15.6.6 is available via the DXLab Launcher and via

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

73,

Dave, AA6YQ


Re: Ports??

darryl
 

Yep. Posted to the wrong group. Sri. I have posted to the N1mM+ group now.   


Re: Ports??

iain macdonnell - N6ML
 

On Wed, Jun 24, 2020 at 5:39 PM darryl <darryl@...> wrote:
Trying to install N1MM+ on a new(er) computer today. Intel Quad core, 8 Gb RAM, 2 monitors, latest update to Windows 10, latest update to N1MM+.

Using the computer only as a control station with a K3 and Remoterigs to access my remote station.

Problem: after I have the Microbit installer create the necessary virtual ports, I go to config in N1MM+ and the ports do not show up.

Any ideas?
Maybe you could try asking the N1MM group?

73,

~iain / N6ML


Re: Ports??

darryl
 

Numerous times...


Re: Ports??

John Battin
 

Did you reboot the computer ???

 

Sent from Mail for Windows 10

 

From: darryl
Sent: Wednesday, June 24, 2020 7:39 PM
To: DXLab@groups.io
Subject: [DXLab] Ports??

 

Hi All,

Trying to install N1MM+ on a new(er) computer today. Intel Quad core, 8 Gb RAM, 2 monitors, latest update to Windows 10, latest update to N1MM+.

Using the computer only as a control station with a K3 and Remoterigs to access my remote station.

Problem: after I have the Microbit installer create the necessary virtual ports, I go to config in N1MM+ and the ports do not show up.

Any ideas?

Thanks.

Darryl K7UT

 


Ports??

darryl
 

Hi All,

Trying to install N1MM+ on a new(er) computer today. Intel Quad core, 8 Gb RAM, 2 monitors, latest update to Windows 10, latest update to N1MM+.

Using the computer only as a control station with a K3 and Remoterigs to access my remote station.

Problem: after I have the Microbit installer create the necessary virtual ports, I go to config in N1MM+ and the ports do not show up.

Any ideas?

Thanks.

Darryl K7UT


Re: Single QSO - Multiple Grid Confirmation

Dave AA6YQ
 

Thanks for testing and the report, Robie!

73,

Dave, AA6YQ

-----Original Message-----
From: Robie Elms [mailto:ruler55@...]
Sent: Wednesday, June 24, 2020 12:47 PM
To: Dave AA6YQ
Subject: Re: [DXLab] Single QSO - Multiple Grid Confirmation

Dave,

The new version of DXKeeper works properly.

Thanks for the quick resolution of the issue.

Robie - AJ4F