Rockwell Automation Allen-Bradley Logix5000 Programming Manual
  1. Manuals
  2. Brands
  3. Rockwell Automation Manuals
  4. Controller
  5. Allen-Bradley Logix5000
  6. Programming manual
Rockwell Automation Allen-Bradley Logix5000 Programming Manual

Rockwell Automation Allen-Bradley Logix5000 Programming Manual

Major and minor faults
Hide thumbs Also See for Allen-Bradley Logix5000:
Table of Contents

Advertisement

Quick Links

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

Advertisement

Table of Contents
loading

Related Manuals for Rockwell Automation Allen-Bradley Logix5000

Summary of Contents for Rockwell Automation Allen-Bradley Logix5000

  • Page 1 Logix5000 Controllers Controller Major and Minor Faults Programming Manual Catalog Numbers 1756 ControlLogix, 1768 CompactLogix, 1769 CompactLogix, 1789 SoftLogix, 1794 FlexLogix, PowerFlex 700S with DriveLogix...
  • Page 2 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.
  • Page 3 Summary of Changes The release of this document contains new and updated information. To find Introduction new and updated information, look for change bars, as shown next to this paragraph. This document contains the following changes. Updated Information Topic Page Updated major fault codes Chapter 2 3Publication 1756-PM014B-EN-P - July 2008...
  • Page 4 Summary of Changes Notes: Publication 1756-PM014B-EN-P - July 2008...

  • Page 5: Table Of Contents

    Table of Contents Purpose of this Manual ........7 Preface How to Use this Manual .
  • Page 6 Table of Contents Publication 1756-PM014B-EN-P - July 2008...

  • Page 7: Purpose Of This Manual

    Preface This manual shows how to monitor and handle major and minor controller Purpose of this Manual 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.
  • Page 8 Summary of Changes Preface Notes: Publication 1756-PM014B-EN-P - July 2008...

  • Page 9: Chapter 1 Introduction

    Chapter Monitor Minor Faults To use relay ladder logic to capture information about a minor fault: Introduction 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 1.
  • Page 10 Chapter 1 Monitor Minor Faults This example checks for a low battery warning. Check for a minor fault EXAMPLE 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.
  • Page 11 Monitor Minor Faults Chapter 1 This example checks for a minor fault that is caused by a specific instruction. Check for a minor fault that is caused by an instruction EXAMPLE Multiply value_a by 1000000 and check for a minor fault, such as a math overflow. ·...

  • Page 12: Minor Fault Codes

    Chapter 1 Monitor Minor Faults The type and code correspond to the type and code displayed in these Minor Fault Codes locations. · Controller Properties dialog box, Minor Faults tab · PROGRAM object, MINORFAULTRECORD attribute Type Code Cause Recovery Method An arithmetic overflow occurred in an instruction.
  • Page 13 Monitor Minor Faults Chapter 1 Type Code Cause Recovery Method The CTS line is not correct for the current configuration. Disconnect and reconnect the serial port cable to the controller. Make sure the cable is wired correctly Poll list error. Check for the following errors in the poll list: ·...
  • Page 14 Chapter 1 Monitor Minor Faults Notes: Publication 1756-PM014B-EN-P - July 2008...

  • Page 15: Chapter 2 Introduction

    Chapter Handle a Major Fault If a fault condition occurs that is severe enough for the controller to shut Introduction down, the controller generates a major fault and stops the execution of logic. · Depending on your application, you may not want all major faults to shut down your entire system.

  • Page 16: Create A Fault Routine For A Program

    Chapter 2 Handle a Major Fault Create a Fault Routine for a Create the Routine Program 1. Right-click the program and choose New Routine. 2. Define the routine. Assign the Routine as the Fault Routine 1. Right-click the program and choose Properties. 2.

  • Page 17: Create A Routine For The Controller Fault Handler

    Handle a Major Fault Chapter 2 Create a Routine for the Controller Fault Handler 1. Create a program for the Controller Fault Handler. 2. Create a routine for the program. 3. Configure the routine as the main routine for the program. The power-up handler is an optional task that executes when the controller Create a Routine for the powers up in run/remote run mode.

  • Page 18: Programmatically Clear A Major Fault

    Chapter 2 Handle a Major Fault Programmatically Clear a To clear a major fault that occurs during the execution of your project, complete these actions in the appropriate routine. Major Fault · Create a Data Type to Store Fault Information ·...

  • Page 19: Get The Fault Type And Code

    Handle a Major Fault Chapter 2 Get the Fault Type and Code 42372 1. The GSV instruction accesses the MAJORFAULTRECORD attribute of this program. This attribute stores information about the fault. 2. The GSV instruction stores the fault information in the major_fault_record tag (of type FAULTRECORD).

  • Page 20: Clear The Fault

    Chapter 2 Handle a Major Fault Clear the Fault 42372 1. The SSV instruction writes new values to the MAJORFAULTRECORD attribute of this program. 2. The SSV instruction writes the values contained in the major_fault_record tag. Since the Type and Code member are set to zero, the fault clears and the controller resumes execution.

  • Page 21: Identify When The Controller Is In Prescan

    Handle a Major Fault Chapter 2 Identify When the Controller is in Prescan In the main routine of your program, enter this rung as the first rung in the main routine of the program. 43063 The fault routine of this program uses the status of this bit to determine if the fault occurred during prescan or normal scan of the logic.

  • Page 22: Check For A Specific Fault

    Chapter 2 Handle a Major Fault Check for a Specific Fault Enter this rung in the fault routine for the program. 43064 1. During prescan the bits of all OTE instructions are off and this instruction is true. Once the controller begins to execute the logic, this instruction is always false.

  • Page 23: Clear The Fault

    Handle a Major Fault Chapter 2 Clear the Fault Enter this rung in the fault routine for the program. 43064 1. During prescan the bits of all OTE instructions are off and this instruction is true. Once the controller begins to execute the logic, this instruction is always false.

  • Page 24: Create A User-Defined Major Fault

    Chapter 2 Handle a Major Fault 3. To simulate a fault, set the input condition. Test a fault routine EXAMPLE When test_fault_routine is on, a major fault occurs and the controller executes Fault_Routine. If you want to suspend (shut down) the controller based on conditions in your Create a User-Defined application, create a user-defined major fault.

  • Page 25: Create A Fault Routine For The Program

    Handle a Major Fault Chapter 2 Create a Fault Routine for the Program Does a fault routine already exist for the program? Then Go to “Jump to the Fault Routine“on page 26 Create a fault routine for the program: 1. In the controller organizer, right-click the program and choose New Routine.

  • Page 26: Jump To The Fault Routine

    Chapter 2 Handle a Major Fault Jump to the Fault Routine In the main routine of the program, enter this rung: conditions when the controller should shut down Where Fault_Routine name of the fault routine for the program value for the fault code Create a User-Defined Major Fault EXAMPLE When Tag_1.0 = 1, execution jumps to name_of_fault_routine.

  • Page 27: Major Fault Codes

    If the problem persists: 1. Before you cycle power to the controller, record the state of the OK and RS232 LEDs. 2. Contact Rockwell Automation support. See the back of this publication. For a controller with a CompactFlash card 1. Clear the fault.
  • Page 28 Contact Rockwell Automation support. See the back of this Load from nonvolatile memory failed due to bad publication. checksum.
  • Page 29 Handle a Major Fault Chapter 2 Type Code Cause Recovery Method Synchronous connection incurred a failure. First execute Motion Axis Fault Reset. If that doesn’t work, pull servo module out and plug back in. If all else fails replace servo module.
  • Page 30 Chapter 2 Handle a Major Fault Notes: Publication 1756-PM014B-EN-P - July 2008...
  • Page 32 New Product Satisfaction Return Rockwell Automation tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility. However, if your product is not functioning and needs to be returned, follow these procedures.

This manual is also suitable for:

Allen-bradley compactlogix 1768Allen-bradley compactlogix 1769Allen-bradley softlogix 1789Allen-bradley controllogix 1756Allen-bradley flexlogix 1794Allen-bradley powerflex 700s with drivelogix

Table of Contents