¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: Spotcollector: Needed does shown new WAZ zones

 

+ AA6YQ comments below

As the title says, new CQ/WAZ zones are not shown as "Needed" in SC.
(New DXCC entities are shown ok).
I have tried to look at settings but I can't see what is wrong.

+ Please make a screen shot showing the Awards tab of DXKeeper's Configuration window, attach the screen shot to an email message, and send the email message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


Sync LOTW QSL's problem

 

I have a new problem. It started with trying to sync LOTW QSL's in DXKeeper. It was working fine and then I started getting a message that the program was not responding. I am not sure what happened then but now it says LOTW responded but not with qsl data. I have a box that ask that I check my account name and password in LOTW QSL configuration. I had checked and that information is correct. All other functions of DXKeeper seem to be working all OK. I can log a QSO with WSJT or the capture window and it is saved to DXKeeper and uploaded to LOTW as usual. I tried rebooting the computer with no luck. I tried to boot in safe mode but it seems that when the Windows 10 PRO operating system was installed in my PC there was a bit code established and since it was done by someone else I can't access it. Why does Windows always seem to fight you when you have a problem?

Any ideas greatly appreciated. <<John


Spotcollector: Needed does shown new WAZ zones

 

As the title says, new CQ/WAZ zones are not shown as "Needed" in SC.
(New DXCC entities are shown ok).
I have tried to look at settings but I can't see what is wrong.


73 de SM5FLM


Re: Now what?

 

Have to say that I read an earlier post about this and looked at Dave¡¯s link about programs that interfere with DX labs, and I had two of them, Kasper antivirus & Logitech setpoint, for my mouse and keyboard. Uninstalled those And everything is back to running great again. Hope this helps also.

And been following support here for a while and they are Great, and there response time is even better. Thanks to Dave and all behind the scenes. ????

N8ND , Michael L Collins

On Mar 6, 2020, at 6:49 PM, Dave AA6YQ <aa6yq@...> wrote:

?+ AA6YQ comments below

Thanks, Dave. I'll investigate. I hate this when things are "normal," turn off the PC, turn it on the next day, and this crap happens.....

+ If your anti-malware applications are configured to automatically update, reconfigure them to prevent that from happening. Then when you're notified that an update is available, authorize it at a time of your choosing, when you can deal with any adverse side effects without negatively impacting your radio activities.

73,

Dave, AAY6YQ





Re: Minor CAPTURE editing tweak request for DXKeeper

 

* More AA6YQ comments below

On Fri, Mar 6, 2020 at 04:25 PM, Dave AA6YQ wrote:


A minor tweak to DXKeeper would be appreciated.
- When pasting a Callsign into the DXKeeper Capture CALL field, the LOOKUP is successful. However, when LOG is pressed, the error "Callsign is invalid" occurs. Recreation of the situation is by pasting (not typing) a Callsign that has a trailing space.

+ I just tested pasting a callsign with a trailing space into the Capture window. Striking the Enter key to populate the Capture window with a DXCC entity, and clicking the Capture window's Log
button results in the QSO being correctly logged. That's because DXKeeper removes any leading or trailing spaces before logging the callsign.

* The difference in behavior is attributable to the fact that Neil had DXKeeper's "Flag invalid callsigns" option enabled, and I did not.

* Since DXKeeper removes leading or trailing spaces from a callsign pasted into the Capture window's Call box before logging a QSO, the next version of DXKeeper won't consider a Callsign pasted into the Capture window to be invalid if it has leading or trailing spaces.?

* (Don't report an error that will automatically be corrected").

? ? ? 73,

? ? ? ? ? ? ?Dave, AA6YQ

?


Re: Tracking SatPC32 frequencies and sending to SDR Console

 

+ AA6YQ comments below

I'm trying to get Commander to send frequency data to SDR Console via Commanders Secondary CAT port when it is connected to SatPC32. I don't seem to be able to do this. If I switch Commander to my HF rig (MultiRadio) it will happily send the HF frequency to SDR Console so the function works; just not with SatPC32. Anyone know how to make this work or is it that the SatPC32 DDE connection doesn't tie into the Secondary CAT port?

+ I sent you a new version of Commander that enables the Secondary CAT port to follow the uplink or downlink frequency when interoperating with SATPC32. Have you received it?

73,

Dave, AA6YQ


Re: Minor CAPTURE editing tweak request for DXKeeper

 

+ AA6YQ comments below

A minor tweak to DXKeeper would be appreciated.
- When pasting a Callsign into the DXKeeper Capture CALL field, the LOOKUP is successful. However, when LOG is pressed, the error "Callsign is invalid" occurs. Recreation of the situation is by pasting (not typing) a Callsign that has a trailing space.

+ I just tested pasting a callsign with a trailing space into the Capture window. Striking the Enter key to populate the Capture window with a DXCC entity, and clicking the Capture window's Log button results in the QSO being correctly logged. That's because DXKeeper removes any leading or trailing spaces before logging the callsign.

73,

Dave, AAA6YQ


Re: Now what?

 

+ AA6YQ comments below

Thanks, Dave. I'll investigate. I hate this when things are "normal," turn off the PC, turn it on the next day, and this crap happens.....

+ If your anti-malware applications are configured to automatically update, reconfigure them to prevent that from happening. Then when you're notified that an update is available, authorize it at a time of your choosing, when you can deal with any adverse side effects without negatively impacting your radio activities.

73,

Dave, AAY6YQ


Re: Now what?

 

Thanks, Dave.? I'll investigate.? I hate this when things are "normal," turn off the PC, turn it on the next day, and this crap happens.....

Incredible support! (as so many others have noted....)

73,
Steve

On Fri, Mar 6, 2020 at 5:40 PM Dave AA6YQ <aa6yq@...> wrote:
* more AA6YQ comments below

Yep!? Pops up in a heartbeat!

* That likely means an application being automatically started by a normally booted Windows is interfering with your DXLab applications. A misconfigured or incompetent antimalware application is usually the culprit. See

<>

? ? ? 73,

? ? ? ? ? ? Dave, AA6YQ



On Fri, Mar 6, 2020 at 5:11 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Asking for guidance before I totally screw something up....

Turned on the shack computer this morning, started Launcher as usual.? DXK is the first to start...window pops up:? DXKeeper did not open in 180 seconds (or something like that).? Launcher goes on to open DXV and SC.? Button under DXK is still red, so I click again.? "DXKeeper is already running on this computer."? ???? After about 30 seconds, up pops DXK!? So, I figure a minor glitch and move on.

Later this afternoon, started the shack machine again.? This time a similar sequence, but DXK never came up.? Tried to terminate it via Launcher - even with CTRL-click, and got the message "wait for DXKeeper to start" (or something like that).? Rebooted, all that sort of thing (multiple times).? Turned on error logging in Launcher, started again...same thing.? Only this time after about 5 minutes, UP pops DXK!? I've saved my log (again), but not tried a restore of WS on the fear I'll screw up the last good save.

Ideas?? Anything obvious (that clearly isn't obvious to me)?

+ This is a diagnostic procedure:

1. reboot Windows into "Safe mode with networking"

2. start the Launcher

3. direct the Launcher to start DXKeeper (or allow it to start DXKeeper, if that's how you have the Launcher configured)

4. does DXKeeper start?

? ? ?73,

? ? ? ? ? ? Dave, AA6YQ









Re: Now what?

 

* more AA6YQ comments below

Yep! Pops up in a heartbeat!

* That likely means an application being automatically started by a normally booted Windows is interfering with your DXLab applications. A misconfigured or incompetent antimalware application is usually the culprit. See

<>

73,

Dave, AA6YQ

On Fri, Mar 6, 2020 at 5:11 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Asking for guidance before I totally screw something up....

Turned on the shack computer this morning, started Launcher as usual. DXK is the first to start...window pops up: DXKeeper did not open in 180 seconds (or something like that). Launcher goes on to open DXV and SC. Button under DXK is still red, so I click again. "DXKeeper is already running on this computer." ??? After about 30 seconds, up pops DXK! So, I figure a minor glitch and move on.

Later this afternoon, started the shack machine again. This time a similar sequence, but DXK never came up. Tried to terminate it via Launcher - even with CTRL-click, and got the message "wait for DXKeeper to start" (or something like that). Rebooted, all that sort of thing (multiple times). Turned on error logging in Launcher, started again...same thing. Only this time after about 5 minutes, UP pops DXK! I've saved my log (again), but not tried a restore of WS on the fear I'll screw up the last good save.

Ideas? Anything obvious (that clearly isn't obvious to me)?

+ This is a diagnostic procedure:

1. reboot Windows into "Safe mode with networking"

2. start the Launcher

3. direct the Launcher to start DXKeeper (or allow it to start DXKeeper, if that's how you have the Launcher configured)

4. does DXKeeper start?

73,

Dave, AA6YQ


Re: Now what?

 

Yep!? Pops up in a heartbeat!


On Fri, Mar 6, 2020 at 5:11 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Asking for guidance before I totally screw something up....

Turned on the shack computer this morning, started Launcher as usual.? DXK is the first to start...window pops up:? DXKeeper did not open in 180 seconds (or something like that).? Launcher goes on to open DXV and SC.? Button under DXK is still red, so I click again.? "DXKeeper is already running on this computer."? ???? After about 30 seconds, up pops DXK!? So, I figure a minor glitch and move on.

Later this afternoon, started the shack machine again.? This time a similar sequence, but DXK never came up.? Tried to terminate it via Launcher - even with CTRL-click, and got the message "wait for DXKeeper to start" (or something like that).? Rebooted, all that sort of thing (multiple times).? Turned on error logging in Launcher, started again...same thing.? Only this time after about 5 minutes, UP pops DXK!? I've saved my log (again), but not tried a restore of WS on the fear I'll screw up the last good save.

Ideas?? Anything obvious (that clearly isn't obvious to me)??

+ This is a diagnostic procedure:

1. reboot Windows into "Safe mode with networking"

2. start the Launcher

3. direct the Launcher to start DXKeeper (or allow it to start DXKeeper, if that's how you have the Launcher configured)

4. does DXKeeper start?

? ? ?73,

? ? ? ? ? ? Dave, AA6YQ





Re: Now what?

 

+ AA6YQ comments below

Asking for guidance before I totally screw something up....

Turned on the shack computer this morning, started Launcher as usual. DXK is the first to start...window pops up: DXKeeper did not open in 180 seconds (or something like that). Launcher goes on to open DXV and SC. Button under DXK is still red, so I click again. "DXKeeper is already running on this computer." ??? After about 30 seconds, up pops DXK! So, I figure a minor glitch and move on.

Later this afternoon, started the shack machine again. This time a similar sequence, but DXK never came up. Tried to terminate it via Launcher - even with CTRL-click, and got the message "wait for DXKeeper to start" (or something like that). Rebooted, all that sort of thing (multiple times). Turned on error logging in Launcher, started again...same thing. Only this time after about 5 minutes, UP pops DXK! I've saved my log (again), but not tried a restore of WS on the fear I'll screw up the last good save.

Ideas? Anything obvious (that clearly isn't obvious to me)?

+ This is a diagnostic procedure:

1. reboot Windows into "Safe mode with networking"

2. start the Launcher

3. direct the Launcher to start DXKeeper (or allow it to start DXKeeper, if that's how you have the Launcher configured)

4. does DXKeeper start?

73,

Dave, AA6YQ


Now what?

 

Asking for guidance before I totally screw something up....

Turned on the shack computer this morning, started Launcher as usual.? DXK is the first to start...window pops up:? DXKeeper did not open in 180 seconds (or something like that).? Launcher goes on to open DXV and SC.? Button under DXK is still red, so I click again.? "DXKeeper is already running on this computer."? ???? After about 30 seconds, up pops DXK!? So, I figure a minor glitch and move on.

Later this afternoon, started the shack machine again.? This time a similar sequence, but DXK never came up.? Tried to terminate it via Launcher - even with CTRL-click, and got the message "wait for DXKeeper to start" (or something like that).? Rebooted, all that sort of thing (multiple times).? Turned on error logging in Launcher, started again...same thing.? Only this time after about 5 minutes, UP pops DXK!? I've saved my log (again), but not tried a restore of WS on the fear I'll screw up the last good save.

Ideas?? Anything obvious (that clearly isn't obvious to me)???

Thanks
Steve, N3SL


Re: PSK

 

+ AA6YQ comments below

Is there a way to get Commander & DXKeeper to recognize when an IC-7851 radio is directly switched to PSK31 or PSK63 mode to use the radio's internal modem (instead of using WinWarbler), so as to automatically set these as the modes for log entries?

+ There's not. My advice is to use WinWarbler for PSK operations.

73,

Dave, AA6YQ


PSK

 

Is there a way to get Commander & DXKeeper to recognize when an IC-7851 radio is directly switched to PSK31 or PSK63 mode to use the radio's internal modem (instead of using WinWarbler), so as to automatically set these as the modes for log entries?

Thanks for any help.

Mike
KC8JT


Minor CAPTURE editing tweak request for DXKeeper

 

Hello Dave:
? My belated congratulations to you for your ARRL President's Award.? Outstanding!?
? A minor tweak to DXKeeper would be appreciated.
? - When pasting a Callsign into the DXKeeper Capture CALL field, the LOOKUP is successful.? However, when LOG is pressed, the error "Callsign is invalid" occurs.? Recreation of the situation is by pasting (not typing) a Callsign that has a trailing space.
? The pasting scenario occurs on my local PC instance of DXKeeper as a result of using TeamViewer to a remote instance of WSJT-X.? It is possible that other hidden characters may appear in the pasting string.
Many thanks and 73,
Neil W3ZQI


Re: RAT for DXCC and TOP progress

 

Scott, my explanation below is incorrect: DXKeeper does compute and display DXCC award credits granted to QSOs in the ¡°user-specified digital mode family¡±.

The discrepancy between "Verified Including deleted" and "Verified Excluding deleted" is the result of a defect in DXKeeper -- an oversight when I added support for the ¡°user-specified digital mode family¡±; thanks for reporting it! I have corrected this defect in the next version of DXKeeper, and sent this version your way.

73,

Dave, AA6YQ


I understand. I also understand the display of specific digital mode families is merely to "to support the user's personal objectives". I was more questioning the discrepancy between Verified Including deleted and Verified Excluding deleted.

But as you said, it does not matter for Awards.

73,
--scott
------
Scott Stembaugh - N9LJX
radio.n9ljx@...

On Thu, Mar 5, 2020 at 8:58 AM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

When I do a summary from the Realtime Award Display on the DXCC Progress it correctly shows number of Verified for FT8 Including deleted but it shows 0 Verified for Excluding deleted. Is this by design? I have FT8 selected as User-specified digital mode family. Checking and unchecking the FT8 box produces the same results.

See for an example.

+ The DXCC award program does not include an FT8-specific award, so no FT8-specific DXCC credits are granted by the ARRL. Unless that changes, the Verified column for FT8 will be 0.

73,

Dave, AA6YQ


Re: Tracking SatPC32 frequencies and sending to SDR Console

Joe W4WT
 

Great!? Thanks,

Joe W4WT


Re: Tracking SatPC32 frequencies and sending to SDR Console

 

+ AA6YQ comments below

Thanks for the response Dave. Any chance this could be considered in a future release of Commander?

The reason I want to do this is to use SDR Console (could be any SDR app) along with my Icom 9700 primarily to follow the Rx frequency. It would be tied into the Rx antenna in order to get a decent panadapter/waterfall display. The 9700 is pretty poor in that area and the "scope" function of SatPC32 isn't much better due to the "audio" nature of the input rather than an IF input that would provide much more detail.

+ I am travelling without access to a radio; otherwise, I'd have extended Commander last night.

73,

Dave, AA6YQ


Re: Tracking SatPC32 frequencies and sending to SDR Console

Joe W4WT
 

Thanks for the response Dave.? Any chance this could be considered in a future release of Commander??

The reason I want to do this is to use SDR Console (could be any SDR app) along with my Icom 9700 primarily to follow the Rx frequency.? It would be tied into the Rx antenna in order to get a decent panadapter/waterfall display.? The 9700 is pretty poor in that area and the "scope" function of SatPC32 isn't much better due to the "audio" nature of the input rather than an IF input that would provide much more detail.

Thanks,

Joe W4WT