Date   

Cabrillo format update

Tony Dixon G4CJC
 

Hi Dave, 
Is there an easy way to update the Cabrillo export formats in DXKeeper. I tried with the EA-MAJESTAD-SSB but no luck. Even using last years EA-SMRE-SSB definition which is in DXKeeper contest config would give me "not supported".
Cheers
Tony G4CJC


Re: Pathfinder error

Dave AA6YQ
 

+ AA6YQ comments below
 Since Pathfinder is dependent at the moment on the latest release of Internet Explorer (version 11) ,per the link in Gil's prior email.
Is there a migration plan to go to another WEB browser when IE-11 goes out of support next year?  And what if any of the other DXLab suite members are also dependent on getting info through IE-11 will also be affected?.
+ Pathfinder works correctly on Windows 10 systems with Microsoft's Edge browser installed, and Internet Explorer not installed. To my knowledge, no DXLab application is specifically dependent on Internet Explorer; all work correctly with Edge.

       73,

              Dave, AA6YQ


Re: Pathfinder error

Dave AA6YQ
 

+ AA6YQ comments below:
When Pathfinder looks up a call on QRZ the error message "An error has occurred in the script on the page" pops up as the call info is displayed.

What is the cause/solution?

+ There are three possible causes:

1. you haven't configured Pathfinder to emulate Internet Explorer version 11
.
2, there's a script error on the web page that Pathfinder is trying to render, and you haven't configured Pathfinder to ignore such errors

3. there's a script error on the web page that Pathfinder is trying to render, you've configured Pathfinder to ignore such errors, but the Windows web browser control that Pathfinder uses is reporting the scripting error anyway

+ Gil W0MN has posted article in "Getting Started with DXLab" that addresses causes 1 and 2. The 3rd cause is beyond my control.

         73,

               Dave, AA6YQ


Re: Pathfinder error

Dave / NR1DX
 

Dave and Gil

On a related note, curiosity question

 Since Pathfinder is dependent at the moment on the latest release of Internet Explorer (version 11) ,per the link in Gil's prior email.
Is there a migration plan to go to another WEB browser when IE-11 goes out of support next year?  And what if any of the other DXLab suite members are also dependent on getting info through IE-11 will also be affected?

Dave
NR1DX

On 6/26/2021 4:36 PM, Gilbert Baron W0MN wrote:
SEE
https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjGmdLtkrbxAhUSVs0KHVzYCi4QFnoECAIQAA&url=http%3A%2F%2Fwww.dxlabsuite.com%2Fdxlabwiki%2FPreventingScriptingErrors&usg=AOvVaw0JCuHZAwfb7e-sz1ywgTXF

Outlook Laptop Gil W0MN
Hierro candente, batir de repente
44.08226N 92.51265W EN34rb

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of tgzuber
Sent: Saturday, June 26, 2021 15:01
To: DXLab@groups.io
Subject: [DXLab] Pathfinder error

When Pathfinder looks up a call on QRZ the error message "An error has occurred in the script on the page" pops up as the call info is displayed.

What is the cause/solution?

Tom Zuber WNØDRC








--
Dave Manuals@ArtekManuals.com www.ArtekManuals.com
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


Re: Pathfinder error

Gilbert Baron W0MN
 

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of tgzuber
Sent: Saturday, June 26, 2021 15:01
To: DXLab@groups.io
Subject: [DXLab] Pathfinder error

When Pathfinder looks up a call on QRZ the error message "An error has occurred in the script on the page" pops up as the call info is displayed.

What is the cause/solution?

Tom Zuber WNØDRC









--
W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


Pathfinder error

tgzuber
 

When Pathfinder looks up a call on QRZ the error message "An error has occurred in the script on the page" pops up as the call info is displayed.

What is the cause/solution?

Tom Zuber WNØDRC


Re: Spocollector

Dave AA6YQ
 

+ AA6YQ comments below
You where suspicious about the mouse and driver i used; I used a microsoft mouse and apropriate driver.
+ I cited your mouse and mouse driver as possible causes of a sudden change in behavior that occurred weeks after you last updated SpotCollector.
Remember, the ErrorLog showed that not every doubleclick was recognized as being a doubleclick.

+ The errorlog showed that Windows was not presenting SpotCollector with "double-click" events in response to the double-click gestures you reported making. That's can't be the result of a defect in SpotCollector.

 

In the mouse-settings there is a doubleclick-test incorporated. Everytime i tested, it did work normally.

The testfolder shown did open or close repeatedly at every doubleclick. Many many times.

Doubleclicking on an Icon on the homepage screen, in order to start an app or program, always worked.

Doubleclicking a Callsign to filter in DXKeeper, always worked fine.

Nevertheless, at your proposition, i changed the mouse, now using an Acer mouse and driver.

Meanwhile, i upgraded to Spotcollector  8.9.1.

All this togheter, i cannot tell what the culprit really has been. The mouse? The driver?

But anyway, finally SC is working fine again as it did before. Doubleclick always works fine, everywhere.

+ When debugging a problem, it is best to change only one variable at a time. Since you changed the mouse and driver, it would have been better to remain with the previous version of SpotCollector for a week or two. Then you'd know for certain that the new mouse or its driver was responsible for eliminating the "lost double-clicks".

+ Also keep in mind that, unlike software, physical devices like computer mice wear out over time.

         73,

                Dave, AA6YQ


Re: 6M WASvReport

Dave AA6YQ
 

+ "AA6YQ comments below".

Your saying that the following doesn't work as it did with the needed states in the first column?

+ I'm saying their are two different progress reports: one for WAS (names "WAS") that applies WAS rules, and one that does not apply WAS rules (named "US States"). The only way to generate the "US States" progress report is from a script.

The " Worked All US States Report" report from 02-Sep-2012 was generated by running a script that invokes the US_States progress report, as described here:

https://www.dxlabsuite.com/dxkeeper/Help/Scripts.htm#Report%20command


What does 'samat script' mean?

+ That's a typographical error; I meant to say "same script"

 

I have never run a script before and noticed under the Check Progress tab a Scripts button at the bottom.

I named them 6M 1 thru 6M 4, sequentially ran them and it worked.

 

As in:

N8XI US States Report 26-Jun-2021

Log Filter: (DXCCPrefix='k') and (band='6M') and (QSL_Rcvd='y' or APP_DXKeeper_LoTW_QSL_RCVD='y')

+ You have successfully generated the "US States" progress report from a script. Due to your Log Filter, however,

1. it only considers the 48 "continental" states, because (DXCCPrefix='k') excludes Alaska and Hawaii

2. it ignores QSOs to which DXCC credit has been granted.

+ My previous post in this thread explains how to correct #2.

       73,

              Dave, AA6YQ


Spocollector

eddy on5jk
 

Dave,

You where suspicious about the mouse and driver i used; I used a microsoft mouse and apropriate driver.

Remember, the ErrorLog showed that not every doubleclick was recognized as being a doubleclick.

In the mouse-settings there is a doubleclick-test incorporated. Everytime i tested, it did work normally.

The testfolder shown did open or close repeatedly at every doubleclick. Many many times.

Doubleclicking on an Icon on the homepage screen, in order to start an app or program, always worked.

Doubleclicking a Callsign to filter in DXKeeper, always worked fine.

Nevertheless, at your proposition, i changed the mouse, now using an Acer mouse and driver.

Meanwhile, i upgraded to Spotcollector  8.9.1.

All this togheter, i cannot tell what the culprit really has been. The mouse? The driver?

But anyway, finally SC is working fine again as it did before. Doubleclick always works fine, everywhere.

Thanks for all support.  I'm happy again.

Eddy ON5JK


Re: 6M WASvReport

Rick Arzadon - N8XI
 

Thanks Dave,

 

Dave,

Your saying that the following doesn't work as it did with the needed states in the first column?

The " Worked All US States Report" report from 02-Sep-2012 was generated by running a script that invokes the US_States progress report, as described here:

https://www.dxlabsuite.com/dxkeeper/Help/Scripts.htm#Report%20command


What does 'samat script' mean?

I have never run a script before and noticed under the Check Progress tab a Scripts button at the bottom.

I named them 6M 1 thru 6M 4, sequentially ran them and it worked.

 

As in:

N8XI US States Report 26-Jun-2021

Log Filter: (DXCCPrefix='k') and (band='6M') and (QSL_Rcvd='y' or APP_DXKeeper_LoTW_QSL_RCVD='y')

States worked:                   45

States confirmed:                45

States submitted for WAS credit: 0

States granted credit:           0

State        Callsign         Date & Time    Band    Mode  Card Cfm  LotW Cfm  LotW Mode    Status

 

       AK

       AL            N4UC   13-Jun-2010 00:59      6M      CW         Y         Y          =         C

       AR           K5NTT   13-Jun-2010 00:36      6M      CW         Y         R                    C

       AZ          WA7JTM   23-May-2011 02:02      6M     SSB                   Y          =         C

       CA           K6MYC   12-Jun-2011 00:38      6M     SSB         Y         R                    C

       CO          KC0RBT   23-May-2011 01:38      6M     SSB         Y         R                    C

       CT          KA1VMG   13-Jun-2010 19:25      6M     SSB         Y         R                    C

       DE

       FL            K4MM   12-Jun-2010 18:51      6M      CW         Y         Y          =         C

       GA            K8CQ   12-Jun-2010 18:53      6M      CW                   Y          =         C

       HI

       IA           KC0CF   23-May-2011 01:23      6M     SSB                   Y          =         C

       ID            KI0E   18-Jun-2020 14:44      6M     FT8                   Y          =         C

       IL            K9NS   13-Jun-2011 01:46      6M      CW         Y         Y          =         C

Thanks
73, Rick – N8XI


Re: Spotcollector Wrong mode.

Dave AA6YQ
 

+ AA6YQ comments below
I use DXlab together Commander, Spotcollector and DXview with the FTdx101MP
Only I have a question are there more users who also suffer from a spot coming in in Spotcollector and it is in CW and when I click on the spot in Spotcollector the Yaesu FTdx101MP goes to Data-u?
If I click on the same spot again, the Yaesu FTdx101MP will go to CW the mode in which it was spotted in Spotcollector.

+ Rien, you just posted the same report in the DXLab Group on Facebook. Within a few minutes of your doing so, I posted this response:

"If you'd like to understand what's happening, Rien, enable "log debugging info" on the General tab of Commander's Configuration window, and then start double-clicking on Spot Database Entries in SpotCollector. When wrong FTDX101MP ends up in the wrong mode for that Spot Database Entry,

1. on the General tab of Commander's Configuration window, uncheck the "log debugging info" box
2. create an email message that describes the Spot Database Entry on which you last double-clicked (callsign, frequency, mode)
3. attach the errorlog.txt file from your Commander folder to the email message you created in step 2, and send the message my way"

 

+ I would appreciate it if you would limit yourself to posting a problem report in no more than one venue; my strong preference is that you post it here.

       73,

                Dave, AA6YQ

 


Spotcollector Wrong mode.

Rien Aarden
 

Go DXLab users.
I use DXlab together Commander, Spotcollector and DXview with the FTdx101MP
Only I have a question are there more users who also suffer from a spot coming in in Spotcollector and it is in CW and when I click on the spot in Spotcollector the Yaesu FTdx101MP goes to Data-u?
If I click on the same spot again, the Yaesu FTdx101MP will go to CW the mode in which it was spotted in Spotcollector.
 
Thanks for the responses
Rien, PA7RA


Re: 6M WASvReport

Dave AA6YQ
 

You are comparing two different reports.

The " Worked All US States" report from 25-Jun-2021 was generated by clicking the Progress button in the WAS panel on the Main window's "Check Progress" tab. It shows your WAS progress by state, on each band and mode for which you are pursuing WAS. It only considers QSOs whose "myQTH" with a checked WAS box, indicating that the QSO was made from a location that "counts" for WAS. This progress report is described here:

https://www.dxlabsuite.com/dxkeeper/Help/Progress.htm#Generating%20and%20Processing%20a%20WAS%20Submission


The " Worked All US States Report" report from 02-Sep-2012 was generated by running a script that invokes the US_States progress report, as described here:

https://www.dxlabsuite.com/dxkeeper/Help/Scripts.htm#Report%20command

If you ran the samat script today, the progress report would be entitled "US States Report". This report does not apply all WAS rules; for example it considers QSOs whether or not the WAS box in their "myQTH" is checked; it is provided for ops not formally pursuing the WAS award.

Here's a 4-line script that will replicate the US_States progress report you generated back in 2012, but corrected to include Alaska and Hawaii, and corrected to count QSOs as confirmed if they have been awarded DXCC credit:


delete <ReportsFolder>us_states_6m_confirmed.txt

filter (DXCCPrefix in ('K','KH6','KL7')) and (band='6m') and (QSL_Rcvd in ('Y','V') or APP_DXKeeper_LoTW_QSL_RCVD in ('Y','V'))

appendreport us_states <ReportsFolder>us_states_6m_confirmed.txt

display <ReportsFolder>us_states_6m_confirmed.txt

73,

Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Rick Arzadon - N8XI via groups.io
Sent: Friday, June 25, 2021 1:47 PM
To: DXLab@groups.io
Subject: Re: [DXLab] 6M WASvReport

Dave,

Here is what I get.

Further down indicated by &&& is what I used to get.
========================================================

N8XI Worked All US States Report 25-Jun-2021

Limited to QSOs with "My QTHs" whose WAS box is checked

Log Filter: (DXCCPrefix='k') and (band='6M') and (QSL_Rcvd='y' or APP_DXKeeper_LoTW_QSL_RCVD='y')

State 6M

AK

AL C

AR C

AZ C

CA C

CO C

CT C

========================================================
&&&
N8XI Worked All US States Report 02-Sep-2012

Log Filter: (DXCCPrefix='k') and (band='6m') and (QSL_Rcvd='y' or APP_DXKeeper_LoTW_QSL_RCVD='y')



States worked or confirmed: 40

States confirmed: 40



State Callsign Date & Time Band Mode Card LotW

AK

AL N4UC 13-Jun-2010 00:59 6M CW Y Y

AR K5NTT 13-Jun-2010 00:36 6M CW Y R

AZ WA7JTM 23-May-2011 02:02 6M SSB Y

CA K6MYC 12-Jun-2011 00:38 6M SSB Y R

CO KC0RBT 23-May-2011 01:38 6M SSB Y R

CT W3EP 13-Jun-2010 19:28 6M SSB Y

DE

FL K4MM 12-Jun-2010 18:51 6M CW Y Y

GA K8CQ 12-Jun-2010 18:53 6M CW Y

HI

IA KC0CF 23-May-2011 01:23 6M SSB Y

ID

IL K9NS 13-Jun-2011 01:46 6M CW Y Y

IN N9XG 17-Jul-2011 13:25 6M SSB Y R

KS W0BH 13-Jun-2010 21:06 6M CW Y Y

KY

LA AA5AU 12-Jun-2011 12:43 6M SSB Y



<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: 6M WASvReport

Rick Arzadon - N8XI
 

Dave,

Here is what I get.

Further down indicated by &&& is what I used to get.
========================================================

N8XI Worked All US States Report 25-Jun-2021

Limited to QSOs with "My QTHs" whose WAS box is checked

Log Filter: (DXCCPrefix='k') and (band='6M') and (QSL_Rcvd='y' or APP_DXKeeper_LoTW_QSL_RCVD='y')

State        6M

AK            

AL            C

AR            C

AZ            C

CA            C

CO            C

CT            C

========================================================
&&&
N8XI Worked All US States Report 02-Sep-2012

Log Filter: (DXCCPrefix='k') and (band='6m') and (QSL_Rcvd='y' or APP_DXKeeper_LoTW_QSL_RCVD='y')

 

States worked or confirmed: 40

States confirmed:           40

 

   State        Callsign         Date & Time    Band    Mode    Card    LotW

      AK

      AL            N4UC   13-Jun-2010 00:59      6M      CW       Y       Y

      AR           K5NTT   13-Jun-2010 00:36      6M      CW       Y       R

      AZ          WA7JTM   23-May-2011 02:02      6M     SSB               Y

      CA           K6MYC   12-Jun-2011 00:38      6M     SSB       Y       R

      CO          KC0RBT   23-May-2011 01:38      6M     SSB       Y       R

      CT            W3EP   13-Jun-2010 19:28      6M     SSB               Y

      DE

      FL            K4MM   12-Jun-2010 18:51      6M      CW       Y       Y

      GA            K8CQ   12-Jun-2010 18:53      6M      CW               Y

      HI

      IA           KC0CF   23-May-2011 01:23      6M     SSB               Y

      ID

      IL            K9NS   13-Jun-2011 01:46      6M      CW       Y       Y

      IN            N9XG   17-Jul-2011 13:25      6M     SSB       Y       R

      KS            W0BH   13-Jun-2010 21:06      6M      CW       Y       Y

      KY

      LA           AA5AU   12-Jun-2011 12:43      6M     SSB               Y


Re: Port 52003 and help documentation

Pete W1RM
 

Thanks Bill.  If this occurs again, I’ll just ignore it.  Click the button and keep on.

 

 

Pete Chamalian, W1RM

W1rm@...

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of g4wjs
Sent: Wednesday, June 23, 2021 10:37 AM
To: DXLab@groups.io
Subject: Re: [DXLab] Port 52003 and help documentation

 

On 23/06/2021 13:32, Pete W1RM wrote:

This morning when I started spot collector I got an error message saying port 52003 was in use by another program.  Where is this port used in spot collector and what to do?

 

It would be great if all the help documentation could be searchable so I could better be able to find this in help.

 

 

Pete Chamalian, W1RM

W1rm@...

Hi Pete,

this error is because DX Lab Suite uses some network service port numbers that are in a range that MS Windows grants to applications on a round robin basis, on demand, for use as temporary ephemeral ports that network partners discover by normal message exchanges. That means that once in a while (could be months between) DX Lab Suite will start only to find a port it wants to use has already been granted to another application. The port may be freed after a short period, it will almost certainly be freed by a reboot.


--
73

Bill

G4WJS.


SpotCollector 8.9.1 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.9.1


This release

- corrects a regression in SpotCollector 8.8.7 that caused incorrect scrolling when the Spot Database sort order is set to
"descending" (tnx to Jon KM8V and Joe W4TV)

- disables the (unintentionally enabled) ability to directly modify a Spot Database Entry (tnx to Salvatore I4FYV)

- correctly displays the port status in the Network Service panel on the Configuration window's General tab

- adds an "Auto Config" checkbox to the WSJT-X panel on the Configuration window's "Spot Sources" tab that when checked directs the
local instance of WSJT-X to select the Configuration whose name is that of the primary transceiver selected in the local instance
of Commander (tnx to Peter N5UWY and Bill G4WJS)

- updates the CollectingSources.htm, SourceConnection.htm, and WSJTXInteraction.htm documentation files


Notes:

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

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

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

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

d. 2/69 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

4. This version provides an updated Sub-band Definition file:

BandModes 2021-04-20

with a single CW entry for the new 5m band and a single CW entry for the new 8m band. You can define a custom Sub-band Definition
file that is consistent with 5m and 8m usage in your area, as described in

https://www.dxlabsuite.com/dxlabwiki/SubbandDefinitions


SpotCollector 8.9.1 is available via the DXLab Launcher, and via

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


73,

Dave, AA6YQ


Re: 6M WASvReport

Dave AA6YQ
 

This is what it looks like on my Tower PC

I just tried it on my LapTop and same is happening there now.

N8XI Log Report 24-Jun-2021

Filter: (DXCCPrefix='k') and (band='6m') and (QSL_Rcvd='y' or APP_DXKeeper_LoTW_QSL_RCVD='y')

Sort: QSO_Begin

+ You're invoking DXKeeper's "Log Report", not its WAS progress report. On the WAS panel in the Main window's "Check Progress" tab, click the Progress button.

73,

Dave, AA6YQ


Re: 6M WASvReport

Rick Arzadon - N8XI
 

This is what it looks like on my Tower PC

I just tried it on my LapTop and same is happening there now.

N8XI Log Report 24-Jun-2021

  Filter: (DXCCPrefix='k') and (band='6m') and (QSL_Rcvd='y' or APP_DXKeeper_LoTW_QSL_RCVD='y') 

   Sort:   QSO_Begin


Re: Spotcollector issue

Dave AA6YQ
 

+ AA6YQ comments below

since last update I noticed that when I click on a spot on the spotcollector screen, I'm yes redirected to that spot, but the cell of the clicked spot goes like in editing mode until the refresh of the spot screen with new incoming spots.

+ That's a defect inadvertently inserted in SpotCollector 8.8.8. It's corrected in the next version of SpotCollector, the public release of which is imminent.

73,

Dave, AA6YQ


Spotcollector issue

Boris Sfiligoj
 

Hello,
since last update I noticed that when I click on a spot on the spotcollector screen, I'm yes redirected to that spot, but the cell of the clicked spot goes like in editing mode until the refresh of the spot screen with new incoming spots.

my best 73
Boris iv3fpx


5861 - 5880 of 207970