Log4OM

I am not sure if my problem is a LoTW problem or a LOG4OM problem, so I will start here.

I am using WSJT, 2.1.0, JT Alert, 2.14.1 and LOG4OM, 138.0.0. When I log a FT4 contact into LOG4OM via JT Alert and then up load to LoTW, LoTW shows the contact as F4. When I download from LoTW to LOG4OM I get a message that the QSO is not found..…. MFSK.. If the contact is important to me, I will edit the contact mode to MFSK in LOG3OM and resubmit to LoTW and I will get the confirmation.

I would appreciate help solving this problem

Dave, W8QXR

The next release fixes this

Thank you Terry. Do you know when the next release is expected?

Dave, W8QXR

A couple of days Dave.

See viewtopic.php?f=1&t=4068

Terry,

I downloaded the new version. I have used JTAlert in the past just to be able to log contacts to LOG4OM. I do not intend to use it once I figure out how to get WSJT-X to talk directly to LOG4OM. Please let me know which box to check on the Communicator inbound settings menu and what port number to use.

Also, do I need to make any changes to WSJT-X?

73,
Dave, W8QXR

W8QXR wrote: 18 Aug 2019, 18:10 Terry,

I downloaded the new version. I have used JTAlert in the past just to be able to log contacts to LOG4OM. I do not intend to use it once I figure out how to get WSJT-X to talk directly to LOG4OM. Please let me know which box to check on the Communicator inbound settings menu and what port number to use.

Also, do I need to make any changes to WSJT-X?

73,
Dave, W8QXR

Page 191 of the user guide?

If you don't use JTAlert to log to Log4OM, then some of the JTAlert functions might not work - alerts, scan log, etc.

Terry,

Thanks- works perfectly. I should have realized there would be a new User Guide.

Dave, W8QXR