Fuji Electric OPC-PRT, Инструкция по эксплуатации

Страница: 56 / 116

55
9.2 EtherNet/IP
9.2.1 Overview
EtherNet/IP is a network adaptation of ODVA’s Common Industrial Protocol (CIP). The card supports the
EtherNet/IP server protocol, including the CSP server variant.
The interface card supports both implicit (class 1 I/O) and explicit (UCMM and class 3) messaging. Class
1 connections support two different types of I/O messaging. One type is the generic I/O assembly
instances 100 and 150, which are entirely user-configurable (refer to section 9.2.5). The other type is the
AC/DC drive profile assembly instances 20 & 70 or 21 & 71, which require no user configuration (refer to
section 9.2.6). With I/O messaging, the data field contains only real-time I/O data. The meaning of the
data is pre-defined at the time the connection is established. I/O messages are short and have low
overhead, and therefore minimizes the processing time and allows for the time-critical performance.
With explicit messaging (refer to section 9.2.7), nodes must interpret each message, execute the
requested task and generate responses. These types of messages can be used to transmit
configuration, control and monitor data.
The following sections demonstrate specific examples of how to use EtherNet/IP to transfer data
between the inverter and Allen-Bradley Logix-brand PLCs.
Some other notes of interest are:
• The interface card supports the EtherNet/IP protocol, as administered by the Open DeviceNet
Vendor Association (ODVA).
• This product has been self-tested and found to comply with ODVA EtherNet/IP Conformance Test
Software Version CT-13.
•
The interface card’s product type code is 2 (AC Drive).
•
The EDS file can be obtained from the included CD-ROM or downloaded from the product web
page on the internet.
• Supports DLR (Device Level Ring) node.
•
Supports unconnected messages (UCMM), and up to 16 simultaneous class 1 (I/O) or class 3
(explicit) connections.
• Class 1 implicit I/O supports both multicast and point-to-point (unicast) when producing data in the
T
→
O direction.
• Point-to-point class 1 connected messages will be produced targeting the IP address of the device
that instantiated the connection, UDP port 0x08AE (UDP port 2222).
• If a class 1 point-to-point connection is established in the (T → O) direction, no more class 1
connections can be established.
•
If a class 1 connection’s consuming half (O
→
T) times out, then the producing half (T
→
O) will also
time-out and will stop producing.
• If a class 1 or class 3 connection timeout (communication loss) occurs, the driver can be
configured to perform a timeout action. For class 1 connections, the timeout value is dictated by
the scanner/client and is at least four times the RPI (Requested Packet Interval). For class 3
connections, the timeout value is also dictated by the scanner/client, but is typically a much larger
value than for class 1 connections.
9.2.2 Server Settings
In the studio, navigate to OPC-PRT…Ethernet…EtherNet/IP Server .
Device Name
The device name is used for identification of a device on the EtherNet/IP network. This string is
accessible as the “product name” attribute of the identity object. Enter a string between 1 and 32
characters in length.
DLR
Device Level Ring is a ring redundancy protocol. All devices in a DLR ring must support DLR.
•
If the checkbox is cleared (default setting), the interface card will not operate correctly in a DLR
ring. By disabling this option, the interface card should not be installed in a DLR ring.
• If the checkbox is checked, the interface card can participate and will operate correctly in a DLR
ring. By enabling this option, the interface card can be installed successfully in a DLR ring.