Programming Manual
Logix5000 Controllers Information and Status
Catalog Numbers 1756 ControlLogix, 1756 GuardLogix, 1768 Compact GuardLogix, 1768
CompactLogix, 1769 CompactLogix, 1789 SoftLogix, PowerFlex with DriveLogix
Important user information
Read this document and the documents listed in the additional resources section about installation, configuration, and operation of
this equipment before you install, configure, operate, or maintain this product. Users are required to familiarize themselves with
installation and wiring instructions in addition to requirements of all applicable codes, laws, and standards.
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.
Labels may also be on or inside the equipment to provide specific precautions.
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).
Allen-Bradley, Rockwell Software, Rockwell Au tomation, and TechConnect are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are prope rty of their respective companies.
Summary of changes
This manual contains new and updated information. There are a number of minor
changes throughout this publication that were made to clarify existing
information. The major changes are listed below.
Change Page
Updated Entries Captured in the Controller Log to add new entries and
correct existing entries.
Updated path to sample ladder logic. See Sample Ladder Logic File on page 39.
Added Program Connection Modified to the Controller Log Events table. See Controller Log Events on page 39.
Added bit numbers 35 and 36 to the ChangesToDetect Format table. See ChangesToDetect Format on page 50.
Updated GSV and SSV classes and attributes from all-capital letters to
initial capitalization for version 22
See Entries Captured in the Controller Logon
page 25.
Throughout the manual.
Rockwell Automation Publication 1756-PM015F-EN-P – October 2014 3
Preface
Connections
Determine controller
Controller logging
Table of contents
memory information
Studio 5000 Environment .................................................................................... 7
Additional Resources ............................................................................................. 8
Chapter 1
Introduction ............................................................................................................ 9
Inhibit a Connection ........................................................................................... 10
Manage a Connection Failure ............................................................................ 12
Configure a Major Fault to Occur.............................................................. 13
Monitor the Health of a Module ................................................................ 13
Chapter 2
Introduction .......................................................................................................... 17
Estimate memory information offline .............................................................. 17
View Run-time Memory Information .............................................................. 19
Write Logic to Get Memory Information ....................................................... 20
Get Memory Information from the Controller ....................................... 20
Choose the Memory Information .............................................................. 21
Convert INTs to a DINT ............................................................................ 22
Chapter 3
Introduction .......................................................................................................... 23
Controller Log ...................................................................................................... 23
Controller Log Header ................................................................................. 24
Controller Log Entry .................................................................................... 24
Entries Captured in the Controller Log .................................................... 25
Controller Log Buffer ................................................................................... 26
Controller Log Files and the Removable Media ...................................... 26
Writing the Controller Log to the CompactFlash Card ........................ 27
Controller logging counters ......................................................................... 30
Log File Storage .............................................................................................. 35
Log file format ................................................................................................ 37
Create custom log entries ............................................................................. 38
Sample Ladder Logic File ............................................................................. 39
Controller log events ..................................................................................... 39
Rockwell Automation Publication 1756-PM015F-EN-P – October 2014 5
Table of Contents
Change detection
Access status information
Index
Chapter 4
Introduction .......................................................................................................... 47
Controller Change Detection ............................................................................ 47
ChangesToDetect ......................................................................................... 48
AuditValue...................................................................................................... 49
ChangesToDetect Format ........................................................................... 50
Change Detection in Logix Designer Application ......................................... 51
Chapter 5
Introduction .......................................................................................................... 53
Status of S:FS When the Project Has an SFC ................................................. 54
Get and Set System Data ..................................................................................... 54
6 Rockwell Automation Publication 1756-PM015F-EN-P – October 2014
Studio 5000 environment
Preface
This manual describes how Logix5000 controllers use connections with other
devices. This manual also describes status keywords and how to get controller
information, such as memory resources. This manual is one of a set of related
manuals that show common procedures for programming and operating
Logix5000 controllers.
For a complete list of common procedures manuals,
Common Procedures Programming Manual, publication 1756-PM001.
The term Logix5000 controller refers to any controller that is based on the
Logix5000 operating system.
The Studio 5000 Automation Engineering & Design Environment™ combines
engineering and design elements into a common environment. The first element is
the Studio 5000 Logix Designer™ application. The Logix Designer application is
the rebranding of RSLogix™ 5000 software and will continue to be the product to
program Logix5000™ controllers for discrete, process, batch, motion, safety, and
drive-based solutions.
Logix5000 Controllers
Rockwell Automation Publication 1756-PM015F-EN-P – October 2014 7
The Studio 5000® environment is the foundation for the future of
Rockwell Automation® engineering design tools and capabilities. The Studio 5000
environment is the one place for design engineers to develop all elements of their
control system.
Preface
Provides declarations of conformity, certificates, and other
Additional resources
These documents contain additional information concerning related Rockwell
Automation products.
Resource Description
Industrial Automation Wiring and Grounding Guidelines,
publication 1770-4.1.
Product Certifications webpage, available at
http://ab.rockwellautomation.com.
Provides general guidelines for installing a Rockwell
Automation industrial system.
certification details.
You can view or download publications at
http://www.rockwellautomation.com/literature. To order paper copies of
technical documentation, contact your local Rockwell Automation distributor or
sales representative.
8 Rockwell Automation Publication 1756-PM015F-EN-P – October 2014
Introduction
Chapter 1
Connections
A Logix5000 controller uses connections for most, but not all, of its
communication with other devices.
Term Definition
Connection
Requested packet
interval (RPI)
Path
A communication link between two devices, such as between a controller and an I/O
module, PanelView terminal, or another controller.
Connections are allocations of resources that provide more reliable communication
between devices than unconnected messages. The number of connections that a single
controller can have is limited.
You indirectly determine the number of connections the controller uses by configuring the
controller to communicate with other devices in the system. These communication types
use the following connections:
• I/O modules
• Produced and consumed tags
• Program parameters
• Certain types of Message (MSG) instructions (not all types use a connection)
The RPI specifies the period at which data updates over a connection. For example, an
input module sends data to a controller at the RPI that you assign to the module.
• Typically, you configure an RPI in milliseconds (ms). The range is 0.2 ms
(200 microseconds)…750 ms.
• If a ControlNet network connects the devices, the RPI reserves a slot in the stream of
data flowing across the ControlNet network. The timing of this slot may not coincide
with the exact value of the RPI, but the control system guarantees that the data
transfers at least as often as the RPI.
The path describes the route that a connection takes to get to the destination.
Typically, you automatically define the path for a connection when you add the devices to
the I/O Configuration folder of the controller.
Rockwell Automation Publication 1756-PM015F-EN-P – October 2014 9
Chapter 1 Connections
Inhibit a connection
In some situations, such as when initially commissioning a system, it is useful to
disable portions of a control system and enable them as you physically connect the
control system. The controller lets you inhibit individual modules or groups of
modules, which prevents the controller from trying to communicate with the
modules.
Inhibiting a module breaks the connection to the module and prevents communication of I/O data.
When you configure an I/O module, it defaults to not inhibited. You can change
an individual module’s properties to inhibit a module.
If you want to Then
Communicate with the module
Prevent communication with the module
Do not inhibit the module. Clear the Inhib it Module
check box.
Inhibit the module. Select the Inhibit Module check box.
When you inhibit a communication bridge module, the controller shuts down the
connections to the bridge module and to all the modules that depend on that
bridge module. Inhibiting a communication bridge module lets you disable an
entire branch of the I/O network.
When you inhibit the module, the Controller Organizer displays a yellow
attention symbol over the module.
If you are And you And Then
Offline ------------------------------> --------> The inhibit status is stored in the project. When you download the project, the module still is
inhibited.
Online Inhibit a module while you are connected
to the module
Inhibit a module but a connection to the
module was not established (perhaps due
to an error condition or fault)
--------> The connection to the module is closed. The module's outputs go to the last configured
Program mode.
--------> The module is inhibited. The module status information changes to indicate that the module is
inhibited and not faulted.
10 Rockwell Automation Publication 1756-PM015F-EN-P – October 2014
Connections Chapter 1
If you are And you And Then
Uninhibit a module (clear the check box) No fault occurs A connection is made to the module and the module is dynamically reconfigured (if the
controller is the owner-controller) with the configuration you created for that module. If the
controller is configured for listen-only, it cannot reconfigure the module.
Fault occurs A connection is not made to the module. The module status information changes to indicate
the fault condition.
Follow these steps to inhibit or uninhibit a module from logic.
1. Use a Get System Value (GSV) instruction to read the Mode attribute for
the module.
2. To inhibit the module, set bit 2. To uninhibit the module, clear bit 2.
3. Use a Set System Value (SSV) instruction to write the Mode attribute back
to the module.
Example:
If Module_1_Inhibit = 1, then inhibit the operation of the I/O module named Module_1.
1. The GSV instruction sets Module_1_Mode = value of the Mode attribute for the module.
2. The OTE instruction sets bit 2 of Module_1_Mode = 1. This means inhibit the connection.
3. The SSV instruction sets the Mode attribute for the module = Module_1_Mode.
Inhibit a Connection
Rockwell Automation Publication 1756-PM015F-EN-P – October 2014 11
Chapter 1 Connections
generate a controller major fault when they lose their connections to the controller, or monitor the status of
Manage a connection
failure
If the controller loses communication with a module, data from that device does
not update. When this occurs, the logic acts on the data in ways that may or may
not be correct. You can program the controller to manage faults safely and
efficiently.
Outputs respond to the last, non-faulted state of the controlling inputs. To avoid potential injury and
damage to machinery, make sure this does not create an unsafe operation. Configure critical I/O modules to
I/O modules.
Example: Loss of Communication
Controller B requires data from controller A. If communication fails between the controllers, controller B
continues to act on the last data that it received from controller A.
If communication with a device in the I/O configuration of the controller does
not occur for 100 ms, the communication times out. If this occurs, you have the
following options.
If you want the controller to Then
Fault (major fault) Configure a major fault to occur on page 13.
Continue operating Monitor the health of a module on page 13.
12 Rockwell Automation Publication 1756-PM015F-EN-P – October 2014
Connections Chapter 1
Configure a major fault to occur
You can configure modules to generate a major fault in the controller if they lose
their connection with the controller. This interrupts the execution of logic and
runs the Controller Fault Handler. If the Controller Fault Handler does not clear
the fault, the controller shuts down.
When you select Major Fault On Controller…Run Mode, the controller:
• Must be connected to the module during the Program transition to Run
mode. During the Program to Run mode transition, there can be a 20second delay.
During this delay, the controller makes one attempt to connect to a module.
If you select Major Fault On Controller…Run Mode and you cannot
connect during the 20-second delay, a fault occurs because at least one
required connection is not established before going to Run mode. This is a
3/23 type fault code. This fault can occur in large systems with networked
I/O.
• Registers a fault if the connection is dropped while in Run mode. A required
I/O module connection failed, creating a 3/16 type fault.
For fault codes, see the
Logix5000 Controllers Major and Minor Faults
Programming Manual, publication 1756-PM014.
Monitor the health of a module
If you do not configure the major fault to occur, you should monitor the module
status. If a module loses its connection to the controller, outputs go to their
configured faulted state. The controller and other I/O modules continue to
operate based on old data from the module.
Rockwell Automation Publication 1756-PM015F-EN-P – October 2014 13
Chapter 1 Connections
If communication with a module times out, the controller produces the following
warnings.
• The I/O status indicator on the front of the controller flashes green.
• A Warning ( ) icon shows over the I/O configuration folder and over the
device that has timed out.
• A module fault code is produced, which you can access through:
• Module Properties window for the module.
• GSV instruction.
To monitor the health of your connections, use a Get System Value (GSV)
instruction to monitor the Module object for either the controller or a specific
module.
If you want to Get this attribute Data Type Description
Determine if communication
has timed out with any
device
Determine if communication
has timed out with a specific
device
LEDStatus INT
For efficiency, use a
DINT as the
destination data type.
FaultCode INT
For efficiency, use a
DINT as the
destination data type.
Current state of the I/O status indicator on the front of the controller.
You do not enter an instance name with this attribute. This attribute applies to the entire
collection of modules.
Value Meaning
0 Status Indicator off. No Module objects are configured for the controller
1 Flashing red. None of the Module objects are Running.
2 Flashing green. At least one Module object is not Running.
3 Solid green. All the Module objects are Running.
A number that identifies a module fault, if one occurs.
In the Instance Name, choose the device whose connection you want to monitor. Make sure
to assign a name to the device in the I/O Configuration folder of the project.
(there are no modules in the I/O Configuration section of the controller
organizer).
If Module_Status is any value other than 4, the controller is not communicating
with the module. See the following example.
14 Rockwell Automation Publication 1756-PM015F-EN-P – October 2014
Connections Chapter 1
Example:
This rung che cks the status of an I/O connection. The controller checks the entry status of the connection; any value other than 4 indicates that the connection is
not functioning correctly. When the controller detects an error, the error code and information is trapped, and the controller tries to re-establish the connection.
Rockwell Automation Publication 1756-PM015F-EN-P – October 2014 15
Introduction
Estimate memory
Chapter 2
Determine controller memory information
Depending on your type of controller, the memory of the controller may be
divided into several areas.
If you have this controller Then it stores this In this memory
1756 ControlLogix
1756 GuardLogix
1768 CompactLogix
1768 Compact GuardLogix
1769-L2x CompactLogix
1769-L3x CompactLogix
FlexLogix
DriveLogix
SoftLogix5800
I/O tags I/O memory
Produced / Consumed tags
Communication via Message (MSG) instructions
Communication with workstations
Communication with polled (OPC/DDE) tags that
use RSLinx software
Tags other than I/O, produced, or consumed tags Data and logic memory2
Logic routines
Communication with polled (OPC/DDE) tags that
use RSLinx software
These controllers do not divide their memory. They store all elements in one
common memory area.
1
1
information offline
Rockwell Automation Publication 1756-PM015F-EN-P – October 2014 17
(1) To communicate with polled tags, the controller uses both I/O data and logic
memory.
(2) 1756-L55M16 controllers have an additional memory section for logic.
To estimate how much controller memory your project requires, use the Memory
tab of the Controller Properties dialog box. For each of the memory areas of your
controller, the dialog box lets you estimate number of bytes of:
• Free (unused) memory.
• Used memory.
• Largest free contiguous block of memory.
Use the following steps to estimate the controller memory.
1. Start the Logix Designer application and open a controller project.
Chapter 2 Determine controller memory information
2. On the Online toolbar (above the Controller Organizer), click the
Controller Properties icon.
3. On the Controller Properties dialog box, click the Memory tab.
4. In the Estimated Data and Logic Memory area, view the memory
information since the last estimate.
5. Click Estimate to re-estimate the amount of controller memory.
6. Click OK.
18 Rockwell Automation Publication 1756-PM015F-EN-P – October 2014
Loading...