Sorry I am coming to the party a little late in response to these emails.. Spent the last 2 weeks camped along the Moose River in the middle Adirondack Mtns of NY Trout Fishing.(My 2nd love after radio.) It is truly amazing how the fish population has returned over the last 15 years after being almost wiped out totally by acid rain.
In N1MM we use same TCP connection as DXLabs does using the DXLabs Radio API. For Radio #1 we use TCP port 52002 and UDP port 2237 For Radio #2 we use TCP port 52004 and UDP port 2239 When setting up the connection for Radio#2 we have the user setup in the second instance of WSJTX to set the Network Server window to be 127.0.0.1:52004 so that the correct settings will be used. I along with Mike have had Dennis run the log output for the radio config and each time when WSJT goes away nothing special is written into that log. The error report and the Radio TCP Error window are produced because the TCP connection from WSJTX has been dropped. This is just the warning to the user that something has happened. I personally have not experienced this issue as I am only setup here to run SO1R so I am only using one instance at all times. I'm not sure what other information you might need but will answer anything sent my way. 73 Rick N2AMG
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
