You can use tag elements (such as "Tag1", "Tag1.Field") and tag element items (such as "Tag1.Field.Q") in Cicode expressions. However, by default, when a tag element or an element item is not accessible, or the element quality is not "Good", graphic objects will indicate that state by displaying some error messages or dithering.
|
UNINTENDED EQUIPMENT OPERATION If you change the value of this parameter to 1, no dithering or background color will visually identify that an element is not Good or is not accessible, even if the parameters to display such an identifier have been set elsewhere. In such a case the operator may operate the plant inappropriately by relying on incorrect data. Use the QualityIsOverride() Cicode function or similar method to identify if a tag element has been overridden. Failure to follow these instructions can result in death, serious injury, or equipment damage. |
However, you have the option to disable the default behaviour and to display values even when the element quality is not "Good". This option is controlled by the IgnoreValueQuality Cicode task context attribute, which provides equivalent functionality to [Page] ComBreak, which is now obsolete .
Allowable Values:
0 - The Control Client supports the existing behaviour (#COM) except dithering (dots) will be not shown on text objects when an error is indicated by #<Error Message> (refer to table of errors below).
1 - The quality of tag subscriptions will be completely ignored. This is equivalent to having previously used the (now obsolete) [Page] ComBreak = 0. The numeric or text objects will display a "bad" quality value and animation will continue. No dithering will be shown.
2 - The text or numeric objects will display "bad" quality values. The background color of the text / numeric objects will change to indicate the quality status. The background colors for QUAL_BAD and QUAL_UNCR are defined by [Page]BadTextBackgroundColor and [Page]UncertainTextBackgroundColor citect.ini parameters.
If [Page]IgnoreValueQuality=0 the following short error messages may be displayed on graphical pages when the Quality of a tag is 'NOT GOOD'. Refer to the Cicode Programming Reference -> Cicode and General Errors section for more information.
ERROR |
ERROR Number | Parameter Set | |
---|---|---|---|
ShowUncertainText=0, |
(Default) ShowUncertainText=1, |
||
CT_ERROR_GENIE_NOT_ASS CT_ERROR_TRANSPARENT_NOT_ASS |
323 324 |
#ASS | #ASS |
CT_ERROR_ZERO_DIVIDE | 273 | #DIV/0 | #DIV/0 |
CT_ERROR_STACK_OVERFLOW | 295 | #STACK | #STACK |
CT_ERROR_OUT_OF_MEMORY | 272 | #MEM | #MEM |
CT_ERROR_FORMAT_OVERFLOW | 344 | #OVR | #OVR |
GENERIC_UNIT_REMOTE | 32 | #WAIT | #WAIT |
CT_ERROR_SUBSCRIPTION_PENDING CT_ERROR_PROPERTY_NOT_READY |
423 432 |
#PEND | #PEND |
GENERIC_TAG_UNKNOWN CT_ERROR_TAG_NOT_FOUND CT_ERROR_NO_CLUSTER_SPECIFIED CT_ERROR_CLUSTER_NOT_FOUND CT_ERROR_CLUSTER_COLLISION CT_ERROR_CLUSTER_NOT_CONNECTED CT_ERROR_CLUSTER_NO_SERVER CT_ERROR_NO_CONNECTOR CT_ERROR_NO_SERVER |
53 424 402 403 404 405 418 425 281 |
#COM | #COM |
CT_ERROR_NO_ERROR | 0 | #OK | #BAD/#UNC |
CT_ERROR_OUT_OF_RANGE | 257 | #RANGE | #BAD/#UNC |
CT_ERROR_UNCERTAIN_LAST_USABLE | 525 | #COM | #BAD/#UNC |
Any other < CT_ERROR_SOFTWARE | 256 | #COM | #BAD/#UNC |
Any other >= CT_ERROR_SOFTWARE | 256 | #ERR | #BAD/#UNC |
Default Value: 0
You can override the IgnoreValueQuality setting for a particular page by using the Ignore Quality field on the Page Properties dialog in Graphics Builder.
Note: The quality of tags referenced by items, ex. Tag1.v or Tag1.Field.t, is GOOD and its timestamps are 0 (INVALID TIMESTAMP). Therefore they give no visual indication of quality, error or change in handling state such as control inhibit or override mode regardless of the setting used for the [Page] IgnoreValueQuality parameter.
See Also