Connect components with different interfaces
The Adapter block allows you to connect the source and destination ports of components that have different interface definitions.
To add or connect System Composer™ components:
Add an Adapter block from the Modeling tab or
the palette. The Adapter block has
Click and drag a port to create a connection. Connect each port to another component. You can also create a new component to complete the connection.
To use an Adapter block:
Insert an Adapter block between two ports with different interfaces. You can create mappings between interface elements on each port.
Double-click the Adapter block to open the Edit Interface
Mappings : Interface Adapter dialog. From here, you can create and edit
mappings between input and output interfaces, and apply interface conversions:
UnitDelay to break an algebraic loop or
RateTransition to reconcile different sample time rates for
reference models. For more information, see Interface Adapter.
When used for structural interface adaptations, the Adapter block uses bus element ports internally and, subsequently, only supports virtual buses.
Source— Input connection from a component
If you connect to a source component, the interfaces on the ports should be compatible.
Destination— Output connection to a component
If you connect to a destination component, the interfaces on the ports should be compatible.
|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: