Type Editor

You can create and edit types in multiple external data sources with the Type Editor.

How you create types in the Type Editor depends on whether you open the Type Editor in the context of a model window or as a standalone window.

You can import types from a function, script, or MAT file into the Type Editor.

Use filters to quickly find objects by name or property value.

You can use the Type Editor to modify types in external data sources, such as the base workspace and data dictionaries.

When you create or modify types, save the types for future use. If blocks specify these types, the types are required for simulation.

The Type Editor can save types to a MAT file (.mat), MATLAB function (.m), or data dictionary (.sldd).

Suppose you want to define an interface for a model with a Simulink.Bus object. For this example, the interface receives signals named sine, chirp, constant, pulse, and saw. You want the interface to group all the signals. Within that group, you want the interface to group the sinusoidal and nonsinusoidal signals.

Since R2023b

When you open the Type Editor in the context of a model, the Type Editor displays the types used by a model. The Type Editor helps you find where these types are used in the model by highlighting the corresponding blocks and ports for a selected type.

Open the ComponentBasedModeling project. Optionally, compile the model that opens. To compile the model, on the Modeling tab of the Simulink Toolstrip, click Update Model or Run. Compiling the model updates the line styles, which you can use to visually identify buses.

To view the types that the model uses, on the Modeling tab, in the Design gallery, click Type Editor. Alternatively, press Ctrl+Shift+P.

To expand an external data source, click the arrow next to the data source name.

The top model in the model hierarchy has access to three external data sources:

The controller interface uses Simulink.Bus objects named Controls, Goals, and Sensors.

To display where the model uses a bus object, click the bus object in the Type Editor. For example, click Sensors.

The block diagram highlights the Subsystem block named Controller because the subsystem uses the Sensors bus object.

Double-click the Controller subsystem to open it.

A subsystem has access to the same external data sources as its parent model.

In the Type Editor, click Sensors.

The block diagram highlights two ports because they use the Sensors bus object.

Double-click the Controller model to open it.

The referenced model named ComponentController has access to two external data sources:

The ComponentBasedModelingData dictionary no longer appears in the Type Editor.

In the Type Editor, click Sensors.

The block diagram does not highlight blocks or ports because the top-level bus object does not correspond with a visible block or port in the block diagram.

In the Type Editor, expand Sensors. Then, click one of its elements. For example, click the element named x1.

The block diagram highlights the In Bus Element blocks that select the element named x1 from the Sensors bus object.

Since R2023b

When you open the Type Editor in the context of a model, you can use the Type Editor to assign the selected type to a block.

Open the ComponentBasedModeling project. Optionally, compile the model that opens. To compile the model, on the Modeling tab of the Simulink Toolstrip, click Update Model or Run. Compiling the model updates the line styles, which you can use to visually identify buses.

To open the Type Editor, on the Modeling tab, in the Design gallery, click Type Editor. Alternatively, press Ctrl+Shift+P. To expand an external data source, click the arrow next to the data source name.

Suppose you want to define the interface that provides the sensor data in the top model. You can use the Simulink.Bus object named Sensors to define this interface.

In the Type Editor, click Sensors.

The sensor port of the Subsystem block named Plant provides the sensor data, but the port is not highlighted because it does not use the Sensors bus object.

On the Subsystem block named Plant, select the sensor port.

In the Type Editor, right-click Sensors. Then, select Assign type to selected blocks and ports.

The sensor port is now highlighted because it uses the Sensors bus object.

Double-click the Subsystem block named Plant.

Two Out Bus Element blocks correspond with the sensor port.

Double-click either of these Out Bus Element blocks.

The Out Bus Element blocks that create the sensor interface are now defined by the Sensors bus object.

You can use the Type Editor to create MATLAB structures for initialization.

MyData_MATLABStruct = struct;
MyData_MATLABStruct.temperature = int16(0);
MyData_MATLABStruct.pressure = struct;
MyData_MATLABStruct.pressure(1).s1 = 0;
MyData_MATLABStruct.pressure(1).s2 = 0;
MyData_MATLABStruct.pressure(2).s1 = 0;
MyData_MATLABStruct.pressure(2).s2 = 0;
MyData_MATLABStruct.pressure(3).s1 = 0;
MyData_MATLABStruct.pressure(3).s2 = 0;