Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

Edge HMI

TABLE OF CONTENTS

Alarm worksheet body

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedOct 29, 2026
  • 3 minute read

The following table describes the Body settings on an Alarm worksheet:

Field

Description

Syntax

Tag Name

Name of the tag associated with the alarm.

Tag

Type

Type of the alarm:

  • HiHi: Activates the alarm if the tag value is greater than or equal to the specified limit.

  • Hi: Activates the alarm if the tag value is greater than or equal to the specified limit. (For Boolean tags, if the value is 1.)

  • Lo: Activates the alarm if the tag value is less than or equal to the specified limit. (For Boolean tags, if the value is 0.)

  • LoLo: Activates the alarm if the tag value is less than or equal to the specified limit.

  • Rate: Activates the alarm if the tag value changes more than the specified limit in a given period. (For Boolean tags, if the value changes at all.)

  • DevP: Activates the alarm if the tag value is greater than or equal to the tag's deviation set point plus the limit.

  • DevM: Activates the alarm if the tag value is less than or equal to the tag's deviation set point minus the limit.

    If you select Rate, you must also specify the check frequency (for example, once per minute) in the tag properties. If you select DevP or DevM, you must also specify the deviation set point in the tag properties. For more information, see Properties of Integer and Real tags.

Combo-box

Limit

Limit associated with each alarm.

The limits can be modified dynamically during run time, using the tag fields HiHiLimit, HiLimit, LoLimit, LoLoLimit, RateLimit, DevPLimit, and DevMLimit. For example: TagLevel->HiLimit

Number

Message

Message associated to the alarm. The message can be displayed on the Alarm/Event Control object and/or stored in the Alarm History and/or sent by Email, depending on the settings configured in the Header of the Alarm group.

Text (up to 256 chars). This field accepts String expressions.

Priority

Priority number associated to the alarm. When displaying alarms on the Alarm/Event Control object , the operator can filter and/or sort the alarms by priority.

Number (from 0 to 255)

Selection

Alias associated to the alarm (for example, AreaA, AreaB, etc). When displaying alarms on the Alarm/Event Control object, the operator can filter and/or sort the alarms by their selection value.

Text (up to 7 characters)

Tip: If you need more characters or a different data type, use a custom field instead.

Custom fields

Additional custom fields that will be saved in history. The number of custom fields (up to 10) can be set in Project Settings: Options.

Any

When you save an Alarm worksheet, only the header settings are saved as part of the worksheet file. All of the alarm configurations that make up the body of the worksheet are actually saved as tag properties. The next time you open that worksheet, the tags database is scanned for all alarm configurations that belong to the worksheet (that is, the alarm group), and then that information is used to recreate the body of the worksheet. This happens quickly and automatically every time you open the worksheet, so it might seem like you are opening a static file but that is not the case.

You may think of the Alarm worksheet as an editor for those tag properties that are related to alarms. If you use either the Tag Properties dialog box or the TagsDBSetAlarm function to edit the same properties, the updated alarm configurations will be included in the body of the worksheet the next time you open it. In fact, you can set alarms on tags before you create any Alarm worksheets at all; when you do create the worksheets, they will be automatically populated with alarm configurations according to their group numbers.

You cannot configure more than one alarm of the same type on a given tag, and each alarm configuration cannot belong to more than one group/worksheet.

If you make extensive changes to the tags database after you save an Alarm worksheet, it might not be possible to recreate the body of the worksheet the next time you open it. For example, if you copy all of the tags from the tags database (in Datasheet View) to a spreadsheet program, use that program to sort the tags, and then copy the tags back to the tags database, most or all of the tag properties will be reset in the process.