Re: Problem with JTAlert 2.16.17


Norman Heyen
 

Thank you for your help Joe,
Unfortunately that is exactly what I have setup. I cannot seem to be able to make it work in any version later than 2.16.10 - works fine there but anything newer opens but gives me the error message.
Any other place that I can look?
Norman


On Tue, Feb 23, 2021 at 2:34 PM Joe Subich, W4TV <lists@...> wrote:


 > Unable to communicate with the WSJT-X process.
 >    UDP Port : 2237
 >    IP Address : 127.1.1.1
 >    Values read from WSJT-X config file...
 >      C:\Users\nheye\AppData\Local\WSJT-X\WSJT-X.ini

In WSJTX -> File -> Setting -> Reporting -> UDP Server

Set UDP Server (IP Address) = 127.0.0.1
Set UDP Server port number = 2237
Check "Accept UDP requests" and "notify on accepted UDP request"


73,

    ... Joe, W4TV


On 2021-02-23 10:47 AM, Norman Heyen wrote:
> I have been having issues with JTAlert versions after version 2.16.10
>
> Version 2.16.10 works well with my setup but it is time to update. My
> setup is:
> DXLab Suite working with WSJT-X version 2.3.0
> Running Windows 10 20H2 fully patched to current levels
>
> With 2.16.10, everything works fine, logging and all that. But with
> 2.16.17, nothing is filled in the main window and I get this error message:
> Unable to communicate with the WSJT-X process.
>    UDP Port : 2237
>    IP Address : 127.1.1.1
>    Values read from WSJT-X config file...
>      C:\Users\nheye\AppData\Local\WSJT-X\WSJT-X.ini
>
> WSJT-X Detected Instance...
>    Process Window Title : WSJT-X   v2.3.0   by K1JT, G4WJS, and K9AN
>    Process Command Line : "C:\WSJT\wsjtx\bin\wsjtx.exe"
>
> Decode alerts and logging will be unavailable until corrected.
>
> So I am sure I've missed a step somewhere. Can someone point me in the
> right direction?
> Thanks!
> Norman
> KC9NVN







Join Support@HamApps.groups.io to automatically receive all group messages.