Main Content

linkToModel

Link component to model

所有的页面崩溃

Syntax

modelHandle = linkToModel(component,modelName)
modelHandle = linkToModel(component,modelFileName)

Description

example

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

modelHandle= linkToModel(component,modelFileName)links from the component to a model or subsystem defined by its full file name with anSLXorSLXPextension.

Examples

collapse all

Save the component namedrobotCompin the architecture modelRobot.slxand reference it from another component namedelectricCompso that the componentelectricCompuses the architecture of the componentrobotComp.

Create a modelarchModel.slx.

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

Add two components to the model with the nameselectricCompandrobotComp.

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

SaverobotCompin 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");

Clean up the model.

Simulink.BlockDiagram.arrangeSystem("archModel");

输入参数

collapse all

电脑及相关知识onent with no sub-components, specified as asystemcomposer.arch.Componentobject.

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

Example:"Robot"

Data Types:char|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.

Example:"Model.slx"

Example:"ProtectedModel.slxp"

Data Types:char|string

Output Arguments

collapse all

Handle to linked model or subsystem, returned as a numeric value.

Data Types:double

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.

 电脑及相关知识ose Architecture Visually
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.

 电脑及相关知识onents
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:

  • 电脑及相关知识onent 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.

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

Areference componentis a component whose definition is a separate architecture model, Simulink®行为模型或仿真软件金宝appubsystem 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 references仿真软件金宝app模型。

  • Subsystem referencesare Simulink subsystems.

  • Architecture referencesare System Composer architecture models.
parameter definition

Aparameter definitionis the definition of a property that has instance semantics. A parameter definition specifies attributes such as name, data type, default value, and units.

Parameter definitions can be specified as model arguments on a Simulink model or a System Composer architecture model.

 Access Model Arguments as Parameters on Reference Components
parameter

Aparameteris an instance-specific value of a parameter definition. A parameter captures instance-specific values and units.

Parameters are available for each component linking to a model reference or architecture reference that specifies model arguments. You can specify independent values for a parameter on each component.

 Use Parameters to Store Instance Values with Components
subsystem component

Asubsystem componentis 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 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

See Also

||||||

Topics