Simulink Real-Time Application is using too much disk for logging (verify.dat file)

[Updated, see solution at the end]

Hi all,

I've a Simulink Real-Time application running on a Speedgoat Real Time machine that is using too much space from the hard disk. In fact, the application writes a verify.dat file that seems to be an internal log. It is located at /home/slrt/applications/MyApplication/verify/verify.dat . After 2 or 3 days running my application consecutively, this verify.dat file becomes too large (around 55GB in my system) and therefore my disk usage increases to 100% and the whole system crashes.

This isn't defined by myself and it is created by the application itself. I tried to stop logging everything from my model and I can't stop this file being created. If I stop the application and restart it, the file is deleted and once the application starts again, the file is recreated and starts increasing.

I'm using the following commands to load and start my application into speedgoat real time machine:

> slrealtime load --AppName MyApplication      //load the application
> slrealtime start                             // starts the application

I tried to delete the verify.dat file while the application is running, but the disk usage keeps increasing, which is expected if the application has the file already open and keeps writing somewhere on the hard disk. The application does not crash. This means the having a cron job deleting or erasing the file every hour doesn't solve the problem. I have to stop and restart the application to release space in disk from this file, which I can't do because I need the application runnning 24/7 .

How to turn off this log in such a way that the verify.dat is no longer created? Another solution would be 'split the verify.dat into several files' and then I could delete the old ones keeping the new ones for debugging, if needed.

Thanks in advance for any help.

Best,

Isaias Faria.

[Solution update]

In my model I had the block "Check Static Range" that creates this verify.dat file. I replaced this block by the "Interval Test" and this file is no longer created. It seems an internal implementation of the "Check Static Range" block.

I'm closing this quesition.

[Isaias]

[Solution update]

In my model I had the block "Check Static Range" that creates this verify.dat file. I replaced this block by the "Interval Test" and this file is no longer created. It seems an internal implementation of the "Check Static Range" block.

Answer 1

[Stefanie Schwarz]

Hi Isaias,

thank you very much for posting your solution.

The Check Static Range block has an Assertion block internally and will create and keep writing to a binary file "verify.dat" on the target. Simulink uses this to make the testing framework compatible with Simulink Real-Time.

We can see how this can become a real issue for long-term runs, so we may look into changing this behavior for future MATLAB versions.