Date   

locked Re: Portable calls crashing WSJT-X Version 2.5.3 #Windows10 #windows11 #decode

Bryan Lynch - NM7C
 

I posted this to the wrong thread before.

Here is a video of the app crashing with a portable call: https://youtu.be/HM9N_RLJb14

Have a good night everyone

73
Bryan Lynch
NM7C


Reino Talarmo
 

I have never operated that mode but it is installed as part of WSJT here.
Hi John,
The JT9 is actually the decoding program that FT8 is using. So it is normal to get that failure not to close it, when wsjt-x crashes.
I have no hint why wsjt-x crashes in those situations. I am not managed to repeat it. If I understood correctly that crash happens also in a later step than Tx3.
73, Reino OH3mA


locked Re: Q65 only decoding the strongest station #decode

Wayne Newport
 

Thanks Charlie I will try to do that. Had the same problem today several stations on waterfall and only decoding the strongest signal. I can select the undecided signal set F Tol to 50 and hit the decode button and it will decode ok. It’s almost like the single decode in settings is ticked although it is untucked. Talked to several vk stations that have the same problem. My computer has plenty of capacity so it’s not the computer being overwhelmed
Cheers Wayne VK4WTN


Bryan Lynch - NM7C
 

I made an error and uploaded an SD version by accident.

Here's the link to the HD version of the crash recording:
https://youtu.be/HM9N_RLJb14

73,
Bryan Lynch
NM7C

On Thu, Dec 16, 2021 at 5:32 PM Bryan Lynch <airshark@...> wrote:

Following on to my last response.
I still have mod post approval turned on for my account...not sure when
that goes away.

I caught this crash on video/audio.

This time everything was fine in the QSO.
I changed TX Freq for my response.
As soon as the RX response to me was decoded, the app crashed.

I've uploaded a video in HD to Youtube. It's still processing the HD
version as of this reply and will need just a few minutes. Until then, only
an SD copy may be viewed.
See the full crash video HERE (Apologies for the TX audio hum):
https://youtu.be/tyATmy5WLLk

I hope this helps.

73,

Bryan Lynch
NM7C

On Thu, Dec 16, 2021 at 5:17 PM Al Groff via groups.io <al.k0vm=
yahoo.com@groups.io> wrote:

More...
It crashed when I attempted to send my TX 3 response.
AL, K0VM


On 12/16/2021 7:12 PM, Al Groff via groups.io wrote:
( WSJT-X 2.5.3 Win 11/64 )
I too had a WSJT-X crash while attempting to work a / call ( N4CXH/4
).. I have worked other / calls with 2.5.3 but that was the first one
that crashed.

AL, K0VM



On 12/16/2021 2:40 PM, rcktscientist64 wrote:
Several people including me have had this happen while working a call
with “/“ in the call sign. I’m not aware of a fix yet other than
roll back to version 2.5.2.

Bruce - K5WBM

On Dec 16, 2021, at 2:25 PM, n4qwf . <N4QWF1@...> wrote:

This morning I upgraded to WSJT-X version 2.5.3. I also upgraded to
JTAlert 2.50.9. All seemed to work smoothly for about an hour. I
worked a number of stations using FT8 on both 20m and 15m. Suddenly
WSJT-X just disappeared from my screen. It had closed. I tried to
reopen it and got an error message. Here is the text from the on
screen error window.

Sub-process error
orphaned jt9 process

JtAlert was still open and I closed it normally. I closed DXLab
utilities that were open and rebooted the computer. Again all seemed
normal for a short while after the reboot then the same error
occurred. I rebooted the computer and reverted to WSJT-X 2.5.2 and I
am still running JTAlert 2.50.9 and everything has been normal now
for the last 5-6 hours.

I am using Windows 10 64 bit operating system, DXLab suite and my
radio is a Flex 5000.

Thanks <<John N4QWF















n4qwf .
 

I can not say what call or macro I was sending when the software stopped
but I am sure it was not the same call. The JT9 error message must be some
type of clue. I have never operated that mode but it is installed as part
of WSJT here.

73<<John

On Thu, Dec 16, 2021 at 8:17 PM Al Groff via groups.io <al.k0vm=
yahoo.com@groups.io> wrote:

More...
It crashed when I attempted to send my TX 3 response.
AL, K0VM


On 12/16/2021 7:12 PM, Al Groff via groups.io wrote:
( WSJT-X 2.5.3 Win 11/64 )
I too had a WSJT-X crash while attempting to work a / call ( N4CXH/4
).. I have worked other / calls with 2.5.3 but that was the first one
that crashed.

AL, K0VM



On 12/16/2021 2:40 PM, rcktscientist64 wrote:
Several people including me have had this happen while working a call
with “/“ in the call sign. I’m not aware of a fix yet other than
roll back to version 2.5.2.

Bruce - K5WBM

On Dec 16, 2021, at 2:25 PM, n4qwf . <N4QWF1@...> wrote:

This morning I upgraded to WSJT-X version 2.5.3. I also upgraded to
JTAlert 2.50.9. All seemed to work smoothly for about an hour. I
worked a number of stations using FT8 on both 20m and 15m. Suddenly
WSJT-X just disappeared from my screen. It had closed. I tried to
reopen it and got an error message. Here is the text from the on
screen error window.

Sub-process error
orphaned jt9 process

JtAlert was still open and I closed it normally. I closed DXLab
utilities that were open and rebooted the computer. Again all seemed
normal for a short while after the reboot then the same error
occurred. I rebooted the computer and reverted to WSJT-X 2.5.2 and I
am still running JTAlert 2.50.9 and everything has been normal now
for the last 5-6 hours.

I am using Windows 10 64 bit operating system, DXLab suite and my
radio is a Flex 5000.

Thanks <<John N4QWF















locked FLRig TCPIP operation #macOS #adiFiles

Mark Erbaugh <mark.election@...>
 

How does FLRig work with TCPIP? I am running DL2RUM's WithoutWire that creates a CI-V (Cat) interface on a TCP port. I give FLRig the address (it is 127.0.0.1) and the port number (7355) selected in WithoutWire. and click "Use tcpip" in FLRig. Both WithoutWire and FLRig indicate that they are connected, but FLRig is still complaining about the serial port not being set up. Do I need to use a "real" serial port even though I've got the CI-V interface over TCP?

73,
Mark, N8ME


locked FLRig / IC-7610 / M1 Mac mini / OSX Monterey 12.1 #Icom (update) #Icom

Mark Erbaugh <mark.election@...>
 

I think I found part of the issue. I had use tcpip checked. When I unchecked that FLRig started working.

73,
Mark, N8ME


locked Re: Portable calls crashing WSJT-X Version 2.5.3 #Windows10 #windows11 #decode

Bryan Lynch - NM7C
 

I had it happen again just now.
I've been on FT8 all day trying to catch this happening again with more attention paid to the actual steps taken.
I had a QSO with one other "/" call today with no issue (W4ID/6) just before this attempt

(I'm NM7C)
Steps to WSJT-X Crash:

RX: AI7MH/P calling CQ
TX: (Several Attempts) AI7MH/P NM7C [report]
Change: NM7C changed split TX Freq as AI7MH/P was in active QSO (Hold Tx Freq function in WSJT-X)
TX: AI7MH/P NM7C [report]
RX: NM7C AI7MH/P [report]
CRASH and program exit.

To be clear again, the crash happened within 1-2 seconds of decoding "NM7C AI7MH/P". No buttons were pressed to make this occur.

Got the message about an orphaned JT9 process upon attempted re-launch of WSJT-X
Killed the process manually.
Launched WSJT-X again, back to normal ops.

Radio is Kenwood TS-2000
Interface is Signalink USB
WSJT-X Version: 2.5.3
Operating System: Windows 10 Pro
CAT Interface: Ham Radio Deluxe 6.7.0.391
Logging: HRD Logbook 6.7.0.391

Windows Event Viewer crash data:
Faulting application name: wsjtx.exe, version: 2.5.3.0, time stamp: 0x61b0e1e7
Faulting module name: ntdll.dll, version: 10.0.19041.1288, time stamp: 0xa280d1d6
Exception code: 0xc0000374
Fault offset: 0x00000000000ff199
Faulting process id: 0x3048
Faulting application start time: 0x01d7f2c175779c6f
Faulting application path: C:\WSJT\wsjtx\bin\wsjtx.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 8064184e-f48e-495a-8c86-25c0d7181db5
Faulting package full name:
Faulting package-relative application ID:


I hope this helps with troubleshooting efforts.
I've never had a WSJT-X crash in years of using it until this issue.

73,
Bryan Lynch
NM7C


locked FLRig / IC-7610 / M1 Mac mini / OSX Monterey 12.1 #Icom

Mark Erbaugh <mark.election@...>
 

Sorry for the duplicate post, but I can't find my original post and wanted to add some more information.

I can't get FLRig (1.4.3.16) to connect to my IC-7610 over USB. I have another program (RUMlogNG) that has no trouble connecting. It even has an auto discovery mode which tells me which port is being used. I point FLRig at the same port and nothing happens when I click the Init button. I did capture a trace, maybe that will help.

00:30:47.616 : closeRig()
00:30:47.616 : close serial port
00:30:47.617 : ClosePort(): fd = 10
00:30:47.624 : serial port closed
00:30:47.624 : clear frequency list
00:30:47.624 : initialize title bar
00:30:47.624 : start tranceiver serial port
00:30:47.631 : /dev/tty.usbserial-21320 opened
00:30:47.635 : D: startXcvrSerial:
Serial port:
Port : /dev/tty.usbserial-21320
Baud : 9
Stopbits : 1
Retries : 2
Timeout : 50
Loop : 200
RTSCTS : 0
CATptt : 1
RTSptt : 0
DTRptt : 0
RTS+ : 0
DTR+ : 1


00:30:47.635 : initialize transceiver
00:30:47.648 : Q: connect_to_remote: Created new remote_addr @ 0x600003205b30

00:30:47.648 : D: get: Found address [127.0.0.1]:7777

00:30:47.648 : D: open: Trying [127.0.0.1]:7777

00:30:47.648 : Q: connect_to_remote: Created new socket @ 0x600003f32500

00:30:47.648 : D: connect: Connecting to [127.0.0.1]:7777

00:30:47.648 : E: connect_to_remote: Error: 61, connect: Connection refused

00:30:47.649 : E: connect_to_remote: Deleted remote address

00:30:47.649 : E: connect_to_remote: Deleted tcpip socket

73,
Mark, N8ME


locked FLRig 1.4.3.16 vs M1 Mac Min (OSX 12.1 - Monterey) #Icom #macOS

Mark Erbaugh <mark.election@...>
 

I can't seem to get FLRig to connect to my Icom IC-7610 which is connected via USB. I have another program. RUMlogNG that has no problem connecting using the same hardware.

The serial device dropdown lists the ports, but when I select the correct one (at least the same one RUMlogNG uses) and click the Init button, nothing happens.

73,
Mark, N8ME


Al Groff
 

More...
  It crashed when I attempted to send my TX 3 response.
AL, K0VM

On 12/16/2021 7:12 PM, Al Groff via groups.io wrote:
( WSJT-X 2.5.3 Win 11/64 )
I too had a WSJT-X crash while attempting to work a / call ( N4CXH/4 ).. I have worked other / calls  with 2.5.3 but that was the first one that crashed.

AL, K0VM



On 12/16/2021 2:40 PM, rcktscientist64 wrote:
Several people including me have had this happen while working a call with “/“ in the call sign.  I’m not aware of a fix yet other than roll back to version 2.5.2.

Bruce - K5WBM

On Dec 16, 2021, at 2:25 PM, n4qwf . <N4QWF1@...> wrote:

This morning I upgraded to WSJT-X version 2.5.3. I also upgraded to JTAlert 2.50.9. All seemed to work smoothly for about an hour. I worked a number of stations using FT8 on both 20m and 15m. Suddenly WSJT-X just disappeared from my screen. It had closed. I tried to reopen it and got an error message. Here is the text from the on screen error window.

Sub-process error
orphaned jt9 process

JtAlert was still open and I closed it normally. I closed DXLab utilities that were open and rebooted the computer. Again all seemed normal for a short while after the reboot then the same error occurred. I rebooted the computer and reverted to WSJT-X 2.5.2 and I am still running  JTAlert 2.50.9 and everything has been normal now for the last 5-6 hours.

I am using Windows 10 64 bit operating system, DXLab suite and my radio is a Flex 5000.

Thanks <<John N4QWF









Al Groff
 

( WSJT-X 2.5.3 Win 11/64 )
I too had a WSJT-X crash while attempting to work a / call ( N4CXH/4 ).. I have worked other / calls  with 2.5.3 but that was the first one that crashed.

AL, K0VM

On 12/16/2021 2:40 PM, rcktscientist64 wrote:
Several people including me have had this happen while working a call with “/“ in the call sign. I’m not aware of a fix yet other than roll back to version 2.5.2.

Bruce - K5WBM

On Dec 16, 2021, at 2:25 PM, n4qwf . <N4QWF1@...> wrote:

This morning I upgraded to WSJT-X version 2.5.3. I also upgraded to JTAlert 2.50.9. All seemed to work smoothly for about an hour. I worked a number of stations using FT8 on both 20m and 15m. Suddenly WSJT-X just disappeared from my screen. It had closed. I tried to reopen it and got an error message. Here is the text from the on screen error window.

Sub-process error
orphaned jt9 process

JtAlert was still open and I closed it normally. I closed DXLab utilities that were open and rebooted the computer. Again all seemed normal for a short while after the reboot then the same error occurred. I rebooted the computer and reverted to WSJT-X 2.5.2 and I am still running JTAlert 2.50.9 and everything has been normal now for the last 5-6 hours.

I am using Windows 10 64 bit operating system, DXLab suite and my radio is a Flex 5000.

Thanks <<John N4QWF





locked Re: Is there a software program to combine WSPR data for a band from multiple receivers on separate antennas? #WSPR

G4SDG
 

I would find this functionality useful too although I appreciate it's a bit of a niche market. I'm often monitoring 136KHz with a loop antenna into an FT817 and an inverted L into an RSP1a. The RSP1a uses SDR-Uno and a virtual audio cable into multiple WSJT-X instances for WSPR and FST4W modes and the FT817 is fed into the PC audio card and then another set of WSJT-X instances for WSPR and FST4W modes. It's all done inside one Windows PC. I only want to report the strongest reception of each station's decodes to WSPRnet rather than cluttering it up with duplicate reports.

73 Chris G4SDG


ok1fwg
 

OS:Windows 10 (21H2), 64-bit Rig: Kenwood TS-450S + TTL Serial2USB converter for CAT Version 2.5.0 w/o issues in this manner. After programm start the QRG was read from the radio. Upgraded to 2.5.3 Seem to me something went wrong as the frequency displayed after programm start is not updated. I have to either change the band manually, or simply start to call some station. Then everything is okay. OR, after about 40 sec without changing/touching anything the handshake with the radio begin and the QRG is updated. It did not do this in 2.5.0. And second, if I have to change band, then it is displayed like this: But next time it is okay, like this: Willi, OK1FWG


Bryan Lynch - NM7C
 

Did you happen to try and work any stations with "/stroke" identifier? There's a thread going right now about crashes exactly as you describe when interacting with /stroke calls.

You don't have to reboot your computer to get back in.
The process for "jt9 - WSJT-X slow mode decoder" must be manually killed to be able to re-launch WSJT-X.

-Bryan NM7C


Bruce - K5WBM
 

Several people including me have had this happen while working a call with “/“ in the call sign. I’m not aware of a fix yet other than roll back to version 2.5.2.

Bruce - K5WBM

On Dec 16, 2021, at 2:25 PM, n4qwf . <N4QWF1@...> wrote:

This morning I upgraded to WSJT-X version 2.5.3. I also upgraded to JTAlert 2.50.9. All seemed to work smoothly for about an hour. I worked a number of stations using FT8 on both 20m and 15m. Suddenly WSJT-X just disappeared from my screen. It had closed. I tried to reopen it and got an error message. Here is the text from the on screen error window.

Sub-process error
orphaned jt9 process

JtAlert was still open and I closed it normally. I closed DXLab utilities that were open and rebooted the computer. Again all seemed normal for a short while after the reboot then the same error occurred. I rebooted the computer and reverted to WSJT-X 2.5.2 and I am still running JTAlert 2.50.9 and everything has been normal now for the last 5-6 hours.

I am using Windows 10 64 bit operating system, DXLab suite and my radio is a Flex 5000.

Thanks <<John N4QWF



n4qwf .
 

This morning I upgraded to WSJT-X version 2.5.3. I also upgraded to JTAlert 2.50.9. All seemed to work smoothly for about an hour. I worked a number of stations using FT8 on both 20m and 15m. Suddenly WSJT-X just disappeared from my screen. It had closed. I tried to reopen it and got an error message. Here is the text from the on screen error window.

Sub-process error
orphaned jt9 process

JtAlert was still open and I closed it normally. I closed DXLab utilities that were open and rebooted the computer. Again all seemed normal for a short while after the reboot then the same error occurred. I rebooted the computer and reverted to WSJT-X 2.5.2 and I am still running JTAlert 2.50.9 and everything has been normal now for the last 5-6 hours.

I am using Windows 10 64 bit operating system, DXLab suite and my radio is a Flex 5000.

Thanks <<John N4QWF


locked Re: Portable calls crashing WSJT-X Version 2.5.3 #Windows10 #windows11 #decode

Reino Talarmo
 

Win10 Event Viewer App Error record:
Faulting application name: wsjtx.exe, version: 2.5.3.0, time stamp: 0x61b0e1e7 Faulting module name: ntdll.dll, version: 10.0.19041.1288, time stamp: 0xa280d1d6 Exception code: 0xc0000374 Fault offset: 0x00000000000ff199 Faulting process id: 0x8b4 Faulting application start time: 0x01d7f1fd6c5bf4f2 Faulting application path: C:\WSJT\wsjtx\bin\wsjtx.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: c7cb1266-3a41-46df-98f1-a78927471446

Hi,

I am not a Windows expert, but just looked the date of the ntdll.dll in my Windows 10 PC and it is 13.10.2021 7:11 in one PC and 26.10.2021 14:31 in another. I have no crashes due to / in one call sign either way. Well, Windows experts could tell more about the report meaning, if that matters at all.

73, Reino OH3mA


locked Re: Q65 only decoding the strongest station #decode

Charles Suckling
 

Hi Wayne

Interesting.  If you can collect some wave file examples (Save All) and send me a few where you are seeing this behaviour, I would be happy to take a look at them here.

73

Charlie

On Thu, 16 Dec 2021 at 08:32, Wayne Newport <wazzan1@...> wrote:
Thanks Charlie, the signals yesterday weren’t overlapping and the weaker signal was around -10.I set F Tol to 50hz positioned on the weaker signal but still only decoded the strongest signal. I talked to another ham friend this morning and he has exactly the same problem
Wayne VK4WTN




locked Re: Q65 only decoding the strongest station #decode

Wayne Newport
 

Thanks Charlie, the signals yesterday weren’t overlapping and the weaker signal was around -10.I set F Tol to 50hz positioned on the weaker signal but still only decoded the strongest signal. I talked to another ham friend this morning and he has exactly the same problem
Wayne VK4WTN

9521 - 9540 of 39974