linkToModel

Link component to a model

Syntax

modelHandle = linkToModel(component,modelName)

modelHandle = linkToModel(component,modelFileName)

Description

modelHandle = linkToModel(component,modelName) links from the component to a model.

modelHandle = linkToModel(component,modelFileName) links from the component to a model defined by its full file name with an .slx or .slxp extension.

Examples

Reuse Component

Save the component named 'robotComp' in the architecture model Robot.slx and reference it from another component named, 'electricComp' so that the component named 'electricComp' uses the architecture of the component named 'robotComp'.

Create a model 'archModel.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 'robotComp' in the 'Robot.slx'model so the component references the model.

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

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

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

Input Arguments

component — Architecture component

component object

Architecture component with no children, specified as a systemcomposer.arch.Component object.

modelName — Model name

character vector

Model name for an existing model that defines the architecture or behavior of the component, specified as a character vector. Models of the same name prioritize protected models.

Example: 'Robot'

Data Types: char

modelFileName — Model file name

character vector

Model file name for an existing model that defines the architecture or behavior of the component, specified as a character vector.

Example: 'Model.slx'

Example: 'ProtectedModel.slxp'

Data Types: char

Output Arguments

modelHandle — Handle to linked model

numeric value

Handle to linked model, returned as a numeric value.

Data Types: double

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. You can represent specific architectures using alternate views.	Different types of architectures describe different aspects of systems: Functional architecture describes the flow of data in a system. Logical architecture describes the intended operation of a system. Physical architecture describes the platform or hardware in a system.	Compose Architecture Visually
model	A System Composer model is 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. System Composer models are stored as .slx files.	Create an Architecture Model
component	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 architecture 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.	Components
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.	There are different types of ports: 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.	Ports
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.	Connections

Term	Definition	Application	More Information
reference component	A reference component is a component whose definition is a separate architecture model or Simulink® behavior model.	A reference component represents a logical hierarchy of other compositions. You can reuse compositions in the model using reference components.	Implement Component Behavior in Simulink Create a Reference Architecture
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 an architectural component using state machines.	Add Stateflow Chart Behavior to Architecture Component
sequence diagram	A sequence diagram is a behavior diagram that represents the interaction between structural elements of an architecture as a sequence of message exchanges.	You can use sequence diagrams to describe how the parts of a static system interact.	Define Sequence Diagrams Use Sequence Diagrams in the Views Gallery