Aphysical subsystemis 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.

Aphysical portrepresents a Simscape physical modeling connector port called aConnection Port(Simscape).

Use physical ports to connect components in an architecture model or to enable physical systems in a Simulink subsystem.

Aphysical connectorcan 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.

Aphysical interface定义了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 aSimulink.ConnectionBusobject that specifies any number ofSimulink.ConnectionElementobjects.

Use a physical interface to bundle physical elements to describe a physical model using at least one physical domain.

Aphysical element描述了物理interfac分解e. A physical element is equivalent to aSimulink.ConnectionElementobject.

Define theTypeof a physical element as a physical domain to enable use of that domain in a physical model.

Aninterface data dictionaryis 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 theInterface 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.

Adata interface定义了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 theInterface Editorto create and manage data interfaces and data elements and store them in an interface data dictionary for reuse between models.

Adata elementdescribes 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:

Avalue typecan 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 theInterface Editorso that you can reuse the value types as interfaces or data elements.

Anowned interfaceis 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.

Anadapterhelps 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 theAdapterblock to implement an adapter.

With an adapter, you can perform functions on theInterface Adapterdialog: