Emerson Exchange 365

• Not Answered

VIM2 Communication with Rockwell PLC (Controllogix,Compact llogix) and any Device via EtherNet IP

Hello Everyone

I have the project used the VIM2 to communication with Rocwell PLC (Controllogix , Compactllogix) and any Device via EtherNet IP ( Gas detector and etc)

Details for DeltaV (DeltaV12.3 Version , DeltaV M-Series Hardware, Redundant VIM2 and IOD-4112 Rockwell PLC EtherNet/IP Driver for DeltaV VIM2.)

I already read manual from Mynah for configuration Class3 UCMM (Encapsulated DF1) connection and Class1 (ENBT) connection.

(Ethernet/IP Master Driver for DeltaV Virtual I/O Module for both Simplex and Redundant Ethernet/IP Version 3.3.3x and 3.3.5x, Apirl 2007)

I plan to choose the Class3 UCMM to communication with Rockwell PLC.

 

My question as details below,

1.For the Rockwell PLC, If we do configuration in DeltaV for mapping data to communication via EtherNet IP, PLC should be configuration for mapping data refering data from DeltaV ? ( Refer Mynah Manual)

2.For the Rockwell PLC, If they configuration  Class3 UCMM (Encapsulated DF1, Use Map PLC/SLC message) connection  and datatype is DINT or DINT[#] (DINT array) this datatype can communication with VIM?

3.For any Device Gas detector, They used Ethernet /IP driver and hardware form Field Server, How to configuration to communication with this Device and This device need any license from Mynah?

 

Could everyone to share your idea and your advice to me.

Thank you & Best regards

Suttiporn.

 

 

 

 

 

 

 

Suttiporn

• 24 Oct 2014 2:46 PM
• Cancel

13 Replies

• lazy_engineer

  

  • 24 Oct 2014 3:38 PM

  I have our ControlLogix PLCs communicating with DeltaV via DF1-VIM as you are considering. MYNAH's "Ethernet/IP Master Driver for DeltaV Virtual I/O Module"(which you referred to) is a great resource for getting things started. Section 5 of that manual has pretty good details for the DeltaV config, but as far as a manual for the RSLogix config goes, I have not came across one. I have a lot of run time using this method, and it has shown great reliability. The PLCs receive and return data through the Map PLC/SLC Messages function which maps the VIM Datasets configured in DeltaV Explorer with the "special data 2" field to the "File Number" field for the RSLogix Controller Tags. Ladder logic is used to pass the data back and forth between the PLC's data channels and DeltaV via the Controller Tag arrays.
  
  I believe the DF1 method only supports the usage of INT and Discrete datatypes.
  
  There are no licenses from MYNAH for any connection.

  • Cancel
• Suttiporn

  

  • 25 Oct 2014 2:25 PM

  In reply to lazy_engineer:

  Hello lazy
  
  Thank you, This is a good information.
  
  I will used Class3 UCMM (Encapsulated DF1, Use Map PLC/SLC message) via EtherNet IP connection to communication with Rockwell PLC.
  
  My project used 3 redundant VIM to connecting many package unit.
  
  For datatypes, I believe your suggestion use INT and Real (for Floating datatype).
  
  Best regards
  
  Suttiporn

  • Cancel
• Bill Sayers

  

  • 27 Oct 2014 11:12 AM

  In reply to Suttiporn:

  Another idea could be to use a Red Lion Data Station Plus. It will take the native tags from the Logix processor and convert it what ever protocol you need. I have a project where I am doing this to serial RTU. This way you do not have to get into the PLC and do the Map a PLC/SLC message you just use the Native Tags.

  • Cancel
• Suttiporn

  

  • 27 Oct 2014 2:45 PM

  In reply to lazy_engineer:

  How many files we can Map PLC/SLC messages in RSLogix 5000 Software ?

  EX Refer PLC/SLC Mapping popup

  File Number                        Name

  1                                         INT[20]              Data 1

  2                                         INT[5]                Data 2

  3                                         INT[5]                Data 3                  

  4                                         INT[100]            Data 4

  5                                         INT[100]            Data 5

  These are above data in PLC/SLC Mapping Table popup seperate for Discrete Input , Discrete Output , Analog Input and Analog Output.

  The limitation of data for Mapping PLC / SLC depend on VIM data specification, Am I right for this information ?

  Best regards

  Suttiporn

   

   

   

   

   

   

   

   

   

  • Cancel
• lazy_engineer

  

  • 27 Oct 2014 4:49 PM

  In reply to Suttiporn:

  The RSLogix File Number value can range from 0-999.
  
  Keep in mind while you're developing this strategy that your VIM Datasets can have a maximum of 100 Registers each with a maximum Register Address value of 65535. The File Number is used to pair the VIM Datasets to your Controller Tag.
  
  The VIM can have up to 16 Datasets configured per Port. There are 2 Ports per virtual card and 4 virtual cards per VIM. That works out to 128 Datasets per VIM. In that case your VIM is the limiter, but you can have multiple VIM/Controller pairs on the same network as your PLCs which in theory could allow you to exceed that maximum File Number value of 999.

  • Cancel
• Suttiporn

  

  • 27 Oct 2014 7:26 PM

  In reply to lazy_engineer:

  Hello lazy_engineer

  For my understand, If I have data map like table below.

  EX Refer PLC/SLC Mapping popup

  File Number                        Name

  1                                         INT[20]              Data 1

  2                                         INT[5]                Data 2

  3                                         INT[5]                Data 3                  

  4                                         INT[100]            Data 4

  5                                         INT[100]            Data 5

  We will count the data map to 5 data ( 5 data = 5 dataset in DeltaV), Am I correct ?

  We have 8 - 9 packages link to this VIM.(The packages used minimum 5 data map per each package).

  If we have 9 packages minimum data map = 9 * 5 = 45 data map or 45 Dataset in DeltaV, These data packages are possible link to one VIM (Maximum = 128 Data or 128 Dataset in DeltaV), My understand is correct or not ?.

   If do you have any advice please let us know.

  Thank you

  Suttiporn

   

   

  • Cancel
• lazy_engineer

  

  • 27 Oct 2014 7:50 PM

  In reply to Suttiporn:

  Correct, from your table I observe that you will need 5 Datasets in your VIM configuration for each package. As long as each File Number is unique and within the 0-999 range, you can have all 45 datasets configured to one VIM.

  • Cancel
• Suttiporn

  

  • 27 Oct 2014 10:58 PM

  In reply to lazy_engineer:

  Hello lazy_engineer

  Thank you for all of your answer, These are good information for developing the our project.

  Best regards

  Suttiporn.

   

   

  • Cancel
• lazy_engineer

  

  • 28 Oct 2014 11:56 AM

  In reply to Suttiporn:

  You're welcome. If you have any issues or new questions come up, I'd be happy to help.
  
  Cheers

  • Cancel
• Suttiporn

  

  • 28 Oct 2014 1:53 PM

  In reply to Bill Sayers:

  Hello Bill Sayers
  
  Thank you for your idea.
  
  For future or next project similar this project, We will consider your solution for implement the project.
  
  Best regards
  
  Suttiporn

  • Cancel
• jaym_DA

  

  • 28 Oct 2014 2:17 PM

  In reply to Bill Sayers:

  Bill Sayers,
  Have you used the Red Lion Data Station Plus method before, and if so how well did it work. Interested in learning more about this method.

  • Cancel
• Bill Sayers

  

  • 28 Oct 2014 8:28 PM

  In reply to jaym_DA:

  Just about to implement one. The nice thing about it from what I gather is you don't have to get into the PLC program and do anything. Simply just get a export of the native tags from the PLC program in CSV format and import them into this converter. A lot of OEM's on our end don't either give the PLC program to us or have it locked so you can not edit it. I will keep you up to date how it works out if you would like.

  • Cancel
• Bill Sayers

  

  • 28 Oct 2014 8:33 PM

  In reply to Bill Sayers:

  Another problem we have is in our existing DeltaV cabinets there is never enough room to put a VIM. From what I have read is that it has to go to the left side of the controller and ps and ours is always right next to a wireway. So to put a two wide carrier would take a lot of moving things around.

  • Cancel