Find if component is referenced to another model
Find If Component Is Reference
Find whether or not the component is a reference to another model.
This component is not a reference.
model = systemcomposer.createModel("archModel",true); rootArch = get(model,"Architecture"); newComponent = addComponent(rootArch,"newComponent"); flag = isReference(newComponent)
flag = logical 0
This component is a reference.
model = systemcomposer.createModel("archModel",true); rootArch = get(model,"Architecture"); newComponent = addComponent(rootArch,"newComponent"); createSimulinkBehavior(newComponent,"newModel"); flag = isReference(newComponent)
flag = logical 1
flag — Whether component is reference
true or 1 |
false or 0
Whether component is reference, returned as a logical.
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:
|Compose Architecture Visually|
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.
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 definition is 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|
A parameter is 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|
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.