Emerson Exchange 365

Primary Cascade Port Powered on-Fiber Optic IOP

Hi all,

Recently started getting a few errors in our plant while commissioning. Some alarms are coming in related to the "Primary Cascade Port" being powered on, but not used for some of our CIOCs. All the ones with alarms coming in are fiber IOPs.

I managed to get rid of one by decommissioning a panel and recommissioning, but I can't decommission some of these panels because there is process running through their IO.

What would cause a fiber IOP to think it even has a cascade port? I checked the properties of the CIOC and everything is configured correctly.

How can I clear these errors without removing  the panels from operation?

Thanks!

RM.severs

• 10 May 2015 12:28 AM
• Cancel

8 Replies

• Matt

  

  • 5 Jan 2016 5:07 PM

  To follow up, we are still experiencing these errors on three of our CIOC panels that use fiber I/O Ports (Cascade not enabled in properties).
  
  Errors are as follows:
  
  1
  - Standby Secondary I/O Port Error
  - Standby Primary I/O Port Error
  - Primary Commissioning Module Error
  - Primary Cascade Port Error
  - Secondary Commissioning Module Error
  - Secondary Cascade Port Error
  
  2&3
  - Primary Cascade Port powered on but not used
  
  
  Could this be a potential hardware issue in the fiber I/O Port or the CIOC Carrier to make it think it has a copper I/O port with cascade capability? Or would it strictly be a commissioning error that would be resolved by decommissioning and commissioning again?

  Edit: These CIOC panels were shop tested using a copper I/O Port, decommissioned and commissioned again at site using the fiber I/O port if that has any relevance.
  
  
  Thanks for any input.
  
  -Matt

  • Cancel
• MPHymel

  

  • 5 Jan 2016 7:43 PM

  For what its worth, we are experiencing the same problem. This CIOC primary and secondary is Software Rev 12.3.1 Build 5229xr; Hardware Rev 8.11.

  • Cancel
• MPHymel

  

  • 6 Jan 2016 2:54 PM

  In reply to MPHymel:

  FYI, we just received instructions from Emerson on clearing this alarm. From the CIOC properties dialog, under the General tab, enable both Primary and Secondary Cascade ports, download changed setup data, then disable both, and download changed setup data again. Seems a fix will come out at some future software revision, so in the mean time we can manage these when they arise.

  • Cancel
• Rachelle McWright

  

  • 6 Jan 2016 3:04 PM

  In reply to MPHymel:

  Thanks so much for sharing this information with the EE365 community, MPHymel.

  Best Regards,

  Rachelle McWright: Business Development Manager, Dynamic Simulation: U.S. Gulf Coast

  • Cancel
• Dewey Kuchle

  

  • 6 Jan 2016 3:13 PM

  In reply to MPHymel:

  Hi MPHymel, glad to see you got this sorted. I'm just curious to know if you may have used a similar procedure to Matt leading to these error messages arising? Matt mentioned that he completed FAT in the panel shop with copper IOPs but then switched to fiber IOP's when he got to the plant. If you don't change the config to reflect this then discrepancy is going to cause errors. Just wondering if your procedure was similar to Matt's or you ended up with this issue by some other route. Haven't had a chance to test it in my own system yet but glad to see that a "download changed setup data" fixed things without a process disruption. That's how it ought to be.

  • Cancel
• MPHymel

  

  • 6 Jan 2016 3:20 PM

  In reply to Dewey Kuchle:

  I don't think this was the case, as we installed about a dozen new CIOCs in this building during an upgrade. We did have this happen on another CIOC more recently on a different project, and it is possible that it was used for testing. We will be installing another 40 CIOCs in 2016, so we may see another come up and we'll try to note any differences with any having the same issue.

  • Cancel
• Dewey Kuchle

  

  • 6 Jan 2016 3:23 PM

  In reply to MPHymel:

  Thanks for the quick reply. Keep us posted as you add more CIOCs, it'll be interesting to hear what you learn as you expand.

  • Cancel
• Matt

  

  • 7 Jan 2016 3:30 PM

  In reply to MPHymel:

  Thanks for sharing that MPHymel. Enabling and disabling the cascade ports successfully cleared the "Primary Cascade Port powered on but not used" maintenance alarm on two of our panels. However, we still have the errors listed below on one panel. I suspect the fix will not be something that can be done online but will keep digging for a possible solution.
  
  - Standby Secondary I/O Port Error
  - Standby Primary I/O Port Error
  - Primary Commissioning Module Error
  - Primary Cascade Port Error
  - Secondary Commissioning Module Error
  - Secondary Cascade Port Error
  
  
  -Matt

  • Cancel