Get object for element
Get Object for Named Data Element
Add a data interface
newInterface to the interface
dictionary of the model. Add a data element
newElement with data type
double. Then, get the object for the data element.
arch = systemcomposer.createModel("newModel",true); interface = addInterface(arch.InterfaceDictionary,"newInterface"); addElement(interface,"newElement",DataType="double"); element = getElement(interface,"newElement")
element = DataElement with properties: Interface: [1×1 systemcomposer.interface.DataInterface] Name: 'newElement' Type: [1×1 systemcomposer.ValueType] UUID: '2d267175-33c2-43a9-be41-a1be2774a3cf' ExternalUID: ''
Get Object for Named Physical Element
Add a physical interface
newInterface to the
interface dictionary of the model. Add a physical element
with domain type
electrical.electrical. Then, get the object for the
arch = systemcomposer.createModel("newModel",true); interface = addPhysicalInterface(arch.InterfaceDictionary,"newInterface"); addElement(interface,"newElement",Type="electrical.electrical"); element = getElement(interface,"newElement")
element = PhysicalElement with properties: Name: 'newElement' Type: [1×1 systemcomposer.interface.PhysicalDomain] Interface: [1×1 systemcomposer.interface.PhysicalInterface] UUID: '25b71628-e904-451a-96ff-f185c5ec60a4' ExternalUID: ''
interface — Interface
data interface object | physical interface object | service interface object
Interface, specified as a
name — Element name
character vector | string
Element name, specified as a character vector or string. An element name must be a valid MATLAB® variable name.
element — Element
data element object | physical element object | function element object
Element, returned as a
|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. You can reuse interface dictionaries between models that need to use a given set of interfaces, elements, and value types. Linked data dictionaries are stored in separate SLDD files.
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.
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:
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|
An owned interface is an 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|
An adapter helps connect two components with incompatible port interfaces by mapping between the two interfaces. An adapter can act as a unit delay or rate transition. You can also use an adapter for bus creation. Use the Adapter block to implement an adapter.
With an adapter, you can perform functions on the Interface Adapter dialog box:
Introduced in R2019a