Date   

Re: waiting for TQSL to complete processing

Dave AA6YQ
 

+ AA6YQ comments below

Is it possible to make the DXKeeper LOTW automatic upload window smaller, not display or have it where is is not always on top of other windows

ps: this is a question not a request hi hi hi

+ The small LoTW window that briefly appears on-screen when automatically uploading a just-logged QSO to LoTW is intentionally "always on top" to assure the operator that the QSO has been successfully uploaded. There is no option to disable this behavior.

73,

Dave, AA6YQ


Re: Controlling sequence from another sequence?

Norm - KC1BMD
 

Thanks, I missed the command I would need due to careless search and reading,
--
73, Norm/KC1BMD


Re: Controlling sequence from another sequence?

Dave AA6YQ
 

I know a sequence can include a command to control a slider (and I do that). Is it possible for a sequence to include a command to control another sequence? For example: You have a bank for four buttons (sequences) and you want to press (click) any one of the buttons and show the other three as not pressed. It could be surface color or LED color changes to show the one (and only one) active button. I am not an avid DX/Contester and was just wondering if this would be a useful enhancement for anyone but me who is primarily using DXLab (Commander) for rig control and simple logging. That's not the primary audience for the DXLab Suite but I thought I would ask. :)

+ There are two ways to show the "state" of a command sequence: by the caption that appears on its button, and by the color of the LED-like display that appears below its button. Any sequence can

- change the button caption of any other sequence

- change the LED color of any other sequence

- branch based on the button caption of any other sequence

73,

Dave, AA6YQ


Re: Support for icom ID-5100

Dave AA6YQ
 

+ AA6YQ comments below

Which radio did you set it to that is "close"? I have the baby
brother, ID-4100A and would like to see what I can do with Commander
and that radio.

IC-756 works for basic stuff.

Thanks - I'll give that a try.

DF4OR has a (metric) ton of CI-V stuff here, but his fascination ran out some years ago. So, as a result, there isn't much new stuff there. As you've found, the basic commands are all the same. Where the command set really goes crazy is with the $1A subcommands - that's where all the "unique to a particular model" stuff seems to go.

+ The ID-5100 diverges in VFO support (command 07), as well as not supporting CW and SSB (command 04).

73,

Dave, AA6YQ


Re: QSL printing size problem

Dave AA6YQ
 

Thanks, Dave. Problem solved. It takes some time adjusting, cut and try so to say. Now it is fine.
I use to have one card layout from my home qth and one from my summer house.

Is it possible to save the layouts for later use?

+ Yes:

1. terminate DXKeeper

2. save DXKeeper's settings to a Workspace named "HomeQTH"

3. start DXKeeper and configure it for your summer QSL cards

4. terminate DXKeeper

5. save DXKeeper's settings to a Workspace named "SummerQTH"

6. next summer, terminate DXKeeper and load its settings from your "SummerQTH" Workspace

+ Step-by-step instructions are in "Saving and Loading Windows Registry Settings" here:

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

73,

Dave, AA6YQ


Re: ADIf export

Dave AA6YQ
 

@ more AA6YQ comments below

Dave is there any progress in exporting log to GMA?

@ No, because a GMA field has not yet been added by ADIF.

@ If you are impatient, you can setup a user-defined item to record GMA information with each QSO. If you do that, you'll have to copy information from your GMA user-defined items to the GMA item after ADIF approves the addition of GMA and I add a GMA item to DXKeeper - but that can be done "en masse" using the "Advanced Sorts, Modifiers, and Filters" window's "Modify QSOs" panel.


Sorry for bothering you again.

@ I have no way of accelerating ADIF's approval and release process.

73,

Dave, AA6YQ


Re: Support for icom ID-5100

nicolas.mailloux@...
 
Edited

On Mon, Mar 1, 2021 at 12:21 PM, Peter Laws / N5UWY wrote:
DF4OR has a (metric) ton of CI-V stuff here, but his fascination ran
out some years ago. So, as a result, there isn't much new stuff
there. As you've found, the basic commands are all the same. Where
the command set really goes crazy is with the $1A subcommands - that's
where all the "unique to a particular model" stuff seems to go.

http://www.plicht.de/ekki/civ/

Icom has never been really good at documenting CI-V but the site above
is a good stand-in. Maybe we should see if the author would let us
convert that to a Wiki and expand on it ...
Thanks, I'm working on something similar specifically made for the ID-5000. I already have a console (dos) application in alpha mode with almost no features, but this is going to be the test base for a more user friendly windows application. My goal is to have a command line that works under linux and windows and a gui application that works on Windows that will mimic the LCD screen.

VE2UTK


Controlling sequence from another sequence?

Norm - KC1BMD
 

I know a sequence can include a command to control a slider (and I do that). Is it possible for a sequence to include a command to control another sequence? For example: You have a bank for four buttons (sequences) and you want to press (click) any one of the buttons and show the other three as not pressed. It could be surface color or LED color changes to show the one (and only one) active button. I am not an avid DX/Contester and was just wondering if this would be a useful enhancement for anyone but me who is primarily using DXLab (Commander) for rig control and simple logging. That's not the primary audience for the DXLab Suite but I thought I would ask. :)

--
73, Norm/KC1BMD


CQ 160 SSB contest submit problem

Phil W9IXX
 

Hi,
Basic user here and setup for contest and went ok as logged thru the capture
window and could log and change exchanges as necessary.

Went to print the Cabrillo report and it did not include the state/prov but did include
the 59 part of the exchange. Noticed in the DXKeeper window and Log QSOs tab
all the info is there except not in the area where all the qsos are shown. I only have
a few of the columns I normally want there. I assume (hate that Hi.) that I need the exchange
for state/prov there also which I do not have in there.

What do I need to add or check-mark to get the report to add them. Also agn assume need to
do a manual scoring of results or other items like times off.  Most all else seems ok.

Thanks for reading this and really like the program. Wish I had more time to go thru all of its features.
73 Phil W9IXX


Re: Support for icom ID-5100

Peter Laws / N5UWY
 

On Mon, Mar 1, 2021 at 10:59 AM <nicolas.mailloux@micronick.com> wrote:

Which radio did you set it to that is "close"? I have the baby
brother, ID-4100A and would like to see what I can do with Commander
and that radio.

IC-756 works for basic stuff.

Thanks - I'll give that a try.

DF4OR has a (metric) ton of CI-V stuff here, but his fascination ran
out some years ago. So, as a result, there isn't much new stuff
there. As you've found, the basic commands are all the same. Where
the command set really goes crazy is with the $1A subcommands - that's
where all the "unique to a particular model" stuff seems to go.

http://www.plicht.de/ekki/civ/

Icom has never been really good at documenting CI-V but the site above
is a good stand-in. Maybe we should see if the author would let us
convert that to a Wiki and expand on it ...

--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


Re: Support for icom ID-5100

nicolas.mailloux@...
 

Which radio did you set it to that is "close"? I have the baby
brother, ID-4100A and would like to see what I can do with Commander
and that radio.
IC-756 works for basic stuff.


Re: Support for icom ID-5100

nicolas.mailloux@...
 

The ID-5100 only operates on 144 mHz and 440 mHz, and only in AM, FM, or Digital Voice; neither CW nor SSB are supported. It's CI-V instruction set is significantly different than that of any other Icom transceiver supported by Commander.

I have no plan to extend Commander to support the ID-5100.
Thanks for letting us know, Dave. I have already started on writing a software for operating the 5100 in a headless mode.


Re: eQSL upload needs a timeout?

AB2ZY
 
Edited

Like I said, FYI. If no one else is reporting this then it must be my computer. FWIW, this is a older Win7 machine that is dedicated to shack duties. The only applications installed are DXlab, N1MM, WSJT, MMTTY, uHAM Router and whatever software is needed for an RSPdx SDR I bought last year. MSINET.OCX is at version 6.01.9782, which is no surprise as ActiveX has been deprecated for some time now and no new applications are being developed with it. I'm quite sure DXLab is the only application using MSINET on that computer.

Thanks,

Al
AB2ZY


waiting for TQSL to complete processing

jim
 

Is it possible to make the DXKeeper LOTW automatic upload window
smaller,
not display
or have it where is is not always on top of other windows

thanks 73
de jim

ps: this is a question not a request hi hi hi


Re: Commander won't launch

David Reed
 

Thanks Dave, got one on order now, arrives Wednesday!

73 de W5SV - David F. Reed

On Mar 1, 2021, at 00:46, Dave AA6YQ <aa6yq@...> wrote:

@ more AA6YQ comments below
A disk problem with a bad sector; looking to replace it with an SSD drive, but reliability is my prime concern here.

+ In my view, making your local backup and recovery mechanism reliable should be your first priority.

Agree 100%; working on that and any recommendations are welcome.

@ SSDs are more expensive than rotating drives, but they are also more reliable. In dedicated backup service, however, a failed rotating drive (as you have now) is not fatal because the primary storage (ideally SSD)  and the cloud backup service both remain intact, preventing a single-bit failure from causing data loss, Thus I would simply replace your failed rotating drive with one having plenty of capacity.

       73,

            Dave, AA6YQ


Re: QSL printing size problem

Knut Meland
 

Thanks, Dave. Problem solved. It takes some time adjusting, cut and try so to say. Now it is fine.
I use to have one card layout from my home qth and one from my summer house.

Is it possible to save the layouts for later use?

73 de Knut LA9RY

Den 01.03.2021 09.24, skrev Dave AA6YQ:

+ AA6YQ comments below

Recommended size for QSL cards is 90*140 mm. My cards are this size.
This size is not in the menu, neither in DXkeeper printer module nor in the printer's menu.
The solution is to make a custom defined format.
I define 90*140 mm.
Then printer tells me that max height is minimum 89 mm.

+ How can a maximum height can have a minimum value?

Thus 90 mm is too much.
Adjusting height according to this.
Then DXKeeper tells me: Specified QSL card is too large: max 85,51341 mm.

+ DXKeeper is telling your that the QSL card you've defined won't fit on the paper size you've specified given the margins reported by your printer driver.

Adjusting according to this is impossible.
Is there a way to solve this?

+ On the "QSL Configuration" window's "Cards" panel,

- What have you selected in the "Page Layout" panel?

- What have you specified for each of the settings in the "Card Dimensions" panel?

+ With at least one QSO in the QSL Queue, on the Main window's QSLs tab, check the "Print preview" box, and then click the "Print QSLs Cards" button to display the "Print Preview" window. What is displayed for the "Left margin", Width, "Top Margin", and Height parameters at the top of this window?


Printing 4 cards on one sheet is definitely not a solution.

+ What do you mean by this? Are you saying that you want to print one card per sheet?

73,

Dave, AA6YQ






Re: ADIf export

eddy on5jk
 

Dave is there any progress in exporting log to GMA?

Sorry for bothering you again.

Eddy ON5JK

Op 7/01/2021 om 9:53 schreef Dave AA6YQ:

+ AA6YQ comments below

Why did i do that: Two reasons:

1) Because i am a dumbo.

2) I was being informed, that if a notification was not correct as described in models, they would never be accepted.

(WWFF abFF-1234 / WCA ab-12345 etc.) ab=prefix and 4 (WWFF)or 5 (WCA)digits . With the needed dash.

also the formats for LH/SOTA etc where explained there.

It was a very great surprise to me, how many errors i made while logging.

Capitals or not; no dash or something else; Wrong numbering; faulty notes in log; etc.etc.

Just because the discovery of that bunch of errors, i edited the log one by one, manualy.

I know i've been born 50 years to early. Or 50 to late HI.

I will follow-up your coming instructions abt the tab delimited file and the next updates.

+ My guess is that fields used by GMA will be added to the next version of ADIF, after which I will add them to DXKeeper. To avoid more unnecessary rework, I suggest that you wait until then.

73,

Dave, AA6YQ






Re: QSL printing size problem

Dave AA6YQ
 

+ AA6YQ comments below

Recommended size for QSL cards is 90*140 mm. My cards are this size.
This size is not in the menu, neither in DXkeeper printer module nor in the printer's menu.
The solution is to make a custom defined format.
I define 90*140 mm.
Then printer tells me that max height is minimum 89 mm.

+ How can a maximum height can have a minimum value?

Thus 90 mm is too much.
Adjusting height according to this.
Then DXKeeper tells me: Specified QSL card is too large: max 85,51341 mm.

+ DXKeeper is telling your that the QSL card you've defined won't fit on the paper size you've specified given the margins reported by your printer driver.

Adjusting according to this is impossible.
Is there a way to solve this?

+ On the "QSL Configuration" window's "Cards" panel,

- What have you selected in the "Page Layout" panel?

- What have you specified for each of the settings in the "Card Dimensions" panel?

+ With at least one QSO in the QSL Queue, on the Main window's QSLs tab, check the "Print preview" box, and then click the "Print QSLs Cards" button to display the "Print Preview" window. What is displayed for the "Left margin", Width, "Top Margin", and Height parameters at the top of this window?


Printing 4 cards on one sheet is definitely not a solution.

+ What do you mean by this? Are you saying that you want to print one card per sheet?

73,

Dave, AA6YQ


QSL printing size problem

Knut Meland
 

Recommended size for QSL cards is 90*140 mm. My cards are this size.
This size is not in the menu, neither in DXkeeper printer module nor in the printer's menu.
The solution is to make a custom defined format.
I define 90*140 mm.
Then printer tells me that max height is minimum 89 mm. Thus 90 mm is too much.
Adjusting height according to this.
Then DXKeeper tells me: Specified QSL card is too large: max 85,51341 mm.
Adjusting according to this is impossible.
Is there a way to solve this? Printing 4 cards on one sheet is definitely not a solution.
73 de Knut LA9RY


Re: Commander won't launch

Dave AA6YQ
 

@ more AA6YQ comments below
A disk problem with a bad sector; looking to replace it with an SSD drive, but reliability is my prime concern here.

+ In my view, making your local backup and recovery mechanism reliable should be your first priority.

Agree 100%; working on that and any recommendations are welcome.

@ SSDs are more expensive than rotating drives, but they are also more reliable. In dedicated backup service, however, a failed rotating drive (as you have now) is not fatal because the primary storage (ideally SSD)  and the cloud backup service both remain intact, preventing a single-bit failure from causing data loss, Thus I would simply replace your failed rotating drive with one having plenty of capacity.

       73,

            Dave, AA6YQ

 

3401 - 3420 of 203497