JTAlert Message: Failure: QSO Not logged

[VE3TKI]

I am a new user of Log4OM 2 (version 2.3.0.0). I have not been able to get Log4OM to automatically log contacts from JTAlert/WSJT-X. In particular, I get a “Failure: QSO not logged” message from JTAlert after I manually save an FT8 qso from within WJST-X. I would appreciate any help you can provide.

The details:

When I select an FT8 call in JTAlert, his call and frequency etc., are displayed correctly in the Log4OM qso window.

I have the following settings:

In Log4OM 2/Configuration/Software Integration/Connections/Remote Control tab:

Remote Control port 2241, enable remote control is checked

In Log4OM 2/Configuration/Software Integration/Connections/UDP tab:

In UDP Inbound Connections:

[UDP_INBOUND] [ADIF_MESSAGE] [2235] JTALERT QSO, checked
[JT_MESSAGE] [1240] JTALERT REBROADCAST, checked

The box below says: 2 items selected, and underneath that message it says WJST-X default port: 2237

In WJST-X File/Settings/Reporting/Network Services:

UDP Server: 127.0.0.1
UDP server port number: 2235 (Note the Log4OM Manual page 143 incorrectly says 2233)
Accept UDP requests, Notify on accepted UDP request, Accepted UDP request restores window: all checked

In JT Alert settings/Manage Settings:

Logging: Log4OM V2
Send WJST-X DX Call to Log4OM: checked
UDP Connections: IP Address 127.0.0.1, ADIF_Message_Port 2235, Control Port 2241

Applications/WJST-X/JTDX:
Rebroadcast WJST-X UDP Packets (received only) checked, IP address: 17.0.0.1, UDP port is 1240

Thank you.

Michael Brickell VE3TKI

[KD0ZV]

Do you have the path to your Log4OM SQL file set to the right location in JTAlert under Log4OM V2?

I think that is not in the manual

[VE3TKI]

Thanks Rich;

That was the problem. I had not set the path in JTAlert. Once I did , everything worked fine. Thanks!

Michael VE3TKI

[KD0ZV]

I ran across that last week. Hopefully Terry will see this thread and chime in and update the manual if needed.

I found out by mistake when I moved my Log4OM data file and forgot to change that setting in JTAlert. I was getting same message as you were and as soon as I fixed the path it was fine.

Rich