Locked RC2.4 and JT4G #JT4
Good Day All
Getting: Subprocess failed with exit code 2 - Not sure if known issue or not Window 7 Pro WSJT-X 2.4.0-RC1 ZLP Interface Radio FT817 - Cat working ok, PTT working ok Switch to JT4G and after about 2 mins of monitoring get error below, click OK and program terminates --------------------------- WSJT-X - sub --------------------------- Subprocess Error --------------------------- Subprocess failed with exit code 2 --------------------------- OK Hide Details... --------------------------- Running: C:\WSJT\wsjtx\bin\jt9 -s "WSJT-X - sub" -w 1 -m 3 -e C:\WSJT\wsjtx\bin -a "C:\Users\Tom\AppData\Local\WSJT-X - sub" -t "C:\Users\Tom\AppData\Local\Temp\WSJT-X - sub" At line 13 of file C:\Users\bill\src\k1jt\wsjtx\lib\pctile.f90 Fortran runtime error: Index '-26' of dimension 1 of array 'tmp' below lower bound of 1 Error termination. Backtrace: Could not print backtrace: libbacktrace could not find executable to open #0 0xffffffff #1 0xffffffff #2 0xffffffff #3 0xffffffff #4 0xffffffff #5 0xffffffff #6 0xffffffff #7 0xffffffff #8 0xffffffff #9 0xffffffff #10 0xffffffff #11 0xffffffff #12 0xffffffff #13 0xffffffff #14 0xffffffff #15 0xffffffff --------------------------- Tom GM8MJV |
|
g3wdg <charlie@...>
Hi Tom
toggle quoted message
Show quoted text
I've successfully used JT4G with 2.4 -rc1 without seeing this error. Which mode were you using prior to switching to JT4? The only subprocess error I have come across is when returning to Q65 from JT4, if the JT4 was on submode F or G. In this case the error reported is different to yours, and is known. Charlie G3WDG Good Day All |
|
Morning Charlie
toggle quoted message
Show quoted text
To be honest I can’t remember, the way wsjt-x automatically saves the settings when I start up WSJT-X now it is in JT4 mode. I will reset the mode to ’something’ say FT8 later on today and have a play. I don’t think it was Q65 as was using it on 13 cms and have not used that mode on that radio before. Thanks Tom GM8MJV
|
|
Sorry Charlie, I deleted my earlier reply as I think I was remembering the original issue before the second release of 2.4.0. Cheers - Dave (G0DJA) |
|
Setup a vanilla configuration for FT8 and switched to it - radio can set there RX'ing no issues at all. Setup JT4G configuration - switched to it - 2 mins later Sub Process Error appears Running: C:\WSJT\wsjtx\bin\jt9 -s "WSJT-X - sub" -w 1 -m 3 -e C:\WSJT\wsjtx\bin -a "C:\Users\Tom\AppData\Local\WSJT-X - sub" -t "C:\Users\Tom\AppData\Local\Temp\WSJT-X - sub" Repeated and will happen each time after about 2 mins.
|
|
Unfortunately, It's just happened again to me. I had been running JT4g trying to detect signals from a 23cm beacon and it had been running for some time. I just came back into the shack and there was an error message "Subprocess Error. Subprocess failed with exit code 2" In the box under 'advanced' there was a message At line 13 of file C:\Users\bill\src\k1jt\wsjtx\lib\pctile.f90 Fortran runtime error: Index '-25' of dimension 1 of array 'tmp' below lower bound of 1
Error termination. Backtrace:
Could not print backtrace: libbacktrace could not find executable to open #0 0xffffffff #1 0xffffffff #2 0xffffffff #3 0xffffffff #4 0xffffffff #5 0xffffffff #6 0xffffffff #7 0xffffffff #8 0xffffffff #9 0xffffffff #10 0xffffffff #11 0xffffffff #12 0xffffffff #13 0xffffffff #14 0xffffffff #15 0xffffffff"
Cheers - Dave (G0DJA) |
|
On 24/02/2021 12:44, David Ackrill
wrote:
Hi Dave, a saved .WAV file that reproduces this issue would be helpful. Send to g4wjs <at> classdesign <dot> com. 73 |
|
OK Bill, I'll set "Save all" to on. Previously was 'Save Decoded" as the empty WAV files end up taking up space. Cheers - Dave (G0DJA) |
|
Now I can't get it to run past the 1st decode attempt after starting. I'll try running in a different mode 1st and swap over to JT4g. Dave (G0DJA) |
|
Bill
toggle quoted message
Show quoted text
WAV file mailed to your private address Tom GM8MJV
|
|
On 24/02/2021 13:06, Bill Somerville
wrote:
Hi Tom, and Dave, thanks for the saved .WAV file Tom. I can confirm that the defect that causes the above error has been fixed for the next release. 73 |
|