Hello,

I'm using series3 DT80. After firmware upgrade to last version v9.22, logger
was working fine for a week, untill I wanted to clear logger internal memory using command DELALLJOBS. Result of "delalljobs" command was that current job was terminated but message SW exception appeared. Moreover, internal disk was not cleared.

Now, logger display show message "No current job", but I can't log any new job. SW exception appers every time after "delalljobs" command execution and internal memory is still not cleared. This is my memory status:
"DT80> STATUS6
3848,122464 Internal kB free, used"

I'm attaching UERRLOG command log:
2021/06/04,10:34:22
Freeze Detected @Task: Command Processor @Pos: 000DDF94 @Ret: 0x000ddf94
Exception 200 at 0x001005ec
SRR1=00009032 DSISR=00000809 DAR=00000000 BAR=00000000 MSTAT=00000080
LR=001005e4 CR=22000022 CTR=0000007e XER=20000000
R00:07 0000007b 04170410 0015bb50 0417047b 00158edd 00000002 04170368 04170478
R08:15 00158edb 00000000 041cfd5a f00d4321 22000024 04021be4 53535353 53535353
R16:23 53535353 53535353 53535353 0000000c 00000000 00000000 00000000 53535353
R24:31 00000001 00000000 000fc9bc 00000002 00030c96 04118ca0 04020000 000ddf94
Call stack: 000fca58 001009f0 0411e590 000fedb0 000ddf94 000be798 000bf5e0 000c2c54
000b70dc 0005000c 0003ca9c 00042768 000fbce4 000fbc78 ffffffff ffffffff

So please tell me what my next steps should be?

Regards
Ladislav

Hi Ladislav,

In the firmware version 9.22, there is a glitch when using memory allocation greater than 30MB; you will not delete the program. This program deletion will happen automatically when you send a new program using the dEX programming platform due to using the same job name CONFIG.

This deletion is not limited to automatic deletion when sending a new program but also a failure on using DELJOB or DELALLJOBS commands and deletion via FTP access. This failure is because deletion of bigger memory allocation will need more time, while a timeout restricts the time itself. The timeout limit is 30MB allocation or less.

If you already have a program with greater than 30MB allocation in the logger, there are two solutions:

• You can downgrade the firmware to the 9.20 version in which no timeout feature.
• You can reformat and reinstall the 9.22 version of firmware before sending a new program.

Currently, we are working on developing the 9.24 version to address this issue.

Best regards,
dataTaker

Thank you for your reply,

Yes, my program was greater than 30MB. I formatted internal file system and downgrade the firmware. Logger works properly now.

Greetings,
Ladislav