d. Select EtherNet/IP for the target variables which will be read
and write by EtherNet/IP client.
n
Configure communication with ControlLogix controllers
In this case, ControlEdge 900 controller can act as EtherNet/IP
client or EtherNet/IP server.
l If ControlEdge 900 controller acts as an EtherNet/IP client,
ControlEdge Builder provides function blocks to enable
communication between 900 controller and third-party
controllers. For how to configure function blocks, see
"EtherNet/IP" in the ControlEdge Builder Function and
Function Block Configuration Reference.
l If ControlEdge 900 controller acts as an EtherNet/IP server:
a. Bind EtherNet/IP Server to ETH1 or ETH2. Only one port
can be bound at a time.
b. Select EtherNet/IP for variables which will be read and write
by EtherNet/IP client. Do not support variables with user-
defined data types communicating with third-party
controllers.
Configuring OPC UA
ControlEdge 900 controller supports OPC UA server and client which
are built-in protocols in the controller, and it provides an IIoT-ready
open platform that enables users to better leverage data across their
assets.
This chapter introduces how to quickly configure OPC UA Server and
OPC UA client. For more information, see "OPC UA Configuration" in
the ControlEdge Builder Protocol Configuration Reference Guide.
Configuring an OPC UA Server
ControlEdge 900 controller OPC UA Server enables the native OPC
UA client access to information on ControlEdge 900 controller.
Configuring the controller as an OPC UA Server
You must establish the physical address or endpoint that enables OPC
UA client access to OPC UA Server. A maximum of two endpoints can
be defined by binding the ETH1 or ETH2 ports on the ControlEdge
900 controller to OPC UA Server. One or two endpoints are possible
depending on if both ETH1 and ETH2 are bound to OPC UA Server.
94
Chapter 6 - Communication
To Next Page
Loading...
Need help?
General
