Date   

Re: DX CMD 13.7.2 , MIcrokeyer II 2nd CAT COM port problems

Alex OE3JTB
 
Edited

Joe tnx that was the hint, the interrogation was set to 10msec, no idea why now :-)
73 Alex


Re: DX CMD 13.7.2 , MIcrokeyer II 2nd CAT COM port problems

Joe Subich, W4TV
 

Works just fine for me. Check your settings, including polling rates
(command interval). I have commander set to 160 ms and WSJT-X set to
1 sec.

Make sure that the "Forward autoinformation to CAT port" boxes are
*NOT* checked in Router -> CAT -> SET.

73,

... Joe, W4TV

On 2018-08-11 1:55 PM, Joe wrote:
Hi Dave
after the last update, I have a trouble with the 2nd CAT at the Microkeyer II
My setup since a long time
RX/TX Elecraft K3
Microkeyer II
DXLAB
other digital programs as WSJTX, WinLink....
I configured 1 CAT in MIcrokeyer port 8, 2nd 13
DX commander is using port 8 and everthing is working fine till I use e.g. WSJT-X, CAT port there 13.
Very slow or no reaction at the CAT in WSJT-X.
When I stop DX Commander, everthing is fine, all other CAT needed programms are working.
I have no multiradio and last version of Microham urouter.
Before the update of DX CMD, all was working without troubles
tnx for a hint
73 Alex, OE3JTB


DX CMD 13.7.2 , MIcrokeyer II 2nd CAT COM port problems

Alex OE3JTB
 

Hi Dave
after the last update, I have a trouble with the 2nd CAT at the Microkeyer II

My setup since a long time
RX/TX Elecraft K3
Microkeyer II
DXLAB
other digital programs as WSJTX, WinLink....

I configured 1 CAT in MIcrokeyer port 8, 2nd 13

DX commander is using port 8 and everthing is working fine till I use e.g. WSJT-X, CAT port there 13.
Very slow or no reaction at the CAT in WSJT-X.
When I stop DX Commander, everthing is fine, all other CAT needed programms are working.
I have no multiradio and last version of Microham urouter.

Before the update of DX CMD, all was working without troubles
tnx for a hint

73 Alex, OE3JTB


Re: "Alt shift" sticking in Commander. Am I alone?

Björn SM7IUN
 

Thanks Carl,

This is what I do. I am well aware of Window's UI mechanics. 

As I pointed out in my post I find having to return to Commander to "correct" this is an inconvenience.

A challenge, from a programming perspective, is that the Alt key is still down when Commander loses focus. 
But given the rich set of API in Windows it may be possible to detect this and address the issue. 

73,

Björn SM7IUN


2018-08-11 16:37 GMT+02:00 Carl - WC4H via Groups.Io <wc4h.dx@...>:

I think that what your are seeing it is standard Windows functionality for the Alt key.  You can still add a Tab to get to the desired opened window.  Once you return the focus to Commander (either with the Alt+Tab sequence or by clicking on it), you can just press Alt again and the box will be unchecked.

73.
Carl - WC4H



Re: DXKeeper 14.6.2 is available

Phil Cooper
 

Hi Dave,

 

You wrote:

 

+ Yes, IOTA only reports each Island Group's status once, so only the logged QSO cited in the file downloaded from IOTA gets corrected. DXKeeper could be further extended to automatically change the Island Group associated with all other logged QSOs with the same callsign, but I don't think that would be a good idea, as ops sometimes move from island to island.

I agree, but thought I would mention it in case folk found other QSO's with the same call in the same island, and wanted to correct the IOTA of similar QSO's.

Mine with VK9CX were only a day apart, and they were only on OC-003, so I manually changed the other contact to reflect this.

Not sure it matters a great deal, but wanted my log to be as accurate as possible.

 

73 de Phil GU0SUP


Re: Moving DXLab to new computer problem

Dave AA6YQ
 

+ AA6YQ comments below

Dave - Thanks. I bought the new Dell at Staples and the techs there did a mirror image of the old to the new - thus the incorrect path for Keeper on the new one. Your change fixed it, but the Old laptop still has the Commander address for Keeper and it works.

+ That must mean you have a copy of DXKeeper.exe in your Commander folder.

Should I change that Keeper address as well or leave well enough alone?

+ I would correct it.

Re the Workspace loading to the Flash Drive, I did not use the process you suggested, but will do so.

+ If Dell did a "mirror image", then the contents of the Windows Registry that represents DXLab settings may have already been moved to your new system, making the "Load all settings from Workspace" operation unnecessary.

73,

Dave, AA6YQ


Re: DXKeeper 14.6.2 is available

Dave AA6YQ
 

+ AA6YQ comments below

Hi Dave and the group,

I was very intrigued to read about the new IOTA update function, so I tried it out.

Very impressed with the results, as it meant I have quite a few new matches.

It also changed a few IOTA references for me, and on checking, the changes were correctly applied.

Not sure how I got the wrong IOTA attached to these though, as I don't recall entering them manually.

One example was VK9CX, which I had as IOTA OC-002, but it changed it to OC-003, which is right.


A point to note is that it will only change the ONE contact which must be the one it selects for the award, so you have to manually change others QSO's with the same callsign.

+ Yes, IOTA only reports each Island Group's status once, so only the logged QSO cited in the file downloaded from IOTA gets corrected. DXKeeper could be further extended to automatically change the Island Group associated with all other logged QSOs with the same callsign, but I don't think that would be a good idea, as ops sometimes move from island to island.

73,

Dave, AA6YQ


Re: TQSL error: permission denied

Dave AA6YQ
 

+ AA6YQ comments below

Good morning Dave,

tried the safe mode, but no luck.
First, when TQSL starts, I don't see the window of TQSL, but the program is running.

+ When did this behavior first appear?

+ What changes to your hardware or software were made around that time?

+ How are you starting TQSL?

73,

Dave, AA6YQ


Re: "Alt shift" sticking in Commander. Am I alone?

Carl - WC4H
 

I think that what your are seeing it is standard Windows functionality for the Alt key.  You can still add a Tab to get to the desired opened window.  Once you return the focus to Commander (either with the Alt+Tab sequence or by clicking on it), you can just press Alt again and the box will be unchecked.

73.
Carl - WC4H


"Alt shift" sticking in Commander. Am I alone?

Björn SM7IUN
 

Since I have some UI issues with Commander that I seem completely alone in having (likely due to some not yet identified Windows
setting or interfering software in my PC) I'd like to know if other experience this issue too:

When I have Commander in focus and want to rapidly shift to e.g. Winwarbler without reaching for the mouse I use Windows' Alt-Tab shortcut.

This works well, apart from the fact that the "ALT" box in the User-defined Controls section becomes checked and stays that way.
This means the secondary set of buttons and sliders are now shown indefinitely, or until I manually uncheck it with the mouse. 
It is a bit of an inconvenience. 

My first question is if others see this also? 

If this is the case, my second question is for Dave; is this possible to fix?

73,

Björn SM7IUN





Re: Moving DXLab to new computer problem

Alan Swinger
 

Dave - Thanks. I bought the new Dell at Staples and the techs there did a mirror image of the old to the new - thus the incorrect path for Keeper on the new one. Your change fixed it, but the Old laptop still has the Commander address for Keeper and it works. Should I change that Keeper address as well or leave well enough alone?

Re the Workspace loading to the Flash Drive, I did not use the process you suggested, but will do so.

As always. Thanks. Will likely have more questions later.
All the best - Alan K9MBQ

On Fri, Aug 10, 2018 at 10:31 PM, Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Am trying to Install DXLabs and move from old PC to new one, and am following the DXLab Wiki . . and have done before all OK.

Have done all the normal stuff - TQSL & LTW to the new PC; Have workspace backed up and on a Flash drive; used Launcher to install Apps in DXLab on C-drive.
When trying to upload stored Workspace to Launcher workspace DXKeeper showed an update Available . . .  in this process I lost the Installed Keeper App.

+ A Workspace is a folder. There is nothing to "upload". Did you restore your settings from the Workspace on your Flash drive by following the "Loading the Windows Registry with All Settings from a Workspace" directions in

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

+ ?

So, in the Launcher CINFIG "installed" SPOT there is a Blank for DXKeeper. "AVAIL" shows in RED 14.5.7 and "ACTION" says "UPGRADE".
- HOW DO I GET keeper RE-INSTALLED?
- When clicking on DXKeeper, msg says (C:\DXLab\Commander\DXKeeper.exedoesnot exist)

+ That's because the wrong pathname is specified. DXKeeper.exe does not reside in C:\DXLab\Commander !

+ On the "DXLab Apps" tab of the Launcher's Configuration window, set the "Program Path" for DXKeeper to

C:\DXLab\DXKeeper\DXKeeper.exe

        73,

           Dave, AA6YQ







Re: DXKeeper 14.6.2 is available

Phil Cooper
 

Hi Dave and the group,

 

I was very intrigued to read about the new IOTA update function, so I tried it out.

Very impressed with the results, as it meant I have quite a few new matches.

It also changed a few IOTA references for me, and on checking, the changes were correctly applied.

Not sure how I got the wrong IOTA attached to these though, as I don't recall entering them manually.

One example was VK9CX, which I had as IOTA OC-002, but it changed it to OC-003, which is right.

 

A point to note is that it will only change the ONE contact which must be the one it selects for the award, so you have to manually change others QSO's with the same callsign.

 

73 de Phil GU0SUP

 

 

-----Original Message-----
From: "Dave AA6YQ" <aa6yq@...>
Sent: Saturday, 11 August, 2018 02:16
To: DXLab@groups.io
Subject: [DXLab] DXKeeper 14.6.2 is available

This release

- includes CM89 in the FFMA.txt script (tnx to Bryan W3CP)

- when submitting QSOs to LoTW, prevents erroneous "RX band and RX frequency are inconsistent" error messages (tnx to Tapio OH3HN)

- ensures that the Cabrillo Export function is properly configured for NAQP contests (tnx to Mike W3QT)

- warns the user on attempting to save a myQTH with fields containing too much data (tnx to Paul W2ECK)

- provides the option to log each imported QSO with the SFI/A/K specified on the Configuration window's Defaults tab substituting
for SFI, A, and K information not present in the imported QSO; the SFI/A/K specified on the Configuration window's Defaults tab is
updated by SpotCollector, if running (tnx to Peter W2IRT)

- adds Kazakhstan Oblasts to the primary subdivision database (tnx to Joe W4TV)

- changes the name of Croatian primary subdivisions from Županija to Zupanija (tnx to Björn SM7IUN)

- generates SOTA Activator progress reports and submission files, employing a User-defined item whose caption is set to MY_SOTA_REF
(tnx to Brad W6BJB/JS6TQS)

- enables the IOTA Update function to update logged QSOs with confirmation information from a "myqsos.csv" file that the user has
downloaded from https://iota-world.org/ (tnx to Salvatore I4FYV, Valeria IK1ADH, and Johan PA3EXX)

- updates all documentation files (HTTP => HTTPS)


Notes:


1. The reason that the user must manually login to https://iota-world.org/ and download his or her "myqsos.csv" file is that no
programmatic interface is available; if and when one becomes available, DXKeeper will be extended to exploit it.


2. Update your firewall and anti-malware applications to consider this new version of DXKeeper to be "safe"


3. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>


4. After upgrading, to revert to the previous version of DXKeeper, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>



DXKeeper 14.6.2 is available via the DXLab Launcher and via

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







Re: TQSL error: permission denied

Gerhard "Gary" Jaeger, DF2RG
 

Good morning Dave,

tried the safe mode, but no luck.
First, when TQSL starts, I don't see the window of TQSL, but the program is
running.
Then, I tried to run DXKeeper, and the same error comes up.
This time I see the window with the error message.

What else can I do?

73 de Gary, DF2RG

-----Ursprüngliche Nachricht-----
Von: DXLab@groups.io <DXLab@groups.io> Im Auftrag von Dave AA6YQ
Gesendet: Samstag, 11. August 2018 08:30
An: DXLab@groups.io
Betreff: Re: [DXLab] TQSL error: permission denied

+ AA6YQ comments below

Ran into a small problem yesterday:

Suddenly, I cannot upload from DXKeeper to LotW.

I get the following error message:

Error writing certificate status file
(C:\Users\df2rg\AppData\Roaming\TrustedQSL\cert_status.xml) :
ios_base::failbit set/Permission denied

+ Reboot Windows into "safe mode with networking", and try again. What
happens?

73,

Dave, AA6YQ


Re: TQSL error: permission denied

Dave AA6YQ
 

+ AA6YQ comments below

Ran into a small problem yesterday:

Suddenly, I cannot upload from DXKeeper to LotW.

I get the following error message:

Error writing certificate status file (C:\Users\df2rg\AppData\Roaming\TrustedQSL\cert_status.xml) : ios_base::failbit set/Permission
denied

+ Reboot Windows into "safe mode with networking", and try again. What happens?

73,

Dave, AA6YQ


TQSL error: permission denied

Gerhard "Gary" Jaeger, DF2RG
 

Hi Dave and DXLAB group,

 

Ran into a small problem yesterday:

Suddenly, I cannot upload from DXKeeper to LotW.

I get the following error message:

Error writing certificate status file (C:\Users\df2rg\AppData\Roaming\TrustedQSL\cert_status.xml) : ios_base::failbit set/Permission denied

 

I did the repair function of TQSL, but no change.

 

Any hint, thanks in advance.

 

73 de Gary, DF2RG


Re: Moving DXLab to new computer problem

Dave AA6YQ
 

+ AA6YQ comments below

Am trying to Install DXLabs and move from old PC to new one, and am following the DXLab Wiki . . and have done before all OK.

Have done all the normal stuff - TQSL & LTW to the new PC; Have workspace backed up and on a Flash drive; used Launcher to install Apps in DXLab on C-drive.
When trying to upload stored Workspace to Launcher workspace DXKeeper showed an update Available . . . in this process I lost the Installed Keeper App.

+ A Workspace is a folder. There is nothing to "upload". Did you restore your settings from the Workspace on your Flash drive by following the "Loading the Windows Registry with All Settings from a Workspace" directions in

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

+ ?

So, in the Launcher CINFIG "installed" SPOT there is a Blank for DXKeeper. "AVAIL" shows in RED 14.5.7 and "ACTION" says "UPGRADE".
- HOW DO I GET keeper RE-INSTALLED?
- When clicking on DXKeeper, msg says (C:\DXLab\Commander\DXKeeper.exedoesnot exist)

+ That's because the wrong pathname is specified. DXKeeper.exe does not reside in C:\DXLab\Commander !

+ On the "DXLab Apps" tab of the Launcher's Configuration window, set the "Program Path" for DXKeeper to

C:\DXLab\DXKeeper\DXKeeper.exe

73,

Dave, AA6YQ


Re: Moving DXLab to new computer problem

Stan KM4HQE <s_gammons@...>
 

When you run DXLab Launcher and click on config, it should have install listed under the action column if that application isn't installed.  Clicking the install button should install it.

hth

73

Stan
KM4HQE


On 08/10/2018 08:50 PM, Alan Swinger wrote:
Am trying to Install DXLabs and move from old PC to new one, and am following the DXLab Wiki . . and have done before all OK.

Have done all the normal stuff - TQSL & LTW to the new PC; Have workspace backed up and on a Flash drive; used Launcher to install Apps in DXLab on C-drive.
When trying to upload stored Workspace to Launcher workspace DXKeeper showed an update Available . . .  in this process I lost the Installed Keeper App. So, in the Launcher CINFIG "installed" SPOT there is a Blank for DXKeeper. "AVAIL" shows in RED 14.5.7 and "ACTION" says "UPGRADE".
- HOW DO I GET keeper RE-INSTALLED?
- When clicking on DXKeeper, msg says (C:\DXLab\Commander\DXKeeper.exedoesnot exist)

What actions do you suggest to restore the DXKeeper app?


Moving DXLab to new computer problem

Alan Swinger
 

Am trying to Install DXLabs and move from old PC to new one, and am following the DXLab Wiki . . and have done before all OK.

Have done all the normal stuff - TQSL & LTW to the new PC; Have workspace backed up and on a Flash drive; used Launcher to install Apps in DXLab on C-drive.
When trying to upload stored Workspace to Launcher workspace DXKeeper showed an update Available . . .  in this process I lost the Installed Keeper App. So, in the Launcher CINFIG "installed" SPOT there is a Blank for DXKeeper. "AVAIL" shows in RED 14.5.7 and "ACTION" says "UPGRADE".
- HOW DO I GET keeper RE-INSTALLED?
- When clicking on DXKeeper, msg says (C:\DXLab\Commander\DXKeeper.exedoesnot exist)

What actions do you suggest to restore the DXKeeper app?


DXKeeper 14.6.2 is available

Dave AA6YQ
 

This release

- includes CM89 in the FFMA.txt script (tnx to Bryan W3CP)

- when submitting QSOs to LoTW, prevents erroneous "RX band and RX frequency are inconsistent" error messages (tnx to Tapio OH3HN)

- ensures that the Cabrillo Export function is properly configured for NAQP contests (tnx to Mike W3QT)

- warns the user on attempting to save a myQTH with fields containing too much data (tnx to Paul W2ECK)

- provides the option to log each imported QSO with the SFI/A/K specified on the Configuration window's Defaults tab substituting
for SFI, A, and K information not present in the imported QSO; the SFI/A/K specified on the Configuration window's Defaults tab is
updated by SpotCollector, if running (tnx to Peter W2IRT)

- adds Kazakhstan Oblasts to the primary subdivision database (tnx to Joe W4TV)

- changes the name of Croatian primary subdivisions from Županija to Zupanija (tnx to Björn SM7IUN)

- generates SOTA Activator progress reports and submission files, employing a User-defined item whose caption is set to MY_SOTA_REF
(tnx to Brad W6BJB/JS6TQS)

- enables the IOTA Update function to update logged QSOs with confirmation information from a "myqsos.csv" file that the user has
downloaded from https://iota-world.org/ (tnx to Salvatore I4FYV, Valeria IK1ADH, and Johan PA3EXX)

- updates all documentation files (HTTP => HTTPS)


Notes:


1. The reason that the user must manually login to https://iota-world.org/ and download his or her "myqsos.csv" file is that no
programmatic interface is available; if and when one becomes available, DXKeeper will be extended to exploit it.


2. Update your firewall and anti-malware applications to consider this new version of DXKeeper to be "safe"


3. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>


4. After upgrading, to revert to the previous version of DXKeeper, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>



DXKeeper 14.6.2 is available via the DXLab Launcher and via

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


Re: S meter

Dave AA6YQ
 

+ AA6YQ comments below

Dave the problem with my S meter not reading the smeter file correctly was that when the 7851/51 file was created it was named
IC-7850 instead of IC-7851. Although I don't remember creating the file. I guess I must have.

+ Commander includes an IC-7850 S-meter file that someone contributed. If you send me your IC-7851 file, I will include it with
future Commander releases.

73,

Dave, AA6YQ

28761 - 28780 of 208071