Emerson Exchange 365

VIM Network switches from active to standby and vice-versa intermittently

Hello experts,

Our Redundant VIM Network switches over from active to standby and vice versa intermittently.

And there's a point in time that both active and standby show red X marks then it goes back to normal.

We have 6 devices all in all but 1 of them is not yet installed. All the 5 are working properly.

Below is our configuration of Redundant Modbus TCP Network.

According to the Modbus TCP User Manual, the switchover can be due to unavailability of one of the device in the active/standby network. In our case, the C59/P01/DEV01 since the device is not yet installed.

Is there any way for the VIM to skip scanning the device that is not yet installed so that it will not switchover to its partner, intermittently?

Or am I missing something here?

Rein

• 13 Dec 2019 8:28 AM
• Cancel

3 Replies

• Mark Millar

  

  • 14 Dec 2019 12:57 AM

  Hi Rein, As far as I know this is unavoidable with a slave that is not talking. You have to remove the configuration from the VIM. We have found that if you leave this for a period of time, you will start to have comm issues and you will have to cycle power on the VIMs to recover them. I hope someone else knows something about this. Our firmware is at 3.10.53.

  • Cancel
• Rein

  

  • 16 Dec 2019 7:31 AM

  In reply to Mark Millar:

  Hello Mark,
  Can I delete C59/P01/DEV01 even if there's DEV02 for the other device?
  What is configured on DEV01 is just the IP definition for the device.
  Or should I leave the configuration of DEV01 empty?

  • Cancel
• Mark Millar

  

  • 30 Dec 2019 12:24 AM

  In reply to Rein:

  Yes, just delete what is causing problems. Doesn't matter what else is on the port. The others will retain their DEV numbers.
  When you get your equipment working, just add the DEV again in VIMnet (VIMNet should add the same number as was deleted previously as long as you didn't add something new), the IP, DeltaV address and description. Upload the VIM. The VIMNet DEV numbers don't have to match the DeltaV DEV numbers but they usually do. As long as the DeltaV DEV number matches the VIMNet DeltaV addess .

  • Cancel