Emerson Exchange 365

Mynah

1:What is the benefit of making a VIM a slave of another VIM & viceversa

2:How to integrate a PLC with Active & Standby units having their respective PRI & SEC redundant networks each with VIM as this will result in to 2 devices being created under VIM with their respective switching IPs. Thus this will double the number of landing modules in DeltaV 

VANSH DEVRAJ

• 21 Sep 2016 5:41 AM
• Cancel

2 Replies

• Tyler Anderson

  

  • 21 Sep 2016 12:30 PM

  Good Morning!
  
  1) Are you talking about a VIM talking to another VIM? Or Redundancy?
  2) This is a pretty extensive topic. If you have the PLC firmware, you can do redundancy with switching IP's. This shows up as Redundant serial cards in DeltaV, so you should not have to double your DST's/landing modules.
  
  I'd give Mynah a call or your local LBP to help walk you through this.
  
  Helpful Links:
  Quick Start guide: www.mynah.com/.../deltav-industrial-ethernet-drivers-quickstart-guide
  EthernetIP Manual: www.mynah.com/.../VIM_EthernetIP.pdf

  • Cancel
• Jake Nichelson

  

  • 21 Sep 2016 1:44 PM

  Vansh,
  
  Regarding your first question:
  From what I've seen, customers have used VIM-to-VIM communication when they want to transfer data between two different DeltaV systems. Say a plant is big enough to have two or more isolated DeltaV control systems but there is some data that you would like to share between the systems. A VIM from DeltaV system A could be used to read/write data from DeltaV system B. Otherwise, I don't see much benefit. In theory, if you wanted to read/write another controller's IO when the controller exists in the same system, you could use each controller's VIM to accomplish it. There should be easier ways to accomplish that instead of using VIMs.
  
  Regarding your second question:
  How to integrate redundant devices will depend largely on what you are communicating to and which VIM firmware you are using - I can't answer this question without knowing these details. However, there appears to be some confusion about what you would expect to see in DeltaV as a result of using redundant VIMs. When using redundant VIMs (if redundancy is supported by your firmware), you will see four sets of redundant serial cards (57-58, 59-60, 61-62, 63-64). VIM A will use cards 57, 59, 61, and 63 and VIM B will use cards 58, 60, 62, and 64. The redundant serial cards will share the same datasets. Say you are reading from Card 57 -> Port 1 -> Device 1 -> Dataset 1 when VIM A is active. If you have a switch over, VIM B will provide the field data to that dataset in place of VIM A. Therefore, you will have redundant serial cards in DeltaV but only need a single landing module because the datasets are shared by the VIMs.
  
  If you have additional questions about the VIMs, feel free to open a support ticket at MYNAH.com - this is the best way to reach us. For more information about MYNAH Support, please see this link: https://www.mynah.com/support

  • Cancel