There are several ways to get third party data into DeltaV. using different Communication protocol (Modbus,OPC, Ethernet I/P, Profinet etc.)
1. VIM
2. OPC
3. EIOC
For smaller applications (1-6 remote Modbus devices), the DeltaV serial card is more cost effective and only takes up 1 card slot (any open slot). It does Modbus RTU (serial connections) out of the box, and can easily do Modbus TCP/IP (network) when combined with a Modbus protocol converter such as the MESR901 from B&B/Advantech (or numerous other similar products).
Industrial Ethernet :
Industrial Ethernet offers a step up from serial communications, with greater speed, increased capacity, faster response, and peer-to-peer architecture. Unlike Information Technology (IT) Ethernet, Industrial Ethernet utilizes rugged Commercial Off The Shelf (COTS) equipment, often in redundant configuration, for higher reliability in harsh environments. Because it is a switched network with a high bandwidth, Industrial IP has few contention issues.
Higher speed, faster response time, and increased capacity of Industrial Ethernet introduce additional complexity, installation and configuration costs when compared to serial communications. Industrial Ethernet is less deterministic than serial buses originally designed for machine control.
Three open protocols widely used for Industrial Ethernet Local Area Networks (LANs) are Modbus/TCP, Ethernet/IP, and Profinet I/O. The first two are utilized in the lion's share of DeltaV system integrations with PLC based systems. Data rates for these protocols range from 10-100 Mbps.
Modbus/TCP is an Ethernet version of Schneider Electric’s Modbus® protocol. Modbus/TCP is used for nonPLC products, as well as PLC’s.
Ethernet/IP applies the Common Industrial Protocol (CIP) over TCP/IP, and is most often used to integrate Rockwell PLC’s.
Other Industrial Ethernet protocols are available for specific applications, including FOUNDATION™ Fieldbus High Speed Ethernet (HSE) for process control.
Note: Industrial Ethernet is always installed physically and electrically separate from the DeltaV Ethernet based Area Control Network (ACN).
To bring Industrial Ethernet into the DeltaV system, a Virtual I/O Module (VIM) Gateway is installed in either simplex or redundant configuration. This technology is flexible, easy to implement, and allows high speed signaling between PLC controller(s) and a DeltaV controller backplane.
A VIM Gateway provides tight integration, keeps the PLC in operation and makes available new operational capabilities such as the following:
You may combine these DeltaV applications. Another option is to expand DeltaV control functions and utilize any spare PLC I/O capacity. Over 300 VIM implementations are installed and performing well.
The VIM supports 128 datasets, 100 registers per dataset. Scan rate is 100 ms for 16 datasets and 32 IP userconfigurable addresses. An Ethernet interface card fits into the DeltaV rack as does a DeltaV serial interface card, and emulates up to four serial cards. VIM architecture is shown in Figures 3 and 4.
OLE for Process Control (OPC)
OPC provides open connectivity in industrial automation as well as enterprise wide applications, allowing otherwise incompatible equipment to communicate via a common data format. OPC has become an accepted standard for process automation. As such, OPC servers are readily available for many PLC’s.
To implement an OPC interface between a PLC and DeltaV system, you need a PLC OPC server, residing in a PC node on the PLC network (Ethernet LAN), plus a DeltaV OPC Server and DeltaV OPC Mirror. DeltaV OPC Mirror enables data read/write between OPC servers.
DeltaV OPC software runs in a DeltaV Application Station or other workstation with OPC server capability. DeltaV OPC architecture is shown in below figure:
OPC connectivity offers speed, seamless integration with Microsoft and other OLE compliant applications, reduced integration costs because proprietary drivers need not be created, and the ability to talk to a wide range of equipment and devices for which OPC servers have been written.
OPC integration keeps your PLC in operation and supports operations including the following:
Comparison of Serial, Industrial Ethernet and OPC
The following table summarises specifications for serial, Industrial Ethernet and OPC communication protocols.
VIM (Virtual IO Module)
1. The VIM only has an Ethernet port; therefore, it only supports Industrial Ethernet protocols directly (like Modbus TCP/IP). A Modbus TCP/RTU gateway can be used to allow the Modbus TCP/IP VIM to communicate to Modbus RTU devices.
2. The VIMs support Modbus TCP/IP, EtherNet/IP, and PROFINET Industrial Ethernet protocols. A VIM can only support one protocol. A single VIM cannot simultaneously communicate via Modbus TCP/IP and EtherNet/IP for instance. At best you can have two VIMs connected to a single controller where each VIM uses a different protocol.
To integrate a set of Modbus RTU devices to DeltaV below are the options:
Option 1.a: DeltaV Serial Card with Standard Firmware - The DeltaV Serial Card is shipped with Modbus RTU firmware.
Option 1.b: DeltaV Serial Card with Enhanced Modbus RTU firmware - This firmware is developed by MYNAH Technologies. This firmware will allow you to integrate devices that use extended Modbus Addresses (40,000/400,000 for Holding Register ranges for instance).
Option 2: DeltaV Virtual IO Module 2 (VIM2) flashed with Modbus TCP/IP firmware (IOD-4111) in combination with a Modbus RTU/TCP gateway.
Note: The VIM is capable of TCP/IP connections only. There is no way to hook up RS485 directly to a VIM. If you need RS485, you'd need a serial to Ethernet converter to get that data into the VIM (Or directly into a real serial Card.)
Source of Information:
Kommentare