This is machine translation

Translated by Microsoft
Mouseover text to see original. Click the button below to return to the English verison of the page.

Note: This page has been translated by MathWorks. Please click here
To view all translated materals including this page, select Japan from the country navigator on the bottom of this page.

Data Stores

Define global values for multiple signals at different levels of a model

A large model can require individual signals to route to many separate blocks in different locations in the diagram. You can configure a data store to allow access to signal data from anywhere in a model, similar to a global variable in a computer program. However, as with global variables, data stores can reduce model transparency and make model verification more difficult. To decide whether to use a data store, see Data Store Basics.

To route signals across large models, consider using Goto and From blocks instead of data stores.


Data Store Memory Define data store
Data Store Read Read data from data store
Data Store Write Write data to data store


Simulink.SimulationData.DataStoreMemory Container for data store logging information
Simulink.SimulationData.BlockPath Fully specified Simulink block path
Simulink.SimulationData.Dataset Create Simulink.SimulationData.Dataset object


Model Global Data by Creating Data Stores

Explicitly model a separate piece of global memory by creating a data store.

Log Data Stores

Configure a data store for logging so that you can view the data stored in a simulation run.

Data Store Basics

A data store is a repository to which you can write data, and from which you can read data, without having to connect an input or output signal directly to the data store.

Signal Ranges

Fully specify your design and optimize data types and the generated code by specifying the minimum and maximum value that a signal can attain during simulation.

Was this topic helpful?