Aller au contenu principal
Version: v3.6 (Non supportée)

Tag Properties

This dialog box defines the main properties of the supervised tags. It can be called from the configuration of supervision l ist, by clicking on the " Add..." button or the " Modify..." button in the dialog box displaying the variable list (see § Erreur ! Source du renvoi introuvable. "Erreur ! Source du renvoi introuvable."). It also can be called from the contextual menu associated with the branch " Variables" in the screen of the main screen (see § 4.6.1.4 "Tags").

The external reference of the concerned tag is displayed in the title bar: DDE reference (under the form "server" |"topic"!"item"), OPC reference ( under the form "server \tag") or simple name.

Type The type of tag defines the usage of the tag in the application. Variable Simple tag only declared to be able to get its value and that can be referenced in an alarm message (see Message format ) or a contextual instruction file to display its current value. Event Variable associated w ith an event condition for recording of the changes of state of the event in the event log. A list of actions to execute (calls of groups or operators, commands ...) can be associated with each change of state of the event (set, reset). An event is processed like an alarm if the "alarm enabled" option is checked. Acknowledg. Variable associated to an event condition, but used to bring up an acknowledgment request for the associated alarm group from a supervised device (acknowledgment hard button) or through a communication driver. If there is no alarm group designated for the variable, the field message must contain a valid operator name. This name will be used to search for and to acknowledge the oldest group in alarm for which a call has been transmitted to the operator in question. See note on the bottom of the page*. Option Not redundant A tag can be defined of non redundant type to specify, in the case of an installation of 2 stations in redundancy, that this tag is specific to the local station and that t he automatic procedure of synchronization of the redundant stations should not recopy it on the distant station. Moreover, for the tag of the event type associated with a call group action, the activation of the non redundant event will always trig the call of the group, whatever is the activation status of the station. Name Alphanumeric identifier of the tag. By default, it is the external reference of the tag, displayed in the title bar of the dialog box (DDE or OPC reference or simple name). This name is this one which will be used to reference the corresponding tag from a client application of the OPC server of ALERT. Station The station defines a subset of the application corresponding to a specific entity, geographical (site) or organizational (company, trade ...). The definition of a station makes it possible to separately treat subsets of tags and operators, with all associated information

  • Usage of an acknowledgment type tag When the tag is type acknowledgment, the change of state of the tag to the event state provokes the acknowledgment of all alarms belonging to the basic functional group associated with the tag. If there is no functional group associated with the tag, the fie ld "Message" must contain the name of a valid operator in order to be able to search for the oldest alarm group transmitted to this operator and acknowledge alarms of this group (with the name of the operator in question). If a Call group action is defined, a call is triggered to the operators concerned by the acknowledgment of the associated alarm group, with transmission of the formatted message of the tag. Example message format: "Acknowledgment of &G alarms by &M" message: "Peter HENRY" associated group: "Boiler room" message transmitted: "Acknowledgment of Boiler room alarms by Peter HENRY"

(on call schedule, alarm table, alarm history, event log). By default the tags are attached to the local station (first station displayed in the main screen). Group The group referred in this dialog box is the basic functional group to which the variable is attached. A functional group allows tags concerning a specific entity (machine, room, category ...) to be grouped. It makes it possible to organize and visualize alarms by groups (alarm table, alarm history) and to be able to execute certain treatments on the level of the groups (acknowledgment, masking, statistics ...). A tag can belong to several groups. The ba sic functional group, selected in this field, present some additional functionalities:  Possibility of integrating the name of the basic group in the alarm message by inserting the string "&G" in the associated message format (see § 5.11.5 "Definition of message format").  Possibility of playing the audio message of the basic group before the audio alarm message, or in substitution if the alarm message is empty.  Possibility of performing only one call for all alarms of the group when this option is enabled on the level of the call driver.  Possibility of acknowledgment of the basic group of an alarm ordered from a driver (vocal ...). If this field is empty, the tag is attached to no basic group. The button on the right of the field gives access to the configuration of the properties of the selected group (see § 5.14 "Tag group properties"). Button Value... Click on this button to define the display format of the value of the tag and associated treatments. See § 5.11.1 "Format of a tag value". DDE / OPC Polling If the reference of the tag is a DDE or OPC reference, the polling mode of the tag must be defined:  Advise: When this option is checked, the tag will be put in permanent polling, by the means of a DDE or OPC ADVISE request near the concerned server. The supervised tag then will be automatically transmitted by the server to each change of its value, without any other request being necessary.  Periodic Request: When this option is checked, the concerned tag will be the subject of explicit and periodic DDE or OPC requests. These requests make it possible to control that the supervised application is always active (watchdog). The polling period and the response timeout can be adjusted in the supervision options (see § 7.2 "Supervision options"). This option should be validated only for a restricted number of tags, insofar as the active polling is consuming resources and as it is not useful to test several variables to check that the supervised application is always active.  On Group Alarm: When this option is checked, the concerned tag will make the object of DDE requests every time an alarm of the same functional group will change of state (activation or deactivation of alarm). This option reduces the number of DDE transactions (economy of resources system), by regrouping alarms of the same group on one alarm ("OR" alarms) set in DDE advise. The

real source of the alarm is provided by reading at this moment all tags of the group having option "On group alarm". Event

  • The event condition defines the state in which the tag must be considered as an event. This condition can be logical (logical state represented by a name, mask of a logical state of the tag) or analogical (comparison with a value, in equality or going beyond of high or low threshold). To define an event condition, in reference to a value "X" of reference, the following operators are proposed: NONE No event condition, event will be trigged from an external application DIFFERENT Event if value is not equal to X EQUAL Event if value is equal to X HIGHER Event if value is higher than X LOWER Event if value is lower than X HIGHER SAME Event if value is higher than or equal to X LOWER SAME Event if value is lower than or equal to X AND Event if a bit defined as 11 into X is 1 into the value NOT AND Event if a bit defined as 1 into X is 0 into the value SUPVAR Event if the variable variation during a time of T seconds is higher than the value V. V and T are defined by the value X = "V;T" INFVAR Event if the variable variation during a time of T seconds is lower than the value V. V and T are defined by the value X = "V;T"

(*) The state of a bit is defined by the corresponding bit in the value "X" converted in hexadecimal. Example: for the bit mask 00010000, translate in hexade cimal (10h), then type the value converted in decimal (16). The value "X" entered in edit field can be numeric (positive or negative, integer or float) or alphanumeric. A value is defined as numeric if it begins by one of the following characters: '+','-','0','1','2','3','4','5','6','7','8','9', or '.' If the value entered is alphanumeric, only the operators NOT EQUAL and EQUAL are available, the other operators being accepted but treated as EQUAL (HIGHER OR SAME, LOWER OR SAME) or NOT EQUAL (all the others). Warning: the definition of an alphanumeric value is only authorized when the tag has been defined with the "String" type (see § 5.11.1 "Format of a tag value")

Examples  Event upon change to high state (non null):

(Condition proposed by default)

1 The state of a bit is defined by the corresponding bit in the value "X" converted in hexadecimal. Example: for the bit mask 00010000, translate in hexadecimal (10h), then type the value converted in decimal (16).

 Detection of crossing high threshold:

The value to not to go across is 117,4.

Remark:

It is possible to supervise a high threshold and a low threshold for the same variable by defining 2 events with the same reference. An event will be associated to the high threshold crossing (as above) with the adequate messages. The other will be associated to the low threshold crossing (LOWER or INF EGAL) with correspondent messages.  Supervision of a "watchdog" variable :

If the variable does not change (at least 1 unit) during 3 seconds, the event is activated.

  • The Transitory option indicates the transitory (or pulsed) state of an event. A transitory event (passage of door...) is only logged when changing to event state (not when returning to the normal state, this last being implicit).
  • The Reactivable option indicates that the event can be reactivated without passing by a return to the normal state. A reactivable event is consigned to each change of state corresponding to an event condition. This option is necessary for example when the tag receives messages and must start a treatment each time it receives a message.
  • The Schedule... button opens a dialog box to define time areas for event invalidation, alarm masking or call inhibition. See § 5.11.2 "Event schedule". When the event invalidation, alarm masking and call inhibition schedule is active, a green led is displayed on the button. Alarm
  • The Alarm enabled option indicates that the event will be processed as an alarm: recording in the alarm table and alarm history , acknowledgment required, possibility of masking.
  • The Priority parameter defines the priority level of the alarm. The priority level determines the order of alarms in the alarm table (and therefore the transmission order of messages), the most important a larms being at the head, as well as the order of the calls when several alarms are detected simultaneously. The priority level also conditions the call processing. If the priority level is lower than the minimal level defined in the alarm options (see § 7.4 "Alarm options") for "reduced duty" period, and if the attached on -call group is in a "reduced duty" period when the event is detected, the call will be delayed until the end of this p eriod (unless alarm is acknowledged meanwhile). The priority level can be defined between "0" and "9999". By default, "0" is the lowest priority. However, the priority order can be reversed in the general alarm options. The parameter Period for automatic priority increment allows the alarm priority to be dynamically incremented by defining a cycle of automatic increment of the alarm priority when the alarm is waiting for transmission. When the Default option is selected, the cycle value is that wh

...