Date   

Re: spots of K1JT modes contain what appear to be QSX indications in their spot notes

w6de
 

I also agree with your suggestion and have no better ideas.

73,
Dave, w6de

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Friday, February 12, 2021 01:24
To: DXLab@groups.io
Subject: [DXLab] spots of K1JT modes contain what appear to be QSX
indications in their spot notes

A spot of 5A0YL today on 18,100 with spot notes

2021-02-11 15:03 de W1HS (NA-E) on 18,100.0 : FT8 wkd -18 NH

led SpotCollector to erroneously set the Spot Database Entry's QSX field to
18,082.

Though WSJT-X may enable your transceiver's Split function in order to keep
your transmit tones in a reasonable range, any QSX
frequency extracted from spot notes is ignored because the panoramic
reception employ bye WSJT-X makes it irrelevant.

I thus propose that the next version of SpotCollector not attempt to extract
QSX frequencies from the spot notes of stations
operating in K1JT modes.

Objections? Better ideas?

73,

Dave, AA6YQ


Re: Script Error

Julio Peralta
 

Dave it appears that all the Script Error popups have stopped. I can’t get any of the services to show a pop up error dialog window.

 

Julio

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Friday, February 12, 2021 5:25 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Script Error

 

+ AA6YQ comments below

Well I did several lookups using the other
services in PF some displayed the Script error
some did not. The last one I tried was QRZ and no
Script Error so I minimized PF as I usually run it
and the script Errors have stopped.

+ It would be helpful to have several specific searches (e.g. this callsign in that search/source) that result in Pathfinder reporting a script error.

     73,

            Dave, AA6YQ


Re: Script Error

Dave AA6YQ
 

+ AA6YQ comments below
Well I did several lookups using the other
services in PF some displayed the Script error
some did not. The last one I tried was QRZ and no
Script Error so I minimized PF as I usually run it
and the script Errors have stopped.

+ It would be helpful to have several specific searches (e.g. this callsign in that search/source) that result in Pathfinder reporting a script error.

     73,

            Dave, AA6YQ


Re: Script Error

Julio Peralta
 

Yes I know PF is IE.

Well I did several lookups using the other
services in PF some displayed the Script error
some did not. The last one I tried was QRZ and no
Script Error so I minimized PF as I usually run it
and the script Errors have stopped.

Julio

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On
Behalf Of Dave AA6YQ
Sent: Friday, February 12, 2021 3:24 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Script Error

+ AA6YQ comments below

IE is not showing an error message with each
lookup. It appears that it is only with PF. PF is
completing the look up.

+ Pathfinder *is* IE, Julio.

+ Is Pathfinder displaying script errors for every
web page in every online callbook, every web page
in just one online callbook
(which one?), or just some web pages in just one
online callbook (which web page?).

+ I just directed Pathfinder to display QSL
information for 10 different callsigns around the
world -- including yours -- but
encountered not a single script error report.

73,

Dave, AA6YQ


Re: Script Error

Dave AA6YQ
 

+ AA6YQ comments below

IE is not showing an error message with each lookup. It appears that it is only with PF. PF is completing the look up.

+ Pathfinder *is* IE, Julio.

+ Is Pathfinder displaying script errors for every web page in every online callbook, every web page in just one online callbook
(which one?), or just some web pages in just one online callbook (which web page?).

+ I just directed Pathfinder to display QSL information for 10 different callsigns around the world -- including yours -- but
encountered not a single script error report.

73,

Dave, AA6YQ


Re: QSO logging in DX keeper

Dave AA6YQ
 

+ AA6YQ comments below

I have been using the subject for about a week now.

+ Welcome to DXLab!

I really like the integration with commander and the ability to fill in the QSO fields automatically (bare with me....I have been out of this hobby for a while!).
Anyway, I would like to enter comments about the QSO but I don't see a specific field for that. I could use QTH or maybe the QSL comments, but I thought there should be a comment field maybe?
Suggestions? Or maybe this is user error?

+ DXKeeper can record a Comment with each logged QSO, along with more than 100 other items. They're documented here:

https://www.dxlabsuite.com/dxkeeper/Help/Items.htm

+ Note that they are organized into 8 groups, corresponding to 8 panels you can make accessible on the Main window's "Log QSOs" tab. The first screen shot in "Getting Started with Logging" in

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

+ shows how to make the Auxiliary and QSL panels accessible. The Comment item you seek resides in the Details panel, which can be made visible by checking the Details box in the vertical column of checkboxes highlighted in the "Getting Started with Logging" article.

+ Most users log new QSOs with the Capture window, using the Main window's "Log QSOs" tab to view/edit QSOs already logged, or to log "already completed" QSOs from a paper logbook. The "Getting Started with Logging" article illustrates expanding the Capture window to make all of its items accessible. Note that the "comment" item resides in the 10th row of boxes, with a button labeled ~ to its right. Clicking this ~ button provides access to the "QSL msg" item; clicking the ~ button again restores access to the "Comment" item.]

+ While every button, box, and selector in every DXLab application will display an explanatory popup if you let your mouse cursor hover over it for a second or three, there is way too much functionality to learn by wandering around. I strongly recommend reviewing "Getting Started with DXLab" in

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

+ and following the advice it offers in the "Reference Documentation" section near the top. Take your time, and don't hesitate to post questions here.

73,

Dave, AA6YQ


Re: Script Error

Julio Peralta
 

IE is not showing an error message with each
lookup. It appears that it is only with PF. PF is
completing the look up.

Julio

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On
Behalf Of Dave AA6YQ
Sent: Friday, February 12, 2021 3:02 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Script Error

+ AA6YQ comments below

Starting yesterday I also have been getting Script
Error every time Path finder looks up a call. The
hide Script Errors box is
checked in the path finder config setup menu and
IE explorer is set to 11 as is Emulation.

Something else must be going on.

+ Is that the case for every web page that you
direct Pathfinder to display, or just web pages
from one online callbook? If the
latter, which one?

+ Note that Windows Explorer does in some
circumstances ignore the "ignore script errors"
setting; that's a defect in Windows
Explorer that I cannot correct.

73,

Dave AA6YQ


Re: Script Error

Dave AA6YQ
 

+ AA6YQ comments below

Starting yesterday I also have been getting Script Error every time Path finder looks up a call. The hide Script Errors box is
checked in the path finder config setup menu and IE explorer is set to 11 as is Emulation.

Something else must be going on.

+ Is that the case for every web page that you direct Pathfinder to display, or just web pages from one online callbook? If the
latter, which one?

+ Note that Windows Explorer does in some circumstances ignore the "ignore script errors" setting; that's a defect in Windows
Explorer that I cannot correct.

73,

Dave AA6YQ


Re: [Elecraft] Powering down K3 using DXLab Commander

Joe Subich, W4TV
 

The K3/K3S does not have any provision to turn on via the RS-232/USB
interface. When it is powered down the processor is not running so
there is nothing there to interpret commands.

The only way to perform a remote power on is to pull the "power on" line
of the ACC connector to ground for at least 100 msec (K3 Owner's Manual,
page 44). Unfortunately, I do not know that Commander has any provision
to toggle a specific hardware signal in response to a User Defined
Command.

73,

... Joe, W4TV

On 2021-02-12 2:46 PM, David F. Reed wrote:
I need some help figuring this out; I can do the power down from the Elecraft Utility (using command "*PS0;*")
In trying to get it to run from Commander, I have done the following (but no results); other than this, Commander is working fine.
User -defined Command Sequence:
    Note:             Power Off
    Command:    PS0;
Unfortunately, hitting Run on the edit screen, or clicking F5 button produces no results.
Any hints for the befuddled?
Thanks & 73 de Dave, W5SV


Re: Powering down K3 using DXLab Commander

David Reed
 

Thanks Ian, that did it!

73 de Dave, W5SV

On 2/12/2021 19:57, iain macdonnell - N6ML wrote:
On Fri, Feb 12, 2021 at 11:46 AM David Reed <w5sv.dave@gmail.com> wrote:
I need some help figuring this out; I can do the power down from the Elecraft Utility (using command "PS0;")

In trying to get it to run from Commander, I have done the following (but no results); other than this, Commander is working fine.

User -defined Command Sequence:
Note: Power Off
Command: PS0;
Try the following:

'PS0;

ASCII commands must be prefixed with a single-quote - see
https://www.dxlabsuite.com/commander/Help/CommandSequences.htm

73,

~iain / N6ML




Re: Powering down K3 using DXLab Commander

iain macdonnell - N6ML
 

On Fri, Feb 12, 2021 at 11:46 AM David Reed <w5sv.dave@gmail.com> wrote:

I need some help figuring this out; I can do the power down from the Elecraft Utility (using command "PS0;")

In trying to get it to run from Commander, I have done the following (but no results); other than this, Commander is working fine.

User -defined Command Sequence:
Note: Power Off
Command: PS0;
Try the following:

'PS0;

ASCII commands must be prefixed with a single-quote - see
https://www.dxlabsuite.com/commander/Help/CommandSequences.htm

73,

~iain / N6ML


Re: Pathfinder Script Error

Dave AA6YQ
 

+ AA6YQ comments below

When I started DxLab Launcher this morning, I got a Script Error in Pathfinder.

An error has occurred in the script on this page.
Line: 1582
Char: 34
Error: Expected ";"
Code: 0
URL: http://www.qrz.com/db/(anycall here) Do you want to continue running scripts on this page?

+ Pathfinder is Microsoft Internet Explorer with a thin added layer to facilitate searching specific web sites for QSL information. The error message above is from Internet Explorer informing you that the web page it is attempting to render contains errors.

I reloaded DxLab and got the same error message.

+ That's the rough equivalent of removing and then re-installing your car's engine when it won't start because its gas tank is empty.

What do I do to fix this problem?

+ See "Preventing Script Errors and Ensuring that Web Pages are Correctly Rendered" in

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

73,

Dave, AA6YQ


Script Error

Julio Peralta
 

Starting yesterday I also have been getting Script Error every time Path finder looks up a call. The hide Script Errors box is checked in the path finder config setup menu and IE explorer is set to 11 as is Emulation.

 

Something else must be going on.

 

Julio


Re: Wrong qrz call

Dave AA6YQ
 

+ AA6YQ comments below

Correction is KU8T

+ Please answer the two questions I posed in

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

73,

Dave, AA6YQ


Powering down K3 using DXLab Commander

David Reed
 

I need some help figuring this out; I can do the power down from the Elecraft Utility (using command "PS0;")

In trying to get it to run from Commander, I have done the following (but no results); other than this, Commander is working fine.

User -defined Command Sequence:
    Note:             Power Off
    Command:    PS0;

Unfortunately, hitting Run on the edit screen, or clicking F5 button produces no results.

Any hints for the befuddled?

Thanks & 73 de Dave, W5SV

 


Re: Pathfinder Script Error

Patrick ON6AT
 

Hi,

Same problem today.

73 Patrick ON6AT


Re: Pathfinder Script Error

Joe Subich, W4TV
 

Dave's oft repeated response to questions about script errors is:

+ Take a look at this article:
https://www.dxlabsuite.com/dxlabwiki/PreventingScriptingErrors



73,

... Joe, W4TV


On 2021-02-12 9:33 AM, Jim Hall wrote:
I also have the same problem and resulting error message with Pathfinder and QRZ this morning.


Re: iCOM "Keyer Type" sequence

Norm - KC1BMD
 

Thanks Dave!
--
73, Norm/KC1BMD


Re: Pathfinder Script Error

Jim Hall
 

I also have the same problem and resulting error message with Pathfinder and QRZ this morning.


Re: QSO logging in DX keeper

Bill Pence
 

There are some click buttons on dxkeeper that show more fields. I think the comments are within the "details" button but I'm not in front of logging pc right now to confirm.

I tried to find in help files. If you open the capture window in dxkeeper, alt-e moves to comments.

4341 - 4360 of 203988