Log4OM

Unfortunately updating WSJT-X and JT Alert has caused the UDP ports to suddenly get messed up. The older versions worked great between WSJT-x, JTAlert and Log40m 2.
I went with wsjtx-2.4.0-rc1, then when noticing the message and having the problem rolled back to wsjt-2.3.0.
If I open Log40m 2 first followed by wsjtx, the Log40m gets a call sign in the window, but when jt alert opens there is an error message, nothing fills in it.
If I open WSJT-x and then JT alert both seem to work as wanted, but opening Log40m nothing happens there now. I am sure the UDP ports are the problem, reading the help explains their function and just confuses me further.

JT Alert settings (Logging)
Last QSL API (Checked) for enable transmitting of last QSL
UDP port (2333)
Log 40M V2
(checked) Enable Log40m V2 logging
UDP (2335 adif message port (2241) control port
Applications
Resend WSJT-X UDP packets ( unchecked)

LOG40M-V2 Settings
Connections UDP inbound connections
jt_message (2237) wsjt_direct
ADIF_message (2235) ADIF_Message
JT_Message (1240) jtalert_rebroadcast
Jt_message (2333) JT DX_ DX call

There are no out going UDP listed

Suggest that you download and read the latest version of our user guide and follow the set up steps religiously

I have done so and am still confused. Would have been more helpful to have the communication path better defined. Wsjt-x sends to this port and JT Alert receives. Logging program needs data sent to this port.

What it looks like is if JT Alert starts first it captures the port that Log40m V2 does if started first. So the second program is not receiving data. Actually I did have things working before the updating, even had a second (field day logger) working when it was needed.. Just do not see what I am missing.

Thanks for the response, hope I can help you someday too!

kb8pxm wrote: 08 Feb 2021, 01:21 Thanks for the response, hope I can help you someday too!

Caustic comments do not encourage us to help you!

We know that if the systems are set up as described in the user guide it all integrates and you admit it has for you in the past! and it works for hundreds of other users! so its a fair assumption to expect you have something set wrongly.

The reason I initially refer users to the guide is because otherwise I end up repeating the user guide instructions every time a user asks a question on the forum, it gets very repetitive!

• Have you checked that a recent update of your antivirus or firewall is not blocking the programs?

• Have you installed ALL programs to 'Run as an administrator'? if not please again follow the instruction's in the user guide for doing that.

• You stated that a recent upgrade of JTAlert and WSJT caused the issue so the assumption is that something changed in those programs, either a setting or their code was changed or perhaps you had a bad install, so why not check them for errors?

• CAT control is shared by WSJT and Log4OM via the multi-threading capability of Omnirig providing all are running as admin and that you select OMNIRIG in WSJT as your radio NOT the actual radio.

Set up correctly JTAlert reads from WSJT and directly logs to the Log4OM SQLite database, providing Log4OM is open. (Page 201 of our latest user guide)