Data Management for File Logging:
If you are using File Logging in your Simulink model, below are several strategies to help you minimize file log data (.dat and .timestamp files).
NOTE: The file logging is automatically stopped for the current file log if the available disk space is less than 1 GB. In this case, the target will show a warning about disk space availability and stop logging. The execution of the application won't be affected.
1. Limit the number of file logs per application:
Control how many file logs are stored on your Speedgoat target machine. You can set a limit so that older logs are automatically overwritten, preventing unnecessary accumulation of data. For detailed instructions, refer to the MATLAB documentation on managing file logs. How can I control the number of file logs stored on my Speedgoat target machine?
2. Reduce the amount of data that you are logging:
To record less data, reduce the number of signals logged, or change the sample time or data type of the signal feeding the "File Log" block. You can alternatively modify the 'Decimation' parameter of the "File Log" block to decrease the frequency of logging (available in R2022a and later). The decimation can also be changed programmatically for every simulation run by using File Log decimation functions.
It is also possible to enclose File Log blocks in Enabled Subsystem blocks to exclude certain signals from logging at certain times. Other conditional block execution semantics like for-iterator, function-call, or triggered subsystem are also supported.
3. Record file logging data only when needed:
Rather than logging signals continuously during the whole simulation run, record data only when needed. This will create multiple smaller file logs during a simulation. You can do this using either the interactive Start/Stop Recording API, or an 'Enable File Log' block in your model. For more details and examples, see:
4. Import and delete file logs:
If your workflow involves frequent runs and generates numerous DAT files, it’s important to regularly import and delete these logs. You can use the Import File Log dialog in MATLAB, or the "import" and "discard" functions. Since R2022b, logs are no longer automatically deleted from the target after import. You can delete all available file logs for all applications with the following command:
>> tg = slrealtime;
>> discard(tg.FileLog,tg.FileLog.list)
Note that file logs can only be imported or deleted if they are not being written to. In R2022b and earlier, the associated simulation must be stopped before performing these operations.
You can also use basic protocols like FTP to copy and remove file logs from the target to your machine. See:
Data Management for other data:
Beyond file logs, other types of data can occupy valuable storage space:
1. Delete installed real-time applications:
Each time you load a model, it is installed in an application folder on the target. To free up space, remove unused applications with:
% Remove a specific application
tg.removeApplication(<applicationName>);
% Remove all applications
tg.removeAllApplications;
To be removed, a real-time application cannot be loaded or running.
2. Delete all user data:
To completely wipe user data—including installed applications and file logs—from the Speedgoat SSD, use the update command:
>> tg.update;
This command erases all user-generated data and returns the system to a clean state with updated software. Make sure to import file log data before running this operation, as it cannot be undone.
3. Don't use "Check Static Range" blocks in your model:
"Check Static Range" blocks can cause the Speedgoat file system to run out of space by creating huge "verify.dat" files. See this MATLAB answer for more information.
