Emerson Exchange 365

CIOC Communication failure

A high temp in rack the room caused controller communication failure with CIOC. This resulted many MOD Bad alarms and the PID controllers went into MAN mode. What is the best way to identify all the PID controllers that went to MAN mode? I couldn't find this information in the events log.

Thanks,

Ravi

kravindranath

• 26 Apr 2021 3:40 PM
• Cancel

1 Reply

• Andre Dicaire

  

  • 26 Apr 2021 5:44 PM

  DeltaV Insight monitors abnormal mode as part of its loop monitoring. This is based monitoring the MODE Target and Normal Mode.
  
  If the Block Error sets the Modules BAD_PV alarm, sorting the Alarm list would give you affected Modules that would include PID loops affected by the affected CIOC's. This would also be in the Event
  
  Standard Dynamos and GEMs have an Abnormal MODE status that also monitors this, assuming MAN is not the Normal mode.
  
  DeltaV Diagnostics also provides Integrity information on Assigned Modules, showing the Mstatus and MError of each module. A failed IO would show up in either the MStatus for FB Abnormal, or MError for FB Bad. You can sort on these individual bits to find the modules with a bad IO, and this would include your PID blocks that shed to manual. It's not a direct list of PID blocks on MAN, but inferred from the IO bad status.
  
  Otherwise, an Excel Spread sheet report could be used to read the MODE.TARGET and MODE.ACTUAL for all you PID modules. you will need a list of your modules with PID blocks, which could be created from a bulk export of modules sorted by Sub-Type, maybe.

  Andre Dicaire

  • Cancel