Log4OM

Hello All,
I have been using Log4OM, WST-X and grid tracker together for years. Actually never been a problem. Even now everything seems to be working fine. A QSO is neatly logged after termination of the QSO. Gridtracker nicely shows the QSO and other DX connections at the moment. But what no longer works is entering Callsign etc after clicking on a call. So no name etc. is shown anymore and no information from QRZ.com like the photo. I've been searching for hours but can't figure out what the cause is. These are my settings:
WSJT-X UDP server 127.0.0.1 udp: 2333
Enabled PSK reporting spotting and Use TCP/IP connection

and
Secondary UDP server same IP and UDP 2237

Log4OM > Connections
UDP Inbound:
[JT_MESSAGE} [2236] Grid tracker
[ADIF Message] [2234] Incoming JT Alert/Gridtracker
[JT-Messag] [2237] Incoming JT Message

Please help

Have you followed the user guide re 'Remote control'?

You have multiple incoming UDP data flows, I am surprised that your not getting duplicate log entries

Thanks Terry, Sorry Terry I didn't see your reply. Sorry Terry I didn't see your reply. But I adjusted the settings. That works the way it has always worked. The only problem is that it doesn't work properly if I don't have GridTracker started. Then Callsign etc is not filled in clicking on a call. So no name etc. is shown anymore and no information from QRZ.com like the photo. The QSO is stored in the logbook.

WSJTX:
UDP 2233 > Accept UDP requests

Sec. UDP server 2237

Log4OM inbound connections:
[ADIF_ message] [2237]
JT_message] [2239]

Gridtracker:
Receive UDP messages: 2233
Forward UDP messages: 2239

Logging: Gridtracker Startup | LOG
PSK reporter Menu | Startup

And the Log4om udp port is set to?

Terry, did I forget a port? I think everything works properly.

G4POP wrote: ↑24 Mar 2024, 21:20 And the Log4om udp port is set to?

No answer, please tell me what you mean