Main Content

linkToModel

Link component to a model

Description

example

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

collapse all

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

collapse all

Component with no sub-components, specified as a systemcomposer.arch.Component object.

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

Example: 'Robot'

Data Types: char | string

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

Example: 'Model.slx'

Example: 'ProtectedModel.slxp'

Data Types: char | string

Output Arguments

collapse all

Handle to linked model, returned as a numeric value.

Data Types: double

More About

collapse all

Definitions

TermDefinitionApplicationMore Information
architectureA 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
modelA 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 with Interfaces and Requirement Links
componentA 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
portA 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
connectorConnectors 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

TermDefinitionApplicationMore Information
reference componentA 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.
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.
state chartA 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.
sequence diagramA 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.

Introduced in R2019a