Emerson Exchange 365

• Not Answered

DeltaV-to-DeltaV EIOC communication setup via EtherNet/IP

I have 2 separate DeltaV systems that need some limited transfer of signals to happen between them.  We investigated Intra-Zone Servers, but the cost was too prohibitive.  We do, however, have an EIOC installed for each system, configured for EtherNet/IP.

We connected the 2 systems together via a network of switches and fiber.  The problem we're seeing is we haven't the foggiest how to set up a DeltaV-to-DeltaV transfer in the software.  We have examples of Rockwell ControlLogix PLC communications and other ancillary systems, but none of those has been able to fully prepare us for this task.

For our discussion, let's call the 2 DeltaV systems SYSTEM_A and SYSTEM_B.

Each system has a configured EIOC.  Let's call them EIOC_A and EIOC_B.  Both have P01 configured for EtherNet/IP Protocol (Port 44818).

The IP addresses (like it really matters, but I'll include them for the discussion) are as follows:

EIOC_A/P01: 192.168.200.11
EIOC_B/P01: 192.168.200.21
Subnet Mask for both: 255.255.255.0
No redundancy on either.

I configured a new device for both:

EIOC_A/P01/DELTAV_B_EIOC (Configured with IP 192.168.200.21)
EIOC_B/P01/DELTAV_A_EIOC (Configured with IP 192.168.200.11)

This was all pretty straightforward.  The problem I have is creating logical devices and signals and linking them to the signals/modules in the remote EIOC.  This is where it all falls apart and I have no idea how to proceed.

What Messaging Class is best for communicating with DeltaV?

Once the ideal logical device is configured, how do I create a signal to link to the other EIOC?  I assume I will need some sort of landing module that references this signal, but so far, any combination I have tried has not worked correctly.

Has anyone configured or even come across anything like this?

I am still working with both Emerson and our Impact Partner, so if we come across a solution outside of this forum, I'll try to post it for all to benefit.

• EIOC
• Ethernet/IP

James Suisse

• 1 Apr 2019 12:57 PM
• Cancel

3 Replies

• DBacker

  

  • 1 Apr 2019 7:18 PM

  The EIOC is only a Modbus master so I don't know how you would setup two EIOCs to communicate with each other.
  For performance testing, I've connected the Modbus Server (the slave) on a PK controller to an EIOC (the Modbus Client, the master).

  • Cancel
• Matt Forbis

  

  • 3 Apr 2019 9:27 PM

  As far as I am aware, the EIOC with ethernet IP can only be a scanner and not an adapter. This is similiar to the modus limitation denis describes with master only. I had a similiar situation trying to communicate between different DeltaV systems and after experimenting for a while, we decided the best plan was to use VIM's with modbus to accomplish what we needed. Hope this helps.

  • Cancel
• Steve Linehan

  

  • 4 Apr 2019 12:19 PM

  In reply to DBacker:

  There are a number of commercially available protocol converters. These are relatively cheap and easy to configure. These can handle multiple protocols but can also do two modbus masters. System A writes a value (Push as master) to a holding reg in the device and System B reads (Pull as master) from the same register. Do a quick web search on "connecting two modbus masters". I have successfully used these in the past. I have not done this with an EIOC but it should be the same principle.

  • Cancel