开云体育

This release

- informs the user when a "Sync LoTW QSOs", "Sync LoTW QSLs", or "Update from LoTW" operation produces a "Username/password
incorrect" response from LoTW; in previous versions, the user had to inspect the file received from LoTW to see this error message

- enables the "Sync LoTW QSOs", "Sync LoTW QSLs" functions to work correctly when the CTRL key is depressed after the breaking
changes made by the ARRL to LoTW's lotwreport programmatic interface (tnx to Vince VA3VF)


Notes:

1. Update your firewall and anti-malware applications to consider this new version of DXKeeper to be "safe"


2. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<>


3. After upgrading, to revert to the previous version of DXKeeper, see
<>


DXKeeper 15.4.9 is available via the DXLab Launcher and via



73,

Dave, AA6YQ

Dave wrote:

"- enables the "Sync LoTW QSOs", "Sync LoTW QSLs" functions to work
correctly when the CTRL key is depressed after the breaking
changes made by the ARRL to LoTW's lotwreport programmatic interface (tnx to
Vince VA3VF)"

Can you explain this a little more? Mine seems to be working fine with
v15.4.8 after I did a manual date change for "Sync LoTW QSOs" and "Sync LoTW
QSLs" after ARRL broke it and then later fixed it.

Should you only do this if it's not working? I don't want to re-download all
307k QSO records and 176.5k QSLs if I don't have to! HI

Thanks,
Don AA5AU

I had a new experience recently. Since I am quite a newbie, I got a message that I had to renew my callsign certificate. So I did. I received my new certificate the following day and didn't activate it right away (I had no idea it inactivates my existing certificate. I kept on doing business as usual but noticed 4 or 5 days later that no new QSOs were in LotW. When I went to LotW and checked my account message, I found that LotW generated an error message: "Processing ABORTED: INVALID CERTIFICATE - Certificate may not be used. Certificate status = Superceded". I am not sure if this gets passed back to DXK, but if it does, it would be cool to display the error to the user. Obviously this is super low priority if not even nice to have.

+ AA6YQ comments below

I had a new experience recently. Since I am quite a newbie, I got a message that I had to renew my callsign certificate. So I did. I received my new certificate the following day and didn't activate it right away (I had no idea it inactivates my existing certificate.

+ The second sentence in

<>

+ is "Note that if you renew Callsign Certificate before it expires, requesting the renewal immediately invalidates the existing Callsign Certificate."

I kept on doing business as usual but noticed 4 or 5 days later that no new QSOs were in LotW. When I went to LotW and checked my account message, I found that LotW generated an error message: "Processing ABORTED: INVALID CERTIFICATE - Certificate may not be used. Certificate status = Superceded". I am not sure if this gets passed back to DXK, but if it does, it would be cool to display the error to the user. Obviously this is super low priority if not even nice to have.

+ LoTW does not make that error message available to applications like DXKeeper.

+ If you routinely invoke "Sync LoTW QSOs" then click the LoTW button in the Filter panel at the bottom of the Main window's "Log QSOs" tab, the Log Page Display will be populated with any QSOs submitted to LoTW but not yet accepted by LoTW , enabling you to investigate if necessary.

73,

Dave, AA6YQ

+ AA6YQ comments below

"- enables the "Sync LoTW QSOs", "Sync LoTW QSLs" functions to work correctly when the CTRL key is depressed after the breaking
changes made by the ARRL to LoTW's lotwreport programmatic interface (tnx to Vince VA3VF)"

Can you explain this a little more? Mine seems to be working fine with
v15.4.8 after I did a manual date change for "Sync LoTW QSOs" and "Sync LoTW QSLs" after ARRL broke it and then later fixed it.

Should you only do this if it's not working? I don't want to re-download all 307k QSO records and 176.5k QSLs if I don't have to! HI

+ In an effort to prevent abuse by users who continuously download all of their QSOs from LoTW, the ARRL made changes to the API
that DXKeeper uses to obtain information about submitted QSOs from LoTW. In the course of making those changes, they introduced two
regressions, both of which were and reported by DXLab users and corrected by LoTW Staff within 48 hours.

+ They also made an unannounced permanent change to the API that broke the ability of DXKeeper's "Sync LoTW QSOs" and "Sync LoTW
QSLs" functions to request all accepted QSOs or all confirmed QSOs respectively by depressing the CTRL key while invoking the
operation. These "request all" functions should only be used when switching to DXKeeper from another logging application that does
not include LoTW status information in the ADIF file it exported.

+ DXKeeper 15.4.9 restores the ability to "request all" by depressing the CTRL key while invoking "Sync LoTW QSOs" or "Sync LoTW
QSLs". There is no need for any current DXLab user to do this.

73,

Dave, AA6YQ