Date   

LoTW Upload popup

Gene
 

I just imported my QSO I made in Russian DX, and started upload to LoTW. A pop-up stating:
----------------------------------------------------------------------------
2020-03-22 @ 23:31:02 : QSOs were uploaded to LotW
success: all qsos submitted were signed and uploaded
----------------------------------------------------------------------------
appeared right after I started the process.

Bit this pop-up has an "Abort" button, and DXKeeper is still doing something (utilizing 18 percent of CPU time -- looks like full capacity of one core).

So the question is -- if everything IS completed, what is happening, and what I would "Abort" if I press the button?

It is running now for at least 10 minutes... In the past, signing much larger files than this small log with under 1500 Qs took seconds.

Should I wait? For how long? What happens if I press "Abort" ?
Thanks,
Gene W3UA


Re: TS-890S/Commander issue

Dave AA6YQ
 

+ AA6YQ comments below

Problem solved. Changing windows to not power down the ports on my computer did not help. But what did do the trick was setting RTS to OFF and setting DTR to ON within Commander/Config/Ports/Primary CAT Serial Port.

+ Kenwood radios prior to the TS-890 required the serial port's RTS modem control signal to be asserted.

+ In the TS-890, there are menu settings that govern how RTS is interpreted; evidently, the default menu setting is "switch from RX to TX". So you should configure Commander to disable RTS. This is documented in step 4.c of

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

+ and in the description of "Advanced Menu 17" on page 3-8 of the TS-890 instruction manual.

+ "Advanced Menu 18" is decribed on the same page, and controls the interpretation of DTR. To which option is this menu set on your TS-890?

73,

Dave, AA6YQ


Re: Comander freezes up

Dave AA6YQ
 

+ AA6YQ comments below

So it's been four days since my commander has locked up. Not sure what happened but I'll take it. The only thing I did was to check the "Log debugging info" box in the confg. area and everything seems to be working fine. Thanks to everyone who helped out with this. I will let y'all know if it happens again but I'm optimistic that it's really fine.

+ Enabling "log debugging info" causes Commander to log diagnostic information to the file errorlog.txt in your Commander folder until the size of this file exceeds 100 megabytes, at which point no more diagnostic information is recorded. Given the amount of diagnostic information that Commander records, this size limit was likely reached within 24 hours.

+ Please do the following:

1. disable "log debugging info"

2. terminate Commander

3. if your radio is connected or your computer via a USB port, make sure that your USB ports are configured to not power down:

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

4. start Commander

Let me know if you encounter another lockup

73,

Dave, AA6YQ


Re: WinWarbler Macro Banks ...

Dave AA6YQ
 

+ AA6YQ comments below

That will work, certainly. Just wondered if a temporary stickiness would be possible.

+ Technically possible yes, but I'd prefer to keep macro bank selection for each mode "intentional".

73,

Dave, AA6YQ


Re: DXLab Commander quarantined with Trojan

Dave AA6YQ
 

+ AA6YQ comments below

Yes, Windows Security Center (Windows Defender) was working for several years on my shack computer. And then it started blocking JT-Alert. And I would remove JT-Alert from quarantine, and tell it to allow. And then several days later, it would block it again. Recently it started blocking Commander in the same way. Regardless, I am running the free version of AVG now instead of Windows Defender. So far, no issues with AVG blocking ham radio software. And no exceptions required for AVG to behave appropriately. It's good when things just work.

+ To augment my use of the free version of AVG, I have the free versions of "Spybot Search and Destroy" and MalwareBytes installed, but I do not have them continuously running. Every few weeks, I run each, and have it scan my computer. None has ever found anything other than tracking cookies and low-risk "potentially unwanted programs".

+ Again, I can make no guarantees as to the effectiveness of this approach. I can only describe what has worked for me and my usage patterns.

73,

Dave, AA6YQ


Re: DXLAB Hijacks Cursor

Dave AA6YQ
 

+ AA6YQ comments below

I'm afraid I am not very certain. My guess is about 3 weeks ago but it may have been longer. FWIW, I upgrade DXLab programs as soon as they are announced and I see them, which is typically within days of release as I check the forum daily. I've done several complete computer shut-downs over the past few weeks.

+ I can't suggest a next diagnostic step without a date on which you are certain that cursor stealing was not occurring.

+ The plan is to have you run the version of Commander that was public on that date. If cursor stealing does not occur, then some subsequent change in Commander is a factor; if cursor stealing does occur, then something other than Commander is responsible.

73,

Dave, AA6YQ


Re: TS-890S/Commander issue

K4PX K4PX
 

Hi Dave,
Problem solved.  Changing windows to not power down the ports on my computer did not help.  But what did do the trick was setting RTS to OFF and setting DTR to ON within Commander/Config/Ports/Primary CAT Serial Port.
Thanks again!
73,
Joe
K4PX


Re: WinWarbler Macro Banks ...

Mike Flowers
 

That will work, certainly.  Just wondered if a temporary stickiness would be possible.

 

Easy enough for the duration of the contest!

 

Thanks, Dave.

 

- 73 and good DX de Mike, K6MKF, NCDXC Secretary

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Sunday, March 22, 2020 09:57
To: DXLab@groups.io
Subject: Re: [DXLab] WinWarbler Macro Banks ...

 

+ AA6YQ comments below

On Sun, Mar 22, 2020 at 08:23 AM, Mike Flowers wrote:

Now my question is:   Can mode macro assignments be made ‘sticky’?   So, if the user was to uncheck the RTTY Startup macro box and select a different set of RTTY macros, after changing mode and then returning to RTTY that the previously loaded macro set would be remembered and loaded.

+ You can configure the RTTY startup macro to load whichever RTTY macro set you wish.

       73,

             Dave, AA6YQ


Re: WinWarbler Macro Banks ...

Dave AA6YQ
 

+ AA6YQ comments below

On Sun, Mar 22, 2020 at 08:23 AM, Mike Flowers wrote:

Now my question is:   Can mode macro assignments be made ‘sticky’?   So, if the user was to uncheck the RTTY Startup macro box and select a different set of RTTY macros, after changing mode and then returning to RTTY that the previously loaded macro set would be remembered and loaded.

+ You can configure the RTTY startup macro to load whichever RTTY macro set you wish.

       73,

             Dave, AA6YQ


WinWarbler Macro Banks ...

Mike Flowers
 

Hi Folks,

 

I’m having fun in the BARTG-RTTY HF contest and learning a lot about WinWarbler RTTY with my K3.   I’d set up my RTTY macros for the BARTG-RTTY HF contest and saved them a BARTG-RTTY 2020.txt file.

 

After running some RTTY QSOs I noticed a CW spot for a DX station I wanted to work on the same band.   I changed mode to CW and tuned down to where the DX was spotted.   After finishing, I changed mode back to RTTY and discovered that now my RTTY macros had reverted to my original RTTY macros.  

 

Of course, I thought, it’s the Startup Macro settings.  I unchecked the RTTY Startup macro box, reloaded my BARTG-RTTY macros and tried changing modes to CW then back to RTTY.

 

The macros remained the CW macros from my test, which makes perfect sense.

 

Now my question is:   Can mode macro assignments be made ‘sticky’?   So, if the user was to uncheck the RTTY Startup macro box and select a different set of RTTY macros, after changing mode and then returning to RTTY that the previously loaded macro set would be remembered and loaded.

 

Perhaps I am missing something in the WW configuration.

 

Guidance gratefully accepted!!

 

Thanks!

 

- 73 and good DX de Mike, K6MKF, NCDXC Secretary

 


Re: DXLab Commander quarantined with Trojan

Jim AF5FH
 

Yes, Windows Security Center (Windows Defender) was working for several years on my shack computer. And then it started blocking JT-Alert. And I would remove JT-Alert from quarantine, and tell it to allow. And then several days later, it would block it again. Recently it started blocking Commander in the same way. Regardless, I am running the free version of AVG now instead of Windows Defender. So far, no issues with AVG blocking ham radio software. And no exceptions required for AVG to behave appropriately. It's good when things just work.

73,
Jim AF5FH 


Re: Comander freezes up

Steve
 

So it's been four days since my commander has locked up. Not sure what happened but I'll take it.  The only thing I did was to check the "Log debugging info" box in the confg. area and everything seems to be working fine. Thanks to everyone who helped out with this. I will let y'all know if it happens again but I'm optimistic that it's really fine.

Steve


On Tue, Mar 17, 2020 at 12:48 PM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

On Tue, Mar 17, 2020 at 05:17 AM, Steve wrote:

I’m not sure where to find “error log.text. I looked all over in my files, checked on the DX labs site and still not sure where to look. Give me a hint and I’ll go look again. By the way, it was over an hour before commander locked up this time. However, this time when it locked up it wouldn’t shut down, even when I tried to close it with task manager so I rebooted the computer. Scratching my head here because it started right up without any problems. 

+ See

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

      73,

             Dave, AA6YQ

 



--
Steve Meade  KC1AQQ
24 Boulevard
Middletown, RI  02842


Re: TS-890S/Commander issue

K4PX K4PX
 

I'll give it a try...thanks Dave!
Joe
K4PX


Re: DXLAB Hijacks Cursor

 

I'm afraid I am not very certain.  My guess is about 3 weeks ago but it may have been longer.   FWIW, I upgrade DXLab programs as soon as they are announced and I see them, which is typically within days of release as I check the forum daily.  I've done several complete computer shut-downs over the past few weeks.
--
Jim NO0B


Re: SpotCollector/DXKeeper: Clear Callsign Filter when press F4 in WSJT-X or when Logged

Dave AA6YQ
 

* more AA6YQ comments below

+ AA6YQ comments below

Feature Request when using Spotcollector with DXKeeper & WSJT-X:
After logging a QSO from WSJT-X or after press F4 (clearing the callsign) in WSJT-X, DXKeeper does not clear the callsign filter.

Can it be made to do that or is there a current setting to make that happen?

+ Given the impact that adding a new configuration option has on perceived complexity, adding an option to eliminate one mouse click after logging a QSO does not seem justified. Use the time to savor the new QSO!

+ I'll see if it's possible to clear the Log Page Display filter in response to clearing the callsign in WSJT-X.

* In the next version of SpotCollector, with the Lookup option enabled on the WSJT-X panel on the Configuration window's "Spot Sources" tab when the WSJT-X "DX Call" box transitions from containing more than one characters to containing no characters, DXKeeper is directed to remove any Log Page display filtering.

73,

Dave, AA6YQ


Re: LOTW upload issues?

Dave AA6YQ
 

+ AA6YQ comments below

On Sat, Mar 21, 2020 at 04:29 PM, n4qwf . wrote:

Thanks again Dave for the help. Rebooting in safe mode solved the upload problem. I uploaded one of the 6 q's while in safe mode and it worked. When I returned to normal mode it uploaded the other 5 without issue. I have entered a ticket with LOTW concerning the credits that are a problem on LOTW.

+ The fact that booting from "Safe Mode with Networking" worked means that an application automatically started when Windows is booted normally was responsible for preventing DXKeeper from interacting with TQSL. The culprit is almost always a misconfigured or incompetent anti-malware application.

+ Why you were still able to upload after booting Windows normally is a mystery.

         73,

                 Dave, AA6YQ

 


Re: LOTW upload issues?

n4qwf .
 

Thanks again Dave for the help. Rebooting in safe mode solved the upload problem. I uploaded one of the 6 q's while in safe mode and it worked. When I returned to normal mode it uploaded the other 5 without issue. I have entered a ticket with LOTW concerning the credits that are a problem on LOTW. 

73<<John


Re: DXLab Commander quarantined with Trojan

Gilbert Baron W0MN
 

It  is strange that you have the problem with Windows Defender. It may give a message but it will let you permit the module to continue and not stop it again.

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Jim Kajder AF5FH
Sent: Saturday, March 21, 2020 17:32
To: DXLab@groups.io
Subject: Re: [DXLab] DXLab Commander quarantined with Trojan

 

Thanks for the recommendation! I have installed AVG free version, and it is allowing me to operate with DXLab, JT-Alert, and WSJT-X without the false positives I was getting from Windows Security.

73,
Jim AF5FH


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


Re: DXLab Commander quarantined with Trojan

Jim AF5FH
 

Thanks for the recommendation! I have installed AVG free version, and it is allowing me to operate with DXLab, JT-Alert, and WSJT-X without the false positives I was getting from Windows Security.

73,
Jim AF5FH


Re: Setting up for BARTG-RTTY ...

Mike Flowers
 

Thanks, Dave!!

- 73 and good DX de Mike, K6MKF, NCDXC Secretary

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Saturday, March 21, 2020 14:05
To: DXLab@groups.io
Subject: Re: [DXLab] Setting up for BARTG-RTTY ...

+ AA6YQ comments below

Found it - the '~' button toggles between QSL Msg and Comment .

+ Correct!

+ Checking out the generated Cabrillo beforehand is the exact right step
to take.

+ If you haven't already, take a look at

<https://www.dxlabsuite.com/winwarbler/Help/ContestSettings.htm>

+ Good luck!

73,

Dave, AA6YQ