Rockwell Automation 1756 ControlLogix, 1756 GuardLogix, 1769 CompactLogix, 1769 Compact GuardLogix, 1789 SoftLogix Programming Manual

...

Programming Manual

Logix 5000 Controllers Information and Status

1756 ControlLogix, 1756 GuardLogix, 1769 CompactLogix, 1769 Compact GuardLogix, 1789 SoftLogix, 5069 CompactLogix, 5069 Compact GuardLogix, Studio 5000 Logix Emulate

Original Instructions

Logix 5000 Controllers Information and Status

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.

temperatures.

for Personal Protective Equipment (PPE).

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

ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss.

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

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

2 Rockwell Automation Publication 1756-PM015L-EN-P - November 2020

Change

Topic

Updated branding.

Throughout

Topic Name

Reason

Legal notices on page 8

Updated Legal notices

5580 controllers.

cable disconnected entries.

page 27

Compact GuardLogix 5380, and GuardLogix 5580 controllers.

Summary of Changes

This manual includes new and updated information. Use these reference tables to locate changed information.

Grammatical and editorial style changes are not included in this summary.

Global changes

New or enhanced features

This table contains a list of topics changed in this version, the reason for the change, and a link to the topic that contains the changed information.

Controller log on page 25 Updated the controller log information for the Compact

GuardLogix 5370, CompactLogix 5370, ControlLogix 5570, GuardLogix 5570 Compact GuardLogix 5380, CompactLogix 5380, CompactLogix 5480, ControlLogix 5580, and GuardLogix 5580 controllers.

Controller log buffer on page 28 Updated the controller log buffer information for the Compact

GuardLogix 5370, CompactLogix 5370, ControlLogix 5570, GuardLogix 5570 Compact GuardLogix 5380, CompactLogix 5380, CompactLogix 5480, ControlLogix 5580, and GuardLogix

Controller log events on page 37 Added the information logged for USB cable connected and USB

Entries captured in the controller log on

Get memory information from the controller on page 22

Added USB cable connected and disconnected to the list.

Added a note to indicate that this section is not applicable to CompactLogix 5380, CompactLogix 5480, ControlLogix 5580,

Rockwell Automation Publication 1756-PM015L-EN-P - November 2020 3

Summary of Changes Connections

Determine controller memory information

Controller logging

Preface

In this manual ............................................................................................. 7

Studio 5000 environment .......................................................................... 7

Additional Resources .................................................................................. 7

Legal notices ................................................................................................ 8

Chapter 1

Introduction ................................................................................................ 9

Inhibit a Connection .................................................................................. 9

Manage a connection failure ..................................................................... 11

Configure a major fault to occur ......................................................... 12

Monitor the health of a module .......................................................... 13

Chapter 2

Introduction ............................................................................................... 17

View data usage ......................................................................................... 17

Capacity tab for controllers that divide memory ............................... 18

Capacity tab for controllers with common memory area ................. 18

Estimate memory information offline for controllers with divided

memory ................................................................................................. 19

View run-time memory information for controllers with divided

memory ................................................................................................ 20

View the maximum and used Ethernet nodes for a controller ........ 21

Write logic to get memory information .................................................. 22

Get memory information from the controller .................................. 22

Choose the memory information .......................................................23

Convert INTs to a DINT ...................................................................... 24

Rockwell Automation Publication 1756-PM015L-EN-P - November 2020 5

Chapter 3

Introduction .............................................................................................. 25

Controller log ............................................................................................ 25

Controller log header .......................................................................... 26

Controller log entry ............................................................................. 26

Entries captured in the controller log ............................................... 27

Controller log buffer ........................................................................... 28

Controller log files and the removable media ................................... 28

Writing the controller log to the SD card .......................................... 28

Automatic save .............................................................................. 29

Save on demand ............................................................................ 30

Controller logging counters ................................................................ 31

Total entry count ............................................................................ 31

Table of Contents

Change detection

Access status information

Unsaved entry count ...................................................................... 31

Execution modification count ......................................................32

Log file storage ..................................................................................... 34

Log file format ...................................................................................... 35

Create Custom Log Entries ................................................................. 36

Sample Ladder Logic File ..................................................................... 37

Controller Log Events .......................................................................... 37

Chapter 4

Introduction ............................................................................................... 45

Controller change detection ..................................................................... 45

ChangesToDetect ................................................................................. 45

AuditValue ............................................................................................ 47

ChangesToDetect format ................................................................... 48

Change detection in the Logix Designer application ............................. 49

Component tracking ................................................................................. 49

Track the state of components and constant tags ............................. 51

View tracked components ................................................................... 51

Retrieve the tracked state value using a Message instruction .......... 51

Chapter 5

Introduction ............................................................................................... 53

Status of S:FS when the project has an SFC ............................................. 53

Get and set system data ............................................................................. 54

6 Rockwell Automation Publication 1756-PM015L-EN-P - November 2020

Resource

Description

Guidelines, publication, 1770-4.1

Automation industrial system.

and other certification details.

In this manual

Studio 5000 environment

Additional Resources

Preface

This manual describes how Logix 5000 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 Logix 5000 controllers.

For a complete list of common procedures manuals, refer to the

Logix 5000 Controllers Common Procedures Programming Manual, publication 1756PM001.

The term Logix 5000 controller refers to any controller based on the Logix 5000 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 Logix 5000™ controllers for discrete, process, batch, motion, safety, and drive-based solutions.

Rockwell Automation Publication 1756-PM015L-EN-P - November 2020 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.

These documents contain additional information concerning related

Rockwell Automation products.

Industrial Automation Wiring and Grounding

Product Certifications website, http://www.ab.com Provides declarations of conformity, certificates,

Provides general guidelines for installing a Rockwell

Preface

Legal notices

View or download publications at

http://www.rockwellautomation.com/literature

. To order paper copies of technical documentation, contact a local Rockwell Automation distributor or sales representative.

Rockwell Automation publishes legal notices, such as privacy policies, license agreements, trademark disclosures, and other terms and conditions on the

Legal Notices

page of the Rockwell Automation website.

End User License Agreement (EULA)

You can view the Rockwell Automation End User License Agreement (EULA) by opening the license.rtf file located in your product's install folder on your hard drive.

The default location of this file is:

C:\Program Files (x86)\Common Files\Rockwell\license.rtf.

Open Source Software Licenses

The software included in this product contains copyrighted software that is licensed under one or more open source licenses.

You can view a full list of all open source software used in this product and their corresponding licenses by opening the oss_license.txt file located your product's OPENSOURCE folder on your hard drive. This file is divided into these sections:

• Components Includes the name of the open source component, its version number, and the type of license.

• Copyright Text Includes the name of the open source component, its version number, and the copyright declaration.

• Licenses Includes the name of the license, the list of open source components citing the license, and the terms of the license.

The default location of this file is:

C:\Program Files (x86)\Common Files\Rockwell\Help\<product name>\Release Notes\OPENSOURCE\oss_licenses.txt.

8 Rockwell Automation Publication 1756-PM015L-EN-P - November 2020

You may obtain Corresponding Source code for open source packages included in this product from their respective project web site(s). Alternatively, you may obtain complete Corresponding Source code by contacting Rockwell Automation via the Contact form on the Rockwell Automation website:

http://www.rockwellautomation.com/global/aboutus/contact/contact.page. Please include "Open Source" as part of the request

text.

Term

Definition

Connection

Requested packet

guarantees that the data transfers at least as often as the RPI.

Path

communication of I/O data.

Introduction

Inhibit a Connection

Connections

A Logix 5000 controller uses connections for most, but not all, of its communication with other devices.

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.

Configuring the controller to communicate with other devices in the system indirectly determines the number of connections the controller uses. These communication types use these connections:

• I/O modules

• Produced and consumed tags

• Program parameters

• Certain types of Message (MSG) instructions (not all types use a connection)

Chapter 1

The RPI specifies the period at which data updates over a connection. For

interval (RPI)

example, an input module sends data to a controller at the RPI assigned to the module.

• Typically, an RPI is configured 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

The path describes the route that a connection takes to get to the destination. Typically, the path for a connection is defined when a device is added to the I/O

Configuration folder of the controller.

In some situations, such as when initially commissioning a system, it is useful

to disable portions of a control system and enable them as they are connected to the control system. Inhibiting individual modules or groups of modules prevents the controller from trying to communicate with the modules.

ATTENTION: Inhibiting a module breaks the connection to the module and prevents

Rockwell Automation Publication 1756-PM015L-EN-P - November 2020 9

Chapter 1 Connections

Then

check box.

box.

And you

And

Then

Program mode.

an error condition or fault)

indicate the fault condition.

An installed I/O module defaults to not inhibited. To inhibit a module, change an individual module’s properties.

Communicate with the module Do not inhibit the module. Clear the Inhibit Module

Prevent communication with the module Inhibit the module. Select the Inhibit Module check

When a communication bridge module is inhibited, the controller shuts down the connections to the bridge module and to all the modules that depend on that bridge module. Inhibit a communication bridge module to disable an entire branch of the I/O network.

When the module is inhibited, the Controller Organizer displays a yellow attention symbol over the module.

Offline ------------------------------> --------> The inhibit status is stored in the project.

When the project downloads to the controller, the module still is inhibited.

Online Inhibit a module while connected

to the module

Inhibit a module but a connection to the module was not established (perhaps due to

Uninhibit a module (clear the check box)

--------> The connection to the module is closed. The module's outputs go to the last configured

--------> The module is inhibited. The module status information changes to indicate that the module is inhibited and not faulted.

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 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

10 Rockwell Automation Publication 1756-PM015L-EN-P - November 2020

of I/O modules.

Manage a connection

Chapter 1 Connections

To inhibit or uninhibit a connection

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: Inhibit a connection

If Module_1_Inhibit = 1, then inhibit the operation of the I/O module named Module_1.

• The GSV instruction sets Module_1_Mode = value of the Mode attribute for the module.

• The OTE instruction sets bit 2 of Module_1_Mode = 1. This means inhibit the connection.

• The SSV instruction sets the Mode attribute for the module = Module_1_Mode.

failure

Rockwell Automation Publication 1756-PM015L-EN-P - November 2020 11

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. Program the controller to manage faults safely and efficiently.

ATTENTION: 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 generate a controller major fault when they lose their connections to the controller, or monitor the status

Chapter 1 Connections

If the controller should

Then

Continue operating

Configure a major fault to

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.

occur

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, choose between these options.

Fault (major fault)

Configure a major fault to occur Monitor the health of a module

Configure a major fault to occur on page 12

Monitor the health of a module on page 13

To force a module to generate a major fault in the controller if it loses connection with the controller, configure a major fault to occur. 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.

12 Rockwell Automation Publication 1756-PM015L-EN-P - November 2020

Monitor the health of a

Chapter 1 Connections

When selecting 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 20-second delay.

During this delay, the controller makes one attempt to connect to a module. If Major Fault On Controller…Run Mode is selected and no connection occurs 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.

module

• 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 Logix 5000 Controllers Major and Minor Faults Programming Manual, publication no. 1756-PM014.

Introduction

View data usage

Chapter 2

Determine controller memory information

Depending on the type of controller, the memory of the controller is divided into several areas.

ControlLogix 5570 GuardLogix 5570S CompactLogix 5370 Compact GuardLogix 5370S ControlLogix 1756-L5x, L6x GuardLogix 1756-L6xS

CompactLogix 1769-L2x, L3x SoftLogix5800 CompactLogix 5380 CompactGuardLogix 5380 CompactLogix 5480 ControlLogix 5580

I/O tags I/O memory Produced / Consumed tags Communication via Message (MSG)

Communication with polled (OPC/DDE) tags

Tags other than I/O, produced, or consumed

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.

Data and logic

memory

(1) To communicate with polled tags, the controller uses both I/O data and logic memory.

Rockwell Automation Publication 1756-PM015L-EN-P - November 2020 17

(2) 1756-L55M16 controllers have an additional memory section for logic.

In the Logix Designer application, the Capacity tab (formerly the Memory tab) on the Controller Properties dialog box shows data usage in the

controller. The data displayed on the Capacity tab depends on the controller.

Tip: Refer to the Memory information table to see whether a controller divides its