Main Content

removeInterface

Remove named interface from interface dictionary

Description

example

removeInterface(dictionary,name) removes the interface specified by name from the interface dictionary dictionary.

Examples

collapse all

Create a new model. Add a data interface newInterface to the interface dictionary of the model.

arch = systemcomposer.createModel("archModel");
systemcomposer.openModel("archModel");
addInterface(arch.InterfaceDictionary,"newInterface");

Open the model, then open the Interface Editor. Confirm that an interface newInterface exists.

open(arch)

Remove the interface.

removeInterface(arch.InterfaceDictionary,"newInterface");

View the Interface Editor. Confirm that newInterface is removed.

Input Arguments

collapse all

Data dictionary, specified as a systemcomposer.interface.Dictionary object. For information on how to create a data dictionary, see createDictionary.

Name of interface to be removed, specified as a character vector or string.

Example: "newInterface"

Data Types: char | string

More About

collapse all

Definitions

TermDefinitionApplicationMore Information
interface data dictionary

An interface data dictionary is a consolidated list of interfaces and value types in an architecture and where you use them in the architecture.

You can save local interfaces on a System Composer™ model in an interface data dictionary using the Interface Editor. You can reuse data dictionaries between models that need to use a given set of interfaces, elements, and value types. Data dictionaries that you attach to models 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.

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:

  • Pins or wires in a connector or harness.

  • Messages transmitted across a bus.

  • Data structures shared between components.

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 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
adapter

An adapter connects two components with incompatible port interfaces by mapping between the two interfaces. An adapter can act as a unit delay, rate transition, or merge. 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:

  • Create and edit mappings between input and output interfaces.

  • Apply an interface conversion UnitDelay to break an algebraic loop.

  • Apply an interface conversion RateTransition to reconcile different sample time rates for reference models.

  • Apply an interface conversion Merge to merge two or more message or signal lines.

  • When output interfaces are undefined, you can use input interfaces in bus creation mode to author owned output interfaces.

TermDefinitionApplicationMore Information
physical subsystem

A physical subsystem is 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.

Implement Component Behavior Using Simscape
physical port

A physical port represents a Simscape physical modeling connector port called a Connection Port (Simscape).

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

Define Physical Ports on Component
physical connector

A physical connector can 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.

Architecture Model with Simscape Behavior for a DC Motor
physical interface

A physical interface defines the kind of 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 a Simulink.ConnectionBus object that specifies a number of Simulink.ConnectionElement objects.

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

Specify Physical Interfaces on Ports
physical element

A physical element describes the decomposition of a physical interface. A physical element is equivalent to a Simulink.ConnectionElement object.

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

Describe Component Behavior Using Simscape

Version History

Introduced in R2019a

See Also

Functions

Objects

Blocks

Tools