Add ports to architecture
Create a model, get the root architecture, add a component, and add a port.
model = systemcomposer.createModel('archModel',true); rootArch = get(model,'Architecture'); newComponent = addComponent(rootArch,'NewComponent'); newPort = addPort(newComponent.Architecture,'NewCompPort','in')
newPort = ArchitecturePort with properties: Parent: [1×1 systemcomposer.arch.Architecture] Name: 'NewCompPort' Direction: Input InterfaceName: '' Interface: [0×0 systemcomposer.interface.SignalInterface] Connectors: [0×0 systemcomposer.arch.Connector] Connected: 0 Model: [1×1 systemcomposer.arch.Model] SimulinkHandle: 52.0001 SimulinkModelHandle: 49.0001 UUID: '98070dc5-1738-4dbf-b9b2-4fc781e7992c' ExternalUID: ''
Architecture, specified as a
ports to the architecture of a component or the root architecture of the model. Use
<component>.Architecture to access the architecture of a
portNames— Names of ports
portTypes— Port types
Port types, specified as a cell array of character vectors or an array of strings. Available port types follow:
stereotypes— Stereotypes to apply to ports
Stereotypes to apply to ports, specified as an array of
systemcomposer.profile.Stereotype objects. Each stereotype in the array must
either be a stereotype that applies to all element types or a port stereotype.
|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:
|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:
System Composer models are stored as SLX files.
|Create an Architecture Model with Interfaces and Requirement Links|
|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:
|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|
|physical subsystem||A physical subsystem is a Simulink® subsystem with Simscape™ connections.||A physical subsystem with Simscape connections uses a physical network approach suited for simulating systems with real physical components and represents a mathematical model.||Describe Component Behavior Using Simscape|
|physical port||A physical port represents a Simscape physical modeling connector port called a Connection Port (Simscape).||Use physical ports to connect components in an architecture model or to enable physical systems in a Simulink subsystem.||Define Physical Ports on a Component|
A physical connector can represent a nondirectional conserving connection of a specific physical domain. Connectors can also represent physical signals.
|Use physical connectors to connect physical components that represent features of a system to simulate mathematically.||Architecture Model with Simscape Behavior for a DC Motor|
A physical interface defines the kind of information that flows through a physical
port. The same interface can be assigned to multiple ports. A physical
interface is a composite interface equivalent to a
|Use a physical interface to bundle physical elements to describe a physical model using at least one physical domain.||Specify Physical Interfaces on the Ports|
A physical element describes the decomposition of a physical interface. A physical
element is equivalent to a
|Define the ||Describe Component Behavior Using Simscape|
|stereotype||A stereotype is a custom extension of the modeling language. Stereotypes provide a mechanism to extend the architecture language elements by adding domain-specific metadata.||Apply stereotypes to elements: root-level architecture, component architecture, connectors, ports, data interfaces, and value types of a model. A model element can have multiple stereotypes. Stereotypes provide model elements with a common set of property fields, such as mass, cost, and power.||Extend Architectural Design Using Stereotypes|
|property||A property is a field in a stereotype. For each element the stereotype is applied to, specific property values are specified.||Use properties to store quantitative characteristics, such as weight or speed, that are associated with a model element. Properties can also be descriptive or represent a status. You can view and edit the properties of each element in the architecture model using the Property Inspector.|
|profile||A profile is a package of stereotypes to create a self-consistent domain of element types.||Author profiles and apply profiles to a model using the Profile Editor. You can store stereotypes for a project in one profile or in several. Profiles are stored in XML files when they are saved.|