QSOs have not been dropped despite the fact that I don't change TX frequency. Good to know. My experience has been the same as yours with most activations, but not all.

Understanding the Context

Either WSJT-X changed - and that is possible since I stopped following WSJT-X developments a long time ago - or the DX is not using WSJT-X, MSHV perhaps. Problem is that some 800 lotw confirmations (of about 1600) are missing from my QRZ log (the contacts are there, just not confirmed) Must have had some ACLog problem? can I use the "import all records" to this problem without duplicating qsos? or is there another explanation.

Key Insights

KF8KI QRZ Staff EngineerQRZ HQ Staff QRZ Page Since you didn't provide the other callsign, I can't help beyond telling you that this is a problem that occurs when the user does not properly have their DX entity set in their operating location, found under settings > logbook properties. It's relatively common for things like DXpeditions and secondary callsigns where the logbook wasn't set up ... Do not put baluns in single element dipoles that would be used for anything other than the frequency they're cut for or the appropriate odd harmonic. Multiple-element "fan" dipoles are great with a good balun. Always use current baluns.

Final Thoughts

The ONLY exception to this are the Radio Works "Remote Balun" and another 4:1 balun called the "Centaur". FLDigi not uploading from QRZ, error blank, May 2017 Discussion in ' QRZ XML Logbook Data ' started by KD8M, . Callsigns not found using API Discussion in ' QRZ Site Community Help Center ' started by KC3RDV, .