Emerson Exchange 365

• Not Answered

NEW CIOC Commission

first issue:

I commissioned and flashed a new CIOC to the newest firmware.  I then downloaded the CIOC with no problems. Every node on my control network showed blue triangle in deltaV explorer when the CIOC was downloaded.  I downloaded changed setup data on the proplus and still all blue triangles.  I went ahead and downladed and assigned 1 CHARM on the new CIOC to a controller on the network.  As soon as the CHARM was downloaded, my controller alarm came up on every operator station saying UOC10 (that's the controller name) (Failed Alarm: Cannot communicate with CIOC24-2 (which is the name of my new CIOC)).  I changed the CHARM to undefined and downloaded it and the controller alarm went away.

---I was informed that I need to download changed setup data on the entire control network in order to update the node list table.  Is this the case?

second issue:

  The CIOC shows bad communication and then a few seconds later it shows "good".  this pattern is repeated every few minutes. I currently have no secondary power to the CIOC, only primary power (waiting on shutdown to access the UPS circuit breaker panel to add a circuit). I dont think the power issue would cause this, but I am open to suggestions

we have DeltaV version 13.3.1

Any help would be appreciated.

Thanks,

Pat

Petrisky

• 21 Sep 2021 3:14 PM
• Cancel

4 Replies

• Andre Dicaire

  

  • 21 Sep 2021 6:33 PM

  The DeltaV system downloads a table of nodes to all nodes, which provides each node with the assigned IP addresses and MAC addresses of all nodes. When you add a node like a CIOC, Controller etc, the Download Changed Setup data will download the device table to the nodes in question. That will resolve the blue triangle and will provide the information to the controller so that it can communicate with the newly assigned CIOC.
  
  The lack of secondary power to the CIOC will likely show as an integrity issue, but would not be the cause of a Bad Communication. I would download the changed set up data first. This will not disrupt any communications or control actions. Then download your CHARM to create a reference for the controller to receive IO from that CIOC.
  
  You can also look at the Condition Summary via diagnostics context menu on the CIOC for more details on any integrity issues.

  Andre Dicaire

  • Cancel
• Petrisky

  

  • 21 Sep 2021 7:11 PM

  In reply to Andre Dicaire:

  I downloaded the controller. I did not download the entire control network. I will try that now.

  • Cancel
• Jason.Brumfield

  

  • 8 Dec 2021 9:39 PM

  In reply to Petrisky:

  You also need to make sure the primary and secondary network connections are correct and not crossed somewhere.

  • Cancel
• David-m.walker

  

  • 14 Dec 2021 9:44 AM

  In reply to Jason.Brumfield:

  There is a KBA (NK-2000-0379) "CIOC With Configured Charms Intermittently Lose Communication on
  Primary/Secondary DeltaV Network"
  
  It's not a comprehensive KBA but could be the issue you are seeing.
  
  Dave.

  • Cancel