Page 2 of 2

Re: TCP Inbound Connection

Posted: 18 Jan 2020, 11:46
Secondary channel in WSJT sends ADIF strings that should be collected with ADIF INBOUND services.

Re: TCP Inbound Connection

Posted: 18 Jan 2020, 14:36
by AE0S
HB9GVJ wrote:
18 Jan 2020, 09:59
I had to switch between 2237 and 2238 ports to make it work as it seems gridtrackerdoes not like to listen to 2238 :D
Was the port number in GridTracker red? That's how it tells that the port number is already in use by something else.

Log4OM doesn't complain to the user about used port numbers. It instead throws an error into the log file.

Important note to the devs: My highlights of shortcomings doesn't mean I don't appreciate your hard work. You did an awsome job and I just haven't listed all the great improvements you did. Thanks and sorry about that.

Re: TCP Inbound Connection

Posted: 19 Jan 2020, 16:01
don't worry about complaints :)
Testing a so big codebase it's hard and it's obvious users can find issues we never faced.

About throwing errors in the log, this is true. I'll check if i can add something more evident. In the HELP menu you can find some useful screens including a monitor of active threads/tasks in Log4OM that can give you an hint