|
|
Post by Tony Ei7bmb on Mar 4, 2022 17:30:41 GMT
Hi, sometimes when I click on the waterfall it kills JTDX and when I try to re start I get this error message  |
|
|
|
Post by Igor UA3DJY on Mar 4, 2022 18:12:42 GMT
Could you start jtdx.exe from terminal (cmd.exe) window, please. Possibly there will be some messages on the failure at clicking on waterfall.
Other option is to check Windows logs: Start → Run → Open → eventvwr.msc
|
|
|
|
Post by Tony Ei7bmb on Mar 5, 2022 10:47:25 GMT
Thanks Igor, next time it happens I will check
|
|
|
|
Post by Tony Ei7bmb on Mar 5, 2022 13:56:55 GMT
Hi Igor, this is what I am seeing on latest crash
Faulting application name: jtdx.exe, version: 2.2.159.0, time stamp: 0x621e1607
Faulting module name: jtdx.exe, version: 2.2.159.0, time stamp: 0x621e1607
Exception code: 0xc0000005
Fault offset: 0x00000000004a8232
Faulting process ID: 0x2d5c
Faulting application start time: 0x01d8307bcd725825
Faulting application path: C:\JTDX64\159\bin\jtdx.exe
Faulting module path: C:\JTDX64\159\bin\jtdx.exe
Report ID: 38742f51-16ff-4623-a0af-940a7c6d20c4
Faulting package full name:
Faulting package-relative application ID:
|
|
|
|
Post by w9mdb on Mar 5, 2022 14:20:08 GMT
I take it you have rebooted the computer and still see it?
The offset looks like it's in the fftwf_codelet in the 64-bit version which doesn't make sense.
Is yours the 32-bit or 64-bit version?
|
|
|
|
Post by Tony Ei7bmb on Mar 5, 2022 14:57:13 GMT
Hi, yes rebooted and see it randomly, JTDX 159 can run for hours with no problem. win64bit version
|
|
|
|
Post by Tony Ei7bmb on Mar 7, 2022 12:02:06 GMT
Just noticed it crashes on band change in Thetis Anan software. I've recently started using TCI CAT control so will revert back to standard CAT as a test.
Edit: It seems using TCI is the issue as I've had no crashes since changing back to standard CAT.
|
|
|
|
Post by Tony Ei7bmb on Mar 30, 2022 11:11:51 GMT
Using 169 rc1 debug build. With TCI used for CAT the program crashes occasionally on freq change. Mode at the time was FT8 but seeing the following reported on debug txt with FT4 mentioned
10:39:39.289 Transceiver set 1 #:4 end 49 ms.
10:39:40.235 10 Poll start interval=1000 retries=3 fast_mode=0 ft4_mode=0 sec=10 ms=235
10:39:40.235 10 Poll end 10:39:40.235 no signal
10:39:41.227 11 Poll start interval=1000 retries=2 fast_mode=0 ft4_mode=0 sec=11 ms=227
10:39:41.227 11 Poll end 10:39:41.227 no signal
10:39:42.229 12 Poll start interval=1000 retries=1 fast_mode=0 ft4_mode=0 sec=12 ms=229
10:39:42.230 12 Poll end 10:39:42.230 signal
10:39:43.237 13 Poll start interval=1000 retries=0 fast_mode=0 ft4_mode=0 sec=13 ms=237
10:39:43.237 13 Poll end 10:39:43.237 no signal
10:39:44.242 14 Poll start interval=1000 retries=0 fast_mode=0 ft4_mode=0 sec=14 ms=242
10:39:44.242 14 Poll end 10:39:44.242 no signal
10:39:45.247 0 Poll start interval=1000 retries=0 fast_mode=0 ft4_mode=0 sec=0 ms=247
10:39:45.247 0 Poll end 10:39:45.247 no signal
10:39:46.237 1 Poll start interval=1000 retries=0 fast_mode=0 ft4_mode=0 sec=1 ms=237
10:39:46.237 1 Poll end 10:39:46.238 no signal
10:39:47.246 2 Poll start interval=1000 retries=0 fast_mode=0 ft4_mode=0 sec=2 ms=246
10:39:47.246 2 Poll end 10:39:47.246 no signal
10:39:48.237 3 Poll start interval=1000 retries=0 fast_mode=0 ft4_mode=0 sec=3 ms=237
10:39:48.237 3 Poll end 10:39:48.237 no signal
10:39:49.244 4 Poll start interval=1000 retries=0 fast_mode=0 ft4_mode=0 sec=4 ms=244
10:39:49.244 4 Poll end 10:39:49.244 no signal
Trace log has this entry mentioning FT4
2022-03-30T10:39:39.239Z(C:\JTSDK64-Tools\tmp\wsjtx\Configuration.cpp:1189)Debug: Configuration::transceiver_ft4_mode: false Transceiver::TransceiverState(online: yes Frequency {50313000Hz, 0Hz} Transceiver::UNK; SPLIT: off; PTT: off; FAST_MODE: off; AUDIO: off; TX_AUDIO: off; TUNE: off; QUICK: off; PERIOD: 120sec.; BLOCKSIZE: 3456; SYMBOLSLENGTH: 79; FRAMESPERSYMBOL: 1920; TRFREQUENCY: 1500Hz; TONESPACING: -3; SYNCHRONIZE: on; DBSNR: 99; TRPERIOD: 60sec.; SPREAD: 0; NSYM: 79; VOLUME: 0; LEVEL: 0dBm; POWER: 0mWatts; SWR: 0)
|
|
|
|
Post by w9mdb on Mar 30, 2022 13:02:56 GMT
I'm using Thetis 2.1.18 21k9b with a 7000MLE MKII and TCI and do not see any such crashes on 1.1.160-rc1
I know Arvo has made some changes which aren't published yet trying to make TCI more robust.
|
|
|
|
Post by Tony Ei7bmb on Mar 30, 2022 13:17:25 GMT
I'm using Thetis 2.1.18 21k9b with a 7000MLE MKII and TCI and do not see any such crashes on 1.1.160-rc1 I know Arvo has made some changes which aren't published yet trying to make TCI more robust. What a coincidence Mike, I have the exact same set up, with K9 though, not the b update. Its no big deal right now as standard CAT works fine, but would be cool to get it working in case TCI audio becomes available in the future for Thetis.
Thanks again for the help, I'll await Arvo's updates.
|
|
|
|
Post by Tony Ei7bmb on Apr 4, 2022 13:55:11 GMT
I'm using Thetis 2.1.18 21k9b with a 7000MLE MKII and TCI and do not see any such crashes on 1.1.160-rc1 I know Arvo has made some changes which aren't published yet trying to make TCI more robust. Mike may I ask if you are using "spilt" or "fake it " option? I've seen no crashes using "fake it" so far. Ramdor over on the thetis forum has been able to replicate the crash's using "spilt" |
|
