Main Content

inlineComponent

Remove reference architecture or behavior from component

Description

example

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

Examples

collapse all

Save the componentrobotCompin the architecture modelRobot.slxand reference it from another component,electricComp, so that theelectricCompcomponent uses the architecture of therobotCompcomponent. Remove the architecture reference from therobotCompcomponent so that its architecture can be edited independently.

Create a modelarchModel.slx.

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

Add two components to the model with the names"electricComp"and"robotComp".

names = ["electricComp","robotComp"]; comp = addComponent(arch,names);

Save therobotCompcomponent in theRobot.slxmodel so the component references the model.

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

Link theelectricCompcomponent to the same modelRobot.slxso it uses the architecture of the originalrobotCompcomponent and references the architecture modelRobot.slx.

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

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

inlineComponent(comp(2),true);

Clean up the model.

Simulink.BlockDiagram.arrangeSystem("archModel");

Add a Stateflow chart behavior to the component namedrobotCompwithin the current model. Then, remove the behavior.

Create a modelarchModel.slx.

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

Add two components to the model with the names"electricComp"and"robotComp".

names = ["electricComp","robotComp"]; comp = addComponent(arch,names);

Add Stateflow chart behavior model to therobotCompcomponent.

createStateflowChartBehavior(comp(2));

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

inlineComponent(comp(2),false);

Clean up the model.

Simulink.BlockDiagram.arrangeSystem("archModel");

Input Arguments

collapse all

Component linked to an architecture model, specified as asystemcomposer.arch.Componentobject.

Control of contents of component, specified as a logical 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

collapse all

Component with referenced architecture or behavior removed, returned as asystemcomposer.arch.Componentobject.

More About

collapse all

Definitions

Term Definition Application More Information
architecture

A System Composer™architecturerepresents a system of components and how they interface with each other structurally and behaviorally. You can represent specific architectures using alternate views.

Different types of architectures describe different aspects of systems:

  • Functional architecturedescribes the flow of data in a system.

  • Logical architecturedescribes the intended operation of a system.

  • Physical architecturedescribes the platform or hardware in a system.

You can define parameters on the architecture level using theParameter Editor.

model

A System Composermodelis the file that contains architectural information, including components, ports, connectors, interfaces, and behaviors.

Perform operations on a model:

  • Extract the root-level architecture contained in the model.

  • 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

Acomponentis a nontrivial, nearly independent, and 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, a 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:

Components
port

Aportis 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.

There are different types of ports:

  • Component portsare interaction points on the component to other components.

  • Architecture portsare ports on the boundary of the system, whether the boundary is within a component or the overall architecture model.

Ports
connector

Connectorsare lines that provide connections between ports. Connectors describe how information flows between components or architectures.

一个连接器允许两个组件进行交互out defining the nature of the interaction. Set an interface on a port to define how the components interact.

Connections

Term Definition Application More Information
reference component

Areference componentis 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 reuse compositions in the model using reference components. There are three types of reference components:

  • Model referencesare Simulink models.

  • Subsystem referencesare Simulink subsystems.

  • Architecture referencesare System Composer architecture models.

parameter

Aparameteris 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 references or architecture references that specify model arguments. You can specify independent values for a parameter on each component.

subsystem component

Asubsystem component苏是一个模万博1manbetx型bsystem 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 asReference Componentblocks because the component is part of the parent model.

state chart

Astate chartdiagram 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 asReference Componentblocks because the component is part of the parent model.

Version History

Introduced in R2019a