Recent Services Discussions
Similar Posts
Writing Value to Third party PLC
Difference between Input or Output Parameter and Internal Read or Write parameter
Using The Output Register for read & write (For Modbus TCP over ethernet) with PK controller.
How can I configure a HART parameter on a wireless 848T to read battery voltage
How to get the Data from Allen Bradley 20-Comm-E to EIOC?
Share

EIOC configuration to read/write data to AB PLC (ControlLogix)

Hi all,

I'm working with some OEM skid vendors for the purposes of integrating their skids into a Delta V installation.  I will have a series of AB ControlLogix processors connected to my Delta V installation using EIOC modules.  I have not worked with an EIOC module before, so I'm wondering how the configuration/mapping works between the systems.  If I have the OEM vendors package the read/write tags that I need to interact with via the EIOC into a UDDT (User-defined Data Type) structure in RSLogix 5000, does the EIOC allow me to work directly with the UDDT?  Are there limitations and configuration restrictions that I need to be aware of?

I have searched for the answer and through documentation but I have not been able to find the answer.  I have purchased a development system to test out this functionality, but it is months away from arrival and I would like to know the answer sooner.

Hoping someone out there has done this work already...

Thanks.

EC

Ekhchow
  • harshad.deshmukh
    User defined data type ( UDDT) is not supported on EIOC. In case of Ethernet I/P you can choose 'UCMM with Logix tags' as a messaging class on EIOC logical device and put the Logix tag name which is same as a PLC controller tag name. You can also select the appropriate data type and number of values as per the definition in the PLC. Please limit the definition of the array length in the PLC to 100 as logical device supports only 100 values.
  • Ekhchow

    In reply to harshad.deshmukh:

    Thank you for the response. So I am free to map to arrays of any of the standard controller data types? DINT, Reals, Bools, Strings (and arrays of each of these assuming they are sized of no more than 100 elements)?
  • harshad.deshmukh

    In reply to Ekhchow:

    The supported data types I can see on the logic device are: Boolean , 8 Bit Signed Integer, 8 Bit Unsigned Integer, 16 bit Unsigned Integer, 32 bit signed integer, 32 bit unsigned integer and floating point ( real ). String is not supported. I hope this is in line with the application requirement. If you have specific requirement please let me know.
  • Ekhchow

    In reply to harshad.deshmukh:

    Thanks Harshad. We'll run with this information and verify when we get our test system set up. Much appreciated.
  • Ekhchow

    In reply to Ekhchow:

    One more thing on the topic of UDDTs - I understanding that it cannot take in a UDDT in its own format, but would it be possible to still map the supported data types (bools, dints, reals etc.) directly into the corresponding sub-datatype in the PLC? For example, if my "PLC_Comms" UDDT contains INT_WORD[3], and REAL_VAL[5], could I still map directly to PLC_Comms.REAL_VAL[0] for array length 5? That would let me still structure it into a UDDT structure on the PLC side (for uniformity's sake).

    Hope the question is clear. Thanks again.
    Ed

  • harshad.deshmukh

    In reply to Ekhchow:

    Hi, I am unable to check with the actual Ethernet I/O card at this moment as it is not available with us right now. The controller tag with user defined data type has got the subtype within e.g. the controller tag name is EIOC_TEST with user defined data type with definition of Boolean sub type within this UDDT. Try using 'EIOC_TEST.Boolean ' in EIOC logical device configuration with messaging class 'UCMM with logix tags'. I could not confirm this right now but as I understand you are soon expecting the actual EIOC hence you can try this.

    I would still recommend to organize the controller tags in PLC in such a manner that you will end up in defining the minimum number of logical devices in DeltaV as you need one DST license per logical device. Hence if you plan accordingly you can save a lot on DST licensing. e.g. if you define the controller tags in PLC specifically for communicating with DeltaV then the advantage is you can easily identify these tags and you can organize the data coming and going from PLC to DeltaV in more effective manner. I hope this makes sense.
  • Ekhchow

    In reply to harshad.deshmukh:

    Yes, if I can map directly into the UDDT subtype, I would still keep all the DINTs in a single array so that Delta V could read it all in one block. Same idea for reals etc. Thanks again for the input.
    Ed

This is the official online community site of the Emerson Global Users Exchange, a forum for the free exchange of non-proprietary information among the global user community of all Emerson Automation Solution's products and services. Our goal is to improve the efficiency and use of automation systems and solutions employed at members’ facilities by sharing our knowledge, experiences, and application information.

User Groups | World Areas | Community Guidelines | Legal Information | Privacy Policy | Contact Community Manager

Website translation provided by Website Translator

© 2015-2022 Emerson Global Users Exchange. All rights reserved.