Date   

Re: LOTW upload issues?

Dave AA6YQ
 

+ AA6YQ comments below

I can login to LOTW using TQSL and upload QSO's. The certificate dates are BEGIN 2-27-2020 and END 2-26-2023.

When I try to upload to LOTW using DXKeeper I get a window that says "Waiting for TQSL to complete processing". I have waited for an hour at times without any progress occuring.

I can sync LOTW and download confirmations to my log using the "Sync LOTW QSL's" button on the QSL screen. I have received three credits today from past QSO's without any problem.

Would you suggest that I upload the 5 pending QSO's using TQSL and marking them as sent manually?

+ No. I suggest that you do the following:

1. reboot Windows into "Safe mode with networking"

2. start the Launcher

3. direct the Launcher to start DXKeeper

4. direct DXKeeper to upload your QSOs to LoTW; does it succeed?

73,

Dave, AA6YQ


Re: LOTW upload issues?

n4qwf .
 

I can login to LOTW using TQSL and upload QSO's. The certificate dates are BEGIN 2-27-2020 and END 2-26-2023. 

When I try to upload to LOTW using DXKeeper I get a window that says "Waiting for TQSL to complete processing". I have waited for an hour at times without any progress occuring. 

I can sync LOTW and download confirmations to my log using the "Sync LOTW QSL's" button on the QSL screen. I have received three credits today from past QSO's without any problem. 

Would you suggest that I upload the 5 pending QSO's using TQSL and marking them as sent manually?

73<<John


Re: Setting up for BARTG-RTTY ...

Dave AA6YQ
 

+ 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


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

Carl - WC4H
 

Thanks Dave.  

For me, I just want it to clear.  I don't need an option.

73.
Carl - WC4H


Re: Something going on at LotW ...

Peter Laws / N5UWY
 

On Sat, Mar 21, 2020 at 3:25 PM Curt Bowles <curt.bowles@...> wrote:

Dave AA6YQ....

Thanks for the Date/Time info below the "Sync LotW QSLs" button...as well as the recent day's acceptances or confirmations info... I did not know that ...! Constantly learn new things about the suite everyday : - )

Worry not. I started using the Suite c.2006 and I learn stuff about
it all the time. And not all of that is because I knew it and then
forgot it. :-)


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


Re: LOTW upload issues?

Mike Kasrich
 

That did it. Thanks.

On 3/21/2020 4:14 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

Still not working exactly correct. I have 3 qsos that attempted to upload when disaster hit LoTW yesterday. Today the qsos don't show up on LoTW and I get an error that they are duplicates. Not sure if it is still a LoTW glitch or if I have something incorrect in DXLab.

+ That error message comes from TQSL: it's refusing to submit your QSOs because one or more of them have already been submitted to LoTW. To get around this, check the "Permit uploading of QSOs already uploaded to LoTW" box on the "QSL Configuration" window's LoTW tab. Then try submitting your QSOs to LoTW again.

73,

Dave, AA6YQ



Re: Something going on at LotW ...

Curt Bowles
 

Dave AA6YQ....

Thanks for the Date/Time info below the "Sync LotW QSLs" button...as well  as the recent day's acceptances or confirmations info... I did not know that ...! Constantly learn new things about the suite everyday : - )
--
Curt Bowles
VE3ZN


Re: LOTW upload issues?

Dave AA6YQ
 

+ AA6YQ comments below

Still not working exactly correct. I have 3 qsos that attempted to upload when disaster hit LoTW yesterday. Today the qsos don't show up on LoTW and I get an error that they are duplicates. Not sure if it is still a LoTW glitch or if I have something incorrect in DXLab.

+ That error message comes from TQSL: it's refusing to submit your QSOs because one or more of them have already been submitted to LoTW. To get around this, check the "Permit uploading of QSOs already uploaded to LoTW" box on the "QSL Configuration" window's LoTW tab. Then try submitting your QSOs to LoTW again.

73,

Dave, AA6YQ


Re: LOTW upload issues?

Mike Kasrich
 

Still not working exactly correct. I have 3 qsos that attempted to upload when disaster hit LoTW yesterday. Today the qsos don't show up on LoTW and I get an error that they are duplicates. Not sure if it is still a LoTW glitch or if I have something incorrect in DXLab.


Re: LOTW upload issues?

Dave AA6YQ
 

+ AA6YQ comments below

There is something weird going on with LOTW. I have not been able to upload QSO's using DXLab since 3/20/2020 @19:57z.

+ What happens when you try to submit QSOs to LoTW?

+ When you check your Callsign Certificate's properties in TQSL, what is shown as the expiration date?

73,

Dave, AA6YQ


LOTW upload issues?

n4qwf .
 

There is something weird going on with LOTW. I have not been able to upload QSO's using DXLab since 3/20/2020 @19:57z. I can sync QSO's without issue. I have also lost one credit from my WAS account. I have 8 bands with 50 states credited but my WAS mixed has been reduced to 49. My WAS digital is also 49 now and I have WAS digital credited using 4 different digital modes. A week or so back I had a bunch of credits removed from my DXCC account and I had to call them to get them reinstated. 

Something ain't right in Newington!


Re: TQSL problem in QSL Config

Dave AA6YQ
 

# more AA6YQ comments below

+ Were you not able to recover your DXLab application settings from the Workspace you created and backed up?
** Where is that? in %APPDATA% DXLabs I don't have anything.

# If you accepted the default location when you directed the Launcher to create the Workspace, it's in the Launcher's Workspaces folder:

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

# This is step 2 of

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



In DXKeeper, When configuring the LOTW and TQSL settings, I get an errot saying"

"'QSL Via' is set to LOTW, but no Station Callsign has been specified on the TQSL panel........"

When I go there to configure that, it won't allow me to add anything there. Nothing happens when I click "Update"

+ Click the "Update" button in that panel will populate the "station location" selector with your Station Locations, if TQSL has been installed and populated with one or more Station Locations. Evidently, that's not the case.

+ What is specified in the TQSL panel's "station callsign" box?
*** There is no callsign there. I get an error when I try an enter one.

"The selected Callsign Certificate specifies Station Callsign; you cannot specify a different Station Callsign."

# What is specified in the TQSL panel's "station location" selector?

# When you click the down-facing black triangle at the right side of the selector, what choices appear in the dropdown?

73,

Dave, AA6YQ


Re: TQSL problem in QSL Config

Kurt Cathcart
 

Never mind.  You gave me enough clues to figure it out myself.  I had to finish rebuilding the TQSL app first.  Thank you for your prompt attention.


-Kurt, KR2C

On 3/21/2020 3:36 PM, Kurt Cathcart, KR2C wrote:

On 3/21/2020 2:59 PM, Dave AA6YQ wrote:
+ AA6YQ comment below

I had the need to rebuild my Windows 10 computer.

Fortunately, I recovered the log file.  However I needed to do some reconfiguration of various DXLab apps.

+ Were you not able to recover your DXLab application settings from the Workspace you created and backed up?
** Where is that?  in %APPDATA% DXLabs I don't have anything.


In DXKeeper, When configuring the LOTW and TQSL settings, I get an errot saying"

"'QSL Via' is set to LOTW, but no Station Callsign has been specified on the TQSL panel........"

When I go there to configure that, it won't allow me to add anything there.  Nothing happens when I click "Update"

+ Click the "Update" button in that panel will populate the "station location" selector with your Station Locations, if TQSL has been installed and populated with one or more Station Locations. Evidently, that's not the case.

+ What is specified in the TQSL panel's "station callsign" box?
*** There is no callsign there.  I get an error when I try an enter one.

"The selected Callsign Certificate specifies Station Callsign; you cannot specify a different Station Callsign."


        73,

                Dave, AA6YQ



Re: TQSL problem in QSL Config

Kurt Cathcart
 

On 3/21/2020 2:59 PM, Dave AA6YQ wrote:
+ AA6YQ comment below

I had the need to rebuild my Windows 10 computer.

Fortunately, I recovered the log file. However I needed to do some reconfiguration of various DXLab apps.

+ Were you not able to recover your DXLab application settings from the Workspace you created and backed up?
** Where is that?  in %APPDATA% DXLabs I don't have anything.


In DXKeeper, When configuring the LOTW and TQSL settings, I get an errot saying"

"'QSL Via' is set to LOTW, but no Station Callsign has been specified on the TQSL panel........"

When I go there to configure that, it won't allow me to add anything there. Nothing happens when I click "Update"

+ Click the "Update" button in that panel will populate the "station location" selector with your Station Locations, if TQSL has been installed and populated with one or more Station Locations. Evidently, that's not the case.

+ What is specified in the TQSL panel's "station callsign" box?
*** There is no callsign there.  I get an error when I try an enter one.

"The selected Callsign Certificate specifies Station Callsign; you cannot specify a different Station Callsign."


73,

Dave, AA6YQ



Re: DXLab Commander quarantined with Trojan

Dave AA6YQ
 

+ AA6YQ comments below

I have had problems twice now with CI-V Commander. The first time I told Windows Security to allow and to remove from quarantine. And it worked for several days. Yesterday, Windows Security removed Commander again. Sigh. Yes, I have told Windows Security again to allow and to remove from quarantine. Not happy about the false positive problem coming back. Also having same issue with JT-Alert software - Windows Security has removed it multiple times, and each time I tell it to allow and remove from quarantine.

Anyone having good results with a different free Windows 10 anti-virus program? Lots of products listed in this VirusTotal scan of CI-V Commander <https://www.virustotal.com/gui/file/8d49ad367c40988b1020fd2950f517fc49a48994e2e6d032e1dfbb594d484b86/detection>

+ I have been using the free version of AVG for many years, but I cannot make any guarantees.

73,

Dave, AA6YQ


Re: TS-890S/Commander issue

Dave AA6YQ
 

+ AA6YQ comments below

When I boot up Commander it puts my TS-890S into BUSY/TX mode. I have to turn the 890S off and then back on to clear it.

+ See step 4.c in

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

+ If that doesn't get you going, please let me know.

73,

Dave, AA6YQ


Re: DXLAB Hijacks Cursor

Dave AA6YQ
 

+ AA6YQ comments below

The problem has existed for at least several weeks but I don't recall when I first noticed it because I didn't attribute the problem to running DXLab for a while. The friend I referred to says he doesn't know when it started with him and he thinks it happens with him less than with me.
I am using the latest DXLab releases, Windows10 current, and have a pretty big computer usually running several programs at the same time.

+ Please specify the most recent date on which you are *certain* that no cursor theft was occurring.

73,

Dave, AA6YQ


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

Dave AA6YQ
 

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

73,

Dave, AA6YQ


Re: TQSL problem in QSL Config

Dave AA6YQ
 

+ AA6YQ comment below

I had the need to rebuild my Windows 10 computer.

Fortunately, I recovered the log file. However I needed to do some reconfiguration of various DXLab apps.

+ Were you not able to recover your DXLab application settings from the Workspace you created and backed up?


In DXKeeper, When configuring the LOTW and TQSL settings, I get an errot saying"

"'QSL Via' is set to LOTW, but no Station Callsign has been specified on the TQSL panel........"

When I go there to configure that, it won't allow me to add anything there. Nothing happens when I click "Update"

+ Click the "Update" button in that panel will populate the "station location" selector with your Station Locations, if TQSL has been installed and populated with one or more Station Locations. Evidently, that's not the case.

+ What is specified in the TQSL panel's "station callsign" box?

73,

Dave, AA6YQ


Re: Something going on at LotW ...

Dave AA6YQ
 

+ AA6YQ comments below

I just did a "Sync LotQ QSOs" this morning in DXKeeper and it worked fine downloaded 30...however I did notice the date/time stamp underneath the sync button was incorrect it is showing yesterday's date/time (20-Mar-20 22:17:40 UTC) when I tried to sync and it failed. So I tried to sync again (21-Mar-20 11:58 UTC) and received 4 more download confirmations but know change in Date/time. So I tried a third time and received the same 4 confirmations and the date/time DID NOT CHANGE.

+ The date and time shown beneath a Sync button is not the date and time that you last clicked the Sync button - it's the date and time of the last reported acceptance or confirmation (depending upon which Sync button you're clicking). I just invoked "Sync LoTW QSOs", for example, and the date shown beneath the "Sync LoTW QSOs" button is

2020-03-19 22:28:54

+ That's the date of the last QSO I submitted to LoTW, not today's date.

+ LoTW responds to your clicking the Sync buttons by reporting all acceptances or confirmations that have arrived after 0Z on the date shown beneath the Sync button you clicked. That means repeatedly clicking the same Sync button will repeatedly report the most recent day's acceptances or confirmations.

+ Executive summary: LoTW is now working correctly.

73,

Dave, AA6YQ