|
<< Click to Display Table of Contents >>
xfDiscreteInfo |
Discrete variables. It may contain as child objects the xoScadaSource- and xoOperatorSource-type objects, in addition to AlarmSource-type objects.
Properties of the xfDiscreteInfo object
Property |
Data Type |
Description |
|---|---|---|
ActiveSource |
Enumeration |
Active source. Possible values for this property are 0: stActiveSource (default), 1: stScada, 2: stOperator, or 3: stCCLink (simulation) |
DiscreteType |
Text |
Free text indicating the sub-type of a Discrete Measurement |
EnableHistorian |
Boolean |
Indicates to Elipse Plant Manager whether this object's data must be stored or not |
Hidden |
Boolean |
Displays this object or not on the Faceplate Screen or on other user-specific Screens |
Boolean |
Indicates whether this object represents more than the values 0 (zero), 1 (one), 2 (two), or 3 (three). If True, users must use an xoScadaSource-type object to indicate each one of these Statuses |
|
Quality |
Number |
Quality, in OPC standard |
RawMask |
Variant |
When the MultiState property is set to True, users must link to this property the raw value verified by xoScadaSource-type objects to retrieve the active condition |
StateColor |
Color |
Color indicating the current status |
StateText0 |
Text |
Text when the current value is equal to 0 (zero) or False |
StateText1 |
Text |
Text when the current value is equal to 1 (one) or True |
StateText2 |
Text |
Text when the current value is equal to 2 (two) |
StateText3 |
Text |
Text when the current value is equal to 3 (three) |
TimeStamp |
Date and time |
Last timestamp |
UserInfo1 and UserInfo2 |
Variant |
Free usage fields |
Value |
Variant |
Current value, in engineering units |
ValueCaption |
Text |
Text corresponding to the current value |
If the input value is already a Boolean or a value equal to 0 (zero) or 1 (one), users can link this value directly. If the ValueCaption property must have different texts representing statuses, users must fill the StateText0 and StateText1 properties. The same procedure must be adopted for double statuses, that is, two bits. In this case, users must fill the StateText0, StateText1, StateText2, and StateText3 properties.
If a value must be processed to extract a meaning, users must use an xoScadaSource-type object as child object. The BitOperation property of this type of object can have the values 0: No operation, 1: Extracting an individual bit, or 2: Mask.
To represent multiple discrete statuses, it is also mandatory using xoScadaSource-type objects for each one of the statuses, configuring the MultiState property to True both in this object and in the xoScadaSource-type child objects. In this case, the first xoScadaSource-type object evaluated as True is the current status, copying both value and color.