Topics

myQTH changed on most QSO's


Steve Wedge <Steve27302@...>
 

This may have to do with updates from LoTW.  I was told that I only really needed to update my latest call sign with LoTW unless I was entering more Q's from paper logs.  Yes, I may do that someday but I just want to make sure that I have everything I already have at 100%.

I don't know how it happened but just about all of my QSO's, going back to 1982, have myQTH changed to my current QTH.  For DXCC and WAZ purposes, it won't matter (I'm still in Zone 5) but I am (a) curious as to how this could have happened and (b) wondering if I could correct this data -- or would it mess up LoTW?

Thanks!

Steve, W1ES/4


Dave AA6YQ
 

+ AA6YQ comments below

This may have to do with updates from LoTW. I was told that I only really needed to update my latest call sign with LoTW unless I was entering more Q's from paper logs.

+ What do you mean by "update my latest callsign with LoTW"?

Yes, I may do that someday but I just want to make sure that I have everything I already have at 100%.

I don't know how it happened but just about all of my QSO's, going back to 1982, have myQTH changed to my current QTH. For DXCC and WAZ purposes, it won't matter (I'm still in Zone 5) but I am (a) curious as to how this could have happened

+ You evidently directed DXKeeper to make those changes; it cannot make such changes autonomously.

and (b) wondering if I could correct this data -- or would it mess up LoTW?

+ You should correct your logged QSOs to specify the correct "my QTH". Each "my QTH" should specify the associated "LoTW Station Location".

+ See

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

73,

Dave, AA6YQ


Steve Wedge <Steve27302@...>
 

The genesis of my problem was when my computer became useless last autumn.  Win10 ran a troubleshooter and advised me to do their wipe and reload.  That gets rid of all applications but leaves the data files.

The problem started when TQSL stopped working.  Apparently, TQSL won't reload certificates onto a "different" computer.  Since it has a new OS build, to TQSL, this is a "different" computer.  I got only the certificate for my latest call and QTH.  When I was trying to fix my requested QSO's in LoTW, when I updated and uploaded to LoTW, it caused everything to be overwritten as W1ES and QTH as Graham.

I have asked Bart at LoTW to send me new certificates.

When I get the new certificates, am I correct in thinking that I will have to make the mass change per the instructions, then upload to LoTW again?

Sorry this has been such a mess.  There are so many interactive pieces here.

73,

Steve, W1ES


Dave AA6YQ
 

+ AA6YQ comments below

The genesis of my problem was when my computer became useless last autumn. Win10 ran a troubleshooter and advised me to do their wipe and reload. That gets rid of all applications but leaves the data files.

The problem started when TQSL stopped working. Apparently, TQSL won't reload certificates onto a "different" computer.

+ You can't effectively move e a Callsign Certificate file (.tq6) from one computer to another unless you also move the Callsign Certificate's "private key". TQSL provides a easy means of moving all Callsign Certificates, Station Locations, and Settings in a single file from one computer to another; see

<https://lotw.arrl.org/lotw-help/backuprestore/>


Since it has a new OS build, to TQSL, this is a "different" computer.

+ No, it's computer whose private keys were deleted by the Windows "wipe and reload" process.


I got only the certificate for my latest call and QTH. When I was trying to fix my requested QSO's in LoTW, when I updated and uploaded to LoTW, it caused everything to be overwritten as W1ES and QTH as Graham.

I have asked Bart at LoTW to send me new certificates.

When I get the new certificates, am I correct in thinking that I will have to make the mass change per the instructions, then upload to LoTW again?

+ No. There is no "mass change" to make, and no need to re-submit anything to LoTW.

+ If you have more than one "My QTH" defined in DXKeeper, it would be a good idea to ensure that each logged QSO specifies the correct "My QTH". This can be accomplished by filtering the Log Page Display to contain QSOs within a date range, and en masse modifying the "My QTH ID" of all of those QSOs to the correct value. Be sure to backup your log before undertaking this process, and don't hesitate to ask for help if you need it.

73,

Dave, AA6YQ


Steve Wedge <Steve27302@...>
 

Thanks, Dave.  I let things take their course and got the all-clear from ARRL after getting new keys for my old callsigns.  Sorry, this is way too much hocus-pocus for my hardware brain but that took care of everything.  I applied for the endorsements and credited everything I had on LoTW.  It cost me $$$ but better now than when really retired.  I do wish that DXK would let you know that it submitted with a prompt or an OK box.  I wasn't sure if it actually changed everything to Verified until I checked it by searching.  

LoTW has certainly reduced the number of cards that I'll need to submit for my 5BDXCC.  I was dreading having to find hundreds of cards and now, I only need 23 cards.  Progress!

73,

'ES


Dave AA6YQ
 

+ AA6YQ comments below

Thanks, Dave. I let things take their course and got the all-clear from ARRL after getting new keys for my old callsigns. Sorry, this is way too much hocus-pocus for my hardware brain but that took care of everything. I applied for the endorsements and credited everything I had on LoTW. It cost me $$$ but better now than when really retired. I do wish that DXK would let you know that it submitted with a prompt or an OK box. I wasn't sure if it actually changed everything to Verified until I checked it by searching.

+ When you direct a DXLab application to perform a function, you can assume that it has done so successfully unless it informs you to the contrary.

73,

Dave, AA6YQ