Add reference to dictionary
Add Referenced Dictionary
Add a data interface
newInterface to the local interface dictionary of the model. Save the local interface dictionary to a shared dictionary as an
arch = systemcomposer.createModel("newModel",true); addInterface(arch.InterfaceDictionary,"newInterface"); saveToDictionary(arch,"TopDictionary") topDictionary = systemcomposer.openDictionary("TopDictionary.sldd");
Create a new dictionary and add it as a reference to the existing dictionary.
refDictionary = systemcomposer.createDictionary("ReferenceDictionary.sldd"); addReference(topDictionary,"ReferenceDictionary.sldd")
dictionary — Data dictionary
Data dictionary, specified as a
systemcomposer.interface.Dictionary object. You can specify the default
data dictionary that defines local interfaces or an external data dictionary that
carries interface definitions. If the model links to multiple data dictionaries, then
dictionary must be the dictionary that carries interface
definitions. For information on how to create a dictionary, see
reference — Referenced dictionary
character vector | string
Referenced dictionary, specified as a character vector or string of the name of the referenced dictionary with the
collisionResolutionOption — Collision resolution option
"Unspecified" (default) |
Collision resolution option if there is a conflict between two interfaces with the same name in the dictionaries, specified as one of the following:
"KeepTop"to keep the interface from the top dictionary and remove the one in the reference dictionary.
"KeepReference"to keep the interface from the reference dictionary and remove the one in the top dictionary.
"Unspecified", which will error if any conflicts exist when creating the reference.
|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.
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: