Create named data interface in interface dictionary
Create a data dictionary, then add a data interface named
dictionary = systemcomposer.createDictionary('new_dictionary.sldd'); interface = addInterface(dictionary,'newInterface')
Create a new model and link the data dictionary. Then, open the Interface Editor to view the new interface.
arch = systemcomposer.createModel('newModel',true); linkDictionary(arch,'new_dictionary.sldd');
Create a dictionary, create a Simulink bus object, populate the bus object with two elements, and add the named data interface that mirrors the Simulink bus object to the dictionary.
dictionary = systemcomposer.createDictionary('new_dictionary.sldd'); % Create the Simulink bus object and populate it with elements busObj = Simulink.Bus; elems(1) = Simulink.BusElement; elems(1).Name = 'element_1'; elems(2) = Simulink.BusElement; elems(2).Name = 'element_2'; busObj.Elements = elems; interface = addInterface(dictionary,'newInterface','SimulinkBus',busObj);
Create a new model, link the data dictionary, and open the Interface Editor.
arch = systemcomposer.createModel('newModel',1); linkDictionary(arch,'new_dictionary.sldd');
dictionary— Data dictionary attached to architecture model
Data dictionary attached to architecture model, 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
name— Name of new data interface
Name of new data interface, specified as a character vector or string. This name must be a valid MATLAB® identifier.
busObject— Simulink bus object that new data interface mirrors
Simulink bus object that new data interface mirrors, specified as a Simulink bus object.
|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: