Functions

Providing an OPC UA server

• Providing all data available and selected on the MOVI-C^® CONTROLLER using the OPC UA communication protocol.
• Connecting a MOVI-C^® CONTROLLER to a third-party component that is an OPC UA client.
• Connecting a third-party component with an OPC UA client to a MOVI-C^® CONTROLLER.
• Provision of structures according to the OPC UA information model in function blocks via the communication manager. The use of methods is currently not supported.

Assigning a name for the MOVI‑C^® CONTROLLER

Freely adjustable name of the MOVI‑C^® CONTROLLER [1], which is used in the symbolic designation of the node ID.

Providing an OPC UA client

Providing an OPC UA client for the MOVI‑C^® CONTROLLER via the data source manager or the MOVIKIT^® Visualization software module. This means that, for example, the following functions are possible:

• Cross communication between two MOVI‑C^® CONTROLLER as an alternative to network variables.
• Connecting an actuator or sensor to the MOVI‑C^® CONTROLLER as an OPC UA server.
• Connecting a visualization (client) to a MOVI‑C^® CONTROLLER (server).

Providing mechanisms for IT security

• Protection via certificates and encryption
• User and password can also be used as OPC UA server
• User group dependent enable of the variables in the symbol configuration

Connecting the DUV40A sensor

Use the MOVIKIT^® OPC UA add-on SensorInterface software module to connect the DUV40A sensor from SEW‑EURODRIVE.