inlineComponent

Remove reference architecture or behavior from component

Syntax

componentObj = inlineComponent(component,inlineFlag)

Description

componentObj = inlineComponent(component,inlineFlag) retains the contents of the architecture model referenced by the specified component and breaks the link to the reference model. If inlineFlag is set to 0 (false)., then the contents of the architecture model are removed and only interfaces remain. You can also use inlineComponent to remove Stateflow^® chart and Simulink^® behaviors from a component or to remove Simulink model or subsystem behaviors referenced by a component.

Examples

Reuse Component and Remove Architecture Reference

Save the component robotComp in the architecture model Robot.slx and reference it from another component, electricComp, so that the electricComp component uses the architecture of the robotComp component. Remove the architecture reference from the robotComp component so that its architecture can be edited independently.

Create a model archModel.slx.

model = systemcomposer.createModel("archModel");
systemcomposer.openModel("archModel");
arch = get(model,"Architecture");

Add two components to the model electricComp and robotComp. Rearrange the model.

names = ["electricComp","robotComp"];
comp = addComponent(arch,names);
Simulink.BlockDiagram.arrangeSystem("archModel")

Save the robotComp component in the Robot.slx model so the component references the model.

saveAsModel(comp(2),"Robot");

Link the electricComp component to the same model Robot.slx so it uses the architecture of the original robotComp component and references the architecture model Robot.slx.

linkToModel(comp(1),"Robot");

Remove the architecture reference from the robotComp component while retaining the contents, so that its architecture can be edited independently, breaking the link to the referenced model.

inlineComponent(comp(2));

Clean up the model.

Simulink.BlockDiagram.arrangeSystem("archModel"); 

Add Stateflow Behavior to Component and Remove

Add a Stateflow chart behavior to the component named robotComp within the current model. Then, remove the behavior.

Create a model archModel.slx.

model = systemcomposer.createModel("archModel");
systemcomposer.openModel("archModel");
arch = get(model,"Architecture");

Add two components to the model electricComp and robotComp. Rearrange the model.

names = ["electricComp","robotComp"];
comp = addComponent(arch,names);
Simulink.BlockDiagram.arrangeSystem("archModel")

Add Stateflow chart behavior model to the robotComp component.

createStateflowChartBehavior(comp(2));

Remove Stateflow chart behavior from the robotComp component and remove all contents of the Stateflow chart.

inlineComponent(comp(2),false);

Clean up the model.

Simulink.BlockDiagram.arrangeSystem("archModel"); 

Input Arguments

component — Component

component object

Component linked to an architecture model, specified as a systemcomposer.arch.Component object.

inlineFlag — Control of contents of component

1 (true) | 0 (false)

Control of contents of component, specified as 1 (true) or 0 (false).1 (true) if contents of the referenced architecture model are copied to the component architecture and 0 (false). if the contents are not copied and only ports and interfaces are preserved.

Data Types: logical

Output Arguments

componentObj — Component

component object

Component with referenced architecture or behavior removed, returned as a systemcomposer.arch.Component object.

More About

Definitions

Term	Definition	Application	More Information
architecture	A System Composer™ architecture represents a system of components and how they interface with each other structurally and behaviorally.	Different types of architectures describe different aspects of systems. You can use views to visualize a subset of components in an architecture. You can define parameters on the architecture level using the Parameter Editor.	Compose Architectures Visually Author Parameters in System Composer Using Parameter Editor
root	A root is at the top of an architecture hierarchy. A root architecture has a boundary defined by its architecture ports that surround the system of interest.	The root architecture has a system boundary surrounding your architecture model. You can add architecture ports that define interfaces across the boundary.	Compose Architectures Visually
model	A System Composer model is the file that contains architectural information, such as components, ports, connectors, interfaces, and behaviors.	Perform operations on a model: Extract root-level architecture. Apply profiles. Link interface data dictionaries. Generate instances from model architecture. A System Composer model is stored as an SLX file.	Create Architecture Model with Interfaces and Requirement Links
component	A component is a replaceable part of a system that fulfills a clear function in the context of an architecture. A component defines an architectural element, such as a function, another system, hardware, software, or other conceptual entity. A component can also be a subsystem or subfunction.	Represented as a block, a component is a part of an architecture model that can be separated into reusable artifacts. Transfer information between components with: Port interfaces using the Interface Editor Parameters using the Parameter Editor	Compose Architectures Visually
port	A port is a node on a component or architecture that represents a point of interaction with its environment. A port permits the flow of information to and from other components or systems.	Component ports are interaction points on the component to other components. Architecture ports are ports on the boundary of the system, whether the boundary is within a component or the overall architecture model. The root architecture has a boundary defined by its ports.	Compose Architectures Visually
connector	Connectors are lines that provide connections between ports. Connectors describe how information flows between components or architectures.	A connector allows two components to interact without defining the nature of the interaction. Set an interface on a port to define how the components interact.	Compose Architectures Visually

Term	Definition	Application	More Information
reference component	A reference component is a component whose definition is a separate architecture model, Simulink behavior model, or Simulink subsystem behavior. A reference component represents a logical hierarchy of other compositions.	You can synchronize and reuse reference components as Reference Component blocks. There are three types of reference components: Model references are Simulink models. Subsystem references are Simulink subsystems. Architecture references are System Composer architecture models or subsystems.	Implement Component Behavior Using Simulink Create Architecture Reference Reference Component
parameter	A parameter is an instance-specific value of a value type.	Parameters are available for inlined architectures and components. Parameters are also available for components linked to model, subsystem, or architecture references that specify model arguments. You can specify independent values for a parameter on each component.	Author Parameters in System Composer Using Parameter Editor Access Model Arguments as Parameters on Reference Components Use Parameters to Store Instance Values with Components
subsystem component	A subsystem component is a Simulink subsystem that is part of the parent System Composer architecture model.	Add Simulink subsystem behavior to a component to author a subsystem component in System Composer. You cannot synchronize and reuse subsystem components as Reference Component blocks because the component is part of the parent model.	Create Simulink Behavior Using Subsystem Component Create Simulink Subsystem Component
state chart	A state chart diagram demonstrates the state-dependent behavior of a component throughout its state lifecycle and the events that can trigger a transition between states.	Add Stateflow chart behavior to describe a component using state machines. You cannot synchronize and reuse Stateflow chart behaviors as Reference Component blocks because the component is part of the parent model.	Implement Behaviors for Architecture Model Simulation Implement Component Behavior Using Stateflow Charts

Version History

Introduced in R2019a