The modules in the DeltaV system have parameters that are associated with the module, regardless of the algorithm type. You can also create custom module-level parameters, but these are the standard ones. In general, these parameters describe operational aspects of the module. The parameters and their descriptions are:
ABNORM_ACTIVE - Indicates that an event or condition has occurred that is not specified in the MERROR_MASK or the MSTATUS_MASK.
BAD_ACTIVE - Indicates that an event or condition has occurred that is specified in the MERROR_MASK or the MSTATUS_MASK.
BLOCK_ERR - Indicates that an error has occurred in one or more of the blocks in the module. The following table describes the bits in BLOCK_ERR, the bit position for each error, and how to access the bits from DeltaV Operate.
|
Bit value |
Bit position |
Access from DeltaV Operate |
|---|---|---|
|
Out Of Service |
0 |
BLOCK_ERR.F_CV[1] |
|
Power Up |
1 |
BLOCK_ERR.F_CV[2] |
|
Device Needs Maintenance Now |
2 |
BLOCK_ERR.F_CV[3] |
|
Readback Failed |
3 |
BLOCK_ERR.F_CV[4] |
|
Lost Non-Volatile Data |
4 |
BLOCK_ERR.F_CV[5] |
|
Lost Static Data |
5 |
BLOCK_ERR.F_CV[6] |
|
Memory Failure |
6 |
BLOCK_ERR.F_CV[7] |
|
Output Failure |
7 |
BLOCK_ERR.F_CV[8] |
|
Input Failure/Bad PV |
8 |
BLOCK_ERR.F_CV[9] |
|
Device Needs Maintenance Soon |
9 |
BLOCK_ERR.F_CV[10] |
|
Device Fault State Set |
10 |
BLOCK_ERR.F_CV[11] |
|
Local Override |
11 |
BLOCK_ERR.F_CV[12] |
|
Simulate Active |
12 |
BLOCK_ERR.F_CV[13] |
|
Link Configuration Error |
13 |
BLOCK_ERR.F_CV[14] |
|
Configuration Error |
14 |
BLOCK_ERR.F_CV[15] |
|
Other Error |
15 |
BLOCK_ERR.F_CV[16] |
The block error can be set by the assigned fieldbus device. Refer to the device reference manual for specific definition of device generated block errors.
If you put BLOCK_ERR on a display, use the numeric values to determine which errors exist in the module. For example, if the module BLOCK_ERR numeric value is 265, that means that one or more of the blocks in the module has one or more of the following errors:
The sum of 1 + 8 + 256 = 265. Note that you can use the numbers to interpret BLOCK_ERR on individual function blocks as well.
EXEC_TIME - The time it takes to execute the module (the module's start execution time to end execution time). The execution time includes time that is suspended (interruptions during execution) while higher priority activity occurs in the controller. This parameter most accurately reflects the actual duration of execution when the module is running at high priority.
MCOMMAND - Allows users to enable or disable the module by setting the module state to In Service or Out of Service. When a module is Out of Service, execution of the function blocks in the module stops and function block parameter values and status do not change. A parameter's status will not indicate an out of service condition unless the function block containing it was taken out of service before the module.
Out of Service does not affect external references used to read the output of other modules, controllers or devices, into the active module. The external reads continue even in Out of Service mode, but are not processed by the module.
MERROR - Indicates if the module has a problem. The parameter continues to indicate a module error as long as errors are present. When the error condition is no longer present, MERROR returns to a value of zero. The following table describes the bits in MERROR, the bit position for each error, and how to access the bits from DeltaV Operate.
|
Bit value |
Explanation |
Bit position |
Access from DeltaV Operate |
|---|---|---|---|
|
Algorithm Error |
A configuration problem with the algorithm. An example is a calc/logic block with no configured expression. |
2 |
MERROR.F_CV[3] |
|
IO Input Error |
A component block cannot read the I/O. An example is an unconfigured DI function block. |
3 |
MERROR.F_CV[4] |
|
IO Output Error |
A component block cannot write the I/O. An example is an unconfigured ISEL block. |
4 |
MERROR.F_CV[5] |
|
Input Transfer Error |
The value of a wired link is rejected at the destination. For example, a function block input parameter is not updated because the value is wrong for the data type (negative floating point wired to an unsigned integer) or the block rejects the write (setpoint limit is more than 10% outside of PV_SCALE) |
5 |
MERROR.F_CV[6] |
|
Output Transfer Error |
A wired link to an external reference parameter cannot transfer its value to the external reference because it is rejected at the destination. See the example for the Input Transfer Error. from a transfer function block. |
6 |
MERROR.F_CV[7] |
|
Alarm Processing Error |
A configuration error on an alarm definition. |
7 |
MERROR.F_CV[8] |
|
FB Bad Active |
A problem exists in one of the function blocks in this module. That function block will have the BAD_ACTIVE parameter set to True. An example is a DO function block, set to Out of Service mode, with BAD_MASK having Out of Service set true. |
8 |
MERROR.F_CV[9] |
If you put MERROR on a display, use the numeric values to determine which errors exists in the module.
MERROR_MASK - Allows you to determine the fault conditions that cause the BAD_ACTIVE parameter of a module to be True. You must check the condition in MERROR_MASK for that condition to cause BAD_ACTIVE to be True. For example, if MERROR indicates an I/O Input Error, but I/O Input Error is not checked in the MERROR_MASK Properties dialog, the BAD_ACTIVE parameter becomes False if an error occurs and DeltaV Diagnostics does not report the error. If, on the other hand, I/O Input Error is checked in the MERROR_MASK Properties dialog, the BAD_ACTIVE parameter goes to True if the error occurs and DeltaV Diagnostics reports the error. The MERROR events and conditions that are not included in this mask cause the ABNORM_ACTIVE parameter to be True.
MSTATE - Indicates whether the module is executing by displaying the module's current state—either In Service or Out of Service .
MSTATUS - Indicates the current status of the module. When none of the status conditions are present, MSTATUS returns to a value of zero. The following table describes the bits in MSTATUS, the bit position for each error, and how to access the bits from DeltaV Operate.
|
Bit value |
Explanation |
Bit position |
Access from DeltaV Operate |
|---|---|---|---|
|
Component Disabled |
Indicates that one or more component blocks might be disabled or have components disabled. |
0 |
MSTATUS.F_CV[1] |
|
Component Error |
One or more component blocks has detected an error. |
1 |
MSTATUS.F_CV[2] |
|
Out Of Service |
Indicates if the module is out of service. |
2 |
MSTATUS.F_CV[3] |
|
Breakpoint Set |
A user has set a breakpoint in the Debug View that prevents the module from continuously executing. The module stops execution at the breakpoint. |
3 |
MSTATUS.F_CV[4] |
|
Debug View Active |
The Debug View is active, and a user could currently be editing the downloaded module. |
4 |
MSTATUS.F_CV[5] |
|
Value Forced |
A user has set a parameter to a particular value during a Debug View session. The module continues to run using this value until you remove the forced value. |
5 |
MSTATUS.F_CV[6] |
|
Unresolved Reference |
One or more references from this module to other modules are unsatisfied. (Usually, this reference is in an expression.) |
6 |
MSTATUS.F_CV[7] |
|
Not Running |
The module is not executing. |
7 |
MSTATUS.F_CV[8] |
|
FB Abnormal Active |
A problem exists in one of the function blocks in this module. That function block will have the ABNORM_ACTIVE parameter set to True. |
10 |
MSTATUS.F_CV[11] |
If you put MSTATUS on a display, use the numeric values to determine which errors exists in the module.
MSTATUS_MASK - Allows you to determine the fault conditions that cause the BAD_ACTIVE parameter of a module to be True. You must check the condition in MSTATUS_MASK for that condition to cause BAD_ACTIVE to be True. For example, if MSTATUS indicates a Component Error, but Component Error is not checked in the MSTATUS_MASK Properties dialog, the BAD_ACTIVE parameter becomes False if an error occurs and DeltaV Diagnostics does not report the error. If, on the other hand, Component Error is checked in the MSTATUS_MASK Properties dialog, the BAD_ACTIVE parameter goes to True if the error occurs and DeltaV Diagnostics reports the error. The MSTATUS events and conditions that are not included in this mask cause the ABNORM_ACTIVE parameter to be True.
The MERROR_MASK and the MSTATUS_MASK settings related to the BAD_ACTIVE parameter can mask most of the errors (excluding the (LMH)PctOnTime overloading errors) that cause bad OInteg at the Control level in DeltaV Diagnostics. As a result, modules below the Control level can show bad integrity without affecting the integrity of this level or of levels below it. To allow a component error in a module to cause bad OInteg at the Control level, enable the Component Error property on the module's MSTATUS_MASK parameter.
VERSION - Can store any number the user sets it to, unless Version Control is enabled. Then, it displays the version of the object as stored in the Version Control database.
DESC - Module's description parameter. For example, FIC101/DESC.A_CV is the description parameter for FIC101.
IDISP - Faceplate for selected module. For example, FIC101/IDSP.A_CV is the faceplate display for FIC101.
CDISP - Control Display for selected module. For example, FIC101/CDSP.A_CV is the control display for FIC101.
DDSP - Detail Display for selected module. For example, FIC101/DDSP.A_CV is the detail display for FIC101.
Additional module-level parameters exist for the various algorithm types.