开云体育

+ AA6YQ comments below

Now I'm not sure it's not me, but it seems for the last couple months, usually after I get done updating from a contest. I get a
message that say updating 29 QSO's. This happens every time I do a SYNC LOTW QSO's on the QSL tab. It says Inspecting 29 QSO's
and setting LOTW Sent to "Y".

Any thoughts ??

+ That is correct behavior. The "Sync LoTW QSOs" function directs LoTW to report all QSOs accepted by LoTW since the last time you
invoked "Sync LoTW QSOs". For each QSO reported as accepted, DXKeeper changes its "LoTW Sent" item from 'U' (meaning "uploaded but
not accepted") to 'Y' (meaning "accepted").

+ See the state diagram in

<>

+ and step 2.e in

<>

73,

Dave, AA6YQ

The last few times I’ve done Sync LOTW QSOs, it shows the same number of QSOs and the same date (3/30). I figure it’s a problem at HQ, and ignore it for now. When they get back to work, maybe it won’t happen.

+ AA6YQ comments below

The last few times I’ve done Sync LOTW QSOs, it shows the same number of QSOs and the same date (3/30). I figure it’s a problem at HQ, and ignore it for now. When they get back to work, maybe it won’t happen.

+ From what I can tell, LoTW has been working correctly for the past several days. Have you submitted new QSOs after 3/30 ?

73,

Dave, AA6YQ

A new version of TQSL showed up today as well., I assume this may be in response to some of the upload issues for the last few weeks???


Dave
NR1DX

--
This email has been checked for viruses by Avast antivirus software.

Yes. It still shows the same date, and still updates the same 900 QSOs.

+ AA6YQ comments below

Yes. It still shows the same date, and still updates the same 900 QSOs.
That was as of this morning.

+ Please attach the file

LOTW_QSOS_ADI.txt

+ from DXKeeper's Databases folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

+ AA6YQ comments below

A new version of TQSL showed up today as well., I assume this may be in response to some of the upload issues for the last few
weeks???

+ No. The upload issues to which you refer were entirely attributable regressions in the LoTW Server.

+ Here's the content of TQSL 2.5.2:

Major feature Additions:

When a log is signed by TQSL, the station details (Callsign, DXCC entity, Gridsquare and other QTH details provided by the selected
Station Location (and Callsign Certificate) are compared to the details provided by the log. When the log states that the US State
is one value but the Station Location gives another, TQSL rejects that QSO. This will allow detection of errors where a station
location is incorrectly chosen. This feature requires that the log provide station details, which previously were not used by TQSL.
Once a logging program supplies these (MY_STATE, MY_DXCC, MY_CQ_ZONE, etc.) then TQSL will validate them against the log. Cabrillo
logs now use the "My Callsign" field to verify that the QSOs are for the correct callsign.

Optionally, a station performing roaming operations (multiple gridsquares) can choose to have TQSL assume that the log is correct.
When callsign or QTH are provided with the log, TQSL will update the details on the upload to Logbook automatically. This behavior
is enabled by selecting "Override Station Location with QTH details from your log" on the "Log Handling" preference page.

When submitting requests for US 1x1 callsigns, which must always be a signed request, ensure that the flow properly marks the
callsign as 1x1, and that the requester has a valid callsign certificate that can be used to sign that request.

Minor Updates:

- Add diagnostic log lines suggested by David, W1HKJ.

- Fix centering of date fields in the date range prompt dialog box.

- When a user is changing the language, the current language is now selected in the language selection dialog.

- TQSL now handles Unicode/UTF-8 format "Cabrillo" files by ignoring the extra bytes before the "START-OF-LOG" signal.

- If a BAND is provided for a QSO along with a FREQ, where that frequency (or receive frequency) is outside the related ham band,
ignore the FREQ setting.

- Ensure that messages from TQSL are properly translatable - some long messages were not entirely translated.

Defects Corrected:

- TQSL now issues an error message when an unrecognized file is loaded as a callsign certificate file. Previously, TQSL simply
ignored the invalid file.

- When TQSL is verifying a US callsign, it could fail and reject a callsign certificate request if the data from the FCC had become
corrupted. TQSL now ignores the data in many of these cases by doing additional lookups of known good callsigns to verify that the
ULS data is valid. TQSL now provides the last update date for the ULS database to the message displayed saying that the ULS data is
missing. When fetching the ULS data fails, TQSL no longer rejects callsign certificate requests, which are allowed to work without
address data.

- TQSL now reports when it is unable to open the files needed to connect to Logbook. There were cases where critical files were
missing from the installation, but the error displayed did not provide useful guidance for correcting the error.

- When https (Secure) connections to Logbook fail, tqsl now falls back to trying insecure (http) requests. This allows systems with
anti-virus software that interferes with network connections to recover. A system running such software is inherently insecure, so
bypassing https is a reasonable workaround.

- ULS checks are no longer performed for US 1x1 callsigns.

- Ensure that expired or otherwise invalid certificates in the chain verifying a user Callsign Certificate are properly reported.
This fixes an issue where in some cases (TQSL on Mac) trying to install an expired callsign certificate (an out-of-date TQ6 file),
would cause an unexpected error "unable to get local issuer certificate". Trying to load an expired TQ6 file now causes an
appropriate error message.

- Correct the behavior when backing up in the Callsign Certificate request wizard so that spurious pages are not displayed.

+ From

<>

73,

Dave, AA6YQ

Last night I downloaded the new TQSL version and upload three QSOs I made yesterday. I then ran sync and it worked, with the correct dates and only 13 QSOs reported. So whatever it was appears to be fixed.

+ AA6YQ comments below

Last night I downloaded the new TQSL version and upload three QSOs I made yesterday. I then ran sync and it worked, with the correct dates and only 13 QSOs reported. So whatever it was appears to be fixed.

+ ARRL Staff corrected the responsible regression on April 3:

</g/DXLab/message/192489>

73,

Dave, AA6YQ