Log4OM

I also have the same problem with version 2.27 any new station I have not worked previously name information etc box is not populated I have gone back to earlier version which works ok.

I cant duplicate this.

So to confirm you deleted your connections and have started over?

You have a functioning lookup service? So if you type that stations callsign in the Main UI it will return all the proper info including name?

If that is the case, please confirm the port in your WSJT settings. And after removing all connections in Log4OM add one connection using the preset with that port from WSJT. Make sure nothing else is running that can conflict with that port use. Don't add any other connections until we finish with WSJT.

Restart Log4om and WSJT-X just to be safe

I have tested with Worked B4 and new and its working fine business.

Rich

I had to reboot the pc a couple of times, after deleting the old UDP settings and entering the new ones, before everything worked. All works now except auto upload to QRZ, which was working on the new version yesterday.....

What happens if you log directly in Log4OM main UI? Does it go to QRZ then?

Yes. if not running WSJTx

NI4TG wrote: ↑22 Mar 2023, 18:27 Yes. if not running WSJTx

Have you deleted all the connections and started over? Only setup an incoming WSJT connection using the preset and whatever port you are using in WSJT?

No. I did confirm required info still there and port numbers confirmed. I may delete, restart and see what happens, thank you.

Yes, you need to delete the connection and re-add it.

NI4TG wrote: ↑22 Mar 2023, 20:27 No. I did confirm required info still there and port numbers confirmed. I may delete, restart and see what happens, thank you.

As I have posted elsewhere if you had an existing UDP connection you must delete it and re-instate it but be sure to note the port you were using and select that port in the new UDP connection

KD0ZV wrote: ↑21 Mar 2023, 21:08 Both actually

I found the problem why the callsign field was not filled when calling a station in WSJT-X and the GRIDs were saved with 6 digits instead of 4 as saved in WSJT-X.
I am also using GridTracker and changed the Incoming GT settings from ADIF_MESSAGE to JT_MESSAGE as it was before.
I cannot explain why it now works again but it does
Attached you can see my other settings, maybe there you can find the problem why ADIF_MESSAGE is not working properly for GT in my setup.

73
Stefan