Lenze Engineer v2.21 - Manual (Page 168)

Defining the system functionality
Port editor (ports)
168
Lenze · Engineer · 2.13 EN - 10/2014
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
8.11.2.5 Defining the interface and process data object
In the last step of the port definition, specify the interface and, if required, the process data object
to be used:
• In the Interface selection field, only the communication interfaces that exist on the device are
offered.
• When "Automatic" has been selected, the interface and thus the process data object are
selected automatically by the system in the case of an interconnection.
• When an interface has been defined and the selection for the process data object is
"Automatic", the process data object is defined by the system.
• A process data object can serve as a container for several ports. This means that several ports
can be transferred by a process data object.
• The interface can be changed subsequently any time.

Click the Complete button to complete the port definition.

Note!
Ports can be assigned to process data objects automatically or manually. If you define a
port up to the process data object level, the flexibility for automatic connection of
interconnections will be reduced.  Defining the type of connection ( 179)
When the ports are assigned to the process data objects, the data width and existing
mapping entries will not be checked. This will only be done when the project is updated
with the ToolsBuild project menu command. In the case of errors, error messages will
be indicated and the compilation process will be cancelled.