Rockwell Automation FactoryTalk View Site Edition Users Guide User Manual
Page 371
14
•
S
ETTING
UP
F
ACTORY
T
ALK
SYSTEM
AVAILABILITY
14–27
•
•
•
• •
14
•
Pla
ceho
lde
r
Optionally, you can specify an area name when you run the AlarmAcceptEdits
command. If you do this, only changes made in the specified area, since AlarmOn was last
run, will take effect. For details, click Help in the Command Wizard.
Example: Modifying HMI tag alarms in a redundant HMI server pair
To ensure that changes to HMI tag alarm properties are copied to the secondary server in a
redundant HMI server pair, follow these steps:
1. Modify the property. For example, change the severity for an analog alarm threshold.
2. Run the AlarmAcceptEdits command.
3. Replicate the change to the secondary HMI server. For instructions, see page 14-17.
How alarm property changes take effect
The following table lists the HMI tag alarm properties you can modify at run time, and the
effect each change will have, the next time AlarmAcceptEdits is run.
Use information in the table to ensure that the changes you make are reflected as
expected, in HMI tag alarm summaries on connected clients.
If you run AlarmAcceptEdits while a redundant HMI server pair is synchronizing alarm states, the
secondary HMI server will not contain the latest changes. To update the secondary server, you
must replicate changes made on the primary server. For details, see page 14-16.
If you replicate changes from the primary to the secondary HMI server before running the
AlarmAcceptEdits command, the primary and secondary HMI projects will not be synchronized.
The AlarmAcceptEdits command is for HMI tag alarms only. The command is not required to
effect online changes to alarm definitions in a Tag Alarm and Event Server. For information about
modifying FactoryTalk tag-based alarm properties, see the FactoryTalk Alarms and Events Help.
If this property
Is changed to this value
This is what happens when AlarmAcceptEdits is run
Alarmed
(Alarmed or Not Alarmed)
True
The newly alarmed tag is monitored for alarms.
Additionally, existing alarm events with the same name
as the newly alarmed tag are removed from HMI tag
alarm summaries.
False
Existing alarm transactions for the tag are removed from
HMI tag alarm summaries.