Home

1756-PM014 - Rockwell Automation

1. se s seseessseesssessessreessreessoerseonreessoerseosresssoerseons 13 Choosing Where to Place the Fault Routine ssssssssssserssssessssssssrreesrssssesses 14 Creating a Fault Routine for a Program ssssesssssssssseseesesssssseseseeeeseeeesssssneeeeeeeeesss 14 Changing a Fault Routine Assignment of a Program ssssssssssrreeseeeeesses 15 Creating a Routine for the Controller Fault Handler ssssssssessssessssssseeeessses 16 Creating a Routine for the Power Up Handler esseessssseessesseseesneens 18 Programmatically Clearing a Major Fault sssssssssssssesssssssssesseeeeersssssssrerereeeeesss 20 Creating a Data Type to Store Fault Information sssssssssssssssssereeseseessesss 21 Cs eteine the Fault Type and Code ironian 23 Checking tora Specie Pa wt unioniin NAE 23 Clearing the EA rarena n e OR 24 Clearing a Major Fault Darina Prescahiaserigekace a 24 Identifying When the Controller is in Prescan ee esssseeseeseeseeneesees 25 Getting the Fault Type and Ode sccsesennsattiatinan learnt aiuiiwnadatenicts 25 Checking for a Specie altesaam 26 Clearing the Pau lt cain itm sonatas itil acute are ulead 26 Terora aae ROUE an a ennor aren TEN SPM TrTTnT ance tmTar 27 Creating a User Denied Mior Fiiltassortainion ena 27 Creating a Fault Routine for the Program ssesssesssssseesesesessssssseeeeeeesrsssssses 28 Configuring the Program to Use the Fault Routine sssssssssssrreeseessessss 28 Jumping to the Fault Routine annenin sti iat tiaitaiines
2. 1 Inthe Controller Organizer expand the MainTask Tasks nie Maint ask iN Unscheduled Programs Phases Rockwell Automation Publication 1756 PM014H EN P November 2015 15 Chapter 1 Major Faults 5 If a fault routine has already been created it is included in the main program Tasks J A MainTask 3 MainProgram A Parameters and Local Tags Ei MainRoutine gt B Program_Fault_Routine_1 Right click MainProgram and choose Properties On the Program Properties MainProgram dialog box click the Configuration tab In the Fault field choose the routine you want to be the program s fault routine So SSS a ef Program Properties MainProgram a General Configuration Parameters Monitor Assigned Routines Main Ef Main Routine x Fault F At_Faut _Routine_2 ay metri B Progam_Fau _Routine_ l Click OK The program you specified in step 4 is now indicated as the fault routine in the main program Creating a Routine for the This section provides the steps for creating a fault routine to operate as the Controller Fault Handler controller fault handler Program tags are automatically created during this process 16 Rockwell Automation Publication 1756 PM014H EN P November 2015 Important Major Faults Chapter 1 When you program the fault handler remember that any instruction that is skipped as part of the fault handling progra
3. controller The ESM needs to be replaced due to a hardware fault Replace the ESM It is not capable of maintaining the WallClockTime attribute or controller program at powerdown The ESM cannot store enough energy to maintain the WallClockTime Replace the ESM attribute or the controller program at power down An internal controller diagnostic has failed Contact Rockwell Automation Technical Support with the fault type and fault code logged 10 13 4 NO 15 1 35 Controller internal temperature is approaching operating limit Measures should be taken to reduce the ambient temperature of the module Follow the recommended limits for the ambient inlet temperature and apply the required clearance around the chassis N4 Rockwell Automation Publication 1756 PM014H EN P November 2015 39 Chapter 3 Indications of 0 Faults Rockwell Automation Publication 1756 PM014H EN P November 2015 1 0 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 in the following ways e The I O indicator of the controller shown in examples below flashes green or red BATT COK The I O status indicator and messages show in the controller status area of the Logix Designer application Then indicator flashes green or red and the corresponding status message indicates an error Rem Prog A Pr
4. such as a math overflow To make sure that a previous instruction did not produce the fault the rung first clears S MINOR The rung then executes the multiply instruction If the instruction produces a minor fault the controller sets S MINOR If S MINOR is set the GSV instruction gets information about the fault and resets S MINOR 36 Rockwell Automation Publication 1756 PM014H EN P November 2015 Minor Faults Chapter 2 S MINOR UL Multiply Source Yvaluie_a Source B 1000000 Dest vallie_b 5 MINA GSW S MIHOR Get System Value Class name Program Instance name THIS Attribute Name Minot aulth ecord Dest minor Fault record T ire Low Minor Fault Codes Minor faults are indicated in the following locations e Controller Properties dialog box Minor Faults tab e Program object MinorFaultRecord attribute The following tables identify the type code and suggested recovery method when applicable 1 e A1769 power supply is connected directly to the controller s 1768 e Remove the power supply from the 1768 CompactBus and cycle power CompactBus with an invalid configuration to the system Oa A e The 1768 power supply powering the controller has failed e Replace the power supply An arithmetic overflow occurred in an instruction Examining arithmetic operations order or adjust the values In a GSV SSV instruction the specified instance was not found Check the instance name In a GSV SSV instruction
5. 2 Download the project e Wrote diagnostic information to the memory card 3 Change to Remote Run or Run mode e Cleared the project from memory If the fault persists contact Rockwell Automation Technical Support Rockwell Automation Publication 1756 PM014H EN P November 2015 29 Chapter 1 Type 1 SPP HS Se Py Sy gt 30 Major Faults For a controller with a Secure Digital SD card installed the 1 Clear the fault controller en N 2 Download the project e Detected a nonrecoverable fault 3 Change to Remote Run or Run mode e Wrote diagnostic information to the memory card If the fault persists contact Rockwell Automation Technical Support When in this state the controller does not open any connections or allow a transition to Run mode A required 1 0 module connection failed Check the e 1 0 module is in the chassis e Electronic keying requirements e Controller properties Major Fault tab and the Module Properties Connection tab for more information about the fault Possible fault with the chassis At least one required connection was not established before Wait for the controller 1 0 light to turn green before changing to Run mode going to Run mode Not recoverable Replace the chassis Unknown instruction encountered Remove the unknown instruction This probably happened due to a program conversion process Array subscript too big control structure POS or LEN
6. Automation Publication 1756 PM014H EN P November 2015 Type 18 18 18 18 18 18 18 18 18 18 18 7 i 128 The CIP Motion drive has not initialized correctly The CIP Motion drive has not initialized correctly This fault is indicated when a manufacturer specific initialization fault has occurred The Physical Axis Fault bit is set indicating a fault on the physical axis The Physical Axis Fault bit is set indicating a fault on the physical axis This fault is indicated when a manufacturer specific axis fault has occurred A motion fault occurred A CIP Motion Drive fault has occurred Usually the fault affects all the axes associated with the module and all of the associated axes are shut down A motion group fault has occurred Usually the fault affects all of the axes associated with a motion group A fault has occurred during the configuration of a CIP Motion Drive Typically this fault occurs after an attempt to update an axis configuration attribute of a CIP Motion Drive was unsuccessful An Absolute Position Recovery APR fault has occurred and the absolute position of the axis cannot be recovered An Absolute Position Recovery APR fault has occurred and the absolute position of the axis cannot be recovered This fault is indicated when a manufacturer specific APR fault has occurred A fault specific to the Guard Motion safety function has occurred This fau
7. Motion Groups H Add On Instructions E Data Types Ctrl C G Trends Ctrl V hin Logical Model Del Ctri X 2 New Local Tag New Parameter Ctrl W Import Routine On the New Routine dialog box in the Name field type the name of the routine In the Assignment field keep the default setting Main Tip Even though you can choose Fault in the Assignment field assigning the routine as a fault routine within the Power Up Handler is not necessary 7 Click OK The fault routine is added to the Power Up Handler If you want to edit the new routine double click it to open it E Controller L75_101 BP Controller Tags 4 Controller Fault Handler oS Power Up Handler 3 PowerUp_Program_1 Ls Parameters and Local Tags E PowerUp_Program_1 Prog rammatically Clearing To clear a major fault that occurs during the execution of your project see the a Major Fault 20 Rockwell Automation Publication 1756 PM014H EN P November 2015 following sections and complete the actions in the appropriate routine Major Faults Chapter 1 e Creating a Data Type to Store Fault Information on page 21 e Getting the Fault Type and Code on page 25 e Checking for a Specific Fault on page 26 e Clearing the Fault on page 26 Important Do not use fault routines to continually clear all faults on the controller Program the fault routine to be selective in the types and number of faults cleared Important Wh
8. Move Source 0 Source 0 Dest m4 jor_fault_record Type Dest major _fault_record Type 0 3 O Set system valus CIP Object class PROGRAM CIP Object name THIS Attribute name MAJORFAULTRECORD Source ms jor_fault_record Time_Low Item Description The first EQU instruction checks for a specific type of fault such as program 1 0 In Source B enter the value for the type of fault that you want to clear 2 The second EQU instruction checks for a specific fault code In Source B enter the value for the code that you want to clear 3 The first CLR instruction sets to zero the value of the fault type in the major_fault_record tag Rockwell Automation Publication 1756 PM014H EN P November 2015 23 Chapter 1 Major Faults Item Description O The second CLR instruction sets to zero the value of the fault code in the major_fault_record tag Clearing the Fault Get System Value Lisz name Instance name Program THIS Altnbute Name a ao rFaulttRecord Dest mano fal record Tme_Low The SSV instruction writes e The new values to the MajorFaultRecord attribute of this program e The values contained in the major_fault_record tag Because the Type and Code member are set to zero the fault clears and the controller resumes execution Clearing aM ajor Fault If the controller faults immediately after you switch it to the Run mode examine During Prescan the prescan operation for the fault Depending on the revision of your
9. Support for initial help in getting your product up and running United States or Canada 1 440 646 3434 Outside United States or Canada Use the Worldwide Locator available at http www rockwellautomation com locations or contact your local Rockwell Automation representative 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 United States Contact your distributor You must provide a Customer Support case number call the phone number above to obtain one to your distributor to complete the return process Outside United States Please contact your local Rockwell Automation representative for the return procedure Documentation feedback Your comments will help us serve your documentation needs better If you have any suggestions on how to improve this document complete the feedback form publication RA DU002 Rockwell Otomasyon Ticaret A S Kar Plaza Is Merkezi E Blok Kat 6 34752 erenk y Istanbul Tel 90 216 5698400 www rockwellautomation com Power Control and Information Solutions Headquarters Americas Rockwell Automation 120 South Second Street Milwaukee WI 53204 2496 USA Tel 1 414 382 2000 Fax 1 414 382 4444 Europe Middle East Africa Rockwell Automarion NV Pegasus Park De Kleetlaan 12a 831 Dieg
10. an error Verify that the instance number specified has been properly specified in the PLC 5 controller FEOD The symbol instance number was found to not be set FEQE The module is currently being updated FEOF Firmware supervisor has attempted to update an unsupported module FE10 The firmware file to update the module cannot be found FE11 The firmware file is corrupted FE12 An error has occurred while updating the module FE13 An active connection could not be made to the target module FE14 The firmware file is currently being read FE22 The target to originator netparams connection type is invalid FE23 The target to originator netparams connection does not specify whether unicast is allowed FFOO The controller is attempting to set up a connection with the module and has received an error Verify that the physical module is the same module type or is a compatible module as created in the software If the module is a 1756 DHRIO module in a remote chassis connected via a ControlNet network verify that the network has been scheduled with RSNetWorx software Even after the network has been scheduled with RSNetWorx for ControlNet software if you are online and if the 1756 DHRIO module is configured for DH network only a ff00 Module Fault no connection instance may occur The module is properly communicating even though Faulted is displayed as its Status on the Module Properties dialog box Disregard the error message a
11. controller an array subscript that is beyond the range of the array out of range during prescan might cause a fault If controller is revision Then 11 x or earlier During prescan an array subscript that is beyond the range of the array out of range produces a major fault 12 x See the release notes for the firmware of your controller 13 0 or later During prescan the controller automatically clears any faults due to an array subscript that is beyond the range of the array out of range See the following procedures to clear a major fault that occurs during prescan e Identifying When the Controller is in Prescan on page 25 e Getting the Fault Type and Code on page 25 e Checking for a Specific Fault on page 26 e Clearing the Fault on page 26 24 Rockwell Automation Publication 1756 PM014H EN P November 2015 Major Faults Chapter 1 Important It is good programming practice to check for a specific fault before clearing that fault Identifying When the Controller is in Prescan In the main routine of your program enter the following rung as the first rung in the main routine of the program LPUL scanning 0 pS m 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 e During prescan this bit is off During prescan the controller resets all bits that are referenced by OTE instructions e When the controller begins to run the
12. either Check the Class name and Attribute name e Specified Class name is not supported e Specified Attribute name is not valid DA The GSV SSV destination tag was too small to hold all of the data Fix the destination so it has enough space Bad parameters passed through to the ASCII port Verify the ASCII configuration settings 35 PID delta time lt 0 Adjust the PID delta time so that it is gt 0 36 PID setpoint out of range Adjust the setpoint so that it is within range The LEN value of the string tag is greater than the DATA size of the string 1 Check that no instruction is writing to the LEN member of the string tag tag 2 In the LEN value enter the number of characters that the string contains SP LS ey gt mi Rockwell Automation Publication 1756 PM014H EN P November 2015 37 Chapter 2 Type 4 38 Minor Faults The output string is larger than the destination Create a new string data type that is large enough for the output string Use the new string data type as the data type for the destination The output number is beyond the limits of the destination data type Either e Reduce the size of the ASCII value e Use a larger data type for the destination The Start or Quantity value is invalid Check that the Start value is between 1 and the DATA size of the Source Check that the Start value plus the Quantity Value is less than or equal to the DATA size of
13. faults Rockwell Automation Publication 1756 PM014H EN P November 2015 Recovering From a Major Fault If the fault is cleared the faulted instruction does not continue to run Chapter 1 Major Faults GU Equal Source return value T Source B 123 10 Example 1 SR Jump To Subroutine Routine Hame subroutine Input Par array bad_index Return Par return alue label MP A JSR instruction passes an input parameter containing an indirect address that is out of bounds If the fault is cleared the JSR instruction is aborted the subroutine does not run and execution resumes with the EQU Example 2 Ao my Aci my AoiTaq inputi qj 0e input j 0e utputi je output t 0e OY Move Surte x 0 Dest y E j The logic inside an Add On Instruction generates a fault While the logic of an Add On Instruction may look like a subroutine it is not the Add On Instruction is an instruction When a fault occurs inside an Add On Instruction the remainder of the Add On Instruction is aborted If the fault is cleared execution resumes with the MOV Rockwell Automation Publication 1756 PM014H EN P November 2015 Major Faults Chapter 1 Important Points Regarding Add On Instructions e The Add On Instruction stops running at the instruction that caused the fault This means that the remainder of the scan mode routine does not run e Ifthe fault is cleared execution resumes at the instruction following the
14. is already running 0103 Possible causes include the following e The controller is requesting services not supported by the module e The module in use that is the physical module is different than the module specified in the 1 0 configuration tree and is therefore causing the connection or service to fail The fault may occur even when the module passed the electronic keying test This may result when Disable Keying or Compatible Keying options were used in the module configuration instead of the Exact Match option Despite passing the electronic keying test the module being connected to does not have the same features or settings as the module specified in the 1 0 configuration tree and does not support the connection or service being attempted Check the module in use and verify that it exactly matches the module specified in the 1 0 configuration tree of Logix Designer application For more information about electronic keying see the user manual for the module you are using 0106 An ownership conflict occurred for the connection One of the following conditions exists e The Connection Request to this module has been rejected due to an Ownership conflict with another Owner for example another Controller This may occur with modules such as output modules that allow only a single Owner to configure and control its outputs This fault may also occur if the module is configured as Listen Only and supports only one connection e Ifthe Owner is co
15. is invalid Adjust the value to be within the valid range Do not exceed the array size or go beyond dimensions defined Control structure LEN or POS lt 0 Adjust the value so it is gt 0 The parameters of the JSR instruction do not match those of Pass the appropriate number of parameters If you pass too many parameters the extra the associated SBR or RET instruction ones are ignored without any error A timer instruction has a negative preset or accumulated value Fix the program so that it cannot load a negative value into timer preset or accumulated value JMP to a label that did not exist or was deleted Correct the JMP target or add the missing label A sequential function chart SFC called a subroutine andthe Remove the jump back to the calling SFC subroutine tried to jump back to the calling SFC This occurs when the SFC uses either a JSR or FOR instruction to call the subroutine 20 21 23 16 20 21 31 34 2 4 co N UY The data tested was not inside the required limits This occurs Adjust the value to be within the valid range Do not exceed the array size or go beyond with array subscripts used with Boolean arrays and bit level the dimensions defined addressing Stack overflow Reduce the subroutine nesting levels or the number of parameters passed In an SFR instruction the target routine does not contain the Correct the SFR target or add the missing step target step A safety instruction o
16. keying see the user manual for the module you are using 0007 A service request is unconnected but should be connected 0008 The controller has requested a service which is not implemented on the target module 0009 The configuration for the module is invalid The module configuration may have been changed in the Data Monitor or programmatically Open the Connections tab of the Module Properties dialog box for the additional fault code The additional fault code indicates the configuration parameter that is causing the fault You may have to correct multiple parameters before this fault is cleared and the module is connected Verify that the configuration is valid by using the module configuration software to validate your configuration Consult the module documentation for a list of fault codes to determine the configuration parameter that is in error 000A Possible causes include the following e A connection is being created where the connection type is invalid e An object attribute or tag value is invalid If an object attribute or tag is invalid export the Logix Designer file then re import it Reschedule the ControlNet network after re importing if applicable 000C The controller is attempting to request a service from the module and has received an error First verify that the module is not faulted For an 1 0 module this may indicate that the module has one of the following conditions e Limited communication is possible but t
17. logic the CPU_scanning bit is always on Getting the Fault Type and Code Enter the following rung in the fault routine for the program GSV Get System Value Clas 1 rame 5 Instance name THIS Program Dew magot_fault recon Tene_Low 0 The GSV instruction e Accesses the MajorFaultRecord attribute of this program This attribute stores information about the fault e Stores the fault information in the major_fault_record of type FAULTRECORD tag When you enter a tag that is based on a structure enter the first member of the tag Rockwell Automation Publication 1756 PM014H EN P November 2015 25 Chapter 1 Major Faults Checking for a Specific Fault Enter the following rung in the fault routine for the program 2 3 CPUL_ scanning EQU WU ft Equal E qual Source 4 major tault_ record ype Source 4 major tault_recond Code je je Source B 4 Source B 2l CLA LF Llear Dest major fault record LCode je Clear Dest major fault record Type a During prescan the bits of all OTE instructions are off and this instruction is true Once the controller begins to run the logic this instruction is always false Item Description The first EQU instruction checks for a fault of type 4 which means that an instruction in this program caused the fault The second EQU instruction checks for a fault of code 20 which means that either an array subscript is too large or a POS or LEN
18. provides a system defined re initialization of the logic invoked from an SFC action when the action is shut down if SFCs are configured for Automatic Reset If an array index is out of range during prescan the controller could generate a major fault There are a number of ways this could happen the controller loses power encounters a major fault or the project is saved while online Because the user program during prescan and postscan cannot assign values to tags the only Rockwell Automation Publication 1756 PM014H EN P November 2015 11 12 Chapter 1 Major Faults way to correct these issues is to manually initialize the index variables using the Logix Designer application or to write a fault handler to ignore the array faults during prescan To reduce the need for manual intervention the Logix Designer application includes an internal fault handler This handler is only used during prescan and only clears array faults type 4 fault codes of 20 of 83 Tip Array faults are not ignored during postscan because the user program controls index tag values when an action is shut down Rockwell Automation Publication 1756 PM014H EN P November 2015 Major Faults Chapter 1 Placement of Fault Routines You use a fault routine to program logic to take specific action after a fault such as clearing the fault and continuing to run Fault routines can be configured specific to a program controller or to the Power Up Handle
19. result when Disable Keying or Compatible Keying options are used in the module configuration instead of the Exact Match option Despite passing the electronic keying test the module being connected to does not have the same features or settings as the module specified in the 1 0 configuration tree and does not support the connection or service being attempted Check the module in use and verify that it exactly matches the module specified in the 1 0 configuration tree of the Logix Designer application For more information about electronic keying see the user manual for the module you are using 0302 The controller is attempting to set up a connection with the module and has received an error a module in the path has exceeded its communication bandwidth capacity Increase the Requested Packet Interval RPI and reconfigure your network with RSNetWorx software Distribute the load on another bridge module 0303 The controller is attempting to set up a connection with the module and has received an error a module in the path has exceeded its communication bandwidth capacity Distribute the load on another bridge module 0304 The ControlNet module is not scheduled to send data Use RSNetWorx for ControlNet software to schedule or reschedule the ControlNet network 0305 The ControlNet configuration in the controller does not match the configuration in the bridge module This may occur because a ControlNet module was changed after the network was
20. the Source ON N4 Oa 0S WM ony The AHL instruction failed to execute because the serial port is set tono Either handshaking e Change the Control Line setting of the serial port e Delete the AHL instruction Periodic task overlap Make changes such as simplifying programs lengthening the period or Periodic task has not completed before it is time to run again raising the relative priority Event task overlap Make changes such as simplifying programs lengthening the period Event task has not completed before it is time to execute again raising the relative priority or slowing the triggering event Virtual adapter task overlap CompactLogix 1769 L2x and 1769 L3x Increase the RPI for the CompactBus controllers only Virtual adapter has not completed running at the rate specified by the Requested Packet Interval RPI when it executed again Project loaded from nonvolatile memory Unknown error while servicing the serial port Contact Rockwell Automation Technical Support 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 A fault was detected with the DF1 master s poll list such as specifying e Total number of stations is greater than the space in the poll list tag more stations than the size of the file specifying more than 255 st
21. top level Add On Instruction invocation For example assume the Add On Instruction myAoi in Example 2 invokes a nested Add On Instruction my Nested which invokes another nested Add On Instruction inner Furthermore assume that an instruction inside of inner causes a fault If the fault is cleared execution resumes with the MOV the remainder of inner does not execute the remainder of myNested does not execute and the remainder of myAoi does not execute e During prescan e The Logic routine runs in prescan mode e The Prescan routine runs in normal scan mode e During postscan e The Logic routine runs in postscan mode e The Postscan routine runs in normal scan mode If a fault occurs while processing the Logic routine the Add On Instruction aborts the remainder of the Logic routine does not run and the pre scan and post scan routines do not run If the fault is cleared execution resumes at the instruction following the top level Add On Instruction invocation Fault Handling During Prescan and Postscan The behavior of each instruction varies depending on the mode in which it runs true false prescan or postscan For details about what a specific instruction does in each mode see the LogixS000 Controllers General Instructions Reference Manual publication number 1756 RMO003 e Prescan provides a system defined initialization of the user program when the controller is switched from program mode to run mode e Postscan
22. 0117 The connection is to an invalid port or port that is already in use One of these conditions exists e Another controller owns this module and has connected with a Communications Format different than the one chosen by this controller Verify that the Communications Format chosen is identical to that chosen by the first owner controller of the module e The module in use that is the physical module is different than the module specified in the 1 0 configuration tree and is therefore causing the connection or service to fail The fault may occur even when the module passed the electronic keying test This may result when Disable Keying or Compatible Keying options were used in the module configuration instead of the Exact Match option Despite passing the electronic keying test the module being connected to does not have the same features or settings as the module specified in the 1 0 configuration tree and does not support the connection or service being attempted Check the module in use and verify that it exactly matches the module specified in the 1 0 configuration tree of the Logix Designer application For more information about electronic keying see the user manual for the module you are using e The controller may be attempting to connect to a nonexistent tag in a producing controller 0118 An invalid configuration format was used One of these conditions exists e The configuration class specified does not match the class supported by the mod
23. 28 Example Creating a User Defined Major Fault i eseeseeeeeeseessen 29 Maor grea UL 0 earner ere roses EEE 29 Chapter 2 Identifying Minor Paults ctsscitiaatiatiniiecteni esti ian ulin 35 Minor Fault CO des erenn n ceases ie ene tem etn 37 Table of contents 1 0 Fault Codes Index Chapter 3 Indications GF O Faults ornica i AAN VO Fut Code eaaa a E a N Rockwell Automation Publication 1756 PM014H EN P November 2015 Studio 5000 environment Rockwell Automation Publication 1756 PM014H EN P November 2015 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 that you can use to troubleshoot your system 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 refer to the Logix5000 Controllers Common Procedures Programming Manual publication 1756 PMOO1 e The term Logix5000 controller refers to any controller that is based on the Logix5000 operating system The Studio 5000 Automation Engineering amp 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 cont
24. Programming Manual AB Allen Bradley Logix5000 Controllers Major Minor and 1 0 Faults Catalog Numbers 1756 ControlLogix 1756 GuardLogix 1768 Compact GuardLogix 1768 CompactLogix 1769 CompactLogix 1789 SoftLogix PowerFlex with DriveLogix 00 Me beet EERE REE AN Allen Bradley Rockwell Software Automation 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 res
25. a fault routine 1 Open the project in the Logix Designer application 2 Inthe Controller Organizer right click MainProgram and choose Add gt New Routine CNG ORGS ES 3 6 Controller L75_101 W Controller Tags Controller Fault Handler p Power Up Handler Sj Tasks MainTask enerom 5 GR MainProg_GS ry CB Conveyor_Co Unscheduled Pros Motion Groups J Add On Instructions IA Paste Ctrl V T J amp Data Types A New Local Tag Ctr w New Parameter 3 Inthe New Routine dialog box type the name of the routine in the Name field Rockwell Automation Publication 1756 PM014H EN P November 2015 Major Faults Chapter 1 Type B Ladder Diagram In Program Mai P E8 MainProgram Assignment lt none gt 4 optional In the Description field type a description of the routine 5 Onthe Type menu use the default setting Ladder Diagram 6 On the In Program or Phase menu use the default setting MainProgram Tip If you are creating a fault routine for the Power Up Handler or Controller Fault Handler you can specify the program name of either program for the In Program or Phase option 7 On the Assignment menu choose Fault 8 optional Select the Open Routine check box if you want to immediately open the ladder logic program 9 Click OK Changing a Fault Routine Assignment of a Program Complete the following steps to change the routine that is assigned as the fault routine
26. ant module does not have the necessary resources to support the connection Reduce the size or number of connections through this module or add another controller or ControlNet module to the system 0322 A connection point mismatch has occurred Possible causes include the following e Anew connection requested does not match the existing connection Check the controllers that are using the connection and verify that all the configurations are identical e The connection requested is not a listener or a controlling connection type 031E The controller is attempting to connect to a tag in a producing controller and has received an error The controller is attempting to connect to a tag in a producing controller and that tag has already been used by too many consumers Increase the maximum number of consumers on the tag 031F No SC servicing controller connection object was found that corresponds to a symbol instance 0800 No interpretation available 0801 No interpretation available 0814 Invalid connection status information was found FDO1 I O map object attributes were found to be invalid A fault has occurred while clearing memory FD02 No error code is supplied by an 1 0 module to describe an 1 0 fault FD03 The controller is attempting to set up a connection with the module and has received an error this module requires a particular set of connections and connection types and one of those connection types is missing FD04 The module requi
27. ations trying to index past the end of the list or polling the broadcast address STN 255 e Current station pointer is greater than the end of the poll list tag e Total number of stations is greater than 255 e Astation number greater than 254 was encountered The RS232 DFI Master Active Station tag is unspecified Specify a tag to be used for the Active Station Tag in the System Protocol tab of the Controller Properties DF1 slave poll timeout Determine and correct delay for polling The poll watchdog has timed out for slave The master has not polled this controller in the specified amount of time Modem contact was lost Correct modem connection to the controller DCD or DSR control lines are not being received in proper sequence or state Data has been dropped or lost from the serial port Slow down the rate at which the initiator is sending data Battery not detected or needs to be replaced Install a new battery Safety partner battery not detected or needs to be replaced Install a new battery Rockwell Automation Publication 1756 PM014H EN P November 2015 Minor Faults Chapter 2 The ESM of a 1756 L7x controller is not installed Install an ESM in the controller If the controller is powered down the WallClockTime attribute and program are not maintained The ESM installed on the 1756 L7x controller is not compatible with the Replace the installed ESM with one that is compatible with the controller
28. ccurs outside a safety task Place the safety instruction inside the safety task Equipment Phase instruction is being called from outside an Only use the instruction in an Equipment Phase program Equipment Phase program User defined major faults See Creating a User Defined Major Fault on page 27 for more information 84 91 991 992 Oo O 00 O O 4 5 O O Rockwell Automation Publication 1756 PM014H EN P November 2015 Type 4 4 4 6 11 11 11 11 11 11 11 11 11 Major Faults Chapter 1 Task watchdog expired Take one or more of these steps User task has not completed in the specified period A program e Increase the task watchdog error caused an infinite loop or the program is too complex to run as quickly as specified or a higher priority task is keeping this task from finishing e Make the priority of this task higher e Shorten the execution time e Simplify higher priority tasks e Move some code to another controller Store to nonvolatile memory failed 1 Try again to store the project to nonvolatile memory 2 Ifthe project fails to store to nonvolatile memory replace the memory card If you are using a 1756 L7x controller verify that the SD card is unlocked A Load from nonvolatile memory failed due to controller type Change to a controller of the correct type or download the project and store it on the mismatch memory card A N Load from nonv
29. cted to does not have the same features or settings as the module specified in the 1 0 configuration tree and does not support the connection or service being attempted Check the module in use and verify that it exactly matches the module specified in the 1 0 configuration tree of the Logix Designer application For more information about electronic keying see the user manual for the module you are using FE06 The input force pointer has not been set FEO7 The output connection point has not been set FEO8 The controller is attempting to set up a connection with the module and has received an error Rockwell Automation Publication 1756 PM014H EN P November 2015 49 Chapter 3 1 0 Fault Codes Code Interpretation FEO9 Possible causes include the following e The controller is attempting to set up a connection with the module and has received an error e The module in use that is the physical module is different than the module specified in the 1 0 configuration tree and is therefore causing the connection or service to fail The fault may occur even when the module passes the electronic keying test This may result when Disable Keying or Compatible Keying options are used in the module configuration instead of the Exact Match option Despite passing the electronic keying test the module being connected to does not have the same features or settings as the module specified in the 1 0 configuration tree and does not support the con
30. e is l New Routine Ex Name Routine _Fault_Handler_1 Description 2 ian Type BB Ladder Diagram Help In Progran ne ese E8 PowerUp_Program_1 x Assignment Main m Open Routine 6 In the Assignment field use the default setting Main Tip Even though you can choose Fault in the Assignment field assigning the routine as a fault routine within the Controller Fault Handler is not necessary 7 Click OK The fault routine is created in the Controller Fault Handler program If you want to edit the fault routine double click it to open it 3 Controller L75_101 I Controller Tags 53 6 Controller Fault Handler a Program_for_Fault_Handler_1 I Parameters and Local Tags EE Routine_Fault_Handler_1 Creating a Routine for the The Power Up Handler is an optional task that executes when the controller Power Up Handler powers up in Run or Remote Run modes To Do this Prevent the controller from returning to Run or Leave the routine for the Power Up Handler empty When Remote mode power is restored a major fault type 1 code 1 occurs and the controller enters the faulted state Direct the controller to take specific actions then In the Power Up Handler fault routine complete these steps resume normal operation when power is restored 1 Clear the major fault type 1 code 1 2 Run the appropriate logic for the specific actions required Important Do not use fault routines to continually clear all faults o
31. ed Reconfigure the number of communication modules on the 1768 bus side of the CompactLogix 1768 L4x controllers only controller ony e 1768 L43 has a maximum of two modules e 1768 L45 has a maximum of four modules that can include up to e Four Sercos modules Two NetLinx communication modules If the controller uses a battery the battery does not contain For controllers that use a battery replace the battery enough charge to save the user program on power down For controllers that use an ESM Energy Storage Module If the controller uses an ESM Energy Storage Module the ESM e Allow the ESM to fully charge before powering down the controller does not contain enough charge to save the user program on power down e Replace the ESM if the ESM is removable or replace the controller if the ESM is not removable e fthe problem persists contact Rockwell Automation Technical Support For a controller with no memory card installed the controller 1 Clear the fault e Detected a non recoverable fault 2 Download the project e Cleared the project from memory 3 Change to Remote Run or Run mode Follow these steps if the fault persists 1 Before you cycle power to the controller record the state of the OK and RS232 status indicators 2 Contact Rockwell Automation Technical Support 61 For a controller with a memory card installed the controller 1 Clear the fault e Detected a non recoverable fault
32. em Belgium Tel 32 2 663 0600 Fax 32 2 663 0640 Asia Pacihe Rockwell Automation Level 14 Core F Cyberport 3 100 Cyberport Road Hong Kong Tel 852 2887 4788 Fax 852 2508 1846 Rockwell Automation Publication 1756 PM014H EN P November 2015 Supersedes Publication 1756 PM014G EN P July 2014 Copyright 2015 Rockwell Automation Inc All rights reserved Printed in the U S A
33. en an instruction generates an error due to a fault for example a COP with an indirect addressing programming error the instruction is skipped and does not run This occurs with all instructions Creating a Data Type to Store Fault Information Logix5000 controllers store system information in objects Unlike PLC 5 or SLC 500 controllers there is no status file e To access system information use a Get System Value GSV or Set System Value SSV instruction e For status information about a program access the PROGRAM object e For fault information access the attribute of the PROGRAM object Attribute Data Type Instruction Description MajorFaultRecord DINT 11 Records major faults for this program Specifies the program name to determine which PROGRAM object you want or specifies THIS to access the PROGRAM object for the program that contains the GSV or SSV instruction To simplify access to the MajorFaultRecord attribute complete these steps to create a user defined data type Rockwell Automation Publication 1756 PM014H EN P November 2015 21 Chapter 1 Major Faults 1 Inthe Controller Organizer right click User Defined and choose New Data Type Motion Groups a Add On Instructions H S Data Types Og CR Strings a New Data Type E Add On Defin Import Data Type m E Predefined a E Module Define X Cut Ctr 2 On the New Data Type window enter the data type information as
34. he module has a Major Fault e A firmware update needs to be completed or is currently being completed Refer to the Module Info tab to determine the exact cause 000D An 0 map instance is created where the instance is already in use 000E A MSG instruction is configured to change an attribute that cannot be changed 000F A MSG instruction has been configured to delete a map object that cannot be deleted 0010 The state of the device prevents a service request from being handled 0011 The reply to a message has a data size that is too large for the destination Change the destination to a tag that can handle the data size and type being returned 0013 The configuration for the module is invalid Not enough configuration data was sent Verify that the correct module is being targeted Rockwell Automation Publication 1756 PM014H EN P November 2015 43 Chapter 3 1 0 Fault Codes Code Interpretation 0014 A MSG instruction is configured to change an attribute that does not exist 0015 The configuration for the module is invalid Too much configuration data was sent Verify that the correct module is being targeted 0100 The connection being accessed is already in use Possible causes include the following e The controller is attempting to make a specific connection to a module and the module cannot support more than one of these connections e The target of a connection recognizes that the owner is attempting to remake a connection that
35. he user manual for the module you are using If the module is a 1756 ControlNet module verify that the chassis size is correct For remote 1 0 adapters verify that the rack size and rack density is correct 0110 The controller is attempting to set up a Listen Only connection with the module and cannot because the module has not been configured and connected to by an Owner for example another controller This controller is not an Owner of this module because it is attempting to establish a Listen Only connection which requires no module configuration It cannot connect until an Owner configures and connects to the module first 0111 Possible causes include the following e The Requested Packet Interval RPI specified is invalid for this module or for a module in the path to this module e The module in use that is the physical module is different than the module specified in the 1 0 configuration tree and is therefore causing the connection or service to fail The fault may occur even when the module passes the electronic keying test This may result when Disable Keying or Compatible Keying options are used in the module configuration instead of the Exact Match option Despite passing the electronic keying test the module being connected to does not have the same features or settings as the module specified in the 1 0 configuration tree and does not support the connection or service being attempted Check the module in use and verify that i
36. lf that does not work pull the servo module out and plug it back in e lf this does not work replace the servo module Servo module has detected a serious hardware fault Replace the module Configuration fault has occurred See the AttributeErrorCode or AttributeErrorlD axis tags to identify which attribute was The motion module or drive rejected the update of one of the rejected and why axis attributes Motor fault has occurred See the DriveFaults axis tag for more information fe Motor thermal fault has occurred See the DriveFaults axis tag for more information Drive thermal fault has occurred See the DriveFaults axis tag for more information SERCOS ring fault has occurred Verify the integrity of the SERCOS fiber optic ring network and the devices on it Rockwell Automation Publication 1756 PM014H EN P November 2015 31 Chapter 1 Type 11 11 11 11 12 12 12 14 14 14 14 14 14 14 14 14 17 32 Major Faults Code Recovery Method Re enable the drive enable input and clear the fault Restore full power connection to the drive and clear the fault See the GuardFaults axis tag for more information The group s course update rate is too high to maintain correct operation Clear the group fault tag raise the group s update rate and then clear the major fault A disqualified secondary controller cycled power and no Verify the following items partner chassis or cont
37. lt is applicable only when a drive with Guard Safety functionality is used Rockwell Automation Publication 1756 PM014H EN P November 2015 Major Faults Chapter 1 To determine corrective action see the CIP Initialization attribute for details about the type of fault that occurred For more information about the CIP Initialization attribute see the Integrated Motion on the Ethernet IP Network Configuration and Startup User Manual publication MOTION UM003 To determine the corrective action see the CIP Initialization Fault Mfg attributes for details about the fault that occurred For more information about the CIP Initialization Fault Mfg attribute see the Integrated Motion on the Ethernet IP Network Configuration and Startup User Manual publication MOTION UM003 To determine corrective action see the CIP Axis Fault attributes for details about the fault that occurred For more information about the CIP Axis Fault attributes see the Integrated Motion on the Ethernet IP Network Configuration and Startup User Manual publication MOTION UM003 To determine corrective action see the CIP Axis Fault Mfg attributes for details about the fault that occurred For more information about the CIP Axis Fault Mfg attributes see the Integrated Motion on the Ethernet IP Network Configuration and Startup User Manual publication MOTION UM003 To determine corrective action see the Motion Fault attribute and Motion Fault bits f
38. m does not run when the main tasks and associated programs run For example if your fault handler skips a JSR instruction that is causing a major fault then that JSR instruction including all of the programming within the subroutine does not run When an instruction generates an error due to a fault for example a COP with an indirect addressing programming error the instruction is skipped and does not run This occurs with all instructions l In the Controller Organizer right click Controller Fault Handler and choose New Program Controller L75_101 A Controller Tags On the New Program dialog box in the Name field enter a program name Verify that the Schedule in field is set to Controller Fault Handler Use as Folder Schedule In Inhibit Program Synchronize Redundancy Data after Execution Open Properties Click OK In the Controller Organizer right click the program you created in step 2 and choose Add gt New Routine amp j Controller 175 101 J Controller Tags 5 Controller Fault Handler Cee Br gram for Faul f 3 GS Power Up Handler de HA New Routir N H E Tasks E Motion Groups E Add On Instructions E Data Types G Trends A NewLocalTag Ctri W New Parameter Import Routine Rockwell Automation Publication 1756 PM014H EN P November 2015 17 Chapter 1 Major Faults 5 On the New Routine dialog box in the Name field enter a name for the routin
39. mation Publication 1756 PM014H EN P November 2015 53 Index clear a major fault 24 program create fault routine 14 recovering from a major fault 9 important points regarding Add On Instructions 9 routine 14 create fault 14 Fault Handler 16 Power Up Handler create 18 S shut down the controller 27 status controller in RSLogix 5000 41 store faults create data type 21 suspend controller 27 T test a fault routine 26 W warning lowbattery 35 54 Rockwell Automation Publication 1756 PM014H EN P November 2015 Rockwell Automation support Rockwell Automation provides technical information on the web to assist you in using its products At hetp www rockwellautomation com support you can find technical and application notes sample code and links to software service packs You can also visit our Support Center at https rockwellautomation custhelp com for software updates support chats and forums technical information FAQs and to sign up for product notification updates In addition we offer multiple support programs for installation configuration and troubleshooting For more information contact your local distributor or Rockwell Automation representative or visit http www rockwellautomation com services online phone Installation assistance If you experience a problem within the first 24 hours of installation review the information that is contained in this manual You can contact Customer
40. 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 gt D gt Allen Bradley Rockwell Software Rockwell Automation and TechConnect are trademarks of Rockwell Automation Inc Trademarks not belonging to Rockwell Automation are property of their respective companies Summary of Changes This manual contains new and updated information The following table contains the changes made to this revision Topic Page Added Controller internal temperature is approaching operating limit to the list of Minor Fault Codes on page 37 minor fault codes Added Controller internal temperature has exceeded operating limit to the list of Major Fault Codes on page 29 major fault codes Rockwell Automation Publication 1756 PM014H EN P November 2015 3 Preface Major Faults Minor Faults Rockwell Automation Publication 1756 PM014H EN P November 2015 Table of contents Studio S000 environ MeN seeni tacos cine estan meet emda dunes 7 Additonal Resource Seniste ae NE AE A E i 8 Chapter 1 Major Falera te eno TAE E O E 9 Recovering From 4 Major FaUl tranne nr EROA 9 Important Points Regarding Add On Instructions 11 Fault Handling During Prescan and Postscan sssssssesssssessssssreersrsessserereeen 11 Placement of Fault Routines
41. n the controller Program the fault routine to be selective in the types and number of faults cleared 18 Rockwell Automation Publication 1756 PM014H EN P November 2015 Major Faults Chapter 1 Important When an instruction generates an error due to a fault for example a COP with an indirect addressing programming error the instruction is skipped and does not run This occurs with all instructions Complete the following steps to create a fault routine for the Power Up Handler in the Logix Designer application 1 Inthe Controller Organizer right click Power Up Handler and choose New Program 3 Controller L 75_101 A Controller Tags Controller Fault Handler Tasks sS 2 On the New Program dialog box in the Name field type a program name fi New Program Name PowerUp_Program_1 Lise as Folder Schedule In Power Up Handler Synchronize Redundancy Data after Execution C Open Properties 3 Click OK The program is added to the Power Up Handler a Controller L75_101 A Controller Tags E Controller Fault Handler Power Up Handler m P 0 weno p_Prog ram _ Rockwell Automation Publication 1756 PM014H EN P November 2015 19 Chapter 1 Major Faults 4 Right click the program you created in step 2 and choose 5 6 Add gt New Routine S Controller L75_101 A Controller Tags E Controller Fault Handler S E Power Up Handler Program l pA Tasks 3
42. nd fault status and continue FF01 The controller is attempting to set up a connection with the module and has received an error Verify that the path to this module is a valid length FF04 The controller s map instance attempted to access a connection while in an invalid state FFO8 The controller is attempting to set up a connection with the module and has received an error Verify that the path to this module is a valid length 50 Rockwell Automation Publication 1756 PM014H EN P November 2015 I 0 Fault Codes Chapter 3 Code Interpretation FFOB Possible causes include the following e The configuration for the module is invalid e The module in use that is the physical module is different than the module specified in the 1 0 configuration tree and is therefore causing the connection or service to fail The fault may occur even when the module passes the electronic keying test This may result when Disable Keying or Compatible Keying options are used in the module configuration instead of the Exact Match option Despite passing the electronic keying test the module being connected to does not have the same features or settings as the module specified in the 1 0 configuration tree and does not support the connection or service being attempted Check the module in use and verify that it exactly matches the module specified in the 1 0 configuration tree of the Logix Designer application For more information about electronic keyi
43. nection or service being attempted Check the module in use and verify that it exactly matches the module specified in the 1 0 configuration tree of the Logix Designer application For more information about electronic keying see the user manual for the module you are using FEOA A connection has been opened without the output force pointer being set FEOB Possible causes include the following e The tag to be consumed on this module is invalid Verify that the tag is marked as being produced e The module in use that is the physical module is different than the module specified in the 1 0 configuration tree and is therefore causing the connection or service to fail The fault may occur even when the module passes the electronic keying test This may result when Disable Keying or Compatible Keying options are used in the module configuration instead of the Exact Match option Despite passing the electronic keying test the module being connected to does not have the same features or settings as the module specified in the 1 0 configuration tree and does not support the connection or service being attempted Check the module in use and verify that it exactly matches the module specified in the 1 0 configuration tree of the Logix Designer application For more information about electronic keying see the user manual for the module you are using FEOC The controller is attempting to set up a connection with the PLC 5 controller and has received
44. ng see the user manual for the module you are using FFOE The controller is attempting to set up a connection with the module and has received an error Rockwell Automation Publication 1756 PM014H EN P November 2015 51 1756 L2x 1 0 fault indicator 41 1756 L6x 1 0 fault indicator 41 check specific fault 25 CIP Motion major fault codes 28 clear major fault 9 20 codes 1 0 faults 41 42 major fault 28 minor fault 37 controller shut down 27 status in RSLogix 5000 41 suspend 27 when in prescan 24 create data type store fault information 21 fault routine 14 routine for Fault Handler 16 routine for Power Up Handler 18 fault clear 9 codes 1 0 42 codes major 28 codes minor 37 create user defined 27 develop routine to clear fault 9 during prescan 24 1 0 42 indirect address 24 monitor minor 35 Index routine create 14 shown in Module Properties 41 test a fault routine 26 Fault Handler create routine 16 fault handling during prescan and postscan 11 0 42 configuration warning 41 1 0 faults indication of 41 indicator I O fault 41 indirect address 24 instruction causing minor fault 35 L low battery warning 35 M major fault codes 28 create user defined 27 develop fault routine 9 how to cleare 20 major faults CIP Motion 28 minor fault codes 37 logic 35 Module Properties faultin 41 motion major faults 28 P Power Up Handler create a routine 18 prescan Rockwell Auto
45. nnected to the module with a Unicast connection over EtherNet IP network other connections to the module may fail because the Owner controls the one connection If the Owner is connected to the module with a Multicast connection over EtherNet IP network Unicast connections to the module may fail because the Owner controls the one connection Configure both the Owner and the Listen Only connection as Multicast 0107 A connection being accessed was not found 0108 An invalid connection type was used One of the following conditions exists e The controller is requesting a connection type not supported by the module e The module in use that is the physical module is different than the module specified in the 1 0 configuration tree and is therefore causing the connection or service to fail e The fault may occur even when the module passes the electronic keying test This may result when Disable Keying or Compatible Keying options are used in the module configuration instead of the Exact Match option Despite passing the electronic keying test the module being connected to does not have the same features or settings as the module specified in the 1 0 configuration tree and does not support the connection or service being attempted Check the module in use and verify that it matches the module specified in the 1 0 configuration tree of the Logix Designer application For more information about electronic keying see the user manual for the module you are u
46. not have the same features or settings as the module specified in the 1 0 configuration tree and does not support the connection or service being attempted Check the module in use and verify that it exactly matches the module specified in the 1 0 configuration tree of Logix Designer application For more information about electronic keying see the user manual for the module you are using If you are using a 1756 DHRIO module verify that the Channel type selected in the software DH or remote 1 0 network matches the module s rotary switch settings 0006 Possible causes include the following e The response buffer is too small to handle the response data e The module in use that is the physical module is different than the module specified in the 1 0 configuration tree and is therefore causing the connection or service to fail The fault may occur even when the module passed the electronic keying test This may result when Disable Keying or Compatible Keying options were used in the module configuration instead of the Exact Match option Despite passing the electronic keying test the module being connected to does not have the same features or settings as the module specified in the 1 0 configuration tree and does not support the connection or service being attempted Check the module in use and verify that it exactly matches the module specified in the 1 0 configuration tree of Logix Designer application For more information about electronic
47. nstruction choose the data type 3 Monitor S MINOR 4 Use a GSV instruction to get the values of the MinorFaultRecord attribute if S MINOR is on 5 Reset S MINOR if you want to detect a minor fault that is cause by another instruction S MINOR remains set until the end of the scan Rockwell Automation Publication 1756 PM014H EN P November 2015 35 Chapter 2 Minor Faults The following 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 minor fault check ON TOR Timer On Delay Timer minor fault check Preset BOOUL e Accum 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 runs once every minute the scan time of most scans is reduced Gov Get System Value Class name FaultLog Instance name Attribute Name Minot aultB its Dest minor fault bits minor fault check ON If minor_fault_bits 10 is on the battery is low or there is an ESM minor fault minor fault bits 10 bathery low warring The following example checks for a minor fault that is caused by a specific instruction Example Check for a minor fault that is caused by an instruction e Multiply value_a by 1000000 and check for a minor fault
48. odule is different than the module specified in the 1 0 configuration tree and is therefore causing the connection or service to fail The fault may occur even when the module passes the electronic keying test This may result when Disable Keying or Compatible Keying options are used in the module configuration instead of the Exact Match option Despite passing the electronic keying test the module being connected to does not have the same features or settings as the module specified in the 1 0 configuration tree and does not support the connection or service being attempted Check the module in use and verify that it exactly matches the module specified in the 1 0 configuration tree of the Logix Designer application For more information about electronic keying see the user manual for the module you are using 0206 Possible causes include the following e The controller is attempting to set up a connection with the module and has received an error the request size is too large Verify that the path to this module is sufficiently close to the controller e The module in use that is the physical module is different than the module specified in the 1 0 configuration tree and is therefore causing the connection or service to fail The fault may occur even when the module passes the electronic keying test This may result when Disable Keying or Compatible Keying options are used in the module configuration instead of the Exact Match option Des
49. ogram Mode E Controller OK No Forces P No Edits sf ery ai e I 1 0 Not Responding Redundancy il 41 Chapter 3 1 0 Fault Codes e A yellow warning symbol appears on the module in the I O Configuration tree of the Logix Designer application Ga I O Configuration amp 1756 Backplane 1756 410 Ph 2 1756 IF 6 analog_input fI 7 1756 L75 10_control P 8 1756 OB16D digital_output e A module fault code and description appear in the Connection tab of the Module Properties dialog box m Module Properties Locak8 1756 08160 3 1 r General Connection Module Info Configuration Diagnostics Pulse Test Backplane Requested Packet Interval RPI 2 1014 ms 02 7500 ms Inhibit Module Major Fault On Controller If Connection Fails While in Run Mode f Module Fault J Code 1640116 Electronic Keying Mismatch Major and or Minor revision invald of incorrect Status Faulted 1 0 Fault Codes Depending i the fault code is indicated the code format contains either the full Hexadecimal number for example 16 000A or the last characters of the code for example 000A The following table lists common I O fault codes and a corresponding description and recovery method when applicable Each code is listed by the last characters of the full Hexadecimal number that is X XXX Code Interpretation 0001 A connection to a module failed 0002 Possible causes include the following e There are no
50. olatile memory failed because the firmware Update the controller firmware to the same revision level as the project that is in revision of the project in nonvolatile memory does not match nonvolatile memory the firmware revision of the controller Load from nonvolatile memory failed due to bad checksum Contact Rockwell Automation Technical Support Failed to restore processor memory Contact Rockwell Automation Technical Support Attempted to place controller in Run mode with keyswitch Wait for the download to complete and clear the fault during download Actual position has exceeded positive overtravel limit Move axis in negative direction until position is within overtravel limit and then execute Motion Axis Fault Reset Actual position has exceeded negative overtravel limit Move axis in positive direction until position is within overtravel limit and then run Motion Axis Fault Reset Actual position has exceeded position error tolerance Move the position within tolerance then run Motion Axis Fault Reset Encoder channel A B or Z connection is broken Reconnect the encoder channel then run Motion Axis Fault Reset Encoder noise event detected or the encoder signals are notin Fix encoder cabling then run Motion Axis Fault Reset quadrature Drive Fault input was activated Clear Drive Fault then run Motion Axis Fault Reset Synchronous connection incurred a failure Try these steps e First run Motion Axis Fault Reset e
51. or details about the fault that occurred For more information about the Motion Fault attribute and Motion Fault bits see the Integrated Motion on the Ethernet IP Network Configuration and Startup User Manual publication MOTION UM003 Reconfigure the faulted motion module to correct the fault For more information about the Module Fault attribute and Module Fault bits see the Integrated Motion on the Ethernet IP Network Configuration and Startup User Manual publication MOTION UM003 Reconfigure the entire motion subsystem to correct the fault See the Group Fault attribute if details about the fault are needed To determine the corrective action see the Configuration Fault in the Attribute Error Code and Attribute Error ID attributes associated with the motion or 1756 ENxT module To determine the corrective action see the APR Fault attributes to determine the cause of the fault For more information about the APR Fault attributes see the Integrated Motion on the Ethernet IP Network Configuration and Startup User Manual publication MOTION UM003 To determine the corrective action see the APR Fault Mfg attributes to determine the cause of the fault For more information about the APR Fault Mfg attributes see the Integrated Motion on the Ethernet IP Network Configuration and Startup User Manual publication MOTION UM003 To determine the corrective action see the Guard Motion attributes and Guard Status bits to determine
52. or fault occurs and the controller executes Fault_ Routine JSR a Jump to Subroutine Routine name Fault Rectae test_fault_routine Creating a User Defined If you want to suspend shut down the controller based on conditions in your Major Fault application create a user defined major fault With a user defined major fault e The fault type 4 e You define a value for the fault code Choose a value between 990 and 999 These codes are reserved for user defined faults e The controller handles the fault the same as other major faults e The controller changes to the Program mode and stops running the logic e Outputs are set to their configured state or value for faulted mode Example When Tag_1 0 1 produce a major fault and generate a fault code of 999 See the following procedures to create a user defined major fault e Creating a Fault Routine for the Program on page 28 Rockwell Automation Publication 1756 PM014H EN P November 2015 27 Chapter 1 Major Faults e Configuring the Program to Use the Fault Routine on page 28 e Jumping to the Fault Routine on page 28 Creating a Fault Routine for the Program If a program already contains a fault routine see Jumping to the Fault Routine on page 28 If a program does not contain a fault routine complete these steps to add one 1 Inthe Controller Organizer right click the program and choose New Routine 2 Inthe Name field type a name for the faul
53. ow from finishing or the safety partner has been removed the safety task to run e Reinsert the safety partner if it was removed 2 Correct the error in the user program logic 3 Install a compatible safety partner 4 Install a compatible safety partner 5 Install a compatible safety partner Safety partner firmware is incompatible Update the safety partner so that the firmware major and minor revision matches the primary controller Safety task is inoperable e Clear the fault This fault occurs when the safety logic is invalid For example a e If a safety task signature exists safety memory is re initialized via the safety task mismatch in logix exists between the primary controller and signature and the safety task begins executing safety partner a watchdog timeout occurred or memory is e Ifa safety task signature does not exist you must download the program again to allow the safety task to run corrupt Coordinated system time CST not found Clear the fault Configure a device to be the CST master Safety partner nonrecoverable controller fault Clear the fault and download the program If the fault persists replace the safety partner 34 Controller internal temperature has exceeded operating limit Measures should be taken to reduce the ambient temperature of the module Follow the recommended limits for the ambient inlet temperature and apply the required clearance around the chassis Rockwell
54. pite passing the electronic keying test the module being connected to does not have the same features or settings as the module specified in the 1 0 configuration tree and does not support the connection or service being attempted Check the module in use and verify that it exactly matches the module specified in the 1 0 configuration tree of the Logix Designer application For more information about electronic keying see the user manual for the module you are using 0301 One of these conditions may exist e The controller is attempting to set up a connection with the module and has received an error a module in the path is out of memory e The controller may be attempting to connect to a tag in a producing controller that is not marked as being produced e The controller may be attempting to connect to a tag in a producing controller That tag may not be configured to allow enough consumers e The size or number of connections through this module needs to be reduced e One of the network modules between the module and the controller may be out of memory Check network configuration of the system e The module may be out of memory Check the system configuration and capabilities of the module e The module in use that is the physical module is different than the module specified in the 1 0 configuration tree and is therefore causing the connection or service to fail The fault may occur even when the module passes the electronic keying test This may
55. ponsibility 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 AN A 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
56. r ProgramFaultRoutine a Tasks amp 4 MainTask 28 MainProgram 3 A Parameters and Local Tags EB MainRoutine B Alt_Fault_Routine B Fault_Routine_1 Other_Routine Controller FaultRoutine Sj Controller Controller_L75_101 JA Controller Tags E Controller Fault Handler B 33 Program_for_Fault_Handler_1 Oo A Parameters and Local Tags gt E Fault_Handler_Routine_1 Power upFaultHandler Routine 3 6 Controller Controller L75 101 1 Controller Tags E Controller Fault Handler 3 6 Power Up Handler amp PowerUp_ Program_1 Parameters and Local Tags ae Ef PowerUp_Program_1 Rockwell Automation Publication 1756 PM014H EN P November 2015 13 Chapter 1 Major Faults Creating a Fault Routine for a Program 14 Choosing Where to Place the Fault Routine Where you place the routine depends on the type of fault that you want to handle Use this table to determine where in the project your fault routine should be configured If you want to clear the fault when See this section Condition The execution of an instruction faults Creating a Fault Routine for a Program on page 14 Communication with an 1 0 module fails Creating a Routine for the Controller Fault Watchdog timer for a task expires eS Handler on pase 1p A motion axis faults mo The controller powers up in Run or Remote Run mode rl Creating a Routine for the Power Up Handler on page 18 Complete the following steps to create
57. r only one controller can make a Rack Optimization connection to the module Verify that this number has not been exceeded 0203 The owner or originator recognizes that the target device is on the network or backplane However 1 0 data and messages are not being responded to In other words the target can be reached but its response is not as expected For example this fault may be indicated where multicast Ethernet packets are not returned When this fault occurs the controller usually attempts to continuously remove and remake the connection If you use FLEX 1 0 modules verify that you are using the correct terminal device 0204 The controller is attempting to make a connection however the target module is not responding The device also appears to be missing from the backplane or network To recover take the following steps e Verify that the module has not been removed and is still functioning and receiving power e Verify that the correct slot number has been specified e Verify that the module is properly connected to the network If you are using FLEX 1 0 modules verify that the correct terminal block is in use 46 Rockwell Automation Publication 1756 PM014H EN P November 2015 I 0 Fault Codes Chapter 3 Code Interpretation 0205 Possible causes include the following e The controller is attempting to set up a connection with the module and has received an error a parameter is in error e The module in use that is the physical m
58. res a Coordinated System Time CST master in the chassis Configure a module typically a controller in this chassis to be the CST master 48 Rockwell Automation Publication 1756 PM014H EN P November 2015 I 0 Fault Codes Chapter 3 Code Interpretation FDO5 The module requires an assigned axis or group table Assign a Group or Axis FD06 The controller command to transition the SERCOS ring to a new phase returned an error from the module Check for duplicate Drive Nodes FDO7 An attempt to configure the SERCOS ring failed The baud rate for all devices must be the same and supported by the drives and the SERCOS module FD08 Mainly two sets of faults may cause this fault physical and interface faults Possible sources of physical faults include the following conditions e Broken ring e Loose connector e Fiber optics not clean e Electrical noise due to improper drive grounding e Too many nodes on the ring e Interface errors are encountered when you are configuring third party drives Potential interface errors include the following No SERCOS MST Protocol Error e Missed AT drive did not send data when expected e SERCOS timing error in phase 3 Error in drive data returned to SERCOS module FD09 An attempt by the controller to configure the node for cyclic operation returned an error FDOA A bad response was received from a motion module FD1F An error occurred adding the safety network segment to a route FD20 No
59. roller was found upon powerup e A partner chassis is connected 14 15 16 2 3 ww N _ Ww gt e Power is applied to both redundant chassis e Partner controllers have the same e Catalog number e Slot number o Firmware revision UY Ww An unpartnered controller has been identified in the new Either primary chassis after a switchover e Remove the unpartnered controller and troubleshoot the cause of the switch over e Adda partner controller to the secondary chassis troubleshoot the cause of the switch over and synchronize the system Just after a switchover occurs the keyswitch positions of the Either primary and secondary controllers are mismatched e Change the keyswitches from Run to Program to Run mode twice to clear the fault The old primary controller is in Program mode and the new al oR r e Use the Logix Designer application to go online with the controllers Then clear the primary controller is in Run mode faults and change the mode on both controllers to Run Safety Task watchdog expired e Clear the fault User task has not completed in a specified period A program e Ifa safety task signature exists safety memory is re initialized and the safety task error caused an infinite loop the program is too complex to run begins executing as quickly as specified a higher priority task is keeping this task eee e fa safety task signature does not exist you must re download the program to all
60. rollers for discrete process batch motion safety and drive based solutions Rockwell Software Studio 5000 Create Open xplore New Project Existing Project Help From Import Sample Project Release Notes fom Sample Project From Upload About Recent Projects B PIO_Destinstion2L75 ay AppFrame_TestwareL75 a SampleOnEventStopc 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 Additional Resources These documents contain additional information concerning related products from Rockwell Automation Resource Description Industrial Automation Wiring and Grounding Guidelines Provides general guidelines for installing a Rockwell publication 1770 4 1 Automation industrial system Product Certifications website http www ab com Provides declarations of conformity certificates and other certification details You can view or download publications at http www rockwellautomation com literature To order paper copies of technical documentation contact your local Allen Bradley distributor or Rockwell Automation sales representative Rockwell Automation Publication 1756 PM014H EN P November 2015 Chapter 1 Major Fault State Major Faults This chapter explains major fault codes and how to
61. safety task appears to be running FD22 Verify the number of physical expansion 1 0 modules configured for the controller and then update the number of modules selected from the Expansion 1 0 list on the General page in the Controller Properties dialog FD23 To verify the number of physical expansion 1 0 the controller supports open the Controller Properties dialog and expand the Expansion 1 0 list on the General page Configure the number of physical expansion 1 0 modules to match the selection in the Expansion 1 0 list FE01 An invalid configuration format was encountered FE02 The Requested Packet Interval RPI specified is invalid for this module See the Connection tab for valid RPI values FE03 The input connection point has not been set FE04 The controller is attempting to set up a connection with the module and has received an error FE05 Possible causes include the following e The controller is attempting to set up a connection with the module and has received an error e The module in use that is the physical module is different than the module specified in the 1 0 configuration tree and is therefore causing the connection or service to fail The fault may occur even when the module passes the electronic keying test This may result when Disable Keying or Compatible Keying options are used in the module configuration instead of the Exact Match option Despite passing the electronic keying test the module being conne
62. scheduled or because a new control program has been loaded into the controller Use RSNetWorx for ControlNet software to reschedule the connections Rockwell Automation Publication 1756 PM014H EN P November 2015 47 Chapter 3 1 0 Fault Codes Code Interpretation 0306 The ControlNet Configuration Master CCM cannot be found The 1756 CNB module and PLC 5 ControlNet processor are the only devices capable of being a CCM and the CCM must be node 1 Verify that a 1756 CNB modules or PLC 5 ControlNet processor is at node 1 and is functioning properly This fault may temporarily occur when the system is powered up and is being cleared when the CCM is located 0311 The controller is attempting to set up a connection with the module and has received an error Verify that all modules in the 1 0 Configuration tree are the correct modules 0312 The controller is attempting to set up a connection with the module and has received an error an invalid link address has been specified A link address can be a slot number a network address or the remote 1 0 chassis number and starting group Verify that the chosen slot number for this module is not greater than the size of the rack Verify that the ControlNet node number is not greater than the maximum node number configured for the network in RSNetWorx for ControlNet software 0315 The segment type or route is invalid Possible causes include the following e The controller is attempting to set up a connection
63. shown in the following table lt gt a E 7 B pea La a gt Data Type Sime 77 Properties Extended Properties Description E General oF Desenption Member Adee Name il Data Type FAULTRECORD Name FAULTRECORD Description Stores the MajorFaultRecord attribute or MinorFaultRecord attribute of the PROGRAM object Members Name Description Time_Low Lower 32 bits of the fault timestamp value Time_High Upper 32 bits of the fault timestamp value Type Fault type program 1 0 and so forth Code Unique code for the fault Info Fault specific information 3 Click OK 22 Rockwell Automation Publication 1756 PM014H EN P November 2015 Major Faults Chapter 1 Getting the Fault Type and Code Enter the following rung in the fault routine for the program SV Get System Value Class name Instance name Program THIS Altibute Name Valor autRecord Den mao lat record Tma _Low oel The GSV instruction e Accesses the MajorFaultRecord attribute of this program This attribute stores information about the fault e Stores the fault information in the major_fault_record of type FAULTRECORD tag When you enter a tag that is based on a structure enter the first member of the tag Checking for a Specific Fault EQU EQU Equal 1 Equal ource A weajor_Ffault_record Type Source A msjor_fault_record code 0 0 Source B fault_type Source H fault_code Move
64. sing e You have configured a consumed tag or module to use a Unicast connection over EtherNet IP network but the producer does not support Unicast connections 44 Rockwell Automation Publication 1756 PM014H EN P November 2015 I 0 Fault Codes Chapter 3 Code Interpretation 0109 The connection size is inconsistent with the expected size Possible causes include the following e The controller is attempting to set up a connection with the module and cannot because the size of the connection is invalid e The controller may be attempting to connect to a tag in a producing controller whose size does not match the tag in this controller e The module in use that is the physical module is different than the module specified in the 1 0 configuration tree and is therefore causing the connection or service to fail e The fault may occur even when the module passed the electronic keying test This may result when Disable Keying or Compatible Keying options were used in the module configuration instead of the Exact Match option Despite passing the electronic keying test the module being connected to does not have the same features or settings as the module specified in the 1 0 configuration tree and does not support the connection or service being attempted Check the module in use and verify that it exactly matches the module specified in the 1 0 configuration tree of the Logix Designer application For more information about electronic keying see t
65. t enough connections available either for the controller or for the communication module being used to connect through Check the connection use of the controller or communication module If all of the connections are used try to free some of the used connections or add another module to route the errant connection through e The 1 0 memory limits of the controller are exceeded Check the 1 0 memory available and make program or tag changes if needed e The 1 0 module targeted does not have enough connections available Check the number of controllers making a connection to this 1 0 module and verify that the number of connections is within the limits of the 1 0 module 42 Rockwell Automation Publication 1756 PM014H EN P November 2015 I 0 Fault Codes Chapter 3 Code Interpretation 0005 The controller is attempting to make a connection to the module and has received an error Possible causes include the following e The configured address for the connection to the module is incorrect e The module in use that is the physical module is different than the module specified in the 1 0 configuration tree and is therefore causing the connection or service to fail The fault may occur even when the module passes the electronic keying test This may result when Disable Keying or Compatible Keying options were used in the module configuration instead of the Exact Match option Despite passing the electronic keying test the module being connected to does
66. t matches the module specified in the 1 0 configuration tree of the Logix Designer application For more information about electronic keying see the user manual for the module you are using e For Listen Only connections the RPI set by the owner of this module is slower than the one requested Either increase the requested RPI or decrease the RPI the owner controller is using See the Connection tab for valid RPI values 0114 The Product Code of the actual module hardware does not match the Product Code of the module created in the software Electronic Keying failed for this module You may have a mismatch between the module created in the software and the actual module hardware 0115 The Product Type of the actual module hardware does not match the Product Type of the module created in the software Electronic Keying failed for this module You may have a mismatch between the module created in the software and the actual module hardware 0116 The Major or Minor revisions of the module do not match the Major or Minor revisions of the module created in the software Verify that you have specified the correct Major and Minor Revision if you have chosen Compatible Module or Exact Match keying Electronic Keying failed for this module You may have a mismatch between the module created in the software and the actual module hardware Rockwell Automation Publication 1756 PM014H EN P November 2015 45 Chapter 3 1 0 Fault Codes Code Interpretation
67. t routine 3 Inthe Type field choose Ladder 4 Click OK Configuring the Program to Use the Fault Routine 1 Inthe Controller Organizer right click the program and choose New Routine 2 On the New Routine dialog box click the Configuration tab 3 Inthe Fault field choose the fault routine 4 Click OK Jumping to the Fault Routine In the main routine of the program enter the following rung where e Fault_Routine is the name of the fault routine for the program e 999 is the value for the fault code Conditions when the JSR controller should shut down Jump To Subroutine Routine Name Fault_Routine Input Par 999 28 Rockwell Automation Publication 1756 PM014H EN P November 2015 Major Faults Chapter 1 Example Creating a User Defined Major Fault When Tag_1 0 1 execution jumps to name_of_fault_routine A major fault occurs and the controller enters the faulted mode Outputs go to the faulted state The Controller Properties dialog box Major Faults tab displays the code 999 JSR Jump To Subroutine Routine Name Fault_Routine Input Par 999 Major Fault Codes The type and code correspond to the type and code displayed in the following locations e Controller Properties dialog box Major Faults tab e Program object MajorFaultRecord attribute 1 1 The controller powered on in Run mode Run the power loss handler I O communication configuration fault detect
68. the cause of the fault For more information about the Guard Motion attributes and Guard Status bits see the Integrated Motion on the Ethernet IP Network Configuration and Startup User Manual publication MOTION UM003 33 Chapter 1 Major Faults 34 Rockwell Automation Publication 1756 PM014H EN P November 2015 Chapter 2 Minor Faults This chapter explains minor fault codes and how to work with them in the Logix Designer application Identifying Minor Faults The following table explains how to use relay ladder logic to monitor information To check fora Task overlap Load from nonvolatile memory Serial port fault Low battery or energy storage status Instruction related fault about common minor faults Do this 1 Enter a GSV instruction that gets the FaultLog object MinorFaultBits attribute 2 Monitor bit 6 1 Enter a GSV instruction that gets the FaultLog object MinorFaultBits attribute 2 Monitor bit 7 1 Enter a GSV instruction that gets the FaultLog object MinorFaultBits attribute 2 Monitor bit 9 1 Enter a GSV instruction that gets the FaultLog object MinorFaultBits attribute 2 Monitor bit 10 1 Create a user defined data type that stores the fault information Name the data type FaultRecord and assign the following members TimeLow Decimal TimeHigh Decimal 1 Create a tag that stores the values of the MinorFaultRecord attribute 2 From the Data Type menu in step 1 of this i
69. ule e The connection instance is not recognized by the module e The path specified for the connection is inconsistent e The module in use that is the physical module is different than the module specified in the 1 0 configuration tree and is therefore causing the connection or service to fail The fault may occur even when the module passed the electronic keying test This may result when Disable Keying or Compatible Keying options were used in the module configuration instead of the Exact Match option Despite passing the electronic keying test the module being connected to does not have the same features or settings as the module specified in the 1 0 configuration tree and does not support the connection or service being attempted Check the module in use and verify that it exactly matches the module specified in the 1 0 configuration tree of the Logix Designer application For more information about electronic keying see the user manual for the module you are using 0119 The controlling connection is not open Where a Listen Only connection is requested the controlling connection is not open 011A The controller is attempting to set up a connection with the module and cannot because required resources are unavailable If the module is a 1756 ControlNet module up to five controllers can make Rack Optimization connections to the module Verify that this number has not been exceeded If the module is a 1794 ACN15 1794 ACNR15 or 1797 ACNR15 adapte
70. value of a CONTROL structure is invalid The first CLR instruction sets to zero the value of the fault type in the major_fault_record tag 0 O The second CLR instruction sets to zero the value of the fault code in the major_fault_record tag Clearing the Fault Enter the following rung in the fault routine for the program GSV Get System Valie Diss name Instance name Program THIS Altrbute Name MajorFaultRecord Desi mao iat record Tine_Low e The SSV instruction 26 Rockwell Automation Publication 1756 PM014H EN P November 2015 Major Faults Chapter 1 e Begins during prescan with the bits of all OTE instructions off and this instruction is true When the controller begins to run the logic this instruction is always false e Writes the new values to the MajorFaultRecord attribute of this program e Writes the values contained in the major_fault_record tag Because the Type and Code member are set to zero the fault clears and the logic starts running again Testing a Fault Routine You can use a JSR instruction to test the fault routine of a program without creating an error simulate a fault 1 Create a BOOL tag that you use to initiate the fault 2 Inthe main routine or a subroutine of the program enter the following rung where e test_fault_routine is the tag that you use to initiate the fault e Fault_Routine is the fault routine of the program When test_fault_routine is on a maj
71. with the module and has received an error the connection request is invalid e The module in use that is the physical module is different than the module specified in the 1 0 configuration tree and is therefore causing the connection or service to fail The fault may occur even when the module passes the electronic keying test This may result when Disable Keying or Compatible Keying options are used in the module configuration instead of the Exact Match option Despite passing the electronic keying test the module being connected to does not have the same features or settings as the module specified in the 1 0 configuration tree and does not support the connection or service being attempted Check the module in use and verify that it exactly matches the module specified in the 1 0 configuration tree of the Logix Designer application For more information about electronic keying see the user manual for the module you are using 0317 The controller is attempting to set up a ControlNet connection with the module and has received an error Use RSNetWorx for ControlNet software to schedule or reschedule the connection to this module 0318 The controller is attempting to set up a connection with the module and has received an error the link address is invalid Verify that the associated ControlNet module has the correct slot or node number selected 0319 The controller is attempting to set up a connection with the module and has received an error the redund
72. work with them in the Logix Designer application If a fault condition occurs that would prevent an instruction from running the instruction is aborted and a major fault is reported A major fault halts logic execution and the controller switches to faulted mode the OK LED flashes red Depending on your application you may not want all major faults to shut down your system If you do not want all major faults to shut down your system create a fault routine to clear the fault and let your application continue to run See Creating a Routine for the Controller Fault Handler on page 16 and Clearing a Major Fault During Prescan on page 24 The process of resuming execution after a fault is cleared is known as fault recovery Important Do not use fault routines to continually clear all faults on the controller Program the fault routine to be selective in the types and number of faults cleaned It is also a good idea to log the fault occurrence so you can analyze it later Important When an instruction generates an error due to a fault for example a COP with an indirect addressing programming error the instruction is skipped and does not run This occurs with all instructions Example In a system that uses recipe numbers as indirect addresses an incorrectly typed number could produce a major fault To keep the entire system from shutting down in the event of this fault you can program a fault routine to clear type 4 code 20 major

1756-PM014 - Rockwell Automation

Contents

Download Pdf Manuals

Related Search

Related Contents