Get object for named interface in interface dictionary
Add Data Interface and Get Data Interface
Add a data interface
'newInterface' to the
interface dictionary of the model. Obtain the data interface object. Confirm by opening
the Interface Editor.
arch = systemcomposer.createModel('newModel',true); addInterface(arch.InterfaceDictionary,'newInterface'); interface = getInterface(arch.InterfaceDictionary,'newInterface')
interface = DataInterface with properties: Owner: [1×1 systemcomposer.interface.Dictionary] Name: 'newInterface' Elements: [0×0 systemcomposer.interface.DataElement] Model: [1×1 systemcomposer.arch.Model] UUID: '205cdd2f-12bc-4bbb-a4a7-75d0ab18adb8' ExternalUID: ''
Add Physical Interface and Get Physical Interface
Add a physical interface
'newInterface' to the
interface dictionary of the model. Obtain the physical interface object. Confirm by
opening the Interface Editor.
arch = systemcomposer.createModel('newModel',true); addPhysicalInterface(arch.InterfaceDictionary,'newInterface'); interface = getInterface(arch.InterfaceDictionary,'newInterface')
interface = PhysicalInterface with properties: Owner: [1×1 systemcomposer.interface.Dictionary] Name: 'newInterface' Elements: [0×0 systemcomposer.interface.PhysicalElement] Model: [1×1 systemcomposer.arch.Model] UUID: '6110207d-2d6d-470e-9bf5-f0e6f6914685' ExternalUID: ''
dictionary — Data dictionary
Data dictionary, specified as a
systemcomposer.interface.Dictionary object. This is the data dictionary
attached to the model. It could be the local dictionary of the model or an external data
name — Name of interface
character vector | string
Name of interface, specified as a character vector or string.
|interface data dictionary||An interface data dictionary is a consolidated list of all the interfaces and value types in an architecture and where they are used.|
Local interfaces on a System Composer™ model can be saved in an interface data dictionary using the Interface Editor.
Interface dictionaries can be reused between models that need to use a given set of interfaces, elements, and value types. Data dictionaries are stored in separate SLDD files.
|data interface||A data interface defines the kind of information that flows through a port. The same interface can be assigned to multiple ports. A data interface can be composite, meaning that it can include data elements that describe the properties of an interface signal.||Data interfaces represent the information that is shared through a connector and enters or exits a component through a port. Use the Interface Editor to create and manage data interfaces and data elements and store them in an interface data dictionary for reuse between models.||Create an Architecture Model with Interfaces and Requirement Links|
|data element||A data element describes a portion of an interface, such as a communication message, a calculated or measured parameter, or other decomposition of that interface.|
Data interfaces are decomposed into data elements:
|value type||A value type can be used as a port interface to define the atomic piece of data that flows through that port and has a top-level type, dimension, unit, complexity, minimum, maximum, and description.||You can also assign the type of data elements in data interfaces to value types. Add value types to data dictionaries using the Interface Editor so that you can reuse the value types as interfaces or data elements.||Create Value Types as Interfaces|
|owned interface||An owned interface is a locally defined interface that is local to a specific port and not shared in a data dictionary or the model dictionary.||Create an owned interface to represent a value type or data interface that is local to a port.||Define Owned Interfaces Local to Ports|
|adapter||An adapter helps connect two components with incompatible port interfaces by mapping between the two interfaces. An adapter can also act as a unit delay or rate transition. Use the Adapter block to implement an adapter.|
With an adapter, you can perform functions on the Interface Adapter dialog:
|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|