Alarming in modules using function block conditions

Alarms based on propagated errors

You can create a module alarm parameter that becomes active when a function block condition occurs by referencing the module BAD_ACTIVE parameter in the alarm and checking FB Bad Active in MERROR_MASK. This alarm will be active whenever a function block condition occurs whose corresponding condition in BAD_MASK is selected in that function block.

Note

The propagation of function block statuses only works within a single module. You cannot propagate a function block's BAD_ACTIVE or ABNORM_ACTIVE status to a different module (that is, one that does not contain the function block that has the condition).

The module parameter MERROR stores the current run-time value of the error conditions shown in MERROR_MASK for monitoring and display. MERROR is used in the standard DeltaV detail displays.

MSTATUS stores the current run-time value of the error conditions shown in MSTATUS_MASK for monitoring and display. MSTATUS is used in the standard DeltaV detail displays.

Therefore, if you have selected the appropriate options for propagating function block conditions in the MERROR_MASK and MSTATUS_MASK parameters, you can configure alarms at the module level based on the function block status along with other module conditions.

For example, to configure the module parameter BAD_ACTIVE to be set to True (1) when any of its function blocks has the Bad Active condition set to True (1), select the FB Bad Active condition in the module parameter MERROR_MASK.

Before you begin building equipment modules, control modules and unit modules, it is important to evaluate the number, types, and similarity of the modules needed in your control strategy.