Sorry my error, having changed to wsjt-x 2.3.1 and then gone back to 2.3.0 because there is a problem with 2.3.1, I hadn't noticed that the UDP server settings were unchecked. All ok now. 73 Geoff.

Yes 73 Geoff.

Just started to use digi modes after a few weeks break and I find that clicking on the callsign in the JTAlert window no longer initiates a qso. Using 2.16.17 and wsjt-x 2.3.0 Any ideas why this shoul

Hi Glyn. Just set wsjt-x to use omnirig 1 or 2 depending on which one you have selected for the 7300. 73 Geoff.

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

This what you mean?

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

Using Flex 5000a, wsjt-x 2.2.2. Win 10. I have noticed that if Log4OM2 is started before JTAlert then the band in use is not shown in the title bar, ie JTAlert 2.6.16, callsign[20m etc.......]. A seri

Patrick. May I recommend Log4om2. Brilliant program and I have used it successfully for some time now. Auto logging with it is very easy. Enjoy. 73 Geoff. G4XMJ