New release Problem

[W4EBB]

I just did an update, two levels, both 2.31 and 2.35. Now log4omV2 will not add qsos to log4om but they do go into wsjt-x log. I think I have a UDP problem. I have tried to delete UDP entries and then reestablish them in log4om and also JtAlert. With no success. I have read thru the user guide with no success. I did not find any warnings about UDP with the new releases, maybe I just did not find them. Need help! Thanks!
Charlie
W4EBB

My settings:
WSJT-X UDP 2237
secondary 2233

JTALert
2235 adif msg port
1241 control port

log4om
connections
UDP INBOUND adif -msg 2234 incoming jt-alert/gt adif

[KI5IO]

Take a look at this "headline" on the Forum.

Many, many posts about the "requirement" to delete and re-establish the UDP connections.

https://forum.log4om.com/viewtopic.php?t=8260

[G4POP]

Your Log4OM UDP port numbers don't match the ones from jt software!

[W4EBB]

Here are some snips of what I have set for the UDP. I just can't get it to log. I could only attach 3 screen shots, so I will include the other 2 in a second reply message.

[W4EBB]

Here are my other 2 screenshots...

[KD0ZV]

I have a teamviewer session scheduled tomorrow afternoon to resolve this.

Rich

[W4EBB]

wsjt-x 2.61.1, log4om 2.27.1.0 and jtalert 2.60.10 works just fine. I decided to update log4omv2 to 2.32.0.0 with exact same UDP settings (after removing them and reinstalling UDP stuff}. Now Log4omv2 will NOT post qsos. So I went back to what was working.

I then enlisted the help of rich, an "A" team member. He could not get it to work. He also tried log4om 2.29. Would not post just like 2.32. He also updated JtAlert to 2.62.1. No Joy. Same thing. Will not post qsos. All with same settings.

So I tried rolling back to original settings. Now it would not work. Would not post qsos. So I rolled JtAlert back to 2.60.10 and all is well. Seems to me there is something in JTAlert (after2.60.10) causing the no posting qsos problem. I did not find anything in the help manual to guide me. Any thoughts PLEASE

Charlie
W4EBB

[G4POP]

Yes contact the author of JTAlert for assistance, we cant edit his software

[W4EBB]

I am up and running on the latest log4omv2, jtalert and wsjt-x. I found help from someone willing to spend a little time on me even though it wasn't "in his department". I am feeling very fortunate.
Charlie
w4ebb

[KI5IO]

I am up and running on the latest log4omv2, jtalert and wsjt-x. I found help from someone willing to spend a little time on me even though it wasn't "in his department". I am feeling very fortunate.
Charlie
w4ebb

Charlie,

Excellent and thanks to the OM who was able to help you out.

Now ... what would even be better is if you would very clearly set forth what was done to resolve your issues.

Such input will help all Log4OM users.

I'm looking forward to that detail from you.