Emerson Exchange 365

• Not Answered

How To Extract List of Activated Interlocks From DeltaV

Hello, 

Our interlocks are configured in DCS with a condition block (CND)---->Boolean Fan Input (BFI)-----> final element (trip valve, motor, etc.).

I would like to view in either Event Chronicle or excel Spread Sheet when a CND block for all modules is evaluted true. I am trying to provide a list for when any interlock on the system is activated to view monthly or daily. 

Thank you for the help in advance.

DCS Newbie

• 27 Oct 2014 1:36 PM
• Cancel

20 Replies

• DCS Newbie

  

  • 27 Oct 2014 9:15 PM

  In reply to Matt Stoner:

  Thank you Matt, 

  I will respond to your detail message. Thank you. 

  I set up the Alarm as shown above in your example. However, I can not see BFI1/FIRST_OUT in event chronicle. I assummed the BFI1/FIRST_OUT value will be displayed so I can see what condition caused the trip at that instant. 

  Thank you

  • Cancel
• DCS Newbie

  

  • 27 Oct 2014 9:37 PM

  In reply to Youssef.El-Bahtimy:

  Youssef,
  
  How do I add alarm limit column to the event chronicle?
  
  Thanks

  • Cancel
• gamella

  

  • 28 Oct 2014 7:33 AM

  In reply to Matt Stoner:

  Related to BFI behavior, I've noticed that FIRST_OUT has BAD status just afted download even if status of IN_D[x] parameters is GOOD and a RESET_D activation is required to set FIRST_OUT status good. If FIRST_OUT is used in logic this must be takenk into account.
  In this situation, does anyone know a workaroud other than adding some code to specially manage first scan cycle after download??
  
  Regards.

  • Cancel
• Youssef.El-Bahtimy

  

  • 28 Oct 2014 12:59 PM

  In reply to gamella:

  If you have logic referencing (any) parameter that is critical for operation, it is important to evaluate the status and availability of the data as part of the decision making process. Downloads can be disruptive, by definition, so you need to decide how long a bad status or unreadable parameter can be tolerated before taking downstream action. Condition blocks have ERROR_OPT and ALGO_OPT parameters for handling of parameter read errors, for instance. In calc block expressions where a numerical value is evaluated, it is also advised to check .ST >=128. Question is, what action do you take for a momentary vs. persistent bad status?
  
  For the specific problem of the BFI, have you tried setting RESET_IN to True in the configuration and downloading? First execution should process the reset and hopefully clear the status, but I haven't tested this.

  • Cancel
• Youssef.El-Bahtimy

  

  • 28 Oct 2014 1:09 PM

  In reply to DCS Newbie:

  Take a look at the PID_LOOP module template in the AnalogControl folder that comes with DeltaV.

  The configuration of LO_ALM, for example, shows that the Alarm Message (DESC2 in Event Chronicle) will be "Low Alarm Value %P1 Limit %P2"

  

  where Message Parameter 1 (P1) is  PID1/PV and Parameter 2 is PID1/LO_LIM.  (The alarmed value and the limit, respectively).

  The message format is configured in the Low Alarm definition within the Alarm Types in DeltaV Explorer System Configuration-->Setup-->Alarm Types.

  If you were to create your own Alarm type based on the new requirements, you would define the alarm message structure in the Alarm Type definition.  Reference that alarm type in your strategy, and configure the reference parameters for the value and limit for the instances accordingly. 

  • Cancel