DeltaV SIS Module - Level Parameters

Download as pdf or txt
Download as pdf or txt
You are on page 1of 1

SIS Module-Level Parameters: DeltaV BOL 9.

http://www.easydeltav.com/bol/mergedprojects/SISMasterBOL/merge...

SIS Module-Level Parameters


All SIS modules have a common set of parameters. You can create parameters, but the following are the standard ones and cannot be deleted. In general, these parameters describe operational aspects of the module. The parameters and their descriptions are: VERSION - Displays the version of the object as stored in the Version Control database, if Version Control is enabled. Otherwise, stores any integer you set it to. EXEC_TIME - The time (in microseconds) it takes to execute the module. SIF_ERRORS - This parameter replaces the parameter MERROR found in other module types. Some of the bits from MERROR are retained in SIF_ERRORS. The following table describes the bits in SIF_ERRORS, the bit position for each error, and how to access the bits from DeltaV Operate. Bit Value Bit Position Access from DeltaV Operate

'Memory Failure' or 'Config Error' bit set in BLOCK_ERR in a Calc/Logic block An input block or parameter reference has Bad status on its output An output block or secure parameter has Bad status on its output 'Failed to Confirm Following a Command to Trip' bit set in DO_ALERTS in an output block 'Fault State Active' bit set in BLOCK_ERR in output block A wired block input is not able to update due to write-check fail or error on source read 'Output Failure' bit set in BLOCK_ERR in a Calc/Logic block A parameter path is unresolved Module not executing at configured scan rate The last partial stroke test failed

0 1 2 3 4 5 6 7 8 9

SIF_ERRORS.F_CV[1] SIF_ERRORS.F_CV[2] SIF_ERRORS.F_CV[3] SIF_ERRORS.F_CV[4] SIF_ERRORS.F_CV[5] SIF_ERRORS.F_CV[6] SIF_ERRORS.F_CV[7] SIF_ERRORS.F_CV[8] SIF_ERRORS.F_CV[9] SIF_ERRORS.F_CV[10]

SIF_ALERTS - This parameter replaces the parameter MSTATUS found in other module types. The following describes the bits in SIF_ALERTS, the bit position for each alert, and how to access the bits from DeltaV Operate. Typically the bits roll up from conditions detected during function block execution. Bit Value Bit Position Access from DeltaV Operate

A wired input to a block or secure parameter is being forced in Debug An AVTR or DVTR block has a bypassed input An AVTR or DVTR block has an active startup override A bypass or startup override is about to expire in an AVTR or DVTR block Trip consensus in an AVTR or DVTR block Pre-trip consensus in an AVTR or DVTR block Deviation limit exceeded in an AVTR or MID block A CEM block has a non-zero FIRST_OUT A CEM block Effect is being forced A DO or DVC block is in an Off state Debug View Active

0 1 2 3 4 5 6 7 8 9 12

SIF_ALERTS.F_CV[1] SIF_ALERTS.F_CV[2] SIF_ALERTS.F_CV[3] SIF_ALERTS.F_CV[4] SIF_ALERTS.F_CV[5] SIF_ALERTS.F_CV[6] SIF_ALERTS.F_CV[7] SIF_ALERTS.F_CV[8] SIF_ALERTS.F_CV[9] SIF_ALERTS.F_CV[10] SIF_ALERTS.F_CV[13]

1 de 1

12/8/2008 10:47

You might also like