|
<< Click to Display Table of Contents >>
System-Type Tabs |
System tabs are defined in the PlantModel Library, with no possibility of customization, and assembled based on the data structure. The syntax in the PopupCode property is a single letter, as described next.
•A: Analog Measurements
•D: Discrete Measurements
•C: Commands
•S: Status
•P: Protections, available only for Elipse Power
The order of these letters define how Links appear on the pop-up window. For example, the expression "A;C;S" indicates the display of Analog, Commands, and Status tabs, in that order. Unless explicitly indicated, described on topic Markers, the window opens and displays the first declared tab, in this case the Analog tab.
Data from PlantModel Library
Parameter |
Description |
Folder |
Object |
|---|---|---|---|
A |
Analog Measurements |
xfMeasuresFolder |
xfAnalogInfo, xfPMRef.ItemObject (if this one references an xfAnalogInfo object) and xfParameter |
xfSetPointsFolder |
xfParameter |
||
D |
Discrete Measurements |
xfMeasuresFolder |
xfDiscreteInfo and xfPMRef.ItemObject, if this one references an xfDiscreteInfo object |
C |
Commands |
xfCommandFolder |
xfCommand, xfCommandUnit, xfInterlockGroup, and xfInterlockUnit |
S |
Status |
xfStatusFolder |
xfDiscreteInfo and xfPMRef.ItemObject, if this one references an xfDiscreteInfo object |
NOTES |
•Objects of type xfParameter can be allocated on folder xfMeasuresFolder as well as on folder xfSetPointsFolder. This allocations is optional and its only for organization purposes, considering instantiation together with other Measurements or separately on the same folder. •The same situation occurs with objects of type xfDiscreteInfo, which can be displayed on the Discrete (D) tab, if allocated on folder xfMeasuresFolder, as well as on the Status (S) tab, if allocated on folder xfStatusFolder. |
Data from Elipse Power
Parameter |
Description |
Folder |
Object |
|---|---|---|---|
A |
Analog Measurements |
(not specified) |
PowerAnalogMeasurement |
D |
Discrete Measurements |
(not specified) |
PowerDiscreteMeasurement |
C |
Commands |
(not specified) |
PowerDiscreteCommand and PowerStepCommand |
P |
Protections |
PowerProtectionGroup |
PowerProtectionDevice |
Users can use custom types of objects on the Faceplate Screen, in the scenarios described next.
On this tab, users can replace the default Screen object linked to an xfAnalogInfo-type object by a custom object, declaring this object and its corresponding library in the PopupCode property, in the following format.
A{Library.Object}
The default Screen object for xfAnalogInfo-type objects is hpXDynValueAnalog.
On this tab, users can replace the default Screen objects linked to xfCommandUnit- and xfInterlockUnit-type objects by custom objects, declaring these objects and their corresponding libraries in the PopupCode property, in the following format.
C{Library.Object1, Library.Object2}
The first declared object links to an xfCommandUnit-type object and the second declared object links to an xfInterlockUnit-type object.
The default Screen object for xfCommandUnit-type objects is hpXCommandButton and the default Screen object for xfInterlockUnit-type objects is hpXBlockIndicator.
On this tab, users can replace the default Screen object linked to xfDiscreteInfo-type objects by a custom object, declaring this object and its corresponding library in the PopupCode property, in the following format.
D{Library.Object}
The default Screen object for xfDiscreteInfo-type objects is hpXDynValueDiscrete.
On this tab, users can replace the default Screen object linked to xfDiscreteInfo-type objects by a custom object, declaring this object and its corresponding library in the PopupCode property, in the following format.
S{Library.Object}
The default Screen object for xfDiscreteInfo-type object is hpXDigitalDisplay.
If users want to keep one of the default objects, use the % (percent) character as a placeholder. For example, on the Commands tab, to use a default command object of a Screen and change only the interlock object, the syntax of the PopupCode property is the following:
C{%,myLib.myXControl}
The syntax of parameters using only placeholders is equivalent to the default usage of parameters. The next examples of the syntax of the PopupCode property are equivalent.
A{%};C{%,%}
A;C