Date
1 - 9 of 9
Locked WSJT Stops Working #stopped_working #windows11 #logging
|
Dennis W1UE
I've posted on this before- kind of- but I thought I'd make it a little
more formal. Set up here is Windows 11, I7=11th gen chip, 16Gb ram. Remote station using Remote Rig units. I've seen mention from one other poster of the same problem. I'm having a problem with WSJT-x when using it in SO2R Mode with N1MM+. The problem is that, without any warning, one of the two EWs will disappear from the screen, and will produce this error message: "Something unexpected caused WSJT to close the Radio TCP port unexpectedly. Please try restarting WSJT again. If that does not work restart N1MM." Closing and restarting WSJT did not restore the functionality. Closing WSJT, closing N1MM, restarting N1MM, then restarting WSJT did not restore the functionality. Using Task Manager to shut down the orphan JT9 process did not restore the functionality. The only way I found to get both EWs up and running again was to restart the computer and restore the programs. Then they would work for a while, then one of the EWs would crash again. Either of the EWs could crash. When the setup is working, it works FB. Once an EW crashes, the only way to restore functionality is to restart the computer and reload everything. I have RigCtl and SYs error files available, and can produce another one within an hour if needed. I did rollback to 2.5.4, and after 16 hours of operation did not have a crash. Dennis W1UE |
|
|
|
Mike Black
Please place this file as described belowhttps://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0
toggle quoted message
Show quoted text
C:\Users\[username]\AppData\Local\WSJT-X The WSJT-X_Rigcontrol.log file will be in the same location For Linux put it in ~/.config The WSJT-X_Rigcontrol.log file will be here: ~/.local/share/WSJT-X Restart WSJT-X and duplicate the problem.Shut down WSJT-X Then send me the WSJT-X_RigControl.log fileMike W9MDB On Monday, July 11, 2022 at 10:05:13 AM CDT, Dennis W1UE <egan.dennis88@...> wrote:
I've posted on this before- kind of- but I thought I'd make it a little more formal. Set up here is Windows 11, I7=11th gen chip, 16Gb ram. Remote station using Remote Rig units. I've seen mention from one other poster of the same problem. I'm having a problem with WSJT-x when using it in SO2R Mode with N1MM+. The problem is that, without any warning, one of the two EWs will disappear from the screen, and will produce this error message: "Something unexpected caused WSJT to close the Radio TCP port unexpectedly. Please try restarting WSJT again. If that does not work restart N1MM." Closing and restarting WSJT did not restore the functionality. Closing WSJT, closing N1MM, restarting N1MM, then restarting WSJT did not restore the functionality. Using Task Manager to shut down the orphan JT9 process did not restore the functionality. The only way I found to get both EWs up and running again was to restart the computer and restore the programs. Then they would work for a while, then one of the EWs would crash again. Either of the EWs could crash. When the setup is working, it works FB. Once an EW crashes, the only way to restore functionality is to restart the computer and reload everything. I have RigCtl and SYs error files available, and can produce another one within an hour if needed. I did rollback to 2.5.4, and after 16 hours of operation did not have a crash. Dennis W1UE |
|
|
|
Chet, N8RA
FWIW I get that same error with this sequence of events:
toggle quoted message
Show quoted text
Win 10 pro, and latest RC1 of WSJT-x Start N1MM+ -OK Start WSJT-X -it displays all 0's for the freq. X off WSJT-X Go to task manager and end a WSJT-X process I see there Start WSJT-X -freq from radio is OK now Erase ADI file -OK Reset Cabrillo log- WSJT-X does a long hourglass and then shuts down leaving that error box. Restart WSJT-X -seems OK. Do a reset Cabrillo again, get the hourglass, shutdown and error box again. Chet, N8RA -----Original Message-----
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Dennis W1UE Sent: Monday, July 11, 2022 7:15 AM To: wsjtx@groups.io Subject: [WSJTX] WSJT Stops Working #Logging #Stopped_working #windows11 I've posted on this before- kind of- but I thought I'd make it a little more formal. Set up here is Windows 11, I7=11th gen chip, 16Gb ram. Remote station using Remote Rig units. I've seen mention from one other poster of the same problem. I'm having a problem with WSJT-x when using it in SO2R Mode with N1MM+. The problem is that, without any warning, one of the two EWs will disappear from the screen, and will produce this error message: "Something unexpected caused WSJT to close the Radio TCP port unexpectedly. Please try restarting WSJT again. If that does not work restart N1MM." Closing and restarting WSJT did not restore the functionality. Closing WSJT, closing N1MM, restarting N1MM, then restarting WSJT did not restore the functionality. Using Task Manager to shut down the orphan JT9 process did not restore the functionality. The only way I found to get both EWs up and running again was to restart the computer and restore the programs. Then they would work for a while, then one of the EWs would crash again. Either of the EWs could crash. When the setup is working, it works FB. Once an EW crashes, the only way to restore functionality is to restart the computer and reload everything. I have RigCtl and SYs error files available, and can produce another one within an hour if needed. I did rollback to 2.5.4, and after 16 hours of operation did not have a crash. Dennis W1UE |
|
|
|
Rick Ellison
Chet..
toggle quoted message
Show quoted text
When you start WSJTX from within N1MM is your radio already reading correctly in N1MM. I have yet to have someone tell me they have needed to restart WSJTX because the frequency was wrong. If you would send me a couple of screenshots. ( N1MM main Config WSJT tab,N1MM Main config Hardware tab, WSJTX radio tab, WSJTX Reporting tab.) send them direct to rellison@..... 73 Rick N2AMG -----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Chet, N8RA Sent: Monday, July 11, 2022 12:56 PM To: main@WSJTX.groups.io; wsjtx@groups.io Subject: Re: [WSJTX] WSJT Stops Working #Logging #Stopped_working #windows11 FWIW I get that same error with this sequence of events: Win 10 pro, and latest RC1 of WSJT-x Start N1MM+ -OK Start WSJT-X -it displays all 0's for the freq. X off WSJT-X Go to task manager and end a WSJT-X process I see there Start WSJT-X -freq from radio is OK now Erase ADI file -OK Reset Cabrillo log- WSJT-X does a long hourglass and then shuts down leaving that error box. Restart WSJT-X -seems OK. Do a reset Cabrillo again, get the hourglass, shutdown and error box again. Chet, N8RA -----Original Message----- From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Dennis W1UE Sent: Monday, July 11, 2022 7:15 AM To: wsjtx@groups.io Subject: [WSJTX] WSJT Stops Working #Logging #Stopped_working #windows11 I've posted on this before- kind of- but I thought I'd make it a little more formal. Set up here is Windows 11, I7=11th gen chip, 16Gb ram. Remote station using Remote Rig units. I've seen mention from one other poster of the same problem. I'm having a problem with WSJT-x when using it in SO2R Mode with N1MM+. The problem is that, without any warning, one of the two EWs will disappear from the screen, and will produce this error message: "Something unexpected caused WSJT to close the Radio TCP port unexpectedly. Please try restarting WSJT again. If that does not work restart N1MM." Closing and restarting WSJT did not restore the functionality. Closing WSJT, closing N1MM, restarting N1MM, then restarting WSJT did not restore the functionality. Using Task Manager to shut down the orphan JT9 process did not restore the functionality. The only way I found to get both EWs up and running again was to restart the computer and restore the programs. Then they would work for a while, then one of the EWs would crash again. Either of the EWs could crash. When the setup is working, it works FB. Once an EW crashes, the only way to restore functionality is to restart the computer and reload everything. I have RigCtl and SYs error files available, and can produce another one within an hour if needed. I did rollback to 2.5.4, and after 16 hours of operation did not have a crash. Dennis W1UE -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus |
|
|
|
Dennis W1UE
Michael W9MDB
On Mon, Jul 11, 2022 at 3:28 PM Michael Black via groups.io <mdblack98= yahoo.com@groups.io> wrote: Please place this file as described belowhttps:// |
|
|
|
I use MicroHam Router 9.3.5 with a microKeyer 2R+ to interact between my 2 K3s and the 2 instances of N1MM+ to run in a SO2R configuration. Recently after an update for the MicroHam Router, the router stopped showing the frequencies that the two radios were on. After changing the baud rate for each FOREW1 and FORew2 by pressing on the set button on the MicroHam router page and then changing back to the real baud rate, then the router would now show the correct frequencies. If I didn't ensure that the frequencies were showing, then usually the FORew2 would disappear with the error saying Radio TCP error and everything would lock up until I re-booted. Once the router shows both frequencies then everything seems to work as normal when doing everyday, non-contesting FT8.
This is a different problem than getting the same error message whenever I try to use the program in contest mode, where when it comes time to send the 73 and log the contact, FORew2 disappears and everything locks up again. I've downloaded the bug file and will place it in the FORew1 and FORew2 folders and go to contest mode and crash the system as described and see what the bug file finds out. My only question is who should I send the bug file to since I don't understand the subtleties of these files and crashes and computers in general. The bug file may contain the answer but I'm not sophisticated enough to understand what I'm seeing there, most likely. Thanks, 73 and I remain, Lew w7ew |
|
|
|
Rick Ellison
Lew you can send it to me to look at.. This isn't the same problem that Dennis is having where WSJTX just closes.
toggle quoted message
Show quoted text
Send them to rellison@... 73 Rick N2AMG -----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Lew Sayre Sent: Monday, July 11, 2022 7:30 PM To: main@WSJTX.groups.io Subject: Re: [WSJTX] WSJT Stops Working #stopped_working #windows11 #logging I use MicroHam Router 9.3.5 with a microKeyer 2R+ to interact between my 2 K3s and the 2 instances of N1MM+ to run in a SO2R configuration. Recently after an update for the MicroHam Router, the router stopped showing the frequencies that the two radios were on. After changing the baud rate for each FOREW1 and FORew2 by pressing on the set button on the MicroHam router page and then changing back to the real baud rate, then the router would now show the correct frequencies. If I didn't ensure that the frequencies were showing, then usually the FORew2 would disappear with the error saying Radio TCP error and everything would lock up until I re-booted. Once the router shows both frequencies then everything seems to work as normal when doing everyday, non-contesting FT8. This is a different problem than getting the same error message whenever I try to use the program in contest mode, where when it comes time to send the 73 and log the contact, FORew2 disappears and everything locks up again. I've downloaded the bug file and will place it in the FORew1 and FORew2 folders and go to contest mode and crash the system as described and see what the bug file finds out. My only question is who should I send the bug file to since I don't understand the subtleties of these files and crashes and computers in general. The bug file may contain the answer but I'm not sophisticated enough to understand what I'm seeing there, most likely. Thanks, 73 and I remain, Lew w7ew -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus |
|
|
|
joe gay
For those who have strange issues - I had WSJT-X connection issues that started immediately after the Win10 x64 pro update in June (KB5014699 June 15) - I reverted the update & issues ceased - MS has confirmed issues with that update. The update also greatly slowed & caused disfunctional connections with IE browsers. MS link to that buggy update -
https://www.windowslatest.com/2022/06/19/microsoft-confirms-new-issues-in-windows-10-june-2022-updates/ Not sure if this affects Win11 73 Joe W4RYW |
|
|
|
Mike Black
There was a recent Windows 10 update that is causing problems.
toggle quoted message
Show quoted text
There are some potential fixes in here https://www.windowslatest.com/2022/06/19/microsoft-confirms-new-issues-in-windows-10-june-2022-updates/ Mike W9MDB On Tuesday, July 12, 2022 at 02:41:49 PM CDT, joe gay via groups.io <hamop@...> wrote:
For those who have strange issues - I had WSJT-X connection issues that started immediately after the Win10 x64 pro update in June (KB5014699 June 15) - I reverted the update & issues ceased - MS has confirmed issues with that update. The update also greatly slowed & caused disfunctional connections with IE browsers. MS link to that buggy update - https://www.windowslatest.com/2022/06/19/microsoft-confirms-new-issues-in-windows-10-june-2022-updates/ Not sure if this affects Win11 73 Joe W4RYW |
|
|