Link component to model
Save the component named
robotComp in the
Robot.slx and reference it from another component
electricComp so that the component
electricComp uses the architecture of the component
Create a model
model = systemcomposer.createModel("archModel",true); arch = get(model,"Architecture");
Add two components to the model with the names
names = ["electricComp","robotComp"]; comp = addComponent(arch,names);
robotComp in the
Robot.slx model so the
component references the model.
electricComp component to the same model
Robot.slx so it uses the architecture of the original
robotComp component and references the architecture model
Clean up the model.
component — Component
Component with no sub-components, specified as a
modelName — Model or subsystem name
character vector | string
Model or subsystem name for an existing model or subsystem that defines the
architecture or behavior of the component, specified as a character vector or string.
Models or subsystems of the same name prioritize protected models with the
modelFileName — Model or subsystem file name
character vector | string
Model or subsystem file name for an existing model or subsystem that defines the architecture or behavior of the component, specified as a character vector or string.
modelHandle — Handle to linked model or subsystem
Handle to linked model or subsystem, returned as a numeric value.
A System Composer™ architecture represents 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:
You can define parameters on the architecture level using the Parameter Editor.
A System Composer model is the file that contains architectural information, including components, ports, connectors, interfaces, and behaviors.
Perform operations on a model:
A System Composer model is stored as an SLX file.
|Create Architecture Model with Interfaces and Requirement Links|
A component is 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:
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.
There are different types of ports:
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.
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 reuse compositions in the model using reference components. There are three types of reference components:
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 references or architecture references that specify model arguments. You can specify independent values for a parameter on each 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.
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.
Introduced in R2019a