Date   
the next version of SpotCollector will directly interoperate with WSJTX

Dave AA6YQ
 

Re: Cabrillo file for the ARRL RTTY contest

Dave AA6YQ
 

+ AA6YQ comments below


It means that if JTAlert is going to log contest QSOs in a manner that will enable DXKeeper to subsequently generate a
Cabrillo file, JTAlert must log those contest QSOs in the manner described in

JTAlert is not a Contest Logger. It simply acts as logging bridge between WSJT-X and DXKeeper. There are no attempts to validate the
Contest exchange based on different Contest rules or extract data from the Contest exchange. There is no attempt to include missing
data within the exchange. JTAlert is a bridge, it simply passes through the WSJT-X Contest exchange.

If DXKeeper is not utilising a valid Contest exchange for the Contest enabled within DXKeeper, eg. WSJT-X and DXKeeper are both set
for RTTY Roundup, and a valid Roundup Exchange is passed to DXKeeper, unchanged by JTAlert, there is not point in logging the
exchange, IMO.

+ DXKeeper expects the contest exchange to be recorded in the RX# and TX# items. In the case of "RTTY Roundup", that means the QSO
partner's "US State" abbreviation, "Canadian Province" abbreviation, or serial number must be recorded in the QSO's RX# item; this
approach enables RTTY ops to employ the same gestures to capture their QSO partner's exchange independent of their QSO partner's
location. See Note 16 in

<https://www.dxlabsuite.com/dxkeeper/Help/Contesting.htm>

73,

Dave, AA6YQ

Re: JS8CAll to DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

Will the UDP broadcast from JS8Call send log entries to DXKeeper?

+ DXKeeper accepts log directives from other applications via DDE and TCP. If you run the N1MM-DXKeeper gateway, then N1MM-style "log this QSO" messages received via UDP will cause DXKeeper to log the QSO.

+ The next version of SpotCollector has been extended to directly interoperate with WSJTX; this includes the ability to accept a "log this QSO" directive from WSJTX and direct DXKeeper to log the QSO. The primary driver for this direct interoperation is to enable SpotCollector to "color-code" callsigns in WSJTX to reflect "Need" (font color) and participation in eQSL AG and LoTW (background color):

<http://www.dxlabsuite.com/spotcollector/SC-WSJTX.jpg>

+ "Need" is based on DXLab's realtime award tracking.

+ This direct interoperation between SpotCollector and WSJTX can remain disabled by users who prefer to JTAlert.

+ If JS8Call employs the same UDP messages as WSJTX, then further extending SpotCollector to interoperate with it should be straightforward. I'll consider that after development of the next version of SpotCollector is complete, documented, tested, and publicly released.

+ If JS8Call provides the option to log QSOs via N1MM-style UDP messages, then the N1MM-DXKeeper gateway should log QSOs received from JS8Call to DXKeeper -- but I have not tested this. See

<https://www.dxlabsuite.com/N1MM-DXKeeper/index.htm>

73,

Dave, AA6YQ

Re: Cabrillo file for the ARRL RTTY contest

HamApps Support (VK3AMA)
 

On 10/01/2019 8:25 am, Dave AA6YQ wrote:
It means that if JTAlert is going to log contest QSOs in a manner that will enable DXKeeper to subsequently generate a Cabrillo file, JTAlert must log those contest QSOs in the manner described in
JTAlert is not a Contest Logger. It simply acts as logging bridge between WSJT-X and DXKeeper. There are no attempts to validate the Contest exchange based on different Contest rules or extract data from the Contest exchange. There is no attempt to include missing data within the exchange. JTAlert is a bridge, it simply passes through the WSJT-X Contest exchange.

If DXKeeper is not utilising a valid Contest exchange for the Contest enabled within DXKeeper, eg. WSJT-X and DXKeeper are both set for RTTY Roundup, and a valid Roundup Exchange is passed to DXKeeper, unchanged by JTAlert, there is not point in logging the exchange, IMO.

The next release of JTAlert will no longer automatically log Contest exchanges (valid or invalid) to DXKeeper (whether in Contest mode or not). The JTAlert user will need to enable an option to permit logging of these unused (by DXKeeper) Contest exchanges.

de Laurie VK3AMA

Re: Running WAS script for 60m issue

Dave AA6YQ
 

+ AA6YQ comments below

The CFM box does have the "S" for 2 stations I had worked in Wisconsin. The 3rd station I have a QSL card but no LOTW for, which happens to be the first station I had worked in Wisconsin. So that is what the report was seeing and reported that station. I need to make an SQL filter in my script to exclude QSL cards but still show LOTW confirmation if I happen to have both for the same station.

+ DXKeeper's "US States" report reviews every QSO in the Log Page Display with a station in the continental US, Alaska, and Hawaii to find the award-wise "most advanced" QSO with each state; the award status hierarchy is

0. worked but not requested

1. requested but not confirmed

2. confirmed but not submitted for WAS credit

3. submitted for WAS credit but no WAS credit granted

4. WAS credit granted

+ If there are multiple QSOs with a state having the same award status, the first QSO encountered is what will be shown in the report.

+ Note that the letters S or V appearing in the report's "Card Cfm" column refer to DXCC credit, not WAS credit.

+ QSOs are reviewed in the current Log Page Display sort order -- so if you want the report to give preference to LoTW confirmations over QSL card confirmations, add this Sort command to your script between the Filter and Report commands:

Sort APP_DXKEEPER_LOTW_QSLRDATE

+ This works because QSOs not confirmed via LoTW have their "QSL Rcvd Date" items set to 4001-01-01.

73,

Dave, AA6YQ

Re: Running WAS script for 60m issue

Joe Subich, W4TV
 

Jay,

What are you trying to accomplish? If you want to "count" only
those states confirmed by LotW, use the following filter:

filter ((Band = '60m') and (APP_DXKEEPER_LotW_QSL_RCVD in ('Y','S','V')
AND APP_DXKEEPER_CONFIRMATION like '*S*'))

If you want to count those states confirmed by either card or LotW the
DXKeeper "US_States" report is correct - it simply selects the first
(or oldest) confirmation for each state without regard to card or LotW.

US_States does not respect the "VUCC & WAS Submission" selection on
the Awards tab to prioritize cards over LotW or vice versa.

73,

... Joe, W4TV

On 2019-01-10 3:46 PM, Jay KA9CFD via Groups.Io wrote:
The CFM box does have the "S" for 2 stations I had worked in Wisconsin. The 3rd station I have a QSL card but no LOTW for, which happens to be the first station I had worked in Wisconsin. So that is what the report was seeing and reported that station. I need to make an SQL filter in my script to exclude QSL cards but still show LOTW confirmation if I happen to have both for the same station.
73 Jay KA9CFD

JS8CAll to DXKeeper

w2eck
 

Will the UDP broadcast from JS8Call send log entries to DXKeeper? Anyone tried it?

73
Paul
w2eck

Re: found DXLab Launcher latest version

Dave AA6YQ
 

+ AA6YQ comments below

Installed latest version of Launcher.

It will not update or allow configure.

+ Has this always been the case, or is it new behavior?

+ If new behavior, when did it first appear? What changes to your hardware or software did you make around that time?

73,

Dave, AA6YQ

Re: Launcher will not respond to "new app upgrades"

Dave AA6YQ
 

+ AA6YQ comments below

Deleted and reinstalled DXLab Launcher 1.9.7 for the 3rd time. Still no way to get CONFIG or “new app…” to do anything but blink. Will see if uninstall will do better job.

+ Perhaps running your computer through your dishwasher will makes the Launcher's Configuration window appear on screen.

73,

Dave, AA6YQ

Re: Launcher will not respond to "new app upgrades"

Dave AA6YQ
 

+ AA6YQ comments below

No go with any of the instructions noted below. Deleted Launcher and will reinstall.

+ Re-installing will not correct the problem, but could introduce much bigger problems.

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

Hope that will do the job.

+ Where computers are involved, hope is an ineffective strategy.

73,

Dave, AA6YQ

Re: Running WAS script for 60m issue

ART W2NRA
 

I assume you know there is no WAS award for 60 meters.  Right?

73, Art, W2NRA

On Jan 10, 2019, at 8:38 AM, Jay KA9CFD via Groups.Io <ka9cfd@...> wrote:

I am having an issue when running the script I have to check my WAS status on 60 meters. 

The script I am using is this:

filter Band='60m'
report us_states <ReportsFolder>us_states_60.txt

When I run it, it is showing LotW confirmed status for Wisconsin as an "R" for a station that I had worked but had never uploaded to LOTW. However I have worked 2 other Wisconsin stations that have confirmed through LOTW and show their received status as a "Y" in DXKeeper. For some reason the script is not picking it up. Any ideas?

73 Jay KA9CFD

Re: Running WAS script for 60m issue

Jay KA9CFD
 

The CFM box does have the "S" for 2 stations I had worked in Wisconsin. The 3rd station I have a QSL card but no LOTW for, which happens to be the first station I had worked in Wisconsin. So that is what the report was seeing and reported that station. I need to make an SQL filter in my script to exclude QSL cards but still show LOTW confirmation if I happen to have both for the same station.

73 Jay KA9CFD 

Re: Running WAS script for 60m issue

Joe Subich, W4TV
 

Carl,

Your script is not accurate. If a station does not include their
state in their tQSL "Station Location," your script will show
"credit" for and invalid confirmation.

To be correct you need:

filter ((Band = '60m') and (QSL_RCVD in ('Y','S','V') or
(APP_DXKEEPER_LotW_QSL_RCVD in ('Y','S','V') AND
APP_DXKEEPER_CONFIRMATION like '*S*')) and QSO_Begin
> #1975-01-01#)


Jay, take a look at the "CFM" box in the LotW field and make
sure your Wisconsin "confirmations" include the letter "S".

73,

... Joe, W4TV


On 2019-01-10 11:29 AM, Carl - WC4H via Groups.Io wrote:
Try this one Jay.  It works:
filter ( (Band = '60m')) and ((APP_DXKEEPER_LOTW_QSL_RCVD='Y')or(APP_DXKEEPER_LOTW_QSL_RCVD='V')or(APP_DXKEEPER_LOTW_QSL_RCVD='S')) and (QSO_BEGIN > #1975-01-01#)
report us_states <ReportsFolder>60m_WAS.txt
73.
Carl - WC4H

Re: Running WAS script for 60m issue

Carl - WC4H
 

You can just use another/other "and" to include the other status(es) that you want.
Alternatively you can just select all from 60 meters (remove all the "and" criteria).  However, that may not serve you well since you would get dupes.  Either way, you can taylor to what you want.

I would rather have one with confirmed and a separate report with non-confirmed, but that's just a personal preference.

73.
Carl - WC4H

Re: Running WAS script for 60m issue

Jay KA9CFD
 

Hi Dave. I double checked the DXKeeper entry in the Online QSL panel. For example NS9I was worked on 60m FT8 and confirmed via LOTW. The cfm field is showing GMSZ.

But I think I figured out the issue.

The report generator appears to look for any confirmation (card or LOTW) first and lists that station. I happened to have worked N9JIY and have his QSL card but not an LOTW confirmation. He was the first WI station I had worked. The other 2 WI stations that I did get confirmed only LOTW came later. So, I think I need to edit the band filter in the script to exclude card confirmations somehow before the report is run. Then I think it would show up OK for what I was looking for. Hope that makes sense.

73 Jay KA9CFD

found DXLab Launcher latest version

Email Service <jfriend31@...>
 

Installed latest version of Launcher.

 

It will not update or allow configure.

 

I am running Win10 Pro Version 1803 OS build 17134.523

 

On an AMD Ryzen 5 1500X Quad core 3.5 GHz

 

16 GB RAM

 

64 bit OS

 

So far as I can tell all other parts of DXLab are working as they should. I have not run Launcher regularly for some time as last year I ran FT8 almost totally with DXKeeper only. Commander works fine when I use it to read the K3.

 

This is a relatively new problem as the last time I tried to update a few days ago everything updated as expected.

 

The recover instructions did not help as I have no recover source.

 

Sincerely

 

Jack ak7o

 

Sent from Mail for Windows 10

 

Re: DXLab Launcher

ND9G Mike
 


The version available via the download and install link on that page is 197 (or 181 if using an old OS)

73,
Mike ND9G


On Thu, Jan 10, 2019 at 1:47 PM Email Service <jfriend31@...> wrote:

Tried to install Launcher by downloading and the downloads all have …126 behind them.

 

Where can I get the latest DXLab Launcher?

 

Jack ak7o

 

Sent from Mail for Windows 10

 

DXLab Launcher

Email Service <jfriend31@...>
 

Tried to install Launcher by downloading and the downloads all have …126 behind them.

 

Where can I get the latest DXLab Launcher?

 

Jack ak7o

 

Sent from Mail for Windows 10

 

Re: Yesteryears marathon dxkeeper report and query

ghassan chammas
 

Thank you Dave.
It worked perfectly.
Regards
Od5ya
Ghassan



Sent from Samsung tablet.

-------- Original message --------
From: Dave AA6YQ <aa6yq@...>
Date: 09/01/2019 23:51 (GMT+02:00)
To: DXLab@groups.io
Subject: Re: [DXLab] Yesteryears marathon dxkeeper report and query

+ AA6YQ comments below

Hi all.
I submitted my 2018 marathon sheet successfully.
I also set the dxkeeper for 2019, no problem I wanted to go back and use dxkeeper to do some analysis using the 2018 log.
Likecwhat would have been my score had i submitted only phone, or only 40m.etc...i saw that even if change the marathon award setup back to 2018, the report output remains based on 2019.

Is there a way to do thay?

+ Yes. On the Configuration window's Awards tab, click the "Marathon Bands and Modes" panel's "Year, Category, Scoresheet Info" button. In the "Year, Category, Scoresheet Information" window that appears,

1. set the "Current year" to 2018

2. select the "Category" for which you want to see your 2018 score

3. click the Progress button in the "CQ DX Marathon" panel on the Main window's "Check Progress" tab.

       73,

              Dave, AA6YQ




Re: Launcher will not respond to "new app upgrades"

Email Service <jfriend31@...>
 

Deleted and reinstalled DXLab Launcher 1.9.7 for the 3rd time. Still no way to get CONFIG or “new app…” to do anything but blink. Will see if uninstall will do better job.

 

Jack ak7o

 

Sent from Mail for Windows 10

 

From: Email Service
Sent: Thursday, January 10, 2019 12:35 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Launcher will not respond to "new app upgrades"

 

No go with any of the instructions noted below. Deleted Launcher and will reinstall. Hope that will do the job. Also deleted Launcher126.

 

Jack ak7o

 

Sent from Mail for Windows 10

 

From: Dave AA6YQ
Sent: Thursday, January 10, 2019 10:37 AM
To: DXLab@groups.io
Subject: Re: [DXLab] Launcher will not respond to "new app upgrades"

 

+ AA6YQ comments below

 

I have reinstalled DXLab Launcher and each time it just will not respond to a click on “new app upgrades.”

 

Clicking on CONFIG does nothing.

 

+ Both actions should make the Launcher's Configuration window visible. Since they are failing to do so, see

 

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

 

       73,

 

              Dave, AA6YQ