Emerson Exchange 365

Delta V EIOC - Micro 870 PLC(Rockwell) Data communication settings.

Hi All,

We are trying to interface  Micro 870 PLC with delta V DCS EIOC(firmware rev: 13.3.0.5788) controller via ethernet. There are 4 options in delta V EIOC Ethernet comms. We tried ‘UCMM for logix tags’ Option and ‘Explicit messaging with PCCC’ Option, but with no avail. I presume 'UCMM for logix tags'option is suitable for control logix/compactlogix PLCs and 'Explicit with PCCC' option is suitable for Micrologix PLCs. Delta V EIOC is able to see the Micro 870 PLC, but not able to communicate.

 The only option we are left with are ‘Class1 Implicit messaging’ and ‘class 3 explicit messaging’.

I am not sure of the communication settings to be configured for both types. It would be helpful if someone can shed light on the following parameters

For class 1 implicit messaging:

Input assembly Instance ,Output assembly Instance, Configuration Assembly Instance

For class 3 explicit messaging:

 Class ID, Instance ID, attribute ID

In terms of communication, we need 12 INTs to be sent across to the Micro 870 PLC and 4 INTs to be received from Micro 870 PLC. Every tag in Micro 870 has been set as global variables, so CIP enabled device can communicate to the tags we need.

Regards,

Akash

• EIOC
• micro

Akash KA

• 17 Nov 2020 10:05 AM
• Cancel

6 Replies

• pmhamilton

  

  • 17 Nov 2020 1:26 PM

  The ‘UCMM for logix tags’ Option should work, but only for atomic datatypes and arrays of the atomic datatypes. see p61
  literature.rockwellautomation.com/.../2080-um002_-en-e.pdf
  
  CIP Symbolic Client/Server can read/write SINT, INT, DINT, LINT and REAL data types using “CIP Data Table Read”
  and “CIP Data Table Write” message types.
  
  What is the error code? Are you sure the path is correct? In this case the path is simply the IP address e.g. there is no routing to the backplane, slot 0, and etc.
  
  It also support Modbus TCP/IP so that might be your second option.

  • Cancel
• Akash KA

  

  • 17 Nov 2020 11:26 PM

  In reply to pmhamilton:

  Thanks pmhamilton. Yeah we initially used 'UCMM For logix tags' option by giving ip address of PLC, Rack number -1, slot number-0 . However, delta V diagnostic showed logical device problem. Delta V EIOC was able to see the micro 870 PLC via IP Address, but not able to communicate. We verified it by looking at the delta V diagnostics- it showed '1 logical device connected'

  • Cancel
• pmhamilton

  

  • 18 Nov 2020 3:31 AM

  In reply to Akash KA:

  Try UCMM with Rack 0 and Slot 0. I don't think the Micro800 has the Rack and Slot because the EtherNet/IP is embedded. I know ControlLogix 5580 aso has an embedded EtherNet/IP port where you would just specify the IP address, but they also allow the Rack 1, Slot 0 for legacy support. I don't know if the Rack 1, Slot 0 is valid for the Micro800? The CIP error codes are standard so you I would hope the EIOC makes them visible for troubleshooting?

  • Cancel
• Andre Dicaire

  

  • 18 Nov 2020 5:04 PM

  In reply to pmhamilton:

  On the UCMM addressing, the EIOC configuration dialog assumes an Ethernet card in a Rack with the CPU collocated. The "RACK = 1" tells the card to go to the Back plane and "Slot = 0" to find the CPU (in slot 0). For a Micro800 with embedded Ethernet/IP Port, pmhamilton suggestion is the best. As for CIP error codes, I don't think they are passed up to DeltaV diagnostics and a Wireshark packet capture is best way to troubleshoot communications.

  Andre Dicaire

  • Cancel
• Akash KA

  

  • 18 Nov 2020 10:27 PM

  In reply to Andre Dicaire:

  Yeah pmhamilton and Andre Dicaire, Thanks for your suggestions. I tried giving the rack as 0 and slot as 0, but getting the same 'Logical device problem' error. when we changed slot to 1, it was showing 'no device connected', which means DeltaV EIOC is able to see the device at slot 0. I tried keeping the slot number as 0 and rack numbers as 0,1,2,3,4,5 but getting the same 'logical device problem' error. Is there any way to check CIP error codes? Also, is there anything that can be done extended addressing -Hop port number, Hop address, Hop rack number , hop slotnumber?

  • Cancel
• Akash KA

  

  • 18 Nov 2020 10:28 PM

  In reply to Akash KA:

  Adding to that, EIOC is connected to Micro 870 PLC via ethernet switch

  • Cancel