Support Forums
Origin of E116 - Cannot log: insufficient space available on B:
E116 DT80 MEMORY

Hello,
The integrated DT80 in our system has lost its configuration (no current job).
It seems thats the DT80 have run out of memory space, and is unable to load the configurated jobs at start up. As descibded in its logs with the error E116 :

EVENT ,2023/04/21,00:39:25,0.003906,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)"
EVENT ,2023/04/21,00:39:25,0.552124,"Beginning entry of job "CONFIG""
EVENT ,2023/04/21,00:39:28,0.198364,"Loaded job "CONFIG""
EVENT ,2023/04/21,17:48:25,0.469970,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)"
EVENT ,2023/04/21,17:48:26,0.016479,"Beginning entry of job "CONFIG""
EVENT ,2023/04/21,17:48:28,0.731079,"E116 - Cannot log: insufficient space available on B:"
EVENT ,2023/04/21,17:48:28,0.945434,"Job cleared"
EVENT ,2023/04/21,18:23:27,0.178466,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)"
EVENT ,2023/04/24,18:39:21,0.865844,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)"

The DT80 and its datalogging is configured to erase the oldest logged data to write the new measurements if it run out of space, and had worked well until this occurence.

Do you know what could have caused this memory error and how to prevent it?

Thanks

Hello, The integrated DT80 in our system has lost its configuration (no current job). It seems thats the DT80 have run out of memory space, and is unable to load the configurated jobs at start up. As descibded in its logs with the error E116 : EVENT ,2023/04/21,00:39:25,0.003906,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)" EVENT ,2023/04/21,00:39:25,0.552124,"Beginning entry of job "CONFIG"" EVENT ,2023/04/21,00:39:28,0.198364,"Loaded job "CONFIG"" EVENT ,2023/04/21,17:48:25,0.469970,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)" EVENT ,2023/04/21,17:48:26,0.016479,"Beginning entry of job "CONFIG"" EVENT ,2023/04/21,17:48:28,0.731079,"E116 - Cannot log: insufficient space available on B:" EVENT ,2023/04/21,17:48:28,0.945434,"Job cleared" EVENT ,2023/04/21,18:23:27,0.178466,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)" EVENT ,2023/04/24,18:39:21,0.865844,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)" The DT80 and its datalogging is configured to erase the oldest logged data to write the new measurements if it run out of space, and had worked well until this occurence. Do you know what could have caused this memory error and how to prevent it? Thanks

Hi Theo,

E116 could be triggered by accidentally trying to send a program with a big memory allocation that is bigger than free memory.

Imagine you have 128 MB of internal memory, 15 MB for file system so in theory, you can use 113 MB for the program.

If you have the program written in dEX 2.0 with a 60 MB allocation, then you try to send another one with a 60 MB allocation from DeTransfer (supposedly to replace the old one). You will trigger E116 because the attempt on DeTransfer will create a secondary program.

We suggest deleting the old program, and ensuring you have enough free memory before sending the new program.

Another possibility (based on our experience) is you accidentally consume the free memory by downloading CSV files to the internal memory. So when you need to send the second program, the space was occupied by many CSV files. DIR would help to detect this issue.

Best regards,
dataTaker Expert

Hi Theo, E116 could be triggered by accidentally trying to send a program with a big memory allocation that is bigger than free memory. Imagine you have 128 MB of internal memory, 15 MB for file system so in theory, you can use 113 MB for the program. If you have the program written in dEX 2.0 with a 60 MB allocation, then you try to send another one with a 60 MB allocation from DeTransfer (supposedly to replace the old one). You will trigger E116 because the attempt on DeTransfer will create a secondary program. We suggest deleting the old program, and ensuring you have enough free memory before sending the new program. Another possibility (based on our experience) is you accidentally consume the free memory by downloading CSV files to the internal memory. So when you need to send the second program, the space was occupied by many CSV files. DIR would help to detect this issue. Best regards, dataTaker Expert

Hello,
Thanks for your answer. However the error and the loss of configuration happend during a regular start up of the system. And not related to configuration installation or DT80 files manipulation.

The only actor exchanging data with the DT80 is a PLC sending Modbus request on ethernet every 2s.

For information, after the error 20.2% of the DT80 internal memory was still free.

Following the error 116, the jobs were cleared and the DT80 reseted but the problem happend again after multiple restarts:

EVENT ,2023/04/25,13:44:37,0.803955,"Beginning entry of job "CONFIG""
EVENT ,2023/04/25,13:44:43,0.644165,"Loaded job "CONFIG""
EVENT ,2023/04/25,14:00:20,0.102539,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)"
EVENT ,2023/04/25,14:00:20,0.693237,"Beginning entry of job "CONFIG""
EVENT ,2023/04/25,14:00:24,0.874511,"Loaded job "CONFIG""
EVENT ,2023/04/26,11:01:46,0.635131,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)"
EVENT ,2023/04/26,11:01:47,0.219360,"Beginning entry of job "CONFIG""
EVENT ,2023/04/26,11:01:51,0.539672,"Loaded job "CONFIG""
EVENT ,2023/04/26,14:34:25,0.949707,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)"
EVENT ,2023/04/26,14:34:26,0.539916,"Beginning entry of job "CONFIG""
EVENT ,2023/04/26,14:34:32,0.004028,"Loaded job "CONFIG""
EVENT ,2023/04/26,14:48:47,0.197509,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)"
EVENT ,2023/04/26,14:48:47,0.781860,"Beginning entry of job "CONFIG""
EVENT ,2023/04/26,14:48:53,0.233032,"Loaded job "CONFIG""
EVENT ,2023/04/26,15:21:36,0.723510,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)"
EVENT ,2023/04/26,15:21:37,0.307983,"Beginning entry of job "CONFIG""
EVENT ,2023/04/26,15:21:41,0.628540,"Loaded job "CONFIG""
EVENT ,2023/04/27,08:16:54,0.452880,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)"
EVENT ,2023/04/27,08:16:55,0.095336,"Beginning entry of job "CONFIG""
EVENT ,2023/04/27,08:16:59,0.288818,"Loaded job "CONFIG""
EVENT ,2023/04/27,15:16:12,0.712524,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)"
EVENT ,2023/04/27,15:16:13,0.295654,"Beginning entry of job "CONFIG""
EVENT ,2023/04/27,15:16:17,0.661987,"Loaded job "CONFIG""
EVENT ,2023/04/27,15:27:55,0.877563,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)"
EVENT ,2023/04/27,15:27:56,0.466796,"Beginning entry of job "CONFIG""
EVENT ,2023/04/27,15:28:01,0.899047,"Loaded job "CONFIG""
EVENT ,2023/05/02,14:39:59,0.328613,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)"
EVENT ,2023/05/02,14:39:59,0.911987,"Beginning entry of job "CONFIG""
EVENT ,2023/05/02,14:40:04,0.346191,"E116 - Cannot log: insufficient space available on B:"
EVENT ,2023/05/02,14:40:04,0.559814,"Job cleared"
EVENT ,2023/05/03,13:05:33,0.979858,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)"
EVENT ,2023/05/03,14:57:49,0.351074,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)"

No operator action was done on th DT80 during this period of operation.

Best regards,
Theo

Hello, Thanks for your answer. However the error and the loss of configuration happend during a regular start up of the system. And not related to configuration installation or DT80 files manipulation. The only actor exchanging data with the DT80 is a PLC sending Modbus request on ethernet every 2s. For information, after the error 20.2% of the DT80 internal memory was still free. Following the error 116, the jobs were cleared and the DT80 reseted but the problem happend again after multiple restarts: EVENT ,2023/04/25,13:44:37,0.803955,"Beginning entry of job "CONFIG"" EVENT ,2023/04/25,13:44:43,0.644165,"Loaded job "CONFIG"" EVENT ,2023/04/25,14:00:20,0.102539,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)" EVENT ,2023/04/25,14:00:20,0.693237,"Beginning entry of job "CONFIG"" EVENT ,2023/04/25,14:00:24,0.874511,"Loaded job "CONFIG"" EVENT ,2023/04/26,11:01:46,0.635131,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)" EVENT ,2023/04/26,11:01:47,0.219360,"Beginning entry of job "CONFIG"" EVENT ,2023/04/26,11:01:51,0.539672,"Loaded job "CONFIG"" EVENT ,2023/04/26,14:34:25,0.949707,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)" EVENT ,2023/04/26,14:34:26,0.539916,"Beginning entry of job "CONFIG"" EVENT ,2023/04/26,14:34:32,0.004028,"Loaded job "CONFIG"" EVENT ,2023/04/26,14:48:47,0.197509,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)" EVENT ,2023/04/26,14:48:47,0.781860,"Beginning entry of job "CONFIG"" EVENT ,2023/04/26,14:48:53,0.233032,"Loaded job "CONFIG"" EVENT ,2023/04/26,15:21:36,0.723510,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)" EVENT ,2023/04/26,15:21:37,0.307983,"Beginning entry of job "CONFIG"" EVENT ,2023/04/26,15:21:41,0.628540,"Loaded job "CONFIG"" EVENT ,2023/04/27,08:16:54,0.452880,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)" EVENT ,2023/04/27,08:16:55,0.095336,"Beginning entry of job "CONFIG"" EVENT ,2023/04/27,08:16:59,0.288818,"Loaded job "CONFIG"" EVENT ,2023/04/27,15:16:12,0.712524,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)" EVENT ,2023/04/27,15:16:13,0.295654,"Beginning entry of job "CONFIG"" EVENT ,2023/04/27,15:16:17,0.661987,"Loaded job "CONFIG"" EVENT ,2023/04/27,15:27:55,0.877563,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)" EVENT ,2023/04/27,15:27:56,0.466796,"Beginning entry of job "CONFIG"" EVENT ,2023/04/27,15:28:01,0.899047,"Loaded job "CONFIG"" EVENT ,2023/05/02,14:39:59,0.328613,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)" EVENT ,2023/05/02,14:39:59,0.911987,"Beginning entry of job "CONFIG"" EVENT ,2023/05/02,14:40:04,0.346191,"E116 - Cannot log: insufficient space available on B:" EVENT ,2023/05/02,14:40:04,0.559814,"Job cleared" EVENT ,2023/05/03,13:05:33,0.979858,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)" EVENT ,2023/05/03,14:57:49,0.351074,"Reset 9.22.9125 POWERUP/BUTTON (c0a00005)" No operator action was done on th DT80 during this period of operation. Best regards, Theo

Hi Theo,

Did you use the NOV option on your schedule?

Can you send the logger service data report to datataker.support@thermofisher.com? I would like to check the setting and file structure.

Thanks.

Best regards,
dataTaker Expert

Hi Theo, Did you use the NOV option on your schedule? Can you send the logger service data report to datataker.support@thermofisher.com? I would like to check the setting and file structure. Thanks. Best regards, dataTaker Expert
edited May 16 '23 at 3:42 am

Hi,
Sorry for the lateness of the response as I was waiting for the results of solutions trials.

All jobs are set on overwrite (OV).

I am not able to generate directly the logger service log via dex or dex2, because it crashes the datataker (then restarts).
Moreover attempting to send commands using dex or dex2 also crashes the datataker.

However I have been able to get the logs and internal files via ftp.

I have sent the configuration file and logs to the provIded email address.

Thanks,
Theo.

Hi, Sorry for the lateness of the response as I was waiting for the results of solutions trials. All jobs are set on overwrite (OV). I am not able to generate directly the logger service log via dex or dex2, because it crashes the datataker (then restarts). Moreover attempting to send commands using dex or dex2 also crashes the datataker. However I have been able to get the logs and internal files via ftp. I have sent the configuration file and logs to the provIded email address. Thanks, Theo.
edited May 23 '23 at 4:29 pm

Hi Theo,

Your program occupied 90MB while it remain dormant. I guess it must be the issue of configuration loss. It is not actually disappear, you can check it using DIRJOBS and restart it using RUNJOB (check for a complete syntax in the manual).

The reason you got E116 is that you tried to send another program with the same 90MB memory usage while you only have 30MB free memory.

Best regards,
dataTaker Expert

Hi Theo, Your program occupied 90MB while it remain dormant. I guess it must be the issue of configuration loss. It is not actually disappear, you can check it using DIRJOBS and restart it using RUNJOB (check for a complete syntax in the manual). The reason you got E116 is that you tried to send another program with the same 90MB memory usage while you only have 30MB free memory. Best regards, dataTaker Expert

Hi,
Thanks, but as I said in my previous posts, the E116 error is not correlated to an external action and happend during the autonomous operation of the DT80.
Is it possible that the device reloaded "on itself" the config and memory allocation and caused the issue? I.e. after a stop/start.

Also, I read in another post that this 30MB memory limit issue should be fixed in the firmeware 9.24. Could you give an estimation of its release date?

Best regards,

Theo

Hi, Thanks, but as I said in my previous posts, the E116 error is not correlated to an external action and happend during the autonomous operation of the DT80. Is it possible that the device reloaded "on itself" the config and memory allocation and caused the issue? I.e. after a stop/start. Also, I read in another post that this 30MB memory limit issue should be fixed in the firmeware 9.24. Could you give an estimation of its release date? Best regards, Theo

Hi Theo,

Sorry for the response delay.

The deletion failure is likely to happen during dEX 2.0 reprogramming and if you mention there was no external factor then we need to check if your schedule has NOV setting. It is a "no overwrite" when the memory is full. Because we realize the message is about insufficient space.

Best regards,
dataTaker Expert.

Hi Theo, Sorry for the response delay. The deletion failure is likely to happen during dEX 2.0 reprogramming and if you mention there was no external factor then we need to check if your schedule has NOV setting. It is a "no overwrite" when the memory is full. Because we realize the message is about insufficient space. Best regards, dataTaker Expert.
152
7
2
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Cancel
Delete
Pending draft ... Click to resume editing
Discard draft