FT Alarms and Events System Configuration Guide
FT Alarms and Events System Configuration Guide
AlarmsandEvents
Any Rockwell Automation software or hardware not mentioned here is also a trademark, registered or
otherwise, of Rockwell Automation, Inc.
Other Trademarks ActiveX, Microsoft, Microsoft Access, SQL Server, Visual Basic, Visual C++, Visual SourceSafe,
Windows, Windows ME, Windows NT, Windows 2000, Windows Server-, Windows XP, Windows 7, and
Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or
other countries.
Adobe, Acrobat, and Reader are either registered trademarks or trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademarks of Oracle Corporation.
ControlNet is a registered trademark of ControlNet International.
DeviceNet is a trademark of the Open DeviceNet Vendor Association, Inc. (ODVA)
All other trademarks are the property of their respective holders and are hereby acknowledged.
Warranty This product is warranted in accordance with the product license. The product’s performance may be
affected by system configuration, the application being performed, operator control, maintenance, and
other related factors. Rockwell Automation is not responsible for these intervening factors. The
instructions in this document do not cover all the details or variations in the equipment, procedure, or
process described, nor do they provide directions for meeting every possible contingency during
installation, operation, or maintenance. This product’s implementation may vary among users.
This document is current as of the time of release of the product; however, the accompanying software
may have changed since the release. Rockwell Automation, Inc. reserves the right to change any
information contained in this document or the software at anytime without prior notice. It is your
responsibility to obtain the most current information available from Rockwell when installing or using
this product.
Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iii
Preface What you need to get started . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Required software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Recommended hardware and supported operating systems. . . . . . . . . . 2
Logix5000 controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Compatible firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Older controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
How to get the information you need . . . . . . . . . . . . . . . . . . . . . . . . 3
Chapter 4 Add a device server for Logix5000, PLC-5, or SLC 500 controllers . . 47
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
What you need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Follow these steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Add a device server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Chapter 6 Add a tag-based alarm server for Logix5000, PLC-5, SLC 500, or third-
party controllers61
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
What you need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Follow these steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Create an application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Add a data server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Add a Tag Alarm and Event Server . . . . . . . . . . . . . . . . . . . . . . . . . 68
Define alarm conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Next steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
iv
• • • • •
Contents
v
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
vi
• • • • •
Contents
vii
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
viii
Preface
Required software
The following software is required to configure and operate FactoryTalk Alarms and
Events services:
Software Version
1
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
Software Version
Logix5000 controllers
The Logix5000 controllers listed in the following table, support FactoryTalk Alarms
and Events services. When you use built-in alarm instructions in Logix5000
controllers, these controllers require a firmware update to a revision between 16.20
and 20. If you do not want to update the firmware in your controllers, use a Tag Alarm
and Event Server for software-based alarms and events. See “Decide what type of
alarm monitoring you need” on page 16.
Catalog number Name
1756-L61 ControlLogix Processor
1756-L62 ControlLogix Processor
1756-L63 ControlLogix Processor
1756-L64 ControlLogix Processor
1756-5555 5555 ControlLogix Processor
1768-L43 CompactLogix L43 Controller
1769-L31 CompactLogix L31 Controller
1769-L32C CompactLogix L32C Controller
1769-L32E CompactLogix L32E Controller
1769-L35CR CompactLogix L35CR Controller
1769-L35E CompactLogix L35E Controller
1794-L34 FlexLogix L34 Controller
1756-L61S ControlLogix Safety Processor
1756-L62S ControlLogix Safety Processor
2
• • • • •
Preface
Compatible firmware
The controller firmware revisions listed in the following table, are compatible with
FactoryTalk Alarms and Events services:
Controller Firmware revision
ControlLogix
CompactLogix L3x and L4x 16.20 to 20
DriveLogix
ControlLogix Redundant Systems 16.60 to 20
SoftLogix 16.03 to 20
Older controllers
These controllers also support FactoryTalk Alarms and Events services:
Logix5000 controllers that communicate with RSLinx Enterprise, using Tag
Alarm and Event Servers
PLC-5 and SLC 500 controllers that communicate with RSLinx Enterprise (or
RSLinx Classic to bridge from Ethernet to DH+ or DH-485 networks), using Tag
Alarm and Event Servers
Third-party PLCs that communicate with OPC Data Servers such as KEPWare,
using Tag Alarm and Event Servers
3
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
FactoryTalk View Site Edition User’s Guide (Available from the Help menu
when you run FactoryTalk View Site Edition.)
RSLinx Classic Online Help (for help with configuring drivers and creating
topics)
RSLinx Classic Quick Start Guide
RSLinx Enterprise Getting Results Guide
RSLinx Enterprise Online Help
4
Chapter 1
5
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
6
• • • • •
1 • Overview of FactoryTalk Alarms and Events services
7
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
Where to start
8
• • • • •
1 • Overview of FactoryTalk Alarms and Events services
9
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
10
• • • • •
1 • Overview of FactoryTalk Alarms and Events services
11
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
Tag-based alarm monitoring works like this (similar to HMI Tag Alarm
Monitoring):
12
• • • • •
1 • Overview of FactoryTalk Alarms and Events services
13
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
14
Chapter 2
15
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
16
• • • • •
2 • Plan your system
17
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
For more information about each software product, see the product Help.
Typical stand-alone system
To use FactoryTalk Alarms and Events with a local station application or a network
station application as part of a stand-alone FactoryTalk system, install all software on
the same computer. Use this diagram only as a starting point; your own system will
vary.
18
• • • • •
2 • Plan your system
19
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
20
Chapter 3
21
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
setting on each RSLinx Enterprise device shortcut. See Chapter 4, “Create a new
shortcut to the controller”.
For controllers with revision 20 or earlier, we recommend that you do not
change the default buffering time unless instructed by the Technical Support.
This release of FactoryTalk Alarms and Events does not support device based
alarm subscription to controllers with firmware revisions 21 or later.
22
• • • • •
3 • Define device-based alarms in Logix5000 controllers
23
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
24
• • • • •
3 • Define device-based alarms in Logix5000 controllers
4. At the top of the Examine-on instruction, click the question mark to select it. On
the File menu, click New Component, and then click Tag.
25
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
5. In the New Tag dialog box, type a name for the tag, choose BOOL as the data
type, and then click OK.
In our example, we named the tag alarm_active.
26
• • • • •
3 • Define device-based alarms in Logix5000 controllers
If you are using RSLogix 5000 version 20 or earlier, the instruction block is like
this:
2. Inside the alarm instruction, beside ALMD, select the question mark.
3. On the File menu, click New Component, and then click Tag.
4. In the New Tag dialog box, type a name for the digital alarm tag, and then click
OK.
In our example, we named the tag DigitalAlarm1.
27
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
3. In the New Tag dialog box, type a name for the tag, select BOOL as the data type,
and then click OK.
In our example, we named the tag DigitalAlarm1_Ack. For details about using the
New Tag dialog box, click Help.
If you are using RSLogix 5000 version 20 or earlier, the instruction block is like
this:
28
• • • • •
3 • Define device-based alarms in Logix5000 controllers
4. Create tags for the ProgReset, ProgDisable, and ProgEnable operands. When you
are finished, the alarm instruction should resemble the one shown here:
If you are using RSLogix 5000 version 20 or earlier, the instruction block is like
this:
29
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
30
• • • • •
3 • Define device-based alarms in Logix5000 controllers
If you are using RSLogix 5000 version 20 or earlier, the ALMD Properties dialog
box is like this:
To create a text message with embedded variables for each alarm, click the Browse
button beside the Message box. At run time, these messages appear in Alarm and
Event graphic objects, such as the Alarm and Event Summary. The maximum length
of an alarm message is 255 characters. When importing alarm messages, RSLogix
5000 will verify the message length and display a warning if the alarm message
exceeds the character limit.
31
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
Step 5: Download the program containing the ladder logic to the controller
1. If it is not already running, start RSLinx Classic to establish communications
between RSLogix 5000 v. 16, or later, and the controller.
2. On the RSLogix 5000 menu, click Communications > Who Active.
32
• • • • •
3 • Define device-based alarms in Logix5000 controllers
4. Click Download. At the prompt, click Download again. The controller is placed
in Program mode.
Step 6: Test the alarm instruction by switching to run mode and triggering
the alarm
1. On the RSLogix 5000 menu, click Communications > Run Mode. Click Yes to
switch the controller to run mode.
33
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
2. To trigger the alarm, right-click the contact on the rung (the one we named
“alarm_active”). On the context menu, click Toggle Bit. The contact should
change from a blue highlight to a green highlight.
34
• • • • •
3 • Define device-based alarms in Logix5000 controllers
2. In the left pane, expand the Tasks folder, right-click MainProgram, and then
click New Routine on the context menu.
3. In the New Routine dialog box, type a name for the routine. We used
alarm_active.
35
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
The new routine appears in the Tasks folder under MainRoutine and the routine
opens on the right side of the RSLogix 5000 window:
36
• • • • •
3 • Define device-based alarms in Logix5000 controllers
2. On the toolbar, click the ALMA button (shown at left) to add an Analog Alarm
block, as shown in the following illustration.
37
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
If you are using RSLogix 5000 version 20 or earlier, the Analog Alarm block is
like this:
38
• • • • •
3 • Define device-based alarms in Logix5000 controllers
3. Using the same Alarm objects on the Language Element toolbar, click the Input
Reference icon (shown at left). An Input Reference tag appears in the Function
Block editor:
4. Right-click the single question mark inside the symbol and then click New Tag.
39
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
5. In the New Tag dialog box, type a name for the tag and then click OK.
In this example, we used AnalogAlarm1.
The screen should resemble the one shown in the following illustration:
40
• • • • •
3 • Define device-based alarms in Logix5000 controllers
6. Connect the input reference block to the Input of the ALMA block, as shown in
the following illustration, by dragging the block’s contact point to the contact
point on the ALMA block.
41
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
42
• • • • •
3 • Define device-based alarms in Logix5000 controllers
If you are using RSLogix 5000 version 20 or earlier, the ALMA Properties dialog
box is like this:
To enter alarm messages and add variables for analog alarms, select the Messages
tab. To create a text message with embedded variables, click the Browse button
beside the Level field, or beside the Rate of Change field. At run time, alarm
messages are displayed in Alarm and Event graphic objects such as the Alarm and
Event Summary.
43
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
Step 4: Add a JSR instruction to the MainRoutine to run the function block:
1. Double-click MainRoutine to open it.
2. Right-click the first rung and then click Add Ladder Element on the context
menu.
3. In the Add Ladder Element dialog box, scroll down to the Program Control
folder and then double-click the folder to expand the list of controls.
44
• • • • •
3 • Define device-based alarms in Logix5000 controllers
45
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
46
Chapter 4
47
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
48
• • • • •
4 • Add a device server for Logix5000, PLC-5, or SLC 500 controllers
FactoryTalk Alarms and Events is not supported for use with FactoryTalk View
Machine Edition.
49
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
3. In the New/Open Site Edition (Local Station) Application dialog box, click the
New tab.
4. In the Application name field, type a name for the new local station application.
In this example, we named the application My Local Site.
5. Leave the Description field blank, or type a description for the application. For
example, you can use this field to record revisions to the application, or contact
information for technical support.
6. If it is not already selected, select the default language for the application. This is
the language in which you are creating the application.
7. Click Create.
50
• • • • •
4 • Add a device server for Logix5000, PLC-5, or SLC 500 controllers
8. In the Add Controller Instruction Faceplates dialog box, click Clear All and
then click OK.
If you have cleared the “Display this dialog when creating a new application” check
box, the Add Controller Instruction Faceplates dialog box does not open
automatically. To open it manually, in the Explorer window right-click the HMI
server and then select Add Controller Instruction Faceplates from the context
menu.
51
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
2. In the RSLinx Enterprise Server Properties dialog box, click the General tab, type
a name for the new server, and then click Apply.
In this example, we named the server FTAE Server.
3. If you plan to use tag-based alarms, skip the rest of the steps in this section, and go
on to “Create a new shortcut to the controller” on page 53. If you are using built-in
alarm instructions in Logix5000 controllers, on the Alarms and Events tab, select
the Enable alarm and event support check box.
52
• • • • •
4 • Add a device server for Logix5000, PLC-5, or SLC 500 controllers
4. Clear the Enable history check box and then click OK. For information about
historical logging, see Chapter 9, “Set up historical alarm and event logging”.
The new server is added to the My Local Site application:
53
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
2. In the Communication Setup dialog box, click the Add button, and then type a
name for the new shortcut. We used FTAE_Controller.
Some options in this dialog box might be different if you are using PLC-5 or SLC
500 controllers.
The warning icon beside the OK button indicates that changing values in this
dialog box at run time can cause unexpected results. For details, see Help.
3. Skip this step if you do not plan to use Logix5000 controllers with built-in alarm
instructions. In the Enable list, click Yes to enable Alarms and Events:
54
• • • • •
4 • Add a device server for Logix5000, PLC-5, or SLC 500 controllers
4. On the Primary tab, expand the list of networks and devices until the controller
you plan to use is visible, and then click the controller.
5. To set the path to the primary controller, click the Apply button.
6. To save the shortcut configuration and close the Communication Setup dialog
box, click OK.
FactoryTalk Alarms and Events server redundancy is only supported in network
station applications and network distributed applications.
55
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
56
Chapter 5
57
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
58
• • • • •
5 • Add an OPC Data Server for third-party controllers
2. In the OPC Data Server Properties dialog box, type a name for the server. This
example uses My OPC Server.
59
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
3. Beside the OPC Server name (ProgID) field, click the Browse button.
4. In the Available OPC Data Servers dialog box, select RSLinx OPC Server, and
then click OK.
5. Click OK again to close the OPC Data Server Properties dialog box.
6. Next, add a Tag Alarm and Event Server and define alarm conditions. See Chapter
6, “Add a tag-based alarm server for Logix5000, PLC-5, SLC 500, or third-party
controllers”.
7. If your FactoryTalk network station application or network distributed application
plan calls for data redundancy, you will want to configure your tag-based alarm
server for redundancy. We recommend completing this step after the FactoryTalk
application is fully configured and all HMI features have been tested using non-
redundant servers. Adding data server redundancy does not affect the
configuration of the graphic displays in the HMI application.
FactoryTalk Alarms and Events server redundancy and data server redundancy
are only supported in network station applications and network distributed
applications.
60
Chapter 6
61
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
62
• • • • •
6 • Add a tag-based alarm server for Logix5000, PLC-5, SLC 500, or third-party controllers
Create an application
In this section, you will create a Rockwell Automation device server (RSLinx
Enterprise) and then configure it to subscribe to alarms that will be detected by a
Logix5000 controller. In this example, the Rockwell Automation device server
(RSLinx Enterprise) is used as a data server for tag values, not as an alarm server.
Step 1: Create an application in FactoryTalk View Studio
If you created a local station application previously, you can skip this step.
Instead, open the existing application by following instructions in Chapter 5, “Open
an existing application in FactoryTalk View Studio”.
FactoryTalk Alarms and Events is not supported for use with FactoryTalk View
Machine Edition.
63
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
3. In the New/Open Site Edition (Local Station) Application dialog box click the
New tab.
4. In the Application name field, type a name for the new application. In this
example, we named the application My Local Site.
5. Leave the Description field blank, or type a description for the application. For
example, you can use this field to record revisions to the application, or contact
information for technical support.
6. If it is not already selected, select the default language for the application. This is
the language in which you are creating the application.
7. Click Create.
64
• • • • •
6 • Add a tag-based alarm server for Logix5000, PLC-5, SLC 500, or third-party controllers
8. In the Add Controller Instruction Faceplates dialog box, click Clear All and
then click OK.
If you have cleared the “Display this dialog when creating a new application” check
box, the Add Controller Instruction Faceplates dialog box does not open
automatically. To open it manually, in the Explorer window right-click the HMI
server and then select Add Controller Instruction Faceplates from the context
menu.
In this example a device server (RSLinx Enterprise) is added to the application to act
as a data server.
65
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
1. In the Explorer window, right-click the application (My Local Site). On the
context menu, point to Add New Server, and then click Rockwell Automation
Device Server (RSLinx Enterprise).
2. In the RSLinx Enterprise Server Properties dialog box, click the General tab,
type a name for the server, and then click Apply. In this example, we named the
server FTAE Server.
The new server is added to the My Local Site application:
1. In the Explorer window, double-click the new RSLinx Enterprise server (in our
example we named it FTAE Server) and then double-click Communication Setup.
66
• • • • •
6 • Add a tag-based alarm server for Logix5000, PLC-5, SLC 500, or third-party controllers
67
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
2. In the Communication Setup dialog box, click the Add button and then type a
name for the new shortcut. We used FTAE_Controller.
Some options in this dialog box might be different if you are using PLC-5 or SLC
500 controllers.
The warning icon beside the OK button indicates that changing values in this
dialog box at run time can cause unexpected results. For details, see Help.
3. On the Primary tab, expand the list of networks and devices until the controller is
visible, and then click the controller. To set the path to the primary controller,
click the Apply button.
4. To save the shortcut configuration and close the Communication Setup dialog
box, click OK.
68
• • • • •
6 • Add a tag-based alarm server for Logix5000, PLC-5, SLC 500, or third-party controllers
3. Type a name for the server, and then click OK. In this example, we used TagAE.
4. On the Priorities and History tab, clear the Enable history check box.
The Priorities and History tab is used to configure alarm and event logging.
Chapter 9, “Set up historical alarm and event logging” describes how to set up
alarm logging for an Tag Alarm and Event Server.
5. To create the Tag Alarm and Event Server and close the dialog box, click OK.
69
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
2. In the Alarm and Event Setup dialog box, click the New button on the toolbar,
and then click Digital.
3. In the Digital Alarm Properties dialog box, type a name for the alarm. In this
example we used Valve1FTO.
4. To select an Input Tag for the alarm, click the browse button, and then expand the
folder folder tree until you can select the online tag you plan to monitor.
70
• • • • •
6 • Add a tag-based alarm server for Logix5000, PLC-5, SLC 500, or third-party controllers
5. Select the tag you plan to monitor and then click OK. In this example we used
Valve1FTO_alm.
6. In the Digital Alarm Properties dialog box, type a message. In this example we
typed ‘The valve failed to open.’ in the Message field.
You can also embed variables within the message. For details, click the Help
button on any tab in the Alarm Setup dialog box.
71
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
8. To save the alarm and start monitoring for the alarm condition, click the Save
button.
Next steps
1. Define additional alarms.
2. After you define alarms, you can add FactoryTalk Alarm and Event objects to
graphic displays. See Chapter 7, “Set up graphic displays”.
3. If your FactoryTalk network station application or network distributed application
plan calls for data redundancy, you will want to configure your tag-based alarm
server and tag data servers for redundancy. We recommend completing this step
after the FactoryTalk application is fully configured and all HMI features have
been tested using non-redundant servers. Adding data and alarm server
redundancy does not affect the configuration of the graphic displays in the HMI
application. See “Configure redundancy for alarms and events” on page 143 for
more information.
FactoryTalk Alarms and Events redundancy and data server redundancy are only
supported in network station applications and network distributed applications.
72
Chapter 7
73
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
74
• • • • •
7 • Set up graphic displays
75
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
A blank display appears in the workspace. Next, add Factory Talk Alarm and
Event objects to the graphic display.
You can use FactoryTalk Security to control which users can acknowledge, enable,
disable, reset, suppress, shelve, or unshelve alarms at run time in an application (or in
an area). To do this, right-click the application (or area) and then click Security on the
context menu. For details, see the FactoryTalk Security System Configuration Guide.
Step 1: Add an Alarm Summary to a graphic display
1. On the Objects menu, point to Alarm and Event, click Summary (or on the
toolbar, click the Alarm and Event Summary button, as shown at left), and then
place the cursor approximately where the object is to be on the display.
2. Hold the left mouse button down and drag it to create a rectangle the size that the
Alarm and Event Summary object should be.
76
• • • • •
7 • Set up graphic displays
3. When the object is the correct size, release the left mouse button. The Alarm and
Event Summary object is drawn on the display.
Step 2: Change the settings of the Alarm and Event Summary display
1. Right-click anywhere in the display and then, click Display Settings on the
context menu.
2. In the Display Settings dialog box, on the Properties tab, make the following
changes and then click OK.
Under Cache After Displaying, click Yes and then select the Always
Updating check box.
77
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
When you set Cache After Displaying to Yes, the display stays in memory
cache when you close it. This shortens the time required to open the graphic
display the next time you do it.
When you select the Always Updating check box, the display continues to be
updated with changes in alarm states when it is cached. This shortens the time
necessary to update the Alarm and Event Summary with current alarms when
you open it again.
If Cache After Displaying is set to No, and the Always Updating check box
is cleared, every time you close the graphic display, all alarms are removed
from the Alarm and Event Summary. When you re-open the graphic display,
the Alarm and Event Summary is blank, and then begins to receive the most
recent alarms when they occur.
Clear the Title Bar check box.
Select the Size to Main Window at Runtime check box.
Select the Allow Display to be Resized check box.
Under When Resized, select the Scale check box is if it is not already
selected.
78
• • • • •
7 • Set up graphic displays
79
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
2. Hold the left mouse button down and drag it to create a rectangle the size that the
Alarm and Event Banner should be.
3. When the object the correct size, release the left mouse button. The Alarm and
Event Banner object is drawn on the display.
4. Resize the graphic display so that the Banner fills the graphic display (do not
leave white space). We do this because the Banner displays no more than five
alarms at a time.
80
• • • • •
7 • Set up graphic displays
This opens the Command Wizard where you will create a command to start the
Alarm and Event Summary graphic display from the Alarm and Event Banner.
3. Scroll down the list of commands on the right side of the wizard, select Display,
and then click Next.
81
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
5. Select the Window Position check box. Scroll down the list on the right and then
click Centered of the screen.
6. Click Finish to save the Display command and add it to the Alarm and Event
Banner Properties dialog box.
82
• • • • •
7 • Set up graphic displays
Step 4: Change the display settings for the Alarm and Event Banner display
1. On the Edit menu, click Display Settings.
2. In the Display Settings dialog box, on the Properties tab, make the following
changes, and then click OK:
83
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
84
• • • • •
7 • Set up graphic displays
2. To open the Command Wizard, double-click anywhere in the body of the macro
editor.
3. In the Command Wizard, scroll down the list of commands on the right side of the
wizard, click Display, and then click Next.
85
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
5. Select the Window Position check box. Scroll down the list on the right and then
select Docked to the bottom.
6. To save the Display command and add it to the macro, click OK.
Step 2: Save the macro
1. On the File menu, click Save.
2. In the Save dialog box, type a name for the new macro and then click OK. In this
example, we used Start Alarm and Event Banner.
86
• • • • •
7 • Set up graphic displays
87
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
4. If necessary, resize either the Alarm and Event Summary object or the graphic
display to expose enough white space at the top, bottom, or on one side to add a
rectangle object that will be the alarm status indicator.
88
• • • • •
7 • Set up graphic displays
In the preceeding expression, “*” means include all alarms that are in the same
location (area) as the HMI server. If the preceeding expression is used in a network
station application or network distributed application with areas, the expression
would include all alarms from the alarm servers that are located in the same area
as the HMI server.
If you want to include alarms from other areas, use the absolute path syntax. For
example, (“/AreaName::*”).
If you type the expression instead of composing it, skip to Step 4: “Set up colors
for the alarm states” on page 93 to apply colors to each state.
89
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
3. In the Expression Editor, click the If button and then click If to add the IF
condition.
90
• • • • •
7 • Set up graphic displays
and are in the In Alarm and Unacknowledged state. Next, move the cursor to the
right of the closing parenthesis.
To count the number of instances of a specific alarm, you can type a tag name
instead of the asterisk.
To include alarms from other areas, use the absolute path syntax. For example,
(“/AreaName::*”).
8. Click Relational and then click > GT for greater than.
9. In the Expression box, type 0, click If and then click Then to add a THEN
condition.
This completes the IF condition: “If the number of In Alarm, Unacknowledged
alarms is greater than 0 . . .”
91
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
10. In the Expression box, type 0, click If and then click Else to add an ELSE
condition.
This completes the THEN condition: “If the number of In Alarm,
Unacknowledged alarms is greater than 0, then animate the rectangle to show the
colors for state 0.”
11. Follow the same process, substituting the necessary selections to add the
remaining two expressions, and then click OK.
If AE_InAlmAckedCount( "*" ) > 0 Then 1 Else (animates the rectangle to show
the colors for state 1)
If AE_NormalUnackedCount( "*" ) > 0 Then 2 Else 3 (animates the rectangle to
show the colors for state 2. If none of the conditions are true, the expression
animates the rectangle to show the colors for state 3.)
92
• • • • •
7 • Set up graphic displays
93
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
2. Right-click one of the alarms, and then click Ack All on the context menu.
Because all active alarms have been acknowledged, the rectangle changes to a
steady red.
94
• • • • •
7 • Set up graphic displays
4. When you are finished, on the View menu, click Edit Display, or click the Edit
Display button (shown at left) on the toolbar.
Next steps
Do one of the following:
Use the displays you just created to monitor and interact with alarms and events.
See Chapter 8, “Monitor and interact with alarms at run time”.
Set up historical alarm and event logging. See Chapter 9, “Set up historical alarm
and event logging”.
95
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
96
Chapter 8
97
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
98
• • • • •
8 • Monitor and interact with alarms at run time
99
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
3. In the FactoryTalk View SE Client Configuration Name dialog box, type a name
for the configuration file. In this example, we used Alarms and Events Demo.
Keep the default path for the configuration file and click Next.
For details about using the FactoryTalk View Site Edition Client Wizard, click the
Help button in the wizard.
4. In the FactoryTalk View SE Client Application Type dialog box, select Local
Station and then click Next.
100
• • • • •
8 • Monitor and interact with alarms at run time
5. In the FactoryTalk View SE Client Application Name dialog box, select the name
of the application you plan to connect to, and then click Next.
In this example, we used the My Local Site application that we created in Chapter
7, “Set up graphic displays”.
6. In the FactoryTalk View SE Client Components dialog box, select the FactoryTalk
View components that run when the FactoryTalk View Site Edition Client starts.
In the Startup macro list, select Start Alarm and Event Banner, and then click
Next.
101
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
7. In the FactoryTalk View SE Client Window Properties dialog box, configure how
the FactoryTalk View SE Client window will look at run time. In this example, we
entered Show Me Alarms in the Title bar text field. At run time, this text is
displayed at the top of the Client window. Do not change any of the other settings
in this dialog box. Click Next.
8. In the FactoryTalk View SE Client Auto Logout dialog box, you can configure the
Client to log out automatically after a period of inactivity. In this example, we
accepted the default setting. Click Next.
102
• • • • •
8 • Monitor and interact with alarms at run time
9. In the FactoryTalk View SE Client Completion Options dialog box, select Save
configuration and open FactoryTalk View SE Client now, and then click
Finish.
The Client window opens with the Alarm and Event Banner docked at the bottom.
103
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
Step 2: Open the Alarm and Event Summary from the Alarm and Event
Banner
1. In the Alarm and Event Banner, click the Alarm and Event Summary button
(shown at left). The Alarm and Event Summary opens, and is similar to the
following graphic display.
104
• • • • •
8 • Monitor and interact with alarms at run time
the connection status of the Tag Alarm and Event Server — whether connected or
disconnected from the Alarm and Event Banner. The green icon shows that the
Tag Alarm and Event Server is connected. When disconnected, the icon flashes
red.
the number of alarms that are In Alarm and Unacknowledged
the number of alarms that are In Alarm and Acknowledged
the number of alarms that are Normal and Unacknowledged
the number of alarm faults
The icons in the body of the Banner list:
To see all of the possible priorities and alarms states for the Alarm and Event objects,
see FactoryTalk Help. On the Windows Start menu, click Start, point to All
Programs > Rockwell Software > FactoryTalk Tools and then click FactoryTalk
Help.
105
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
Acknowledge an alarm
When you acknowledge an alarm it does not correct the condition causing the alarm,
but indicates that an operator is aware of the alarm.
The Digital Alarm Properties, Level Alarm Properties, and Deviation Alarm
Properties dialog boxes each contain a Control Tags tab that allows you to
acknowledge alarms by using tags in the controller. You can see the acknowledged
alarms displayed in the Alarm and Event client objects.
At runtime, the alarm state changes to Acknowledged when the remote
acknowledge tag value is changed to positive.
Functions of the alarm importing and exporting were modified to support the
new remote acknowledgement feature.
See the Help for more information on using the Control Tags tab.
A single tag might have several alarm conditions In Alarm. Each alarm condition must
be acknowledged separately. For example, a tag that monitors a temperature might
trigger HI and HIHI alarm conditions by the time it is acknowledged. The alarm could
also go into and out of alarm several times before it is acknowledged.
Previous occurrences of an alarm that have gone Out of Alarm and then back In Alarm
cannot be acknowledged. These old occurrences are called “out of scope” and are
displayed in the alarm list with a different icon. When the most recent occurrence of
an alarm is acknowledged, previous occurrences are removed from the alarm list.
To acknowledge the selected alarm:
In the Alarm and Event Summary event list, do one of the following:
Select the alarms you want to acknowledge, and then click the Acknowledge
selected alarm button, shown at left.
Select the alarms you want to acknowledge, right-click the selected alarms, and
then click Ack on the context menu.
106
• • • • •
8 • Monitor and interact with alarms at run time
2. In the Acknowledge Alarm with Comment dialog box, type a comment, and
then click Acknowledge. If historical logging is set up, the comment is displayed
in the Alarm and Event Log as part of the Tracking event that is generated from
the Acknowledge command.
You can view the last comment that was entered for an operation (for example,
ack, disable, suppress) in the Alarm Details dialog box. To view a comment
associated with an alarm state, select an alarm and then click the Show details for
the selected alarm button on the toolbar. In the Alarm Details dialog box, expand
an alarm state (Disabled, Suppressed, Acknowledged, and so on) to view the
comment associated with that state.
107
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
Right-click one of the alarms and then click Ack Page on the context menu.
108
• • • • •
8 • Monitor and interact with alarms at run time
Unlike a silenced alarm, a disabled alarm does not trigger the alarm bell in the Alarm
and Event Banner if the alarm condition occurs again after the alarm was disabled.
Disable alarms that are related to equipment that is being shut down or serviced.
Enabled alarms
When an alarm is enabled, the operator is notified when the alarm condition occurs.
Enabled alarms sound the alarm bell, and continue appearing as new events in the
Alarm and Event Summary, unless they are suppressed.
You can use FactoryTalk Security to control who can disable or suppress alarms. If a
user attempts to perform an operation for which they do not have the required
security rights, the operation will fail and a message will be displayed stating that
the user has insufficient rights to perform the operation. To add another level of
security, the Alarm and Event Summary can be configured not to show the toolbar
buttons, which also hides those operations on the context menu.
109
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
2. In the Disable Alarm dialog box, type a comment (for example, to explain why
the alarm is disabled) and then click Disable.
This comment is stored with the alarm and is logged to the Comment field in the
Alarm and Event Log, which you can view using the Alarm and Event Log
Viewer.
Any alarms you disable stay in that state until you enable them again. You must use
the Alarm Status Explorer to enable alarms.
110
• • • • •
8 • Monitor and interact with alarms at run time
To enable an alarm:
1. In the Alarm and Event Summary window, do one of the following:
If it is visible on the toolbar, click the Display the Alarm Status Explorer
button.
If the toolbar button is not visible, right-click an alarm in the Alarm and Event
Summary event list, and then click Alarm Status on the context menu.
2. In the Alarm Status Explorer window, select the alarms you want to enable and
then click the Enable selected alarm button.
Any alarms you enable stay in that state until you disable them again.
For details about the other features of the Alarm Status Explorer, click Help in the
dialog box.
111
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
112
• • • • •
8 • Monitor and interact with alarms at run time
2. In the Suppress Alarm window, type a comment, to explain why you suppressed
the alarm, and then click Suppress.
This comment is stored with the alarm and is logged to the Comment field in the
Alarm and Event Log, which you can view using the Alarm and Event Log
Viewer.
Unsuppress an alarm
Unsuppress an alarm that was previously suppressed if an alarm that was not needed
temporarily now needs to be monitored again. For example, an operator might have
suppressed an alarm because the alarm was caused by another alarm that an operator
was already attending to.
An unacknowledged suppressed alarm is displayed in the Alarm and Event Summary.
To unsuppress an alarm:
1. In the Alarm and Event Summary window, right-click an alarm and then click
Alarm Status on the context menu.
113
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
2. In the Alarm Status Explorer window, select the alarm or alarms you want to
unsuppress, and then click the Unsuppress selected alarm button on the toolbar.
You can filter alarm sources to make it easier to find the alarm you want. In the
Name box, type all or part of an alarm name, or select an alarm status from the
list. You can use the * and ? wildcard characters in the filter. For details about
filtering alarm sources, see FactoryTalk Help. On the Windows Start menu, click
Start, point to All Programs > Rockwell Software > FactoryTalk Tools and then
click FactoryTalk Help.
3. In the Unsuppress Alarm dialog box, type a comment to explain why the alarm is
unsuppressed, and then click Unsuppress.
This comment is stored with the alarm and is logged to the Comment field in the
Alarm and Event Log, which you can view using the Alarm and Event Log
Viewer if historical logging has been configured.
For details about the other features of the Alarm Status Explorer, click the Help button
in the dialog box.
114
• • • • •
8 • Monitor and interact with alarms at run time
A shelved alarm is displayed in the Alarm and Event Summary or Alarm Status
Explorer. However, a shelved alarm is not displayed in the Alarm and Event Banner.
Disable an alarm instead of shelving it if you want to completely turn off the alarm
detection logic for the alarm source, and prevent the alarm from being detected. See
“Disable or enable an alarm” on page 109 for more information.
To shelve an alarm:
1. In the Alarm and Event Summary event list, do one of the following:
Select the alarm you want to shelve and click the Shelve selected alarm
button on the toolbar.
Right-click the alarm you want to shelve and select Shelve.
115
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
Field Description
Alarm name Shows the name of the selected alarm.
If multiple alarms are selected, it is displayed as
"Multiple (x alarms selected)" where x is the total
count of selected alarms.
Shelve duration Specifies the period of time the alarm should be
shelved. Once the shelve duration expires, the alarm is
unshelved. The value must be a whole number.
Default: 1
Minimum: 1
Maximum: 2147483647
Comment (optional) Specifies the reason for shelving the alarm.
The default value is empty. The maximum length is
512 characters.
This comment is stored with the alarm and is logged to
the UserComment field in the alarm database, which
you can view using the Alarm and Event Log Viewer.
To unshelve an alarm:
If alarms that were previously shelved need to be monitored again, you can unshelve
the specified alarms in the Alarm Status Explorer.
116
• • • • •
8 • Monitor and interact with alarms at run time
1. In the Alarm and Event Summary window, right-click an alarm and then click
Alarm Status on the context menu.
2. In the Alarm Status Explorer window, select the alarm or alarms you want to
unshelve, and then click the Unshelve selected alarm button on the toolbar.
3. In the Unshelve Alarm dialog box, enter a comment to explain why the alarm is
unshelved and then click Unshelve.
117
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
The comment is stored with the alarm and is logged to the Comment field in the
Alarm and Event Log, which you can view using the Alarm and Event Log
Viewer if historical logging has been configured.
You can also unshelve all shelved alarms in the Alarm and Event Summary:
1. In the Alarm and Event Summary event list, do one of the following:
On the toolbar, click the Unshelve all alarms button.
Right-click and select Unshelve All.
2. The Unshelve All Alarms dialog box displays. Enter a comment to explain why
the alarms are unshelved and then click Unshelve All.
118
Chapter 9
Use the Alarm and Event Log Viewer to display entries corresponding to all event
types or to filter the events you want to view. Alarms and events generated during run
time can be logged to a Microsoft SQL Server database.
Simple Events are not supported in this release. A simple event describes a simple
occurrence in the system, such as failure to access a computer or device.
Condition-related events — those that relate to changes in alarm state —and
tracking-related events — those that monitor audited changes to the system — are
supported in this release.
To set up historical alarm and event logging, follow these steps. Each step is explained
in detail in this chapter.
Confirm that the Microsoft SQL Server software is installed.
Add a database definition to your FactoryTalk system.
Associate a database definition with an alarm and event server.
Add an Alarm and Event Log Viewer object to a graphic display.
Run the FactoryTalk View Site Edition Client software and then monitor the
graphic display.
119
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
120
• • • • •
9 • Set up historical alarm and event logging
121
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
122
• • • • •
9 • Set up historical alarm and event logging
3. In the New/Open Site Edition (Local Station) Application dialog box, click the
Existing tab, and then select the My Local Site application that you created in
Chapter 4, “Add a device server for Logix5000, PLC-5, or SLC 500 controllers”.
2. In the Alarm and Event Historian Database Properties dialog box, configure
properties for the new database definition.
In this example, we used FTAE_History for the definition name and database
name, FTAE_Historian for the database user name, as well as password for the
123
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
password. Select the version of SQL Server you are using. For details, click Help
on the dialog box.
3. Click the Advanced tab. The system will attempt to create the database, the user
account, and the tables that are necessary to store the alarm and event information.
124
• • • • •
9 • Set up historical alarm and event logging
If the database or user does not already exist in SQL Server, you are prompted to
create them. Click Yes.
4. Configure the settings for the Alarm and Event Historian Database.
If the connection to the database is lost, alarm and event information will continue
to be cached to files. After the connection is restored, the cached information will
be sent to the database.
5. When you finish, click OK. If you are prompted to create the database, click Yes.
The database definition is added to the Databases folder and is ready for use.
125
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
3. In the New/Open Site Edition (Local Station) Application dialog box, click the
Existing tab, and then select the My Local Site application that you created in
Chapter 4, “Add a device server for Logix5000, PLC-5, or SLC 500 controllers”.
2. Right-click the alarm server named FTAE Server that you created in Chapter 4,
“Add a device server for Logix5000, PLC-5, or SLC 500 controllers”. On the
context menu, click Properties.
126
• • • • •
9 • Set up historical alarm and event logging
3. For an RSLinx Enterprise Device Server, do the following and then click OK:
In the RSLinx Enterprise Server Properties dialog box, click the Alarms
and Events tab.
Under Alarm and Event History, select the Enable history check box.
In the Database definition list, select a definition (for this example, we used
FTAE_History).
127
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
4. For a Tag Alarm and Event Server, do the following and then click OK:
In the Tag Alarm and Event Server Properties dialog box, click the
Priorities and History tab.
Under Alarm History, select the Enable history check box.
In the Database Definition list, select a definition.
128
• • • • •
9 • Set up historical alarm and event logging
2. If necessary, resize the graphic display to about the same size as the one you
created for the Alarm and Event Summary.
Step 3: Add an Alarm and Event Log Viewer object to the display
1. On the Objects menu, point to Alarm and Event and then click Log Viewer (or
click the Alarm and Event Log Viewer toolbar button, as shown at left).
2. Hold the left mouse button down and drag the mouse to create a rectangle that is
the size required for the Alarm and Event Log Viewer object.
129
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
3. When the object is the correct size, release the left mouse button. The Alarm and
Event Log Viewer object is drawn on the graphic display.
Step 4: Configure the properties of the Alarm and Event Log Viewer
1. To open the Alarm and Event Log Viewer Properties dialog box, double-click
the Alarm and Event Log Viewer object.
2. On the General tab, select the alarm log whose entries you want to view. In the
previous example, we selected FTAE_History. This is the SQL database we
created in “Associate a database definition with an alarm server” on page 125.
3. Click the Columns tab, and then clear the Area check box.
4. On the other tabs, set properties to customize the Log Viewer display, as desired.
For details, click Help in the dialog box.
5. When you are finished, click OK to close the dialog box.
130
• • • • •
9 • Set up historical alarm and event logging
Create a button to open the Alarm and Event Log Viewer display
We will add a button to open the Alarm and Event Log Viewer display in the same
FactoryTalk View Client window as the Alarm and Event Banner display.
Step 1: Create a new graphic display
1. In the Explorer window, expand the Graphics folder, right-click Displays, and
then click New.
2. If necessary, resize the graphic display to about the same size as the one you
created for the Alarm and Event Summary.
131
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
2. In the Command Categories pane on the left, expand Graphics > Graphic
Displays > Navigation.
3. In the list of commands on the right, click Display, and then click Next.
132
• • • • •
9 • Set up historical alarm and event logging
4. In the File list, select the name of the graphic display that is to open when the
button is clicked.
In this example, we want the button to start the Alarm and Event Log Viewer, so
we select Alarm and Event Log Viewer.
5. To close the Command Wizard, click Finish. In the Button Properties dialog
box, the command Display “Alarm and Event Viewer /CC” appears in the Press
action box.
133
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
7. In the Caption box, type Run the Alarm and Event Log Viewer. Press the Enter
key after “Alarm” so that the text wraps to the next line. This is the text that will
appear on the button.
8. Click OK to save the button configuration. The button is drawn on the graphic
display.
134
• • • • •
9 • Set up historical alarm and event logging
2. In the Display Settings dialog box, make the following changes on the Properties
tab and then click OK:
Clear the Title Bar check box.
Select the Size to Main Window at Runtime check box.
Select the Allow Display to be Resized check box.
Under When Resized, select Scale option if it is not already selected.
135
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
5. Select the Window Position check box. In the list of window positions, click
Docked to the Top.
136
• • • • •
9 • Set up historical alarm and event logging
6. To save the configuration and display it in the macro editor, click Finish.
137
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
5. In the Launch FactoryTalk View SE Client dialog box, select Alarms and Events
Demo.cli and then click OK.
138
• • • • •
9 • Set up historical alarm and event logging
The FactoryTalk View SE Client opens after a few moments. The button appears
at the top of the window and the Alarm and Event Banner appears at the bottom.
139
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
6. Click the Run Alarm and Event Log Viewer button to make the Log Viewer
appear in the middle of the Client window:
7. Click the Run Alarm and Event Summary button on the Banner display at the
bottom of the window. The Summary display replaces the Log Viewer.
140
• • • • •
9 • Set up historical alarm and event logging
141
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
142
Chapter 10
143
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
Existing alarm servers and tag data servers can be configured to support redundancy if
the distributed system supporting your FactoryTalk application has been adequately
planned and prepared beforehand.
If favor current is selected and a redundant switchover occurs, the secondary server
remains active in the application even after the primary server is recovered and
available once again.
Favor current is the default behavior. When it is selected you can perform manual
switchovers from primary to secondary and back again. This can be useful for testing
redundant applications. You can change this selection at any time.
You can change the redundant server configuration from favor current to favor
primary any time that both servers are running and connected to the network station
application or network distributed application.
144
• • • • •
10 • Configure redundancy for alarms and events
145
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
146
• • • • •
10 • Configure redundancy for alarms and events
147
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
3. In the New/Open Site Edition (Network Distributed) Application dialog box with
the Existing tab selected, under the heading Application Name, select the name of
the existing application. In this example, we named the application My Network
App.
148
• • • • •
10 • Configure redundancy for alarms and events
4. Click Open.
4. Select the name of the secondary server computer in the Select Computer dialog
box and then click OK.
You may want to select Favor current to use manual switchover to test the
redundant pair. You can change the selection when testing is complete.
5. In the Redundancy tab, Continue using the secondary server even when the
primary server becomes available again is selected by default. This selects
favor current behavior. If you want favor primary behavior, select Switch over
to primary server when it becomes available again.
3. To set the path to the secondary controller, click the Apply button.
4. To save the shortcut configuration and close the Communication Setup dialog
box, click OK.
149
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
4. Click Open.
3. In the Tag Alarm and Event Server Properties dialog box, click the
Redundancy tab.
4. Select the Provide redundancy using a secondary server check box.
5. Select the secondary server computer from the computer list and then click OK.
If your distributed network application has been planned and implemented
beforehand as recommended, then the secondary server computer name will be
listed in the Select Computer dialog box.
150
• • • • •
10 • Configure redundancy for alarms and events
6. In the Tag Alarm and Event Server Properties dialog box, the switchbackup option
Continue using the secondary server even when the primary server becomes
available again is selected by default. This selects favor current behavior. If you
want favor primary behavior, click the option Switch over to primary server
when it becomes available again.
You may want to select Favor current to use manual switchover to test the
redundant pair. You can change the selection later, if necessary, once testing is
completed.
151
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
2. To close the Server Status dialog box without making any changes, click Cancel.
152
Appendix A
For more detailed information, see the FactoryTalk View Site Edition Help in
FactoryTalk View Studio.
153
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
154
• • • • •
A • Getting started with language switching
155
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
156
• • • • •
A • Getting started with language switching
When translating to or from Unicode character sets (for example, Asian languages),
you must export and then import the RSLogix 5000 tag database as a .txt file. The
.csv format does not support Unicode character sets. This limitation does not apply
to Tag Alarm and Event Servers.
The last line of text in the file is the alarm definition. The first element from the
left is the instruction type (ALMMSG:) and the language string for the alarm
message (en-us for English in the United States).
The alarm message text appears as the fourth element from the left (“Tank
Temperature is High”).
2. Copy the ALMMSG line and paste it at the end of the file.
3. Change en-us to it-it (for Italian in Italy), and then change the alarm message text
to read, “La temperatura del serbatoio è alta”.
4. Paste another copy of the ALMMSG line at the end of the file.
157
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
5. Change en-us to de-de (for German in Germany), and change the alarm message
text to read, “Hohe Tanktemperatur!”.
158
• • • • •
A • Getting started with language switching
159
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
2. Open the Project Documentation Language dialog box, click the Documentation
Language Configuration icon or click Documentation Languages on the Tools
menu.
160
• • • • •
A • Getting started with language switching
5. Select the languages to include in the localization file and then click Next. For
example, select German (Germany) and Italian (Italy) if the project
documentation will be translated into German and Italian.
6. To add the configuration information to the localization file, click Next.
7. Specify the name and location of the exported localization file and then click
Export.
8. Click OK.
The first column contains the instruction type ALMMSG. Column C is labeled
KEY:en-US [English (United States)] and the alarm message is displayed in
English.
Column D is labeled de-DE [Deutsch (Deutschland)], and Column E is labeled
it-IT [italiano (Italia)]. These are the languages you selected for the export.
2. Type, “Hohe Tanktemperatur!” in column D in the same row that displays “Tank
Temperature is High”.
3. Type “La temperatura del serbatoio è alta” in column E in the same row that
displays “Tank Temperature is High”.
4. To save the file, click Save on the File menu.
161
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
162
• • • • •
A • Getting started with language switching
2. In the Application Type Selection window, select View Site Edition (Local
Station) and then click Continue.
3. In the New/Open Site Edition (Local Station) Application dialog box, click the
Existing tab, select the application you created in Chapter 4, “Add a device server
for Logix5000, PLC-5, or SLC 500 controllers” (we used My Local Site).
4. In the Language list, select the language in which you are creating your
application (in this example, English (United States), en-US), and then click
Open.
163
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
164
• • • • •
A • Getting started with language switching
4. In the Digital Alarm Properties dialog box, in the Name box, type
TankTempThreshold.
165
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
5. In the Input Tag field, type system\Second. This tag uses the second count from
the computer’s internal clock to trigger the alarm. You can also click the Browse
button beside the Input Tag field to select the system\Second tag and then click
OK.
6. In the Digital Alarm Properties dialog box, in the Condition list, select
Input = 0. This triggers the alarm every time the value of the system\Second tag is
0 — which happens every minute.
7. In the Message field, type Tank Temperature is High, and then click OK.
166
• • • • •
A • Getting started with language switching
8. Close the Alarm and Event Setup editor and save your changes.
When the Display undefined strings using the default language check box is
selected, any strings that are not defined in the current language are displayed in
the default language at run time.
When this check box is not selected, any strings that are not defined in the current
language are displayed as question marks (???) at run time.
167
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
3. In the Add Language dialog box, click German (Germany) and then click OK.
4. In the Language Configuration dialog box, click Add to add the next language.
5. In the Add Language dialog box, click Italian (Italy) and then click OK.
168
• • • • •
A • Getting started with language switching
169
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
8. On the Arrange menu, click Space Horizontal to space the buttons equally apart.
170
• • • • •
A • Getting started with language switching
171
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
9. Repeat the steps above to add captions to the other two buttons:
For the second button, the press action is Language it-IT (Italian for Italy).
For the second button, the caption is Italiano.
For the third button, the press action is Language de-DE (German for
Germany).
For the third button, the caption is Deutsch.
172
• • • • •
A • Getting started with language switching
173
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
4. In the Language list, select Italian (Italy), it-IT and then click Open.
174
• • • • •
A • Getting started with language switching
2. In the Alarm and Event Setup editor, click the Digital tab and then double-click
the TankTempThreshold alarm to edit it.
3. In the Digital Alarm Properties dialog box, in the Message field, type La
temperatura del serbatoio è alta and then click OK.
175
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
2. In the Alarm Import Export Wizard, in the Operation Type window, leave
Export alarm configuration to Excel file selected and then click Next.
176
• • • • •
A • Getting started with language switching
3. In the Alarms to Export window, leave the TankTempThreshold alarm in the list
of alarms to export and then click Next.
If you have many alarms and you want to export only some of them, you can filter
the list of alarms to find the ones you want, and then you can include only those
alarms you need in the exported file. For details, click Help.
4. In the Messages to Export window, leave Export messages for all alarms
selected, leave all of the languages selected, and then click Next.
In this window you can choose whether to export all alarm messages, the
messages for only the alarms you selected in the previous step, or no alarm
messages, which then exports only the alarm data. If you are exporting alarm
messages, you can also select which languages you want to export.
177
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
5. In the Specify Output File window, leave the file name as it is. You can specify a
location where you want the file to be save or use the default location that is
displayed, and then click Finish.
To browse for a location, click the Browse button (shown at left).
Each alarm is located in a new row in the spreadsheet. The column names
correspond to the settings for each alarm. At the bottom of the Excel window
there are tabs that organize the alarms by type (Digital, Level, Deviation).
178
• • • • •
A • Getting started with language switching
Two additional tabs contain the alarm messages and the tag update rates. These
items are located on their own tabs because they can apply to multiple alarms.
For example, if you had 50 alarms, you could use the same alarm message for 10
of them, but have different messages for the rest. Instead of editing the same alarm
message 10 times, you only need to edit it once. Each alarm message has its own
numeric identifier (in the Message column located in column H in our example),
which links a message to each alarm (level alarms can have a different message
for each level).
The maximum length for an alarm message is 255 characters. Messages that are
longer than 255 characters are truncated when they are imported.
2. At the bottom of the Excel window, click the Messages tab.
3. To add a new language for messages, add a new column and then type the
associated language identifier as the column heading. For example, click cell D1
and then type de-DE. This is the language identifier for German.
For example, the column heading, en-US is the language identifier for English
(United States). For more information, see “Language identifiers for language
switching” on page 231.
179
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
4. To add messages, type the new message in a row under the column specified for
that language. For example, click cell D2 and then type Hohe Tanktemperatur!
5. At the bottom of the Excel window, click the Tag Update Rates tab. The columns
are labeled with the update rates. For example cell A-1, is labeled 0.10 Seconds
and cell E-1 is labeled 2 Seconds.
6. To update an input tag every 2 seconds, enter the name of the input tag in the
column labeled 2 Seconds.
7. To save your changes, click Save on the File menu.
8. Close Microsoft Excel.
180
• • • • •
A • Getting started with language switching
2. In the Alarm Import Export Wizard, in the Operation Type window, select
Import alarm configuration from Excel file and then click Next.
3. In the File to Import window, select the Excel spreadsheet to which you added
the German alarm message and then click Next.
To browse for the file, click the Browse button (shown at left).
4. In the Alarms to Import window, select Import only alarm messages, and then
click Next.
In this window you can choose to overwrite any existing alarms, add only the new
alarms, leaving all existing alarms unchanged, or delete all existing alarms and
then import only those that are in the import file.
181
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
5. In the Messages to Import window, select Update existing messages and create
new messages from the import file, and then click Finish.
Do not select either of the other two options in this window. In our Excel
spreadsheet, we added a language to an existing alarm message; we did not create
a new alarm message. If you do not choose to update existing messages, the
translated text will not appear in your alarm messages.
6. After the import is complete, click OK.
182
• • • • •
A • Getting started with language switching
For details about using the FactoryTalk View Site Edition Client Wizard, click
Help in the wizard.
3. In the FactoryTalk View SE Client Application Type window, click Local Station
and then click Next.
183
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
4. In the FactoryTalk View SE Client Application Name window, select the name of
the application you want to connect to, and then click Next.
In this example, we used the My Local Site application that we created in Chapter
7, “Set up graphic displays”.
184
• • • • •
A • Getting started with language switching
7. In the FactoryTalk View SE Client Auto Logout window, you can configure the
Client to log out automatically after a period of inactivity. In this example, we
accepted the default setting. Click Next.
185
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
186
• • • • •
A • Getting started with language switching
When you click the Italiano button, the alarm message appears in Italian. Notice that
the other parts of the Alarm and Event Summary (for example, the Details pane)
currently appear in the language version of the FactoryTalk View software you have
installed on your computer. However, you can make these items switch languages by
editing the properties of the Alarm and Event Summary to modify the column heading
text. You can also export the graphic display’s language strings in FactoryTalk View,
and then translate them before importing them again.
The behavior of the display is the same when you click the Deutsch button to display
the alarm message in German.
The labels on the buttons do not change when we switch languages. This is
intentional — because we did not provide translated strings for the buttons, and
because we selected the Display undefined strings using the default language
187
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
check box. If you do not select this check box, undefined strings are displayed as
question marks (?) at run time.
188
• • • • •
A • Getting started with language switching
189
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
190
Appendix B
Controller specifications
This release of FactoryTalk Alarms and Events does not support device based alarm
subscription to controllers with firmware revisions 21 or later.
191
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
Scan times increase more during a scan when many alarms change state at the same
time.
An alarm state change is any event that changes the condition of the alarm. To
minimize the potential for large alarm bursts, create dependencies on related
alarms. Large alarm bursts can have a significant impact on the scan time of
application code.
For historical alarm logging, you must be able to log on to a Microsoft SQL Server
database.
192
• • • • •
B • System performance and limits
When a controller has been disconnected and then reconnected to alarm servers on the
network, alarms will start appearing in clients within 30 seconds. It may take up to 2
minutes to fully recover, depending on the computer hardware and the number of
controllers and alarms in the system. In a redundant application, the active server
failover and manual switchover recovery time is the same as the controller reconnect
time.
193
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
194
Appendix C
Summary of steps
Step 1: Confirm that FactoryTalk Services Platform is installed on the computer
where you are going to install FactoryTalk Alarms and Events.
Step 2: Install FactoryTalk Alarms and Events.
195
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
196
Appendix D
Operating systems
Microsoft SQL Server works with the following operating systems:
Windows 7
Windows Server 2008
Windows Server 2008 R2
Windows XP, Service Pack 2 or later
Windows Server 2003, Service Pack 2 or later
For more information about operating system requirements, see the Microsoft web
site.
197
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
Summary of steps
The following is a summary of the steps required to install Microsoft SQL Server
2008 R2 SP2 Express. Each step is described in more detail on the following pages.
Step 1: Open the FTView folder, which is at the root of the FactoryTalk View
installation DVD. The subfolders Redist and System contain the software for
Microsoft SQL Server 2008 R2 SP2 Express and its prerequisite software.
Step 2: Install the .NET Framework and other prerequisite software. The SQL
Server 2008 R2 SP2 Express installation fails without these components.
Step 3: Run the SQL Server Install batch file to install and configure SQL Server
2008 R2 SP2 Express.
Step 4: Configure the Windows firewall if you want to allow for remote
connections.
198
• • • • •
D • Install Microsoft SQL Server 2008 R2 SP2 Express
.NET Framework
Microsoft .NET Framework version 3.5 (SP1) is a prerequisite for SQL Server 2008
R2 SP2 Express.You will need to manually install it if it is not installed.
If you have .NET Framework 1.2 or any version before 2.0.50727, you must uninstall
it (versions 1.0 and 1.1 do not have to be uninstalled) before installing the correct
version.
To determine which .NET Framework versions are on your computer, see Microsoft
Knowledge Base article 318785 at http://msdn.microsoft.com/en-us/kb/
kbarticle.aspx?id=318785.
To install .NET Framework 3.5 (SP1):
1. At the root of the FactoryTalk View installation DVD, open the
FTView\Redist\DotNet35SP1 folder and then double-click dotnetfx35.exe.
2. Follow the on-screen instructions.
MSXML6
To check if you have MSXML6:
1. From the Start menu, select Control Panel and then double-click Add or
Remove Programs.
2. Check to see if MSXML6 is included in the list. If not, install.
To install MSXML6:
1. At the root of the FactoryTalk View installation DVD, open the
FTView\Redist\MSXML6 folder and then double-click msxml6.msi.
2. Follow the on-screen instructions.
199
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
200
• • • • •
D • Install Microsoft SQL Server 2008 R2 SP2 Express
Step 3: Run the SQL Server Install batch file (not the .exe)
The batch file installs Microsoft SQL Server 2008 R2 SP2 Express on your computer
with the correct settings for logging alarms and events. The batch file will configure
the following settings for SQL Server:
allow remote connections to the database using the TCP/IP protocol
enable SQL Server Browser
To install Microsoft SQL Server 2008 R2 SP2 Express:
1. Close any open programs.
2. At the root of the FactoryTalk View installation DVD, open the
FTView\Redist\SQLServerEXPR_2008R2SP2 folder and then double-click SQL
Server Install.bat.
3. In the Setup Support Rules window, click OK.
4. In the Product Key window, click Next (SQL Server 2008 R2 SP2 Express does
not need a product key).
5. Review the End User License Agreement, select the check box to accept it, and
then click Next.
6. In the Setup Support Files window, click Install.
201
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
4. To accept the changes and close the Windows Firewall dialog box, click OK.
202
Appendix E
203
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
have remote clients (for example, a log viewer) that needs access to the database
want to configure the database remotely
Summary of steps
Step 1: Install Microsoft SQL Server Management Tools
Step 2: Specify Mixed Mode authentication for the SQL Server database
Step 3: Configure TCP/IP protocol for the database
Step 4: Enable the SQL Server Browser service
Step 5: Configure the Windows Firewall
204
• • • • •
E • Use an existing Microsoft SQL Server database
d. In the Feature Selection page, select the Management Tools - Basic check
box. If you do not want to install the complete management tools, clear the
Management Tools - Complete check box. Click Next.
5. Follow the instructions in the wizard to complete the installation. If you are
prompted to restart you computer, click Yes.
Step 2: Specify Mixed Mode authentication for the SQL Server database
To change the authentication mode and configure the “sa” login, perform the
following steps:
1. Click Start > All Programs > Microsoft SQL Server 2005 (or Microsoft SQL
Server 2008) > SQL Server Management Studio.
2. In Object Explorer, right-click the server node, and then click Properties.
3. On the Security page, under Server authentication, select SQL Server and
Windows Authentication mode, and then click OK.
4. To acknowledge the need to restart SQL Server, click OK in the SQL Server
Management Studio dialog box.
5. In Object Explorer, expand Security, expand Logins, right-click sa, and then click
Properties.
6. On the General page, you may have to create and confirm a password for the “sa”
login.
7. On the Status page, under Login, click Enabled, and then click OK.
8. Restart the server if you changed the authentication mode. In Object Explorer,
right-click the server node, and then click Restart.
205
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
206
• • • • •
E • Use an existing Microsoft SQL Server database
4. To accept the changes and close the Windows Firewall dialog box, click OK.
207
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
208
Appendix F
209
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
210
• • • • •
F • Alarm time stamping
You can see the calculated result in RSLogix 5000, in the Controller Properties
dialog box, on the Date/Time tab, as shown in the following illustration.
We recommend using local time only to drive events from the controller, and not to
time-stamp alarms.
211
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
If you are using RSLogix 5000 version 20 or earlier, the instruction block is like
this:
212
• • • • •
F • Alarm time stamping
2. When you click the Browse button to edit the alarm instruction, on the
Configuration tab, you can specify the alarm message.
3. On the Status tab, time stamps appear when the alarm is triggered,
acknowledged, returns to normal, or when the alarm count is reset.
213
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
4. On the Parameters tab, these UTC time stamps are automatically transferred to
tags that you can then use in logic of your own.
For details about adding an Alarm and Event Summary object to a graphic display in
FactoryTalk View, see Chapter 7, “Set up graphic displays” or see the FactoryTalk
View Site Edition Help.
214
• • • • •
F • Alarm time stamping
Example
215
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
216
Appendix G
Time synchronization
FactoryTalk Alarms and Events provides excellent resolution and accuracy for alarms
and events time stamps. You can build a very accurate time sequence for events that
led to a failure, or simply to diagnose the exact order of their occurrence. Because the
alarms are generated by the controller, the time-stamp accuracy is a function of the
rate of the controller’s ability to scan the alarm instruction, plus the accuracy of the
controller’s wall clock.
When an alarm instruction is evaluated in code and an alarm transition event occurs
(goes into alarm, or is acknowledged, suppressed, and so on), the instruction
immediately records the current value of the controller’s wall clock. This 64-bit,
microsecond-resolution number reflects the time of the event relative to the
controller’s wall clock in UTC time (no time zone or daylight savings information is
included). When you view this time stamp, either in RSLogix 5000 or in FactoryTalk
View Site Edition, the time zone of the computer running the software is used to
visualize the time value. You can use a distributed system that covers multiple time
zones to display a valid sequence of events at an operator or maintenance station
independently of the time zone the time stamps are captured in.
217
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
218
• • • • •
G • Time synchronization
The left pane of the Clock Update Tool window contains a tree view, with these items:
Scheduled Synchronizations lists synchronization schedules that have been
configured. Right-click an individual schedule for more options.
Devices lists devices that have been configured. Right-click an individual device
for more options.
Log contains a log of the most recent events. The path indicated under the list of
events contains the location of the complete log file for the day.
Summary of steps
To synchronize devices on a schedule, complete these steps:
1. Create a synchronization schedule. This schedule determines when
synchronization takes place.
2. Create a list of devices you want to synchronize and then add them to
synchronization schedules. Devices that are not included in this list are not
synchronized.
3. Optionally, match existing devices with existing synchronization schedules. Skip
this step if you specified a synchronization schedule when you added the device.
Devices that are not matched to any synchronization schedule are not
synchronized.
This chapter includes information about each of these steps.
219
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
220
• • • • •
G • Time synchronization
221
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
Add devices
After creating one or more synchronization schedules, add the devices you want to
include in the schedules.
When you add a device, you can also match it to a synchronization schedule, or you
can add all of the devices first and then match them to synchronization schedules later.
If you add the devices later, you can add all of the devices to a single synchronization
schedule in one step.
You can add a device to only one synchronization schedule.
To add a device:
1. In the Logix5000 Clock Update Tool, in the left pane, click Devices.
2. Right-click the right pane and then click Add New Device or click the Add
Device button, shown at left.
3. In the RSLinx dialog box, browse to the device you want to add, select it, and
then click OK.
You cannot click OK unless you have selected a device that is capable of being
synchronized and has not already been configured.
222
• • • • •
G • Time synchronization
4. In the Add Device to Schedule list, select the synchronization schedule to which
you want to add the device, and then click OK.
The device is added to the list. Because this device has not yet been synchronized,
question marks (?????) appear in the Last Update column:
Remove a device
To remove a device from the list, right-click the device you want to remove, and
then click Remove Device, or click the Remove Device button, shown at left. If
the device is associated with a particular synchronization schedule, it is removed
from that schedule.
If you want to remove all devices from the list, right-click in the Device pane and
then click Remove All Devices. All devices are removed from the list, as well as
from their respective synchronization schedules.
223
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
computer’s time, the device’s time, the device’s response time, and the time difference
between the computer and the device.
When you add a new device, you can assign it to a specific schedule at that time.
See “Add devices” on page 222.
To add a device to this selected synchronization schedule, select the check box to
the left of the device. To remove the device from the synchronization schedule,
clear the check box beside the device.
To add all devices to the specified schedule, select the Select All check box at the
bottom of the list.
224
• • • • •
G • Time synchronization
225
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
2. In the Browse for Folder dialog box, select the new folder for the log files, and
then click OK. To create a new folder for the log file, click Make New Folder.
226
• • • • •
G • Time synchronization
Supported devices
The Logix5000 Clock Update Tool supports the following controller families:
ControlLogix
CompactLogix
All CompactLogix processors can be used with ENI. CompactLogix L32E
and CompactLogix L35E can be directly connected via Ethernet or with ENI.
Make sure that the CompactLogix port is set up for DF1 Full-duplex.
Make sure the routing is enabled on NET-ENI (check box). Net-ENI works
with Ethernet devices drivers and not with EtherNet/IP drivers.
DriveLogix
FlexLogix
PLC-5
SLC
MicroLogix
PowerMonitor
227
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
228
Appendix H
229
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
230
Appendix I
Language identifiers
The following table lists the language identifiers:
Language ID
Afrikaans (South Africa) af-ZA
Albanian (Albania) sq-AL
Arabic (Algeria) ar-DZ
Arabic (Bahrain) ar-BH
Arabic (Egypt) ar-EG
Arabic (Iraq) ar-IQ
Arabic (Jordan) ar-JO
Arabic (Kuwait) ar-KW
Arabic (Lebanon) ar-LB
Arabic (Libya) ar-LY
Arabic (Morocco) ar-MA
231
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
Language ID
Arabic (Oman) ar-OM
Arabic (Qatar) ar-QA
Arabic (Saudi Arabia) ar-SA
Arabic (Syria) ar-SY
Arabic (Tunisia) ar-TN
Arabic (U.A.E.) ar-AE
Arabic (Yemen) ar-YE
Armenian (Armenia) hy-AM
Azeri (Cyrillic) az-Cyrl-AZ
Azeri (Latin) az-Latn-AZ
Basque eu-ES
Belarusian be-BY
Bosnian (Cyrillic, Bosnia and Herzegovina) bs-Cyrl-BA
Bosnian (Latin, Bosnia and Herzegovina) bs-Latn-BA
Bulgarian bg-BG
Catalan ca-ES
Chinese (Hong Kong S.A.R.) zh-HK
Chinese (Macau S.A.R.) zh-MO
Chinese (PRC) zh-CN
Chinese (Singapore) zh-SG
Chinese (Taiwan) zh-TW
Croatian (Croatia) hr-HR
Czech (Czech Republic) cs-CZ
Danish (Denmark) da-DK
Divehi (Maldives) dv-MV
Dutch (Belgium) nl-BE
Dutch (Netherlands) nl-NL
English (Australia) en-AU
English (Belize) en-BZ
English (Canada) en-CA
English (Caribbean) en-029
English (Ireland) en-IE
English (Jamaica) en-JM
English (New Zealand) en-NZ
232
• • • • •
I • Language identifiers for language switching
Language ID
English (Philippines) en-PH
English (South Africa) en-ZA
English (Trinidad ) en-TT
English (United Kingdom) en-GB
English (United States) en-US
English (Zimbabwe) en-ZW
Estonian (Estonia) et-EE
Faroese (Faroe Islands) fo-FO
Farsi fa-IR
Filipino(Philippines) fil-PH
Finnish (Finland) fi-FI
French (Belgium) fr-BE
French (Canada) fr-CA
French (France) fr-FR
French (Luxembourg) fr-LU
French (Monaco) fr-MC
French (Switzerland) fr-CH
Frisian (Netherlands) fy-NL
FRYO (Macedonian) mk-MK
Galician gl-ES
Georgian ka-GE
German (Austria) de-AT
German (Germany) de-DE
German (Liechtenstein) de-LI
German (Luxembourg) de-LU
German (Switzerland) de-CH
Greek (Greece) el-GR
Gujarati (India) gu-IN
Hebrew (Israel) he-IL
Hindi (India) hi-IN
Hungarian (Hungary) hu-HU
Icelandic (Iceland) is-IS
Indonesian (Indonesia) id-ID
Inuktitut (Latin, Canada) iu-Latn-CA
233
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
Language ID
Irish (Ireland) ga-IE
Italian (Italy) it-IT
Italian (Switzerland) it-CH
Japanese (Japan) ja-JP
Kannada (India) kn-IN
Kazakh (Kazakhstan) kk-KZ
Konkani (India) kok-IN
Korean (Korea) ko-KR
Kyrgyz (Cyrillic) ky-KG
Latvian (Latvia) lv-LV
Lithuanian (Lithuania) lt-LT
Luxembourgish (Luxembourg) lb-LU
Malay (Brunei Darussalam) ms-BN
Malay (Malaysia) ms-MY
Maktese mt-MT
Maori mi-NZ
Mapudungun (Chile) arn-CL
Marathi (India) mr-IN
Mohawk (Mohawk) moh-CA
Mongolian (Cyrillic) mn-MN
Norwegian (Bokmal) nb-NO
Norwegian (Nynorsk) nn-NO
Polish (Poland) pl-PL
Portuguese (Brazil) pt-BR
Portuguese (Portugal) pt-PT
Punjabi pa-IN
Quechua (Bolivia) quz-BO
Quechua (Equador) quz-EC
Quechua (Peru) quz-PE
Romanian (Romania) ro-RO
Romansh (Switzerland) rm-CH
Russian (Russia) ru-RU
Sami, Inari (Finland) smn-FI
Sami, Lule (Norway) smj-NO
234
• • • • •
I • Language identifiers for language switching
Language ID
Sami, Lule (Sweden) smj-SE
Sami, Northern (Finland) se-FI
Sami, Northern (Norway) se-NO
Sami, Northern (Sweden) se-SE
Sami, Skolt (Finland) sms-FI
Sami, Southern (Norway) sma-NO
Sami, Southern (Sweden) sma-SE
Sanskrit - India sa-IN
Serbian (Cyrillic) sr-Cyrl-CS
Serbian (Cyrillic, Bosnia and Herzdgovina) sr-Cryl-BA
Serbian (Latin) sr-Latn-CS
Serbian (Latin, Bosnia and Herzdgovina) sr-Latn-BA
Sesotho sa Leboa (South Africa) ns-ZA
Sestswana (South Africa) tn-ZA
Slovak sk-SK
Slovenian (Slovenia) sl-SI
Spanish (Argentina) es-AR
Spanish (Bolivia) es-BO
Spanish (Chile) es-CL
Spanish (Colombia) es-CO
Spanish (Costa Rica) es-CR
Spanish (Dominican Republic) es-DO
Spanish (Ecuador) es-EC
Spanish (El Salvador) es-SV
Spanish (Guatemala) es-GT
Spanish (Honduras) es-HN
Spanish (International Sort) es-ES
Spanish (Mexico) es-MX
Spanish (Nicaragua) es-NI
Spanish (Panama) es-PA
Spanish (Paraguay) es-PY
Spanish (Peru) es-PE
Spanish (Puerto Rico) es-PR
Spanish (Traditional Sort) es-ES_tradnl
235
• • • • •
FactoryTalk Alarms and Events System Configuration Guide
Language ID
Spanish (Uruguay) es-UY
Spanish (Venezuela) es-VE
Swahili (Kenya) sw-KE
Swedish (Finland) sv-FI
Swedish sv-SE
Syriac (Syria) syr-SY
Tamil (India) ta-IN
Tatar (Russia) tt-RU
Telugu (India) te-IN
Thai (Thailand) th-TH
Turkish (Turkey) tr-TR
Ukrainian (Ukraine) uk-UA
Urdu (Pakistan) ur-PK
Uzbek (Cyrillic) uz-Cyrl-UZ
Uzbek (Latin) uz-Latn-UZ
Vietnamese (Vietnam) vi-VN
Welch cy-GB
Xhosa xh-ZA
Zula zu-ZA
For more information, see “Enter alarm messages in Excel” on page 178.
236
Symbols
119, 120, 199, 200
???
appears at run time in graphic displays 167
.csv files
do not support Unicode in RSLogix 5000 157
.NET Framework
installing 199
.txt files
using with Unicode character sets for language switching in RSLogix 5000 157
.xls files
exporting alarm messages from Tag Alarm and Event Servers 162
.xml files
exporting alarm messages from Tag Alarm and Event Servers 162
A
about
acknowledging alarms 106
Alarm and Event Banner 11
Alarm and Event Historian 10
Alarm and Event Log Viewer 10, 11
Alarm and Event Summary 11, 76
Alarm Status Explorer 11, 76
Coordinated System Time 209
Coordinated Universal Time 210
data displayed at run time 6
database definitions 11
device-based alarm monitoring 5, 9, 13
distributed applications 229
FactoryTalk Alarms and Events 5
FactoryTalk Audit Log 10, 11
FactoryTalk Diagnostics 10
FactoryTalk Diagnostics Viewer 11
graphic displays 73
HMI Tag Alarm Monitoring 11
language switching 155
Local station applications 16, 49, 63
monitoring for alarm conditions 11
Network distributed applications 15
Network station applications 15
OPC Data Servers 6
planning your system 15
process data 6
security for alarms and events 6
setting up FactoryTalk Alarms and Events 10
software-based tag servers 5
Tag Alarm and Event Servers 61
tag-based alarm monitoring 5, 10, 11, 16, 47
time stamps for alarms 6
warning icons 54, 68
acknowledgement required
setting in RSLogix 5000 42
acknowledging alarms 106
all in event list 108
all on page 107
with comment 107
activations
planning 18
Alarm and Event Banner
about 11
adding to graphic displays 79
definition of 11
number of alarms displayed 80
opening Alarm and Event Summary from 81
run-time columns in 105
setting up 81
silencing alarms 76
uses for 14
Alarm and Event Historian
See also Alarm and Event Log
about 10
Alarm and Event Log
See also Alarm and Event Historian
language switching 155
Alarm and Event Log Viewer 119
about 10, 11
adding to graphic displays 128
definition of 11
showing or hiding areas 130
specifying database 130
uses for 14
Alarm and Event Summary
about 11, 76
adding to graphic displays 76, 172
definition of 11
uses for 14
alarm blocks
configuring properties in RSLogix 5000 42
overview 212
alarm buffering
device-based 21
tag-based 125
alarm expressions 86
alarm history. See historical logging
alarm instructions
adding to rung in RSLogix 5000 26
built into RSLogix5000 controllers 5
alarm messages
advantages of using Excel to edit 173
creating in FactoryTalk View Studio 162
default location for exported 178
editing exported in Notepad 157, 161
editing in Alarm and Event Setup editor 162
editing in alternate languages 173
editing in Microsoft Excel 173, 178
embedded variables in RSLogix 5000 43
exporting to Microsoft Excel 176
importing into RSLogix 5000 158, 162
importing into Tag Alarm and Event Servers 180
language switching 155
maximum length 31, 173, 179
tag-based alarm monitoring 162
testing at run time 186
uploaded to controllers by RSLinx Enterprise 155
alarm monitoring
about device-based 5, 13
about HMI Tag Alarm Monitoring 11
about tag-based 5, 11, 16, 47
adding Tag Alarm and Event Servers 68
choosing between tag- and device-based 16, 47
comparison of methods 13
how device-based works 13
how HMI Tag Alarm Monitoring works 11
how tag-based works 11
uses for device-based 14
uses for tag-based 14
Alarm Status Explorer
about 11, 76
definition of 11
enabling alarms 111
opening 111
uses for 14, 110
alarm system tags
in FactoryTalk View 14
alarms and events
See also alarm monitoring
See also alarms and events
See also FactoryTalk Alarms and Events
about acknowledging 106
about monitoring for 11
acknowledging all in event list 108
acknowledging all on page 107
acknowledging selected 106
acknowledging with comment 107
ALMA instructions 37
condition-related 119
creating in Logix5000 controllers 21
creating in RSLogix 5000 34
creating in Tag Alarm and Event Servers 69, 70, 164
default location for exported 178
digital 24
disabling 109, 110
enabling 76, 109, 111
enabling in RSLinx Enterprise 54
enabling support for data servers 52
filtering 114
generating time-stamped using CST time 215
historical do not switch languages 153
historical logging 119
interacting with 97
monitoring 97
new graphic objects 14
no support for FactoryTalk View ME 49, 63
quantity displayed in Alarm and Event Banner 80
securing 105
setting up 10
shelving 115
silencing 76
simple 119
suppressing 112
synchronizing time stamps 209, 217
tracking-related 119
trigger conditions for digital 166
triggering in Logix5000 controllers 33
unshelving 115
unsuppressing 76, 112, 113
viewing details 107
viewing historical 137
ALMA instructions 37
connecting to input references 41
ALMD instructions
adding to RSLogix 5000 26
Always Updating option
for graphic displays in FactoryTalk View 77
analog alarms
creating in RSLogix 5000 34
animation
color 89
applications
adding Tag Alarm and Event Servers in FactoryTalk View 68
creating in FactoryTalk View 49, 63
Local station 16, 49, 63
Network distributed 15
Network station 15
opening existing in FactoryTalk View Studio 59
opening in a different language 173
running in SE Client 100, 101
areas
not supported in Local station applications 16
showing or hiding in Alarm and Event Log Viewer 130
Audit Log. See FactoryTalk Audit Log
auditing. See historical logging
B
Banner. See Alarm and Event Banner
bits
toggling in RSLogix 5000 34
buttons
adding captions 134, 170
adding to graphic displays 131
using to switch languages at run time 168
C
captions
adding to buttons 134, 170
centering graphic displays on screen 82
clock synchronization
CompactLogix controllers 227
ControlLogix processors 227
DriveLogix controllers 227
FlexLogix controllers 227
manual 225
MicroLogix controllers 227
PLC-5 controllers 227
PowerMonitor controllers 227
SLC 500 controllers 227
using the Logix5000 Clock Update Tool 219
color animation
adding to graphic displays 89
columns
in Alarm and Event Banner at run time 105
Command Wizard 132, 170
in FactoryTalk View 81, 84, 85
in startup macros 136
commands
adding to Alarm and Event Banner 81
adding to buttons 132, 170
adding to startup macros 84, 85, 136
Display 85, 132, 170
SuppressOff 14
SuppressOn 14
comments
entering when acknowledging alarms 107
Communication Setup editor
in RSLinx Enterprise 53, 66
CompactLogix controllers
clock synchronization 227
compatible firmware revisions 3
support for alarms and events 2
comparison
between software-based and device-based alarm monitoring 13
components
of FactoryTalk Alarms and Events 9
start up in FactoryTalk View SE Client 101
condition-related events 119
configuration files
for FactoryTalk View SE Client 99, 182
connections
database, for alarm and event historical logging 123
status of Tag Alarm and Event Server at run time 105
ControlFLASH
device-based alarm monitoring 22
language switching 154
version required 1
controller instruction faceplates
adding 51, 65
controllers
compatible with Alarms and Events 3
linking tags with FactoryTalk Directory 58
selecting paths for device shortcuts in RSLinx Enterprise 55, 68
synchronizing time clocks 217
ControlLogix processors
clock synchronization 227
compatible firmware versions 3
ControlLogix Safety Processor 2
support for alarms and events 2
Coordinated System Time
about 209
generating time-stamped alarms and events 215
Coordinated Universal Time
about 210
coordinating multiple controllers’ clocks 217
CST. See Coordinated System Time
D
data
viewing for historical alarms 137
data access
FactoryTalk Administration Console 57
FactoryTalk View Studio 57
OPC programmable controllers 57
PLC-5 controllers 57
SLC 500 controllers 57
data servers
adding 51, 57
adding for PLC-5 controllers 47
adding for SLC 500 controllers 47
adding RSLinx Enterprise 47
adding to applications in FactoryTalk View 59
enabling alarms and events 52
RSLinx OPC Server versus RSLinx Remote OPC Server 60
database definitions
about 11
adding for historical alarm and event logging 122
associating with alarm servers 125
definition of 11
for historical logging 119
specifying to display in Log Viewer 130
default language
using for undefined strings 167
design
for typical distributed system 229
for typical stand-alone system 18
planning your system 18
details
viewing for alarms 107
device servers
adding for Logix5000 controllers 47
device shortcuts
creating in RSLinx Enterprise 53, 66
mapping to controller paths 55, 68
device-based alarm monitoring
about 5, 9, 13
choosing over tag-based 16, 47
compared with software-based 13
ControlFLASH 22
definition of 9
FactoryTalk Administration Console 47
FactoryTalk View Studio 47
how it works 13
language switching 155
Logix5000 firmware 22
RSLinx Classic 22
RSLinx Enterprise 47
RSLogix 5000 22
uses for 14
devices
adding to clock synchronization schedule 222, 224
removing from clock synchronization schedule 223
synchronizing clocks manually 225
viewing clock synchronization 223
Diagnostics Viewer. See FactoryTalk Diagnostics Viewer
digital alarms
creating in RSLogix 5000 24
creating in Tag Alarm and Event Servers 164
trigger conditions 166
disabling alarms 110
in Tag Alarm and Event Servers 109
Display command 85, 132, 170
using in FactoryTalk View 81
distributed applications
about 229
typical 229
docking
graphic displays 136
documentation
finding 3
drawing objects
adding to graphic displays 88
DriveLogix controllers
clock synchronization 227
compatible firmware versions 3
DriveLogix5370 3
E
embedded variables
in RSLogix 5000 43
enabling alarms 76, 111
in Alarm Status Explorer 111
in Tag Alarm and Event Servers 109
events. See alarms and events
existing applications. See applications
expressions
adding functions to graphic displays 90
in alarms 86
F
FactoryTalk Administration Console
as alternative to FactoryTalk View Studio 58, 65
data access 57
device-based alarm monitoring 47
language switching 154
tag-based alarm monitoring 61
FactoryTalk Alarms and Events
about 5
compatible controllers 3
components 9
installing manually 195
new graphic objects 14
setting up 10
version required 1
versus HMI Tag Alarm Monitoring 5, 6
FactoryTalk Audit Log
about 10, 11
definition of 11
FactoryTalk Diagnostics
about 10
FactoryTalk Diagnostics Viewer
about 11
definition of 11
FactoryTalk Directory
linking with controller tags 58
FactoryTalk documentation
finding 3
FactoryTalk Security
and alarms and events 6
FactoryTalk Services Platform
version required 1
FactoryTalk View ME 49, 63
See also FactoryTalk View Studio
FactoryTalk View SE 97
See also FactoryTalk View SE Client
See also FactoryTalk View Studio
documentation 3
new graphic objects for alarms and events 14
version required 1
FactoryTalk View SE Client 97, 119, 120
auto logout period 102
configuring 99, 182
language switching 154
running applications 100, 101
setting up run-time window 102
starting from within FactoryTalk View Studio 138
startup components 101
FactoryTalk View Studio 73, 120
See also FactoryTalk View ME
See also FactoryTalk View SE
adding data servers 59
adding Tag Alarm and Event Servers 68
as alternative to FactoryTalk Administration Console 58, 65
Command Wizard 81
creating alarm messages 162
creating applications 49, 63
creating graphic displays 73
data access 57
device-based alarm monitoring 47
historical logging 120
language switching 154
opening existing applications 59
saving graphic displays 78, 173
setting up graphic displays 77, 83, 135
starting the FactoryTalk View SE Client 138
tag-based alarm monitoring 61
version required 1
filtering alarms 114
firmware. See Logix5000 firmware
FlexLogix controllers
clock synchronization 227
support for alarms and events 2
function block diagrams
in RSLogix 5000 35, 36
functions
adding to graphic displays 90
G
getting started 8
graphic displays
See also graphic objects
about 73
adding buttons 131
adding drawing objects 88
centering on screen 82
creating in FactoryTalk View 75
creating in FactoryTalk View Studio 73
docking to bottom of screen 86
docking to top of screen 136
performance 77
refreshing automatically 77
saving 78, 84, 93, 131, 135, 173
sizing 77, 83, 135
test running 94
title bars 77, 83, 135
graphic objects
Alarm and Event Banner 14, 79
Alarm and Event Log Viewer 14, 128
Alarm and Event Summary 14, 76, 172
Alarm Status Explorer 14
HMI Tag Alarm Log Viewer 14
HMI Tag Alarm Summary 14
new alarms and events objects 14
H
Help
finding 3
Historian. See Alarm and Event Historian
historical alarms
do not switch languages 153
viewing 137
historical logging
associating databases with alarm servers 125
database definitions 119
enabling in RSLinx Enterprise 125
enabling in Tag Alarm and Event Servers 125
language switching 155
setting up for alarms and events 119
HMI Tag Alarm Log Viewer 14
HMI Tag Alarm Monitoring
about 11
how it works 11
versus FactoryTalk Alarms and Events 5, 6
HMI Tag Alarm Summary 14
I
icons
about warning icons 54, 68
input references
connecting to input of ALMA block 41
in RSLogix 5000 39
install
FactoryTalk Alarms and Events manually 195
Logix5000 Clock Update Tool 218
Microsoft SQL Server 19, 197
Microsoft SQL Server 2008 R2 Express 197
planning 18
J
JSR instructions
adding to RSLogix 5000 44
K
KEPWare OPC data server
support for alarms and events 3
L
labels
adding to buttons 134
language switching 153
about 155
Alarm and Event Banner 189
Alarm and Event Log Viewer 190
Alarm and Event Summary 189
alarm messages in FactoryTalk View Studio 162
ControlFLASH 154
device-based alarm messages 155
displaying undefined strings in default language 167
editing alarm messages 173
editing applications in different languages 173
FactoryTalk Administration Console 154
FactoryTalk View SE Client 154
FactoryTalk View Studio 154
historical alarms do not switch languages 153
how it works 155
importing alarm messages into Tag alarm and Event Servers 180
items that do not switch languages 153
Logix5000 controllers 154
Microsoft Excel 154
PLC-5 controllers 154
RSLinx Classic 154
RSLinx Enterprise 154, 155
RSLogix 5 154
RSLogix 500 154
RSLogix 5000 154
SLC 500 controllers 154
Tag Alarm and Event Servers 162
tag-based alarm messages 162
testing at run time 186
text that does not switch languages at run time 189
text that switches languages at run time 189
time and date formats do not switch 153
tips for setting up 188
.txt files for Unicode character sets in RSLogix 5000 157
Unicode character sets in RSLogix 5000 157
using buttons to switch languages at run time 168
languages
editing alarm messages 173
editing applications in different 173
importing alarm messages into Tag Alarm and Event Servers 180
limits
controller specifications 191
tested system limits 191, 192
log file
changing location for Logix5000 Clock Update Tool 225
viewing for Logix5000 Clock Update Tool 225
Log Viewer. See Alarm and Event Log Viewer
logging. See historical logging
logic
creating new in RSLogix 5000 24
Logix Designer
version required 1
Logix5000 Clock Update Tool 217
changing location of log file 225
installing 218
starting automatically 218
synchronizing clocks 219
synchronizing clocks manually 225
viewing log file 225
Logix5000 controllers 33
See also Logix5000 firmware
about built-in alarm instructions 5
acknowledgement required 42
adding device servers 47
ALMA instructions 37
analog alarms 34
configuring alarm blocks 42
creating alarms 21
defining routines 34
digital alarms 24
downloading programs to 32
embedded variables in alarm messages 43
firmware required for device-based alarm monitoring 16
function block diagrams 35, 36
input references 39
JSR instructions 44
language switching 154
mapping to device shortcuts in RSLinx Enterprise 55, 68
Run Mode 45
support for alarms and events 2, 3
tag-based alarm monitoring 10, 61
tags 40
triggering alarms 33
Who Active 45
Logix5000 firmware
device-based alarm monitoring 22
revisions compatible with Alarms and Events 3
when to update 19
logout
in FactoryTalk View SE Client 102
M
macros
creating 135
editing 136
saving 86, 137
startup 84, 135, 136
manuals
finding 3
maximum length
alarm messages 31, 173, 179
MicroLogix controllers
clock synchronization 227
Microsoft Excel
editing alarm messages 173, 178
exporting alarm messages from Tag Alarm and Event Servers 176
language switching 154
Microsoft SQL Server
historical logging 119, 120
installing 19, 197
version required 2
Microsoft SQL Server 2008 R2 Express
configuring Windows firewall 202
install batch file 201
installing 197
monitoring for alarms
about 11
about device-based 13
about HMI Tag Alarm Monitoring 11
about tag-based 11
choosing between tag- and device-based 16, 47
comparison of methods 13
how device-based works 13
how HMI Tag Alarm Monitoring works 11
how tag-based works 11
uses for device-based 14
uses for tag-based 14
MSXML6
installing for SQL Server 199
N
Notepad
editing exported alarm messages 157
O
objects. See graphic objects
OPC Data Servers
about 6
OPC data servers
adding to applications in FactoryTalk View 59
RSLinx OPC Server vs. RSLinx Remote OPC Server 60
specifying name 60
support for alarms and events 3
tag-based alarm monitoring 10
OPC Data Servers. See OPC Data Servers
OPC programmable controllers
data access 57
P
performance
controller specifications 191
of graphic displays 77
tested system limits 192
tested system performance 191
planning your system 15
distributed applications 229
install and activation 18
local applications 18
PLC-5 controllers
adding data servers for 47
adding Tag Alarm and Event Servers for 61
clock synchronization 227
data access 57
language switching 154
support for alarms and events 3
tag-based alarm monitoring 10, 61
PowerMonitor controllers
clock synchronization 227
process data
about 6
ProgID
for data servers 60
programs
downloading to controllers from RSLogix 5000 32, 45, 159, 162
projects
downloading to controllers from RSLogix 5000 159, 162
Q
question marks
appear at run time in graphic displays 167
R
required hardware 2
required software 1
resizing
graphic displays 77, 83, 135
Rockwell Automation Device Server. See RSLinx Enterprise
routines
defining in RSLogix 5000 34
routing services
for alarms and events 10
RSLinx Classic
device-based alarm monitoring 22
documentation 4
downloading programs to controllers 32, 45
language switching 154
support for PLC-5 and SLC 500 controllers 3, 61
tag-based alarm monitoring 10, 61, 154
version required 1
RSLinx Enterprise 10, 73, 97, 120
adding data servers 47, 51
associating databases for historical logging 125
Communication Setup editor 53, 66
controller paths for device shortcuts 55, 68
device shortcuts 53, 66
device-based alarm monitoring 47
documentation 4
enabling alarms and events 52, 54
historical logging 120
language switching 154, 155
uploads alarm messages to controllers 155
version required 1
RSLinx Gateway
tag-based alarm monitoring 10
RSLinx OPC Server
versus RSLinx Remote OPC Server 60
RSLinx Remote OPC Server
versus RSLinx OPC Server 60
RSLogix 5 57
language switching 154
tag-based alarm monitoring 61
version required 1
RSLogix 500 57
language switching 154
tag-based alarm monitoring 61
version required 1
RSLogix 5000
acknowledgement required 42
adding alarm instructions 26
ALMA instructions 37
ALMD instructions 26
analog alarms 34
configuring alarm blocks 42
creating new logic 24
creating tags 25
.csv format does not support Unicode 157
device-based alarm monitoring 22
documentation 3
downloading programs to controllers 32, 45, 159, 162
embedded variables in alarm messages 43
function block diagrams 35, 36
importing alarm messages 158, 162
input references 39
JSR instructions 44
language switching 154
Run Mode 45
switching controllers to Run Mode 33
toggling bits 34
triggering alarms 33
version required 1
Who Active 45
RSLogix Emulate 5000
support for alarms and events 3
Run Mode
for Logix5000 controllers 33, 45
run time
about displayed data at 6
interacting with alarms 97
monitoring alarms 97
setting up window in FactoryTalk View SE Client 102
S
schedules
adding devices for synchronizing clocks 222, 224
creating for synchronizing clocks 220
enabling or disabling for synchronizing clocks 221
modifying for synchronizing clocks 221
removing devices for synchronizing clocks 223
removing for synchronizing clocks 221
security
auto logout in FactoryTalk View SE Client 102
for alarms and events 105
services
routing for alarms and events 10
shelving alarms 115
shortcuts. See device shortcuts
silencing alarms 76
simple events 119
sizing
graphic displays 77, 83, 135
SLC 500 controllers
adding data servers for 47
adding Tag Alarm and Event Servers for 61
clock synchronization 227
data access 57
language switching 154
support for alarms and events 3
tag-based alarm monitoring 10, 61
SoftLogix controllers
compatible firmware versions 3
support for alarms and events 3
version required 1
software
required 1
software-based alarm monitoring
compared with device-based 13
software-based tag servers. See Tag Alarm and Event Servers
stand-alone applications. See applications
stand-alone system
design for typical 18
startup components
in FactoryTalk View SE Client 101
startup macros
adding commands 85, 136
creating 135
editing 136
for graphic displays in FactoryTalk View 84
saving 137
specifying in FactoryTalk View SE Client 101
Summary. See Alarm and Event Summary
Suppressed list
in FactoryTalk View SE 14
suppressing alarms 112
SuppressOff command 14
SuppressOn command 14
switching languages. See language switching
switching to Run Mode 33
synchronization schedules
adding devices for synchronizing clocks 222, 224
creating for synchronizing clocks 220
enabling or disabling for synchronizing clocks 221
modifying for synchronizing clocks 221
removing devices for synchronizing clocks 223
removing for synchronizing clocks 221
synchronizing controller clocks 217
system performance. See performance
system tags
in FactoryTalk View 14
system time 210
T
Tag Alarm and Event Servers
about 5, 61
adding for PLC-5 controllers 61
adding for SLC 500 controllers 61
adding for third-party controllers 61
adding in FactoryTalk View Studio 68
adding to applications 68
connection status at run time 105
creating alarms 69, 164
enabling historical logging 125
exporting alarm messages in Excel format 162
exporting alarm messages in XML format 162
exporting alarm messages to Microsoft Excel 176
language switching 162
time stamps 226
uses for 3
tag-based alarm monitoring
about 5, 10, 11, 16, 47
adding Tag Alarm and Event Servers 68
creating alarms in Tag Alarm and Event Servers 69
definition of 10
FactoryTalk View Studio 61
how it works 11
language switching 162
Logix5000 controllers 10, 61
OPC data servers 10
PLC-5 controllers 10, 61
RSLinx Classic 10, 61, 154
RSLinx Gateway 10
RSLogix 5 61
RSLogix 500 61
SLC 500 controllers 10, 61
third-party controllers 10
uses for 14
tag-based alarms
time stamps 226
tags
creating in RSLogix 5000 25
in RSLogix 5000 40
test run
graphic displays 94
third-party controllers
adding data servers for 57
adding Tag Alarm and Event Servers for 61
support for alarms and events 3
tag-based alarm monitoring 10
time and date formats
do not switch languages 153
time stamps 217
about 6
for Tag Alarm and Event Servers 226
synchronizing for alarms 209
synchronizing manually in the Logix5000 Clock Update Tool 225
time synchronization 217
for controllers 217
tips
for setting up language switching 188
title bars
in graphic displays 77, 83, 135
tracking-related events 119
traditional alarm monitoring
compared with device-based 13
triangles. See warning icons
typical stand-alone system
design for 18
U
undefined strings
displaying in default language 167
Unicode character sets
language switching in RSLogix 5000 157
using .txt files with RSLogix 5000 157
unshelving alarms 115
unsuppressing alarms 76, 112, 113
user’s guides. See documentation
uses for device-based alarm monitoring 14
uses for tag-based alarm monitoring 14
UTC. See Coordinated Universal Time
V
variables. See embedded variables
W
wall clock time 209
warning icons
about 54, 68
Who Active
in RSLogix 5000 45
windows
docked to bottom of screen 86
docking to top of screen 136
setting up for run time in FactoryTalk View SE Client 102
Windows 2000
version required 1
Windows firewall
configuring for SQL Server 202
Windows Installer 4.5
installing for SQL Server 199
Windows Powershell 1.0
installing for SQL Server 200
Windows Server 2003
version required 1
Windows XP
version required 1
Y
yellow triangles. See warning icons