FTAE-RM001A-EN-E:Layout 1 4/28/08 4:51 PM Page 1 INTEGRATED PRODUCTION & PERFORMANCE SUITE AlarmsandEvents SYSTEM CONFIGURATION GUIDE PUBLICATION FTAE-RM001A-EN-E–May 2009
Contact Rockwell Technical Support Telephone — 440-646-3434 Technical Support Fax — 440-646-5801 World Wide Web — www.rockwellautomation.com Copyright Notice © 2009 Rockwell Automation Technologies, Inc. All rights reserved. Printed in USA. This document and any accompanying Rockwell Software products are copyrighted by Rockwell Automation Technologies, Inc. Any reproduction and/or distribution without prior written consent from Rockwell Automation Technologies, Inc. is strictly prohibited.
Contents Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iii Preface What you need to get started . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Required software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Recommended hardware and supported operating systems. . . . . . . . . . 2 Logix5000 controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Compatible firmware . . . . . . . . . . . . . . . . . .
• • • • • FactoryTalk Alarms and Events System Configuration Guide Chapter 3 Define device-based alarms in Logix5000 controllers . . . . . . . . . . . 21 Alarm buffering during loss of connection to the controller . . . . . . . . 21 Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 What you need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Follow these steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 7 Set up graphic displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 What you need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Follow these steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Create a graphic display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Create an Alarm and Event Summary . . . .
• • • • • FactoryTalk Alarms and Events System Configuration Guide Appendix A Getting started with language switching . . . . . . . . . . . . . . . . . . . 137 Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 What you need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Follow these steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Create device-based alarm messages . . . . . . . . . . . . . . . . . . . .
Appendix D Install Microsoft SQL Server 2005 Express . . . . . . . . . . . . . . . . . . 183 Operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Summary of steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Step 1: Open the Redist folder . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Step 2: Install the .NET Framework and other prerequisite software . 185 .NET Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
• • • • • FactoryTalk Alarms and Events System Configuration Guide Appendix G Time synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Coordinating multiple controllers’ wall clocks . . . . . . . . . . . . . . . . 203 Install the Logix5000 Clock Update Tool . . . . . . . . . . . . . . . . . . . . 204 Start the Logix5000 Clock Update Tool . . . . . . . . . . . . . . . . . . . . . 204 Starting the Update Tool automatically . . . . . . . . . . . . . . . . . .
Preface What you need to get started The FactoryTalk System Configuration Guide describes the tasks that are required to install, configure, and use FactoryTalk Alarms and Events services as part of a FactoryTalk-enabled automation system. This guide also includes references to additional documentation that provides more detail. This guide describes how to set up a Local application. However, the procedure for setting up a Network application is similar.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Recommended hardware and supported operating systems The hardware and supported operating systems that are recommended to run FactoryTalk Alarms and Events are the same hardware and operating systems that are recommended to run FactoryTalk View Site Edition. For details, see the FactoryTalk View Site Edition Installation Guide.
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 version 16.20 or later. 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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 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
Chapter 1 Overview of FactoryTalk Alarms and Events services FactoryTalk View Site Edition now supports two systems that monitor and log alarms. HMI tag alarm monitoring is still supported to maintain compatibility with existing applications. FactoryTalk Services Platform and FactoryTalk View Site Edition introduced a new system of monitoring alarm and event information.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Monitors alarms and events from third-party controllers. Tag-based alarm monitoring also makes it possible to monitor alarm conditions from third-party controllers, which communicate through OPC Data Servers. Provides accurate time stamps on alarm conditions that are generated from Logix5000 controllers using device-based alarm monitoring.
Migrate to FactoryTalk Alarms and Events if you want to: use device-based alarm monitoring. You can use a Logix5000 controller not only to detect alarms, but also to monitor alarms. This keeps all alarm and event processing in the controller. To use device-based alarm monitoring, add the builtin alarm instructions, available in RSLogix 5000 v. 16 or later, to a logic project and then download the project to a Logix5000 controller.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Where to start 8
FactoryTalk Alarms and Events components The following diagram shows a high-level view of the components of the FactoryTalk Alarms and Events system. For more detailed information, see FactoryTalk Alarms and Events Help (click Start, point to All Programs > Rockwell Software > FactoryTalk Tools and then click FactoryTalk Help). 1. Device-based alarm monitoring To do device-based alarm monitoring, you program alarm instructions, that are available with RSLogix 5000 v.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Use device-based alarm monitoring with: Logix5000 controllers, that you have programmed with RSLogix 5000 v. 16 or later software, and Rockwell Automation device servers (RSLinx Enterprise). 2. Tag-based alarm monitoring The Tag Alarm and Event Server uses tags to monitor programmable controllers for alarm conditions. When an alarm condition is detected, the server publishes the information to FactoryTalk Alarms and Events services.
Alarm and Event Summary Use the Alarm and Event Summary object, embedded in a FactoryTalk View graphic display, to acknowledge, disable, suppress, filter, and sort alarms at run time. Alarm and Event Banner Use the Alarm and Event Banner object, embedded in a FactoryTalk View graphic display, to monitor and respond to the most serious alarms that require immediate attention.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Tag-based alarm monitoring works like this (similar to HMI Tag Alarm Monitoring): This approach has several disadvantages: Programming is required in both the controller and the HMI software or Tag Alarm and Event Server. Tags must be duplicated in the HMI server and mapped to the controller. For Tag Alarm and Event Servers, controller tags must be mapped to alarms — in either case, a tedious, error-prone process.
Device-based alarm monitoring works like this: This approach has several advantages over software-based alarm detection: Alarm instructions are programmed only once, and then downloaded to the controller, which reduces programming effort and errors. Alarm conditions are detected more quickly. Alarms are detected at the same time the logic is being executed. HMI tags or alarms in a Tag Alarm and Event Server are not required, which reduces overhead and potential tag mapping errors.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Choosing between tag-based and device-based alarm monitoring Use tag-based alarm monitoring with: Logix5000 controllers PLC-5, SLC 500 devices Third-party controllers that communicate through OPC Data Servers Use device-based alarm monitoring with: Logix5000 controllers, using downloaded alarm instructions programmed with RSLogix 5000 v. 16 or later.
Chapter 2 Plan your system Before you build and deploy FactoryTalk Alarms and Events as part of a local or network application, consider which computer hardware and operating systems you plan to use, as well as where to install the various hardware and software components. The information in this chapter offers some guidelines as you begin planning. See also “Required software” on page 1 and “Recommended hardware and supported operating systems” on page 2.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Decide what type of alarm monitoring you need FactoryTalk Alarms and Events supports two types of alarm monitoring: Device-based alarm monitoring. Built-in alarm instructions, that are available in RSLogix 5000 v. 16 or later, are programmed in a logic project and then downloaded to a Logix5000 controller. The controller detects alarm conditions and publishes event information, which can be displayed and logged.
Follow these steps 17 • • • • • 2 • Plan your system
• • • • • FactoryTalk Alarms and Events System Configuration Guide Install and activate FactoryTalk software Follow these procedures to install and activate the software products required for FactoryTalk Alarms and Events. This guide describes how to set up a local application. The procedure to set up a network application is similar. This guide provides additional information about Network applications where it is necessary. See also Appendix H, “Reference for building a distributed system”.
Install FactoryTalk software For specific installation instructions, refer to the installation guide for each product. If you plan to build local applications, install everything on one computer. If you plan to build network applications distributed across multiple computers, see FactoryTalk Help (Start > All Programs > Rockwell Software > FactoryTalk Tools > FactoryTalk Help) for instructions.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 20
Chapter 3 Define device-based alarms in Logix5000 controllers To set up device-based alarm monitoring, you program alarm instructions, that are available with RSLogix 5000 v. 16 or later, and download them to a Logix5000 controller. The controller detects alarm conditions and notifies alarms and events services of alarm states.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Before you begin Review Chapter 2, “Plan your system”. Verify that you have installed and activated the software listed next under “What you need”. Verify that the Logix5000 firmware has been updated to version 16.
Follow these steps 23 • • • • • 3 • Define device-based alarms in Logix5000 controllers
• • • • • FactoryTalk Alarms and Events System Configuration Guide Define a digital alarm Digital tags are either on or off. They have states instead of limits. The alarm trigger condition compares the value of the tag to the configured alarm state.
5. Click OK to save the configuration and open it in RSLogix 5000, as shown here. Step 2: Create a rung of logic that will trigger the alarm 1. In the left pane, expand the folders Tasks > MainTask > MainProgram, and then double-click MainRoutine.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 2. On the Language Element toolbar, click the Examine-on instruction button (shown at left) to add it to a rung on the ladder project. 3. 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.
4. 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. Step 3: Add a digital alarm instruction to the rung 1. On the Language Element toolbar, click the Alarms tab, and then click the ALMD button (shown at left). The instruction block is placed in the ladder logic. 2. Inside the alarm instruction, beside ALMD, select the question mark. 3. On the File menu, click New Component, and then click Tag.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 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. Step 4: Specify a tag for each of the digital alarm’s operands, or just enter 0 1. Inside the alarm instruction, select the ProgAck operand. 2. On the File menu, click New Component, and then click Tag. 3. In the New Tag dialog box, type a name for the tag, select BOOL as the data type, and then click OK.
4. Create tags for the ProgReset, ProgDisable, and ProgEnable operands. When you are finished, the alarm instruction should resemble the one shown here: Step 5: Configure the properties of the new digital alarm tag: 1. Inside the alarm instruction, click the Browse button (shown at left). 2. In the ALMD Properties dialog box, specify configuration settings, and then click OK. For help with specifying configuration settings, click Help.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Step 6: 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. 3. If it is not already highlighted, select the controller to which you want to download the project.
4. Click Download. At the prompt, click Download again. The controller is placed in Program mode. Step 7: 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.
• • • • • 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. Step 8: Finish creating alarms, and next steps 1. Define additional digital alarms or analog alarms, using either ladder logic, function blocks, or structured text, and download the logic to the controller. 2.
Configure the alarm and download it to the controller This example uses the Function Block editor that comes with RSLogix 5000. You can also configure analog alarms in ladder logic or structured text. Step 1: Start RSLogix 5000 and then create a new project 1. Run RSLogix 5000 v. 16 or later software. 2. On the File menu, click New. 3. In the New Controller dialog box, select the required controller type from the Type list and then type a name for the new controller in the Name0 field.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 4. Click OK to save the configuration and open it in RSLogix 5000, as shown here. Step 2: Define a new routine 1. In the left pane, expand the Tasks folder, right-click MainProgram, and then click New Routine on the context menu.
2. In the New Routine dialog box, type a name for the routine. We used alarm_active. 3. In the Type list, click Function Block Diagram. 4. Select the Open Routine check box, and then click OK.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Step 3: Build the function block logic 1. To add an alarm block, go to the tabs in the center right area (Favorites, Add-On, and so on) as shown in the following illustration. Scroll to the right, and then click the Alarms tab. 2. On the toolbar, click the ALMA button (shown at left) to add an Analog Alarm block, as shown in the following illustration.
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.
• • • • • 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.
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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Step 4: Configure the properties of the alarm block 1. Click the Browse button on the alarm block. 2. In the ALMA Properties dialog box, set the Input Levels as shown in the following illustration and then click OK. To require that an operator acknowledge the alarm at run time, make sure the Acknowledgement Required check box is selected. To enter alarm messages and add variables for analog alarms, select the Messages tab.
Step 5: 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. 4. Select JSR and then click OK. 5. In the JSR instruction, double-click Routine Name and then click alarm_active in the list. 6.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Step 6: Download the program 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. 3. Select the controller to which you want to download the project. 4. Click Download. At the prompt, click Download again. 5.
Chapter 4 Add a device server for Logix5000, PLC-5, or SLC 500 controllers To use device-based alarms in Logix5000 controllers, or tag-based alarms in PLC-5, SLC 500, or Logix5000 controllers you must add a device server to your application. FactoryTalk Alarms and Events supports two types of alarm monitoring: Device-based alarm monitoring. Built-in alarm instructions, that are available in RSLogix 5000 v. 16 or later, are programmed in a logic project and then downloaded to a Logix5000 controller.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Follow these steps 44
Add a device server 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. If you are using third-party controllers, you do not need a device-based alarm server. Instead, go to Chapter 5, “Add an OPC Data Server for third-party controllers”. Step 1: Create an application in FactoryTalk View Studio This example shows how to create a local application. 1.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 3. In the New/Open Site Edition (Local) Application dialog box click the New tab. 4. In the Application name field, type a name for the new Local 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.
Step 2: Configure the device server 1. In the Explorer window, right-click the new 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 new server, and then click Apply. In this example, we named the server FTAE Server.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 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 49. 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. 4. Clear the Enable history check box and then click OK.
Step 3: Create a new shortcut to the controller 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. 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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 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: Set the Buffer Timeout setting for the length of time (zero to 120) you want to cache alarm information if the connection to the controller is lost. To disable alarm buffering set the value to zero. (See “Alarm buffering during loss of connection 4.
Step 4: Finish creating data servers, and next steps 1. If your FactoryTalk application includes third-party OPC-DA controllers, add an OPC Data Server, create a tag-based alarm server, and then define alarms. See Chapter 5, “Add an OPC Data Server for third-party controllers” and Chapter 6, “Add a tag-based alarm server for Logix5000, PLC-5, SLC 500, or third-party controllers”. 2.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 52
Chapter 5 Add an OPC Data Server for third-party controllers To monitor alarms in a third-party controller, create a controller program to detect alarm conditions and communicate them to tags. Use an OPC Data Server (for example, KEPWare server) to obtain tag values from the controller, and use a Tag FactoryTalk Alarm and Event Server to monitor those tags for alarm conditions. This chapter describes how to use RSLinx Classic as an OPC Data Server.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Follow these steps Add an OPC Data Server to an application When you add a data server to an application or area, tags published by the data server can be accessed by any client — in this case, the Tag Alarm and Event Server. This guide uses FactoryTalk View Studio to add a data server. You can also use FactoryTalk Administration Console. For more information, select Help > Contents from the FactoryTalk Administration Console window.
Step 1: Open an existing application in FactoryTalk View Studio 1. To run FactoryTalk View Studio on the Windows Start menu, click Start, point to All Programs > Rockwell Software > FactoryTalk View and then click FactoryTalk View Studio. 2. In the Application Type Selection window, select Site Edition (Local) and then click Continue. 3.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 4. In the Available OPC Data Servers dialog box, select RSLinx OPC Server, and then click OK. When creating a Network application, select RSLinx Remote OPC Server. 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”.
Chapter 6 Add a tag-based alarm server for Logix5000, PLC-5, SLC 500, or third-party controllers FactoryTalk Tag Alarm and Event Servers provide software-based alarms and events. Use tag alarm and event servers to monitor alarm conditions in Logix5000 controllers, PLC-5, SLC 500, or third-party OPC-DA programmable controllers.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Follow these steps 58
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 application previously, you can skip this step.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 3. In the New/Open Site Edition (Local) Application dialog box click the New tab. 4. In the Application name field, type a name for the new Local 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.
Add a data server Step 1: Configure the device server (RSLinx Enterprise) When you add a data server to an application or area, tags published by the data server can be accessed by any client — in this case, the Tag Alarm and Event Server. This guide uses FactoryTalk View Studio to add a data server. You can also use FactoryTalk Administration Console. For more information, select Help > Contents from the FactoryTalk Administration Console window.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Step 2: Create a new shortcut to the controller If you already created a shortcut to the controller in a previous chapter, you can skip this step. 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.
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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Add a Tag Alarm and Event Server To create a server and define alarm conditions that monitor tags for PLC-5 or SLC 500 controllers, and Logix5000 controllers, complete the following steps. These instructions apply to FactoryTalk View Studio. For help with FactoryTalk Administration Console, see FactoryTalk Help.
Define alarm conditions After you create a Tag Alarm and Event Server, you define the conditions that will trigger alarms at run time. This example shows how to create a digital alarm in a Tag Alarm and Event Server. 1. In the Explorer window, expand the TagAE server, and then double-click Alarm and Event Setup. 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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 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.
7. To close the Digital Alarm Properties dialog box, click OK. 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”.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 68
Chapter 7 Set up graphic displays Create graphic displays in FactoryTalk View Studio. They are containers for graphic objects, like the FactoryTalk Alarm and Event Summary object. Add FactoryTalk Alarm and Event objects to displays so that an operator can monitor and interact with both device-based and tag-based alarms at run time.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Follow these steps 70
Create a graphic display Create a graphic display to host FactoryTalk Alarm and Event objects, such as the Alarm and Event Summary. Step 1: Open an existing application in FactoryTalk View Studio 1. To run FactoryTalk View Studio, on the Windows Start menu, click Start, point to All Programs > Rockwell Software > FactoryTalk View and then click FactoryTalk View Studio. 2. In the Application Type Selection window, select Site Edition (Local) and then click Continue. 3.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Step 2: Create a graphic display to host FactoryTalk Alarms and Events objects 1. In the Explorer window, expand the Graphics folder, right-click Displays, and then click New. A blank display appears in the workspace. Next, add Factory Talk Alarm and Event objects to the graphic display.
Create an Alarm and Event Summary Use the Alarm and Event Summary object to view and interact with a summary of all the current alarms and events in an application. You can acknowledge, suppress, and disable alarms. You cannot use the Alarm and Event Summary to enable or turn alarm suppression off. To enable or turn alarm suppression off, use the Alarm Status Explorer. See “Monitor alarms and events” on page 103. To silence an alarm, use the Alarm and Event Banner.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 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. In any application, do not include more than two graphic displays that have Cache After Displaying and Always Updating set because these options can consume large numbers of processor cycles. 2.
Step 3: Save the display 1. On the File menu, click Save. 2. In the Save dialog box, type a name for the new display and then click OK. We used Alarm and Event Summary in the example shown. 3. Close the display. Create an Alarm and Event Banner display This section describes how to add an Alarm and Event Banner object to a graphic display, and then create a startup macro that docks the Banner to the bottom of the FactoryTalk View Site Edition Client window. Step 1: Create a new graphic display 1.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Step 2: Add an Alarm and Event Banner object to the display 1. On the Objects menu, point to Alarm and Event, and then click Banner (or, on the toolbar, click the Banner button, as shown at left). The Object drawing cursor appears in the blank display.
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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 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. Step 3: Configure the properties of the Alarm and Event Banner 1. To open the Alarm and Event Banner Properties dialog box, double-click the Alarm and Event Banner object. For details about all of the properties in the dialog box, click Help in the dialog box. 2.
3. Scroll down the list of commands on the right side of the wizard, select Display, and then click Next. 4. In the File list, click Alarm and Event Summary. 5. Select the Window Position check box. Scroll down the list on the right and then click Centered on the screen.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 6. Click Finish to save the Display command and add it to the Alarm and Event Banner Properties dialog box. 7. Click OK to close the dialog box.
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: Clear the Title Bar check box. Select Size to Main Window at Runtime. Select Allow Display to be Resized. Under When Resized, select Scale if it is not already selected. The Alarm and Event Banner graphic display is always visible because it is docked.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Step 5: Save the graphic display 1. On the File menu, click Save. 2. In the Save dialog box, type a name for the graphic display and then click OK. In this example, we used Alarm and Event Banner. 3. Close the graphic display. Create a startup macro for the Banner display This section describes how to create a startup macro. You will use the macro when you configure the FactoryTalk View Site Edition Client.
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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 4. In the File list, click Alarm and Event Banner. 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.
Step 1: Create a new graphic display 1. In the Explorer window, expand the Graphics folder. 2. Right-click Displays, and then click New on the context menu. Step 2: Add an Alarm and Event Summary to the graphic display 1. On the Objects menu, point to Alarm and Event, and then click Summary (or on the toolbar, click the Summary button, as shown at left). 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. 3.
• • • • • 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. 5. On the Objects menu, point to Drawing and then click Rectangle. 6. In the graphic display, hold down the left mouse button and then drag the mouse to draw a box for the alarm status indicator.
Step 3: Add an expression to animate the rectangle 1. Right-click the rectangle, point to Animation and then click Color on the context menu. To create an expression for the color animation, you can compose the expression step by step, as explained in the following steps, or you can type the following expression in the Expression box.
• • • • • 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. 4. In the Expression Editor, click Functions. 5. In the Functions dialog box, in the list of Function Categories, click Alarm and Event. The HMI Tag Alarming category contains functions that apply only to HMI tags located in an HMI server.
7. In the Expression Editor, the AE_InAlmUnackedCount( ) function appears in the Expression box, with the cursor between the parentheses. Next, type “*” to return a count of all alarms that are in the same location (area) as the HMI server 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.
• • • • • 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.
Step 4: Set up colors for the alarm states This step, describes how to set up colors for the rectangle, for each solution to the expression. 1. In the Animation dialog box, under Expression, click state A. 2. In the Value box, type 0. 3. Beside Background, click Blink. 4. Beside Background, make sure the colored boxes are set to red (for the foreground color) and black (for the background color). 5.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Step 6: Test run the display 1. On the View menu, click Test Display, or click the Test Display button (shown at left) on the toolbar. If there are unacknowledged alarms whose alarm condition is In Alarm, the rectangle flashes red. 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.
3. Continue experimenting to observe the effects of acknowledging alarms: If there are no active alarms, but there are normal unacknowledged alarms, the rectangle is yellow. If there are no active or unacknowledged alarms, the rectangle is green. 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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 94
Chapter 8 Monitor and interact with alarms at run time To interact with alarms and events at run time, set up a FactoryTalk View Site Edition Client. Next, run the FactoryTalk View Site Edition Client and then monitor the graphic displays that host the Alarm and Event graphic objects. Before you begin Be sure you have defined alarms as described in Chapter 3, “Define device-based alarms in Logix5000 controllers”.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Follow these steps 96
Create and then run a FactoryTalk View Client configuration To run an application and monitor graphic displays for alarm messages, start the FactoryTalk View Site Edition Client. For this example, be sure that the controller is running the West_Plant_Controller program that we created in Chapter 3, and that you have tripped the alarm (rightclick the rung contact and then click Toggle Bit). Step 1: Create a FactoryTalk View Site Edition Client configuration file 1.
• • • • • 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 and then click Next.
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, you 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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 7. In the FactoryTalk View SE Client Window Properties dialog box, you 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.
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.
• • • • • 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. Step 3: Next steps Do one of the following: 102 Monitor and interact with alarms and events as shown in the next section.
Monitor alarms and events The data fields in the Alarm and Event Banner window are organized in columns, and represent various alarm and event data. At run time, only the columns that were configured at design time to be visible are displayed in the Alarm and Event Banner. In our example, the status bar shows (from left to right): the connection status of the Tag Alarm and Event Server — whether connected or disconnected from the Alarm and Event Banner.
• • • • • 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. 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.
To acknowledge the selected alarm and enter a comment: 1. In the Alarm and Event Summary event list, do one of the following: Select the alarms you want to acknowledge, and then click Acknowledge selected alarm with comment. Select the alarms you want to acknowledge, right-click the selected alarms, and then click Ack Comment on the context menu. 2. In the Acknowledge Alarm with Comment dialog box, type a comment, and then click Acknowledge.
• • • • • FactoryTalk Alarms and Events System Configuration Guide To acknowledge all of the alarms displayed on the page: In the Alarm and Event Summary toolbar, do one of the following: Click Ack page of alarms. All alarms currently visible in the event list are acknowledged. Right-click one of the alarms and then click Ack Page on the context menu.
Disable or enable an alarm Disabled alarms When an alarm is disabled the operator is not notified when the alarm condition occurs and the alarm is removed from the Alarm and Event Summary. An alarm that is disabled is effectively turned off in the controller. The alarm condition is no longer monitored and notifications are not generated by the controller. Disabled alarms do not sound the alarm bell in the Alarm and Event Banner, and are not displayed as new events in the Alarm and Event Summary.
• • • • • FactoryTalk Alarms and Events System Configuration Guide To disable selected alarms: 1. In the Alarm and Event Summary event list, do one of the following: Select the alarms you want to disable, and then on the toolbar, click the Disable selected alarm button. Select the alarms you want to disable, right-click the selected alarms, and then click Disable Alarm on the context menu. 2.
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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Suppress or unsuppress an alarm You can suppress an alarm that is not needed temporarily; for example, because the alarm is caused by another alarm that you are already addressing. You can suppress or unsuppress up to 2000 alarms at one time. A suppressed alarm does not appear in the Alarm and Event Banner, or Alarm and Event Summary.
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 After you acknowledge a suppressed alarm, the suppressed alarm will not appear in the Alarm and Event Banner, or Alarm and Event Summary. You can use the Alarm Status Explorer to unsuppress alarms.
• • • • • 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.
Chapter 9 Set up historical alarm and event logging Use the FactoryTalk Alarm and Event Log Viewer to view alarms and events that have been logged to a Microsoft SQL Server database that is configured to store historical alarm and event data. If you do not have a Microsoft SQL Server database installed, we recommend that you install Microsoft SQL Server 2005 Express (SP2) using the batch file available on both the FactoryTalk View and RSLinx Enterprise installation CDs in the Redist folder.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Before you begin If you do not already have Microsoft SQL Server software installed, you can install Microsoft SQL Server 2005 Express (SP2), which is available from the \Redist folder on both the FactoryTalk View and RSLinx Enterprise installation CDs.
Follow these steps 115 • • • • • 9 • Set up historical alarm and event logging
• • • • • FactoryTalk Alarms and Events System Configuration Guide Confirm that the Microsoft SQL Server software is installed To log historical alarms and events, you can either install Microsoft SQL Server 2005 Express (SP2), or you can use an existing Microsoft SQL Server database already installed on your network. If you are using an existing Microsoft SQL Server database you will need to set up your database for alarm and event logging. See “Summary of steps” on page 184.
3. In the New/Open Site Edition (Local) 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”. Step 2: Create a new database connection 1. In the Explorer window, expand the folders System > Connections, and then right-click the Databases folder. On the context menu, click New Database.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 2. In the Alarm and Event Historian Database Properties dialog box, configure properties for the new database definition. To improve efficiency when writing to the database, information is sent to a cache file located on the computer hosting the alarm server before writing to the database.
If the database or user does not already exist in SQL Server, you are prompted to create them. Click Yes. Limit how much information is cached to files if the database connection is lost. After the limits are reached the oldest information is overwritten. 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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 3. In the New/Open Site Edition (Local) 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”. Step 2: Configure the alarm server 1. In the Explorer window, expand the application tree until each alarm server is visible. 2.
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).
• • • • • 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.
Step 2: Create a new graphic display 1. In the Explorer window, expand the Graphics folder, right-click Displays, and then click New. A blank display appears in the workspace. 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 Log Viewer toolbar button, as shown at left). 2.
• • • • • 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.
Step 5: Save the graphic display 1. On the File menu, click Save. 2. In the Save dialog box, type a name for the new display and then click OK. In this example, we used Alarm and Event Log Viewer for the name of the graphic display. 3. Close the graphic display. 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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Step 2: Add a button to the graphic display 1. On the Objects menu, point to Push Button, and then click Button (or click the Add Button button on the toolbar). 2. Hold the left mouse button down and drag the mouse to create a rectangle the correct size for the button and then release the mouse button. 3. In the Button Properties dialog box, click the Action tab.
Step 3: Configure the button commands 1. Click the browse button to the right of the Press action field, to open the Command Wizard. 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. 4. In the File list, select the name of the graphic display that is to open when the button is clicked.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 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. 6. Click the Up Appearance tab. 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.
Step 4: Configure the properties of the graphic display 1. On the Edit menu, click Display Settings. 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. Step 5: Save the graphic display 1. On the File menu, click Save. 2.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Step 1: Edit the startup macro 1. In FactoryTalk View Studio, in the Explorer window, double-click the Start Alarm and Event Banner macro. The macro editor opens, showing the Banner display command (Display “Alarm and Event Banner” /DB). 2. To open the Command Wizard, double-click anywhere in the body of the macro editor. 3. In the list of commands on the right, select Display, and then click Next. 4. In the File list, click Menu Bar. 5.
6. To save the configuration and display it in the macro editor, click Finish. Step 2: Save the startup macro 1. On the File menu, click Save. 2. Close the macro editor. View historical alarm data in a FactoryTalk View SE Client Use the Alarm and Event Log Viewer — embedded in a FactoryTalk View graphic display — to view, sort, filter, and export historical alarm information stored in Alarm and Event Logs.
• • • • • FactoryTalk Alarms and Events System Configuration Guide To start the FactoryTalk View SE Client from within FactoryTalk View Studio: 1. If FactoryTalk View Studio is not still open, on the Windows Start menu, point to Programs > Rockwell Software > FactoryTalk View Enterprise, and then click FactoryTalk View Studio. 2. In the Application Type Selection window, select Site Edition (Local) and then click Continue. 3. In the New/Open Site Edition (Local) Application dialog box, click Cancel. 4.
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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 6.
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. For details about enabling, disabling, suppressing, unsuppressing, and acknowledging alarms, see Chapter 8, “Monitor and interact with alarms at run time”, or see FactoryTalk Help: on the Windows Start menu, click Start > All Programs > Rockwell Software > FactoryTalk Tools > FactoryTalk Help.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 136
Appendix A Getting started with language switching You can use language switching to display text strings that you define when you create an application, in up to 40 different languages. At run time, a FactoryTalk View SE Client can switch between any of the languages the application supports. In a network application, multiple clients can run in different languages at the same time. For information, see “Language identifiers for language switching” on page 217.
• • • • • FactoryTalk Alarms and Events System Configuration Guide What you need If you are using device-based alarms RSLogix 5000 v. 16 or later RSLinx Enterprise ControlFLASH FactoryTalk View Studio RSLinx Classic FactoryTalk View SE Client If you are using tag-based alarms 138 PLC-5, SLC 500, third-party, or Logix5000 controllers that have not been programmed with alarm instructions included in RSLogix 5000 v.
Follow these steps Create device-based alarm messages To create device-based alarm messages in multiple languages you can use the import and export features in RSLogix 5000. At run time, alarm messages located in Logix5000 controllers can be displayed in the language of the FactoryTalk View application in which they are displayed. When RSLinx Enterprise connects to the controller, all alarm messages and their languages are uploaded from the controller.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Translate alarm messages using import and export A system may have thousands of alarm messages that need to be translated. To simplify this process, you can export alarm messages from RSLogix 5000 to a file, add translated messages in multiple languages to the file, and then import the file back into your project. Any of the languages you translate the strings into must be supported by FactoryTalk View.
3. In the Export dialog box, click Export. If your RSLogix 5000 project includes a large number of programs, and you want to translate alarm messages from only one of them, you can make selections in the Export dialog box to limit the data that is exported. For details, click Help in the dialog box. 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 .
• • • • • 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!”. 6. On the File menu, click Save to save the file. When you import alarm messages, RSLogix 5000 v. 16 verifies the message length and displays a warning if the alarm message exceeds the character limit.
Step 3: Import the translated alarm messages 1. In the RSLogix 5000 window, on the Tools menu, click Import. 2. In the Import window, select the file you modified and then click Import. The import process produces warnings because it overwrote existing tags.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Step 4: Download the project to the controller To update the controller with additional alarm messages in the new languages, download the project to the controller. Next, either continue setting up tag-based alarm messages, or set up a graphic display for language switching. See “Add buttons to a graphic display to switch languages at run time” on page 153. Translating alarm messages using RSLogix 5000 v.
4. After you select a language for the project, the Project Documentation Language Configuration dialog box opens. To export a localization file, click Export. If the dialog box does not open, click Documentation Languages on the Tools menu. 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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Step 2: Translate the exported alarm messages 1. In Windows Explorer, locate the file you exported. Right-click the file, point to Open With and then click Microsoft Excel. 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)].
4. Verify the languages you want to import in the Import Project Documentation dialog box and then click Import. 5. Click OK. When you import alarm messages, RSLogix 5000 v. 17 will verify the message length and display a warning if the alarm message exceeds the 255 character limit. Step 4: Download the project to the controller To update the controller with additional alarm messages in the new languages, download the project to the controller.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 2. In the Application Type Selection window, select Site Edition (Local) and then click Continue. 3. In the New/Open Site Edition (Local) 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.
Step 2: Create a digital alarm This section uses the FactoryTalk Tag Alarm and Event Server you created in Chapter 6, “Add a tag-based alarm server for Logix5000, PLC-5, SLC 500, or third-party controllers”. If you haven’t yet created the server, do so before continuing. 1. In the Explorer window, expand the new Tag Server, and then double-click Alarm and Event Setup. 2. In the Alarm Setup dialog box, click the Digital tab. 3. On the toolbar, click the New button (shown at left).
• • • • • FactoryTalk Alarms and Events System Configuration Guide 4. In the Digital Alarm Properties dialog box, in the Name box, type TankTempThreshold.
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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Add languages to the application 1. In FactoryTalk View Studio, on the Tools menu, click Languages. 2. In the Language Configuration dialog box, select the Display undefined strings using the default language check box, and then click Add. 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.
5. In the Add Language dialog box, click Italian (Italy) and then click OK. 6. In the Language Configuration dialog box, click OK. Add buttons to a graphic display to switch languages at run time In this section, we’ll add a button to a graphic display, to switch among available languages at run time. Step 1: Create a new graphic display 1. In FactoryTalk View Studio, in the Explorer window, expand the Graphics folder. 2. Right-click Displays, and then click New on the context menu.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Step 2: Add buttons to the graphic display 1. On the Objects menu, click Button and then click Push Button. 2. In the graphic display, hold down the left mouse button and then drag the mouse to draw a box for the button. 3. On the Edit menu, click Copy. 4. On the keyboard, press Ctrl-V twice, to paste two more copies of the button in the graphic display. 5. Drag the copies of the button apart on the display. 6.
Step 3: Add captions to the buttons 1. Double-click the first button to edit it. 2. In the Button Properties dialog box, click the Action tab. 3. Click the browse button to the right of the Release action field. The Command Wizard opens. 4. In the Command Categories pane on the left, expand All Commands and Macros. 5. In the list of commands on the right, click Language, and then click Next. 6. In the Language ID list, select the name of the language and then click Finish.
• • • • • 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. Step 4: Add an Alarm and Event Summary to the graphic display 1.
Step 5: Save and then close the graphic display 1. On the File menu, click Save. 2. In the Save dialog box, type a name for the graphic display and then click OK. In this example, we used Alarm Summary Multilingual. 3. On the File menu, click Close to close the graphic display. Enter alarm messages in other languages In this section, we’ll edit our application twice. The first time, we’ll open the application in Italian, and then we’ll enter the Italian alarm message in the Alarm Properties dialog box.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 4. In the Language list, select Italian (Italy), it-IT and then click Open. Step 2: Enter the alarm message for the digital alarm 1. In the Explorer window, expand the Tag Server, and then double-click Alarm and Event Setup.
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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Step 3: Export alarm messages to an Excel spreadsheet 1. Right-click the Tag Alarm and Event Server where the alarms are defined, and then click Import and Export on the context menu. In this example, right-click the Tag Alarm and Event Server called Tag Server. 2. In the Alarm Import Export Wizard, in the Operation Type window, leave Export alarm configuration to Excel file selected and then click Next.
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.
• • • • • 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). 6. After the export is complete, click OK. Step 4: Enter alarm messages in Excel 1. Locate the exported alarm file and then double-click it to open it in Microsoft Excel.
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.
• • • • • 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.
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.
• • • • • 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.
Step 2: Create a FactoryTalk View Site Edition Client configuration file 1. In the FactoryTalk View Client Wizard, click New. 2. In the FactoryTalk View SE Client Configuration Name window, type a name for the configuration file. In this example, we used Multilingual Alarms. Keep the default path for the configuration file and then click Next. For details about using the FactoryTalk View Site Edition Client Wizard, click Help in the wizard. 3.
• • • • • 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”. 5. In the FactoryTalk View SE Client Components window, select the FactoryTalk View components that run when the FactoryTalk View Site Edition Client starts.
6. In the FactoryTalk View SE Client Window Properties window, you 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, and does not switch languages. Don’t change any of the other settings in this window. Click Next. 7.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 8. In the FactoryTalk View SE Client Completion Options window, click Save configuration and open FactoryTalk View SE Client now, and then click Finish. Test alarm messages at run time For details about triggering an alarm in RSLogix 5000, see “Test the alarm instruction by switching to run mode and triggering the alarm” on page 31.
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.
• • • • • 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. Summary and tips for setting up language switching To set up language switching for an application: 1. Develop the application in a base language. 2. Export the application’s user-defined text strings.
Text that supports language switching In general, the user-defined strings that support language switching are those that an operator sees in an application at run time. Specifically, these are: text you specify for graphic objects and global objects including captions, tool tip text, time and date embedded variables, and numeric embedded variables. graphic and global object display titles specified in the Display Settings dialog box.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Alarm and Event Log Viewer You can use the Alarm and Event Log Viewer to configure column headings, button captions, and button tooltips in multiple languages. Define strings in one language at a time. FactoryTalk View controls which language is displayed. When the Alarm and Event Log Viewer is notified of a language switch, the contents of the viewer, which consists of report data, are not translated.
Appendix B System performance and limits FactoryTalk Alarms and Events has been tested to conform to the following performance limits.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Tested system limits Tested limit Value Number of alarms per FactoryTalk application 20,000 Number of Rockwell Automation Device Servers per application 2 Number of alarms per Rockwell Automation Device Server (RSLinx Enterprise) 10,000 Number of Tag Alarm and Event Servers per application 2 Number of alarms per Tag Alarm and Event Server 10,000 Alarm burst (number of alarms occurring at once) 2000 Simultaneous alarm operatio
Tested topology Non-redundant topology: All testing was performed on the recommended hardware. See the FactoryTalk View Site Edition Installation Guide. In FactoryTalk View Studio, click the Help menu, point to Online Books, and then click Installation Guide.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 178
Appendix C Install FactoryTalk Alarms and Events manually FactoryTalk Alarms and Events software is installed when you install FactoryTalk View Site Edition and RSLinx Enterprise software; it is not installed as part of the FactoryTalk Services Platform. If you installed the platform on a computer where FactoryTalk View Site Edition and RSLinx Enterprise are not installed, you will not have the FactoryTalk Alarms and Events software, and must install it manually.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Summary of steps Step 1: Confirm that the FactoryTalk Services Platform is installed on the computer where you’re going to install FactoryTalk Alarms and Events. Step 2: Install FactoryTalk Alarms and Events software. Step 1: Confirm that the FactoryTalk Services Platform is installed The FactoryTalk Services Platform must be installed before installing FactoryTalk Alarms and Events.
6. Select the Complete Installation option, and then click Next. The Client-only option is not applicable for this release. 7. To install Microsoft SQL Server 2005 Express (SP2) after installing FactoryTalk Alarms and Events, leave the check box selected, and then click Next. If you already have a Microsoft SQL Server database that you want to use for logging alarm and event information, clear the check box, and then click Next. 8. Click Install to begin the installation. 9.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 182
Appendix D Install Microsoft SQL Server 2005 Express FactoryTalk Alarms and Events uses Microsoft SQL Server as the database engine for logging alarm and event information. You can connect to an existing SQL Server database, or you can install Microsoft SQL Server 2005 Express, Service Pack 2, which is included in the Redist folder on the FactoryTalk View Site Edition and RSLinx Enterprise CDs.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Summary of steps Following is a summary of the steps required to install Microsoft SQL Server 2005 Express. Each step is described in more detail on the following pages. Step 1: Open the Redist folder, which is at the root of the FactoryTalk View Site Edition or RSLinx Enterprise CD. This folder contains the software for Microsoft SQL Server 2005 Express (SP2) and its prerequisite software. Step 2: Install the .
Step 2: Install the .NET Framework and other prerequisite software Install the software components described in the following sections. .NET Framework Microsoft .NET Framework version 2.0.50727 is installed with FactoryTalk View SE and RSLinx Enterprise. If you’ve installed those products on the computer where you are installing Microsoft SQL Server 2005 Express, you will already have the correct version of the .NET Framework and don’t need to install it again.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 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 it is not, install it. To install MSXML6: 1. At the root of the FactoryTalk View SE or RSLinx Enterprise CD, open the Redist folder, open the MSXML6 folder, and then double-click msxml6.msi. 2. Follow the on-screen instructions. Windows Installer 3.
To install Microsoft SQL Server 2005 Express: 1. Close any programs that are open. 2. At the root of the FactoryTalk View SE or RSLinx Enterprise CD, open the Redist folder, open the SQLServer2005 folder, and then double-click SQL Server Install.bat. 3. Review the End User License Agreement, select the check box to accept it, and then click Next. 4. In the Installing Prerequisites window, click Install, and then click Next on subsequent windows.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 7. In the Authentication Mode window, leave the authentication mode set to Mixed Mode, type a strong password for the system administrator account, and then click Next. Be sure to remember the password, because you’ll need it to create the database objects for the FactoryTalk Alarm and Event Historian.
Step 4: Install Microsoft SQL Server Management Studio Express Use Microsoft SQL Server Management Studio Express to perform management operations on the alarms and events database, such as adding or removing users. To install Microsoft SQL Server Management Studio Express: 1. Close any programs that are open. 2. At the root of the FactoryTalk View Site Edition or RSLinx Enterprise CD, open the Redist folder, open the SQLServer2005 folder, and then double-click SQLServer2005_SSMSEE.msi. 3.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Step 5: Configure the Windows firewall If you want to allow remote connections to the SQL Server 2005 Express database, the database engine service and the SQL Server Browser service must be added to the Windows Firewall Exception List. Set this up if you: have remote clients (for example, a log viewer) that needs access to the database want to configure the database remotely To configure the Windows firewall: 1.
Appendix E Use an existing Microsoft SQL Server database FactoryTalk Alarms and Events uses Microsoft SQL Server as the database engine for logging alarm and event information. You can connect to an existing SQL Server database, or you can install Microsoft SQL Server 2005 Express, Service Pack 2, which is included in the Redist folder on the FactoryTalk View Site Edition and RSLinx Enterprise CDs. For more information, see Appendix D, “Install Microsoft SQL Server 2005 Express”.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Step 1: Install Microsoft SQL Server Management Tools To add the SQL Server 2005 Management Tools to an existing instance of SQL Server 2005, follow these steps: 1. Close any open programs. 2. In Control Panel, open Add or Remove Programs. 3. Under Currently installed programs, select Microsoft SQL Server 2005, and then click Change. 4. On the Component Selection page, click To install a new component, click here. 5.
10. Click Install to begin the installation. 11. When the installation is finished, click Finish to close the window. 12. 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, point to All Programs > Microsoft SQL Server 2005 and then click SQL Server Management Studio. 2.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Step 3: Configure TCP/IP protocol for the database To configure TCP/IP protocol, complete the following steps: 1. Click Start, point to All Programs > Microsoft SQL Server 2005 > Configuration Tools and then click SQL Server Surface Area Configuration. 2. On the SQL Server 2005 Surface Area Configuration page, click Surface Area Configuration for Services and Connections. 3.
Step 5: Configure the Windows Firewall To configure the Windows Firewall, perform the following steps: 1. Click Start, point to Control Panel, and then double-click Windows Firewall. 2. On the Exceptions tab, SQL Server (sqlservr.exe) might be listed in the Programs and Services box, but not selected as an exception. If you select the check box, Windows will open port 1433 to allow TCP requests. Alternatively, if you do not see SQL Server listed: Click the Add Program button. Click the Browse button.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 196
Appendix F Alarm time stamping FactoryTalk Alarms and Events provides significantly improved time-stamp accuracy over traditional alarm monitoring systems, you can obtain better time-stamp resolution in some cases by using time stamps directly retrieved from peripheral devices like I/O cards or other time-stamping hardware.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Coordinated Universal Time (UTC) Coordinated Universal Time is a real-world time relative to a time constant, but with no time zone information and no daylight savings time offsets. It is the raw value used to represent time and also the value required for time stamps in the FactoryTalk Alarms and Events system. UTC is equivalent to Greenwich Mean Time, with no daylight savings time offsets.
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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide FactoryTalk Alarms and Events: features for alarm monitoring ALMD and ALMA alarm blocks When the controller detects a condition that causes an In Alarm event, the controller stores the current UTC value in the backing tag for the alarm. 1. The alarm is provided by ladder logic that includes the ALMD or ALMA instructions: 2.
3. On the Status tab, time stamps appear when the alarm is triggered, acknowledged, returns to normal, or when the alarm count is reset. 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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Inserting time stamps manually To insert a time stamp manually, you must enter the new time under the .ProgTime element and set the boolean .UseProgTime in the backing tag for the alarm before the actual alarm instruction is triggered.
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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Install the Logix5000 Clock Update Tool This stand-alone tool is included on the RSLogix 5000 v. 16 CD.
Using the Logix5000 Clock Update Tool The Logix5000 Clock Update Tool lets you view and synchronize the system time of the controllers and devices on a network, using any computer running Microsoft Windows and RSLinx Classic. You can also schedule automatic synchronization of all devices. 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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Create a synchronization schedule A synchronization schedule determines when devices are synchronized. For example, you can schedule devices to be synchronized on a fixed time interval. You can also configure a synchronization schedule to expire on a particular date. To create a synchronization schedule: 1. In the Logix5000 Clock Update Tool, in the left pane, click Scheduled Synchronizations. 2.
Remove a synchronization schedule To remove a synchronization schedule from the list, right-click the synchronization schedule you want to remove and then click Remove Event. Any devices that are associated with this synchronization schedule now belong to no schedule. Modify a synchronization schedule 1. To modify an existing synchronization schedule, right-click the synchronization schedule and then click Modify Event. 2.
• • • • • 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.
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.
• • • • • 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. Assign devices to synchronization schedules When a synchronization schedule is selected in the left pane, the Device pane lists all of the devices that are configured. When you add a new device, you can assign it to a specific schedule at that time. See “Add devices” on page 208.
Synchronize devices manually In addition to scheduling automatic synchronization, you can synchronize devices manually. Right-click a device and then click Synchronize Device or right-click anywhere in the Device pane and then click Synchronize All Devices (or click the Synchronize All Devices button on the toolbar). Any errors in synchronization are saved to the log file. In addition, an icon appears in the device list and in the main tree view to indicate the error.
• • • • • 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.
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.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 214
Appendix H Reference for building a distributed system This book focuses on building an alarms and events system on a single computer. When building a distributed system on multiple computers on the network, bear the following guidelines in mind. Installing FactoryTalk Alarms & Events software FactoryTalk Alarms and Events software is installed with FactoryTalk View and RSLinx Enterprise software.
• • • • • FactoryTalk Alarms and Events System Configuration Guide Typical distributed system on a network 216
Appendix I Language identifiers for language switching With the FactoryTalk View language switching feature, run-time operators can view the text strings defined in an application in up to 40 different languages. FactoryTalk View SE Clients can run in any of the languages an application supports. In a network application, multiple clients can run in different languages at the same time. The languages in the following table are supported for language switching by the application at run time.
• • • • • FactoryTalk Alarms and Events System Configuration Guide 218 Language ID Arabic (Qatar) ar-QA Arabic (Saudi Arabia) ar-SA Arabic (Syria) ar-SY Arabic (Tunisia) ar-TN Arabic (U.A.E.
Language ID 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 Galicia
• • • • • FactoryTalk Alarms and Events System Configuration Guide 220 Language ID 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 (In
Language ID 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)
• • • • • FactoryTalk Alarms and Events System Configuration Guide Language ID 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 inform
Index Symbols ??? appears at run time in graphic displays 152 .csv files do not support Unicode in RSLogix 5000 141 .NET Framework installing 185 .txt files using with Unicode character sets for language switching in RSLogix 5000 141 .xls files exporting alarm messages from Tag Alarm and Event Servers 147 .
• • • • • FactoryTalk Alarms and Events Configuration Guide acknowledging alarms 104 all in event list 106 alarm instructions all on page 106 adding to rung in RSLogix 5000 27 with comment 105 built into RSLogix5000 controllers 5 activations planning 18 Alarm and Event Banner alarm messages advantages of using Excel to edit 157 creating in FactoryTalk View Studio 147 about 11 default location for exported 162 adding to graphic displays 75, 76 editing exported in Notepad 141, 146 definition of
unsuppressing 73, 110, 111 alarms and events See also alarm monitoring viewing details 105 See also alarms and events viewing historical 131 See also FactoryTalk Alarms and Events ALMA instructions 36 about acknowledging 104 connecting to input references 39 about monitoring for 11 ALMD instructions adding to RSLogix 5000 27 acknowledging all in event list 106 acknowledging all on page 106 Always Updating option for graphic displays in FactoryTalk View 74 acknowledging selected 104 acknowledgin
• • • • • FactoryTalk Alarms and Events Configuration Guide clock synchronization configuration files for FactoryTalk View SE Client 97, 166 CompactLogix controllers 213 ControlLogix processors 213 connections DriveLogix controllers 213 database, for alarm and event historical logging 117 FlexLogix controllers 213 status of Tag Alarm and Event Server at run time 103 manual 211 ControlFLASH MicroLogix controllers 213 device-based alarm monitoring 22 PLC-5 controllers 213 language switching 138
data servers device-based alarm monitoring adding 47, 53 about 5, 9, 13 adding for PLC-5 controllers 43 choosing over tag-based 16, 43 adding for SLC 500 controllers 43 compared with software-based 13 adding RSLinx Enterprise 43 ControlFLASH 22 adding to applications in FactoryTalk View 55 definition of 9 enabling alarms and events 48 FactoryTalk Administration Console 43 RSLinx OPC Server versus RSLinx Remote OPC Server 56 FactoryTalk View Studio 43 database definitions how it works 13 lan
• • • • • FactoryTalk Alarms and Events Configuration Guide E FactoryTalk Security embedded variables in RSLogix 5000 40 enabling alarms 73, 109 in Alarm Status Explorer 109 in Tag Alarm and Event Servers 107 events. See alarms and events and alarms and events 6 FactoryTalk Services Platform version required 1 FactoryTalk View ME 45, 59 See also FactoryTalk View Studio FactoryTalk View SE 95 existing applications.
FactoryTalk View Studio 69, 114 G See also FactoryTalk View ME getting started 8 See also FactoryTalk View SE graphic displays adding data servers 55 See also graphic objects adding Tag Alarm and Event Servers 64 about 69 as alternative to FactoryTalk Administration Console 54, 61 adding buttons 126 adding drawing objects 86 Command Wizard 79 centering on screen 79 creating alarm messages 147 creating in FactoryTalk View 71, 72 creating applications 45, 59 creating in FactoryTalk View Studi
• • • • • FactoryTalk Alarms and Events Configuration Guide historical alarms J do not switch languages 137 JSR instructions viewing 131 historical logging associating databases with alarm servers 119 adding to RSLogix 5000 41 K KEPWare OPC data server database definitions 113 enabling in RSLinx Enterprise 119 enabling in Tag Alarm and Event Servers 119 language switching 139 Microsoft SQL Server Express 114 setting up for alarms and events 113 SQL Server Express 113 HMI Tag Alarm Log Viewer 14 HMI
language switching 137 languages about 139 editing alarm messages 157 Alarm and Event Banner 173 editing applications in different 157 Alarm and Event Log Viewer 174 importing alarm messages into Tag Alarm and Event Servers 164 Alarm and Event Summary 173 alarm messages in FactoryTalk View Studio 147 limits ControlFLASH 138 controller specifications 175 device-based alarm messages 139 tested system limits 175, 176 displaying undefined strings in default language 152 Local applications.
• • • • • FactoryTalk Alarms and Events Configuration Guide Logix5000 controllers 31 See also Logix5000 firmware M macros about built-in alarm instructions 5 creating 129 acknowledgement required 40 editing 130 adding device servers 43 saving 84, 131 ALMA instructions 36 startup 82, 129, 130 analog alarms 32 configuring alarm blocks 40 creating alarms 21 defining routines 34 digital alarms 24 downloading programs to 30 embedded variables in alarm messages 40 firmware required for device-based al
Microsoft SQL Server.
• • • • • FactoryTalk Alarms and Events Configuration Guide R RSLogix 5 53 required hardware 2 language switching 138 required software 1 tag-based alarm monitoring 57 resizing version required 1 graphic displays 74, 81, 129 Rockwell Automation Device Server.
Run Mode for Logix5000 controllers 31, 42 run time about displayed data at 6 interacting with alarms 95 software required 1 software-based alarm monitoring compared with device-based 13 monitoring alarms 95 software-based tag servers. See Tag Alarm and Event Servers setting up window in FactoryTalk View SE Client 100 stand-alone applications.
• • • • • FactoryTalk Alarms and Events Configuration Guide T tags Tag Alarm and Event Servers about 5, 57 adding for PLC-5 controllers 57 adding for SLC 500 controllers 57 adding for third-party controllers 57 in RSLogix 5000 38 test run graphic displays 92 third-party controllers adding in FactoryTalk View Studio 64 adding data servers for 53 adding to applications 64 adding Tag Alarm and Event Servers for 57 connection status at run time 103 support for alarms and events 4 creating alarms 65,
U undefined strings displaying in default language 152 Unicode character sets language switching in RSLogix 5000 141 using .txt files with RSLogix 5000 141 unsuppressing alarms 73, 110, 111 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.
• • • • • FactoryTalk Alarms and Events Configuration Guide xxiv
