Allen-Bradley ProcessLogix 1756-IA16, Reference Manual, Page: 107 / 120

Publication 1757-RM810A-EN-P - May 2002
Functional Blocks 3-67
Execution Status
The status of input fetching is reflected in the Overall Execution Status
(EXECSTS) parameter. EXECSTS provides information on how
successful the block is in fetching the input. EXECSTS can have the
following values:
•
OK - Successful, i.e. when input fetching and the conversion is
done without any error or clamping.
•
CLAMPWARNING - Function completed, but with some
limitation (e.g. value clamped after data conversion). This
provides information on how successful the block is in type
conversion. After fetching good data, if the block has to clamp
the input during type conversion, EXECSTS will be
CLAMPWARNING.
•
BADINPUT - This happens when the connection to the input
block is lost or it is simply bad data.
•
INBLKMISSING – This happens when the block detects that
there is no input connection made to any of the inputs of the
PUSH block.
Store Status
The status of output store is reflected in the Store Status (STORESTS)
parameter. STORESTS provides information on how successful the
block is in storing input. STORESTS can have the following values:
•
STOREOK - Successful, i.e. the store was successful.
•
STOREPENDING – This is an intermediate status when the store
is made to a destination, which is in a peer controller. Until the
block receives a store request, the status is STOREPENDING.
•
STOREFAIL – If the output destination block rejects the store,
the push block displays the STOREFAIL status. The reason for
failure may be block specific. When the store fails, the PUSH
block retries the store immediately in the next execution cycle. If
this store also fails, then the store is not tried for two cycles. This
continues until the time goes to 6 secs. After that the store is not
attempted again until after another 6 seconds. Thus there is
exponential increase in time between any two failed stores. This
is required to save peer-to-peer communication resources
•
DATATYPERR – This is used if the output store could not be
made because of some error in CB where a connection of
parameters between different data types is allowed. This is also
the store status if there is no output connection configured on
the PUSH block.
Spare Allen-Bradley Parts