Date   

Re: Two Monitor Solution

Bill <ko4nrbs@...>
 

I have two monitors set up now with all the software appearing identically on both of them (Duplicate).  Maybe use Extend or ?? and then drag everything but HDSDR over to the 2nd monitor?

Will DXCommander/Keeper and HDSDR need to have separate com ports?

Wondering about com port conflicts.

Thanks Dave!!

73,

Bill KO4NR

On Saturday, March 14, 2020, 08:41:11 AM CDT, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below

Is it possible, using the same computer, to run WSJT-X, DXCommander/Keeper and JTALERT on one monitor and HDSDR on a second monitor?

+ Every DXLab application provides a "Use multiple monitors" option on its Configuration window's General tab. Enable this option, and DXLab application windows dragged to a secondary monitor and terminated will re-appear on that secondary monitor when they are next started.


      73,


              Dave, AA6YQ





Re: SpotCollector : <need> filter

Dave AA6YQ
 

+ AA6YQ comments below

Gotcha !
Thank you so much Dave.

I'm going back to learn the suite

+ Take your time! The steepness of the learning curve is driven by the velocity with which you attack it. I recommend the approach described here:

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

73,

Dave, AA6YQ


Re: Two Monitor Solution

Dave AA6YQ
 

+ AA6YQ comments below

Is it possible, using the same computer, to run WSJT-X, DXCommander/Keeper and JTALERT on one monitor and HDSDR on a second monitor?

+ Every DXLab application provides a "Use multiple monitors" option on its Configuration window's General tab. Enable this option, and DXLab application windows dragged to a secondary monitor and terminated will re-appear on that secondary monitor when they are next started.

73,

Dave, AA6YQ


Re: SpotCollector : <need> filter

Rick I2BRT
 

Gotcha !
Thank you so much Dave.

I'm going back to learn the suite now  (hoping to catch P5DX hi).
Best 73 de Rick I2BRT 


Two Monitor Solution

Bill <ko4nrbs@...>
 

Is it possible, using the same computer, to run WSJT-X, DXCommander/Keeper and JTALERT on one monitor and HDSDR on a second monitor?

Please excuse my ignorance!!

73,
Bill KO4NR


Re: SpotCollector : <need> filter

Dave AA6YQ
 

+ AA6YQ comments below

Here is a dummy user (starting to learn DXLabs modules).
Great applications but sometime the Learning curve seems to be steep.

+ With great power comes a steep learning curve.

So here is my first stupid question.

Configured almost anything in SpotCollector and imported in DXKeeper my existing logs.
Configured 4 telnet spot sources and IIRC in SC.
Set up Band, Mode, Cont and Origin filters to my preferred choice.
Band : 80,40,30,20,17,15,12,10,6
Mode : SSB,CW,RTTY,FT8
Cont : all
Orig : EU
So far so good.
I see sposts "Filter : Band and Mode and Origin" (matching my setup, bands mode and dx spotter origin)
"Source" column shows callsign of European spotters.

Now, I click "Need"
SC display "Filter : Band and Mode and Origin and Unconfirmed DXCC".

Here is my problem.
I have spots also form other countries, non only form EU spotters.
"Source" column now shows me callsign of USA spotters (K1ETA, W3ON, etc) but also ZL (ZL3AB) etc.
Is it by design ?

+ Yes.

Am I missing something ?
My goal would be to see needed spost ONLY from the Origin I selected befeore using "Origin" button.

+ The entries displayed on SpotCollector's Main window do not represent individual spots. Each entry represents an active DX station operating in a particular mode near a particular frequency. The information in each entry is collected from multiple spots. See

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

+ When you set SpotCollector's Origin filter to EU, you are configuring SpotCollector to hide the entries for active stations that have not been spotted from EU. An entry whose callsign has been spotted from both EU and OC will still be shown.

+ Why? Suppose your next door neighbor spots P5DX on 14020. A few minutes later, a station in Australia spots P5DX. Do you want the entry for P5DX hidden because of the Australian spot?

73,

Dave, AA6YQ


SpotCollector : <need> filter

Rick I2BRT
 

HI !
Here is a dummy user (starting to learn DXLabs modules).
Great applications but sometime the Learning curve seems to be steep.
So here is my first stupid question.

Configured almost anything in SpotCollector and imported in DXKeeper my existing logs.
Configured 4 telnet spot sources and IIRC in SC.
Set up Band, Mode, Cont and Origin filters to my preferred choice.
Band : 80,40,30,20,17,15,12,10,6
Mode : SSB,CW,RTTY,FT8
Cont : all
Orig : EU
So far so good.
I see sposts "Filter : Band and Mode and Origin" (matching my setup, bands mode and dx spotter origin)
"Source" column shows callsign of European spotters.

Now, I click "Need"
SC display "Filter : Band and Mode and Origin and Unconfirmed DXCC".

Here is my problem.
I have spots also form other countries, non only form EU spotters.
"Source" column now shows me callsign of USA spotters (K1ETA, W3ON, etc) but also ZL (ZL3AB) etc.
Is it by design ? Am I missing something ?
My goal would be to see needed spost ONLY from the Origin I selected befeore using "Origin" button.

Many thanks indeed for any possible comment.
Kind regards,
Rick I2BRT.





Re: DXKeeper Capture Window Fails to Clear on Lookup

Fred Coelho
 

Thanks Dave, I thought I missed a setting somewhere but hitting shift should be easy enough to do too.

73, Fred WX1S


Re: eQSL upload errors

Dave AA6YQ
 

+ AA6YQ comments below

Follow up question, why is DXKeeper logging all new QSO's with a mode of "F2". I see this now in the prop section, never saw it before. Thanks.

+ On the Configuration window's Defaults tab, to what is the "Propagation mode" selector set?

73,

Dave, AA6YQ


Re: eQSL upload errors

Paul W1IP
 

Follow up question, why is DXKeeper logging all new QSO's with a mode of "F2". I see this now in the prop section, never saw it before. Thanks.
--
Paul W1ip


Re: DXKeeper Capture Window Fails to Clear on Lookup

Dave AA6YQ
 

+ AA6YQ comments below

Is there a way to set DXKeepers Capture window to clear (Name and QTH) when you overwrite an existing call sign. If I enter a new call sign and hit lookup all fields populate fine. If I subsequently overwrite the call with a new one and hit lookup, stuff like Name and QTH do not get updated. If I clear the window first hit enter or lookup the fields update as expected. I'm just wondering if there's a way to do this automatically?

+ See the first two bullets in

<https://www.dxlabsuite.com/dxkeeper/Help/LogNewCapture.htm>

73,

Dave, AA6YQ


DXKeeper Capture Window Fails to Clear on Lookup

Fred Coelho
 

Is there a way to set DXKeepers Capture window to clear (Name and QTH) when you overwrite an existing call sign. If I enter a new call sign and hit lookup all fields populate fine. If I subsequently overwrite the call with a new one and hit lookup, stuff like Name and QTH do not get updated. If I clear the window first hit enter or lookup the fields update as expected. I'm just wondering if there's a way to do this automatically?

I am using QRZ XML data for lookups. This isn't a huge deal because I can clear the window prior to logging a QSO. However sometimes I forget and a wrong QTH/Name gets logged. Double clicking an item in SpotCollector clears and updates the capture window as I would expect.

Thanks,
fred WX1S


Re: Trouble with 2 Radio Control in Commander

Dave AA6YQ
 

+ AA6YQ comments below

On Thu, Mar 12, 2020 at 03:24 PM, Steve / W1SMC wrote:

Thanks for the help Dave........ Things are working great now.

Previous Kenwood transceivers have required the com port RTS modem control signal to be set to ‘Y’, whether transceiver control employed a physical com port or a virtual com port created by a USB connection. But when your computer is connected to a TS-890 via USB, however, RTS can implement flow control, CW keying, RTTY keying, or RX-TX switching as a function of Advanced Menu item 17. Steve's TS-890 had RTS configured to control RX-TX switching, which is why his TS-890 switched from RX to TX whenever it was selected in Commander as the primary transceiver.

 

Setting Commander’s RTS selector to ‘N’ eliminating the undesired behavior. I have updated step 4.c in


Getting Started with Kenwood Transceiver Control

 

to reflect this.

     
      73,

            Dave, AA6YQ


Re: DXLab Commander quarantined with Trojan

Dave AA6YQ
 

+ AA6YQ comments below

Haven't used commander in a few days, due to another problem, but, what steps did you take (how) to clear that up?

+ There is nothing to "clear up"; Commander does not contain malware.

73,

Dave, AA6Yq

@danny_douglas
Ex WN5QMX,WA5UKR,ET2US,ET3USA,SV0WPP,VS6DD,N7DC/YV5/G5CTB
QSL Bureau, DIRECT, LOTW Preferred, eQSL used but upload at a courtesy only, as do not use the system for awards.

On March 11, 2020 at 10:57 PM Phil NA4M <na4m4dx@...> wrote:

Other than an occasional scan by Malwarebytes Free I also only use W10 Security/Defender and have since system was new.

Have run DXLab suite also since system was purchased. Never have gotten any "hits" from Defender until after today's update.

W10 Security/Defender did spit out a message that it quarantined Commander. I had to "Allow" it before I could get Commander to run,

Here's Defender message:
Severe
Threat blocked 03/11/2020 22:16
Status: Quarantined Quarantined files are in a restricted area where they can't harm your device. They will be removed automatically.
Threat detected: Trojan:Win32/Azden.B!c! Alert level: Severe Date: 03/11/2020 22:16 Category: Trojan Details: This program is dangerous and executes commands from an attacker.
Learn more
Affected items:
file: C:\DXLab Commander C-V Commander1440.exe

Phil NA4M


Re: DXLab Commander quarantined with Trojan

Danny Douglas <n7dc@...>
 

Havent used commander in a few days, due to another problemj, but, what steps did you take (how) to clear that up?

N7DC@...
Ex WN5QMX,WA5UKR,ET2US,ET3USA,SV0WPP,VS6DD,N7DC/YV5/G5CTB
QSL Bureau, DIRECT, LOTW Preferred, eQSL used but upload at a courtesy only, as do not use the system for awards.

On March 11, 2020 at 10:57 PM Phil NA4M <na4m4dx@...> wrote:

Other than an occasional scan by Malwarebytes Free I also only use W10 Security/Defender and have since system was new. 

Have run DXLab suite also since system was purchased. Never have gotten any "hits" from Defender until after today's update.  

W10 Security/Defender did spit out a message that it quarantined Commander.  I had to "Allow" it before I could get Commander to run,

Here's Defender message:

Severe

Threat blocked 03/11/2020 22:16

Status: Quarantined Quarantined files are in a restricted area where they can't harm your device. They will be removed automatically.

Threat detected: Trojan:Win32/Azden.B!c! Alert level: Severe Date: 03/11/2020 22:16 Category: Trojan Details: This program is dangerous and executes commands from an attacker.

Learn more

Affected items:

file: C:\DXLab Commander C-V Commander1440.exe


Phil NA4M


 


Re: Trouble with 2 Radio Control in Commander

Steve / W1SMC
 

On Thu, Mar 12, 2020 at 10:25 AM, Dave AA6YQ wrote:
Dave, AA6YQ
Thanks for the help Dave........ Things are working great now.


Re: Something going on at LotW ...

Joe Subich, W4TV
 

QRZ.COM log sync reports: "LOTW Uploads and Downloads are not
currently available, We are actively working to restore LOTW
integration"
As ususal QRZ.com has been bitten by their lazy programming.

Many years ago ARRL changed the URL for LotW from p1k.arrl.org
to lotw.arrl.org and left a redirect in place. With the recent
change in internet provider for ARRL, that redirect no longer
works. If QRZ.com had changed the URL they use for LotW integration
*as all logging software developers and others who interoperate with*
*LotW were told to do* they would not have the problem.

Note: at least two logging programs have announced updates to resolve
this issue for their users in the last two days. DXKeeper does not
have the problem as it uses the correct URL for Sync LotW QSOs/QSLs.

73,

... Joe, W4TV


On 2020-03-12 2:40 PM, Mike Flowers wrote:
Trying to Sync LotW QSOs yielded "Unable to download from LotW: invalid
request:
QRZ.COM log sync reports: "LOTW Uploads and Downloads are not currently
available, We are actively working to restore LOTW integration"
Club Log just worked fine doing a LotW Sync ..
Just a FYI .
- 73 and good DX de Mike, <http://www.qrz.com/db/k6mkf/> K6MKF, NCDXC
<https://www.ncdxc.org/> Secretary


Re: Commander Issues

Dave AA6YQ
 

* more AA6YQ comments below

Dave --no joy did that already and that's when I get the error.

* OK.

C:/DxLab/ci-v commander.exe

* Is not where Commander would be installed by default. On the Launcher's Configuration window, please make a screen shot showing the "DXLab Apps" tab, attach this screenshot to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


Re: Commander Issues

Samuel Bacon
 

Dave 

So maybe I should add how I got the program to work when it could not find Commander. Maybe that will help.

Launcher
Config
Double clicked on Program Path

Maybe that is the issue??


On Thursday, March 12, 2020, 03:11:46 PM EDT, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below

After a Windows 10 upgrade last night I have the following issue. I finally got Commander to open after the program said it couldn't find it.
Now the issue is when I try to upgrade from 14.3.1 to 14.4.0 I get the following message

"Can't replace C:/DxLab/cl-vcommander.exe because it's either in use or write protected; commander has not been upgraded."

Any ideas??

+ As a first step, reboot Windows, start the Launcher, and then direct the Launcher to upgrade Commander. Any joy?


        73,


              Dave, AA6YQ




Re: Commander Issues

Samuel Bacon
 

Dave --no joy did that already and that's when I get the error.

On Thursday, March 12, 2020, 03:11:46 PM EDT, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below

After a Windows 10 upgrade last night I have the following issue. I finally got Commander to open after the program said it couldn't find it.
Now the issue is when I try to upgrade from 14.3.1 to 14.4.0 I get the following message

"Can't replace C:/DxLab/cl-vcommander.exe because it's either in use or write protected; commander has not been upgraded."

Any ideas??

+ As a first step, reboot Windows, start the Launcher, and then direct the Launcher to upgrade Commander. Any joy?


        73,


              Dave, AA6YQ