Helps_SV_V11_1 _ WORD FILES _ ENUSV_Variables

Managing Variables Using the Application Explorer3Using Cut, Copy and Paste with Variables and Branches6Using Cut, Copy and Paste of Variables with Behaviors9Using Cut, Copy and Paste with Mapping10Important Note About Linking or Mapping a Variable to its Source11Variables Settings12Level Labels16About the Variables Tree18How the Variables Tree is Structured19Rules for Branch and Variable Naming21Using the Variables Tree with Graphic Symbols22Before You Start to Configure Variables23Configuring the Variable Branches24Adding Variables to a Branch25Properties Common to all Variable types26Using the Permanent Scan for Mimic Options28Configuring and Using Extended Attributes29Text Variables31Features Specific to Register Variables33Features Specific to Bit Variables36Alarm Variables Overview37Using the Latch Behavior Property38Using Different Levels for Alarm Acknowledgement, Masking and Maintenance39What is Associated Behavior?40Configuring a Threshold43Configuring a Counter44Configuring a Chronometer45Configuring Discrepancy Checking on Bits46Configuring an Associated Action47Configuring Alarm Masking48Configuring an Alarm Acknowledge Trace Bit49Configuring an Event50Configuring Trend Recording51Configuring Overflow Processing52Linking a Variable to its Source Overview53Linking a Variable to an Equipment Item55Linking a Variable to an OPC Item58Linking a Variable to a DDE Source60Linking a Variable to an External Source62Linking a Variable to a Lonworks Variable63Advanced Properties Specific to LonWorks Variables65How to Use an Expression with a Structured LonWorks Variable67How Variable Properties are Linked to BACnet Object Properties68Linking a Variable to a BACnet Object, Property or Event/Alarm70Advanced Properties Specific to BACnet Variables73Using BACnet Proprietary Properties75Linking a Variable to an IEC 60870-5-104 Object76Linking a Variable to a DNP3 Source78Advanced Properties Specific to DNP3 Variables80Using Advanced Properties to Configure a DNP3 CROB81Using Advanced Properties to Configure a DNP3 AOB83Linking a Variable to an SNMP Source85The SNMP OID Selector Dialog87Advanced Properties Specific to SNMP Variables90Scaling and Adding a Deadband to Register Variables92Domain and Nature94Associated Labels95Using the Variable Selector97Expressions Overview99How to Add a Template Expression100How to Add a Variable Expression102Expression Syntax104Alarm Synthesis Overview106How to Add an Alarm Synthesis108Configuring an Alarm Synthesis Filter110About Formulae112Formula Management Dialog Box113Creating a Formula115Flow calculation 1: F = c1*v1*(v2+c2)/(v3+c3)116Flow calculation 2: F = c1*v1*sqrt(v2+c2)/(v3+c3)117Flow calculation 3: F = c1*sqrt(v1*(v2+c2)/(v3+c3)*(1-c5*v1/c6max)118Integral: C = C+(v1*Period/3600)119Standard Operators 1: R=(op1)v1)op2v2op3v3)op4v4)120Standard operators 2: R = R+(op1)v1)op2v2op3v3)op4v4)121What is Variable Treatment?122Creating an Equipment Life Indicator123Creating a Supervisor Life Indicator124Creating Group Alarm Acknowledgement125Creating a Variable Life Indicator127Population Filters Overview129The Population Dialog Box130Configuring a Population131About System Variables133System Information Variables134Printer Status Variables136Communication Status Variables137Lonworks Status Variables138DDE Status Variables140OPC Status Variables141BACnet Status Variables142SNMP Status Variables144Alarm Counter Variables146Network Status Variables147HDS Status Variables148Message Status Variables149Event Counter Variables150IEC 60870-5-104 Status Variables152Managing Variables Using the Application ExplorerThe Variables folder includes the Variables Tree, Domain and Nature, Expressions and Alarm Synthesis. Also associated with variables are Associated Labels, Formulae, Recipes and Vartreat (specialist variable treatment). Although these are not currently configurable via the Application Explorer they are included in this help book for completeness. When used to manage the Variables Tree, the appearance of the Application Explorer is modified to include a third pane that is used to associate behaviors with variables. Behaviors include such functionality as Trend, Thresholds, Events and Alarm Actions. Show pictureThe Variables Tree was known as the Variables Database in previous versions of the Supervisor. The name has been changed to avoid confusion with Relational Database Systems (also known as Databases) which are increasingly used in conjunction with the Supervisor for recording historical data.Tasks applicable to variables, Variables Tree, domain and nature, expressions and alarm synthesisWhen the Variables folder is selected.IconTaskDescriptionSettingsDisplay the general variables settings dialog.When the Variables tree or a branch is selectedIconTaskDescriptionAdd a branchAdd a new branch to the Variables Tree.Add a registerAdd a new register variable to the Variables Tree.Add a bitAdd a new bit variable to the Variables Tree.Add a textAdd a new text variable to the Variables Tree.CopyCopy the selected branch.CutCut the selected branch.PastePaste a branch or variable. Only available after a cut or copy.When a variable is selected.IconTaskDescriptionAdd a thresholdAdd threshold behavior to a register.Add an alarm actionDisplays the alarm action tools.Add an ack traceAdd alarm acknowledgement trace using a bit.Add a program actionAdd an action to run a program from an alarm in the alarm viewer.Add a window actionAdd an action to open a window from an alarm in the alarm viewer.Add maskingAdd alarm masking by a variable.Add masking by expressionAdd alarm masking by an expression template.Add an event actionDisplay the event action tools.Add a message eventAdd an event to trigger a message to a bit, register or text.Add a program eventAdd an event to trigger a program to a bit, register or text.Add a trendAdd trending to a bit or register.Add discrepancyAdd discrepancy checking to a bit.Add chronoAdd chronometer behavior to a register.Add counterAdd counter behavior to a register.CopyCopy the selected variable.CutCut the selected variable.When the Domain folder is selected.IconTaskDescriptionAdd a domainAdd a domain.When the Nature folder is selected.IconTaskDescriptionAdd a natureAdd a nature.When the Expressions folder is selected.IconTaskDescriptionAdd an expression templateAdd an expression as a template.Add an expression on a variableAdd an expression to a variable.When the Alarm Synthesis folder is selected.IconTaskDescriptionAdd an alarm synthesisAdd an alarm synthesis.A note about the Removal and Properties tasksThe configuration objects created by the above tasks all have corresponding remove and properties tasks. The icons corresponding to these tasks are similar to those used to add the object except that, for a remove task the icon includes a red X, and for properties a magnifying glass.For example the icons to add, remove, and display the properties of a nature are , and respectively.Using Cut, Copy and Paste with Variables and BranchesThe cut, copy and paste tasks can be used on a single variable or an entire branch of the variables tree. If used on a single variable then any behaviors attached to the variable are included in the operation. If used on a branch, all sub-branches, variables and behaviors are included in the operation. The combination of copy and paste allows you to rapidly develop the variables tree, particularly if it has a uniform structure.The combination of cut and paste can be used to move or rename a variable or branch.See the topic Using cut, copy and paste of variables with behaviors for important information about pasting variables with behaviors.Reminder about the difference between copy and cut? Copy makes a copy of the selected variable or branch. It can be pasted any number of times. Cut makes a copy of the selected variable or branch. It can only be pasted once. After the paste, the variable or branch that was cut is deleted. If you use cut and close the Application Explorer before using paste, the variable or branch that you have cut is not deleted.What happens when I cut or copy and paste a variable?When you cut or copy a single variable, the entire variable name including the branch appears in paste task in the task pane. Show pictureWhen you paste the variable only the variable name is used - the branch is not included. A dialog will open suggesting a name for the duplicated variable. Show pictureWhat happens when I cut or copy and paste a branch?When you cut or copy a branch, only the branch name appears in paste task in the task pane. Show pictureWhen you paste the branch, a dialog will open suggesting a name for the branch. Show pictureThe paste task can take several seconds to complete if you are pasting complex branch with many sub-branches and variables.Using Cut, Copy and Paste of Variables with BehaviorsWhen you copy and paste a variable with one or more behaviors, the behaviors are included in the paste and a duplicate behavior is created for the duplicate variable.Should the behavior be one that includes one or more variables in its configuration (threshold, chronometer, etc.) then those variables will also be duplicated as long as they are only used in a behavior of one variable.If several behaviors use the same variables in their configuration (For example a common reset variable for several chronometers) then those variables common to the behaviors will not be duplicated.The Application Explorer will determine the strategy to apply for a copy paste by analyzing both the name of the variable and the names of the variables involved in the behavior. It will duplicate the behavior variables as long as their names conform to the following rule. The full name (that is branch and leaf) of any variable included in a behavior that is to be copied and pasted should contain the name of the leaf of the variable to which the behavior is attached. This example of a register with chronometer behavior, that follows this rule, illustrates this.Original variablesCopy to new variable nameunder the same branchCopy same variable name to new branch Branch02RegisterBranch01.Register01Branch01.Register02Branch02.Register01Trigger bitBranch01.Register01.TriggerBranch01.Register02.TriggerBranch02.Register01.TriggerInit bitBranch01.Register01.ResetBranch01.Register02.ResetBranch02.Register01.ResetRegisterBranch01.Register01Branch01.Register02Branch02.Register01Trigger bitBranch01.Register01_TriggerBranch01.Register02_TriggerBranch02.Register01_TriggerInit bitBranch01.Register01_ResetBranch01.Register02_ResetBranch02.Register01_ResetIf the names used for the included variables do not follow this rule, the variables included in the behavior of the newly pasted variable will keep the original names.Original variablesCopy to new variable nameunder the same branchCopy same variable name to new branch Branch02RegisterBranch01.Register01Branch01.Register02Branch02.Register01Trigger bitBranch01.TriggerBranch01.TriggerBranch01.TriggerInit bitBranch01.ResetBranch01.ResetBranch01.ResetCopy and paste of a register with threshold behaviorIf you add a threshold behavior to a register, the names of the threshold variables that it automatically generates do not follow the above rule. The threshold variable name contains a modified copy of the register name including the threshold type . The copy paste behavior is modified to accommodate this. The following table illustrates this.Copied variable namePasted variable nameRegisterBranch01.Register01Branch01.Register02Hi hi thresholdBranch01.Register01_HiHiBranch01.Register02_HiHiHigh thresholdBranch01.Register01_HighBranch01.Register02_HighLow thresholdBranch01.Register01_LowBranch01.Register02_LowLo lo thresholdBranch01.Register01_LoLoBranch01.Register02_LoLoIf the Variables Tree contains threshold behavior using a non-standard naming scheme you should avoid copy and paste of those particular variables as the paste will not work and may destroy the link between the original variable and its thresholds.Using Cut, Copy and Paste with MappingIf you cut and paste, or copy and paste, any variable where the source is mapped to one of the Supervisors data acquisition objects then the mapping is duplicated in the new variable. The mapping of more than one variable to the some data acquisition objects is not recommended therefore, after using copy and paste, the mapping of either the original variable, or the duplicate, must be edited.Data acquisition objectMapping of more than one variable permittedOPCYesEquipment (Native drivers)YesIEC 60870-5-104YesDNP3YesIEC 61850YesLonWorksYesBACnetYesDDENoImportant Note About Linking or Mapping a Variable to its SourceThere are two methods to link (also know as mapping) a variable to the source of its value. It is important to understand the difference.From the Source tab of the variables configuration dialogThe Source tab, in the configuration of each variable, allows you to link a variable to its source one variable at a time. This is generally considered to be the more time consuming method of linking variables. However, this method gives you direct access to the advanced properties sometimes required when linking variables.The help topics for this method are found in the Variables help book.From the mapping dialog for each data acquisition objectEach data acquisition object (OPC, Equipment, DNP3 etc) has its own mapping dialog. The mapping dialogs allow you to link many variables to their source at the same time and even allow you to create the variables automatically. This is generally considered to be the quickest method to link variables. However, it does not give you direct access to the advanced properties sometimes required when linking variables.The help topics for this method are found in Data Acquisition help book.Variables SettingsThe variables settings can be displayed from the Variables entry in the Application Explorers Main settings dialog or from the Settings task when the Variables folder is selected in the Application Explorers configuration tree. Show pictureAlso see the topic Level labels. Persistence Save period for internal variables - The period at which the value of internal variables, with the Saved property enabled, is saved on hard disk. The last saved value of the variable is restored when the Supervisor is re-started. Internal variables Internal variable initialization Initial value for internal bits and alarms - Enable the initialization of internal bits and alarms when the Supervisor starts. Initial value for bits Invalid - Internal bits are all set to invalid. To 0 - Internal bits are all set to 0. To 1 - Internal bits are all set to 1. Initial value for internal alarms Invalid - Alarms are all set to invalid. Alarm off - Alarms are all set to off. Behavior No producer list assigned behavior - The following two options only affect variables that have not been assigned to a producer list. Local association - The saved value behaves normally. User context - The saved (and restored) value is dependent on the User that is logged on. See the book Deploying the Supervisor on a Remote Desktop Session (RDS) Host for more information. Permanent scan Permanent scan for all variables Causes the Supervisor to permanently scan all communication frames linked to one or more variables. If this property is not selected then the scanning can be disabled if none of the variables linked to it are displayed in a window. Invalidate variable if no scan for mimic When a communication frame is not scanned because none of the linked variables are displayed in a mimic, all the linked variables are set to invalid. Attributes and properties Extended attributes Enable the extended attributes for all inventory variables. Binary attribute Behavior Static - The attribute value can only be changed using the variable configuration dialog. Dynamic - The attribute can be changed at run-time using the SCADA Basic instruction VARIABLE. Distributed - When used in a multi-station project, changes in the value of the attribute are propagated to all interested stations. Commandable - The value of an attribute can be changed by any of the Supervisors sub-systems that have access to it. Command level - The command level that the User must have in order to write the attribute value. Browsing level - In the case of an OPC client connected to the Supervisors OPC server, the browsing level that the User must have in order for the attribute to be visible in the address space. Persistent - The value of the attribute is saved in the file VariablesSaved.dat. If the Variables Tree is saved the value is not lost (as it otherwise would be). Text attribute 3 (to 16) Behavior Static - The attribute value can only be changed using the variable configuration dialog. Dynamic - The attribute can be changed at run-time using the SCADA Basic instruction VARIABLE. Distributed - When used in a multi-station project, changes in the value of the attribute are propagated to all interested stations. Commandable - The value of an at