STS Variables are place holders that are used at different places to set attribute values of STS objects from their respective context.
Example for HMI Text related to the XCBR.Pos.stVal of the Circuit Breaker QA0. :
"<conductingequipment.name> Position"
will be resolved to
QA0 Position"
Variables can be used for
-
Setting of attribute values in the Signal List
-
Setting of Logical Node Prefixes
Variables
"<process.name>";
"<process.desc>";
"<process.template>";
"<process.ref>";
"<process:1.name>";
"<process:1.desc>";
"<process:1.template>";
"<process:1.ref>";
"<process:2.name>";
"<process:2.desc>";
"<process:2.template>";
"<process:2.ref>";
"<bay.name>";
"<bay.desc>";
"<bay.template>";
"<bay.ref>";
"<busbar.name>";
"<busbar.desc>";
"<busbar.template>";
"<busbar.ref>";
"<substation.name>";
"<substation.desc>";
"<substation.template>";
"<substation.ref>";
"<voltagelevel.name>";
"<voltagelevel.voltage>";
"<voltagelevel.nomFreq>";
"<voltagelevel.numPhases>";
"<voltagelevel.desc>";
"<voltageLevel.name>";
"<voltageLevel.voltage>";
"<voltagelevel.desc>";
"<voltagelevel.ref>";
"<voltagelevel.nomFreq>";
"<voltagelevel.numPhases>";
"<function.name>";
"<function.desc>";
"<function.template>";
"<function:1.name>";
"<function:1.desc>";
"<function:1.template>";
"<function:2.name>";
"<function:2.desc>";
"<function:2.template>";
"<powerEquipment.name>";
"<powerEquipment.desc>";
"<powerequipment.name>";
"<powerequipment.desc>";
"<powerequipment.template>";
"<powerequipment.ref>";
"<conductingEquipment.name>";
"<conductingEquipment.desc>";
"<conductingequipment.name>";
"<conductingequipment.desc>";
"<conductingequipment.template>";
"<conductingequipment.ref>";
"<feeder.desc>";
"<feeder.name>";
"<feeder.template>";
"<powerTransformer.desc>";
"<powerTransformer.name>";
"<powertransformer.desc>";
"<powertransformer.template>";
"<powertransformer.name>";
"<ied.name>";
"<publisher.ied.name>";
"<ied.type>";
"<ied.devicerole>";
"<ied.desc>";
"<ied.manufacturer>";
"<logicaldevice.name>";
"<signal.name>";
"<logicalnode.class>";
"<logicalnode.prefix>";
"<logicalnode.name>";
In addition, many objects have an action ‘Extended Parameters’ in their right-click context menu. The value of an extended parameter can be accessed by using the corresponding objects name + parameter name, e.g. <bay.myExtendedParameter>
Application Template Variables
Two new variable groups are available for parameterizing application template communication settings:
Sender Variables
Resolve based on the signal source context. Available categories include:
-
<sender.bay.name>,<sender.bay.desc>,<sender.bay.template>— bay-level properties -
<sender.function.appid>,<sender.function.macsuffix>— function-level properties -
<sender.substation.name>,<sender.substation.desc>— substation-level properties -
<sender.voltagelevel.name>— voltage level properties -
Additional categories:
sender.signal,sender.logicalnode,sender.conductingequipment,sender.powertransformer
Receiver Variables
Resolve based on the input destination context. Available categories include:
-
<receiver.function.macsuffix>,<receiver.function.desc>— function-level properties -
<receiver.bay.name>,<receiver.bay.desc>— bay-level properties -
Additional categories mirror the sender groups
These variables are used in service configuration properties (App ID, MAC Address, VLAN ID, etc.) and in input role Name Constraints. The full list of available variables is visible in the Context Formula Editor.
Variables are resolved using one of three resolution contexts (Specification, Implementation, or Any Context). See Application Templates for details on resolution behavior.