HomeAVEVA InTouch HMIExample of Alarm Queries Wonderware InTouch

Example of Alarm Queries Wonderware InTouch

About InTouch Alarms Wonderware InTouch

Touch Alarms wonderware intouch

Alarms represent warnings of process conditions that could cause problems and require an operator response. A typical alarm is triggered when a process value exceeds a user-defined limit, such as an analog value exceeding an upper threshold. This triggers an alarm to notify the operator of a problem.

After the operator acknowledges the alarm, the InTouch HMI recognizes the alarm has been acknowledged. You can configure the InTouch HMI to require an alarm to be acknowledged even if the condition causing the alarm has passed. This ensures that an operator is aware of events that caused a temporary alarm state but have returned to normal. The main alarm states are described in the following table:

  Alarm State    Condition
  ACK   Alarm was acknowledged.
  ALM   Alarm has occurred.
  RTN   Tag returned from an alarm state to a normal state.  

InTouch Alarms

An event is a detectable occurrence of something happening within the system, which may or may not be associated with an alarm. A transition into or out of an alarmed state is one kind of event. An event might also be an operator action, a change to the system configuration, or some kind of system error.

An event is different than a condition. A condition can persist for minutes, hours, days, or weeks. An event is momentary; it takes place and is immediately over. An alarm is a condition; an alarm notification is an event.

Events represent normal system status messages and do not require an operator response.

When you define a tag to do event monitoring, you can choose to have event messages printed or logged to the alarm system each time the tag value changes. The event message includes how the value changed and whether the operator, I/O, scripts, or the system initiated the change.

An event can be one of the following types:

  Event   Condition
  OPR   The operator modified the tag value using the Value input.  
  LGC   A quick script modified the tag value.
  DDE   The tag value was poked from a DDE client.
  SYS   A system event occurred.
  USER   $Operator changed.

The SYS and USER events are generated by the system regardless of whether event logging is enabled for any tags. DDE, OPR, and LGC events relate to tag values and are only generated for tags that have event logging enabled.

Related Topics  

Types of InTouch Alarms

Within the InTouch HMI, alarms are classified into general categories based on their characteristics. These categories are known as Class and Type. The Distributed Alarm system categorizes all alarms into five general conditions: Discrete, Value, Deviation, Rate-of-Change, and SPC.

  Alarm Condition    Distributed Class    Distributed Type 
  Discrete   DSC   DSC
  Value – LoLo   VALUE   LOLO
  Value – Low   VALUE   LO
  Value – High   VALUE   HI
  Value – HiHi   VALUE   HIHI
  Deviation – Major    DEV   MAJDEV
  Deviation – Minor    DEV   MINDEV
  Rate-of-Change   ROC   ROC
  SPC   SPC   SPC

You associate each InTouch tag with an alarm condition when you define the tag. Depending upon a tag’s type, you can define one or more of the alarm classes or types for it.

Alarm Queries Wonderware InTouch

Alarms and Events Window Popup Wonderware Intouch :-https://youtu.be/fHKgPYI8agA

How to Create Alarms and Events



Alarm queries follow this syntax for the local node:

Provider!AlarmGroup

For example:

InTouch!$System

Use the following query syntax for remote nodes:

\NodeNameProvider!AlarmGroup

For example:

\ProdSvrInTouch!$System

Use the following syntax for querying alarms from a Galaxy. This syntax gets alarms from a specific attribute of an object in a specific area on a specific computer.

\NodeNameGalaxy!Area.Object.Attribute

The following syntax gets all alarms from a specific area:

\Galaxy!Area

The following syntax gets alarms from two areas:

\Galaxy!Area1 \Galaxy!Area2

The following syntax gets all alarms from the Platform on computer node (by default):

\NodeNameGalaxy

You can also use a wildcard. The following syntax gets all alarms from Area1, Area2, Area3, and so on:

\Galaxy!Area*

The following syntax gets all alarms from all objects starting with the characters “Tank” in the area “Area”:

\Galaxy!Area.Tank*

Recent Posts

Popular Posts

Wonderware Intouch Cracked

Wonderware IntouchInTouch software leaps onto your screen with breakthrough technology, amazing graphic capabilities, and comprehensive functionality delivered with Wonderware’s legendary ease of use. Wonderware’s...

How to Install Intouch License: Download, Types, Features, Working

Intouch LicenseWonderware is a powerful and widely-used software platform that is used by many businesses and organizations to streamline their operations and increase efficiency....

Visual Basic and C-Action Script WinCC: How to Write Script

Action ScriptsActionScript is a programming language used to create interactive and dynamic animations, games, and applications for the web and mobile devices. It is...

Popular Softwares

Wonderware Intouch Cracked

Wonderware IntouchInTouch software leaps onto your screen with breakthrough technology, amazing graphic capabilities, and comprehensive functionality delivered with Wonderware’s legendary ease of use. Wonderware’s...

Download RSLogix 500 v12

RSLogix 500 is a programming software developed by Rockwell Automation for programming and configuring Allen-Bradley PLCs (Programmable Logic Controllers). It is part of the...

GX Developer free download

GX Developer with serial keyGX-Developer is a software program used for programming and controlling programmable logic controllers (PLCs) made by Mitsubishi Electric. It is...

FIND MORE