Emerson Exchange 365

• Not Answered

Flood Suppression Modules - v12 versus v13 & 14 - what all changed?

Matt Stoner  - Any chance you recall what all may have changed in the v13 module templates aside from the content of the CALC block, where alarms are set to OOS as opposed to OPSUP?

I'm thinking I can just cut-and-paste the code from the new templates to the modules created prior to v13. Or would you recommend just deleting them and reconstituting them using the new template?

Thanks,

John

• advanced alarming

John Rezabek

• 16 Apr 2021 1:39 PM
• Cancel

4 Replies

• Victor OBrien

  

  • 16 Apr 2021 3:03 PM

  John,
  I just wanted to say congratulations on the Control Hall of Fame. Well-deserved honor and very impressive. Happy to have you on EE365.

  • Cancel
• Matt Stoner

  

  • 16 Apr 2021 5:01 PM

  Here are the changes I see in v13 vs v12:

  ALM_FLOOD_SUP

  • Configuration Tips updated
  • Code in ALM_SUP_LOGIC changed
  • Code in UNSUPPRESS changed
  • Code in USER_EXPRESSION changed
  • VOTER/STATUS_OPT changed to Vote to Trip if Bad

  ALM_FLOOD_SUP_32

  • Configuration Tips updated
  • MODBAD_ALM suppression timeout changed
  • COMMON_ALM suppression timeout changed
  • Code in ALM_SUP_LOGIC changed
  • Code in UNSUPPRESS changed
  • Code in USER_EXPRESSION changed
  • VOTER/STATUS_OPT changed to Vote to Trip if Bad

  FO_ALM_SUP

  • Configuration Tips updated
  • MODBAD_ALM suppression timeout changed
  • Code in SUPPRESS changed
  • Code in UNSUPPRESS changed
  • Code in USER_EXPRESSION changed

  So if you get all this in your copy and pastes you should be good I think. Make a backup before starting first...

  • Cancel
• John Rezabek

  

  • 17 Apr 2021 3:41 PM

  In reply to Matt Stoner:

  Matt that's more than I thought . . . it's good to remember how "benign" these suppression modules are. That is, they really don't interact with the real-time data and alarm system much until they're triggered. Since our SILalarm database has preserved the logic and affected alarms I think I'll just re-import them using the templates in v14.
  
  Is the practice to create multiple ALM_FLOOD_SUP_32 when there's more than 32 alarms that are no longer informative when a trip is detected? I've thought about adding more variables etc. to ALM_FLOOD_SUP_32 but then I'd have to get clever about the detail displays etc.
  
  Victor thanks for the compliments - all of us end users are fortunate for having the knowledgeable and diligent experts on here (like Matt for example) who take the time for education and advice - in addition to their normal duties; glad I can contribute once in a while!

  • Cancel
• Matt Stoner

  

  • 19 Apr 2021 12:59 PM

  In reply to John Rezabek:

  Got the display work done for you already as the detail will support up to 96 alarms so you just have to follow the naming conventions and put in the logic to suppress the added alarms. Just be aware that you will have to split the logic to fit in expressions and your loading will start to take bigger hits with the more alarms and logic added.

  • Cancel