Preferences

Alarms

Interface for configuring the default options for project’s alarms.

Turn on the Open comments dialog on acknowledge flag to make project users comment upon each alarm acknowledgement.

Personal alarm settings configured in the Manage permissions menu override this parameter.

The Disable all notifications flag stops email alarm notifications.

You can also set the specifics of commenting by configuring Priority and Categories parameters.

The Priority and Categories parameters are auxiliary to the Open comments dialog on acknowledge flag.

The Priority setting defines what priority groups of alarms users should comment on acknowledgement:

• Low
  Users must comment acknowledgements of alarms of all priority levels starting with the lowest.
• Medium
  Users must comment acknowledgements of alarms of medium and high priority levels.
• High
  Users must comment acknowledgements of alarms only of high priority.

The Categories parameter allows you to choose particular groups of alarms.

Personal user permission may override these preferences.

Under System settings, you can configure time lags for activation and deactivation of system alarms. You can set the time lag for activation in the Delay-on field and make a similar operation for deactivation in the Delay-off field.

Server

Node Preferences contain device-related parameters. You can configure the following parameters in this subsection:

• Maximum decimal places for float tags
• Maximum error count to ignore
• Period of sending tags
• Ignore anonymous write

Set the maximum number of digits after a decimal point in the Maximum decimal places for float tags field.

Devices send tag values once in a certain period. You can set the default period for your project devices with the Period of sending tags parameter.

A connection error is a situation when for some reason, the system cannot get the data from a device. The Maximum error count to ignore parameter defines the number of connection errors that the system would skip showing the last obtained value. If the number of errors has exceeded the parameter, the connection error message appears.

For example, the period of obtaining tag values is one second. And the error counter is set to 3. So, if the system cannot get the data for more than 3 seconds in a row, then the system signals the connection error.

The Ignore anonymous write flag allows switching off the system alarm on anonymous tag writings.

History

History preferences is a set of essential for tag history storing parameters. These parameters applied to all project tags unless otherwise defined in particular tag’s history settings. History preferences contain:

• Aggregate the tag values before storing
• Aggregation parameters:
• Function
• Interval
• Exclude duplicate values

For more details on history configuration, see History.

HMI

In this subsection, you can edit HMI View related settings. There are the following points to configure:

• Open comments dialog on value change
  Enables or disables commenting tag value changes.
• Enable anonymous writing monitoring
  Turns on registering of external changes of tag values
• Default starting page
  Defines the initial page that a user sees when opening HMI View.
• Timezone
  Sets the default project timezone. You can type your location or time zone and choose one of the available options.
• Default locale
  Defines the project language.
• Waiting time for writing tag
  Sets the time interval after which the value gets transmitted to the tag.

The Set Point Settings block of options allows you to configure the Set point deviation property’s appearance preferences. By default, the Enabled flag is set to false. You can change colours for the three points. The default colours are blue, green, and red for the Min Color, Set Point Colour, and Max Colour parameters respectively.

Fig. 1. You can change the default colours to custom ones

Automation Binding Conditions

Automation binding conditions make the process of label creation and other element related actions more streamlined and standardized. The user can create sets of conditions by which the bindings are executed. The set of rules apply to tags with specific suffixes defined by the user. The user can then:

• replace or remove the tag suffix in the label;
• define default label formatting;
• specify other element property settings (Add to trend, Click event, Process value, etc.)
•  Bind formatted tag name to element with the button.

In order for automation bindings to work properly, it is a prerequisite that tag suffixes are consistent and standardized, for example, separate suffixes should be used for digital and analog inputs.

Fig. 2. The process of defining an automation binding and binding it to the page element.

The following tables explains the rules available to the user.

Table 1. Automation binding rule options