I really appreciate the hours and effort that have gone into the creation of WSJT. The enhancements in 2.6 are all great, except for the one that seems to have created a problem for me. I'll describe my setup and then the problem.
Computer #1- I7 11th gen, 16Gb RAM, Win 11 Pro Computer #2- I5 4th gen, 8Gb RAM, Win10 Pro- new (to me) computer, very little on it WSJT 2.5.4 works flawlessly in my setup. Setup: WSJT configured to work with N1MM+ Logger thru DX Lab Commander. Local rigs are K3 radios, connected to Remote Rig (RR) boxes that stream the audio to a radio site 70 miles away. The computer and K3s talk at 38400. My normal operation is So2R, although at times I may operate with only one For EW. I use separate sound cards to decode each radio, and a third soundcard that generates the transmit tones. All the signal processing (WSJT, N1MM+, sound cards) is done at the Control site. Problem: With no warning and no provocation, one of the WSJT-X-FOR EW will suddenly close and I'll ge this error message: "Something caused WSJT to close the Radio TCP Port unexpectedly. Please try starting WSJT again. If that doesn't restore operation, restart N1MM+." Restarting WSJT doesn't work, and restarting N1MM+ doesn't work. The only way to restore operation at this point is to restart the computer. 1. The time between crashes is 15 min to 3 hrs. 2. Either WSJT-X ForEW1 or EW2 can crash. 3. THe problem occurs on both of the above computers. 4. The problem occurs when local communications are at 38400 or 9600. 5. I have not found a way to generate the problem, it just happens. 6. The crash can occur when I'm not touching the keyboard or mouse. 7. The crash occurs when using either the 32 or 64 bit program 8. On Mike W9MDB's suggestion, I reconfigured WSJT and N1MM so that WSJT controlled the radios directly; the crash still occurs. Since I haven't heard many complaining about this, I'm thinking there aren't many ops trying to operate SO2R through a remote station, and the remote station has something to do with it (something timing out, momentary interruption of data or audio streams) I"ve also considered that maybe that error message is something of a catchall, and the problem doesn't have a specific error message. Since this problem didn't occur with 2.5.4, and does with 2.6.0, something changed between the two to create this problem. In any case, thanks for anything that can be done to correct this. If I can assist with any fixes on this or other items please feel free to call on me. Dennis W1UE
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
