Reinitialize Function

Execute subsystem on model or subsystem reinitialize event

Since R2022a

• 

Libraries:
Simulink / User-Defined Functions

Description

The Reinitialize Function block is a preconfigured Subsystem block that executes on a model or subsystem reinitialize event. By default, the Reinitialize Function block includes:

• An Event Listener block with the Event type set to Reinitialize and the Event name set to reinit

• A Constant block with the Constant value set to 0

• A State Writer block with no State owner block set

Customize the Reinitialize Function block by, for example, replacing the Constant block with source blocks that generate the state value for the State Writer block and specifying a State owner block for the State Writer block.

To generate a model reinitialize event, send a function-call signal to a reinitialize port of a Model block that references a model that contains a Reinitialize Function block. To generate a subsystem reinitialize event, send a function-call signal to a reinitialize port of a Subsystem block that contains a Reinitialize Function block. The reinitialize event has these effects:

1. The state of each block in the model or subsystem reverts back to its initial condition, including blocks within subsystems or referenced models inside the model or subsystem receiving the reinitialize event.

2. The contents of the Reinitialize Function block corresponding to the reinitialize port are executed.

3. If any subsystems or referenced models inside the model or subsystem receiving the reinitialize event contain a Reinitialize Function block, and the Event name of that block matches the Event name of the Reinitialize Function block corresponding to the reinitialize port, then the contents of those Reinitialize Function blocks are executed.

If a Simulink^® based state in a Stateflow^® chart contains a Reinitialize Function block, to generate a subsystem reinitialize event for the state, use a transition event with this syntax:

{StateName.ReinitializeEventName()}

Conditionally executed subsystems with output ports are fully supported within Reinitialize Function blocks.

A model or subsystem can have multiple Reinitialize Function blocks with each block having a different Event name. Each of these reinitialize events appears in the generated code as a different function. Set the Event name in the block dialog of the Event Listener block. The Event Name appears on the Reinitialize Function block icon, and as the port label for the reinitialize port corresponding to the reinitialize event.

You can select an Initialize Function, Reinitialize Function, Reset Function, or Terminate Function block or a corresponding state owner block to highlight blocks related to it. To show a related block in an open diagram or new tab, pause on the ellipsis that appears after selection. Then, select Related Blocks from the action bar. When multiple blocks correspond to the selected block, a list of related blocks opens. You can filter the list of related blocks by entering a search term in the text box. After you select a related block from the list, window focus goes to the open diagram or new tab that shows the related block.

Examples

Working with the Reinitialize Function Block

Use a Reinitialize Function block to reset the initial condition of a Discrete-Time Integrator block for every function-call event received by a subsystem. In this example, the Reinitialize Function block is inside a subsystem, and the subsystem receives a function-call event at every five simulation time steps.

Open Live Script

Limitations

• If a referenced model or subsystem contains more than one Reinitialize Function block, the function-call signals driving all reinitialize ports of the Model or Subsystem block must have a common source.

• Only these blocks can have reinitialize ports:

  • Model

  • Atomic Subsystem

  • Enabled Subsystem

  • Triggered Subsystem

  • Enabled and Triggered Subsystem

  • Message Triggered Subsystem

  • Message Polling Subsystem

  • Function-Call Subsystem

  • If Action Subsystem

  • Switch Case Action Subsystem

  • For Iterator Subsystem

  • While Iterator Subsystem

• For a list of unsupported blocks and features, see Initialize, Reinitialize, Reset, and Terminate Function Limitations.

Block Characteristics

Data Types	Booleana | busa | doublea | enumerateda | fixed pointa | halfa | integera | singlea | stringa
Direct Feedthrough	no
Multidimensional Signals	yesa
Variable-Size Signals	no
Zero-Crossing Detection	no
a Actual data type or capability support depends on block implementation.

Extended Capabilities

C/C++ Code Generation

Generate C and C++ code using Simulink® Coder™.

Actual code generation support depends on block implementation.

Fixed-Point Conversion

Design and simulate fixed-point systems using Fixed-Point Designer™.

Actual data type support depends on block implementation.

Version History

Introduced in R2022a