[wsjt-devel] WSJT-x Stopping
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
Re: [wsjt-devel] WSJT-x Stopping
Mike, I don't see anything in that thread that resembles the issues we are having. Ron, WV4P On Wed, Aug 24, 2022 at 10:50 PM Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > See if this thread helps at all... > > https://groups.io/g/N1MMLoggerPlus/topic/89323949 > > Mike W9MDB > > > > > On Wednesday, August 24, 2022 at 04:59:32 PM CDT, Ron WV4P via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > > I was able to produce this RTE, again it's N1MM but may hold clues ? > > Ron WV4P > > N1MMLogger.net - Version 1.0.9635.0 > Built: 8/24/2022 10:45:18 AM > Microsoft Windows NT 10.0.19044.0,64:1,en-US,en-US,.NET:528372 > Error occurred at: 8/24/2022 4:49:14 PM in Thread: Name: '', Id: '33', > Prio: 'Normal' > > --- > System.Net.Sockets.SocketException (0x80004005): An established connection > was aborted by the software in your host machine >at System.Net.Sockets.Socket.BeginReceive(Byte[] buffer, Int32 offset, > Int32 size, SocketFlags socketFlags, AsyncCallback callback, Object state) >at N1MMLogger.Net.AsyncTcpListener.ReceiveCallback(IAsyncResult ar) in > C:\Users\nsafr\source\Workspaces\VS2019\N1MM Logger on .NET\main\N1MM > Logger.Net\Classes\AsyncTcpListener.vb:line 142 > > --- > > > Call Stack before the runtime error: at > System.Environment.GetStackTrace(Exception e, Boolean needFileInfo) >at System.Environment.get_StackTrace() >at N1MMLibrary.SharedLib.CallStackString() in > C:\Users\nsafr\source\Workspaces\VS2019\N1MM Logger on .NET\main\N1MM > Library\Classes\SharedCode.vb:line 118 >at N1MMLogger.Net.SharedCode.HandleError(Exception e, String PortName, > String Info, String additionalInfoForLogFile) in > C:\Users\nsafr\source\Workspaces\VS2019\N1MM Logger on .NET\main\N1MM > Logger.Net\Modules\SharedCode.vb:line 223 >at N1MMLogger.Net.AsyncTcpListener.ReceiveCallback(IAsyncResult ar) in > C:\Users\nsafr\source\Workspaces\VS2019\N1MM Logger on .NET\main\N1MM > Logger.Net\Classes\AsyncTcpListener.vb:line 162 >at System.Net.LazyAsyncResult.Complete(IntPtr userToken) >at System.Net.ContextAwareResult.CompleteCallback(Object state) >at System.Threading.ExecutionContext.RunInternal(ExecutionContext > executionContext, ContextCallback callback, Object state, Boolean > preserveSyncCtx) >at System.Threading.ExecutionContext.Run(ExecutionContext > executionContext, ContextCallback callback, Object state, Boolean > preserveSyncCtx) >at System.Threading.ExecutionContext.Run(ExecutionContext > executionContext, ContextCallback callback, Object state) >at System.Net.ContextAwareResult.Complete(IntPtr userToken) >at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, > IntPtr userToken) >at > System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 > errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped) >at > System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 > errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP) > > On Wed, Aug 24, 2022 at 3:22 PM Ron WV4P wrote: > > > > [image: image.png] > This is the Error that pops up when it first crashes. I presume this is > generated by N1MM when the WSJT window disappears. > The Orphaned JT9 process always prevents restarting WSJT. Killing it in > Task Manager Sometimes allows you to reopen it, sometimes not. Sometimes > there is one JT9 process, sometimes 2. Often the Second WSJT window will > continue working, killing Both JT9 processes seems to have no effect on > it. > > I played for a couple hours trying to find a way to Make it fail, I was > unable. For a while it made me think it was not going to fail. Then it did, > and even after a reboot it failed within 10 min afterwards. > > Ron, WV4P > > Ron, WV4P > > On Tue, Aug 23, 2022 at 9:15 PM Joe Taylor via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > Hi Dennis and Ron, > > Thanks for your reports. This message is off-list, since your needs are > rather specialized -- but I have CC'd other members of our core > development group. > > On 8/23/2022 2:43 PM, Dennis W1UE via wsjt-devel wrote: > > I had high hopes for 2.6.0 rc3. I ran it for 25 hours decode time using > > an SO2R setup. It never stopped working nor crashed.2.6.0 rc1 and rc2- > > the EW just disappeared from the screen and I got an error box related > > to TCP. Since that first stoppage- or crash- I've had 4 more crashes. > > The longest I've operated since then has been about 40 minutes. > > > > So, the bug that is causing the program to suddenly close, has not been > > found. And it was looking so good! > > On 8/23/2022 2:52 PM, Ron WV4P via wsjt-devel wrote: > > Same here, running N1MM with 2 instances it keeps crashing and locking > > everything down when it does. It took a long time for the first > >
Re: [wsjt-devel] WSJT-x Stopping
See if this thread helps at all... https://groups.io/g/N1MMLoggerPlus/topic/89323949 Mike W9MDB On Wednesday, August 24, 2022 at 04:59:32 PM CDT, Ron WV4P via wsjt-devel wrote: I was able to produce this RTE, again it's N1MM but may hold clues ? Ron WV4P N1MMLogger.net - Version 1.0.9635.0 Built: 8/24/2022 10:45:18 AM Microsoft Windows NT 10.0.19044.0,64:1,en-US,en-US,.NET:528372 Error occurred at: 8/24/2022 4:49:14 PM in Thread: Name: '', Id: '33', Prio: 'Normal' --- System.Net.Sockets.SocketException (0x80004005): An established connection was aborted by the software in your host machine at System.Net.Sockets.Socket.BeginReceive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, AsyncCallback callback, Object state) at N1MMLogger.Net.AsyncTcpListener.ReceiveCallback(IAsyncResult ar) in C:\Users\nsafr\source\Workspaces\VS2019\N1MM Logger on .NET\main\N1MM Logger.Net\Classes\AsyncTcpListener.vb:line 142 --- Call Stack before the runtime error: at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo) at System.Environment.get_StackTrace() at N1MMLibrary.SharedLib.CallStackString() in C:\Users\nsafr\source\Workspaces\VS2019\N1MM Logger on .NET\main\N1MM Library\Classes\SharedCode.vb:line 118 at N1MMLogger.Net.SharedCode.HandleError(Exception e, String PortName, String Info, String additionalInfoForLogFile) in C:\Users\nsafr\source\Workspaces\VS2019\N1MM Logger on .NET\main\N1MM Logger.Net\Modules\SharedCode.vb:line 223 at N1MMLogger.Net.AsyncTcpListener.ReceiveCallback(IAsyncResult ar) in C:\Users\nsafr\source\Workspaces\VS2019\N1MM Logger on .NET\main\N1MM Logger.Net\Classes\AsyncTcpListener.vb:line 162 at System.Net.LazyAsyncResult.Complete(IntPtr userToken) at System.Net.ContextAwareResult.CompleteCallback(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Net.ContextAwareResult.Complete(IntPtr userToken) at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken) at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped) at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP) On Wed, Aug 24, 2022 at 3:22 PM Ron WV4P wrote: This is the Error that pops up when it first crashes. I presume this is generated by N1MM when the WSJT window disappears.The Orphaned JT9 process always prevents restarting WSJT. Killing it in Task Manager Sometimes allows you to reopen it, sometimes not. Sometimes there is one JT9 process, sometimes 2. Often the Second WSJT window will continue working, killing Both JT9 processes seems to have no effect on it. I played for a couple hours trying to find a way to Make it fail, I was unable. For a while it made me think it was not going to fail. Then it did, and even after a reboot it failed within 10 min afterwards. Ron, WV4P Ron, WV4P On Tue, Aug 23, 2022 at 9:15 PM Joe Taylor via wsjt-devel wrote: Hi Dennis and Ron, Thanks for your reports. This message is off-list, since your needs are rather specialized -- but I have CC'd other members of our core development group. On 8/23/2022 2:43 PM, Dennis W1UE via wsjt-devel wrote: > I had high hopes for 2.6.0 rc3. I ran it for 25 hours decode time using > an SO2R setup. It never stopped working nor crashed.2.6.0 rc1 and rc2- > the EW just disappeared from the screen and I got an error box related > to TCP. Since that first stoppage- or crash- I've had 4 more crashes. > The longest I've operated since then has been about 40 minutes. > > So, the bug that is causing the program to suddenly close, has not been > found. And it was looking so good! On 8/23/2022 2:52 PM, Ron WV4P via wsjt-devel wrote: > Same here, running N1MM with 2 instances it keeps crashing and locking > everything down when it does. It took a long time for the first > occurrence but now its lucky to stay up 30 min. ... > I'll be single op. > If anyone makes it work with the Max Distance feature they will have a > distinct advantage. Sadly it's back to 2.54 for me, I could not make it work > reliably. I'll run it again this evening to try and get some screen shots and > data that might help the Smart people, before I swap back to the stable > version. > Good luck, Dennis ! You rocked the
Re: [wsjt-devel] WSJT-x Stopping
I was able to produce this RTE, again it's N1MM but may hold clues ? Ron WV4P N1MMLogger.net - Version 1.0.9635.0 Built: 8/24/2022 10:45:18 AM Microsoft Windows NT 10.0.19044.0,64:1,en-US,en-US,.NET:528372 Error occurred at: 8/24/2022 4:49:14 PM in Thread: Name: '', Id: '33', Prio: 'Normal' --- System.Net.Sockets.SocketException (0x80004005): An established connection was aborted by the software in your host machine at System.Net.Sockets.Socket.BeginReceive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, AsyncCallback callback, Object state) at N1MMLogger.Net.AsyncTcpListener.ReceiveCallback(IAsyncResult ar) in C:\Users\nsafr\source\Workspaces\VS2019\N1MM Logger on .NET\main\N1MM Logger.Net\Classes\AsyncTcpListener.vb:line 142 --- Call Stack before the runtime error: at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo) at System.Environment.get_StackTrace() at N1MMLibrary.SharedLib.CallStackString() in C:\Users\nsafr\source\Workspaces\VS2019\N1MM Logger on .NET\main\N1MM Library\Classes\SharedCode.vb:line 118 at N1MMLogger.Net.SharedCode.HandleError(Exception e, String PortName, String Info, String additionalInfoForLogFile) in C:\Users\nsafr\source\Workspaces\VS2019\N1MM Logger on .NET\main\N1MM Logger.Net\Modules\SharedCode.vb:line 223 at N1MMLogger.Net.AsyncTcpListener.ReceiveCallback(IAsyncResult ar) in C:\Users\nsafr\source\Workspaces\VS2019\N1MM Logger on .NET\main\N1MM Logger.Net\Classes\AsyncTcpListener.vb:line 162 at System.Net.LazyAsyncResult.Complete(IntPtr userToken) at System.Net.ContextAwareResult.CompleteCallback(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Net.ContextAwareResult.Complete(IntPtr userToken) at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken) at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped) at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP) On Wed, Aug 24, 2022 at 3:22 PM Ron WV4P wrote: > > > [image: image.png] > This is the Error that pops up when it first crashes. I presume this is > generated by N1MM when the WSJT window disappears. > The Orphaned JT9 process always prevents restarting WSJT. Killing it in > Task Manager Sometimes allows you to reopen it, sometimes not. Sometimes > there is one JT9 process, sometimes 2. Often the Second WSJT window will > continue working, killing Both JT9 processes seems to have no effect on > it. > > I played for a couple hours trying to find a way to Make it fail, I was > unable. For a while it made me think it was not going to fail. Then it did, > and even after a reboot it failed within 10 min afterwards. > > Ron, WV4P > > Ron, WV4P > > On Tue, Aug 23, 2022 at 9:15 PM Joe Taylor via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > >> Hi Dennis and Ron, >> >> Thanks for your reports. This message is off-list, since your needs are >> rather specialized -- but I have CC'd other members of our core >> development group. >> >> On 8/23/2022 2:43 PM, Dennis W1UE via wsjt-devel wrote: >> > I had high hopes for 2.6.0 rc3. I ran it for 25 hours decode time >> using >> > an SO2R setup. It never stopped working nor crashed.2.6.0 rc1 and rc2- >> > the EW just disappeared from the screen and I got an error box related >> > to TCP. Since that first stoppage- or crash- I've had 4 more crashes. >> > The longest I've operated since then has been about 40 minutes. >> > >> > So, the bug that is causing the program to suddenly close, has not been >> > found. And it was looking so good! >> >> On 8/23/2022 2:52 PM, Ron WV4P via wsjt-devel wrote: >> > Same here, running N1MM with 2 instances it keeps crashing and locking >> > everything down when it does. It took a long time for the first >> > occurrence but now its lucky to stay up 30 min. >> >> ... >> >> > I'll be single op. >> > If anyone makes it work with the Max Distance feature they will have a >> distinct advantage. Sadly it's back to 2.54 for me, I could not make it >> work reliably. I'll run it again this evening to try and get some screen >> shots and data that might help the Smart people, before I swap back to the >> stable version. >> > Good luck, Dennis ! You rocked the last one. >> >> We'll be happy to help you guys to isolate the problem
Re: [wsjt-devel] WSJT-x Stopping
[image: image.png] This is the Error that pops up when it first crashes. I presume this is generated by N1MM when the WSJT window disappears. The Orphaned JT9 process always prevents restarting WSJT. Killing it in Task Manager Sometimes allows you to reopen it, sometimes not. Sometimes there is one JT9 process, sometimes 2. Often the Second WSJT window will continue working, killing Both JT9 processes seems to have no effect on it. I played for a couple hours trying to find a way to Make it fail, I was unable. For a while it made me think it was not going to fail. Then it did, and even after a reboot it failed within 10 min afterwards. Ron, WV4P Ron, WV4P On Tue, Aug 23, 2022 at 9:15 PM Joe Taylor via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hi Dennis and Ron, > > Thanks for your reports. This message is off-list, since your needs are > rather specialized -- but I have CC'd other members of our core > development group. > > On 8/23/2022 2:43 PM, Dennis W1UE via wsjt-devel wrote: > > I had high hopes for 2.6.0 rc3. I ran it for 25 hours decode time using > > an SO2R setup. It never stopped working nor crashed.2.6.0 rc1 and rc2- > > the EW just disappeared from the screen and I got an error box related > > to TCP. Since that first stoppage- or crash- I've had 4 more crashes. > > The longest I've operated since then has been about 40 minutes. > > > > So, the bug that is causing the program to suddenly close, has not been > > found. And it was looking so good! > > On 8/23/2022 2:52 PM, Ron WV4P via wsjt-devel wrote: > > Same here, running N1MM with 2 instances it keeps crashing and locking > > everything down when it does. It took a long time for the first > > occurrence but now its lucky to stay up 30 min. > > ... > > > I'll be single op. > > If anyone makes it work with the Max Distance feature they will have a > distinct advantage. Sadly it's back to 2.54 for me, I could not make it > work reliably. I'll run it again this evening to try and get some screen > shots and data that might help the Smart people, before I swap back to the > stable version. > > Good luck, Dennis ! You rocked the last one. > > We'll be happy to help you guys to isolate the problem you're having, > apparently with communication between WSJT-X and N1MM+, but I must > caution you that it may take some time. Moreover, in the immediate > future my time is largely committed to a paper on the EME Echo mode > features in WSJT-X 2.6.0. > > None of our program versions 2.6.0-rc1, -rc2, or -rc3 have intentional > changes to the way communications take place with an external program > such as N1MM+. At present I don't know the details of what happens when > you say it (I suppose you mean WSJT-X) crashes. Any error message? > What was happening just before the failure? Is WSJT-X doing any rig > control? Can you stress-test the situation in a way that reliably > forces a failure? > > These release-candidate versions of WSJT-X 2.6.0 have been bullet-proof > in my own usage patterns, including in the ARRL-DIGI contest back in > June at W2ZQ. But we were using it alone, not with N1MM. Of course, > WSJT-X does not have built-in SO2R features. Are there other reasons > that you want N1MM in addition to WSJT-X for, say, the WW-DIGI contest? > > None of us is a regular user of the N1MM + WSJT-X combination, so we > really need your help -- and possibly that of the N1MM development > group, to track down what's flaky about this two-program kludge. > > -- 73, Joe, K1JT > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-x Stopping
Hi Dennis and Ron, Thanks for your reports. This message is off-list, since your needs are rather specialized -- but I have CC'd other members of our core development group. On 8/23/2022 2:43 PM, Dennis W1UE via wsjt-devel wrote: I had high hopes for 2.6.0 rc3. I ran it for 25 hours decode time using an SO2R setup. It never stopped working nor crashed.2.6.0 rc1 and rc2- the EW just disappeared from the screen and I got an error box related to TCP. Since that first stoppage- or crash- I've had 4 more crashes. The longest I've operated since then has been about 40 minutes. So, the bug that is causing the program to suddenly close, has not been found. And it was looking so good! On 8/23/2022 2:52 PM, Ron WV4P via wsjt-devel wrote: Same here, running N1MM with 2 instances it keeps crashing and locking everything down when it does. It took a long time for the first occurrence but now its lucky to stay up 30 min. ... I'll be single op. If anyone makes it work with the Max Distance feature they will have a distinct advantage. Sadly it's back to 2.54 for me, I could not make it work reliably. I'll run it again this evening to try and get some screen shots and data that might help the Smart people, before I swap back to the stable version. Good luck, Dennis ! You rocked the last one. We'll be happy to help you guys to isolate the problem you're having, apparently with communication between WSJT-X and N1MM+, but I must caution you that it may take some time. Moreover, in the immediate future my time is largely committed to a paper on the EME Echo mode features in WSJT-X 2.6.0. None of our program versions 2.6.0-rc1, -rc2, or -rc3 have intentional changes to the way communications take place with an external program such as N1MM+. At present I don't know the details of what happens when you say it (I suppose you mean WSJT-X) crashes. Any error message? What was happening just before the failure? Is WSJT-X doing any rig control? Can you stress-test the situation in a way that reliably forces a failure? These release-candidate versions of WSJT-X 2.6.0 have been bullet-proof in my own usage patterns, including in the ARRL-DIGI contest back in June at W2ZQ. But we were using it alone, not with N1MM. Of course, WSJT-X does not have built-in SO2R features. Are there other reasons that you want N1MM in addition to WSJT-X for, say, the WW-DIGI contest? None of us is a regular user of the N1MM + WSJT-X combination, so we really need your help -- and possibly that of the N1MM development group, to track down what's flaky about this two-program kludge. -- 73, Joe, K1JT ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-x Stopping
Joe, Dennis and company, All of the errors I got were generic in nature, no RTE's with a script or anything. Most of the time it happens when idle, even for only a short time. In addition to what Dennis said about N1MM it also posts to the online scoreboards and such. The combo of your software and theirs is really incredible for these tests. I believe Rick N2AMG would be the one on the N1MM team to help sort it out but he's currently Trout Fishing... And I'm jealous ! If there is anything I can do to help before I swap back to 2.54 just let me know. All of my experiences to date mirror what Dennis has seen to a tee. I also have Anydesk and can let you monitor / operate if wanted. I will reinstall RC3 after the contest. Joe, Thanks again for supporting WWDigi not only with your Software but sponsoring the Plaque Dennis thinks he will take from me this year :o) We may both be left in the dust if someone gets RC3 working though... CQ Max Dist is an incredible feature. Ron, WV4P On Tue, Aug 23, 2022 at 5:39 PM Dennis W1UE via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > GA Joe, and thanks to you and the development team for their efforts. > I hope I included all the info that you wanted. > > WSJT-x doesn't really "crash"- one of the WSJT Entry Windows simply > "disappears". > No BSOD, No RTE. There is an error message in a little box: "Something > unexpected > caused WSJT to close the Radio TCP port unexpectedly. Please try > restarting WSJT again. > If that does not work restart N1MM." I can't tell what was happening > just > before the failure, as there is no warning there is going to be a failure. > WSJT is controllilng two radios through N1MM using > the DX Lab Commander process, as detailed in the N1MM setup instructions. > I > have not found a way to force a failure. I will note, that version 2.5.4 > did not have this problem. The EW that closes may be either EW1 or EW2; > there > is no way of guessing which is going to crash, and no indication that I've > noticed to indicate which window is about to crash. > > If you then restart WSJT, you will get another error box: "Sub-process > error. > Failed to close orphaned jt9 process." Going into Task Manager and > closing > that JT9 function does not restore functionality. If I close all the WSJT > windows and all the N1MM+ windows, and try to restart N1MM, I get another > error message about a port 13064 not being closed. The quickest and most > reliable > way to get back to making contacts is to restart the computer, restart > N1MM, > and restart each WSJT window. > > Yes, there are other reasons for wanting N1MM. I use it to keep track of > multipliers- what do I need, and where what I need is operating. I also > tie in Telnet with N1MM to keep me up on multipliers and what bands are > open > and to where. Rate info, transferring score to one of the Online > Scoreboards. > Since I don't have a big big display for all this, I also network N1MM to > display > info that won't fit on my regular display. > > One other thing I noticed after the last crash- I went in to delete the > orphaned JT9 process, and found that there were two JT9 processes, one > about > 20Mb and one about 180Mb. After I restarted the N1MM and the 2 WSJT EWs, I > went into the same process and found only 1 JT9 process, about 18-22Mb. I > just restarted the computer and reentered everything again, and now I have > 2 jT9 processes, one about 20Mb and one about 194Mb. Took another look- > now they are both 14.5Mb. Now both are at 180Mb. Don't know if this is > apropos > at all, just seems odd. > > Right now, I'm planning to use 2.5.4 for the WWDigi Test. I hate to give > away the > advantages of using 2.6.0rc3, but I can't handle the interruptions and > lost QSOs. > > Dennis W1UE > > On Tue, Aug 23, 2022 at 4:35 PM Joe Taylor wrote: > >> Hi Dennis and Ron, >> >> Thanks for your reports. This message is off-list, since your needs are >> rather specialized -- but I have CC'd other members of our core >> development group. >> >> On 8/23/2022 2:43 PM, Dennis W1UE via wsjt-devel wrote: >> > I had high hopes for 2.6.0 rc3. I ran it for 25 hours decode time >> using >> > an SO2R setup. It never stopped working nor crashed.2.6.0 rc1 and rc2- >> > the EW just disappeared from the screen and I got an error box related >> > to TCP. Since that first stoppage- or crash- I've had 4 more crashes. >> > The longest I've operated since then has been about 40 minutes. >> > >> > So, the bug that is causing the program to suddenly close, has not been >> > found. And it was looking so good! >> >> On 8/23/2022 2:52 PM, Ron WV4P via wsjt-devel wrote: >> > Same here, running N1MM with 2 instances it keeps crashing and locking >> > everything down when it does. It took a long time for the first >> > occurrence but now its lucky to stay up 30 min. >> >> ... >> >> > I'll be single op. >> > If anyone makes it work with the Max Distance feature they will have a >> distinct
Re: [wsjt-devel] WSJT-x Stopping
GA Joe, and thanks to you and the development team for their efforts. I hope I included all the info that you wanted. WSJT-x doesn't really "crash"- one of the WSJT Entry Windows simply "disappears". No BSOD, No RTE. There is an error message in a little box: "Something unexpected caused WSJT to close the Radio TCP port unexpectedly. Please try restarting WSJT again. If that does not work restart N1MM." I can't tell what was happening just before the failure, as there is no warning there is going to be a failure. WSJT is controllilng two radios through N1MM using the DX Lab Commander process, as detailed in the N1MM setup instructions. I have not found a way to force a failure. I will note, that version 2.5.4 did not have this problem. The EW that closes may be either EW1 or EW2; there is no way of guessing which is going to crash, and no indication that I've noticed to indicate which window is about to crash. If you then restart WSJT, you will get another error box: "Sub-process error. Failed to close orphaned jt9 process." Going into Task Manager and closing that JT9 function does not restore functionality. If I close all the WSJT windows and all the N1MM+ windows, and try to restart N1MM, I get another error message about a port 13064 not being closed. The quickest and most reliable way to get back to making contacts is to restart the computer, restart N1MM, and restart each WSJT window. Yes, there are other reasons for wanting N1MM. I use it to keep track of multipliers- what do I need, and where what I need is operating. I also tie in Telnet with N1MM to keep me up on multipliers and what bands are open and to where. Rate info, transferring score to one of the Online Scoreboards. Since I don't have a big big display for all this, I also network N1MM to display info that won't fit on my regular display. One other thing I noticed after the last crash- I went in to delete the orphaned JT9 process, and found that there were two JT9 processes, one about 20Mb and one about 180Mb. After I restarted the N1MM and the 2 WSJT EWs, I went into the same process and found only 1 JT9 process, about 18-22Mb. I just restarted the computer and reentered everything again, and now I have 2 jT9 processes, one about 20Mb and one about 194Mb. Took another look- now they are both 14.5Mb. Now both are at 180Mb. Don't know if this is apropos at all, just seems odd. Right now, I'm planning to use 2.5.4 for the WWDigi Test. I hate to give away the advantages of using 2.6.0rc3, but I can't handle the interruptions and lost QSOs. Dennis W1UE On Tue, Aug 23, 2022 at 4:35 PM Joe Taylor wrote: > Hi Dennis and Ron, > > Thanks for your reports. This message is off-list, since your needs are > rather specialized -- but I have CC'd other members of our core > development group. > > On 8/23/2022 2:43 PM, Dennis W1UE via wsjt-devel wrote: > > I had high hopes for 2.6.0 rc3. I ran it for 25 hours decode time using > > an SO2R setup. It never stopped working nor crashed.2.6.0 rc1 and rc2- > > the EW just disappeared from the screen and I got an error box related > > to TCP. Since that first stoppage- or crash- I've had 4 more crashes. > > The longest I've operated since then has been about 40 minutes. > > > > So, the bug that is causing the program to suddenly close, has not been > > found. And it was looking so good! > > On 8/23/2022 2:52 PM, Ron WV4P via wsjt-devel wrote: > > Same here, running N1MM with 2 instances it keeps crashing and locking > > everything down when it does. It took a long time for the first > > occurrence but now its lucky to stay up 30 min. > > ... > > > I'll be single op. > > If anyone makes it work with the Max Distance feature they will have a > distinct advantage. Sadly it's back to 2.54 for me, I could not make it > work reliably. I'll run it again this evening to try and get some screen > shots and data that might help the Smart people, before I swap back to the > stable version. > > Good luck, Dennis ! You rocked the last one. > > We'll be happy to help you guys to isolate the problem you're having, > apparently with communication between WSJT-X and N1MM+, but I must > caution you that it may take some time. Moreover, in the immediate > future my time is largely committed to a paper on the EME Echo mode > features in WSJT-X 2.6.0. > > None of our program versions 2.6.0-rc1, -rc2, or -rc3 have intentional > changes to the way communications take place with an external program > such as N1MM+. At present I don't know the details of what happens when > you say it (I suppose you mean WSJT-X) crashes. Any error message? > What was happening just before the failure? Is WSJT-X doing any rig > control? Can you stress-test the situation in a way that reliably > forces a failure? > > These release-candidate versions of WSJT-X 2.6.0 have been bullet-proof > in my own usage patterns, including in the ARRL-DIGI contest back in > June at W2ZQ. But we were using it alone, not with N1MM.
Re: [wsjt-devel] WSJT-x Stopping
Dennis, I'll be single op. If anyone makes it work with the Max Distance feature they will have a distinct advantage. Sadly it's back to 2.54 for me, I could not make it work reliably. I'll run it again this evening to try and get some screen shots and data that might help the Smart people, before I swap back to the stable version. Good luck, Dennis ! You rocked the last one. Ron, WV4P On Tue, Aug 23, 2022 at 2:22 PM Dennis W1UE via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Ron > > I thought I was the only one crazy enough to do this! I also ran 2 > instances with N1MM+. I had high hopes of using > it in WWDigi, but I don't think its ready yet. > > You doing a Multi-op or SO2R? I'm SO2R LP. > > Dennis W1UE > > > On Tue, Aug 23, 2022 at 2:58 PM Ron WV4P via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > >> Same here, running N1MM with 2 instances it keeps crashing and locking >> everything down when it does. It took a long time for the first occurrence >> but now its lucky to stay up 30 min. >> >> Ron, WV4P >> >> On Tue, Aug 23, 2022, 1:48 PM Dennis W1UE via wsjt-devel < >> wsjt-devel@lists.sourceforge.net> wrote: >> >>> I had high hopes for 2.6.0 rc3. I ran it for 25 hours decode time using >>> an SO2R setup. It never stopped working nor crashed.2.6.0 rc1 and rc2- the >>> EW just disappeared from the screen and I got an error box related to TCP. >>> Since that first stoppage- or crash- I've had 4 more crashes. The longest >>> I've operated since then has been about 40 minutes. >>> >>> So, the bug that is causing the program to suddenly close, has not been >>> found. And it was looking so good! >>> >>> Dennis W1UE >>> >>> ___ >>> wsjt-devel mailing list >>> wsjt-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>> >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-x Stopping
Ron I thought I was the only one crazy enough to do this! I also ran 2 instances with N1MM+. I had high hopes of using it in WWDigi, but I don't think its ready yet. You doing a Multi-op or SO2R? I'm SO2R LP. Dennis W1UE On Tue, Aug 23, 2022 at 2:58 PM Ron WV4P via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Same here, running N1MM with 2 instances it keeps crashing and locking > everything down when it does. It took a long time for the first occurrence > but now its lucky to stay up 30 min. > > Ron, WV4P > > On Tue, Aug 23, 2022, 1:48 PM Dennis W1UE via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > >> I had high hopes for 2.6.0 rc3. I ran it for 25 hours decode time using >> an SO2R setup. It never stopped working nor crashed.2.6.0 rc1 and rc2- the >> EW just disappeared from the screen and I got an error box related to TCP. >> Since that first stoppage- or crash- I've had 4 more crashes. The longest >> I've operated since then has been about 40 minutes. >> >> So, the bug that is causing the program to suddenly close, has not been >> found. And it was looking so good! >> >> Dennis W1UE >> >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-x Stopping
Same here, running N1MM with 2 instances it keeps crashing and locking everything down when it does. It took a long time for the first occurrence but now its lucky to stay up 30 min. Ron, WV4P On Tue, Aug 23, 2022, 1:48 PM Dennis W1UE via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > I had high hopes for 2.6.0 rc3. I ran it for 25 hours decode time using > an SO2R setup. It never stopped working nor crashed.2.6.0 rc1 and rc2- the > EW just disappeared from the screen and I got an error box related to TCP. > Since that first stoppage- or crash- I've had 4 more crashes. The longest > I've operated since then has been about 40 minutes. > > So, the bug that is causing the program to suddenly close, has not been > found. And it was looking so good! > > Dennis W1UE > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] WSJT-x Stopping
I had high hopes for 2.6.0 rc3. I ran it for 25 hours decode time using an SO2R setup. It never stopped working nor crashed.2.6.0 rc1 and rc2- the EW just disappeared from the screen and I got an error box related to TCP. Since that first stoppage- or crash- I've had 4 more crashes. The longest I've operated since then has been about 40 minutes. So, the bug that is causing the program to suddenly close, has not been found. And it was looking so good! Dennis W1UE ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
