Sorry that I have not commented on this topic. I was on a business trip and unfortunately had little time. I have now taken a close look at it. The mistake is on my side, JTAlert is doing everything

VP8LP does NOT show as a user of LoTW, and has not for a long time in my system. However he responds quickly to a QSL card request. Neil N4FN

When are you going to give an example of a bad one? You did see where old LOTW calls will still be in the file, right? They may not be active anymore but were at one time. Mike W9MDB

When is this problem going to be fixed?

You can use just an ADIF file. Logger is highly recommended though. Make sure you back up whatever log you use. Mike W9MDB

Can JTAlert work without having to connect to a Logger? JoAnn AB8YZ

In the beginning I didn't... But finally, when I did it all worked great! Thank you so much Mike! 73 Jacek SP5APW pon., 23 lis 2020 o 22:27 Michael Black via groups.io <mdblack98@...>

Did you change the Report port in the 2nd instance? Each instance has to have a unique port. Mike W9MDB

Thanks for the quick answer! However the second JT Alert doesn't connect to WSJT-X: Jacek SP5APW pon., 23 lis 2020 o 22:07 Michael Black via groups.io <mdblack98@...> napisał(a):

Should be automatic....just run JTAlert twice after your start your WSJT-X instances. Mike W9MDB

Hi, I am working two instances of WSJT-X and would also like to have two instances of JT Alert, each one connected to a suitable instance of WSJT-X. Is it possible? If yes, how can it be configured? I

Thank you both. Not sure why I set 2237. Anyway all fine now. Tks, Geoff.

See the JTAlert Help file, "Settings -> Logging -> Log4OM V2" topic for JTAlert setup instructions (with pictures). It is a simple setup. de Laurie VK3AMA

Yes...you set up the wrong port. The port number in Log4OM should be the JTAlert port number for Log4OM and not the WSJST-X port number. You have 2237 in Log4OM which is intercepting the packets

Sounds like Log4OM2 is taking exclusive control of the WSJT-X UDP Server port preventing JTAlert from receiving the UDP data from WSJT-X. There is no need to have Log4OM2 directly interacting with

OM (Name?, Callsign?) A double quote will not break the QRZ logging. My tests with a single and multiple quotes, also using your provided comment, all successfully logged...

This what you mean?

No -- I meant the Connections screen in Log4OM. I sent a snapshot but apparently the image is blocked by your email. Look at it online https://hamapps.groups.io/g/Support/topic/78457207#32487 Mike

I presume you mean the JTAlert window. 2 pngs attached.

I start Log4OM2 before JTAlert with no such problem. What does you Connections screen look like?