HomeSoftware & Software SupportLOTW_EQSL_Utility

LOTW_EQSL_Utility is an application that allows you to export your LOTW and eQSL marked qso’s from Logger32 or an existing ADIF file and process them to the format of the service you are using and automatically upload them to either LOTW or The application also allows you to download QSL’s that are waiting since the last time you downloaded from the service or your whole inbox on either service and then sync those records into Logger32. As of version 1.3.0 the ability to Upload Qso’s to and has been added. Also a full featured FTP application is now included to upload/Download your backups to a webserver or ftp site.
Version 1.4.96 will work with both TQSL v 1.13 and the new TQSL v 1.14
Current Full Version: 1.4.98
Full Install

Current Update Version: 1.5.01


LOTW_EQSL_Utility — 68 Comments


  2. Mariao..

    Are you using Windows 10?? If so try running both Logger32 and the LOTW Utility using the Run as Administrator settings in the properties under the compatibility tab.

    Also do you have any programs called unchecky installed?? This is also know to minimize the program and make it un-accessible.

    Let me know if either of these work for you..

    73 Rick N2AMG

  3. Rick, Thanks so much for the help. I had no idea that unchekit program was installed. I stop it and now works perfectly!!! I take this opportunity to say thank you again for the application as it is excellent, years using it. greetings, Mariano lu7ec

  4. My Logger32 will not create an ADIF Audit Trail.txt file. If I manually create the file, it will not write new logs to it. I only use the section of the LoTW_eQSL utility. I had this working before but have a new OS and software. Any suggestions?

  5. Dave.
    In the utility there is a checkbox that indicate you want to use the Audit Trail File. Once that check box is checked it will tell Logger32 you want to use the Audit Trail and it will start saving the file. Or you can turn it on in the Logger32.ini file. Look for this ADIF Audit Trail=0 if you can’t find that entry in the Logger32 place this entry in the Logger32.ini Under the [Globals] section ADIF Audit Trail=1

    Reboot Logger32 and it will not create the Audit trail and will update the file anytime a qso is logged, Changed, Or edited..

    73 Rick N2AMG
    Sorry for taking so long to answer. I did not get a message from my website that a post was made..

  6. bonjour
    je souhaite que chaque qso apparaisse sur ma page dans la rubrique club log quelle est la maniere d’installation

  7. Roger..
    I’m not sure I follow what you are asking for.
    DO you want your logbook to be uploaded to ClubLog or do you want your ClubLog qso’s to shown on your QRZ page??

    My utility does nt interact with QRZ in that way. I am in the process of re-writing this application to allow users to upload the L32 qso’s to be uploaded to but progress on that is moving slow as I do not get much time for programming.

    73 Rick N2AMG

  8. Rick
    I consulted on the call an operator and each time he made a QSO celui_ci was displayed immediately on the log clublog of
    I wanted to know how to install. Personally I have a QSO each export my part since logger32 log to log club.

  9. Hello
    I have exactly my last fifteen QSO appear on clublog my page.
    I wanted to know if it is possible that when I made a QSO it automatically appears on the page soon as I logged on log 32?

  10. Ok I understand now..
    When a qso is uploaded to ClubLog it takes between one minute to up to ten minutes before the qso is processed depending on how much server load there is. You should be able to see your qso on the QRZ display right after that is done. The ClubLog display does not refresh itself automatically so you would need to refresh your browser for the display to update and download the new qso activity. And after doing that the new qso should be listed.

    73 Rick N2AMG

  11. Ralph..
    before you upload your qso’s look in the logger32 directory for these files ClubLog_Dump_File.txt or ClubLogNotUploaded.adi if you find either one delete them. Then do your bulk upload to ClubLog…
    Somehow one of those files did not get deleted and it is trying to upload those qso’s using the realtime upload.. In the new version I am working on this will be fixed.

    73 Rick N2AMG

  12. Hi Rick.

    Seeing as you are working on a new version, I have two suggestions and two bugs to report:

    1. Please cut down the number of confirmation clicks for the things we do routinely. If there is some reason to retain all the confirmations, I’d settle for an “Expert mode” config option that lets me pick and choose between them.

    2. Please change the logic sequence so that the log is not updated in Logger32 to show QSOs sent to LoTW until AFTER a signed-and-uploaded LoTW file is received and starts processing on the LoTW system. If the upload fails for some reason, the current version incorrectly updates the log.

    3. The version checker option under Help shows that my current version is 1.4.99 and the latest, but this page (above) refers to 1.5.01 … which turns out to have the same size and date/time-stamp as the file that calls itself 1.4.99.

    I’d be very happy to help with specifying, testing and/or documenting the new version, Rick, if you like. I use L32 and your utility a lot, and I’m a tech author by day, a reformed IT auditor too! 73 Gary ZL2iFB

  13. Hi Gary..
    Re #1 and 2..
    Those are all done in Logger32. When you press the upload to lotw button the program sends a message to Logger32 that the user wants to export records to LOTW. LOgger32 then takes over and does its thing with the export. When it gets done outputting the file it then sends a message back to the utility so the utility can call TQSL to sign and upload. There is very little that the utility has for user interaction.

    Re#2 I will email Bob and see if there is something else we can do here as I have been bit also by a unable to upload export file and had to changes qso’s back to show they were unsent…

    #3 I will have to check out the working directory on my computer and see what caused that. There were changes made in the last version and it should have changed the size of the .exe file..

    I will keep you in mind when I get close to testing it. I have 3 tabs left to work on so as I get those done i will email you a copy..

    73 Rick N2AMG

Leave a Reply

Your email address will not be published. Required fields are marked *