beautypg.com

Setting up alarms for hmi analog tags, Setting up alarms for hmi digital tags, Modifying hmi tag and alarm properties at run time – Rockwell Automation FactoryTalk View Site Edition Users Guide User Manual

Page 233

background image

11

S

ETTING

UP

HMI

TAG

ALARMS

11–21

• •

11

Pla
ceho

lde

r

Setting up alarms for HMI analog tags

These are the tasks involved in setting up alarms for HMI analog tags:

1. Set up the alarm threshold, and then choose the message to show when the threshold is

crossed.

2. Set up the messages that are sent when a tag goes out of alarm, and when an operator

acknowledges an alarm.

3. Set up advanced features, such as deadband and handshake.

For details about options in the Analog Alarm editor, click Help.

Setting up alarms for HMI digital tags

These are the tasks involved in setting up alarms for HMI digital tags:

1. Set up alarm states.

2. Set up the messages that are sent when a tag goes out of alarm, and when an operator

acknowledges an alarm.

3. Set up advanced features, such as handshake.

For details about options in the Digital Alarm editor, click Help.

Modifying HMI tag and alarm properties at run time

In a FactoryTalk View SE network distributed application, you can modify HMI tag and
alarm properties at run time, and have the changes take effect at connected clients, without
restarting the clients.

HMI tag properties can be modified in FactoryTalk View Studio, in the Tags editor, in the
HMI Tag dialog box (opened from the Tag Browser), or in the Tag Import & Export
Wizard.

HMI tag alarm properties can be modified in the Analog or Digital Alarms editors, opened
from the Tags editor. The AlarmAcceptEdits command must be run for alarm changes to
take effect.

In FactoryTalk View Studio, for a redundant network distributed application, you can also
replicate changes made at the primary server, to the secondary server.

For information about:

Modifying HMI tag properties, see page 14-23.

Modifying HMI tag alarm properties, see page 14-26.

Replicating changes from the primary to the secondary server, see page 14-16.