isProtected

R2026b

Determine component reference model is protected

Syntax

flag = isProtected(compObj)

Description

flag = isProtected(compObj) determines whether or not the referenced model on the component is protected. Both published and protected models are saved with an SLXP extension. This function returns true only for protected models.

Examples

Find If Component Reference Model Is Protected

Find whether or not the referenced model on the component is protected.

Create a new System Composer™ model and add a new component.

model = systemcomposer.createModel("archModel");
rootArch = get(model,"Architecture");
newComponent = addComponent(rootArch,"newComponent");

Create new Simulink^® referenced model and save.

newRef = new_system("newReference","Model");
save_system(newRef);

Protect the Simulink model reference.

Simulink.ModelReference.protect(newRef);

Link the Simulink model to the component newComponent.

linkToModel(newComponent,"newReference.slxp");

Verify that the referenced model linked to the component is protected.

flag = isProtected(newComponent)

flag =

  logical

   1

Input Arguments

compObj — Component

component object | variant component object

Component, specified as a systemcomposer.arch.Component or systemcomposer.arch.VariantComponent object.

Output Arguments

flag — Whether referenced model on component is protected

1 (true) | 0 (false)

Whether referenced model on component is protected, returned as 1 (true) or 0 (false).

Data Types: logical

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.	Different types of architectures describe different aspects of systems. You can use views to visualize a subset of components in an architecture. You can define parameters on the architecture level using the Parameter Editor.	Compose Architectures Visually Author Parameters in System Composer Using Parameter Editor
Root	A root is at the top of an architecture hierarchy. A root architecture has a boundary defined by its architecture ports that surround the system of interest.	The root architecture has a system boundary surrounding your architecture model. You can add architecture ports that define interfaces across the boundary.	Compose Architectures Visually
Model	A System Composer model is the file that contains architectural information, such as components, ports, connectors, interfaces, and behaviors.	Perform operations on a model including extracting root-level architecture, applying profiles, linking interface data dictionaries, or generating instances from model architecture. A System Composer model is stored as an SLX file.	Create Architecture Model with Interfaces and Requirement Links
Component	A component is a 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, another 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 using port interfaces and parameters. Port interfaces and parameters can be configured using the Interface Editor and the Parameter Editor.	Compose Architectures Visually Component
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.	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. The root architecture has a boundary defined by its ports.	Compose Architectures Visually Port
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.	Compose Architectures Visually

Term	Definition	Application	More Information
Reference component	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 synchronize and reuse reference components as Reference Component blocks. Model references are Simulink models. FMU components are components that link to Functional Mockup Unit (FMU) files. Subsystem references are Simulink subsystems. Architecture references are System Composer architecture models or subsystems.	Implement Component Behavior Using Simulink Create Architecture Reference Reference Component
Parameter	A parameter is an instance-specific value of a value type.	Parameters are available for architectures and components that are part of the architecture model. Parameters are also available for components linked to model, subsystem, or architecture references that specify model arguments. You can specify independent values for a parameter on each component.	Author Parameters in System Composer Using Parameter Editor Access Model Arguments as Parameters on Reference Components Use Parameters to Store Instance Values with 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.	Create Simulink Behavior Using Subsystem Component Create Simulink Subsystem Component
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 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.	Implement Behaviors for Architecture Model Simulation Implement Component Behavior Using Stateflow Charts

Version History

Introduced in R2021b