Specify a name for the data store you are defining with this block. Data Store Read and Data Store Write blocks with the same name can read from, and write to, the data store initialized by this block. The name can represent a Data Store Memory block or a sign object defined to be a data store.

Programmatic Use

Rename this data store everywhere the Data Store Read and Data Store Write blocks use it in a model.

Limitations

You cannot use Rename All to rename a data store if you:

You must instead rename the corresponding Simulink.Signal object from Model Explorer. For an example, see Rename Data Store Defined by Signal Object.

List all the Data Store Read and Data Store Write blocks that have the same data store name as the current block, and that are in the current system or in any subsystem below it in the model hierarchy. Clicking a block path displays and highlights that block in your model.

Specify the initial value or values of the data store. The Minimum parameter specifies the minimum value for this parameter, and the Maximum parameter specifies the maximum value.

If you specify a nonscalar value and set Dimensions to -1 (the default), the data store has the same dimensions as the array. Data that you write to the data store (by using Data Store Write blocks) must have these dimensions.

If you set the Dimensions parameter to a value other than -1, the initial value dimensions must match the dimensions that you specify, unless the initial value is a scalar or a MATLAB^® structure. If you specify a scalar, each element of the data store uses the scalar as the initial value. Use this technique to apply the same initial value (the scalar that you specify) to each element without manually matching the dimensions of the initial value with the dimensions of the data store.

To use this block to initialize a nonvirtual bus signal, specify the initial value as a MATLAB structure and set the model configuration parameter Underspecified initialization detection to Simplified. For more information about initializing nonvirtual bus signals using structures, see Specify Initial Conditions for Bus Signals.

Programmatic Use

Specify the minimum value that the block should output. The default value is [] (unspecified). This number must be a finite real double scalar value.

Simulink^® uses the minimum value to perform:

Programmatic Use

Specify the maximum value that the block should output. The default value is [] (unspecified). This number must be a finite real double scalar value.

Simulink uses the maximum value to perform:

Programmatic Use

Specify the output data type. You can set it to:

Click the Show data type assistant button to display the Data Type Assistant, which helps you set the data type attributes. For more information, see Specify Data Types Using Data Type Assistant.

Programmatic Use

Select this parameter to prevent the fixed-point tools from overriding the Output data type you specify on the block. For more information, see Use Lock Output Data Type Setting (Fixed-Point Designer).

Programmatic Use

Dimensions of the data store. The default value, -1, enables you to set the dimensions of the data store by using the Initial value parameter. However, in this case, you cannot use scalar expansion with the initial value. You must specify the initial value by using an array that has the dimensions that you want.

If you use a value other than -1, specify the same dimensions as the dimensions of the Initial value parameter, unless you specify the initial value as a scalar (for scalar expansion) or a MATLAB structure. If the data store represents an array of buses, and if you use a MATLAB structure for the initial value, you can specify dimensions to initialize the array of buses with this structure.

Programmatic Use

Specify that the data store interpret vector initial values as one-dimensional.

By default, MATLAB represents vector data as matrices, which have two dimensions. For example, MATLAB represents the vector [1 2 3] as a 1-by-3 matrix.

When you select this parameter, the data store represents vector data by using only one dimension instead of two. For example, if you specify an initial value of [1 2 3], the data store stores a one-dimensional vector with three elements.

For more information, see Determine the Output Dimensions of Source Blocks.

Programmatic Use

Specify the numeric type, real or complex, of the values in the data store.

Programmatic Use

In a single model reference hierarchy, when you use multiple Model blocks to refer to a model that contains a Data Store Memory block, by default, each instance of the referenced model (each Model block) reads from and writes to a separate copy of the data store. When you select Share across model instances, instead of interacting with a separate copy, all of the instances read from and write to the same data store.

When you set the model configuration parameter Code interface packaging to Reusable function to generate reentrant code from a model (Simulink Coder™), a data store with Share across model instances selected appears in the code as a global symbol that the generated entry-point functions access directly. For example, a global symbol is a global variable or a field of a global structure variable. Therefore, each call that your code makes to the entry-point functions (each instance of the model) shares the data.

For an example, see Share Data Store Between Instances of a Reusable Algorithm. For more information, see Share Data Among Referenced Model Instances.

Programmatic Use

Specify that Simulink software, when compiling the model, searches the model and base workspace for a Simulink.Signal object having the same name, as described in Symbol Resolution. If Simulink does not find such an object, the compilation stops with an error. Otherwise, Simulink compares the attributes of the signal object to the corresponding attributes of the Data Store Memory block. If the block and the object attributes are inconsistent, Simulink halts model compilation and displays an error.

Programmatic Use

Choose a custom storage class package by selecting a signal object class that the target package defines. For example, to apply custom storage classes from the built-in package mpt, select mpt.Signal. Unless you use an ERT-based code generation target with Embedded Coder^® software, custom storage classes do not affect the generated code.

For information about storage classes, see C Code Generation Configuration for Model Interface Elements (Simulink Coder). For information about custom storage classes, see Organize Parameter Data into a Structure by Using Struct Storage Class (Embedded Coder).

Programmatic Use

Applies the storage class or custom storage class that you select from the list. For information about storage classes, see C Code Generation Configuration for Model Interface Elements (Simulink Coder). For information about custom storage classes, see Organize Parameter Data into a Structure by Using Struct Storage Class (Embedded Coder).

Use Signal object class to select custom storage classes from a package other than Simulink.

To programmatically set this parameter, use StateStorageClass or StateSignalObject. See C Code Generation Configuration for Model Interface Elements (Simulink Coder).

Programmatic Use

Specify a storage type qualifier such as const or volatile.

During simulation, the block uses the following values:

For more information, see Data Objects.

Dependencies

To enable this parameter, set Code generation storage class to ExportedGlobal, ImportedExtern, ImportedExternPointer, or Model default. This parameter is hidden unless you previously set its value.

Programmatic Use

Select the diagnostic action to take if the model attempts to read data from a data store to which it has not written data in this time step. See also the Detect read before write diagnostic in the Data Store Memory block section of the Model Configuration Parameters > Diagnostics > Data Validity pane.

Programmatic Use

Select the diagnostic action to take if the model attempts to write data to the data store after previously reading data from it in the current time step. See also the Detect write after read diagnostic in the Data Store Memory block section of the Model Configuration Parameters > Diagnostics > Data Validity pane.

Programmatic Use

Select the diagnostic action to take if the model attempts to write data to the data store twice in succession in the current time step. See also the Detect write after write diagnostic in the Data Store Memory block section of the Model Configuration Parameters > Diagnostics > Data Validity pane.

Programmatic Use

Select this option to save the values of this signal to the MATLAB workspace during simulation. See Signal Logging for details.

Programmatic Use

Use this pair of controls, consisting of a list box and an edit field, to specify the name associated with logged signal data.

Simulink uses the signal name as its logging name by default. To specify a custom logging name, select Custom from the list box and enter the custom name in the adjacent edit field.

Programmatic Use

Discard all but the last N data points, where N is the number that you enter in the adjacent edit field. For more information, see Log Data Stores.

Programmatic Use

Log every Nth data point, where N is the number that you enter in the adjacent edit field. For example, suppose that your model uses a fixed-step solver with a step size of 0.1 s. If you select this option and accept the default decimation value (2), Simulink records data points for this signal at times 0.0, 0.2, 0.4, and so on. For more information, see Log Data Stores.

Programmatic Use