Beruflich Dokumente
Kultur Dokumente
Original Instructions
Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are
required to be carried out by suitably trained personnel in accordance with applicable code of practice.
If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may
be impaired.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from
the use or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and
requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or
liability for actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or
software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation,
Inc., is prohibited
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous
environment, which may lead to personal injury or death, property damage, or economic loss.
ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property
damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence.
IMPORTANT Identifies information that is critical for successful application and understanding of the product.
SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous
voltage may be present.
BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may
reach dangerous temperatures.
ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to
potential Arc Flash. Arc Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL
Regulatory requirements for safe work practices and for Personal Protective Equipment (PPE).
Table of Contents
Preface
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chapter 1
Logix Change Detector Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
(L_ChangeDet) Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Required Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Controller Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Logix Change Detector InOut Structure . . . . . . . . . . . . . . . . . . . . 12
Logix Change Detector Input Structure . . . . . . . . . . . . . . . . . . . . . 13
Logix Change Detector Output Structure . . . . . . . . . . . . . . . . . . . 13
Logix Change Detector Local Configuration Tags. . . . . . . . . . . . 14
Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Programming Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Chapter 2
Logix Controller CPU Utilization Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
(L_CPU) Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Required Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Controller Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Visualization Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Controller Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Logix Controller CPU Utilization InOut Structure . . . . . . . . . . 25
Logix Controller CPU Utilization Input Structure . . . . . . . . . . . 26
Logix Controller CPU Utilization Output Structure . . . . . . . . . 27
Logix Controller CPU Utilization Local Configuration Tags . 28
Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Programming Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Display Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Status/Quality Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Using Display Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Operator Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Communication Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Faults Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Performance Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Memory Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Maintenance Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Logix CPU Faceplate Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Chapter 3
Logix Redundant Controller Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Monitor (L_Redun) Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Required Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Controller File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Visualization Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Controller Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Logix Redundant Controller Monitor InOut Structure . . . . . . . 53
Logix Redundant Controller Monitor Input Structure. . . . . . . . 53
Logix Redundant Controller Monitor Output Structure. . . . . . 55
Logix Redundant Controller Monitor Local Configuration Tags 58
Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Command Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Programming Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Display Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Status/Quality Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Using Display Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Operator Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Engineering Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Diagnostics Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Alarms Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
L_Redun Faceplate Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Chapter 4
Logix Task Monitor (L_TaskMon) Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Required Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Controller File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Visualization Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Controller Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Logix Task Monitor Input Structure . . . . . . . . . . . . . . . . . . . . . . . . 77
Logix Task Monitor Output Structure . . . . . . . . . . . . . . . . . . . . . . 78
Logix Task Monitor Local Configuration Tags. . . . . . . . . . . . . . . 80
Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Command Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Programming Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Display Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Status/Quality Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Using Display Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Operator Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Maintenance Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Trends Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Alarms Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
L_TaskMon Faceplate Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Chapter 5
Logix Module Status Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
(L_ModuleSts) Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Required Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Controller Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Logix Module Status InOut Structure . . . . . . . . . . . . . . . . . . . . . . . 96
Logix Module Status Input Structure. . . . . . . . . . . . . . . . . . . . . . . . 97
Logix Module Status Output Structure . . . . . . . . . . . . . . . . . . . . . . 97
Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Command Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Notes:
Define and
Install Prep Develop Operate
Procure
• Selection Guide • Virtualization User Manual • Infrastructure User Manual • Application User Manual • Verify and Troubleshoot User Manual
PROCES-SG001 9528-UM001 PROCES-UM001 PROCES-UM003 PROCES-UM004
• Reference Manual • Reference Manual • Reference Manual
PROCES-RM001 PROCES-RM001 PROCES-RM001
• Library of Process Objects
PROCES-RM013
PROCES-RM014
For the latest compatible software information and to download the Rockwell
Automation Library of Logix Diagnostic Objects, see the Product
Compatibility and Download Center at
http://www.rockwellautomation.com/rockwellautomation/support/
pcdc.page.
Additional Resources These documents contain additional information concerning related products
from Rockwell Automation.
Resource Description
PlantPAx Process Automation System Selection Guide, Provides information to assist with equipment
publication PROCES-SG001 procurement for your PlantPAx system.
PlantPAx Process Automation System Reference Manual, Provides characterized recommendations for
publication PROCES-RM001 implementing your PlantPAx system.
Rockwell Automation Library of Process Objects, Provides general considerations for the PlantPAx
publications PROCES-RM013 and PROCES-RM014 system library of process objects.
FactoryTalk® View Machine Edition User Manual, Provides details on how to use this software package
publication VIEWME-UM004 for creating an automation application.
FactoryTalk View SE Edition User Manual, publication Provides details on how to use this software package
VIEWSE-UM006 for developing and running human machine interface
(HMI) applications that can involve multiple users and
servers, which are distributed over a network.
Logix 5000™ Controllers Add-On Instructions Provides information for the design, configuration,
Programming Manual, publication 1756-PM010 and programming of Add-On Instructions.
ControlLogix® Enhanced Redundancy System User Manual, Provides information for planning and implementing
publication 1756-UM535 a ControlLogix enhanced redundancy system.
Guidelines Use this instruction if you want to monitor a Logix controller for changes, to
be sure that the correct application is being run for regulatory, quality, or
security reasons.
IMPORTANT Once the rung is imported, and before downloading and running the
application, set the path in each of the referenced Message structures to
point to the Logix controller to be monitored.
The interval at which this instruction checks for changes and updates its status
is configurable, from 1…60 seconds.
The import file for this Add-On Instruction can be downloaded from the
Product Compatibility and Download Center at
http://www.rockwellautomation.com/rockwellautomation/support/
pcdc.page.
There are no visualization files because the L_ChangeDet object does not use
display elements or faceplates.
Controller Code This section describes the parameters for this Add-On Instruction.
Output parameters are used to link the Add-On Instruction to external tags
that contain the necessary data for the instruction to operate. These external
tags are brought in with the rung import.
Operations Modes
Alarms
Simulation
Execution
Condition Description
EnableIn False (false rung) No EnableIn False logic is provided. The L_ChangeDet
instruction must always be scanned true. In relay ladder
logic, the L_ChangeDet instruction must be by itself on
an unconditional rung. If the Rung Import provided with
the Rockwell Automation Library is used to install this
instruction, the proper rung is created for you.
Powerup (prescan, first scan) On Prescan, any commands that are received before First
Scan are discarded. The update timer and internal
polling status are reset.
Postscan (SFC transition) No SFC Postscan logic is provided.
Programming Example The L_ChangeDet instruction is provided fully configured as a rung import;
so little programming is required for the instruction to be used. This
programming example shows how the rung import is used to instantiate the
L_ChangeDet instruction.
1. In your ladder routine, right-click where to insert the rungs and choose
Import Rungs.
7. Complete the following steps for each of the three MSG control tags.
a. Click the ellipsis button next to the MSG control tag.
c. Click OK.
8. Place the controller in RUN mode.
Status bits on the L_ChangeDet instruction indicate changes made to
the monitored controller. Set Cmd_AckAll to 1 to clear the latched-in
detections.
The global object and faceplate in the following image are examples of the
HMI interface that is provided with this library object.
Global Object
Do not use this instruction at a high update rate on a continuing basis. The
L_CPU instruction increases the communication load on the controller when
it is polling for performance data. At high update rates, the resource load that
the L_CPU instruction polling generates can affect control performance,
especially if you already have a fully loaded controller.
Functional Description The L_CPU instruction collects and summarizes various data from the Logix
controller that is being monitored. This information includes the following:
• Processor Identity information:
– Catalog number and description
– Major and minor firmware revision numbers
• Communication Responsiveness information:
– CPU% available for responding to communication requests
– CPU% used for responding to communication requests
– Optimized Packets that are used for responding to communication
requests
• Memory usage (total and for each of several classes of memory):
– Total memory size
– Memory used
– Memory available
– Largest contiguous block of available memory.
IMPORTANT The L_CPU instruction does not support SoftLogix™ 5800 or RSLogix™
Emulate 5000 controllers.
The items that are listed previously are displayed on several faceplate tabs, with
summary information on the main (home) tab.
IMPORTANT We recommend that you access the L_CPU faceplate when you contact
Rockwell Automation Technical Support. The information on the Operator
(home) tab is often requested when you call. You also need your
RSLogix 5000® software serial number or other license or support contract
information. The Maintenance tab has a space for you to record this
information for reference.
Required Files Add-On Instructions are reusable code objects that contain encapsulated logic
that can streamline implementing your system. With these Add-On
Instructions, you can create your own instruction set for programming logic as
a supplement to the instruction set provided natively in the ControlLogix®
firmware. An Add-On Instruction is defined once in each controller project,
and can be instantiated multiple times in your application code as needed.
Controller Files
For Logix 5x60 and 5x70 controllers, the following rung imports must be
imported into the controller for each instance of L_CPU in your project:
• L_CPU_18_4.0.00_RUNG.L5X
• L_CPU_19_4.0.00_RUNG.L5X
• L_CPU_20_4.0.00_RUNG.L5X
• L_CPU_21_4.0.00_RUNG.L5X
• L_CPU_23_4.0.00_RUNG.1.5X
• L_CPU_24_Up_4.0.00_RUNG.1.5X
You select the appropriate file, which is based on the revision of the controller
being used (18, 19, 20, 21, 23, or 24 or later). The service release number
(boldfaced) can change as service revisions are created.
For Logix 5x80 controllers, the following rung import must be imported into
the controller for each instance of L_CPU in your project:
L_CPU_5x80_4.0.00_RUNG.1.5X
The import file can be downloaded from the Product Compatibility and
Download Center at
http://www.rockwellautomation.com/rockwellautomation/support/
pcdc.page.
Visualization Files
IMPORTANT The visualization file dependencies require Process Library content imports
to occur in a specific order as reflected in the following tables:
• Images
• Global Objects
• Standard Displays
• HMI Tags
• Macros
Images are external graphic files that can be used in displays. They must be
imported for FactoryTalk® View to use them.
When you import PNG files, FactoryTalk View renames them with a .bmp file
extension, but retains a .png format.
Table 5 - Visualization Files: Images (.png)
FactoryTalk View SE Software FactoryTalk View ME Software Description
All .png files in the images folder All .png files in the images folder These files are the common icons that are used in the
global objects and standard displays for all Process
Objects.
The Global Object files (.ggfx file type) in the following table are Process
Library display elements that are created once and referenced multiple times on
multiple displays in an application. When changes are made to a Global
Object, all instances in the application are automatically updated.
Table 6 - Visualization Files: Global Objects (.ggfx)
FactoryTalk View SE Software FactoryTalk View ME Software Description
(RA-BAS) BuiltIn Faceplate Objects (RA-BAS-ME) BuiltIn Faceplate Objects Global objects for built-in instruction faceplates.
(RA-BAS) BuiltIn Graphics Librarys (RA-BAS-ME) BuiltIn Graphics Librarys Global object device symbols that are used to build built-
in instruction graphics.
(RA-BAS) BuiltIn Help Objects (RA-BAS-ME) BuiltIn Help Objects Global objects for built-in instruction Help displays.
(RA-BAS) Common Faceplate Objects (RA-BAS-ME) Common Faceplate Objects Global objects that are used on process object faceplates.
(RA-BAS) Logix Faceplate Objects (RA-BAS-ME) Logix Faceplate Objects Global objects that are used on Logix faceplates.
(RA-BAS) Logix Graphics Library (RA-BAS-ME) Logix Graphics Library Global object device symbols that are used to build
displays for all Logix Objects.
The Standard Display files (.gfx file type) in the following table are the Process
Library displays that you see at runtime.
Controller Code This section describes the parameter references for this Add-On Instruction.
Operations Modes
Alarms
The L_CPU Add-On Instruction does not provide any alarms. If an alarm is
required, connect the output status to be alarmed to a P_Alarm
instruction instance.
Simulation
Execution
Condition Description
EnableIn False (false rung) The L_CPU instruction has no EnableInFalse logic and
does nothing on a false rung. Data that are associated
with the instruction are left in their last state.
Powerup (pre-scan, first scan) Logic is sure that the window time is sent to the
controller when it transitions to Run mode. Previously
active polling (before power down or transition to
Program mode) is canceled. High-water data that is
stored in the instruction (not built in to the controller
status registers) are cleared.
Postscan (SFC transition) No SFC Postscan logic is provided.
Programming Example The L_CPU instruction is provided fully configured as a rung import;
therefore, little programming is required for the instruction to be used. This
programming example shows how the rung import is used to instantiate the
L_CPU instruction.
1. In your ladder routine, right-click where to insert the rungs and choose
Import Rungs.
Set this value before putting the controller into Run mode. If the value is
changed, it requires a transition from Program to Run on the controller
for the new value to take effect.
6. If there is a continuous task in your application, put its name in the GSV
as the ‘Instance Name’ as shown in the following image.
Display Elements A display element (global object) is created once and can be referenced
multiple times on multiple displays in an application. When changes are made
to the original (base) object, the instantiated copies (reference objects) are
automatically updated. Use of global objects, with tag structures in the
ControlLogix system, aid consistency and save engineering time.
Table 16 - L_CPU Display Elements Description
Display Element Display Element Description
Name
GO_L_CPU_Type0 This global object is used for
1756-L6x ControlLogix
controllers.
Status/Quality Indicators
One of these symbols appears on the graphic symbol when the described
condition is true.
Graphic Symbol Description
Invalid configuration
Forces Active
The global objects for L_CPU can be found in the global object file (RA-BAS)
L_CPU Graphics Library.ggfx. Do the following to use a global object.
1. Copy it from the global object file and paste it in the display file.
2. In the display, right-click the global object and choose Global Object
Parameter Values.
3. Type the tag or value in the Value column as specified in the Description
column.
IMPORTANT You can click the ellipsis (. . .) to browse and select a tag.
Values for items marked ‘(optional)’ can be left blank.
4. Click OK.
Faceplate The L_CPU faceplate consists of tabs and each tab consists of one or more
pages.
The Operator tab is displayed when the faceplate is initially opened. To access a
specific tab, click the appropriate icon on the left of the faceplate.
Operator Tab
The Faceplate initially opens to the Operator (‘Home’) tab. From here, an
operator can monitor the general controller status. The L_CPU_5x80
faceplate does not contain the memory tab.
2
1 3
4
5
6
7
8
10
Communication Tab
Faults Tab
The Faults tab contains the list of minor faults and the fault count. There is an
indicator to display the status of each fault. A blue indicator box shows that the
fault is active.
Performance Tab
The Performance tab shows the approximate CPU percentage that is used by
each of the major activities for the controller. If there is a continuous task
running in the controller, the top segment of the bar graph shows the CPU
used by the continuous task. If there is no continuous task, the top segment
shows the percentage CPU free (unused). The CPU percentages do not
necessarily add up to 100% because of the variability between execution cycles
of the listed tasks and rounding errors.
Memory Tab
Controller Overall Memory, I/O Memory, and Data and Logic Memory are
visible on the tab. This tab is not present in the L_CPU_5x80 instruction. The
memory usage in the Logix 5380, 5480 or 5580 controller is calculated and
displayed in Studio 5000 Logix Designer® software.
The Memory tab displays the size of overall controller memory and the amount
free. For each memory section displayed, the data includes the following:
• Total memory that is allocated to that section
• Amount of memory in that section that is used and unused
• Maximum (‘high-water’) amount of memory used
• Largest contiguous block of unused memory
Maintenance Tab
The L_CPU and L_CPU5x80 Maintenance tabs have the same format.
2
3
1
2
Press the help button on the faceplates to access help specific to that faceplate.
The help file is in .pdf format and opens in a separate window.
Notes:
Global Object
Faceplate
Add-On Instruction
Functional Description The L_Redun instruction is provided as a rung import for installation. The
import of this rung into your ladder diagram routine:
• imports the Add-On Instruction definition
• creates an instruction instance
• creates and completes all required tags and data structures for the
instruction
Once the rung is imported, and before you download and run the application,
set the path in each Message tag that references the input/output parameters of
the instruction to point to slot that contains the 1756-RM2 module in the
local chassis ('1, <slot>').
Required Files Add-On Instructions are reusable code objects that contain encapsulated logic
that can streamline implementing your system. With these Add-On
Instructions, you can create your own instruction set for programming logic as
a supplement to the instruction set provided natively in the ControlLogix
firmware. An Add-On Instruction is defined once in each controller project,
and can be instantiated multiple times in your application code as needed.
Controller File
The L_Redun_4.00.00_RUNG.L5X rung import file must be imported into
the controller project to be able to be used in the controller configuration. The
service release number (boldfaced) can change as service revisions are created.
The import file is available from the Product Compatibility and Download
Center at
http://www.rockwellautomation.com/rockwellautomation/support/
pcdc.page.
Visualization Files
IMPORTANT The visualization file dependencies require Process Library content imports
to occur in a specific order as reflected in the following tables:
• Images
• Global Objects
• Standard Displays
• HMI Tags
• Macros
Images are external graphic files that can be used in displays. They must be
imported for FactoryTalk® View to use them.
When you import PNG files, FactoryTalk View renames them with a .bmp file
extension, but retains a .png format.
Table 18 - Visualization Files: Images (.png)
FactoryTalk View SE Software FactoryTalk View ME Software Description
All .png files in the images folder All .png files in the images folder These files are the common icons that are used in the
global objects and standard displays for all Process
Objects.
The Global Object files (.ggfx file type) in the following table are Process
Library display elements that are created once and referenced multiple times on
multiple displays in an application. When changes are made to a Global
Object, all instances in the application are automatically updated.
Table 19 - Visualization Files: Global Objects (.ggfx)
FactoryTalk View SE Software FactoryTalk View ME Software Description
(RA-BAS) BuiltIn Faceplate Objects (RA-BAS-ME) BuiltIn Faceplate Objects Global objects for built-in instruction faceplates.
(RA-BAS) BuiltIn Graphics Librarys (RA-BAS-ME) BuiltIn Graphics Librarys Global object device symbols that are used to build built-
in instruction graphics.
(RA-BAS) BuiltIn Help Objects (RA-BAS-ME) BuiltIn Help Objects Global objects for built-in instruction Help displays.
(RA-BAS) Common Faceplate Objects (RA-BAS-ME) Common Faceplate Objects Global objects that are used on process object faceplates.
(RA-BAS) Logix Faceplate Objects (RA-BAS-ME) Logix Faceplate Objects Global objects that are used on Logix faceplates.
(RA-BAS) Logix Graphics Library (RA-BAS-ME) Logix Graphics Library Global object device symbols that are used to build
displays for all Logix Objects.
The Standard Display files (.gfx file type) in the following table are the Process
Library displays that you see at runtime.
Table 20 - Visualization Files: Standard Displays (.gfx)
FactoryTalk View SE Software FactoryTalk View ME Software Description
(RA-BAS) Built-In Family-Help (RA-BAS-ME) Built-In Family-Help Built-in instruction help information that is accessed from
the built-in faceplates.
(RA-BAS) Common-AnalogEdit — Faceplate that is used for analog input data entry. The
FactoryTalk View ME faceplates use the native
analog-input data entry so no file is required.
(RA-BAS) L_Logix Family-Help (RA-BAS-ME) L_Logix Family-Help The Help display that is used for the object.
(RA-BAS) L_Redun-Faceplate (RA-BAS-ME) L_Redun-Faceplate The faceplate that is used for the object.
(RA-BAS) P_Alarm-Faceplate (RA-BAS-ME) P_Alarm-Faceplate The faceplate that is used for the object
(RA-BAS) P_Alarm-Help (RA-BAS-ME) P_Alarm-Help Alarm Help information that is accessed from the
P_AIarm faceplate.
(RA-BAS) Built-In Totalizer-Faceplate (RA-BAS-ME) Built-In Totalizer Faceplate Optional
The faceplate display that is used for the Totalizer object.
(RA-BAS) Built-In TotalizerTgt-Faceplate (RA-BAS-ME) Built-In TotalizerTgt Faceplate Optional
The faceplate display that is used for the Totalizer Target
object.
Controller Code This section describes the parameter references for this Add-On Instruction.
Cfg_Slot06 0
Cfg_Slot07 0
Cfg_Slot08 0
Cfg_Slot09 0
Cfg_Slot10 0
Cfg_Slot11 0
Cfg_Slot12 0
Cfg_Slot13 0
Cfg_Slot14 0
Cfg_Slot15 0
Cfg_Slot16 0
Cfg_HasSecNotRdyAlm BOOL SecNotRdy.Cfg_Exists 0 1 = Secondary Not Ready alarm exists and is checked.
Cfg_SecNotRdyResetReqd SecNotRdy.Cfg_ResetReqd 0 1 = Secondary Not Ready alarm is latched in, requires Reset command to clear.
Cfg_SecNotRdyAckReqd SecNotRdy.Cfg_AckReqd 1 1 = Secondary Not Ready, alarm must be acknowledged.
Cfg_SecNotRdySeverity DINT SecNotRdy.Cfg_Severity 750 This parameter determines the severity of the secondary not ready alarm. The
severity drives the color and symbol that is used to indicate alarm status on the
faceplate and the global object.
The following are valid values:
1…250 = Low
251…500 = Medium
501…750 = High
751…1000 = Urgent
IMPORTANT: For FactoryTalk View software version 7, this severity parameter
drives only the indication on the global object and faceplate. The FactoryTalk
Alarms and Events definition of severity drives the color and symbol that is used
on the alarm banner, alarm summary, and the value that is returned by
FactoryTalk Alarms and Events display commands.
PCmd_Reset BOOL 0 Program command to reset all latched alarms.
PCmd_SecNotRdyAck BOOL SecNotRdy.PCmd_Ack 0 • Set PCmd_<Alarm>Ack to 1 to Acknowledge alarm
• This parameter is reset automatically
PCmd_SecNotRdySuppress SecNotRdy.PCmd_Suppress When Cfg_PCmdClear is 1:
PCmd_SecNotRdyUnsuppress SecNotRdy.PCmd_Unsuppress • Set PCmd_<Alarm>Suppress to 1 to suppress alarm
• Set PCmd_<Alarm>Unsuppress to 1 to unsuppress alarm
• These parameters reset automatically
When Cfg_PCmdClear is 0:
• Set PCmd_<Alarm>Suppress to 1 to suppress alarm
• Set PCmd_<Alarm>Suppress to 0 to unsuppress alarm
• PCmd_<Alarm>Unsuppress is not used
• These Parameters do not reset automatically
PCmd_SecNotRdyUnshelve SecNotRdy.PCmd_Unshelve • Set PCmd_<Alarm>Unshelve to 1 to Unshelve alarm
• This parameter is reset automatically
Operations This section describes the primary operations for Add-On Instructions.
Command Sources
Alarm
The L_Redun Instruction uses the following alarm, which is implemented by
using an embedded P_Alarm Add-On Instruction.
Simulation
Execution
Programming Example The L_Redun instruction is provided fully configured as a rung import, so
little programming is required for the instruction to be used. This
programming example shows how the rung import is used to instantiate the
L_Redun instruction.
1. In your ladder routine, right-click where to insert the rungs and choose
Import Rungs.
b. To set the second number in the path to the slot number of the 1756-
RM2 module, click the Communication tab.
c. Click OK.
Display Elements A display element (global object) is created once and can be referenced
multiple times on multiple displays in an application. When changes are made
to the original (base) object, the instantiated copies (reference objects) are
automatically updated. Use of global objects, with tag structures in the
ControlLogix system, aid consistency and save engineering time.
Table 27 - L_Redun Display Elements Description
Display Element Name Display Element Description
GO_L_Redun This global object is used
for redundancy modules.
The L_Redun instruction has display elements (global objects) for use on
process graphic displays. These elements provide you with the following:
• Information on the current state of the object
• Touch field to open the faceplate of the object
• Tooltip to display the configured tag and description of the object
Status/Quality Indicators
One of these symbols appears to the left of the graphic symbol when the
described condition is true.
Graphic Symbol Description
Invalid configuration
TIP When the Invalid Configuration indicator appears, you can find
what configuration setting is invalid by following the indicators.
Click the graphic symbol to open the faceplate. The Invalid
Configuration indicator appears next to the appropriate tab at the
top of the faceplate to help you in find the configuration error. Once
you navigate to the tab, the misconfigured item is flagged with this
indicator or appears in a magenta box.
The global objects for L_Redun can be found in the global object file (RA-
BAS) L_Redun Graphics Library.ggfx. Do the following to use a global object.
1. Copy it from the global object file and paste it in the display file.
2. In the display, right-click the global object and choose Global Object
Parameter Values.
3. Type the tag or value in the Value column as specified in the Description
column.
IMPORTANT You can click the ellipsis (. . .) to browse and select a tag.
Values for items marked ‘(optional)’ can be left blank.
4. Click OK.
Faceplate The Operator tab is displayed when the faceplate is initially opened. To access a
specific tab, click the appropriate icon on the left of the faceplate.
Operator Tab
2 5
3 6
7
4
8
10
Engineering Tab
On the Engineering tab, you can identify and configure each chassis and
configure display, switchover, and synchronization options.
4
5
6
7
8
9
Diagnostics Tab
The Diagnostics tab contains the list of minor faults and the status of the
controller chassis. There is an indicator to display the status of each fault. A
blue indicator box shows that the fault is active.
Alarms Tab
The Alarms tab displays each configured alarm for the L_Redun instruction.
The icon on the tab for the alarms page changes color based on the current
active alarms. A blinking alarm border indicates that one or more alarms must
be acknowledged or the device must be reset.
Click an alarm name to open the P_Alarm faceplate for that alarm. From the
P_Alarm faceplate, you can configure and perform additional operations on
the alarm.
One of these symbols appears on the left of the label to indicate the described
alarm condition. The alarm border blinks if acknowledgment of an alarm
condition is required. Once the alarm is acknowledged, the alarm border
remains the color that corresponds to the severity of the alarm and the alarm
symbol is still present.
Symbol Border Color Description
Red Urgent-severity alarm
The Reset and Acknowledge All Alarms button is enabled, the panel behind
the alarm blinks, and the Alarm Acknowledge button is enabled if the alarm
requires acknowledgment. Click the button with the check mark to
acknowledge the alarm.
Press the help button on the faceplates to access help specific to that faceplate.
The help file is in .pdf format and opens in a separate window.
Faceplate
Add-On Instruction
Do not use this instruction if you are using suitable software or another
method to monitor controller task execution.
Functional Description The L_TaskMon instruction includes an Add-On Instruction for use with:
• RSLogix 5000® software, version 18 or later
• Logix controllers, firmware revision 18 or later
• graphic symbol and faceplate display for use with either FactoryTalk®
View Site Edition or Machine Edition software, version 7.0 or later.
Required Files Add-On Instructions are reusable code objects that contain encapsulated logic
that can streamline implementing your system. With these Add-On
Instructions, you can create your own instruction set for programming logic as
a supplement to the instruction set provided natively in the ControlLogix®
firmware. An Add-On Instruction is defined once in each controller project,
and can be instantiated multiple times in your application code as needed.
Controller File
The L_TaskMon_4.00.00_AOI.L5X Add-On Instruction must be imported
into the controller project for use in the controller configuration. The service
release number (boldfaced) can change as service revisions are created.
The import file is available from the Product Compatibility and Download
Center at
http://www.rockwellautomation.com/rockwellautomation/support/
pcdc.page.
Visualization Files
IMPORTANT The visualization file dependencies require Process Library content imports
to occur in a specific order as reflected in the following tables:
• Images
• Global Objects
• Standard Displays
• HMI Tags
• Macros
Images are external graphic files that can be used in displays. They must be
imported for FactoryTalk View to use them.
When you import PNG files, FactoryTalk View renames them with a .bmp file
extension, but retains a .png format.
Table 28 - Visualization Files: Images (.png)
FactoryTalk View SE Software FactoryTalk View ME Software Description
All .png files in the images folder All .png files in the images folder These files are the common icons that are used in the
global objects and standard displays for all Process
Objects.
The Global Object files (.ggfx file type) in the following table are Process
Library display elements that are created once and referenced multiple times on
multiple displays in an application. When changes are made to a Global
Object, all instances in the application are automatically updated.
Table 29 - Visualization Files: Global Objects (.ggfx)
FactoryTalk View SE Software FactoryTalk View ME Software Description
(RA-BAS) BuiltIn Faceplate Objects (RA-BAS-ME) BuiltIn Faceplate Objects Global objects for built-in instruction faceplates.
(RA-BAS) BuiltIn Graphics Librarys (RA-BAS-ME) BuiltIn Graphics Librarys Global object device symbols that are used to build built-
in instruction graphics.
(RA-BAS) BuiltIn Help Objects (RA-BAS-ME) BuiltIn Help Objects Global objects for built-in instruction Help displays.
(RA-BAS) Common Faceplate Objects (RA-BAS-ME) Common Faceplate Objects Global objects that are used on process object faceplates.
(RA-BAS) Logix Faceplate Objects (RA-BAS-ME) Logix Faceplate Objects Global objects that are used on Logix faceplates.
The Standard Display files (.gfx file type) in the following table are the Process
Library displays that you see at runtime.
Table 30 - Visualization Files: Standard Displays (.gfx)
FactoryTalk View SE Software FactoryTalk View ME Software Description
(RA-BAS) Built-In Family-Help (RA-BAS-ME) Built-In Family-Help Built-in instruction help information that is accessed
from the built-in faceplates.
(RA-BAS) Common-AnalogEdit — Faceplate that is used for analog input data entry. The
FactoryTalk View ME faceplates use the native
analog-input data entry so no file is required.
(RA-BAS) L_Logix Family-Help (RA-BAS-ME) L_Logix Family-Help The Help display that is used for the object.
(RA-BAS) L_TaskMon-Faceplate (RA-BAS-ME) L_TaskMon-Faceplate The faceplate that is used for the object.
(RA-BAS) P_Alarm-Faceplate (RA-BAS-ME) P_Alarm-Faceplate The faceplate that is used for the object
(RA-BAS) P_Alarm-Help (RA-BAS-ME) P_Alarm-Help Alarm Help information that is accessed from the
P_AIarm faceplate.
(RA-BAS) Built-In Totalizer-Faceplate (RA-BAS-ME) Built-In Totalizer Faceplate Optional
The faceplate display that is used for the Totalizer object.
(RA-BAS) Built-In TotalizerTgt-Faceplate (RA-BAS-ME) Built-In TotalizerTgt Faceplate Optional
The faceplate display that is used for the Totalizer Target
object.
(RA-BAS) L_TaskMon-Summary (RA-BAS-ME) L_TaskMon-Summary Optional
Contains eight L_TaskMon objects to show all tasks in
a controller.
Controller Code This section describes the parameter references for this Add-On Instruction.
Operations The L_TaskMon instruction monitors one task in a Logix controller, and
provides the following:
• Task configuration information:
– Task Name
– Task Priority
– Task Rate (for a Periodic Task)
– Watchdog Timer setting
• Task statistics:
– Last scan time
– Maximum scan time
– Task Overlap count
– Maintenance commands to reset the maximum time and overlap
count
• Task status:
– Task active or Inhibited status
• Task ‘plan’ execution-time handling:
– Configuration of a ‘plan’ execution time
– Optional alarm if the actual execution time exceeds the ‘plan’
threshold
– Reset command to clear and acknowledge the Over Plan alarm
Command Sources
Alarm
Simulation
Execution
Programming Example Include one instance of the L_TaskMon instruction in each controller task.
A good place to put each instance is at the top of the Main Routine of the
Main Program of the task.
If you code the L_TaskMon instances in ladder diagram routines, their backing
tags can be in an array, as shown in the previous image.
You can configure the Cfg_PlanExecT to set a planned task execution time. If
the execution time of the task, which includes all higher-priority tasks, exceeds
the Plan value, an Over Plan alarm can be generated.
TIP If you plan to inhibit tasks and plan to show when a task is inhibited, add a
rung in a separate task to check for this condition. An inhibited task does
not scan its logic and so cannot detect when it has been inhibited.
Display Elements A display element (global object) is created once and can be referenced
multiple times on multiple displays in an application. When changes are made
to the original (base) object, the instantiated copies (reference objects) are
automatically updated. Use of global objects, with tag structures in the
ControlLogix system, aid consistency and save engineering time.
Table 36 - L_TaskMon Display Elements Description
Display Element Name Display Element Description
GO_TaskMon This global object provides task statistics for
one task in a Logix controller.
The L_TaskMon instruction has display elements (global objects) for use on
process graphic displays. These elements provide you with the following:
• Information on the current state of the object
• Touch field to open the faceplate of the object
• Tool tip to display the configured tag and description of the object
Status/Quality Indicators
One of these symbols appears to the left of the graphic symbol when the
described condition is true.
Graphic Symbol Description
Invalid configuration
TIP When the Invalid Configuration indicator appears, you can find
what configuration setting is invalid by following the indicators.
Click the graphic symbol to open the faceplate. The Invalid
Configuration indicator appears next to the appropriate tab at the
top of the faceplate to help you find the configuration error. Once
you navigate to the tab, the misconfigured item is flagged with this
indicator or appears in a magenta box.
The global objects for L_TaskMon can be found in the global object file (RA-
BAS) L_TaskMon Graphics Library.ggfx. Do the following to use a global
object.
1. Copy it from the global object file and paste it in the display file.
2. In the display, right-click the global object and choose Global Object
Parameter Values.
3. Type the tag or value in the Value column as specified in the Description
column.
TIP You can click the ellipsis (. . .) to browse and select a tag.
Values for items marked ‘(optional)’ can be left blank.
4. Click OK.
Faceplate The L_TaskMon faceplate consists of four tabs and each tab consists of one or
more pages.
The Operator tab is displayed when the faceplate is initially opened. To access a
specific tab, click the appropriate icon on the left of the faceplate.
The faceplate provides the means for maintenance personnel, engineers, and
others to interact with the L_TaskMon instruction instance.
Operator Tab
The Faceplate initially opens to the Operator (‘Home’) tab. From here, an
operator can monitor the task status.
Maintenance Tab
Trends Tab
The Trends tab shows trend charts of key device data over time. These faceplate
trends provide a quick view of current device performance to supplement, but
not replace, dedicated historical or live trend displays.
Alarms Tab
The Alarms tab displays each configured alarm for the L_TaskMon
instruction. The icon on the tab for the alarms page changes color based on the
current active alarms. A blinking alarm border indicates that one or more
alarms must be acknowledged or the device must be reset.
Click an alarm name to open the P_Alarm faceplate for that alarm. From the
P_Alarm faceplate, you can configure and perform additional operations on
the alarm.
One of these symbols appears on the left of the label to indicate the described
alarm condition. The alarm border blinks if acknowledgment of an alarm
condition is required. Once the alarm is acknowledged, the alarm border
remains the color that corresponds to the severity of the alarm and the alarm
symbol is still present.
Symbol Border Color Description
Red Urgent-severity alarm
The Reset and Acknowledge All Alarms button is enabled, the panel behind
the alarm blinks, and the Alarm Acknowledge button is enabled if the alarm
requires acknowledgment. Click the button with the check mark to
acknowledge the alarm.
Press the help button on the faceplates to access help specific to that faceplate.
The help file is in .pdf format and opens in a separate window.
Notes:
IMPORTANT The Logix Module Status Add-On Instruction is for use with Studio 5000
Logix Designer® (software and Logix controller firmware) version 24 or later.
Guidelines Use this instruction if you want to monitor the I/O connection status of a
given module.
Functional Description The L_ModuleSts Add-On Instruction is used to check the I/O connection
status for the given module. The instruction provides an I/O Fault status
output, which is 1 when the connection is NOT running normally, and 0 when
the connection to the I/O module is OK. This status is used by other
Add-On Instructions that use inputs or outputs of the given I/O module or
device.
The following images represent the function block and ladder diagram usage
once the Add-On Instruction is imported.
The L_ModuleSts instruction can be used to provide the connection status for
any connected device (one with a Requested Packet Interval) in the I/O
Configuration tree in RSLogix 5000/Studio 5000 Logix Designer application.
These devices include I/O modules and drives, overload relays, flowmeters,
analyzers, weigh scales and other devices on EtherNet/IP.
TIP Entry of a name for an I/O module or other device in the I/O Configuration is
optional. However, in order for the L_ModuleSts instruction to refer to the
module or device, you MUST give the module or device a name.
The red oval highlights the ‘optional’ name that is required for the Add-On
Instruction to be able to reference the module
The module is defined in the I/O tree (inside the red rectangle in the following
image).
Required Files The L_ModuleSts_4.00.00_AOI.L5X import file must be imported into the
controller project. The service release number (boldfaced) can change as
service revisions are created.
The import file for this Add-On Instruction is included in the Rockwell
Automation Library of Process Objects, which can be downloaded from the
Product Compatibility and Download Center at
http://www.rockwellautomation.com/rockwellautomation/support/
pcdc.page.
There are no visualization files because the L_ModuleSts object does not use
display elements or faceplates. The I/O Fault status is displayed on the graphics
for the object (valve, motor, drive, or other device) that uses the
L_ModuleSts output.
Controller Code This section describes the parameters for this Add-On Instruction.
Output parameters include Status Data elements (Sts_). Status Data elements
are bit outputs of the instruction for use by the HMI or other application logic.
Table 39 - L_ModuleSts Output Parameters
Name Data Type Description
EnableOut BOOL Enable output: This instruction does not manipulate the EnableOut signal. Its output state always reflects EnableIn Input
state.
Sts_I/OFault BOOL 1 = Module I/O connection fault (module is not in ‘running’ state).
Alarms
Simulation
Execution
Condition Description
EnableIn False (false rung) No EnableIn False logic is provided. The L_ModuleSts
instruction must always be scanned true. In relay ladder
logic, the L_ModuleSts instruction must be by itself on
an unconditional rung.
Powerup (prescan, first scan) No Prescan logic is provided.
Postscan (SFC transition) No SFC Postscan logic is provided.
Technical Support Center Knowledgebase Articles, How-to Videos, FAQs, Chat, User https://rockwellautomation.custhelp.com/
Forums, and Product Notification Updates.
Local Technical Support Phone Numbers Locate the phone number for your country. http://www.rockwellautomation.com/global/support/get-support-now.page
Find the Direct Dial Code for your product. Use the code to
Direct Dial Codes route your call directly to a technical support engineer. http://www.rockwellautomation.com/global/support/direct-dial.page
Documentation Feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document, complete the
How Are We Doing? form at http://literature.rockwellautomation.com/idc/groups/literature/documents/du/ra-du002_-en-e.pdf.
Rockwell Automation maintains current product environmental information on its website at http://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page.
Allen-Bradley, ControlLogix, FactoryTalk, Logix 5000, PlantPAx, Rockwell Automation, Rockwell Software, RSLogix, RSLinx, SoftLogix, Studio 5000 Logix Designer, and TechConnect are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Rockwell Otomasyon Ticaret A.Ş., Kar Plaza İş Merkezi E Blok Kat:6 34752 İçerenköy, İstanbul, Tel: +90 (216) 5698400