Date   

Re: DXLab Commander connection to HF-AUTO SW

Jon Gefaell
 

On Fri, Feb 26, 2021 at 04:13 PM, Norm - KC1BMD wrote:
Terry Glagowski / W1TR developed an application called HFAUTO SW to control the Palstar HF-AUTO ATU. I installed it and connected to to DXLab Commander via the [Net Serv] configuration.
How very nice! I've downloaded and installed it. Thanks for the heads up. Can you tell me more about the [Net Serv] configuration, please? 


Re: DXKeeper - LotW Sync QSO and QSLs - Not Responding

Jon Gefaell
 

On Sat, Feb 27, 2021 at 04:47 PM, Dave AA6YQ wrote:

+ The fact that Windows displays a separate window offering to stop DXKeeper or continue waiting is also unique to your situation.

I look forward to hearing back from the OP whether waiting has resolved his concern. Or maybe I missed that?

+ You have reported that the LoTW Sync functions work if you start DXKeeper immediately after rebooting Windows; that likely rules out interference from anti-malware or firewall applications automatically started by Windows, since they were running when you reported success. 

Agreed. I never, ever run anti-malware software. They're the main source of problems. IMO, but YMMV, of course. I do run regular standalone scans and always come up clean. The built-in Windows 10 firewall does its thing, and my Unifi Software Defined Network's firewall is doing a lovely job as well. But agreed, what's in place is in place when it works and when it doesn't. 

+ If you (understandably) cannot diagnose Windows yourself, then I suggest engaging with Microsoft Support to obtain their assistance in tracking down the root cause of this behavior.

I can't help but chuckle at the notion. "Hello, DX Keeper is has failures to sync LoTW QSLs for me but works for others." ;)

The *only* reason I run Windows, which I despise, is because of amateur radio. With DX Lab Suite square at the center. I couldn't even consider anything else.

I think this is my cross to bear, on my own. As problems go, it's pretty mild. Grin. 

Thanks as always for your efforts.


Re: DXKeeper - LotW Sync QSO and QSLs - Not Responding

Dave AA6YQ
 

+ AA6YQ comments below

Thank you, Dave. I just did this again so that I could explain it carefully. Hopefully, this is useful at some point. I'm delighted to be discussing this, thank you.

I selected "Sync LOTW QSLs." The progress dialogue pops up and halts at 59 seconds. The title bar displays 'not responding,' and shortly thereafter, the windows dialogue comes up, saying the same thing and offering a choice of stopping the program or waiting. I select to wait. The DXKeeper windows (main, capture, and the QSL sync progress) are shaded. I have been waiting 35 minutes with no change.

Memory is 41% utilized, CPU is 40%, Disk and Network are 0%, and GPU is 8%. I don't have the skills to look into the number of open file handles, etc. But there are no other evident issues with closing, opening, and using numerous applications that would consume additional resources, open file handles and network connections, allocating memory, etc. 

I'll keep at it. It feels like a blocking issue. One day I'll find my gremlin. :) Thanks again, sir!

+ The fact that Windows displays a separate window offering to stop DXKeeper or continue waiting is also unique to your situation..

+ You have reported that the LoTW Sync functions work if you start DXKeeper immediately after rebooting Windows; that likely rules out interference from anti-malware or firewall applications automatically started by Windows, since they were running when you reported success. 

+ If you (understandably) cannot diagnose Windows yourself, then I suggest engaging with Microsoft Support to obtain their assistance in tracking down the root cause of this behavior.

        73,

                Dave, AA66YQ

 


Re: Lat & Long

Dave AA6YQ
 

+ AA6YQ comments below
Just set up DXLab Suite on a new laptop... all went well but an issue with Lat/long in DX View and Prop View.

My QTHID Lat/Long is correct for my home QTH. [45 31' 14" N 76 37' 30" W] in DXK & SC....

DXVIEW General Tab Lat/Long... was incorrect [45 48' 45" N  63 52' 30" W] so I changed it to my Home QTH lat/long. ( This also changes My Home QTH on DX Atlas). 

Prop View Parameter Tab Lat/long was incorrect [45 48' 45" N  63 52' 30" W] so I changed it to my Home QTH lat/long. 

I save all my settings to a workspace BUT when I opened up all the apps again the lat/long for both DXVIEW and Prop View changed  and neither app keeps my home QTH's Lat/long.

+ When you start DXView and PropView, what latitude and longitude do each display for your QTH?

     73,

             Dave, AA6YQ

 


Re: DXKeeper - LotW Sync QSO and QSLs - Not Responding

Jon Gefaell
 

On Sat, Feb 27, 2021 at 02:05 PM, Dave AA6YQ wrote:
+ For the record, I frequently see the "not responding" message in window title bars -- including in the title bars of Microsoft applications. Letting the operation run to completion invariably succeeds.

Thank you, Dave. I just did this again so that I could explain it carefully. Hopefully, this is useful at some point. I'm delighted to be discussing this, thank you.

I selected "Sync LOTW QSLs." The progress dialogue pops up and halts at 59 seconds. The title bar displays 'not responding,' and shortly thereafter, the windows dialogue comes up, saying the same thing and offering a choice of stopping the program or waiting. I select to wait. The DXKeeper windows (main, capture, and the QSL sync progress) are shaded. I have been waiting 35 minutes with no change.

Memory is 41% utilized, CPU is 40%, Disk and Network are 0%, and GPU is 8%. I don't have the skills to look into the number of open file handles, etc. But there are no other evident issues with closing, opening, and using numerous applications that would consume additional resources, open file handles and network connections, allocating memory, etc. 

I'll keep at it. It feels like a blocking issue. One day I'll find my gremlin. :) Thanks again, sir!

 


Lat & Long

Curt Bowles
 

Hi Dave...

Just set up DXLab Suite on a new laptop... all went well but an issue with Lat/long in DX View and Prop View.

My QTHID Lat/Long is correct for my home QTH. [45 31' 14" N 76 37' 30" W] in DXK & SC....

DXVIEW General Tab Lat/Long... was incorrect [45 48' 45" N  63 52' 30" W] so I changed it to my Home QTH lat/long. ( This also changes My Home QTH on DX Atlas). 

Prop View Parameter Tab Lat/long was incorrect [45 48' 45" N  63 52' 30" W] so I changed it to my Home QTH lat/long. 

I save all my settings to a workspace BUT when I opened up all the apps again the lat/long for both DXVIEW and Prop View changed  and neither app keeps my home QTH's Lat/long.

This is repeatable so I suspect maybe a setting is not correct but I can't find what is causing this1 Help Pse.

73


--
Curt Bowles
VE3ZN


testing help sought: additional support for the Yaesu FTDX-10

Dave AA6YQ
 

I have extended Yaesu FTDX-10 support in the next version of Commander to provide the ability to specify a default width and a
default shift for each of 7 modes, with the option to automatically set the specified width and shift after a mode change:

www.dxlabsuite.com/commander/FTDX-10%20default%20bandwidth%20by%20mode.jpg

After getting this working with an FTDX-10, my plan is to provide similar support for other recent Yaesu transceivers (3000, 1200,
991, 891, 9000, 5000, 2000, 950, 450).

If you have a Yaesu FTDX-10 and would be willing to test this new version, please send email to me via

aa6yq (at) ambersoft.com

Note: the Yaesu FTDX-10 documentation does not specify the available widths when the transceiver is operating in AM or FM, so
reverse engineering these will be part of the fun!

73,

Dave, AA6YQ


Re: Support for icom ID-5100

Dave AA6YQ
 

+ AA6YQ comments below

Hi, is support for ID-5100 planned ? It already almost works using othe models.

+ 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.

73,

Dave, AA6YQ


Re: Support for icom ID-5100

Peter Laws / N5UWY
 

On Sat, Feb 27, 2021 at 4:23 PM <nicolas.mailloux@micronick.com> wrote:

Hi, is support for ID-5100 planned ? It already almost works using othe rmodels.
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.



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


Support for icom ID-5100

nicolas.mailloux@...
 

Hi, is support for ID-5100 planned ? It already almost works using othe rmodels.


Re: LoTW and eQSL status of QSO's uploaded from HRD Logbook

Dave AA6YQ
 

+ AA6YQ comments below

I'd like to know if it matters whether I uploaded the QSO's using HRD instead of using DXKeeper (i.e. does DXKeeper care)?

+ LoTW doesn't know which application submitted QSOs, and so can't report this information when directed to provide it.

I understood that LoTW would not know how data was submitted but thought DXKeeper might care if it tracked whether it uploaded the data or not. But OK, I understand. After looking at my log more carefully, it seems that the eQSL and LoTW data was populated when I imported the ADIF, so I think I only have the 18 newest QSO's to sync for both online systems.

Maybe I'll switch from HRD logbook to DXKeeper for everything if I can get accustomed to it. The capabilities (and number of configuration items) is a little daunting and there lots of ways to mess things up, whereas the HRD Logbook could be used as a graphic on "Logging for Dummies" (hi). I do back up my DXK log on exit, so that should help if I run into problems.

+ DXLab was designed for users willing to make the investment of time required to effectively use its advanced capabilities. Yes, being able to modify thousands of QSOs en masse means that you can "mess things up" if you haven't ever reviewed the documentation and fail to backup your log beforehand - but it's mighty handy when you've imported a file of QSOs whose times were recorded in PST instead of UTC, or whose Station Callsign items are all incorrect. Yes, it takes time to learn how to exploit SpotCollector's Spot Database to identify propagation openings between your QTH and needed DX stations, and to discern the operating patterns of those needed DX stations; aggressive DXers are happy to traverse that learning curve - rather than spend time in pileups with the cluster hordes.

+ There's nothing wrong with using a simpler application if it better meets your needs.

73,

Dave, AA6YQ


Re: DXKeeper - LotW Sync QSO and QSLs - Not Responding

Dave AA6YQ
 

+ AA6YQ comments below

* That's a likely symptom of resource exhaustion, Windows misconfiguration, or a latent defect in Windows - which is why I posted the above advice.

I've re-read both my description and his. They seem complimentary. There may be an issue of semantics, and my choice of words to describe the issue may benefit from fine-tuning. I would appreciate some insight as to how our two reports are crucially different.

+ Hank reported the appearance of "not responding" in DXKeeper's Main window's title bar, and (understandably) misinterpreted it to mean that the Sync process was not proceeding. My advice is to let the operation run to completion, ignoring the "not responding" message.

+ You reported that unless you start DXKeeper alone after rebooting, DXKeeper never completes the Sync process. The fact that the Sync process runs to completion when your instance of Windows has been freshly rebooted is what points to a resource management or misconfiguration issue in Windows.

+ For the record, I frequently see the "not responding" message in window title bars -- including in the title bars of Microsoft applications. Letting the operation run to completion invariably succeeds.

73,

Dave. AA6YQ


Re: LoTW and eQSL status of QSO's uploaded from HRD Logbook

Norm - KC1BMD
 

On Sat, Feb 27, 2021 at 04:34 PM, Dave AA6YQ wrote:
I'd like to know if it matters whether I uploaded the QSO's using HRD instead of using DXKeeper (i.e. does DXKeeper care)?

+ LoTW doesn't know which application submitted QSOs, and so can't report this information when directed to provide it.
I understood that LoTW would not know how data was submitted but thought DXKeeper might care if it tracked whether it uploaded the data or not. But OK, I understand. After looking at my log more carefully, it seems that the eQSL and LoTW data was populated when I imported the ADIF, so I think I only have the 18 newest QSO's to sync for both online systems.

Maybe I'll switch from HRD logbook to DXKeeper for everything if I can get accustomed to it. The capabilities (and number of configuration items) is a little daunting and there lots of ways to mess things up, whereas the HRD Logbook could be used as a graphic on "Logging for Dummies" (hi). I do back up my DXK log on exit, so that should help if I run into problems.

I book marked the main index of the Wiki too, so it should enhance my searching for user information. Thanks very much to all for this info!

--
73, Norm/KC1BMD


Re: DXKeeper - LotW Sync QSO and QSLs - Not Responding

Jon Gefaell
 

Thanks, Dave. I greatly appreciate your advice. I prefer my workaround of rebooting and starting DXKeeper by itself, performing the sync, and starting the rest of the software I use. I really like the integration and automation that is provided by DXKeeper. My system reboots in about 20-30 seconds, so it's no problem. :)

On Sat, Feb 27, 2021 at 01:46 PM, Dave AA6YQ wrote:

# Until you diagnose and repair your system, here's a workaround to consider when you want to "Sync LoTW QSLs":


Re: DXKeeper - LotW Sync QSO and QSLs - Not Responding

Jon Gefaell
 

On Sat, Feb 27, 2021 at 01:39 PM, Dave AA6YQ wrote:
* That's a likely symptom of resource exhaustion, Windows misconfiguration, or a latent defect in Windows - which is why I posted the above advice.

I've re-read both my description and his. They seem complimentary. There may be an issue of semantics, and my choice of words to describe the issue may benefit from fine-tuning. I would appreciate some insight as to how our two reports are crucially different.

 

At any rate, as I stated, however:

"Something your and my systems are doing is causing the issue, but it's elusive and does not seem to be experienced by others. This certainly seems to explicate DX Keeper."

I run an eight-core i7 with 64GB of RAM and have over 1GB of free space on my NVME SSD's. Resource monitoring shows vast amounts of headroom in terms of processor, network bandwidth, and memory utilization. I have no issues with my system and the many things it does. So, it's elusive. I'm going with a latent defect in Windows, but what is triggering it is... inexplicable.

It's a small bother to work around the issue, and certainly not a DX Keeper defect. I wish I was nearly as handy with system analysis in Windows as I am with *nix. I'd be all over it.  Thanks for your wonderful software and the effort you put into ensuring it interoperates with everything so well. There is nothing that comes close.


Re: DXKeeper - LotW Sync QSO and QSLs - Not Responding

Dave AA6YQ
 

# Even more AA6YQ comments below

You're not alone. I reported this same issue in this thread https://groups.io/g/DXLab/topic/78720234#197922

and was advised:

+ Your next step should be to diagnose and correct your Windows system.

* Your report in the above-cited thread is entirely different. In that thread, you reported

"This only seems to happen when I have the entire DX Lab Suite of programs up and running. If I start from a fresh reboot, and only start DX Keeper I can successfully perform the sync functions. Sometimes merely closing the other DX Lab Suite programs will result in the sync functions working."

* That's a likely symptom of resource exhaustion, Windows misconfiguration, or a latent defect in Windows - which is why I posted the above advice.


# Until you diagnose and repair your system, here's a workaround to consider when you want to "Sync LoTW QSLs":

1. check the "PC has no internet connection" box on the "QSL Configuration" window's LotW tab

2. follow the instructions in the "Obtaining New Confirmations from LoTW" section of " Uploading to LotW and Synchronizing with LotW from a PC not connected to the internet" in

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

3. use your web browser to download the file from LoTW and save it to the specified location, and then click the OK button to trigger DXKeeper's processing of that information.

4. uncheck the "PC has no internet connection" box on the "QSL Configuration" window's LotW tab

73,

Dave, AA6YQ


Re: DXKeeper - LotW Sync QSO and QSLs - Not Responding

Dave AA6YQ
 

* AA6YQ comments below

You're not alone. I reported this same issue in this thread https://groups.io/g/DXLab/topic/78720234#197922

and was advised:

+ Your next step should be to diagnose and correct your Windows system.

* Your report in the above-cited thread is entirely different. In that thread, you reported

"This only seems to happen when I have the entire DX Lab Suite of programs up and running. If I start from a fresh reboot, and only start DX Keeper I can successfully perform the sync functions. Sometimes merely closing the other DX Lab Suite programs will result in the sync functions working."

* That's a likely symptom of resource exhaustion, Windows misconfiguration, or a latent defect in Windows - which is why I posted the above advice.

73,

Dave, AA6YQ


Re: LoTW and eQSL status of QSO's uploaded from HRD Logbook

Dave AA6YQ
 

+ AA6YQ comment sbeloe

I'd like to know if it matters whether I uploaded the QSO's using HRD instead of using DXKeeper (i.e. does DXKeeper care)?

+ LoTW doesn't know which application submitted QSOs, and so can't report this information when directed to provide it.

The LoTW Sync button on the QSL tab says that QSO's will be downloaded. I don't want to download QSO's that I already have in my log. I only want to update the QSL confirmation status. Unless I can get clarification

+ You can "get clarification" by reading this section of the reference documentation:

https://www.dxlabsuite.com/dxkeeper/Help/QSL.htm#Updating_Logged_QSOs_to_their_Reflect_Acceptance_and_Confirmation_by_LotW

+ The fact that DXKeeper's "Sync LoTW QSOs" and "Sync LoTW QSLs" functions update logged QSOs with information obtained from LoTW is also described here:

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

73,

Dave, AA6YQ


Re: LoTW and eQSL status of QSO's uploaded from HRD Logbook

Joe Subich, W4TV
 

On 2021-02-27 4:09 PM, Norm - KC1BMD wrote:
I'd like to know if it matters whether I uploaded the QSO's using HRD
instead of using DXKeeper (i.e. does DXKeeper care)? The LoTW Sync
button on the QSL tab says that **QSO's will be downloaded. **I don't
want to download QSO's that I already have in my log.
While DXKeeper downloads QSOs/QSLs when doing a "sync" operation, those
QSOs are *not* added to the log, the status of the matching QSOs in
the log are updated.

73,

... Joe, W4TV


On 2021-02-27 4:09 PM, Norm - KC1BMD wrote:
I'd like to know if it matters whether I uploaded the QSO's using HRD instead of using DXKeeper (i.e. does DXKeeper care)? The LoTW Sync button on the QSL tab says that **QSO's will be downloaded. **I don't want to download QSO's that I already have in my log. I only want to update the QSL confirmation status. Unless I can get clarification it might be easier for me to just continue exporting my DXKeeper QSO's to ADIF, importing them to HRD logbook and from there uploading/downloading with LoTW and eQSL and tracking the status in HRD, which is what I have been doing anyway since installing the DXLab Suite a couple of weeks ago..
--
73, Norm/KC1BMD


Re: LoTW and eQSL status of QSO's uploaded from HRD Logbook

Dave AA6YQ
 

+ AA6YQ comments below

My log was imported from an ADIF file generated from HRD Logbook after I installed DXKeeper. I had already uploaded the QSO's to LoTW and eQSL using HRD Logbook. I would like to get the confirmed status from LoTW and eQSL into DXKeeper. I'm a little confused about what I need to do. If this is possible, what would be the easiest way to proceed to just update the eQSL and LoTW confirmed status in DXKeeper. Anything I need to be careful about?

+ The step-by-step procedure for LoTW is here:

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

+ Depending on how many QSOs you've submitted to LoTW, this can take awhile. My advices is to start it before retiring for the evening. Don't be fooled by "not responding" appearing in DXKeeper's Main window title bar; that's just Microsoft's (user hostile) way of informing you that the application is waiting for information being downloaded.

+ For eQSL.cc, set the "QSL Via" panel on the Main window's QSL tab to "eQSL.cc" and then depress the CTRL key while clicking the "Sync eQSL.cc QSLs" button; this operation can also take a while.

73,

Dave, AA6YQ

2701 - 2720 of 202739