Yet another LOTW question

[N4TII]

I'm a first time user of LOG4OM - and it was just an oversight when doing the initial install of the program. We're good now and it's behaving how I wish it to behave.

[kq4aji]

I have seen similar behavior and checked my ITU and found it was 8 vs 6. I fixed it today

I also have a lot of REQUESTED status under the LOTW Confirmed field since 6/22/2025. Even after several sessions with LOG4OM close and opened over that time, most remained at REQUESTED, some changed to YES or NO but most are REQUESTED.

This never happened before, as after a LOG4OM session, the next time they showed YES or NO.

Any thoughts on it there was a code change in those area. Or is there a process to fix this behavior, or is now the way it is?

[G4POP]

I cant accertain if there were any changes in that area because you dont state whet the release number is of Log4OM, please dont say the latest! I need thactual release number found in help/about

Sugggest you try bulk editing the requested status in the QSO manager to N - No

[kq4aji]

LOG4OM v23.6.1.0

Will do on the bulk change. Why does it get marked as REQUESTED when it has been sent? I do regularly download LOTW via the QSL Manager. Thanks for your help.

[G4POP]

LOG4OM v23.6.1.0

Will do on the bulk change. Why does it get marked as REQUESTED when it has been sent? I do regularly download LOTW via the QSL Manager. Thanks for your help.

Check your settings in Program Config/Confirmations

Also watch the three Youtube tutorials Confirmations, confirmations 2 and confirmations 3

BTW no code changes in this area for several releases

[KI5IO]

Phillip,

You didn't mention if you are also using the FTxx mode of communications. However, I did see on your QRZ page that you do a lot of FT8.

Thus you are likely using WSJTx, JTAlert and/or Gridtracker and such related 3rd party APPs.

Those APPs have options/settings that also set the flags for uploading Q's and labeling with Yes, No, Requested, etc..

Log4OM does not change such information as it comes from those 3rd party APPs.

Be sure to check the settings in all those APPs you use and choose what you want them to do.

Myself I'm old-fashioned and simply use Yes and No for Q's being sent/received. You can be sure those 3rd party APPs do that as well and then let Log4OM properly adjust the Yes/No status when the Q's are uploaded via QSL Manager.

And, as Terry noted, be sure to watch the 3 Y/T videos about Confirmations.

[kq4aji]

Nolan,
Thanks for the info and insight. I did check that JT Alert is sending the QSO to LOG4ON (as set up to do) and it has the R in the LOTW Conf Received as you suspected.

I the past when I had a Phone QSO the flag was initially R but when LOG4OM closed the LOTW transactions happened and when I open LOG4OM the flag was set to N till I ran QSL Manager to download confirmations. Short story is that it was working as YT videos taught.

Your are correct that something about FT8 and JT Alert, looks like when I started using JTAlert the R flag gets stuck.

No worries, I will fix it in Bulk. Wanted to get FT8 WAS completed and then switching back to PHONE for DXCC (14 to go!)

BTW I have PHONE WAS and it took about 3 years, FT8 has taken me 6 weeks for 50 State except a QSL on Hawaii (3 QSO's)

Thanks again for listening

[KI5IO]

Phillip,

Glad you will get it sorted.

I'm a CW - only station anymore. I ran some FTxx a number of years ago to help test new options for Log4OM V2 when I was on the Alpha Support Team, but that mode wore thin on me quite fast.

And I'm pretty sure I have a microphone in a file cabinet drawer somewhere for my K3, but would have to dig to find it.