Rockwell-automation Logix5000 Controllers Major, Minor, and I/O Faults Instrukcja Użytkownika

Przeglądaj online lub pobierz Instrukcja Użytkownika dla Ekwipunek Rockwell-automation Logix5000 Controllers Major, Minor, and I/O Faults. Rockwell Automation Logix5000 Controllers Major, Minor, and I/O Faults Programming Manual User Manual Instrukcja obsługi

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj

Podsumowanie treści

Strona 1 - Programming Manual

Programming Manual Logix5000 Controllers Major, Minor, and I/O Faults Catalog Numbers 1756 ControlLogix, 1756 GuardLogix, 1768 Compact GuardLogix,

Strona 2 - Important user information

Chapter 1 Major faults Recover from a major fault If the fault is cleared, the faulted instruction does not continue to run. Example

Strona 3 - Summary of changes

Major faults Chapter 1 The logic inside an Add-On Instruction generates a fault. While the logic of an Add-On Instruction may look

Strona 4

Chapter 1 Major faults • Prescan provides a system-defined initialization of the user program when the controller is switched from

Strona 5 - Table of contents

Major faults Chapter 1 Placement of fault routines You use a fault routine to program logic to take specific action after a fault,

Strona 6 - Chapter 3

Chapter 1 Major faults Choose where to place the fault routine Where you place the routine depends on the type of fault that you wan

Strona 7 - Additional resources

Major faults Chapter 1 4. (optional) In the Description field, type a description of the routine. 5. On the Type menu, use the

Strona 8

Chapter 1 Major faults If a fault routine has already been created, it is included in the main program. 2. Right-click MainProgram

Strona 9 - Major faults

Major faults Chapter 1 This section provides the steps for creating a fault routine to operate as the controller fault handler. Pr

Strona 10 - Example 2

Chapter 1 Major faults 4. In the Controller Organizer, right-click the program you created in step 2 and choose Add>New Routine.

Strona 11

Major faults Chapter 1 The Power-Up Handler is an optional task that executes when the controller powers up in Run or Remote Run m

Strona 12

Important user information Read this document and the documents listed in the additional resources section about installation, configuration, and ope

Strona 13 - Placement of fault routines

Chapter 1 Major faults 3. Click OK. The program is added to the Power-Up Handler. 4. Right-click the program you created in step

Strona 14 - Create a fault routine for a

Major faults Chapter 1 7. Click OK. The fault routine is added to the Power-Up Handler. If you want to edit the new routine, doub

Strona 15

Chapter 1 Major faults To simplify access to the MajorFaultRecord attribute, complete these steps to create a user-defined data type

Strona 16

Major faults Chapter 1 Get the fault type and code Enter the following rung in the fault routine for the program. The GSV instruc

Strona 17 - Controller Fault Handler

Chapter 1 Major faults Item Description The second CLR instruction sets to zero the value of the fault code in the major_fault_rec

Strona 18

Major faults Chapter 1 Identify when the controller is in prescan In the main routine of your program, enter the following rung as

Strona 19 - Power-Up Handler

Chapter 1 Major faults Check for a specific fault Enter the following rung in the fault routine for the program. Item Description

Strona 20

Major faults Chapter 1 The SSV instruction: • Begins during prescan with the bits of all OTE instructions off and this instructio

Strona 21 - Programmatically clear a

Chapter 1 Major faults See the following procedures to create a user-defined major fault. • Create a fault routine for the program

Strona 22

Major faults Chapter 1 Example: Create a User-Defined Major Fault When Tag_1.0 = 1, execution jumps to name_of_fault_routine. A m

Strona 23 - Check for a specific fault

Summary of changes This manual contains new and updated information. The following table contains the changes made to this revision. Topic Page Upda

Strona 24 - Clear a major fault during

Chapter 1 Major faults Type Code Cause Recovery Method 1 60 For a controller with no memory card installed, the controller: • D

Strona 25

Major faults Chapter 1 Type Code Cause Recovery Method 4 89 In an SFR instruction, the target routine does not contain the ta

Strona 26 - Clear the fault

Chapter 1 Major faults Type Code Cause Recovery Method 11 7 Synchronous connection incurred a failure. Try these steps: • Fir

Strona 27 - Create a user-defined major

Major faults Chapter 1 Type Code Cause Recovery Method 14 6 Safety partner firmware is incompatible. Update the safety partn

Strona 28 - Jump to the Fault Routine

Chapter 1 Major faults Type Code Cause Recovery Method 18 9 An Absolute Position Recovery (APR) fault has occurred and the abso

Strona 29 - Major fault codes

Chapter 2 Minor faults This chapter explains minor fault codes and how to work with them in the Logix Designer application. The following table expla

Strona 30

Chapter 2 Minor faults The following example checks for a low battery warning. Example: Check for a minor fault. Minor_fault_check

Strona 31

Minor faults Chapter 2 Minor faults are indicated in the following locations. • Controller Properties dialog box, Minor Faults ta

Strona 32

Chapter 2 Minor faults Type Code Cause Recovery Method 6 4 Virtual adapter task overlap. (CompactLogix 1769-L2x and 1769-L3x co

Strona 33

Chapter 3 I/O fault codes This chapter explains I/O fault codes and how to work with them in the Logix Designer application. I/O faults are indicated

Strona 35 - Minor faults

Chapter 3 I/O fault codes • A yellow warning symbol appears on the module in the I/O Configuration tree of the Logix Designer appli

Strona 36

I/O fault codes Chapter 3 Code Interpretation #0005 The controller is attempting to make a connection to the module and has rece

Strona 37 - Minor fault codes

Chapter 3 I/O fault codes Code Interpretation #0014 A MSG instruction is configured to change an attribute that does not exist. #0

Strona 38

I/O fault codes Chapter 3 Code Interpretation #0109 The connection size is inconsistent with the expected size. Possible causes

Strona 39 - I/O fault codes

Chapter 3 I/O fault codes Code Interpretation #0117 The connection is to an invalid port or port that is already in use. One of th

Strona 40

I/O fault codes Chapter 3 Code Interpretation #0205 Possible causes include the following. • The controller is attempting to se

Strona 41

Chapter 3 I/O fault codes Code Interpretation #0306 The ControlNet Configuration Master (CCM) cannot be found. The 1756-CNB module

Strona 42

I/O fault codes Chapter 3 Code Interpretation #FD05 The module requires an assigned axis or group table. Assign a Group or Axis.

Strona 43

Chapter 3 I/O fault codes Code Interpretation #FE09 Possible causes include the following. • The controller is attempting to set

Strona 44

I/O fault codes Chapter 3 Code Interpretation #FF0B Possible causes include the following. • The configuration for the module i

Strona 45

Table of contents Studio 5000 environment ... 7 Additional resource

Strona 47

1 1756-L2x I/O fault indicator 43 1756-L6x I/O fault indicator 43 C check specific fault 26 CIP Motion major fault codes 29 clear major fau

Strona 48

Index program create fault routine 14 R recovering from a major fault 9 important points regarding Add-On Instructions 9 routine 14 create

Strona 49

Rockwell Automation support Rockwell Automation provides technical information on the web to assist you in using its products. At http://www.rockwell

Strona 50

Table of Contents Chapter 3 Indications of I/O faults ... 39 I/O f

Strona 51

Preface This manual shows how to monitor and handle major and minor controller faults. It also provides lists of major, minor, and I/O fault codes th

Strona 52

Preface Resource Description Industrial Automation Wiring and Grounding Guidelines, publication 1770-4.1. Provides general guidelines for installing

Strona 53 - Rockwell Automation support

Chapter 1 Major faults This chapter explains major fault codes and how to work with them in the Logix Designer application. If a fault condition occu

Komentarze do niniejszej Instrukcji

Brak uwag