Rockwell Automation Allen-Bradley Logix5000 Owner's manual

Programming Manual
Catalog Numbers
1756 ControlLogix,
1768 CompactLogix, 1769 CompactLogix,
1789 SoftLogix, 1794 FlexLogix,
PowerFlex 700S with DriveLogix
Logix5000 Controllers Controller
Major and Minor Faults

Important User Information
Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the
Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1 available from your local Rockwell Automation sales
office or online at http://literature.rockwellautomation.com) describes some important differences between solid state equipment and hard-
wired electromechanical devices. Because of this difference, and also because of the wide variety of uses for solid state equipment, all
persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable.
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.
Allen-Bradley, Rockwell Automation, and TechConnect are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
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.
IMPORTANT Identifies information that is critical for successful application and understanding of the product.
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
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.

3Publication 1756-PM014B-EN-P - July 2008 3
Summary of Changes
Introduction
The release of this document contains new and updated information. To find
new and updated information, look for change bars, as shown next to this
paragraph.
Updated Information
This document contains the following changes.
Topic Page
Updated major fault codes Chapter 2

4Publication 1756-PM014B-EN-P - July 2008
Summary of Changes
Notes:

5Publication 1756-PM014B-EN-P - July 2008 5
Table of Contents
Preface Purpose of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
How to Use this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 1
Monitor Minor Faults Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Minor Fault Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 2
Handle a Major Fault Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Choose Where to Place the Fault Routine . . . . . . . . . . . . . . . . . . . 15
Create a Fault Routine for a Program . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Create the Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Assign the Routine as the Fault Routine . . . . . . . . . . . . . . . . . . . . 16
Create a Routine for the Controller Fault Handler. . . . . . . . . . . . . . . . 17
Create a Routine for the Power-Up Handler . . . . . . . . . . . . . . . . . . . . 17
Programmatically Clear a Major Fault. . . . . . . . . . . . . . . . . . . . . . . . . . 18
Create a Data Type to Store Fault Information . . . . . . . . . . . . . . . 18
Get the Fault Type and Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Check for a Specific Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Clear the Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Clear a Major Fault During Prescan . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Identify When the Controller is in Prescan . . . . . . . . . . . . . . . . . . 21
Get the Fault Type and Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Check for a Specific Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Clear the Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Test a Fault Routine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Create a User-Defined Major Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Create a Fault Routine for the Program . . . . . . . . . . . . . . . . . . . . . 25
Configure the Program to Use the Fault Routine . . . . . . . . . . . . . 25
Jump to the Fault Routine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Major Fault Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

6Publication 1756-PM014B-EN-P - July 2008
Table of Contents

7Publication 1756-PM014B-EN-P - July 2008 7
Preface
Purpose of this Manual
This manual shows how to monitor and handle major and minor controller
faults. 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, see the Logix 5000 Controllers
Common Procedures Programming Manual, publication 1756-PM001.
The term Logix5000 controller refers to any controller that is based on the
Logix5000 operating system, such as:
·CompactLogix controllers
·ControlLogix controllers
·DriveLogix controllers
·FlexLogix controllers
·SoftLogix5800 controllers
How to Use this Manual
Some text is formatted differently from the rest of the text.
Text that is Identifies For example Means
Italic the actual name of an item that you
see on your screen or in an example Right-click User-Defined … Right-click the item that is named User-Defined.
courier information that you must supply
based on your application (a
variable)
Right-click
name_of_program …You must identify the specific program in your application. Typically, it is a name or
variable that you have defined.
enclosed in brackets a keyboard key Press [Enter]. Press the Enter key.

8Publication 1756-PM014B-EN-P - July 2008
Summary of Changes Preface
Notes:

9Publication 1756-PM014B-EN-P - July 2008 9
Chapter 1
Monitor Minor Faults
Introduction
To use relay ladder logic to capture information about a minor fault:
To check for a Do this
Periodic task overlap 1. Enter a GSV instructions that gets the FAULTLOG object, MinorFaultBits attribute.
2. Monitor bit 6.
Load from nonvolatile
memory 1. Enter a GSV instructions that gets the FAULTLOG object, MinorFaultBits attribute.
2. Monitor bit 7.
Problem with the serial port 1. Enter a GSV instructions that gets the FAULTLOG object, MinorFaultBits attribute.
2. Monitor bit 9.
Low battery 1. Enter a GSV instructions that gets the FAULTLOG object, MinorFaultBits attribute.
2. Monitor bit 10.
Problem with an instruction 1. Create a user-defined data type that stores the fault information. Name the data type FaultRecord and
assign these members:
Name: Data Type: Style:
TimeLow DINT Decimal
TimeHigh DINT Decimal
Type INT Decimal
Code INT Decimal
Info DINT[8] Hex
2. Create a tag that will store the values of the MinorFaultRecord attribute. Select the data type from
step 1.
3. Monitor S:MINOR.
4. If S:MINOR is on, use a GSV instruction to get the values of the MinorFaultRecord attribute.
5. If you want to detect a minor fault that is caused by another instruction, reset S:MINOR. (S:MINOR
remains set until the end of the scan.)

10 Publication 1756-PM014B-EN-P - July 2008
Chapter 1 Monitor Minor Faults
This example checks for a low battery warning.
EXAMPLE Check for a minor fault
Minor_fault_check times for 1 minute (60000 ms) and then automatically restarts itself.
Every minute, minor_fault_check.DN turns on for one scan. When this occurs, the GSV instruction gets the value of the
FAULTLOG object, MinorFaultBits attribute, and stores it in the minor_fault_bits tag. Because the GSV instruction only
executes once every minute, the scan time of most scans is reduced.
If minor_fault_bits.10 is on, then the battery is low.
42373