Log4OM not automatically uploading to LOTW

[w7btm]

I have configured Log4OM to upload to LOTW on program exit... but it is not working at all. Not even a notice or error, just... nothing!

I have a verified login to LOTW. My Station ID is retrieved from Tsql so I assume that connection is working.
Upload to QRZ is working fine.

Also, my current connection settings work fine with WSJT-x, OmniRig and several other programs.

Here is a screenshot of my configuration page... is there something wrong with this?

Thanks!

Log4OM Not Uploading to LOTW.jpg (113.92 KiB) Viewed 1644 times

Here are my UDP connection settting:

Log4OM UDP Connections.jpg (56.07 KiB) Viewed 1642 times

[G4POP]

Have you got 'Upload QSO' set for your UDP connections as detailed on page 238 of the user guide? (Make sure that you have latest user guide or page numbers may differ.

I would alo recomment using a temporary path other than OneDrive as this can cause issues

[w7btm]

Thanks for the reply.

I did NOT have an "Upload QSO" UDP entry. I do have them for other connections that are working.

My usual problem is being confused by port number selection.

Also the instructions on page 238 do not specifically mention LOTW, so I assume this is a generic connection that will just work.

See screenshot below of my possible setup... will this work using the same port numbers are my other connections?

Thank you!

Possible UDP setup for LOTW.jpg (161.05 KiB) Viewed 1612 times

[KI5IO]

Bruce,

Why add another UDP inbound with yet another port?

Why not just 'edit' the existing JT Message on Port 2237 you already have in place?

Edit that existing port and tic the box to upload the QSO.

Give that a try first and see how things shake out. Adding more port numbers only just confuses the bee-jeebers out of things and 'me' as well.

.

[w7btm]

So, my "inbound" setting on port 2237 already had "upload QSO" checked!

I just dont' understand the UDP message system well enough. Why is an inbound message used when uploading TO another program (LOTW in this case)? Why isn't that an "outbound" message?

Anyway, something must still be wrong....

UDP Inbound Port 2237.jpg (68.45 KiB) Viewed 1580 times

[KI5IO]

Bruce,

Did you also relocate your LOTW Temporary Path to a folder location on your "C" drive say under "My Documents" or such a location? As Terry noted using 'One Drive' can also add issues that we've seen over the years in weird things.

One other item to look into would be the configuration settings in JT Alert itself. Settings in JT Alert can impact the uploads in Log4OM as well.

One other question: Can you do 'manual' LOTW uploads of Q's via the QSL Manager routine?

[w7btm]

Update.... I learned how to use "QSL Manager" in Log4OM which DOES work to upload to LOTW. That proves that my connections are working. But Log4OM still does not seem to upload automatically when I exit the program. And the shutdown messages fly by too quickly for me to see what it's doing on exit...

Also, I'm now trying this on a different PC. This is my Windows 11 PC that I am slowly building out. It's my secondary pc for now, I'm trying get used to Windows 11, but I don't like it very much. Anyway, Log4OM is working the same on both (and I never have both running at the same time).

I'm going to work on it for a while longer and update this thread when I have more information.