Date   

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.


Re: QSO logging in DX keeper

ND9G Mike
 

" 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?"


If you're using the capture window to enter QSOs, expand the window by dragging the top/bottom edges. There is a comment field there you can enter.

If you're entering them directly on the log page display, click the box to enable the "Details" panel, there is a comment field there.

73,
Mike ND9G


On Fri, Feb 12, 2021 at 9:16 AM Lance HP <lstronk@...> wrote:
I have been using the subject for about a week now. 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?


QSO logging in DX keeper

Lance HP
 

I have been using the subject for about a week now. 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?


File /SpotCollector Sub-band Definition files/BandModes (EU incl VHF).txt uploaded #file-notice

DXLab@groups.io Notification <noreply@...>
 

The following files have been uploaded to the Files area of the DXLab@groups.io group.

By: aart wedemeijer PA3C <pa3c@...>

Description:
Bandmodes for EU incl. 6M&2M


Pathfinder Script Error

Stewart Lewis
 

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? 

I reloaded DxLab and got the same error message.
What do I do to fix this problem?


Re: Wrong qrz call

Dave Tucker Nu4N <dwtucker19@...>
 

Correction is KU8T
--
73's de NU4N Dave


Re: Wrong qrz call

Dave Tucker Nu4N <dwtucker19@...>
 

KU is Thomas in in IND is correct The I have Randolph in CA & Laurence in MI.

Kinda strange
--
73's de NU4N Dave


Re: iCOM "Keyer Type" sequence

Dave AA6YQ
 

+ AA6YQ comments below

Anyone have a sequence for controlling "Keyer Type" (i.e. Straight, BUG-KEY, ELEC-KEY from iCOM menu controlled by VFO knob rotation) for an iCOM IC-756Pro3 or similar radio? I checked the files section already. Maybe someone could suggest how to approach the sequence construction?

+ 40% of the way down the left-hand column on page 113 of the IC-756ProIII Instruction Manual, the Command 1A with Sub command 0554 controls the choice among keyer type:

FEFE<CIV>E01A055400FD - selects straight key

FEFE<CIV>E01A055401FD - selects bug key

FEFE<CIV>E01A055402FD - selects ELEC key

+ Note that the Command and Sub command may be different for different Icom transceivers; with my IC-7800, for example, the Sub command is 0143 rather than 0554.

+ If your objective is a sequence that’s one specific keyer type, then your sequence need only specify the correct instruction above, followed by

<end>

+ If you want a sequence that progress through two or three different keyer types, use an existing 2-state or 3-state sequence from this Group's Files aread that controls some other Icom function (preamp, anenna, noise blanker, APF) and emulate its structure, substituting in the commands to control the keyer type.

73,

Dave, AA6YQ


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

Mike Flowers
 

I agree. This should be the behavior in such cases.

-- 73 de Mike Flowers, K6MKF, NCDXC - "It's about DX!"

On Feb 11, 2021, at 5:26 PM, Jon Gefaell <jon@turing.org> wrote:

Sounds like the right behaviour to me.

On 2/11/2021 20:23, Dave AA6YQ wrote:
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: spots of K1JT modes contain what appear to be QSX indications in their spot notes

Jon Gefaell
 

Sounds like the right behaviour to me.

On 2/11/2021 20:23, Dave AA6YQ wrote:
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




3841 - 3860 of 203479