Log4OM

JtAlert does not receive confirmation after logging QSO in through Log4OM_2.
There should be feedback from Log4OM to JtAlert as it was in version 1.
Maybe you need to set some UDP OUT action?

There is nothing returned to JTAlert except the default UDP handshacking.

That is, it is impossible to make confirmation in JTAlert whether QSO was logged in correctly as it is in ver 1 Log4OM ?

A new version of JTAlert which supports Log4OM V2 is pending release, we are told.

If you want to continue to use JTAlert, I recommend that you turn off logging in JTAlert, and log directly from WSJTx or JTDX into V2. Note, if you are using the DX Call forwarding to V2, you will need to setup Rebroadcast of the UDP messages in JTAlert. I covered how to do this in this thread - viewtopic.php?f=33&t=4324&start=10

73,
Doug
W7DRM

IW3HMH wrote: ↑18 Jan 2020, 11:44 There is nothing returned to JTAlert except the default UDP handshacking.

Think he is referring to the not logged warning from JTalert due to JTalert not being able to read the version 2 database

Thank you for the information, you have to wait for the JTAlert update.
Login works correctly only JTAlert does not receive confirmation.