Split (1)

train · 4.25k rows

Document Name stringclasses 11 values	URL stringclasses 11 values	page_number int64 1 1.26k	full_text stringlengths 65 18.2k
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	107	6 Trouble shooting by Event log 104 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20051, Not allowed command Description The command is only allowed when the client is in control of the resource (program/motion). Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Check if the client is in control, by checking "Write Access" in RobotStudio. 2) Check if the client who ought to be in control really is. 20054, Not allowed command Description The command is NOT allowed when the program is executing. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Make sure the program is not executing. 20060, Not allowed command Description The command is not allowed in Auto mode. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Make sure the system is NOT in Auto Mode. 20061, Not allowed command Description The command is not allowed when changing to Auto mode. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Make sure the system is NOT changing to Auto Mode. 20062, Not allowed command Description The command is not allowed in Manual mode. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Make sure the system is NOT in Manual Mode. 20063, Not allowed command Description The command is not allowed in Manual full speed mode. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Make sure the system is NOT in Manual full speed Mode. 20064, Not allowed command Description The command is not allowed when changing to Manual full speed mode. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Make sure the system is NOT changing to Manual full speed Mode. 20065, Not allowed command Description The command is only allowed in Manual mode (reduced or full speed). Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Make sure the system is NOT in Auto mode or changing to Manual Mode (reduced or full speed). 20070, Not allowed command Description The command is not allowed in Motors ON state. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Make sure the system is in Motors OFF state. 6 Trouble shooting by Event log 105 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20071, Not allowed command Description The command is not allowed while changing to Motors ON state. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Investigate by whom and why the action was requested, and, if required, correct the reason. 20072, Not allowed command Description The command is not allowed in Motors OFF state. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Make sure the system is in Motors ON state. 20073, Not allowed command Description The command is not allowed while changing to Motors OFF state. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Investigate by whom and why the action was requested, and, if required, correct the reason. 20074, Not allowed command Description The command is not allowed in Guard Stop state. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Make sure the system is NOT in Guard Stop state. 20075, Not allowed command Description The command is not allowed in Emergency Stop state. Consequences Emergency stop reset is required. Recommended actions 1) Make sure the system is NOT in Emergency Stop state. 20076, Not allowed command Description The command is not allowed in System Failure state. Consequences A non-recoverable system error has resulted, and a warm start is required. Recommended actions 1) Make sure the system is NOT in Emergency Stop state. 2) Perform a restart as detailed in the Operator's Manual, IRC5. 3) If restarting is not possible, switch the main power OFF and then back ON. 20080, Not allowed command Description The command is not allowed when axis has not been commutated. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Commutate the axis as detailed in the Additional Axes Manual. 2) Investigate by whom and why the action was requested, and, if required, correct the reason. 20081, Not allowed command Description The command is not allowed when axis is not calibrated. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Calibrate the axis as detailed in the Calibration Pendulum Instruction or the Instructions for Levelmeter calibration, depending on which equipment to be used. 20082, Not allowed command Description The command is not allowed when axis revolution counter is not updated. Consequences The system remains in the same status, and the requested action will not be performed. 6 Trouble shooting by Event log 106 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Update the revolution counter as detailed in Operator's Manual, IRC5. 20083, Not allowed command Description The command is not allowed when axis is not synchronized. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Synchronize the axis as detailed in the Calibration Pendulum Instruction or the Instructions for Levelmeter calibration, depending on which equipment to be used. 20084, Not allowed command Description This command is not allowed since data in the Serial Measurement Board (SMB) memory is not OK. Consequences All data must be OK before automatic operation is possible. Manually jogging the robot is possible. Recommended actions 1) Update the Serial Measurement Board data as detailed in Operator's Manual, IRC5. 20088, Automatic Mode Rejected Description The speed could not be set to 100% when automatic mode was requested. Consequences The system can not enter automatic mode. Probable causes The speed could not be set to 100%. Recommended actions 1) Switch back to manual mode 2a) Set the speed in the QuickSet menu 2b) or set System Parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to No if the system should be in debug mode when switching to auto. 3) Switch back to automatic mode and confirm. 20089, Automatic Mode Rejected Description The call chain was altered to begin at a routine other than main and could not be reset to main when automatic mode was requested. Consequences The system can not enter automatic mode. Probable causes Program pointer could not be set to Main. Recommended actions 1) Switch back to manual mode. 2a) Move PP to main. 2b) or if the program always shall start at the new routine, change System Parameter "Main entry" (Domain Controller, Type Task) to the new routine name. 2c) or set System Parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to No if the system should be in debug mode when switching to auto. 3) Switch back to automatic mode and confirm. 20092, Not allowed command Description Not allowed in state System IO Start Blocked. Recommended actions 20093, Automatic Mode Rejected Description One or more of the NORMAL tasks were disabled and could not be enabled when automatic mode was requested. Consequences The system can not enter automatic mode. Probable causes It is not possible to reset Task Selection Panel in synchronized block. Recommended actions 1) Switch back to manual mode. 2a) Set PP to main. 2b) or step out of synchronized block. 2c) or set System Parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to No if the system should be in debug mode when switching to auto. 3) Switch back to automatic mode and confirm. 20094, Load name could not be found Description Load name arg could not be found. Consequences It is not possible to jog without a correct defined load. Probable causes The module with the load definition is probably deleted.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	108	6 Trouble shooting by Event log 105 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20071, Not allowed command Description The command is not allowed while changing to Motors ON state. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Investigate by whom and why the action was requested, and, if required, correct the reason. 20072, Not allowed command Description The command is not allowed in Motors OFF state. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Make sure the system is in Motors ON state. 20073, Not allowed command Description The command is not allowed while changing to Motors OFF state. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Investigate by whom and why the action was requested, and, if required, correct the reason. 20074, Not allowed command Description The command is not allowed in Guard Stop state. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Make sure the system is NOT in Guard Stop state. 20075, Not allowed command Description The command is not allowed in Emergency Stop state. Consequences Emergency stop reset is required. Recommended actions 1) Make sure the system is NOT in Emergency Stop state. 20076, Not allowed command Description The command is not allowed in System Failure state. Consequences A non-recoverable system error has resulted, and a warm start is required. Recommended actions 1) Make sure the system is NOT in Emergency Stop state. 2) Perform a restart as detailed in the Operator's Manual, IRC5. 3) If restarting is not possible, switch the main power OFF and then back ON. 20080, Not allowed command Description The command is not allowed when axis has not been commutated. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Commutate the axis as detailed in the Additional Axes Manual. 2) Investigate by whom and why the action was requested, and, if required, correct the reason. 20081, Not allowed command Description The command is not allowed when axis is not calibrated. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Calibrate the axis as detailed in the Calibration Pendulum Instruction or the Instructions for Levelmeter calibration, depending on which equipment to be used. 20082, Not allowed command Description The command is not allowed when axis revolution counter is not updated. Consequences The system remains in the same status, and the requested action will not be performed. 6 Trouble shooting by Event log 106 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Update the revolution counter as detailed in Operator's Manual, IRC5. 20083, Not allowed command Description The command is not allowed when axis is not synchronized. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Synchronize the axis as detailed in the Calibration Pendulum Instruction or the Instructions for Levelmeter calibration, depending on which equipment to be used. 20084, Not allowed command Description This command is not allowed since data in the Serial Measurement Board (SMB) memory is not OK. Consequences All data must be OK before automatic operation is possible. Manually jogging the robot is possible. Recommended actions 1) Update the Serial Measurement Board data as detailed in Operator's Manual, IRC5. 20088, Automatic Mode Rejected Description The speed could not be set to 100% when automatic mode was requested. Consequences The system can not enter automatic mode. Probable causes The speed could not be set to 100%. Recommended actions 1) Switch back to manual mode 2a) Set the speed in the QuickSet menu 2b) or set System Parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to No if the system should be in debug mode when switching to auto. 3) Switch back to automatic mode and confirm. 20089, Automatic Mode Rejected Description The call chain was altered to begin at a routine other than main and could not be reset to main when automatic mode was requested. Consequences The system can not enter automatic mode. Probable causes Program pointer could not be set to Main. Recommended actions 1) Switch back to manual mode. 2a) Move PP to main. 2b) or if the program always shall start at the new routine, change System Parameter "Main entry" (Domain Controller, Type Task) to the new routine name. 2c) or set System Parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to No if the system should be in debug mode when switching to auto. 3) Switch back to automatic mode and confirm. 20092, Not allowed command Description Not allowed in state System IO Start Blocked. Recommended actions 20093, Automatic Mode Rejected Description One or more of the NORMAL tasks were disabled and could not be enabled when automatic mode was requested. Consequences The system can not enter automatic mode. Probable causes It is not possible to reset Task Selection Panel in synchronized block. Recommended actions 1) Switch back to manual mode. 2a) Set PP to main. 2b) or step out of synchronized block. 2c) or set System Parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to No if the system should be in debug mode when switching to auto. 3) Switch back to automatic mode and confirm. 20094, Load name could not be found Description Load name arg could not be found. Consequences It is not possible to jog without a correct defined load. Probable causes The module with the load definition is probably deleted. 6 Trouble shooting by Event log 107 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Load module with load definition. Choose other load. 20095, Tool name could not be found Description Tool name arg could not be found. Consequences It is not possible to jog without a correct defined tool. Probable causes The module with the tool definition is probably deleted. Recommended actions Load module with tool definition. Choose other tool. 20096, WorkObject name could not be found Description WorkObject name arg could not be found. Consequences It is not possible to jog without a correct defined workobject. Probable causes The module with the workobject definition is probably deleted. Recommended actions Load module with workobject definition. Choose other workobject. 20097, Not allowed to jog with LOCAL PERS Load Description The object arg is of type LOCAL PERS and is not possible to jog. Recommended actions Change Load. 20098, Not allowed to jog with LOCAL PERS Tool Description The object arg is of type LOCAL PERS and is not possible to jog. Recommended actions Change Tool. 20099, Not allowed to jog with LOCAL PERS Work Object Description The object arg is of type LOCAL PERS and is not possible to jog. Recommended actions Change Work Object. 20101, TP (program) in control. Description The teachpendant programming window has focus and is in control of the program server. Recommended actions Change to the production window and perform the command again. 20103, Controller busy updating Task Selection Panel. Description The Task Selection Panel is having an update. It is not possible to do the requested command. Recommended actions Perform the command again or make a warm start and perform the command again. 20105, Backup already in progress Description A backup is already in progress. Consequences The command "Backup" from System Input Signal will be rejected. Recommended actions Use System Output Signal "Backup in progress" to control if a backup can be strarted or not. 20106, Backup path Description There are errors in the backup path or the backup name in the configuration for the System Input Backup. The directory for the backup can not be created. Backup path: arg Backup name: arg Consequences The command "Backup" from System Input Signal will be rejected.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	109	6 Trouble shooting by Event log 106 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Update the revolution counter as detailed in Operator's Manual, IRC5. 20083, Not allowed command Description The command is not allowed when axis is not synchronized. Consequences The system remains in the same status, and the requested action will not be performed. Recommended actions 1) Synchronize the axis as detailed in the Calibration Pendulum Instruction or the Instructions for Levelmeter calibration, depending on which equipment to be used. 20084, Not allowed command Description This command is not allowed since data in the Serial Measurement Board (SMB) memory is not OK. Consequences All data must be OK before automatic operation is possible. Manually jogging the robot is possible. Recommended actions 1) Update the Serial Measurement Board data as detailed in Operator's Manual, IRC5. 20088, Automatic Mode Rejected Description The speed could not be set to 100% when automatic mode was requested. Consequences The system can not enter automatic mode. Probable causes The speed could not be set to 100%. Recommended actions 1) Switch back to manual mode 2a) Set the speed in the QuickSet menu 2b) or set System Parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to No if the system should be in debug mode when switching to auto. 3) Switch back to automatic mode and confirm. 20089, Automatic Mode Rejected Description The call chain was altered to begin at a routine other than main and could not be reset to main when automatic mode was requested. Consequences The system can not enter automatic mode. Probable causes Program pointer could not be set to Main. Recommended actions 1) Switch back to manual mode. 2a) Move PP to main. 2b) or if the program always shall start at the new routine, change System Parameter "Main entry" (Domain Controller, Type Task) to the new routine name. 2c) or set System Parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to No if the system should be in debug mode when switching to auto. 3) Switch back to automatic mode and confirm. 20092, Not allowed command Description Not allowed in state System IO Start Blocked. Recommended actions 20093, Automatic Mode Rejected Description One or more of the NORMAL tasks were disabled and could not be enabled when automatic mode was requested. Consequences The system can not enter automatic mode. Probable causes It is not possible to reset Task Selection Panel in synchronized block. Recommended actions 1) Switch back to manual mode. 2a) Set PP to main. 2b) or step out of synchronized block. 2c) or set System Parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to No if the system should be in debug mode when switching to auto. 3) Switch back to automatic mode and confirm. 20094, Load name could not be found Description Load name arg could not be found. Consequences It is not possible to jog without a correct defined load. Probable causes The module with the load definition is probably deleted. 6 Trouble shooting by Event log 107 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Load module with load definition. Choose other load. 20095, Tool name could not be found Description Tool name arg could not be found. Consequences It is not possible to jog without a correct defined tool. Probable causes The module with the tool definition is probably deleted. Recommended actions Load module with tool definition. Choose other tool. 20096, WorkObject name could not be found Description WorkObject name arg could not be found. Consequences It is not possible to jog without a correct defined workobject. Probable causes The module with the workobject definition is probably deleted. Recommended actions Load module with workobject definition. Choose other workobject. 20097, Not allowed to jog with LOCAL PERS Load Description The object arg is of type LOCAL PERS and is not possible to jog. Recommended actions Change Load. 20098, Not allowed to jog with LOCAL PERS Tool Description The object arg is of type LOCAL PERS and is not possible to jog. Recommended actions Change Tool. 20099, Not allowed to jog with LOCAL PERS Work Object Description The object arg is of type LOCAL PERS and is not possible to jog. Recommended actions Change Work Object. 20101, TP (program) in control. Description The teachpendant programming window has focus and is in control of the program server. Recommended actions Change to the production window and perform the command again. 20103, Controller busy updating Task Selection Panel. Description The Task Selection Panel is having an update. It is not possible to do the requested command. Recommended actions Perform the command again or make a warm start and perform the command again. 20105, Backup already in progress Description A backup is already in progress. Consequences The command "Backup" from System Input Signal will be rejected. Recommended actions Use System Output Signal "Backup in progress" to control if a backup can be strarted or not. 20106, Backup path Description There are errors in the backup path or the backup name in the configuration for the System Input Backup. The directory for the backup can not be created. Backup path: arg Backup name: arg Consequences The command "Backup" from System Input Signal will be rejected. 6 Trouble shooting by Event log 108 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Verify that configured path and name for the System Input Backup are correct. 20111, TP (program) in control Description The teachpendant programming window has focus and is in control of the program server. Recommended actions Change to the production window and perform the command again. 20120, System IO in control Description See Title Recommended actions 20126, Load data has changed Description The active load arg was removed and replaced with arg . The load data was located in task: arg connected to mechanical unit arg . Consequences The load definition for jogging may not be correct. Probable causes The load data was removed. The module containing the original tool definition may have been deleted. Recommended actions If you require the old definition, locate the program or module of the original load data and load it. 20127, Tool data has changed Description The active tool arg was removed and replaced with arg . The tool data was located in task: arg connected to mechanical unit arg . Consequences The tool definition for jogging may not be correct. Probable causes The tool data was removed. The module containing the original tool definition may have been deleted. Recommended actions If you require the old definition, locate the program or module of the original tool data and load it. 20128, Work object data has changed Description The active work object arg was removed and replaced with arg . The work object data was located in task: arg connected to mechanical unit arg . Consequences The work object definition for jogging may not be correct. Probable causes The work object data was removed. The module containing the original tool definition may have been deleted. Recommended actions If you require the old definition, locate the program or module of the original work object data and load it. 20130, Active Task Menu is restored Description During warm start, the "Active Task Menu" is restored in Auto mode. Consequences If one or several tasks were unchecked, they are now checked again after the warm start in Auto mode. Probable causes A warm start has been performed Recommended actions Go to manual mode. 2. Uncheck the not wanted tasks 3. Go back to Auto mode. 20131, Automatic Mode Rejected Description One or more logical I/O signals were blocked and could not be unblocked when automatic mode was requested. Consequences The system can not enter automatic mode. Probable causes Some blocked I/O signal could not be unblocked. Recommended actions 1) Switch back to manual mode. 2a) Check Event Log for errors related to I/O. 2b) or set System Parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to No if the system should be in debug mode when switching to auto. 3) Switch back to automatic mode and confirm.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	110	6 Trouble shooting by Event log 107 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Load module with load definition. Choose other load. 20095, Tool name could not be found Description Tool name arg could not be found. Consequences It is not possible to jog without a correct defined tool. Probable causes The module with the tool definition is probably deleted. Recommended actions Load module with tool definition. Choose other tool. 20096, WorkObject name could not be found Description WorkObject name arg could not be found. Consequences It is not possible to jog without a correct defined workobject. Probable causes The module with the workobject definition is probably deleted. Recommended actions Load module with workobject definition. Choose other workobject. 20097, Not allowed to jog with LOCAL PERS Load Description The object arg is of type LOCAL PERS and is not possible to jog. Recommended actions Change Load. 20098, Not allowed to jog with LOCAL PERS Tool Description The object arg is of type LOCAL PERS and is not possible to jog. Recommended actions Change Tool. 20099, Not allowed to jog with LOCAL PERS Work Object Description The object arg is of type LOCAL PERS and is not possible to jog. Recommended actions Change Work Object. 20101, TP (program) in control. Description The teachpendant programming window has focus and is in control of the program server. Recommended actions Change to the production window and perform the command again. 20103, Controller busy updating Task Selection Panel. Description The Task Selection Panel is having an update. It is not possible to do the requested command. Recommended actions Perform the command again or make a warm start and perform the command again. 20105, Backup already in progress Description A backup is already in progress. Consequences The command "Backup" from System Input Signal will be rejected. Recommended actions Use System Output Signal "Backup in progress" to control if a backup can be strarted or not. 20106, Backup path Description There are errors in the backup path or the backup name in the configuration for the System Input Backup. The directory for the backup can not be created. Backup path: arg Backup name: arg Consequences The command "Backup" from System Input Signal will be rejected. 6 Trouble shooting by Event log 108 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Verify that configured path and name for the System Input Backup are correct. 20111, TP (program) in control Description The teachpendant programming window has focus and is in control of the program server. Recommended actions Change to the production window and perform the command again. 20120, System IO in control Description See Title Recommended actions 20126, Load data has changed Description The active load arg was removed and replaced with arg . The load data was located in task: arg connected to mechanical unit arg . Consequences The load definition for jogging may not be correct. Probable causes The load data was removed. The module containing the original tool definition may have been deleted. Recommended actions If you require the old definition, locate the program or module of the original load data and load it. 20127, Tool data has changed Description The active tool arg was removed and replaced with arg . The tool data was located in task: arg connected to mechanical unit arg . Consequences The tool definition for jogging may not be correct. Probable causes The tool data was removed. The module containing the original tool definition may have been deleted. Recommended actions If you require the old definition, locate the program or module of the original tool data and load it. 20128, Work object data has changed Description The active work object arg was removed and replaced with arg . The work object data was located in task: arg connected to mechanical unit arg . Consequences The work object definition for jogging may not be correct. Probable causes The work object data was removed. The module containing the original tool definition may have been deleted. Recommended actions If you require the old definition, locate the program or module of the original work object data and load it. 20130, Active Task Menu is restored Description During warm start, the "Active Task Menu" is restored in Auto mode. Consequences If one or several tasks were unchecked, they are now checked again after the warm start in Auto mode. Probable causes A warm start has been performed Recommended actions Go to manual mode. 2. Uncheck the not wanted tasks 3. Go back to Auto mode. 20131, Automatic Mode Rejected Description One or more logical I/O signals were blocked and could not be unblocked when automatic mode was requested. Consequences The system can not enter automatic mode. Probable causes Some blocked I/O signal could not be unblocked. Recommended actions 1) Switch back to manual mode. 2a) Check Event Log for errors related to I/O. 2b) or set System Parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to No if the system should be in debug mode when switching to auto. 3) Switch back to automatic mode and confirm. 6 Trouble shooting by Event log 109 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20132, Blocked I/O signals Description One or more logical I/O signals were blocked during startup in automatic mode. Consequences Blocked signals will be unblocked. Probable causes System was switched to automatic mode during warm start. System parameter AllDebugSettings is set to Yes. Recommended actions None, system has automatically reset debug settings. To keep debug settings in auto: 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to NO. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20133, Debug Settings in Auto Description One or more logical I/O signals were blocked during startup in automatic mode. Consequences Blocked I/O signals will stay blocked. System will not be in full production mode in auto. Recommended actions For full production mode: 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to YES. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20134, Call Chain Description The call chain has been altered to begin at a routine other than main. Consequences Program pointer will be reset to main routine. Probable causes System was switched to automatic mode during warm start. System parameter AllDebugSettings is set to Yes. Recommended actions For debug mode in auto: 1) Switch back to manual mode 2) Set system parameter AllDebugSetting, reset to NO. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20135, Debug Settings in Auto Description The call chain has been altered to begin at a routine other than main. Consequences Program pointer will not be set to main. System will not be in full production mode in auto. Recommended actions For full production mode: 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to YES. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20136, Reduced Speed Description The system was running at reduced speed during startup in automatic mode. Consequences Speed will be set to 100%. Probable causes System was switched to automatic mode during warm start. Recommended actions None, system has automatically reset debug settings. To keep debug settings in auto: 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to NO. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20137, Debug Settings in Auto Description The system was running at reduced speed during startup in automatic mode. Consequences Speed will stay unchanged. System will not be in full production mode in auto. Recommended actions For full production mode:
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	111	6 Trouble shooting by Event log 108 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Verify that configured path and name for the System Input Backup are correct. 20111, TP (program) in control Description The teachpendant programming window has focus and is in control of the program server. Recommended actions Change to the production window and perform the command again. 20120, System IO in control Description See Title Recommended actions 20126, Load data has changed Description The active load arg was removed and replaced with arg . The load data was located in task: arg connected to mechanical unit arg . Consequences The load definition for jogging may not be correct. Probable causes The load data was removed. The module containing the original tool definition may have been deleted. Recommended actions If you require the old definition, locate the program or module of the original load data and load it. 20127, Tool data has changed Description The active tool arg was removed and replaced with arg . The tool data was located in task: arg connected to mechanical unit arg . Consequences The tool definition for jogging may not be correct. Probable causes The tool data was removed. The module containing the original tool definition may have been deleted. Recommended actions If you require the old definition, locate the program or module of the original tool data and load it. 20128, Work object data has changed Description The active work object arg was removed and replaced with arg . The work object data was located in task: arg connected to mechanical unit arg . Consequences The work object definition for jogging may not be correct. Probable causes The work object data was removed. The module containing the original tool definition may have been deleted. Recommended actions If you require the old definition, locate the program or module of the original work object data and load it. 20130, Active Task Menu is restored Description During warm start, the "Active Task Menu" is restored in Auto mode. Consequences If one or several tasks were unchecked, they are now checked again after the warm start in Auto mode. Probable causes A warm start has been performed Recommended actions Go to manual mode. 2. Uncheck the not wanted tasks 3. Go back to Auto mode. 20131, Automatic Mode Rejected Description One or more logical I/O signals were blocked and could not be unblocked when automatic mode was requested. Consequences The system can not enter automatic mode. Probable causes Some blocked I/O signal could not be unblocked. Recommended actions 1) Switch back to manual mode. 2a) Check Event Log for errors related to I/O. 2b) or set System Parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to No if the system should be in debug mode when switching to auto. 3) Switch back to automatic mode and confirm. 6 Trouble shooting by Event log 109 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20132, Blocked I/O signals Description One or more logical I/O signals were blocked during startup in automatic mode. Consequences Blocked signals will be unblocked. Probable causes System was switched to automatic mode during warm start. System parameter AllDebugSettings is set to Yes. Recommended actions None, system has automatically reset debug settings. To keep debug settings in auto: 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to NO. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20133, Debug Settings in Auto Description One or more logical I/O signals were blocked during startup in automatic mode. Consequences Blocked I/O signals will stay blocked. System will not be in full production mode in auto. Recommended actions For full production mode: 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to YES. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20134, Call Chain Description The call chain has been altered to begin at a routine other than main. Consequences Program pointer will be reset to main routine. Probable causes System was switched to automatic mode during warm start. System parameter AllDebugSettings is set to Yes. Recommended actions For debug mode in auto: 1) Switch back to manual mode 2) Set system parameter AllDebugSetting, reset to NO. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20135, Debug Settings in Auto Description The call chain has been altered to begin at a routine other than main. Consequences Program pointer will not be set to main. System will not be in full production mode in auto. Recommended actions For full production mode: 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to YES. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20136, Reduced Speed Description The system was running at reduced speed during startup in automatic mode. Consequences Speed will be set to 100%. Probable causes System was switched to automatic mode during warm start. Recommended actions None, system has automatically reset debug settings. To keep debug settings in auto: 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to NO. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20137, Debug Settings in Auto Description The system was running at reduced speed during startup in automatic mode. Consequences Speed will stay unchanged. System will not be in full production mode in auto. Recommended actions For full production mode: 6 Trouble shooting by Event log 110 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to YES. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20138, Disabled Tasks Description One or more of the NORMAL tasks were disabled during the startup when in automatic mode. Consequences All disabled normal tasks will be enabled. Probable causes System was switched to automatic mode during warm start System parameter AllDebugSettings is set to Yes. Recommended actions None, system has automatically reset debug settings. To keep debug settings in auto: 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to NO. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20139, Debug Settings in Auto Description One or more of the NORMAL tasks were disabled during startup in automatic mode. Consequences Disabled tasks will stay disabled. System will not be in full production mode in auto. Recommended actions For full production mode: 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to YES. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20140, Motors On rejected Description Motors On, via System IO, was rejected. Recommended actions 20141, Motors Off rejected Description Motors Off, via System IO, was rejected. Recommended actions 20142, Start rejected Description Start/restart of program, via System IO, was rejected. The reason could be that the robot is outside of regain distance. Recommended actions 20143, Start at main rejected Description Start of program at main, via System IO, was rejected. Recommended actions 20144, Stop rejected Description Stop of program, via System IO, was rejected. Recommended actions 20145, Stop cycle rejected Description Stop of program after cycle, via System IO, was rejected. Recommended actions 20146, Manual interrupt rejected Description Manual interrupt of program, via System IO, was rejected. Recommended actions 20147, Load and start rejected Description Load and start of program, via System IO, was rejected. Recommended actions The name of the program file to be loaded (including mass memory unit) must be defined.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	112	6 Trouble shooting by Event log 109 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20132, Blocked I/O signals Description One or more logical I/O signals were blocked during startup in automatic mode. Consequences Blocked signals will be unblocked. Probable causes System was switched to automatic mode during warm start. System parameter AllDebugSettings is set to Yes. Recommended actions None, system has automatically reset debug settings. To keep debug settings in auto: 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to NO. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20133, Debug Settings in Auto Description One or more logical I/O signals were blocked during startup in automatic mode. Consequences Blocked I/O signals will stay blocked. System will not be in full production mode in auto. Recommended actions For full production mode: 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to YES. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20134, Call Chain Description The call chain has been altered to begin at a routine other than main. Consequences Program pointer will be reset to main routine. Probable causes System was switched to automatic mode during warm start. System parameter AllDebugSettings is set to Yes. Recommended actions For debug mode in auto: 1) Switch back to manual mode 2) Set system parameter AllDebugSetting, reset to NO. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20135, Debug Settings in Auto Description The call chain has been altered to begin at a routine other than main. Consequences Program pointer will not be set to main. System will not be in full production mode in auto. Recommended actions For full production mode: 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to YES. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20136, Reduced Speed Description The system was running at reduced speed during startup in automatic mode. Consequences Speed will be set to 100%. Probable causes System was switched to automatic mode during warm start. Recommended actions None, system has automatically reset debug settings. To keep debug settings in auto: 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to NO. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20137, Debug Settings in Auto Description The system was running at reduced speed during startup in automatic mode. Consequences Speed will stay unchanged. System will not be in full production mode in auto. Recommended actions For full production mode: 6 Trouble shooting by Event log 110 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to YES. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20138, Disabled Tasks Description One or more of the NORMAL tasks were disabled during the startup when in automatic mode. Consequences All disabled normal tasks will be enabled. Probable causes System was switched to automatic mode during warm start System parameter AllDebugSettings is set to Yes. Recommended actions None, system has automatically reset debug settings. To keep debug settings in auto: 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to NO. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20139, Debug Settings in Auto Description One or more of the NORMAL tasks were disabled during startup in automatic mode. Consequences Disabled tasks will stay disabled. System will not be in full production mode in auto. Recommended actions For full production mode: 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to YES. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20140, Motors On rejected Description Motors On, via System IO, was rejected. Recommended actions 20141, Motors Off rejected Description Motors Off, via System IO, was rejected. Recommended actions 20142, Start rejected Description Start/restart of program, via System IO, was rejected. The reason could be that the robot is outside of regain distance. Recommended actions 20143, Start at main rejected Description Start of program at main, via System IO, was rejected. Recommended actions 20144, Stop rejected Description Stop of program, via System IO, was rejected. Recommended actions 20145, Stop cycle rejected Description Stop of program after cycle, via System IO, was rejected. Recommended actions 20146, Manual interrupt rejected Description Manual interrupt of program, via System IO, was rejected. Recommended actions 20147, Load and start rejected Description Load and start of program, via System IO, was rejected. Recommended actions The name of the program file to be loaded (including mass memory unit) must be defined. 6 Trouble shooting by Event log 111 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20148, Confirm rejected Description Emergency Stop reset confirm, via System IO, was rejected. Recommended actions 20149, Error reset rejected Description Program execution error reset, via System IO, was rejected. Recommended actions 20150, Load failure Description Load of program, via System IO, failed. Consequences Program will not be possible to start. Probable causes - The arguments for the System Input Load are wrong. - The module was loaded, but the system failed to set the program pointer. - The program was executing. Recommended actions Check the following: - correct arguments for System Input Load. - defined and correct name of the program file to be loaded (including mass memory unit). - defined and correct name of the task that the program should be loaded in. - program stopped before activating System Input Load. 20153, Motors On and Start rejected Description Motors On and Start/Restart of program, via System IO, was rejected. The reason could be that the robot is outside of regain distance. Recommended actions 20154, Stop instruction rejected Description Stop of program after instruction, via System IO, was rejected. Recommended actions 20156, Undefined Argument Description Interrupt routine name for System IO Manual Interrupt is not defined. Recommended actions Configure the interrupt routine name. 20157, Undefined Argument Description Program name for System IO LoadStart is not defined Recommended actions Configure the program name. 20158, No System Input signal Description A System Input has been configured to an I/O-signal that doesn't exist. System Input: arg Signal Name: arg Consequences The system goes to status SYS FAIL. Recommended actions Add signal arg to eio.cfg or remove System Input arg from eio.cfg. For every System Input a signal must be configured. 20159, No System Output signal Description A System Output has been configured to an I/O-signal that doesn't exist. System Output: arg Signal Name: arg Consequences The system goes to status SYS FAIL. Recommended actions Add signal arg to eio.cfg or remove System Output arg from eio.cfg. For every System Output a signal must be configured. 20161, Path not found Description The system module arg in task arg has a corresponding specification in the configuration for "Task modules" that point out a non existing file path Recommended actions View "Task modules" in the "System Parameter" menu and change the path
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	113	6 Trouble shooting by Event log 110 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to YES. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20138, Disabled Tasks Description One or more of the NORMAL tasks were disabled during the startup when in automatic mode. Consequences All disabled normal tasks will be enabled. Probable causes System was switched to automatic mode during warm start System parameter AllDebugSettings is set to Yes. Recommended actions None, system has automatically reset debug settings. To keep debug settings in auto: 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to NO. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20139, Debug Settings in Auto Description One or more of the NORMAL tasks were disabled during startup in automatic mode. Consequences Disabled tasks will stay disabled. System will not be in full production mode in auto. Recommended actions For full production mode: 1) Switch back to manual mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to YES. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20140, Motors On rejected Description Motors On, via System IO, was rejected. Recommended actions 20141, Motors Off rejected Description Motors Off, via System IO, was rejected. Recommended actions 20142, Start rejected Description Start/restart of program, via System IO, was rejected. The reason could be that the robot is outside of regain distance. Recommended actions 20143, Start at main rejected Description Start of program at main, via System IO, was rejected. Recommended actions 20144, Stop rejected Description Stop of program, via System IO, was rejected. Recommended actions 20145, Stop cycle rejected Description Stop of program after cycle, via System IO, was rejected. Recommended actions 20146, Manual interrupt rejected Description Manual interrupt of program, via System IO, was rejected. Recommended actions 20147, Load and start rejected Description Load and start of program, via System IO, was rejected. Recommended actions The name of the program file to be loaded (including mass memory unit) must be defined. 6 Trouble shooting by Event log 111 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20148, Confirm rejected Description Emergency Stop reset confirm, via System IO, was rejected. Recommended actions 20149, Error reset rejected Description Program execution error reset, via System IO, was rejected. Recommended actions 20150, Load failure Description Load of program, via System IO, failed. Consequences Program will not be possible to start. Probable causes - The arguments for the System Input Load are wrong. - The module was loaded, but the system failed to set the program pointer. - The program was executing. Recommended actions Check the following: - correct arguments for System Input Load. - defined and correct name of the program file to be loaded (including mass memory unit). - defined and correct name of the task that the program should be loaded in. - program stopped before activating System Input Load. 20153, Motors On and Start rejected Description Motors On and Start/Restart of program, via System IO, was rejected. The reason could be that the robot is outside of regain distance. Recommended actions 20154, Stop instruction rejected Description Stop of program after instruction, via System IO, was rejected. Recommended actions 20156, Undefined Argument Description Interrupt routine name for System IO Manual Interrupt is not defined. Recommended actions Configure the interrupt routine name. 20157, Undefined Argument Description Program name for System IO LoadStart is not defined Recommended actions Configure the program name. 20158, No System Input signal Description A System Input has been configured to an I/O-signal that doesn't exist. System Input: arg Signal Name: arg Consequences The system goes to status SYS FAIL. Recommended actions Add signal arg to eio.cfg or remove System Input arg from eio.cfg. For every System Input a signal must be configured. 20159, No System Output signal Description A System Output has been configured to an I/O-signal that doesn't exist. System Output: arg Signal Name: arg Consequences The system goes to status SYS FAIL. Recommended actions Add signal arg to eio.cfg or remove System Output arg from eio.cfg. For every System Output a signal must be configured. 20161, Path not found Description The system module arg in task arg has a corresponding specification in the configuration for "Task modules" that point out a non existing file path Recommended actions View "Task modules" in the "System Parameter" menu and change the path 6 Trouble shooting by Event log 112 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. in the item for this system module 20162, Write error Description A write error occur when the system try to save the system module arg at arg in task arg . Or the file system was full Recommended actions View "Task modules" in the "System Parameter" menu and change the path in the item for this system module 20164, Reconfig failed Description There are still some unsaved system modules. Recommended actions Read error descriptions in earlier messages. Try another system start 20165, Program Pointer lost. Description Restart is no longer possible from current position. Recommended actions The program has to be started from the beginning. 20166, Refuse to save module Description The module arg is older than the source at arg in task arg . Recommended actions 20167, Unsaved module Description The module arg is changed but not saved in task arg . Recommended actions 20170, The system was stopped Description An error was detected, which stopped the system. Consequences The system goes to status SYS STOP and the robot is stopped along the path. The full meaning of this status is described in the Trouble Shooting Manual, IRC5. Probable causes A number of errors may cause this status transition. Recommended actions 1) Check other event log messages occurring at the same time to determine the actual cause. 2) Fix the cause of the fault. 20171, The system was halted Description An error was detected, which halted the system. Consequences The system goes to status SYS HALT, the program and robot motion is stopped and the motors are switched OFF. The full meaning of this status is described in the Trouble Shooting Manual, IRC5. Probable causes A number of errors may cause this status transition. Recommended actions 1) Check other event log messages occurring at the same time to determine the actual cause. 2) Fix the cause of the fault. 3) Restart the program. 20172, The system has failed Description An error was detected, which caused the system to fail. Consequences The system goes to status SYS FAIL. The program and robot motion is stopped and the motors are switched OFF. The full meaning of this status is described in the Trouble Shooting Manual, IRC5. Probable causes A number of errors may cause this status transition. Recommended actions 1) Check other event log messages occurring at the same time to determine the actual cause. 2) Fix the cause of the fault. 3) Perform a system restart as detailed in the Operator's Manual, IRC5.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	114	6 Trouble shooting by Event log 111 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20148, Confirm rejected Description Emergency Stop reset confirm, via System IO, was rejected. Recommended actions 20149, Error reset rejected Description Program execution error reset, via System IO, was rejected. Recommended actions 20150, Load failure Description Load of program, via System IO, failed. Consequences Program will not be possible to start. Probable causes - The arguments for the System Input Load are wrong. - The module was loaded, but the system failed to set the program pointer. - The program was executing. Recommended actions Check the following: - correct arguments for System Input Load. - defined and correct name of the program file to be loaded (including mass memory unit). - defined and correct name of the task that the program should be loaded in. - program stopped before activating System Input Load. 20153, Motors On and Start rejected Description Motors On and Start/Restart of program, via System IO, was rejected. The reason could be that the robot is outside of regain distance. Recommended actions 20154, Stop instruction rejected Description Stop of program after instruction, via System IO, was rejected. Recommended actions 20156, Undefined Argument Description Interrupt routine name for System IO Manual Interrupt is not defined. Recommended actions Configure the interrupt routine name. 20157, Undefined Argument Description Program name for System IO LoadStart is not defined Recommended actions Configure the program name. 20158, No System Input signal Description A System Input has been configured to an I/O-signal that doesn't exist. System Input: arg Signal Name: arg Consequences The system goes to status SYS FAIL. Recommended actions Add signal arg to eio.cfg or remove System Input arg from eio.cfg. For every System Input a signal must be configured. 20159, No System Output signal Description A System Output has been configured to an I/O-signal that doesn't exist. System Output: arg Signal Name: arg Consequences The system goes to status SYS FAIL. Recommended actions Add signal arg to eio.cfg or remove System Output arg from eio.cfg. For every System Output a signal must be configured. 20161, Path not found Description The system module arg in task arg has a corresponding specification in the configuration for "Task modules" that point out a non existing file path Recommended actions View "Task modules" in the "System Parameter" menu and change the path 6 Trouble shooting by Event log 112 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. in the item for this system module 20162, Write error Description A write error occur when the system try to save the system module arg at arg in task arg . Or the file system was full Recommended actions View "Task modules" in the "System Parameter" menu and change the path in the item for this system module 20164, Reconfig failed Description There are still some unsaved system modules. Recommended actions Read error descriptions in earlier messages. Try another system start 20165, Program Pointer lost. Description Restart is no longer possible from current position. Recommended actions The program has to be started from the beginning. 20166, Refuse to save module Description The module arg is older than the source at arg in task arg . Recommended actions 20167, Unsaved module Description The module arg is changed but not saved in task arg . Recommended actions 20170, The system was stopped Description An error was detected, which stopped the system. Consequences The system goes to status SYS STOP and the robot is stopped along the path. The full meaning of this status is described in the Trouble Shooting Manual, IRC5. Probable causes A number of errors may cause this status transition. Recommended actions 1) Check other event log messages occurring at the same time to determine the actual cause. 2) Fix the cause of the fault. 20171, The system was halted Description An error was detected, which halted the system. Consequences The system goes to status SYS HALT, the program and robot motion is stopped and the motors are switched OFF. The full meaning of this status is described in the Trouble Shooting Manual, IRC5. Probable causes A number of errors may cause this status transition. Recommended actions 1) Check other event log messages occurring at the same time to determine the actual cause. 2) Fix the cause of the fault. 3) Restart the program. 20172, The system has failed Description An error was detected, which caused the system to fail. Consequences The system goes to status SYS FAIL. The program and robot motion is stopped and the motors are switched OFF. The full meaning of this status is described in the Trouble Shooting Manual, IRC5. Probable causes A number of errors may cause this status transition. Recommended actions 1) Check other event log messages occurring at the same time to determine the actual cause. 2) Fix the cause of the fault. 3) Perform a system restart as detailed in the Operator's Manual, IRC5. 6 Trouble shooting by Event log 113 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20176, Analog System Output Outside Limits Description The value arg for the System Output arg , signal arg , is outside its limits (logical min: arg m/s, logical max: arg m/s). Consequences The new value is not set; the previous value of the analogue signal is preserved. Probable causes The logical upper and/or lower limit for the signal may be defined wrongly. Recommended actions Adjust the values of the logical upper and/or lower limit for the signal and restart the controller. 20177, Short circuit in Motor phase circuit Description The motor or motor cable for joint arg in drive module arg , drive unit number arg , is a short circuit. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty motor or motor cable. It may also be caused by contamination in the contactors for the cables or a failure of the motor windings. Recommended actions 1) Make sure the motor cable is correctly connected to the drive unit. 2) Check the cable and motor by measuring their resistance respectively. Disconnect before measuring. 3) Replace any faulty component. 20178, Wrong task name configured Description Wrong task name arg configured for System Input arg . Consequences The digital input signal will not be connected to the specified event. Recommended actions Change the configuration and restart the system. 20179, Disk memory critically low Description The amount of free storage capacity on the disk has reached a critical level. It is now less than 10 Mb. Execution of RAPID programs is stopped. Consequences The disk memory is very close to being completely full. When this happens the system will not be able to function. Probable causes Too much data on the disk Recommended actions 1) Save the files on some other disk connected to the network. 2) Erase data from disk. 3) After removing files from the drive, restart the program. 20181, System Reset rejected. Description System Reset via System IO not allowed. Recommended actions 20184, Incorrect argument for System Inputs Description An undefined Start Mode has been declared for System IO. Recommended actions 20185, Incorrect Name Description An undefined Name has been declared in current runchn_bool configuration. Recommended actions 20187, Diagnostics record file created Description Due to any of a number of faults, a system diagnostics file was created at arg . This file contains internal debug info and is intended for trouble shooting and debugging purposes. Consequences The system will react to the error causing the stop as specified in its own event log text. Probable causes A number of errors may cause this. Faults causing the system to go to status SYS FAIL will generally also create a diagnostics record file. Recommended actions If required, the file may be appended to an error report sent to your local ABB representative.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	115	6 Trouble shooting by Event log 112 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. in the item for this system module 20162, Write error Description A write error occur when the system try to save the system module arg at arg in task arg . Or the file system was full Recommended actions View "Task modules" in the "System Parameter" menu and change the path in the item for this system module 20164, Reconfig failed Description There are still some unsaved system modules. Recommended actions Read error descriptions in earlier messages. Try another system start 20165, Program Pointer lost. Description Restart is no longer possible from current position. Recommended actions The program has to be started from the beginning. 20166, Refuse to save module Description The module arg is older than the source at arg in task arg . Recommended actions 20167, Unsaved module Description The module arg is changed but not saved in task arg . Recommended actions 20170, The system was stopped Description An error was detected, which stopped the system. Consequences The system goes to status SYS STOP and the robot is stopped along the path. The full meaning of this status is described in the Trouble Shooting Manual, IRC5. Probable causes A number of errors may cause this status transition. Recommended actions 1) Check other event log messages occurring at the same time to determine the actual cause. 2) Fix the cause of the fault. 20171, The system was halted Description An error was detected, which halted the system. Consequences The system goes to status SYS HALT, the program and robot motion is stopped and the motors are switched OFF. The full meaning of this status is described in the Trouble Shooting Manual, IRC5. Probable causes A number of errors may cause this status transition. Recommended actions 1) Check other event log messages occurring at the same time to determine the actual cause. 2) Fix the cause of the fault. 3) Restart the program. 20172, The system has failed Description An error was detected, which caused the system to fail. Consequences The system goes to status SYS FAIL. The program and robot motion is stopped and the motors are switched OFF. The full meaning of this status is described in the Trouble Shooting Manual, IRC5. Probable causes A number of errors may cause this status transition. Recommended actions 1) Check other event log messages occurring at the same time to determine the actual cause. 2) Fix the cause of the fault. 3) Perform a system restart as detailed in the Operator's Manual, IRC5. 6 Trouble shooting by Event log 113 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20176, Analog System Output Outside Limits Description The value arg for the System Output arg , signal arg , is outside its limits (logical min: arg m/s, logical max: arg m/s). Consequences The new value is not set; the previous value of the analogue signal is preserved. Probable causes The logical upper and/or lower limit for the signal may be defined wrongly. Recommended actions Adjust the values of the logical upper and/or lower limit for the signal and restart the controller. 20177, Short circuit in Motor phase circuit Description The motor or motor cable for joint arg in drive module arg , drive unit number arg , is a short circuit. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty motor or motor cable. It may also be caused by contamination in the contactors for the cables or a failure of the motor windings. Recommended actions 1) Make sure the motor cable is correctly connected to the drive unit. 2) Check the cable and motor by measuring their resistance respectively. Disconnect before measuring. 3) Replace any faulty component. 20178, Wrong task name configured Description Wrong task name arg configured for System Input arg . Consequences The digital input signal will not be connected to the specified event. Recommended actions Change the configuration and restart the system. 20179, Disk memory critically low Description The amount of free storage capacity on the disk has reached a critical level. It is now less than 10 Mb. Execution of RAPID programs is stopped. Consequences The disk memory is very close to being completely full. When this happens the system will not be able to function. Probable causes Too much data on the disk Recommended actions 1) Save the files on some other disk connected to the network. 2) Erase data from disk. 3) After removing files from the drive, restart the program. 20181, System Reset rejected. Description System Reset via System IO not allowed. Recommended actions 20184, Incorrect argument for System Inputs Description An undefined Start Mode has been declared for System IO. Recommended actions 20185, Incorrect Name Description An undefined Name has been declared in current runchn_bool configuration. Recommended actions 20187, Diagnostics record file created Description Due to any of a number of faults, a system diagnostics file was created at arg . This file contains internal debug info and is intended for trouble shooting and debugging purposes. Consequences The system will react to the error causing the stop as specified in its own event log text. Probable causes A number of errors may cause this. Faults causing the system to go to status SYS FAIL will generally also create a diagnostics record file. Recommended actions If required, the file may be appended to an error report sent to your local ABB representative. 6 Trouble shooting by Event log 114 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20188, System data is not valid Description The contents of the file, arg , containing system persistent data is invalid. Internal error code: arg . The system has been started using last good system data saved earlier at arg . Consequences Any changes made in the system configuration or RAPID programs since arg will NOT be available after restart. Any such changes will have to be re-implemented. Recommended actions 1) Check other event log messages occurring at the same time to determine the actual cause. 2) If acceptable, perform a B-restart to accept starting with the loaded last good system data. 3) Reinstall the system. 4) Check the available disk storage capacity. If required, erase data to increase free storage capacity. 20189, Robot data not valid Description Could not load the system independent robot data from file arg . The file exists but the content is not valid. Internal code: arg Recommended actions Check other logged messages for needed actions. Make sure there is free memory left on the device. 20192, Disk memory low Description The amount of free storage capacity on the disk is less than 25 MB. When reaching 10 MB, execution of RAPID programs will be stopped. Consequences The disk memory is close to being completely full. When this happens the system will not be able to function. Probable causes Too much data on the disk Recommended actions 1) Save the files on some other disk connected to the network. 2) Erase data from disk. 20193, Robot data update warning Description Axis sync values and service information data (SIS) was restored from backup. The system independent robot data was not saved during system shutdown. The data was restored from latest backup. Recommended actions Make sure there is free memory left on the device. The backup battery may be drained. Check the hardware log. 20194, System data backup could not be created Description The system was restored successfully but a backup of the current system data could not be created. Recommended actions Make sure there is free memory left on the device arg . 20195, System data from last shutdown is lost Description Normally, all system data is saved on shutdown. During the last shutdown saving data has failed. The system has been started using last good system data saved earlier at arg . Consequences Any changes made in system configuration or RAPID programs since arg will NOT be available after restart. Any such changes will have to be re-implemented. Probable causes The backup energy bank may have been drained at the time of the shut down. The storage disk may be full. Recommended actions 1) Check other event log messages occurring at the same time to determine the actual cause. 2) If acceptable, perform a B-restart to accept starting with the loaded system data. 3) Reinstall the system. 4) Check the available disk storage capacity. If required, erase data to increase free storage capacity. 20196, Module saved Description During reconfiguration of the system a changed and not saved module was found. The module was saved to arg .
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	116	6 Trouble shooting by Event log 113 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20176, Analog System Output Outside Limits Description The value arg for the System Output arg , signal arg , is outside its limits (logical min: arg m/s, logical max: arg m/s). Consequences The new value is not set; the previous value of the analogue signal is preserved. Probable causes The logical upper and/or lower limit for the signal may be defined wrongly. Recommended actions Adjust the values of the logical upper and/or lower limit for the signal and restart the controller. 20177, Short circuit in Motor phase circuit Description The motor or motor cable for joint arg in drive module arg , drive unit number arg , is a short circuit. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty motor or motor cable. It may also be caused by contamination in the contactors for the cables or a failure of the motor windings. Recommended actions 1) Make sure the motor cable is correctly connected to the drive unit. 2) Check the cable and motor by measuring their resistance respectively. Disconnect before measuring. 3) Replace any faulty component. 20178, Wrong task name configured Description Wrong task name arg configured for System Input arg . Consequences The digital input signal will not be connected to the specified event. Recommended actions Change the configuration and restart the system. 20179, Disk memory critically low Description The amount of free storage capacity on the disk has reached a critical level. It is now less than 10 Mb. Execution of RAPID programs is stopped. Consequences The disk memory is very close to being completely full. When this happens the system will not be able to function. Probable causes Too much data on the disk Recommended actions 1) Save the files on some other disk connected to the network. 2) Erase data from disk. 3) After removing files from the drive, restart the program. 20181, System Reset rejected. Description System Reset via System IO not allowed. Recommended actions 20184, Incorrect argument for System Inputs Description An undefined Start Mode has been declared for System IO. Recommended actions 20185, Incorrect Name Description An undefined Name has been declared in current runchn_bool configuration. Recommended actions 20187, Diagnostics record file created Description Due to any of a number of faults, a system diagnostics file was created at arg . This file contains internal debug info and is intended for trouble shooting and debugging purposes. Consequences The system will react to the error causing the stop as specified in its own event log text. Probable causes A number of errors may cause this. Faults causing the system to go to status SYS FAIL will generally also create a diagnostics record file. Recommended actions If required, the file may be appended to an error report sent to your local ABB representative. 6 Trouble shooting by Event log 114 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20188, System data is not valid Description The contents of the file, arg , containing system persistent data is invalid. Internal error code: arg . The system has been started using last good system data saved earlier at arg . Consequences Any changes made in the system configuration or RAPID programs since arg will NOT be available after restart. Any such changes will have to be re-implemented. Recommended actions 1) Check other event log messages occurring at the same time to determine the actual cause. 2) If acceptable, perform a B-restart to accept starting with the loaded last good system data. 3) Reinstall the system. 4) Check the available disk storage capacity. If required, erase data to increase free storage capacity. 20189, Robot data not valid Description Could not load the system independent robot data from file arg . The file exists but the content is not valid. Internal code: arg Recommended actions Check other logged messages for needed actions. Make sure there is free memory left on the device. 20192, Disk memory low Description The amount of free storage capacity on the disk is less than 25 MB. When reaching 10 MB, execution of RAPID programs will be stopped. Consequences The disk memory is close to being completely full. When this happens the system will not be able to function. Probable causes Too much data on the disk Recommended actions 1) Save the files on some other disk connected to the network. 2) Erase data from disk. 20193, Robot data update warning Description Axis sync values and service information data (SIS) was restored from backup. The system independent robot data was not saved during system shutdown. The data was restored from latest backup. Recommended actions Make sure there is free memory left on the device. The backup battery may be drained. Check the hardware log. 20194, System data backup could not be created Description The system was restored successfully but a backup of the current system data could not be created. Recommended actions Make sure there is free memory left on the device arg . 20195, System data from last shutdown is lost Description Normally, all system data is saved on shutdown. During the last shutdown saving data has failed. The system has been started using last good system data saved earlier at arg . Consequences Any changes made in system configuration or RAPID programs since arg will NOT be available after restart. Any such changes will have to be re-implemented. Probable causes The backup energy bank may have been drained at the time of the shut down. The storage disk may be full. Recommended actions 1) Check other event log messages occurring at the same time to determine the actual cause. 2) If acceptable, perform a B-restart to accept starting with the loaded system data. 3) Reinstall the system. 4) Check the available disk storage capacity. If required, erase data to increase free storage capacity. 20196, Module saved Description During reconfiguration of the system a changed and not saved module was found. The module was saved to arg . 6 Trouble shooting by Event log 115 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 20197, System data from last shutdown can not be found Description Normally, all system data is saved on shutdown. The file containing system persistent data cannot be found. The system has been started using last good system data saved earlier at arg . Consequences Any changes made in system configuration or RAPID programs since arg will NOT be available after restart. Any such changes will have to be re-implemented. Probable causes The file containing the saved system data may have been manually moved or deleted. Recommended actions 1) Check the location and availability of the saved system data file. 2) If acceptable, perform a B-restart to accept starting with the loaded last good system data. 3) Reinstall the system. 20199, System SoftStop Rejected Description The System Input SoftStop is not allowed Recommended actions 20200, Limit Switch opened by SC Description The limit switch on the robot has been opened by the Safety Controller (SC) Consequences The system goes to the Guard stop state. Probable causes The Safety Controller has opened the limit switch because of a safety violation. Recommended actions 1) Check for reason found in other event logs. 2)Check the cable between the contactor board and the Safety Controller 3)Do a Confirm Stop by pressing the Motors on push button or by activating the appropriated system input. 20201, Limit Switch open Description The limit switch on the robot has opened. Consequences The system goes to the Motors OFF status. Probable causes The robot has been run outside the working range defined by the limit switches fitted to the robot. Recommended actions 1) Press an eventual existing external "Override Limit" button and manually jog the robot back into the working area. 2) Resume operation. 20202, Emergency Stop open Description The emergency stop circuit has previously been broken, and while broken, an attempt was made to operate the robot. Consequences The system remains in the Emergency Stop status. Probable causes An attempt has been made to manoeuvre a control, e.g. the enabling device. Recommended actions 1) To resume operation, first reset the emergency stop button triggering the stop. 2) Then switch the system back to state Motors ON by pressing the Motors ON button on the Control Module. 20203, Enabling Device open Description Only one of the two Enabling Device chains was opened. Consequences The system goes to status SYS HALT. Probable causes The teach pendant Enabling Device may be faulty or incorrectly connected. The teach pendant and its Enabling Device is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check the teach pendant cable and its connection. 2) If required, replace the faulty teach pendant or its cable. 20204, Operation Key imbalance Description The system has detected an imbalance in the two parallel MANUAL / AUTO Operation Key circuits. Probable causes The contact pair in any of the cables connected to the Operation Key circuit is not working correctly.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	117	6 Trouble shooting by Event log 114 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20188, System data is not valid Description The contents of the file, arg , containing system persistent data is invalid. Internal error code: arg . The system has been started using last good system data saved earlier at arg . Consequences Any changes made in the system configuration or RAPID programs since arg will NOT be available after restart. Any such changes will have to be re-implemented. Recommended actions 1) Check other event log messages occurring at the same time to determine the actual cause. 2) If acceptable, perform a B-restart to accept starting with the loaded last good system data. 3) Reinstall the system. 4) Check the available disk storage capacity. If required, erase data to increase free storage capacity. 20189, Robot data not valid Description Could not load the system independent robot data from file arg . The file exists but the content is not valid. Internal code: arg Recommended actions Check other logged messages for needed actions. Make sure there is free memory left on the device. 20192, Disk memory low Description The amount of free storage capacity on the disk is less than 25 MB. When reaching 10 MB, execution of RAPID programs will be stopped. Consequences The disk memory is close to being completely full. When this happens the system will not be able to function. Probable causes Too much data on the disk Recommended actions 1) Save the files on some other disk connected to the network. 2) Erase data from disk. 20193, Robot data update warning Description Axis sync values and service information data (SIS) was restored from backup. The system independent robot data was not saved during system shutdown. The data was restored from latest backup. Recommended actions Make sure there is free memory left on the device. The backup battery may be drained. Check the hardware log. 20194, System data backup could not be created Description The system was restored successfully but a backup of the current system data could not be created. Recommended actions Make sure there is free memory left on the device arg . 20195, System data from last shutdown is lost Description Normally, all system data is saved on shutdown. During the last shutdown saving data has failed. The system has been started using last good system data saved earlier at arg . Consequences Any changes made in system configuration or RAPID programs since arg will NOT be available after restart. Any such changes will have to be re-implemented. Probable causes The backup energy bank may have been drained at the time of the shut down. The storage disk may be full. Recommended actions 1) Check other event log messages occurring at the same time to determine the actual cause. 2) If acceptable, perform a B-restart to accept starting with the loaded system data. 3) Reinstall the system. 4) Check the available disk storage capacity. If required, erase data to increase free storage capacity. 20196, Module saved Description During reconfiguration of the system a changed and not saved module was found. The module was saved to arg . 6 Trouble shooting by Event log 115 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 20197, System data from last shutdown can not be found Description Normally, all system data is saved on shutdown. The file containing system persistent data cannot be found. The system has been started using last good system data saved earlier at arg . Consequences Any changes made in system configuration or RAPID programs since arg will NOT be available after restart. Any such changes will have to be re-implemented. Probable causes The file containing the saved system data may have been manually moved or deleted. Recommended actions 1) Check the location and availability of the saved system data file. 2) If acceptable, perform a B-restart to accept starting with the loaded last good system data. 3) Reinstall the system. 20199, System SoftStop Rejected Description The System Input SoftStop is not allowed Recommended actions 20200, Limit Switch opened by SC Description The limit switch on the robot has been opened by the Safety Controller (SC) Consequences The system goes to the Guard stop state. Probable causes The Safety Controller has opened the limit switch because of a safety violation. Recommended actions 1) Check for reason found in other event logs. 2)Check the cable between the contactor board and the Safety Controller 3)Do a Confirm Stop by pressing the Motors on push button or by activating the appropriated system input. 20201, Limit Switch open Description The limit switch on the robot has opened. Consequences The system goes to the Motors OFF status. Probable causes The robot has been run outside the working range defined by the limit switches fitted to the robot. Recommended actions 1) Press an eventual existing external "Override Limit" button and manually jog the robot back into the working area. 2) Resume operation. 20202, Emergency Stop open Description The emergency stop circuit has previously been broken, and while broken, an attempt was made to operate the robot. Consequences The system remains in the Emergency Stop status. Probable causes An attempt has been made to manoeuvre a control, e.g. the enabling device. Recommended actions 1) To resume operation, first reset the emergency stop button triggering the stop. 2) Then switch the system back to state Motors ON by pressing the Motors ON button on the Control Module. 20203, Enabling Device open Description Only one of the two Enabling Device chains was opened. Consequences The system goes to status SYS HALT. Probable causes The teach pendant Enabling Device may be faulty or incorrectly connected. The teach pendant and its Enabling Device is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check the teach pendant cable and its connection. 2) If required, replace the faulty teach pendant or its cable. 20204, Operation Key imbalance Description The system has detected an imbalance in the two parallel MANUAL / AUTO Operation Key circuits. Probable causes The contact pair in any of the cables connected to the Operation Key circuit is not working correctly. 6 Trouble shooting by Event log 116 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Isolate the cable connection causing the conflict 2) Connect the cable in a correct way 20205, Auto Stop open Description The Automatic Mode Safeguarded Stop circuit has been broken. Consequences The system goes to the Auto Stop status. Probable causes One or more of the switch connected in series with the Automatic Mode Safeguarded Stop circuit have been opened, which may be causes by a large number of faults. This is only possible while in the Auto operational mode. The Automatic Mode Safeguarded Stop circuit is described in the Trouble Shooting Manual. Recommended actions 1) Locate the switch, reset it and restart the system. 2) Check cables and connections. 20206, General Stop open Description The General Mode Safeguarded Stop circuit has been broken. Consequences The system goes to the General Stop status. Probable causes One or more of the switch connected in series with the General Mode Safeguarded Stop circuit have been opened, which may be causes by a large number of faults. This is possible in any operational mode. The General Mode Safeguarded Stop circuit is described in the Trouble Shooting Manual. Recommended actions 1) Locate the switch, reset it and restart the system. 2) Check cables and connections. 20208, Chain switches open Description A safety chain, other than Auto Stop and General Stop, has been broken. Consequences The system goes to the Guard Stop status. Probable causes One or more of the switch connected in series with the RUN Chain Top circuit have been opened, which may be causes by a large number of faults. The RUN Chain Top is described in the Trouble Shooting Manual and Circuit Diagram. Recommended actions 1) Check other error messages for primary fault reason. 2) Locate the switch, reset it and restart the system. 3) Check cables and connections. 20209, External Contactor open Description An external contactor has been opened. Consequences The system goes from the Motors OFF status to SYS HALT when attempting to start. Probable causes The RUN chain of external equipment has been broken, which may be caused by the external contactor auxiliary contacts or, if used, any PLC, controlling it. The external contactor supplies power to a piece of external equipment, equivalently to how the RUN contactor supplies a robot. This fault may occur when attempting to go to the Motors ON mode only. The RUN chain is described in the Trouble Shooting Manual and Circuit Diagram. Recommended actions 1) Locate the switch, reset it and restart the system. 2) Check cables and connections. 3) Check the external contactor auxiliary contacts. 4) If used, check any PLC equipment controlling the external contactor. 20211, Two channel fault, ENABLE chain Description A switch in only one of the two ENABLE chains was briefly affected, opening the chain and then reclosing it, without the other chain being affected. Consequences The system goes to status SYS HALT. Probable causes There may be a loose signal connection on either the axis computer or the Safety System. The ENABLE chain is described in the Trouble Shooting Manual and Circuit Diagram. Recommended actions 1) Check cables and connections. 2) Make sure all signal connectors on the axis computer board and the Safety System are securely connected. 3) If there is no loose connection, replace the faulty board. 20212, Two channel fault, RUN CHAIN Description Only one of the two RUN chains was closed.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	118	6 Trouble shooting by Event log 115 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 20197, System data from last shutdown can not be found Description Normally, all system data is saved on shutdown. The file containing system persistent data cannot be found. The system has been started using last good system data saved earlier at arg . Consequences Any changes made in system configuration or RAPID programs since arg will NOT be available after restart. Any such changes will have to be re-implemented. Probable causes The file containing the saved system data may have been manually moved or deleted. Recommended actions 1) Check the location and availability of the saved system data file. 2) If acceptable, perform a B-restart to accept starting with the loaded last good system data. 3) Reinstall the system. 20199, System SoftStop Rejected Description The System Input SoftStop is not allowed Recommended actions 20200, Limit Switch opened by SC Description The limit switch on the robot has been opened by the Safety Controller (SC) Consequences The system goes to the Guard stop state. Probable causes The Safety Controller has opened the limit switch because of a safety violation. Recommended actions 1) Check for reason found in other event logs. 2)Check the cable between the contactor board and the Safety Controller 3)Do a Confirm Stop by pressing the Motors on push button or by activating the appropriated system input. 20201, Limit Switch open Description The limit switch on the robot has opened. Consequences The system goes to the Motors OFF status. Probable causes The robot has been run outside the working range defined by the limit switches fitted to the robot. Recommended actions 1) Press an eventual existing external "Override Limit" button and manually jog the robot back into the working area. 2) Resume operation. 20202, Emergency Stop open Description The emergency stop circuit has previously been broken, and while broken, an attempt was made to operate the robot. Consequences The system remains in the Emergency Stop status. Probable causes An attempt has been made to manoeuvre a control, e.g. the enabling device. Recommended actions 1) To resume operation, first reset the emergency stop button triggering the stop. 2) Then switch the system back to state Motors ON by pressing the Motors ON button on the Control Module. 20203, Enabling Device open Description Only one of the two Enabling Device chains was opened. Consequences The system goes to status SYS HALT. Probable causes The teach pendant Enabling Device may be faulty or incorrectly connected. The teach pendant and its Enabling Device is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check the teach pendant cable and its connection. 2) If required, replace the faulty teach pendant or its cable. 20204, Operation Key imbalance Description The system has detected an imbalance in the two parallel MANUAL / AUTO Operation Key circuits. Probable causes The contact pair in any of the cables connected to the Operation Key circuit is not working correctly. 6 Trouble shooting by Event log 116 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Isolate the cable connection causing the conflict 2) Connect the cable in a correct way 20205, Auto Stop open Description The Automatic Mode Safeguarded Stop circuit has been broken. Consequences The system goes to the Auto Stop status. Probable causes One or more of the switch connected in series with the Automatic Mode Safeguarded Stop circuit have been opened, which may be causes by a large number of faults. This is only possible while in the Auto operational mode. The Automatic Mode Safeguarded Stop circuit is described in the Trouble Shooting Manual. Recommended actions 1) Locate the switch, reset it and restart the system. 2) Check cables and connections. 20206, General Stop open Description The General Mode Safeguarded Stop circuit has been broken. Consequences The system goes to the General Stop status. Probable causes One or more of the switch connected in series with the General Mode Safeguarded Stop circuit have been opened, which may be causes by a large number of faults. This is possible in any operational mode. The General Mode Safeguarded Stop circuit is described in the Trouble Shooting Manual. Recommended actions 1) Locate the switch, reset it and restart the system. 2) Check cables and connections. 20208, Chain switches open Description A safety chain, other than Auto Stop and General Stop, has been broken. Consequences The system goes to the Guard Stop status. Probable causes One or more of the switch connected in series with the RUN Chain Top circuit have been opened, which may be causes by a large number of faults. The RUN Chain Top is described in the Trouble Shooting Manual and Circuit Diagram. Recommended actions 1) Check other error messages for primary fault reason. 2) Locate the switch, reset it and restart the system. 3) Check cables and connections. 20209, External Contactor open Description An external contactor has been opened. Consequences The system goes from the Motors OFF status to SYS HALT when attempting to start. Probable causes The RUN chain of external equipment has been broken, which may be caused by the external contactor auxiliary contacts or, if used, any PLC, controlling it. The external contactor supplies power to a piece of external equipment, equivalently to how the RUN contactor supplies a robot. This fault may occur when attempting to go to the Motors ON mode only. The RUN chain is described in the Trouble Shooting Manual and Circuit Diagram. Recommended actions 1) Locate the switch, reset it and restart the system. 2) Check cables and connections. 3) Check the external contactor auxiliary contacts. 4) If used, check any PLC equipment controlling the external contactor. 20211, Two channel fault, ENABLE chain Description A switch in only one of the two ENABLE chains was briefly affected, opening the chain and then reclosing it, without the other chain being affected. Consequences The system goes to status SYS HALT. Probable causes There may be a loose signal connection on either the axis computer or the Safety System. The ENABLE chain is described in the Trouble Shooting Manual and Circuit Diagram. Recommended actions 1) Check cables and connections. 2) Make sure all signal connectors on the axis computer board and the Safety System are securely connected. 3) If there is no loose connection, replace the faulty board. 20212, Two channel fault, RUN CHAIN Description Only one of the two RUN chains was closed. 6 Trouble shooting by Event log 117 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences The system goes to status SYS HALT. Probable causes Any of the switches connected to the RUN chain may be faulty or not correctly connected, causing only one channel to close. The RUN chain is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine which switch caused the fault. 3) Make sure all switches are working correctly. 4) To assist in returning the chains to a defined status, first pressing, then resetting the Emergency Stop 5) If there is no loose connection, replace the faulty switch. 20213, Two channel fault Description A brief status change in any of the RUN or ENABLE chains has been detected. Consequences The system goes to status SYS HALT. Probable causes This may be caused by a number of faults. The ENABLE and RUN chains are described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine the cause of the fault. 3) To assist in returning the chains to a defined status, first pressing, then resetting the Emergency Stop may work. 20214, Limit Switch open, DRV1 Description The limit switch on the robot has opened. Consequences The system goes to the Motors OFF status. Probable causes The robot has been run outside the working range defined by the limit switches fitted to the robot. Recommended actions 1) Press an eventual existing external "Override Limit" button and manually jog the robot back into the working area. 2) Resume operation. 20215, Superior Stop open Description The Superior Mode Safeguarded Stop circuit has been opened. Consequences The system goes to the Superior Stop status. Probable causes One or more of the switch connected in series with the Superior Mode Safeguarded Stop circuit have been opened, which may be causes by a large number of faults. This is possible in any operational mode. The Superior Mode Safeguarded Stop circuit is described in the Trouble Shooting Manual. Recommended actions 1) Locate the switch, reset it and restart the system. 20216, Enabling device active in Auto mode Description The system has detected that the Enabling device has been pressed for more than 3 seconds in Automatic operating mode. Consequences The system goes to status Guard Stop. Recommended actions 1. Release the Enabling device 2. Switch to Manual mode 20217, Limit Switch open, DRV2 Description The limit switch on the robot has opened. Consequences The system goes to the Motors OFF status. Probable causes The robot has been run outside the working range defined by the limit switches fitted to the robot. Recommended actions 1) Press an eventual existing external "Override Limit" button and manually jog the robot back into the working area. 2) Resume operation. 20218, Limit Switch open, DRV3 Description The limit switch on the robot has opened. Consequences The system goes to the Motors OFF status.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	119	6 Trouble shooting by Event log 116 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Isolate the cable connection causing the conflict 2) Connect the cable in a correct way 20205, Auto Stop open Description The Automatic Mode Safeguarded Stop circuit has been broken. Consequences The system goes to the Auto Stop status. Probable causes One or more of the switch connected in series with the Automatic Mode Safeguarded Stop circuit have been opened, which may be causes by a large number of faults. This is only possible while in the Auto operational mode. The Automatic Mode Safeguarded Stop circuit is described in the Trouble Shooting Manual. Recommended actions 1) Locate the switch, reset it and restart the system. 2) Check cables and connections. 20206, General Stop open Description The General Mode Safeguarded Stop circuit has been broken. Consequences The system goes to the General Stop status. Probable causes One or more of the switch connected in series with the General Mode Safeguarded Stop circuit have been opened, which may be causes by a large number of faults. This is possible in any operational mode. The General Mode Safeguarded Stop circuit is described in the Trouble Shooting Manual. Recommended actions 1) Locate the switch, reset it and restart the system. 2) Check cables and connections. 20208, Chain switches open Description A safety chain, other than Auto Stop and General Stop, has been broken. Consequences The system goes to the Guard Stop status. Probable causes One or more of the switch connected in series with the RUN Chain Top circuit have been opened, which may be causes by a large number of faults. The RUN Chain Top is described in the Trouble Shooting Manual and Circuit Diagram. Recommended actions 1) Check other error messages for primary fault reason. 2) Locate the switch, reset it and restart the system. 3) Check cables and connections. 20209, External Contactor open Description An external contactor has been opened. Consequences The system goes from the Motors OFF status to SYS HALT when attempting to start. Probable causes The RUN chain of external equipment has been broken, which may be caused by the external contactor auxiliary contacts or, if used, any PLC, controlling it. The external contactor supplies power to a piece of external equipment, equivalently to how the RUN contactor supplies a robot. This fault may occur when attempting to go to the Motors ON mode only. The RUN chain is described in the Trouble Shooting Manual and Circuit Diagram. Recommended actions 1) Locate the switch, reset it and restart the system. 2) Check cables and connections. 3) Check the external contactor auxiliary contacts. 4) If used, check any PLC equipment controlling the external contactor. 20211, Two channel fault, ENABLE chain Description A switch in only one of the two ENABLE chains was briefly affected, opening the chain and then reclosing it, without the other chain being affected. Consequences The system goes to status SYS HALT. Probable causes There may be a loose signal connection on either the axis computer or the Safety System. The ENABLE chain is described in the Trouble Shooting Manual and Circuit Diagram. Recommended actions 1) Check cables and connections. 2) Make sure all signal connectors on the axis computer board and the Safety System are securely connected. 3) If there is no loose connection, replace the faulty board. 20212, Two channel fault, RUN CHAIN Description Only one of the two RUN chains was closed. 6 Trouble shooting by Event log 117 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences The system goes to status SYS HALT. Probable causes Any of the switches connected to the RUN chain may be faulty or not correctly connected, causing only one channel to close. The RUN chain is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine which switch caused the fault. 3) Make sure all switches are working correctly. 4) To assist in returning the chains to a defined status, first pressing, then resetting the Emergency Stop 5) If there is no loose connection, replace the faulty switch. 20213, Two channel fault Description A brief status change in any of the RUN or ENABLE chains has been detected. Consequences The system goes to status SYS HALT. Probable causes This may be caused by a number of faults. The ENABLE and RUN chains are described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine the cause of the fault. 3) To assist in returning the chains to a defined status, first pressing, then resetting the Emergency Stop may work. 20214, Limit Switch open, DRV1 Description The limit switch on the robot has opened. Consequences The system goes to the Motors OFF status. Probable causes The robot has been run outside the working range defined by the limit switches fitted to the robot. Recommended actions 1) Press an eventual existing external "Override Limit" button and manually jog the robot back into the working area. 2) Resume operation. 20215, Superior Stop open Description The Superior Mode Safeguarded Stop circuit has been opened. Consequences The system goes to the Superior Stop status. Probable causes One or more of the switch connected in series with the Superior Mode Safeguarded Stop circuit have been opened, which may be causes by a large number of faults. This is possible in any operational mode. The Superior Mode Safeguarded Stop circuit is described in the Trouble Shooting Manual. Recommended actions 1) Locate the switch, reset it and restart the system. 20216, Enabling device active in Auto mode Description The system has detected that the Enabling device has been pressed for more than 3 seconds in Automatic operating mode. Consequences The system goes to status Guard Stop. Recommended actions 1. Release the Enabling device 2. Switch to Manual mode 20217, Limit Switch open, DRV2 Description The limit switch on the robot has opened. Consequences The system goes to the Motors OFF status. Probable causes The robot has been run outside the working range defined by the limit switches fitted to the robot. Recommended actions 1) Press an eventual existing external "Override Limit" button and manually jog the robot back into the working area. 2) Resume operation. 20218, Limit Switch open, DRV3 Description The limit switch on the robot has opened. Consequences The system goes to the Motors OFF status. 6 Trouble shooting by Event log 118 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes The robot has been run outside the working range defined by the limit switches fitted to the robot. Recommended actions 1) Press an eventual existing external "Override Limit" button and manually jog the robot back into the working area. 2) Resume operation. 20219, Limit Switch open, DRV4 Description The limit switch on the robot has opened. Consequences The system goes to the Motors OFF status. Probable causes The robot has been run outside the working range defined by the limit switches fitted to the robot. Recommended actions 1) Press an eventual existing external "Override Limit" button and manually jog the robot back into the working area. 2) Resume operation. 20220, Superior stop conflict Description Only one of the two Superior Mode Safeguarded Stop chains was opened. Consequences The system goes to status SYS HALT. Probable causes Any of the switches connected to the Superior Stop chain may be faulty or not correctly connected, causing only one channel to close. The Superior Stop chain is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine which switch caused the fault. 3) Make sure all switches are working correctly. 4) If there is no loose connection, replace the faulty switch. 20221, Run chain conflict Description Status conflict for Run chain. Recommended actions Please check the Run chain cables. 20222, Limit switch conflict Description Only one of the two Limit switch chains was opened. Consequences The system goes to status SYS HALT. Probable causes Any of the switches connected to the Limit switch chain may be faulty or not correctly connected, causing only one channel to close. The Limit switch chain is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine which switch caused the fault. 3) Make sure all switches are working correctly. 4) If there is no loose connection, replace the faulty switch. 20223, Emergency Stop conflict Description Only one of the two Emergency Stop chains was opened. Consequences The system goes to status SYS HALT. Probable causes Any of the switches connected to the Emergency Stop chain may be faulty or not correctly connected, causing only one channel to close. The Emergency Stop chain is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine which switch caused the fault. 3) Make sure all switches are working correctly. 4) If there is no loose connection, replace the faulty switch. 20224, Enabling Device conflict Description Only one of the two Enabling Device chains was opened. Consequences The system goes to status SYS HALT. Probable causes The teach pendant Enabling Device may be faulty or incorrectly connected. The teach pendant and its Enabling Device is described in the Trouble Shooting Manual, IRC5.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	120	6 Trouble shooting by Event log 117 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences The system goes to status SYS HALT. Probable causes Any of the switches connected to the RUN chain may be faulty or not correctly connected, causing only one channel to close. The RUN chain is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine which switch caused the fault. 3) Make sure all switches are working correctly. 4) To assist in returning the chains to a defined status, first pressing, then resetting the Emergency Stop 5) If there is no loose connection, replace the faulty switch. 20213, Two channel fault Description A brief status change in any of the RUN or ENABLE chains has been detected. Consequences The system goes to status SYS HALT. Probable causes This may be caused by a number of faults. The ENABLE and RUN chains are described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine the cause of the fault. 3) To assist in returning the chains to a defined status, first pressing, then resetting the Emergency Stop may work. 20214, Limit Switch open, DRV1 Description The limit switch on the robot has opened. Consequences The system goes to the Motors OFF status. Probable causes The robot has been run outside the working range defined by the limit switches fitted to the robot. Recommended actions 1) Press an eventual existing external "Override Limit" button and manually jog the robot back into the working area. 2) Resume operation. 20215, Superior Stop open Description The Superior Mode Safeguarded Stop circuit has been opened. Consequences The system goes to the Superior Stop status. Probable causes One or more of the switch connected in series with the Superior Mode Safeguarded Stop circuit have been opened, which may be causes by a large number of faults. This is possible in any operational mode. The Superior Mode Safeguarded Stop circuit is described in the Trouble Shooting Manual. Recommended actions 1) Locate the switch, reset it and restart the system. 20216, Enabling device active in Auto mode Description The system has detected that the Enabling device has been pressed for more than 3 seconds in Automatic operating mode. Consequences The system goes to status Guard Stop. Recommended actions 1. Release the Enabling device 2. Switch to Manual mode 20217, Limit Switch open, DRV2 Description The limit switch on the robot has opened. Consequences The system goes to the Motors OFF status. Probable causes The robot has been run outside the working range defined by the limit switches fitted to the robot. Recommended actions 1) Press an eventual existing external "Override Limit" button and manually jog the robot back into the working area. 2) Resume operation. 20218, Limit Switch open, DRV3 Description The limit switch on the robot has opened. Consequences The system goes to the Motors OFF status. 6 Trouble shooting by Event log 118 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes The robot has been run outside the working range defined by the limit switches fitted to the robot. Recommended actions 1) Press an eventual existing external "Override Limit" button and manually jog the robot back into the working area. 2) Resume operation. 20219, Limit Switch open, DRV4 Description The limit switch on the robot has opened. Consequences The system goes to the Motors OFF status. Probable causes The robot has been run outside the working range defined by the limit switches fitted to the robot. Recommended actions 1) Press an eventual existing external "Override Limit" button and manually jog the robot back into the working area. 2) Resume operation. 20220, Superior stop conflict Description Only one of the two Superior Mode Safeguarded Stop chains was opened. Consequences The system goes to status SYS HALT. Probable causes Any of the switches connected to the Superior Stop chain may be faulty or not correctly connected, causing only one channel to close. The Superior Stop chain is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine which switch caused the fault. 3) Make sure all switches are working correctly. 4) If there is no loose connection, replace the faulty switch. 20221, Run chain conflict Description Status conflict for Run chain. Recommended actions Please check the Run chain cables. 20222, Limit switch conflict Description Only one of the two Limit switch chains was opened. Consequences The system goes to status SYS HALT. Probable causes Any of the switches connected to the Limit switch chain may be faulty or not correctly connected, causing only one channel to close. The Limit switch chain is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine which switch caused the fault. 3) Make sure all switches are working correctly. 4) If there is no loose connection, replace the faulty switch. 20223, Emergency Stop conflict Description Only one of the two Emergency Stop chains was opened. Consequences The system goes to status SYS HALT. Probable causes Any of the switches connected to the Emergency Stop chain may be faulty or not correctly connected, causing only one channel to close. The Emergency Stop chain is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine which switch caused the fault. 3) Make sure all switches are working correctly. 4) If there is no loose connection, replace the faulty switch. 20224, Enabling Device conflict Description Only one of the two Enabling Device chains was opened. Consequences The system goes to status SYS HALT. Probable causes The teach pendant Enabling Device may be faulty or incorrectly connected. The teach pendant and its Enabling Device is described in the Trouble Shooting Manual, IRC5. 6 Trouble shooting by Event log 119 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Check the teach pendant cable and its connection. 2) If required, replace the faulty teach pendant or its cable. 20225, Auto Stop conflict Description Only one of the two Automatic Mode Safeguarded Stop chains was opened. Consequences The system goes to status SYS HALT. Probable causes Any of the switches connected to the Auto Stop chain may be faulty or not correctly connected, causing only one channel to close. The Auto Stop chain is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine which switch caused the fault. 3) Make sure all switches are working correctly. 4) If there is no loose connection, replace the faulty switch. 20226, General Stop conflict Description Only one of the two General Mode Safeguarded Stop chains was opened. Consequences The system goes to status SYS HALT. Probable causes Any of the switches connected to the General Stop chain may be faulty or not correctly connected, causing only one channel to close. The General Stop chain is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine which switch caused the fault. 3) Make sure all switches are working correctly. 4) If there is no loose connection, replace the faulty switch. 20227, Motor Contactor conflict, DRV1 Description Only one of the two Motor Contactors for drive system 1 has acknowledged the activation order. Consequences The system goes to status SYS HALT. Probable causes A failure of the motor contactor auxiliary contacts or the supply to these. Recommended actions 1) Check cables and connections. 2) Check the function of the auxiliary contacts. 20231, Delayed Emergency Stop due to circuit imbalance Description The system has detected an imbalance in the two parallel Emergency Stop circuits. Consequences The system goes to status Emergency Stop after approximately 1 sec. Probable causes The contact pair in any of the Emergency Stop buttons is not working correctly. Recommended actions 1. Isolate the Emergency Stop button causing the conflict. 2. Check the contact pair. 3. Make sure all connections are tight. 4. Replace the button if required. 20232, Delayed Auto Stop due to circuit imbalance Description The system has detected an imbalance in the two parallel Auto Stop circuits. Consequences The system goes to status Guard Stop after approximately 1 sec. Probable causes The contact pair in any of the safety devices connected to the Auto Stop circuit is not working correctly. Recommended actions 1. Isolate the safety device causing the conflict. 2. Make sure the device used is a two-channel device. 3. Check the contact pair. 4. Make sure all connections are tight. 5. Replace the device if required. 20233, Delayed General Stop due to circuit imbalance Description The system has detected an imbalance in the two parallel General Stop circuits.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	121	6 Trouble shooting by Event log 118 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes The robot has been run outside the working range defined by the limit switches fitted to the robot. Recommended actions 1) Press an eventual existing external "Override Limit" button and manually jog the robot back into the working area. 2) Resume operation. 20219, Limit Switch open, DRV4 Description The limit switch on the robot has opened. Consequences The system goes to the Motors OFF status. Probable causes The robot has been run outside the working range defined by the limit switches fitted to the robot. Recommended actions 1) Press an eventual existing external "Override Limit" button and manually jog the robot back into the working area. 2) Resume operation. 20220, Superior stop conflict Description Only one of the two Superior Mode Safeguarded Stop chains was opened. Consequences The system goes to status SYS HALT. Probable causes Any of the switches connected to the Superior Stop chain may be faulty or not correctly connected, causing only one channel to close. The Superior Stop chain is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine which switch caused the fault. 3) Make sure all switches are working correctly. 4) If there is no loose connection, replace the faulty switch. 20221, Run chain conflict Description Status conflict for Run chain. Recommended actions Please check the Run chain cables. 20222, Limit switch conflict Description Only one of the two Limit switch chains was opened. Consequences The system goes to status SYS HALT. Probable causes Any of the switches connected to the Limit switch chain may be faulty or not correctly connected, causing only one channel to close. The Limit switch chain is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine which switch caused the fault. 3) Make sure all switches are working correctly. 4) If there is no loose connection, replace the faulty switch. 20223, Emergency Stop conflict Description Only one of the two Emergency Stop chains was opened. Consequences The system goes to status SYS HALT. Probable causes Any of the switches connected to the Emergency Stop chain may be faulty or not correctly connected, causing only one channel to close. The Emergency Stop chain is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine which switch caused the fault. 3) Make sure all switches are working correctly. 4) If there is no loose connection, replace the faulty switch. 20224, Enabling Device conflict Description Only one of the two Enabling Device chains was opened. Consequences The system goes to status SYS HALT. Probable causes The teach pendant Enabling Device may be faulty or incorrectly connected. The teach pendant and its Enabling Device is described in the Trouble Shooting Manual, IRC5. 6 Trouble shooting by Event log 119 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Check the teach pendant cable and its connection. 2) If required, replace the faulty teach pendant or its cable. 20225, Auto Stop conflict Description Only one of the two Automatic Mode Safeguarded Stop chains was opened. Consequences The system goes to status SYS HALT. Probable causes Any of the switches connected to the Auto Stop chain may be faulty or not correctly connected, causing only one channel to close. The Auto Stop chain is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine which switch caused the fault. 3) Make sure all switches are working correctly. 4) If there is no loose connection, replace the faulty switch. 20226, General Stop conflict Description Only one of the two General Mode Safeguarded Stop chains was opened. Consequences The system goes to status SYS HALT. Probable causes Any of the switches connected to the General Stop chain may be faulty or not correctly connected, causing only one channel to close. The General Stop chain is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine which switch caused the fault. 3) Make sure all switches are working correctly. 4) If there is no loose connection, replace the faulty switch. 20227, Motor Contactor conflict, DRV1 Description Only one of the two Motor Contactors for drive system 1 has acknowledged the activation order. Consequences The system goes to status SYS HALT. Probable causes A failure of the motor contactor auxiliary contacts or the supply to these. Recommended actions 1) Check cables and connections. 2) Check the function of the auxiliary contacts. 20231, Delayed Emergency Stop due to circuit imbalance Description The system has detected an imbalance in the two parallel Emergency Stop circuits. Consequences The system goes to status Emergency Stop after approximately 1 sec. Probable causes The contact pair in any of the Emergency Stop buttons is not working correctly. Recommended actions 1. Isolate the Emergency Stop button causing the conflict. 2. Check the contact pair. 3. Make sure all connections are tight. 4. Replace the button if required. 20232, Delayed Auto Stop due to circuit imbalance Description The system has detected an imbalance in the two parallel Auto Stop circuits. Consequences The system goes to status Guard Stop after approximately 1 sec. Probable causes The contact pair in any of the safety devices connected to the Auto Stop circuit is not working correctly. Recommended actions 1. Isolate the safety device causing the conflict. 2. Make sure the device used is a two-channel device. 3. Check the contact pair. 4. Make sure all connections are tight. 5. Replace the device if required. 20233, Delayed General Stop due to circuit imbalance Description The system has detected an imbalance in the two parallel General Stop circuits. 6 Trouble shooting by Event log 120 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences The system goes to status Guard Stop after approximately 1 sec. Probable causes The contact pair in any of the safety devices connected to the General Stop circuit is not working correctly. Recommended actions 1. Isolate the safety device causing the conflict. 2. Make sure the device used is a two-channel device. 3. Check the contact pair. 4. Make sure all connections are tight. 5. Replace the device if required. 20234, Immediate Emergency Stop Description The Emergency Stop circuits have been broken. Consequences The system goes directly to status Emergency Stop. Probable causes One or more of the red emergency stop buttons have been activated. Recommended actions 1) Isolate the Emergency Stop button that was opened. 2) Reset the button. 20235, Immediate Auto Stop Description The Auto Stop circuits have been broken. Consequences The system goes directly to status Guard Stop. Probable causes One or more of the safety device switches in the Auto Stop circuit have been opened Recommended actions 1) Isolate the safety device that was opened 2) Reset the device switch. 20236, Immediate General Stop Description The General Stop circuits have been broken. Consequences The system goes directly to status Guard Stop. Probable causes One or more of the safety device switches in the General Stop circuit have been opened Recommended actions 1) Isolate the safety device that was opened 2) Reset the device switch. 20237, Immediate Superior Stop Description The Superior Stop circuits have been broken. Consequences The system goes directly to status Guard Stop. Probable causes One or more of the safety device switches in the Superior Stop circuit have been opened Recommended actions 1) Isolate the safety device that was opened 2) Reset the device switch. 20238, Delayed Superior Stop due to circuit imbalance Description The system has detected an imbalance in the two parallel Superior Stop circuits. Consequences The system goes to status Guard Stop after approximately 1 sec. Probable causes The contact pair in any of the safety devices connected to the Superior Stop circuit is not working correctly. Recommended actions 1. Isolate the safety device causing the conflict. 2. Make sure the device used is a two-channel device. 3. Check the contact pair. 4. Make sure all connections are tight. 5. Replace the device if required. 20240, Conflict between ENABLE signals Description A switch in only one of the two ENABLE chains was affected, without the other chain being affected. Consequences The system goes to status SYS HALT. Probable causes There may be a loose signal connection on the Safety System. The ENABLE chain is described in the Trouble Shooting Manual and Circuit Diagram. Recommended actions 1) Check cables and connections.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	122	6 Trouble shooting by Event log 119 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Check the teach pendant cable and its connection. 2) If required, replace the faulty teach pendant or its cable. 20225, Auto Stop conflict Description Only one of the two Automatic Mode Safeguarded Stop chains was opened. Consequences The system goes to status SYS HALT. Probable causes Any of the switches connected to the Auto Stop chain may be faulty or not correctly connected, causing only one channel to close. The Auto Stop chain is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine which switch caused the fault. 3) Make sure all switches are working correctly. 4) If there is no loose connection, replace the faulty switch. 20226, General Stop conflict Description Only one of the two General Mode Safeguarded Stop chains was opened. Consequences The system goes to status SYS HALT. Probable causes Any of the switches connected to the General Stop chain may be faulty or not correctly connected, causing only one channel to close. The General Stop chain is described in the Trouble Shooting Manual, IRC5. Recommended actions 1) Check cables and connections. 2) Check other event log messages occurring at the same time to determine which switch caused the fault. 3) Make sure all switches are working correctly. 4) If there is no loose connection, replace the faulty switch. 20227, Motor Contactor conflict, DRV1 Description Only one of the two Motor Contactors for drive system 1 has acknowledged the activation order. Consequences The system goes to status SYS HALT. Probable causes A failure of the motor contactor auxiliary contacts or the supply to these. Recommended actions 1) Check cables and connections. 2) Check the function of the auxiliary contacts. 20231, Delayed Emergency Stop due to circuit imbalance Description The system has detected an imbalance in the two parallel Emergency Stop circuits. Consequences The system goes to status Emergency Stop after approximately 1 sec. Probable causes The contact pair in any of the Emergency Stop buttons is not working correctly. Recommended actions 1. Isolate the Emergency Stop button causing the conflict. 2. Check the contact pair. 3. Make sure all connections are tight. 4. Replace the button if required. 20232, Delayed Auto Stop due to circuit imbalance Description The system has detected an imbalance in the two parallel Auto Stop circuits. Consequences The system goes to status Guard Stop after approximately 1 sec. Probable causes The contact pair in any of the safety devices connected to the Auto Stop circuit is not working correctly. Recommended actions 1. Isolate the safety device causing the conflict. 2. Make sure the device used is a two-channel device. 3. Check the contact pair. 4. Make sure all connections are tight. 5. Replace the device if required. 20233, Delayed General Stop due to circuit imbalance Description The system has detected an imbalance in the two parallel General Stop circuits. 6 Trouble shooting by Event log 120 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences The system goes to status Guard Stop after approximately 1 sec. Probable causes The contact pair in any of the safety devices connected to the General Stop circuit is not working correctly. Recommended actions 1. Isolate the safety device causing the conflict. 2. Make sure the device used is a two-channel device. 3. Check the contact pair. 4. Make sure all connections are tight. 5. Replace the device if required. 20234, Immediate Emergency Stop Description The Emergency Stop circuits have been broken. Consequences The system goes directly to status Emergency Stop. Probable causes One or more of the red emergency stop buttons have been activated. Recommended actions 1) Isolate the Emergency Stop button that was opened. 2) Reset the button. 20235, Immediate Auto Stop Description The Auto Stop circuits have been broken. Consequences The system goes directly to status Guard Stop. Probable causes One or more of the safety device switches in the Auto Stop circuit have been opened Recommended actions 1) Isolate the safety device that was opened 2) Reset the device switch. 20236, Immediate General Stop Description The General Stop circuits have been broken. Consequences The system goes directly to status Guard Stop. Probable causes One or more of the safety device switches in the General Stop circuit have been opened Recommended actions 1) Isolate the safety device that was opened 2) Reset the device switch. 20237, Immediate Superior Stop Description The Superior Stop circuits have been broken. Consequences The system goes directly to status Guard Stop. Probable causes One or more of the safety device switches in the Superior Stop circuit have been opened Recommended actions 1) Isolate the safety device that was opened 2) Reset the device switch. 20238, Delayed Superior Stop due to circuit imbalance Description The system has detected an imbalance in the two parallel Superior Stop circuits. Consequences The system goes to status Guard Stop after approximately 1 sec. Probable causes The contact pair in any of the safety devices connected to the Superior Stop circuit is not working correctly. Recommended actions 1. Isolate the safety device causing the conflict. 2. Make sure the device used is a two-channel device. 3. Check the contact pair. 4. Make sure all connections are tight. 5. Replace the device if required. 20240, Conflict between ENABLE signals Description A switch in only one of the two ENABLE chains was affected, without the other chain being affected. Consequences The system goes to status SYS HALT. Probable causes There may be a loose signal connection on the Safety System. The ENABLE chain is described in the Trouble Shooting Manual and Circuit Diagram. Recommended actions 1) Check cables and connections. 6 Trouble shooting by Event log 121 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 2) Make sure all signal connectors on the Safety System are securely connected. 3) If there is no loose connection, replace the faulty board. 20241, Operating mode conflict Description There is a conflict between the operating mode selected on the operating mode selector on the controller cabinet front and the actual operating mode as detected by the axis computer. Consequences The system goes to status SYS HALT. Probable causes There may be a hardware fault in the operating mode selector or its cabling to the Safety System. Recommended actions Check the operating mode selector and its cabling to the Safety System. 20245, Run Control status conflict, DRV2 Description Status conflict between Run Control and Motor Contactors for drive system 2. Consequences The system goes to status SYS HALT. Probable causes A failure of the Motor Contactors or the supply to these. Recommended actions 1) Check cables and connections. 2) Do a Warm start. 20246, Run Control status conflict, DRV3 Description Status conflict between Run Control and Motor Contactors for drive system 3. Consequences The system goes to status SYS HALT. Probable causes A failure of the Motor Contactors or the supply to these. Recommended actions 1) Check cables and connections. 2) Do a Warm start. 20247, Run Control status conflict, DRV4 Description Status conflict between Run Control and Motor Contactors for drive system 4. Consequences The system goes to status SYS HALT. Probable causes A failure of the Motor Contactors or the supply to these. Recommended actions 1) Check cables and connections. 2) Do a Warm start. 20248, Motor Contactor conflict, DRV2 Description Only one of the two Motor Contactors for drive system 2 has acknowledged the activation order. Consequences The system goes to status SYS HALT. Probable causes A failure of the motor contactor auxiliary contacts or the supply to these. Recommended actions 1) Check cables and connections. 2) Check the function of the auxiliary contacts. 20249, Motor Contactor conflict, DRV3 Description Only one of the two Motor Contactors for drive system 3 has acknowledged the activation order. Consequences The system goes to status SYS HALT. Probable causes A failure of the motor contactor auxiliary contacts or the supply to these. Recommended actions 1) Check cables and connections. 2) Check the function of the auxiliary contacts. 20250, Motor Contactor conflict, DRV4 Description Only one of the two Motor Contactors for drive system 4 has acknowledged the activation order. Consequences The system goes to status SYS HALT.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	123	6 Trouble shooting by Event log 120 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences The system goes to status Guard Stop after approximately 1 sec. Probable causes The contact pair in any of the safety devices connected to the General Stop circuit is not working correctly. Recommended actions 1. Isolate the safety device causing the conflict. 2. Make sure the device used is a two-channel device. 3. Check the contact pair. 4. Make sure all connections are tight. 5. Replace the device if required. 20234, Immediate Emergency Stop Description The Emergency Stop circuits have been broken. Consequences The system goes directly to status Emergency Stop. Probable causes One or more of the red emergency stop buttons have been activated. Recommended actions 1) Isolate the Emergency Stop button that was opened. 2) Reset the button. 20235, Immediate Auto Stop Description The Auto Stop circuits have been broken. Consequences The system goes directly to status Guard Stop. Probable causes One or more of the safety device switches in the Auto Stop circuit have been opened Recommended actions 1) Isolate the safety device that was opened 2) Reset the device switch. 20236, Immediate General Stop Description The General Stop circuits have been broken. Consequences The system goes directly to status Guard Stop. Probable causes One or more of the safety device switches in the General Stop circuit have been opened Recommended actions 1) Isolate the safety device that was opened 2) Reset the device switch. 20237, Immediate Superior Stop Description The Superior Stop circuits have been broken. Consequences The system goes directly to status Guard Stop. Probable causes One or more of the safety device switches in the Superior Stop circuit have been opened Recommended actions 1) Isolate the safety device that was opened 2) Reset the device switch. 20238, Delayed Superior Stop due to circuit imbalance Description The system has detected an imbalance in the two parallel Superior Stop circuits. Consequences The system goes to status Guard Stop after approximately 1 sec. Probable causes The contact pair in any of the safety devices connected to the Superior Stop circuit is not working correctly. Recommended actions 1. Isolate the safety device causing the conflict. 2. Make sure the device used is a two-channel device. 3. Check the contact pair. 4. Make sure all connections are tight. 5. Replace the device if required. 20240, Conflict between ENABLE signals Description A switch in only one of the two ENABLE chains was affected, without the other chain being affected. Consequences The system goes to status SYS HALT. Probable causes There may be a loose signal connection on the Safety System. The ENABLE chain is described in the Trouble Shooting Manual and Circuit Diagram. Recommended actions 1) Check cables and connections. 6 Trouble shooting by Event log 121 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 2) Make sure all signal connectors on the Safety System are securely connected. 3) If there is no loose connection, replace the faulty board. 20241, Operating mode conflict Description There is a conflict between the operating mode selected on the operating mode selector on the controller cabinet front and the actual operating mode as detected by the axis computer. Consequences The system goes to status SYS HALT. Probable causes There may be a hardware fault in the operating mode selector or its cabling to the Safety System. Recommended actions Check the operating mode selector and its cabling to the Safety System. 20245, Run Control status conflict, DRV2 Description Status conflict between Run Control and Motor Contactors for drive system 2. Consequences The system goes to status SYS HALT. Probable causes A failure of the Motor Contactors or the supply to these. Recommended actions 1) Check cables and connections. 2) Do a Warm start. 20246, Run Control status conflict, DRV3 Description Status conflict between Run Control and Motor Contactors for drive system 3. Consequences The system goes to status SYS HALT. Probable causes A failure of the Motor Contactors or the supply to these. Recommended actions 1) Check cables and connections. 2) Do a Warm start. 20247, Run Control status conflict, DRV4 Description Status conflict between Run Control and Motor Contactors for drive system 4. Consequences The system goes to status SYS HALT. Probable causes A failure of the Motor Contactors or the supply to these. Recommended actions 1) Check cables and connections. 2) Do a Warm start. 20248, Motor Contactor conflict, DRV2 Description Only one of the two Motor Contactors for drive system 2 has acknowledged the activation order. Consequences The system goes to status SYS HALT. Probable causes A failure of the motor contactor auxiliary contacts or the supply to these. Recommended actions 1) Check cables and connections. 2) Check the function of the auxiliary contacts. 20249, Motor Contactor conflict, DRV3 Description Only one of the two Motor Contactors for drive system 3 has acknowledged the activation order. Consequences The system goes to status SYS HALT. Probable causes A failure of the motor contactor auxiliary contacts or the supply to these. Recommended actions 1) Check cables and connections. 2) Check the function of the auxiliary contacts. 20250, Motor Contactor conflict, DRV4 Description Only one of the two Motor Contactors for drive system 4 has acknowledged the activation order. Consequences The system goes to status SYS HALT. 6 Trouble shooting by Event log 122 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes A failure of the motor contactor auxiliary contacts or the supply to these. Recommended actions 1) Check cables and connections. 2) Check the function of the auxiliary contacts. 20252, Motor temperature high, DRV1 Description Over temperature in Manipulator Motor. Make sure to let the Motor cool down before ordering Motors On again. Recommended actions 1) Wait until the overheated Motor has cooled down before ordering Motors On again. 2) If optional air filter is used, check if it is clogged and has to be exchanged 20253, External device temperature high, DRV1 Description Over temperature in External Device. Make sure to let the External Device cool down before ordering Motors On again. Recommended actions Wait until the overheated Motor has cooled down before ordering Motors On again. 20254, Motor temperature high, DRV2 Description Over temperature in Manipulator Motor. Make sure to let the Motor cool down before ordering Motors On again. Recommended actions 1) Wait until the overheated Motor has cooled down before ordering Motors On again. 2) If optional air filter is used, check if it is clogged and has to be exchanged 20255, External device temperature high, DRV2 Description Over temperature in External Device. Make sure to let the External Device cool down before ordering Motors On again. Recommended actions Wait until the overheated Motor has cooled down before ordering Motors On again. 20256, Motor temperature high, DRV3 Description Over temperature in Manipulator Motor. Make sure to let the Motor cool down before ordering Motors On again. Recommended actions 1) Wait until the overheated Motor has cooled down before ordering Motors On again. 2) If optional air filter is used, check if it is clogged and has to be exchanged 20257, External device temperature high, DRV3 Description Over temperature in External Device. Make sure to let the External Device cool down before ordering Motors On again. Recommended actions Wait until the overheated Motor has cooled down before ordering Motors On again. 20258, Motor temperature high, DRV4 Description Over temperature in Manipulator Motor. Make sure to let the Motor cool down before ordering Motors On again. Recommended actions 1) Wait until the overheated Motor has cooled down before ordering Motors On again. 2) If optional air filter is used, check if it is clogged and has to be exchanged 20259, External device temperature high, DRV4 Description Over temperature in External Device. Make sure to let the External Device cool down before ordering Motors On again. Recommended actions Wait until the overheated Motor has cooled down before ordering Motors On again. 20260, Run Control status conflict, DRV1 Description Status conflict between Run Control and Motor Contactors for drive system 1. Consequences The system goes to status SYS HALT. Probable causes A failure of the Motor Contactors or the supply to these. Recommended actions 1) Check cables and connections. 2) Do a Warm start.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	124	6 Trouble shooting by Event log 121 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 2) Make sure all signal connectors on the Safety System are securely connected. 3) If there is no loose connection, replace the faulty board. 20241, Operating mode conflict Description There is a conflict between the operating mode selected on the operating mode selector on the controller cabinet front and the actual operating mode as detected by the axis computer. Consequences The system goes to status SYS HALT. Probable causes There may be a hardware fault in the operating mode selector or its cabling to the Safety System. Recommended actions Check the operating mode selector and its cabling to the Safety System. 20245, Run Control status conflict, DRV2 Description Status conflict between Run Control and Motor Contactors for drive system 2. Consequences The system goes to status SYS HALT. Probable causes A failure of the Motor Contactors or the supply to these. Recommended actions 1) Check cables and connections. 2) Do a Warm start. 20246, Run Control status conflict, DRV3 Description Status conflict between Run Control and Motor Contactors for drive system 3. Consequences The system goes to status SYS HALT. Probable causes A failure of the Motor Contactors or the supply to these. Recommended actions 1) Check cables and connections. 2) Do a Warm start. 20247, Run Control status conflict, DRV4 Description Status conflict between Run Control and Motor Contactors for drive system 4. Consequences The system goes to status SYS HALT. Probable causes A failure of the Motor Contactors or the supply to these. Recommended actions 1) Check cables and connections. 2) Do a Warm start. 20248, Motor Contactor conflict, DRV2 Description Only one of the two Motor Contactors for drive system 2 has acknowledged the activation order. Consequences The system goes to status SYS HALT. Probable causes A failure of the motor contactor auxiliary contacts or the supply to these. Recommended actions 1) Check cables and connections. 2) Check the function of the auxiliary contacts. 20249, Motor Contactor conflict, DRV3 Description Only one of the two Motor Contactors for drive system 3 has acknowledged the activation order. Consequences The system goes to status SYS HALT. Probable causes A failure of the motor contactor auxiliary contacts or the supply to these. Recommended actions 1) Check cables and connections. 2) Check the function of the auxiliary contacts. 20250, Motor Contactor conflict, DRV4 Description Only one of the two Motor Contactors for drive system 4 has acknowledged the activation order. Consequences The system goes to status SYS HALT. 6 Trouble shooting by Event log 122 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes A failure of the motor contactor auxiliary contacts or the supply to these. Recommended actions 1) Check cables and connections. 2) Check the function of the auxiliary contacts. 20252, Motor temperature high, DRV1 Description Over temperature in Manipulator Motor. Make sure to let the Motor cool down before ordering Motors On again. Recommended actions 1) Wait until the overheated Motor has cooled down before ordering Motors On again. 2) If optional air filter is used, check if it is clogged and has to be exchanged 20253, External device temperature high, DRV1 Description Over temperature in External Device. Make sure to let the External Device cool down before ordering Motors On again. Recommended actions Wait until the overheated Motor has cooled down before ordering Motors On again. 20254, Motor temperature high, DRV2 Description Over temperature in Manipulator Motor. Make sure to let the Motor cool down before ordering Motors On again. Recommended actions 1) Wait until the overheated Motor has cooled down before ordering Motors On again. 2) If optional air filter is used, check if it is clogged and has to be exchanged 20255, External device temperature high, DRV2 Description Over temperature in External Device. Make sure to let the External Device cool down before ordering Motors On again. Recommended actions Wait until the overheated Motor has cooled down before ordering Motors On again. 20256, Motor temperature high, DRV3 Description Over temperature in Manipulator Motor. Make sure to let the Motor cool down before ordering Motors On again. Recommended actions 1) Wait until the overheated Motor has cooled down before ordering Motors On again. 2) If optional air filter is used, check if it is clogged and has to be exchanged 20257, External device temperature high, DRV3 Description Over temperature in External Device. Make sure to let the External Device cool down before ordering Motors On again. Recommended actions Wait until the overheated Motor has cooled down before ordering Motors On again. 20258, Motor temperature high, DRV4 Description Over temperature in Manipulator Motor. Make sure to let the Motor cool down before ordering Motors On again. Recommended actions 1) Wait until the overheated Motor has cooled down before ordering Motors On again. 2) If optional air filter is used, check if it is clogged and has to be exchanged 20259, External device temperature high, DRV4 Description Over temperature in External Device. Make sure to let the External Device cool down before ordering Motors On again. Recommended actions Wait until the overheated Motor has cooled down before ordering Motors On again. 20260, Run Control status conflict, DRV1 Description Status conflict between Run Control and Motor Contactors for drive system 1. Consequences The system goes to status SYS HALT. Probable causes A failure of the Motor Contactors or the supply to these. Recommended actions 1) Check cables and connections. 2) Do a Warm start. 6 Trouble shooting by Event log 123 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20262, SC arg Not found Description The system has an option for arg Safety Controller (SC) on drive module arg , but no Safety Controller was found. Recommended actions - Check Safety Controller cabling. - Check Safety Controller health. Warm start controller, after performing recommended actions. 20263, SC arg Communication Failure Description Communication error with Safety Controller (SC) arg Recommended actions - Check Safety Controller cabling. - Check Safety Controller health. Warm start controller, after performing recommended actions. 20264, SC arg Option Not Present Description Found arg Safety Controller (SC) on drive module arg .This system does not have the option for a Safety Controller on that drive module. Recommended actions - Check drive module software options. - Install a system with Safety Controller option. 20265, SC Soft Stop Error Description Safety Controller (SC) Soft Stop has not opened the Motor Contactors within the calculated time Recommended actions Check Lim-switch connection if SafeMove is present 20266, SC arg PIN Code Request Description Safety Controller (SC) arg has a new Safety Configuration and needs a new PIN code to be activated. Recommended actions 1. Log in as a user with Safety Configuration grants. 2. Enter new PIN-Code for the Safety Controller in the Control Panel. 20267, SC arg Initialization Failed Description Safety Controller (SC) arg failed to initialize properly, or failed to respond during start up. Recommended actions 1. Check previous error logs for possible causes. 2. Restart the system. 20268, SC arg Wrong Type Description Found arg Safety Controller (SC) on drive module arg , expected arg . Recommended actions - Check drive module software options. - Install a system with correct Safety Controller option. - Install a Safety Controller of the correct type. 20270, Access error Description Panel Module access error. Recommended actions Examine your I/O configuration files. 20280, Symbol conflict Description The signal arg defined in the IO configuration conflict with another program symbol with the same name. Due on that fact the signal will not be mapped to a program variable. Recommended actions Rename the signal in the IO configuration. 20281, IO configuration error Description argarg with signal name arg has wrong signal type. Found arg expected arg . Recommended actions Change your configuration and restart the system. 20282, Resource and index exist Description Resource arg Index arg .
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	125	6 Trouble shooting by Event log 122 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes A failure of the motor contactor auxiliary contacts or the supply to these. Recommended actions 1) Check cables and connections. 2) Check the function of the auxiliary contacts. 20252, Motor temperature high, DRV1 Description Over temperature in Manipulator Motor. Make sure to let the Motor cool down before ordering Motors On again. Recommended actions 1) Wait until the overheated Motor has cooled down before ordering Motors On again. 2) If optional air filter is used, check if it is clogged and has to be exchanged 20253, External device temperature high, DRV1 Description Over temperature in External Device. Make sure to let the External Device cool down before ordering Motors On again. Recommended actions Wait until the overheated Motor has cooled down before ordering Motors On again. 20254, Motor temperature high, DRV2 Description Over temperature in Manipulator Motor. Make sure to let the Motor cool down before ordering Motors On again. Recommended actions 1) Wait until the overheated Motor has cooled down before ordering Motors On again. 2) If optional air filter is used, check if it is clogged and has to be exchanged 20255, External device temperature high, DRV2 Description Over temperature in External Device. Make sure to let the External Device cool down before ordering Motors On again. Recommended actions Wait until the overheated Motor has cooled down before ordering Motors On again. 20256, Motor temperature high, DRV3 Description Over temperature in Manipulator Motor. Make sure to let the Motor cool down before ordering Motors On again. Recommended actions 1) Wait until the overheated Motor has cooled down before ordering Motors On again. 2) If optional air filter is used, check if it is clogged and has to be exchanged 20257, External device temperature high, DRV3 Description Over temperature in External Device. Make sure to let the External Device cool down before ordering Motors On again. Recommended actions Wait until the overheated Motor has cooled down before ordering Motors On again. 20258, Motor temperature high, DRV4 Description Over temperature in Manipulator Motor. Make sure to let the Motor cool down before ordering Motors On again. Recommended actions 1) Wait until the overheated Motor has cooled down before ordering Motors On again. 2) If optional air filter is used, check if it is clogged and has to be exchanged 20259, External device temperature high, DRV4 Description Over temperature in External Device. Make sure to let the External Device cool down before ordering Motors On again. Recommended actions Wait until the overheated Motor has cooled down before ordering Motors On again. 20260, Run Control status conflict, DRV1 Description Status conflict between Run Control and Motor Contactors for drive system 1. Consequences The system goes to status SYS HALT. Probable causes A failure of the Motor Contactors or the supply to these. Recommended actions 1) Check cables and connections. 2) Do a Warm start. 6 Trouble shooting by Event log 123 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20262, SC arg Not found Description The system has an option for arg Safety Controller (SC) on drive module arg , but no Safety Controller was found. Recommended actions - Check Safety Controller cabling. - Check Safety Controller health. Warm start controller, after performing recommended actions. 20263, SC arg Communication Failure Description Communication error with Safety Controller (SC) arg Recommended actions - Check Safety Controller cabling. - Check Safety Controller health. Warm start controller, after performing recommended actions. 20264, SC arg Option Not Present Description Found arg Safety Controller (SC) on drive module arg .This system does not have the option for a Safety Controller on that drive module. Recommended actions - Check drive module software options. - Install a system with Safety Controller option. 20265, SC Soft Stop Error Description Safety Controller (SC) Soft Stop has not opened the Motor Contactors within the calculated time Recommended actions Check Lim-switch connection if SafeMove is present 20266, SC arg PIN Code Request Description Safety Controller (SC) arg has a new Safety Configuration and needs a new PIN code to be activated. Recommended actions 1. Log in as a user with Safety Configuration grants. 2. Enter new PIN-Code for the Safety Controller in the Control Panel. 20267, SC arg Initialization Failed Description Safety Controller (SC) arg failed to initialize properly, or failed to respond during start up. Recommended actions 1. Check previous error logs for possible causes. 2. Restart the system. 20268, SC arg Wrong Type Description Found arg Safety Controller (SC) on drive module arg , expected arg . Recommended actions - Check drive module software options. - Install a system with correct Safety Controller option. - Install a Safety Controller of the correct type. 20270, Access error Description Panel Module access error. Recommended actions Examine your I/O configuration files. 20280, Symbol conflict Description The signal arg defined in the IO configuration conflict with another program symbol with the same name. Due on that fact the signal will not be mapped to a program variable. Recommended actions Rename the signal in the IO configuration. 20281, IO configuration error Description argarg with signal name arg has wrong signal type. Found arg expected arg . Recommended actions Change your configuration and restart the system. 20282, Resource and index exist Description Resource arg Index arg . 6 Trouble shooting by Event log 124 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 20283, Text database is full. Description Resource arg Index arg Recommended actions 20284, Wrong Signal Type For System Input Description The System Input arg is configured with an I/O-signal of wrong type. The I/O-signal arg is of type arg and this System Input requires an I/O-signal of type arg . Recommended actions Change the configuration for the specified System Input. 20285, Wrong Signal Type For System Output Description The System Output arg is configured with an I/O-signal of wrong type. The I/O-signal arg is of type arg and this System Output requires an I/O-signal of type arg . Recommended actions Change the configuration for the specified System Output. 20286, Not Unique I/O-Signal For System Output Description Each System Output must have a unique I/O-signal configured. It is not possible to configure same I/O-signal to several System Outputs. System Output: arg Signal Name: arg Recommended actions 20287, Not Unique I/O-signal For System Input Description Each System Input must have a unique I/O-signal configured. It is not possible to configure same I/O-signal to several System Inputs. System Input: arg Signal Name: arg 20288, Unknown System Output Type Description The configured System Output type is unknown by the system. Unknown System Output: arg Recommended actions Verify that the System Output name is correctly spelled. 20289, Unknown System Input Type Description The configured System Input type is unknown by the system. Unknown System Input: arg Recommended actions Verify that the System Input name is correctly spelled. 20290, Unknown Mechanical Unit Name For System Output Description A System Output is configured with a mechanical unit name which is unknown by the system. System Output: arg Mechanical unit name: arg Recommended actions The specified mechanical unit must be configured in order to be used by System Outputs Verify that the mechanical unit name is correctly spelled. 20291, Unknown System Input Restriction Type Description The configured System Input Restriction Type is unknown by the system. Unknown System Input Restriction: arg Recommended actions Verify that the System Input Restriction name is correctly spelled. 20292, Unknown System Input Restriction Description The configured System Input Restriction is unknown by the system. System Input Restriction Type: arg Unknown System Input Restriction: arg Recommended actions Verify that the System Input Restriction name is correctly spelled.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	126	6 Trouble shooting by Event log 123 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20262, SC arg Not found Description The system has an option for arg Safety Controller (SC) on drive module arg , but no Safety Controller was found. Recommended actions - Check Safety Controller cabling. - Check Safety Controller health. Warm start controller, after performing recommended actions. 20263, SC arg Communication Failure Description Communication error with Safety Controller (SC) arg Recommended actions - Check Safety Controller cabling. - Check Safety Controller health. Warm start controller, after performing recommended actions. 20264, SC arg Option Not Present Description Found arg Safety Controller (SC) on drive module arg .This system does not have the option for a Safety Controller on that drive module. Recommended actions - Check drive module software options. - Install a system with Safety Controller option. 20265, SC Soft Stop Error Description Safety Controller (SC) Soft Stop has not opened the Motor Contactors within the calculated time Recommended actions Check Lim-switch connection if SafeMove is present 20266, SC arg PIN Code Request Description Safety Controller (SC) arg has a new Safety Configuration and needs a new PIN code to be activated. Recommended actions 1. Log in as a user with Safety Configuration grants. 2. Enter new PIN-Code for the Safety Controller in the Control Panel. 20267, SC arg Initialization Failed Description Safety Controller (SC) arg failed to initialize properly, or failed to respond during start up. Recommended actions 1. Check previous error logs for possible causes. 2. Restart the system. 20268, SC arg Wrong Type Description Found arg Safety Controller (SC) on drive module arg , expected arg . Recommended actions - Check drive module software options. - Install a system with correct Safety Controller option. - Install a Safety Controller of the correct type. 20270, Access error Description Panel Module access error. Recommended actions Examine your I/O configuration files. 20280, Symbol conflict Description The signal arg defined in the IO configuration conflict with another program symbol with the same name. Due on that fact the signal will not be mapped to a program variable. Recommended actions Rename the signal in the IO configuration. 20281, IO configuration error Description argarg with signal name arg has wrong signal type. Found arg expected arg . Recommended actions Change your configuration and restart the system. 20282, Resource and index exist Description Resource arg Index arg . 6 Trouble shooting by Event log 124 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 20283, Text database is full. Description Resource arg Index arg Recommended actions 20284, Wrong Signal Type For System Input Description The System Input arg is configured with an I/O-signal of wrong type. The I/O-signal arg is of type arg and this System Input requires an I/O-signal of type arg . Recommended actions Change the configuration for the specified System Input. 20285, Wrong Signal Type For System Output Description The System Output arg is configured with an I/O-signal of wrong type. The I/O-signal arg is of type arg and this System Output requires an I/O-signal of type arg . Recommended actions Change the configuration for the specified System Output. 20286, Not Unique I/O-Signal For System Output Description Each System Output must have a unique I/O-signal configured. It is not possible to configure same I/O-signal to several System Outputs. System Output: arg Signal Name: arg Recommended actions 20287, Not Unique I/O-signal For System Input Description Each System Input must have a unique I/O-signal configured. It is not possible to configure same I/O-signal to several System Inputs. System Input: arg Signal Name: arg 20288, Unknown System Output Type Description The configured System Output type is unknown by the system. Unknown System Output: arg Recommended actions Verify that the System Output name is correctly spelled. 20289, Unknown System Input Type Description The configured System Input type is unknown by the system. Unknown System Input: arg Recommended actions Verify that the System Input name is correctly spelled. 20290, Unknown Mechanical Unit Name For System Output Description A System Output is configured with a mechanical unit name which is unknown by the system. System Output: arg Mechanical unit name: arg Recommended actions The specified mechanical unit must be configured in order to be used by System Outputs Verify that the mechanical unit name is correctly spelled. 20291, Unknown System Input Restriction Type Description The configured System Input Restriction Type is unknown by the system. Unknown System Input Restriction: arg Recommended actions Verify that the System Input Restriction name is correctly spelled. 20292, Unknown System Input Restriction Description The configured System Input Restriction is unknown by the system. System Input Restriction Type: arg Unknown System Input Restriction: arg Recommended actions Verify that the System Input Restriction name is correctly spelled. 6 Trouble shooting by Event log 125 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20293, System Input is Restricted Description The system input arg is restricted by the system input arg set by I/O signal arg . Consequences The action called for by system input arg will not take place, and the operation will NOT be affected. Probable causes System input arg may be set by external equipment, such as PLCs, etc, for a number of reasons. Recommended actions 1) Investigate why the system input was set, and, if required, correct the reason. 20294, Action arg can not be fulfilled. Description The requested action cannot be fulfilled since the IO unit is not responding. Consequences It is not possible to decide if there are any restrictions set to the action. Probable causes The requested action will not be fulfilled until the I/O unit is enabled again. Recommended actions Never disable a unit with System Inputs/Outputs. 20295, Signal cannot be used as System Output. Description The System Output arg is configured with an I/O-signal with wrong category. The I/O-signal arg has category Safety and can not be used as System Output. Recommended actions Choose another signal or set to another category. 20296, Wrong task name configured Description Wrong task name arg configured for System Output arg . Consequences The digital output signal will not be connected to the specified event. Recommended actions Change the configuration and restart the system. 20307, Motor cooling fan malfunction, axis 1 Description The axis 1 motor cooling fan on the robot connected to Drive Module arg does not work correctly. Consequences The full meaning of this status is described in the Trouble Shooting Manual, IRC5. Probable causes -The fan power cabling may be damaged or not connected correctly to motor or contactor unit. -The fan or the Drive Module Power Supply may be faulty. Recommended actions 1) Make sure the fan cable is correctly connected 2) Make sure the fan is free to rotate and that the air flow is not obstructed. 3) Make sure the Drive Module Power Supply output and input voltages are within specified limits as detailed in the Trouble shooting manual. Replace any faulty unit. 20308, Motor cooling fan malfunction, axis 2 Description The axis 2 motor cooling fan on the robot connected to Drive Module arg does not work correctly. Consequences The full meaning of this status is described in the Trouble Shooting Manual, IRC5. Probable causes -The fan power cabling may be damaged or not connected correctly to motor or contactor unit. -The fan or the Drive Module Power Supply may be faulty. Recommended actions 1) Make sure the fan cable is correctly connected 2) Make sure the fan is free to rotate and that the air flow is not obstructed. 3) Make sure the Drive Module Power Supply output and input voltages are within specified limits as detailed in the Trouble shooting manual. Replace any faulty unit. 20309, Motor cooling fan malfunction, axis 3 Description The axis 3 motor cooling fan on the robot connected to Drive Module arg does not work correctly. Consequences The full meaning of this status is described in the Trouble Shooting Manual, IRC5.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	127	6 Trouble shooting by Event log 124 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 20283, Text database is full. Description Resource arg Index arg Recommended actions 20284, Wrong Signal Type For System Input Description The System Input arg is configured with an I/O-signal of wrong type. The I/O-signal arg is of type arg and this System Input requires an I/O-signal of type arg . Recommended actions Change the configuration for the specified System Input. 20285, Wrong Signal Type For System Output Description The System Output arg is configured with an I/O-signal of wrong type. The I/O-signal arg is of type arg and this System Output requires an I/O-signal of type arg . Recommended actions Change the configuration for the specified System Output. 20286, Not Unique I/O-Signal For System Output Description Each System Output must have a unique I/O-signal configured. It is not possible to configure same I/O-signal to several System Outputs. System Output: arg Signal Name: arg Recommended actions 20287, Not Unique I/O-signal For System Input Description Each System Input must have a unique I/O-signal configured. It is not possible to configure same I/O-signal to several System Inputs. System Input: arg Signal Name: arg 20288, Unknown System Output Type Description The configured System Output type is unknown by the system. Unknown System Output: arg Recommended actions Verify that the System Output name is correctly spelled. 20289, Unknown System Input Type Description The configured System Input type is unknown by the system. Unknown System Input: arg Recommended actions Verify that the System Input name is correctly spelled. 20290, Unknown Mechanical Unit Name For System Output Description A System Output is configured with a mechanical unit name which is unknown by the system. System Output: arg Mechanical unit name: arg Recommended actions The specified mechanical unit must be configured in order to be used by System Outputs Verify that the mechanical unit name is correctly spelled. 20291, Unknown System Input Restriction Type Description The configured System Input Restriction Type is unknown by the system. Unknown System Input Restriction: arg Recommended actions Verify that the System Input Restriction name is correctly spelled. 20292, Unknown System Input Restriction Description The configured System Input Restriction is unknown by the system. System Input Restriction Type: arg Unknown System Input Restriction: arg Recommended actions Verify that the System Input Restriction name is correctly spelled. 6 Trouble shooting by Event log 125 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20293, System Input is Restricted Description The system input arg is restricted by the system input arg set by I/O signal arg . Consequences The action called for by system input arg will not take place, and the operation will NOT be affected. Probable causes System input arg may be set by external equipment, such as PLCs, etc, for a number of reasons. Recommended actions 1) Investigate why the system input was set, and, if required, correct the reason. 20294, Action arg can not be fulfilled. Description The requested action cannot be fulfilled since the IO unit is not responding. Consequences It is not possible to decide if there are any restrictions set to the action. Probable causes The requested action will not be fulfilled until the I/O unit is enabled again. Recommended actions Never disable a unit with System Inputs/Outputs. 20295, Signal cannot be used as System Output. Description The System Output arg is configured with an I/O-signal with wrong category. The I/O-signal arg has category Safety and can not be used as System Output. Recommended actions Choose another signal or set to another category. 20296, Wrong task name configured Description Wrong task name arg configured for System Output arg . Consequences The digital output signal will not be connected to the specified event. Recommended actions Change the configuration and restart the system. 20307, Motor cooling fan malfunction, axis 1 Description The axis 1 motor cooling fan on the robot connected to Drive Module arg does not work correctly. Consequences The full meaning of this status is described in the Trouble Shooting Manual, IRC5. Probable causes -The fan power cabling may be damaged or not connected correctly to motor or contactor unit. -The fan or the Drive Module Power Supply may be faulty. Recommended actions 1) Make sure the fan cable is correctly connected 2) Make sure the fan is free to rotate and that the air flow is not obstructed. 3) Make sure the Drive Module Power Supply output and input voltages are within specified limits as detailed in the Trouble shooting manual. Replace any faulty unit. 20308, Motor cooling fan malfunction, axis 2 Description The axis 2 motor cooling fan on the robot connected to Drive Module arg does not work correctly. Consequences The full meaning of this status is described in the Trouble Shooting Manual, IRC5. Probable causes -The fan power cabling may be damaged or not connected correctly to motor or contactor unit. -The fan or the Drive Module Power Supply may be faulty. Recommended actions 1) Make sure the fan cable is correctly connected 2) Make sure the fan is free to rotate and that the air flow is not obstructed. 3) Make sure the Drive Module Power Supply output and input voltages are within specified limits as detailed in the Trouble shooting manual. Replace any faulty unit. 20309, Motor cooling fan malfunction, axis 3 Description The axis 3 motor cooling fan on the robot connected to Drive Module arg does not work correctly. Consequences The full meaning of this status is described in the Trouble Shooting Manual, IRC5. 6 Trouble shooting by Event log 126 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes -The fan power cabling may be damaged or not connected correctly to motor or contactor unit. -The fan or the Drive Module Power Supply may be faulty. Recommended actions 1) Make sure the fan cable is correctly connected 2) Make sure the fan is free to rotate and that the air flow is not obstructed. 3) Make sure the Drive Module Power Supply output and input voltages are within specified limits as detailed in the Trouble shooting manual. Replace any faulty unit. 20310, SC arg Communication Failed Description An error occurred while trying to communicate with Safety Controller (SC) arg Recommended actions - Check Safety Controller cabling. - Check Safety Controller health. Warm start controller, after performing recommended actions. 20311, Enable 1 open Description The ENABLE 1 circuit monitoring the Safety System has been opened. Consequences The system goes to status SYS HALT. Probable causes There may be an internal fault in the Safety System or the internal supervision has detected a fault. Recommended actions 1) Check all connections to the Safety System. 2) If faulty, replace the faulty board. 20312, Enable 2 open Description The ENABLE 2 circuit monitoring the Axis Computer has been opened. Consequences The system goes to status SYS HALT. Probable causes There may be a connection problem between Main Computer and Axis Computer. Recommended actions 1) Check all connections to the axis computer. 2) Check cables conntected to the Safety System. 20313, Enable1 supervision fault Description The ENABLE1 circuit has been broken. This circuit monitors the function of the Safety System and the main computer. Consequences The system goes to status SYS HALT. Probable causes A fault, probably a software fault, has been detected by any of the units supervised by the ENABLE1 circuit. Recommended actions 1) Attempt restarting by pressing the Motors ON button. If restarting is IMPOSSIBLE it indicates a hardware fault in Safety System, axis computer. If restarting is POSSIBLE, it indicates a software fault. In such case, contact your local ABB representative. 2) Determine which unit is faulty by checking its indication LEDs. The LEDs are described in the Trouble Shooting Manual. Replace the faulty unit. 20314, Enable2 supervision fault Description The ENABLE2 circuit to drive module 1 has been broken. This circuit monitors e.g. the function of the Safety System and the axis computer. Consequences The system goes to status SYS HALT. Probable causes A fault, probably a software fault, has been detected by any of the units supervised by the ENABLE2 circuit. Recommended actions 1) Attempt restarting by pressing the Motors ON button. If restarting is IMPOSSIBLE it indicates a hardware fault in Safety System, axis computer. If restarting is POSSIBLE, it indicates a software fault. In such case, contact your local ABB representative. 2) Determine which unit is faulty by checking its indication LEDs. The LEDs are described in the Trouble Shooting Manual. Replace the faulty unit. 20315, Enable2 Supervision fault Description The ENABLE2 circuit to drive module 2 has been broken. This circuit monitors e.g. the function of the Safety System and the axis computer. Consequences The system goes to status SYS HALT. Probable causes A fault, probably a software fault, has been detected by any of the units supervised by the ENABLE2 circuit.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	128	6 Trouble shooting by Event log 125 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20293, System Input is Restricted Description The system input arg is restricted by the system input arg set by I/O signal arg . Consequences The action called for by system input arg will not take place, and the operation will NOT be affected. Probable causes System input arg may be set by external equipment, such as PLCs, etc, for a number of reasons. Recommended actions 1) Investigate why the system input was set, and, if required, correct the reason. 20294, Action arg can not be fulfilled. Description The requested action cannot be fulfilled since the IO unit is not responding. Consequences It is not possible to decide if there are any restrictions set to the action. Probable causes The requested action will not be fulfilled until the I/O unit is enabled again. Recommended actions Never disable a unit with System Inputs/Outputs. 20295, Signal cannot be used as System Output. Description The System Output arg is configured with an I/O-signal with wrong category. The I/O-signal arg has category Safety and can not be used as System Output. Recommended actions Choose another signal or set to another category. 20296, Wrong task name configured Description Wrong task name arg configured for System Output arg . Consequences The digital output signal will not be connected to the specified event. Recommended actions Change the configuration and restart the system. 20307, Motor cooling fan malfunction, axis 1 Description The axis 1 motor cooling fan on the robot connected to Drive Module arg does not work correctly. Consequences The full meaning of this status is described in the Trouble Shooting Manual, IRC5. Probable causes -The fan power cabling may be damaged or not connected correctly to motor or contactor unit. -The fan or the Drive Module Power Supply may be faulty. Recommended actions 1) Make sure the fan cable is correctly connected 2) Make sure the fan is free to rotate and that the air flow is not obstructed. 3) Make sure the Drive Module Power Supply output and input voltages are within specified limits as detailed in the Trouble shooting manual. Replace any faulty unit. 20308, Motor cooling fan malfunction, axis 2 Description The axis 2 motor cooling fan on the robot connected to Drive Module arg does not work correctly. Consequences The full meaning of this status is described in the Trouble Shooting Manual, IRC5. Probable causes -The fan power cabling may be damaged or not connected correctly to motor or contactor unit. -The fan or the Drive Module Power Supply may be faulty. Recommended actions 1) Make sure the fan cable is correctly connected 2) Make sure the fan is free to rotate and that the air flow is not obstructed. 3) Make sure the Drive Module Power Supply output and input voltages are within specified limits as detailed in the Trouble shooting manual. Replace any faulty unit. 20309, Motor cooling fan malfunction, axis 3 Description The axis 3 motor cooling fan on the robot connected to Drive Module arg does not work correctly. Consequences The full meaning of this status is described in the Trouble Shooting Manual, IRC5. 6 Trouble shooting by Event log 126 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes -The fan power cabling may be damaged or not connected correctly to motor or contactor unit. -The fan or the Drive Module Power Supply may be faulty. Recommended actions 1) Make sure the fan cable is correctly connected 2) Make sure the fan is free to rotate and that the air flow is not obstructed. 3) Make sure the Drive Module Power Supply output and input voltages are within specified limits as detailed in the Trouble shooting manual. Replace any faulty unit. 20310, SC arg Communication Failed Description An error occurred while trying to communicate with Safety Controller (SC) arg Recommended actions - Check Safety Controller cabling. - Check Safety Controller health. Warm start controller, after performing recommended actions. 20311, Enable 1 open Description The ENABLE 1 circuit monitoring the Safety System has been opened. Consequences The system goes to status SYS HALT. Probable causes There may be an internal fault in the Safety System or the internal supervision has detected a fault. Recommended actions 1) Check all connections to the Safety System. 2) If faulty, replace the faulty board. 20312, Enable 2 open Description The ENABLE 2 circuit monitoring the Axis Computer has been opened. Consequences The system goes to status SYS HALT. Probable causes There may be a connection problem between Main Computer and Axis Computer. Recommended actions 1) Check all connections to the axis computer. 2) Check cables conntected to the Safety System. 20313, Enable1 supervision fault Description The ENABLE1 circuit has been broken. This circuit monitors the function of the Safety System and the main computer. Consequences The system goes to status SYS HALT. Probable causes A fault, probably a software fault, has been detected by any of the units supervised by the ENABLE1 circuit. Recommended actions 1) Attempt restarting by pressing the Motors ON button. If restarting is IMPOSSIBLE it indicates a hardware fault in Safety System, axis computer. If restarting is POSSIBLE, it indicates a software fault. In such case, contact your local ABB representative. 2) Determine which unit is faulty by checking its indication LEDs. The LEDs are described in the Trouble Shooting Manual. Replace the faulty unit. 20314, Enable2 supervision fault Description The ENABLE2 circuit to drive module 1 has been broken. This circuit monitors e.g. the function of the Safety System and the axis computer. Consequences The system goes to status SYS HALT. Probable causes A fault, probably a software fault, has been detected by any of the units supervised by the ENABLE2 circuit. Recommended actions 1) Attempt restarting by pressing the Motors ON button. If restarting is IMPOSSIBLE it indicates a hardware fault in Safety System, axis computer. If restarting is POSSIBLE, it indicates a software fault. In such case, contact your local ABB representative. 2) Determine which unit is faulty by checking its indication LEDs. The LEDs are described in the Trouble Shooting Manual. Replace the faulty unit. 20315, Enable2 Supervision fault Description The ENABLE2 circuit to drive module 2 has been broken. This circuit monitors e.g. the function of the Safety System and the axis computer. Consequences The system goes to status SYS HALT. Probable causes A fault, probably a software fault, has been detected by any of the units supervised by the ENABLE2 circuit. 6 Trouble shooting by Event log 127 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Attempt restarting by pressing the Motors ON button. If restarting is IMPOSSIBLE it indicates a hardware fault in safety board, axis computer. If restarting is POSSIBLE, it indicates a software fault. In such case, contact your local ABB representative. 2) Determine which unit is faulty by checking its indication LEDs. The LEDs are described in the Trouble Shooting Manual. Replace the faulty unit. 20316, Enable2 Supervision fault Description The ENABLE2 circuit to drive module 3 has been broken. This circuit monitors e.g. the function of the Safety System and the axis computer. Consequences The system goes to status SYS HALT. Probable causes A fault, probably a software fault, has been detected by any of the units supervised by the ENABLE2 circuit. Recommended actions 1) Attempt restarting by pressing the Motors ON button. If restarting is IMPOSSIBLE it indicates a hardware fault in Safety System, axis computer. If restarting is POSSIBLE, it indicates a software fault. In such case, contact your local ABB representative. 2) Determine which unit is faulty by checking its indication LEDs. The LEDs are described in the Trouble Shooting Manual. Replace the faulty unit. 20317, Enable2 Supervision fault Description The ENABLE2 circuit to drive module 4 has been broken. This circuit monitors e.g. the function of the Safety System and the axis computer. Consequences The system goes to status SYS HALT. Probable causes A fault, probably a software fault, has been detected by any of the units supervised by the ENABLE2 circuit. Recommended actions 1) Attempt restarting by pressing the Motors ON button. If restarting is IMPOSSIBLE it indicates a hardware fault in Safety System, Axis computer. If restarting is POSSIBLE, it indicates a software fault. In such case, contact your local ABB representative. 2) Determine which unit is faulty by checking its indication LEDs. The LEDs are described in the Trouble Shooting Manual. Replace the faulty unit. 20350, Not a valid task name Description The task name arg cannot be used as a name of a task. It is either already used as an installed symbol, a reserved word in the system or too long (max. 16 characters). Consequences The task will not be installed in the system. Recommended actions Change the configuration of the task name and restart the controller. 20351, Max number of tasks exceeded Description The maximum number of tasks, arg , of the configuration type arg is exceeded. Consequences All configured tasks will not be installed. Recommended actions Change the configuration and restart the system. 20352, Not a valid motion planner name Description The motion planner name for mechanical unit group arg in arg is not correct. The reason can be one of the following: 1. empty name 2. not present in the motion configuration 3. already in use by another mechanical unit group Consequences The system will not be able to use. Recommended actions Change the configuration and restart the controller. 20353, Mechanical unit not found Description The mechanical unit arg in arg can not be found in the list of configured mechanical units. Consequences It is not possible to execute any RAPID instructions that use the configured mechanical units. Probable causes The unit is probably not present in the motion configuration. Recommended actions Change the configuration and restart the controller.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	129	6 Trouble shooting by Event log 126 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes -The fan power cabling may be damaged or not connected correctly to motor or contactor unit. -The fan or the Drive Module Power Supply may be faulty. Recommended actions 1) Make sure the fan cable is correctly connected 2) Make sure the fan is free to rotate and that the air flow is not obstructed. 3) Make sure the Drive Module Power Supply output and input voltages are within specified limits as detailed in the Trouble shooting manual. Replace any faulty unit. 20310, SC arg Communication Failed Description An error occurred while trying to communicate with Safety Controller (SC) arg Recommended actions - Check Safety Controller cabling. - Check Safety Controller health. Warm start controller, after performing recommended actions. 20311, Enable 1 open Description The ENABLE 1 circuit monitoring the Safety System has been opened. Consequences The system goes to status SYS HALT. Probable causes There may be an internal fault in the Safety System or the internal supervision has detected a fault. Recommended actions 1) Check all connections to the Safety System. 2) If faulty, replace the faulty board. 20312, Enable 2 open Description The ENABLE 2 circuit monitoring the Axis Computer has been opened. Consequences The system goes to status SYS HALT. Probable causes There may be a connection problem between Main Computer and Axis Computer. Recommended actions 1) Check all connections to the axis computer. 2) Check cables conntected to the Safety System. 20313, Enable1 supervision fault Description The ENABLE1 circuit has been broken. This circuit monitors the function of the Safety System and the main computer. Consequences The system goes to status SYS HALT. Probable causes A fault, probably a software fault, has been detected by any of the units supervised by the ENABLE1 circuit. Recommended actions 1) Attempt restarting by pressing the Motors ON button. If restarting is IMPOSSIBLE it indicates a hardware fault in Safety System, axis computer. If restarting is POSSIBLE, it indicates a software fault. In such case, contact your local ABB representative. 2) Determine which unit is faulty by checking its indication LEDs. The LEDs are described in the Trouble Shooting Manual. Replace the faulty unit. 20314, Enable2 supervision fault Description The ENABLE2 circuit to drive module 1 has been broken. This circuit monitors e.g. the function of the Safety System and the axis computer. Consequences The system goes to status SYS HALT. Probable causes A fault, probably a software fault, has been detected by any of the units supervised by the ENABLE2 circuit. Recommended actions 1) Attempt restarting by pressing the Motors ON button. If restarting is IMPOSSIBLE it indicates a hardware fault in Safety System, axis computer. If restarting is POSSIBLE, it indicates a software fault. In such case, contact your local ABB representative. 2) Determine which unit is faulty by checking its indication LEDs. The LEDs are described in the Trouble Shooting Manual. Replace the faulty unit. 20315, Enable2 Supervision fault Description The ENABLE2 circuit to drive module 2 has been broken. This circuit monitors e.g. the function of the Safety System and the axis computer. Consequences The system goes to status SYS HALT. Probable causes A fault, probably a software fault, has been detected by any of the units supervised by the ENABLE2 circuit. 6 Trouble shooting by Event log 127 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Attempt restarting by pressing the Motors ON button. If restarting is IMPOSSIBLE it indicates a hardware fault in safety board, axis computer. If restarting is POSSIBLE, it indicates a software fault. In such case, contact your local ABB representative. 2) Determine which unit is faulty by checking its indication LEDs. The LEDs are described in the Trouble Shooting Manual. Replace the faulty unit. 20316, Enable2 Supervision fault Description The ENABLE2 circuit to drive module 3 has been broken. This circuit monitors e.g. the function of the Safety System and the axis computer. Consequences The system goes to status SYS HALT. Probable causes A fault, probably a software fault, has been detected by any of the units supervised by the ENABLE2 circuit. Recommended actions 1) Attempt restarting by pressing the Motors ON button. If restarting is IMPOSSIBLE it indicates a hardware fault in Safety System, axis computer. If restarting is POSSIBLE, it indicates a software fault. In such case, contact your local ABB representative. 2) Determine which unit is faulty by checking its indication LEDs. The LEDs are described in the Trouble Shooting Manual. Replace the faulty unit. 20317, Enable2 Supervision fault Description The ENABLE2 circuit to drive module 4 has been broken. This circuit monitors e.g. the function of the Safety System and the axis computer. Consequences The system goes to status SYS HALT. Probable causes A fault, probably a software fault, has been detected by any of the units supervised by the ENABLE2 circuit. Recommended actions 1) Attempt restarting by pressing the Motors ON button. If restarting is IMPOSSIBLE it indicates a hardware fault in Safety System, Axis computer. If restarting is POSSIBLE, it indicates a software fault. In such case, contact your local ABB representative. 2) Determine which unit is faulty by checking its indication LEDs. The LEDs are described in the Trouble Shooting Manual. Replace the faulty unit. 20350, Not a valid task name Description The task name arg cannot be used as a name of a task. It is either already used as an installed symbol, a reserved word in the system or too long (max. 16 characters). Consequences The task will not be installed in the system. Recommended actions Change the configuration of the task name and restart the controller. 20351, Max number of tasks exceeded Description The maximum number of tasks, arg , of the configuration type arg is exceeded. Consequences All configured tasks will not be installed. Recommended actions Change the configuration and restart the system. 20352, Not a valid motion planner name Description The motion planner name for mechanical unit group arg in arg is not correct. The reason can be one of the following: 1. empty name 2. not present in the motion configuration 3. already in use by another mechanical unit group Consequences The system will not be able to use. Recommended actions Change the configuration and restart the controller. 20353, Mechanical unit not found Description The mechanical unit arg in arg can not be found in the list of configured mechanical units. Consequences It is not possible to execute any RAPID instructions that use the configured mechanical units. Probable causes The unit is probably not present in the motion configuration. Recommended actions Change the configuration and restart the controller. 6 Trouble shooting by Event log 128 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20354, The argument is undefined Description The configured argument arg for task arg is not a valid type. Consequences The behaviour of the task will be undefined. Recommended actions Change the configuration and restart the controller. 20355, Mechanical unit group name not correct Description The configured name of arg in task arg is not correct. The reason could be: 1. The argument is not used in the configuration 2. The configured name is not a member of the mechanical unit group 3. The configured name is already used by another task. Consequences The task will not be installed or it will not be possible to execute RAPID motion instructions. Recommended actions Change the configuration and restart the controller. 20356, Maximum number of motion tasks exceeded Description Only arg tasks are allowed to control mechanical units i.e. execute RAPID move instructions. Recommended actions Change the configuration and restart the controller. 20357, No configured motion task Description No task is configured to control mechanical units i.e. execute RAPID move instructions. Consequences It is not possible to execute any RAPID move instructions. Recommended actions Change the configuration to include a task controlling mechanical units. Restart the controller. 20358, No members of arg configured Description The configuration type is required in a multi robot system. Consequences It is not possible to execute any RAPID move instructions. Recommended actions Change the configuration and restart the controller. 20359, Cfg type arg is configured Description The type was found but not expected in a system with current options. Recommended actions Check if the right configuration file is loaded or remove all instances of the type. Restart the controller. 20360, Unknown event in cfg type arg Description The event arg is not a system event. Recommended actions Change the configuration and restart the system. 20361, Only shared modules in the shared task Description The module arg is not configured shared and cannot be loaded into the shared task. Recommended actions Change the configuration and restart the system. 20362, Not defined task name Description The task arg in cfg type arg is not configured in the system. Recommended actions Change the configuration and restart the system. 20363, Module not a system module Description The module arg loaded from the file arg is not a system module. Recommended actions Change the file suffix or add a module attribute to the module. Load the module again or restart the system. 20364, Max number of mechanical unit groups exceeded Description The maximum number of mechanical unit groups, arg , of the configuration type arg is exceeded.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	130	6 Trouble shooting by Event log 127 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Attempt restarting by pressing the Motors ON button. If restarting is IMPOSSIBLE it indicates a hardware fault in safety board, axis computer. If restarting is POSSIBLE, it indicates a software fault. In such case, contact your local ABB representative. 2) Determine which unit is faulty by checking its indication LEDs. The LEDs are described in the Trouble Shooting Manual. Replace the faulty unit. 20316, Enable2 Supervision fault Description The ENABLE2 circuit to drive module 3 has been broken. This circuit monitors e.g. the function of the Safety System and the axis computer. Consequences The system goes to status SYS HALT. Probable causes A fault, probably a software fault, has been detected by any of the units supervised by the ENABLE2 circuit. Recommended actions 1) Attempt restarting by pressing the Motors ON button. If restarting is IMPOSSIBLE it indicates a hardware fault in Safety System, axis computer. If restarting is POSSIBLE, it indicates a software fault. In such case, contact your local ABB representative. 2) Determine which unit is faulty by checking its indication LEDs. The LEDs are described in the Trouble Shooting Manual. Replace the faulty unit. 20317, Enable2 Supervision fault Description The ENABLE2 circuit to drive module 4 has been broken. This circuit monitors e.g. the function of the Safety System and the axis computer. Consequences The system goes to status SYS HALT. Probable causes A fault, probably a software fault, has been detected by any of the units supervised by the ENABLE2 circuit. Recommended actions 1) Attempt restarting by pressing the Motors ON button. If restarting is IMPOSSIBLE it indicates a hardware fault in Safety System, Axis computer. If restarting is POSSIBLE, it indicates a software fault. In such case, contact your local ABB representative. 2) Determine which unit is faulty by checking its indication LEDs. The LEDs are described in the Trouble Shooting Manual. Replace the faulty unit. 20350, Not a valid task name Description The task name arg cannot be used as a name of a task. It is either already used as an installed symbol, a reserved word in the system or too long (max. 16 characters). Consequences The task will not be installed in the system. Recommended actions Change the configuration of the task name and restart the controller. 20351, Max number of tasks exceeded Description The maximum number of tasks, arg , of the configuration type arg is exceeded. Consequences All configured tasks will not be installed. Recommended actions Change the configuration and restart the system. 20352, Not a valid motion planner name Description The motion planner name for mechanical unit group arg in arg is not correct. The reason can be one of the following: 1. empty name 2. not present in the motion configuration 3. already in use by another mechanical unit group Consequences The system will not be able to use. Recommended actions Change the configuration and restart the controller. 20353, Mechanical unit not found Description The mechanical unit arg in arg can not be found in the list of configured mechanical units. Consequences It is not possible to execute any RAPID instructions that use the configured mechanical units. Probable causes The unit is probably not present in the motion configuration. Recommended actions Change the configuration and restart the controller. 6 Trouble shooting by Event log 128 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20354, The argument is undefined Description The configured argument arg for task arg is not a valid type. Consequences The behaviour of the task will be undefined. Recommended actions Change the configuration and restart the controller. 20355, Mechanical unit group name not correct Description The configured name of arg in task arg is not correct. The reason could be: 1. The argument is not used in the configuration 2. The configured name is not a member of the mechanical unit group 3. The configured name is already used by another task. Consequences The task will not be installed or it will not be possible to execute RAPID motion instructions. Recommended actions Change the configuration and restart the controller. 20356, Maximum number of motion tasks exceeded Description Only arg tasks are allowed to control mechanical units i.e. execute RAPID move instructions. Recommended actions Change the configuration and restart the controller. 20357, No configured motion task Description No task is configured to control mechanical units i.e. execute RAPID move instructions. Consequences It is not possible to execute any RAPID move instructions. Recommended actions Change the configuration to include a task controlling mechanical units. Restart the controller. 20358, No members of arg configured Description The configuration type is required in a multi robot system. Consequences It is not possible to execute any RAPID move instructions. Recommended actions Change the configuration and restart the controller. 20359, Cfg type arg is configured Description The type was found but not expected in a system with current options. Recommended actions Check if the right configuration file is loaded or remove all instances of the type. Restart the controller. 20360, Unknown event in cfg type arg Description The event arg is not a system event. Recommended actions Change the configuration and restart the system. 20361, Only shared modules in the shared task Description The module arg is not configured shared and cannot be loaded into the shared task. Recommended actions Change the configuration and restart the system. 20362, Not defined task name Description The task arg in cfg type arg is not configured in the system. Recommended actions Change the configuration and restart the system. 20363, Module not a system module Description The module arg loaded from the file arg is not a system module. Recommended actions Change the file suffix or add a module attribute to the module. Load the module again or restart the system. 20364, Max number of mechanical unit groups exceeded Description The maximum number of mechanical unit groups, arg , of the configuration type arg is exceeded. 6 Trouble shooting by Event log 129 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences Exceeded instances are ignored. Recommended actions Change the configuration and restart the controller. 20365, Update of configuration is done Description All tasks are reset to its main routine due to configuration changes. Recommended actions 20366, Type error in task configuration Description The task arg is configured with wrong type. Task configured to control mechanical units i.e. execute RAPID move instructions must be of type arg . Consequences The task will not be installed. Recommended actions Change the configuration and restart the controller. 20367, No configured mechanical units Description The instance arg of configuration type arg has no mechanical unit argument. Consequences It will not be possible to perform any actions against the motion system, i.e. execute RAPID move instructions. Recommended actions Change the configuration and restart the controller. 20368, Not connected mechanical unit group Description There is no RAPID motion task connected with the mechanical unit group arg . Consequences It will not be possible to use the mechanical units that belong to this group. Probable causes The cause of this error can be a missing RAPID task instance in the controller domain of the configuration or a task that has not been configured as a motion task. Recommended actions 1. Add a motion task instance that is connected to the mechanical unit group. 2. Change an existing non-motion task to a motion task. 3. Remove the mechanical unit group. 4. Check for misspelled names. 20369, Confusing configuration of system parameters. Description There is a mixture of old and new structure of type System Misc. Consequences It is possible that not the correct parameters are configured. Probable causes Configuration of old and new structure has been loaded into the system. Recommended actions 1. Check that the correct parameters are configured. 2. Update the parameters in System Misc with correct values. 3. Save the controller domain and replace the old config file. 20370, Failed to read configuration data for regain distance Description The system failed to read the configuration data for the type < arg >. The regain distance is the limit when the system will warn before a start with regain movement. Consequences Default value for the regain distance will be used. Probable causes -The sys.cfg file loaded into the system does not contain any regain distance information. -No sys.cfg file has been loaded due to file errors. Recommended actions 1) Load a new sys.cfg file and restart the system 20371, A default mechanical unit group is used Description The configuration of task arg has no connection to arg . The attribute arg is required in a multimove system and is missing. Consequences The task performs no movement by the mechanical unit, but can read motion data. The RAPID functions may fail, if they read motion data and is connected to the wrong mechanical unit. The mechanical unit group in arg has been connected to the task. Probable causes -The attribute was not specified when the configuration was created. -The configuration file could have been created in a non-multi move system.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	131	6 Trouble shooting by Event log 128 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20354, The argument is undefined Description The configured argument arg for task arg is not a valid type. Consequences The behaviour of the task will be undefined. Recommended actions Change the configuration and restart the controller. 20355, Mechanical unit group name not correct Description The configured name of arg in task arg is not correct. The reason could be: 1. The argument is not used in the configuration 2. The configured name is not a member of the mechanical unit group 3. The configured name is already used by another task. Consequences The task will not be installed or it will not be possible to execute RAPID motion instructions. Recommended actions Change the configuration and restart the controller. 20356, Maximum number of motion tasks exceeded Description Only arg tasks are allowed to control mechanical units i.e. execute RAPID move instructions. Recommended actions Change the configuration and restart the controller. 20357, No configured motion task Description No task is configured to control mechanical units i.e. execute RAPID move instructions. Consequences It is not possible to execute any RAPID move instructions. Recommended actions Change the configuration to include a task controlling mechanical units. Restart the controller. 20358, No members of arg configured Description The configuration type is required in a multi robot system. Consequences It is not possible to execute any RAPID move instructions. Recommended actions Change the configuration and restart the controller. 20359, Cfg type arg is configured Description The type was found but not expected in a system with current options. Recommended actions Check if the right configuration file is loaded or remove all instances of the type. Restart the controller. 20360, Unknown event in cfg type arg Description The event arg is not a system event. Recommended actions Change the configuration and restart the system. 20361, Only shared modules in the shared task Description The module arg is not configured shared and cannot be loaded into the shared task. Recommended actions Change the configuration and restart the system. 20362, Not defined task name Description The task arg in cfg type arg is not configured in the system. Recommended actions Change the configuration and restart the system. 20363, Module not a system module Description The module arg loaded from the file arg is not a system module. Recommended actions Change the file suffix or add a module attribute to the module. Load the module again or restart the system. 20364, Max number of mechanical unit groups exceeded Description The maximum number of mechanical unit groups, arg , of the configuration type arg is exceeded. 6 Trouble shooting by Event log 129 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences Exceeded instances are ignored. Recommended actions Change the configuration and restart the controller. 20365, Update of configuration is done Description All tasks are reset to its main routine due to configuration changes. Recommended actions 20366, Type error in task configuration Description The task arg is configured with wrong type. Task configured to control mechanical units i.e. execute RAPID move instructions must be of type arg . Consequences The task will not be installed. Recommended actions Change the configuration and restart the controller. 20367, No configured mechanical units Description The instance arg of configuration type arg has no mechanical unit argument. Consequences It will not be possible to perform any actions against the motion system, i.e. execute RAPID move instructions. Recommended actions Change the configuration and restart the controller. 20368, Not connected mechanical unit group Description There is no RAPID motion task connected with the mechanical unit group arg . Consequences It will not be possible to use the mechanical units that belong to this group. Probable causes The cause of this error can be a missing RAPID task instance in the controller domain of the configuration or a task that has not been configured as a motion task. Recommended actions 1. Add a motion task instance that is connected to the mechanical unit group. 2. Change an existing non-motion task to a motion task. 3. Remove the mechanical unit group. 4. Check for misspelled names. 20369, Confusing configuration of system parameters. Description There is a mixture of old and new structure of type System Misc. Consequences It is possible that not the correct parameters are configured. Probable causes Configuration of old and new structure has been loaded into the system. Recommended actions 1. Check that the correct parameters are configured. 2. Update the parameters in System Misc with correct values. 3. Save the controller domain and replace the old config file. 20370, Failed to read configuration data for regain distance Description The system failed to read the configuration data for the type < arg >. The regain distance is the limit when the system will warn before a start with regain movement. Consequences Default value for the regain distance will be used. Probable causes -The sys.cfg file loaded into the system does not contain any regain distance information. -No sys.cfg file has been loaded due to file errors. Recommended actions 1) Load a new sys.cfg file and restart the system 20371, A default mechanical unit group is used Description The configuration of task arg has no connection to arg . The attribute arg is required in a multimove system and is missing. Consequences The task performs no movement by the mechanical unit, but can read motion data. The RAPID functions may fail, if they read motion data and is connected to the wrong mechanical unit. The mechanical unit group in arg has been connected to the task. Probable causes -The attribute was not specified when the configuration was created. -The configuration file could have been created in a non-multi move system. 6 Trouble shooting by Event log 130 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Make sure the correct mechanical unit group is connected to the task. 20372, Failed to read configuration data. Description The system failed to read the configuration data for the type < arg >. Consequences Hotedit or modpos will not be possible. Probable causes -The sys.cfg file loaded into the system does not contain hotedit and modpos information. -No sys.cfg file has been loaded due to file errors. Recommended actions Load a new sys.cfg file and restart the system 20380, No motion planner connected to mechanical unit Description The mechanical unit arg has no motion planner connected. Consequences It is not possible to use this mechanical unit in any operations such as calibration or activation. Probable causes The cause of this error is probably an error in the configuration. Recommended actions Check the motion and/or controller configuration. 20381, Error when recreating path after power fail Description The path wasn't successfully recreated. Consequences The Program Pointer must be moved before restarting the program. It's recommended to move the robot to a safe position though the robot might not follow the original path when restarted. Probable causes A number of errors may cause this. Faults causing the system to go to status SYS FAIL will generally also cause path recreate after powerfail to fail. Recommended actions 1) Check other event log messages occurring at the same time to determine the actual cause. 2) Fix the cause of the fault. 3) Move the robot to a safe position before restarting. The robot may not follow the original path. 20390, Start rejected Description Start/restart of program, via System IO, was rejected. The reason is that write access is held by arg using arg Recommended actions 20391, Start at main rejected Description Start of program at main, via System IO, was rejected. The reason is that write access is held by arg using arg Recommended actions 20392, Manual interrupt rejected Description Manual interrupt of program, via System IO, was rejected. The reason is that write access is held by arg using arg Recommended actions 20393, Load and start rejected Description Load and start of program, via System IO, was rejected. The reason is that write access is held by arg using arg Recommended actions 20394, Motors On and Start rejected. Description Motors On and Start/restart of program, via System IO, was rejected. The reason is that write access is held by arg using arg Recommended actions 20395, Load rejected Description Load of program via System IO, was rejected. The reason is that write access is held by arg using arg
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	132	6 Trouble shooting by Event log 129 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences Exceeded instances are ignored. Recommended actions Change the configuration and restart the controller. 20365, Update of configuration is done Description All tasks are reset to its main routine due to configuration changes. Recommended actions 20366, Type error in task configuration Description The task arg is configured with wrong type. Task configured to control mechanical units i.e. execute RAPID move instructions must be of type arg . Consequences The task will not be installed. Recommended actions Change the configuration and restart the controller. 20367, No configured mechanical units Description The instance arg of configuration type arg has no mechanical unit argument. Consequences It will not be possible to perform any actions against the motion system, i.e. execute RAPID move instructions. Recommended actions Change the configuration and restart the controller. 20368, Not connected mechanical unit group Description There is no RAPID motion task connected with the mechanical unit group arg . Consequences It will not be possible to use the mechanical units that belong to this group. Probable causes The cause of this error can be a missing RAPID task instance in the controller domain of the configuration or a task that has not been configured as a motion task. Recommended actions 1. Add a motion task instance that is connected to the mechanical unit group. 2. Change an existing non-motion task to a motion task. 3. Remove the mechanical unit group. 4. Check for misspelled names. 20369, Confusing configuration of system parameters. Description There is a mixture of old and new structure of type System Misc. Consequences It is possible that not the correct parameters are configured. Probable causes Configuration of old and new structure has been loaded into the system. Recommended actions 1. Check that the correct parameters are configured. 2. Update the parameters in System Misc with correct values. 3. Save the controller domain and replace the old config file. 20370, Failed to read configuration data for regain distance Description The system failed to read the configuration data for the type < arg >. The regain distance is the limit when the system will warn before a start with regain movement. Consequences Default value for the regain distance will be used. Probable causes -The sys.cfg file loaded into the system does not contain any regain distance information. -No sys.cfg file has been loaded due to file errors. Recommended actions 1) Load a new sys.cfg file and restart the system 20371, A default mechanical unit group is used Description The configuration of task arg has no connection to arg . The attribute arg is required in a multimove system and is missing. Consequences The task performs no movement by the mechanical unit, but can read motion data. The RAPID functions may fail, if they read motion data and is connected to the wrong mechanical unit. The mechanical unit group in arg has been connected to the task. Probable causes -The attribute was not specified when the configuration was created. -The configuration file could have been created in a non-multi move system. 6 Trouble shooting by Event log 130 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Make sure the correct mechanical unit group is connected to the task. 20372, Failed to read configuration data. Description The system failed to read the configuration data for the type < arg >. Consequences Hotedit or modpos will not be possible. Probable causes -The sys.cfg file loaded into the system does not contain hotedit and modpos information. -No sys.cfg file has been loaded due to file errors. Recommended actions Load a new sys.cfg file and restart the system 20380, No motion planner connected to mechanical unit Description The mechanical unit arg has no motion planner connected. Consequences It is not possible to use this mechanical unit in any operations such as calibration or activation. Probable causes The cause of this error is probably an error in the configuration. Recommended actions Check the motion and/or controller configuration. 20381, Error when recreating path after power fail Description The path wasn't successfully recreated. Consequences The Program Pointer must be moved before restarting the program. It's recommended to move the robot to a safe position though the robot might not follow the original path when restarted. Probable causes A number of errors may cause this. Faults causing the system to go to status SYS FAIL will generally also cause path recreate after powerfail to fail. Recommended actions 1) Check other event log messages occurring at the same time to determine the actual cause. 2) Fix the cause of the fault. 3) Move the robot to a safe position before restarting. The robot may not follow the original path. 20390, Start rejected Description Start/restart of program, via System IO, was rejected. The reason is that write access is held by arg using arg Recommended actions 20391, Start at main rejected Description Start of program at main, via System IO, was rejected. The reason is that write access is held by arg using arg Recommended actions 20392, Manual interrupt rejected Description Manual interrupt of program, via System IO, was rejected. The reason is that write access is held by arg using arg Recommended actions 20393, Load and start rejected Description Load and start of program, via System IO, was rejected. The reason is that write access is held by arg using arg Recommended actions 20394, Motors On and Start rejected. Description Motors On and Start/restart of program, via System IO, was rejected. The reason is that write access is held by arg using arg Recommended actions 20395, Load rejected Description Load of program via System IO, was rejected. The reason is that write access is held by arg using arg 6 Trouble shooting by Event log 131 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20396, Manual interrupt rejected Description Manual interrupt of program, via System IO, was rejected in task arg . Manual interrupt is not allowed during synchronized movement. 20397, Manual interrupt rejected Description Manual interrupt of program, via System IO, was rejected in task arg . The interrupt is connected to arg , which is not a valid RAPID procedure. Consequences arg will not be executed. Probable causes 1. arg does not exist. 2. arg is not a procedure (PROC) that takes zero (0) parameters. Recommended actions Make sure that arg is an existing procedure (PROC) that takes zero (0) parameters. 20398, Automatic Mode Rejected Description A stopped static/semistatic task (alias background task) could not be started when automatic mode was requested. Consequences The system can not enter automatic mode. Probable causes A stopped static/semistatic task could not be started. Recommended actions 1) Switch back to manual mode. 2) Make sure that all static/semistatic tasks has a program/module containing the configured production entry. 3) Make sure that no static/semistatic task has any syntax errors. 4) Switch back to automatic mode and confirm. 20399, Static/Semistatic task started Description At least on static/semistatic task (alias background task) was not executing after startup in automatic mode. Consequences Execution was started in at least one static/semistatic task. Probable causes System was switched to automatic mode during warm start. Recommended actions None, system has automatically reset debug settings. To keep debug settings in auto: 1) Switch back to auto mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to NO. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20400, Debug Settings In Auto Description A static/semistatic task (alias background task) has been stopped. Consequences The static/semistatic task will not be started. System will not be in full production mode in auto. Recommended actions For full production mode: 1) Switch back to manual mode. 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to Yes. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20401, Too many CFG instances Description There are too many instances arg of type arg in topic arg . Consequences The wrong instance may be used and cause unexpected behavior. Probable causes There are multiple instances of arg of type arg in topic arg . Recommended actions Remove all instances but one. 20440, Failed to initialize FW upgrade framework Description The firmware upgrade framework for hardware boards could not be initialized Consequences No firmware upgrade of hardware boards will be performed Probable causes An invalid xml file in the controller installation: arg Recommended actions For developers: - Correct the file. Use the hw_compatibility.xsd schema to verify.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	133	6 Trouble shooting by Event log 130 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Make sure the correct mechanical unit group is connected to the task. 20372, Failed to read configuration data. Description The system failed to read the configuration data for the type < arg >. Consequences Hotedit or modpos will not be possible. Probable causes -The sys.cfg file loaded into the system does not contain hotedit and modpos information. -No sys.cfg file has been loaded due to file errors. Recommended actions Load a new sys.cfg file and restart the system 20380, No motion planner connected to mechanical unit Description The mechanical unit arg has no motion planner connected. Consequences It is not possible to use this mechanical unit in any operations such as calibration or activation. Probable causes The cause of this error is probably an error in the configuration. Recommended actions Check the motion and/or controller configuration. 20381, Error when recreating path after power fail Description The path wasn't successfully recreated. Consequences The Program Pointer must be moved before restarting the program. It's recommended to move the robot to a safe position though the robot might not follow the original path when restarted. Probable causes A number of errors may cause this. Faults causing the system to go to status SYS FAIL will generally also cause path recreate after powerfail to fail. Recommended actions 1) Check other event log messages occurring at the same time to determine the actual cause. 2) Fix the cause of the fault. 3) Move the robot to a safe position before restarting. The robot may not follow the original path. 20390, Start rejected Description Start/restart of program, via System IO, was rejected. The reason is that write access is held by arg using arg Recommended actions 20391, Start at main rejected Description Start of program at main, via System IO, was rejected. The reason is that write access is held by arg using arg Recommended actions 20392, Manual interrupt rejected Description Manual interrupt of program, via System IO, was rejected. The reason is that write access is held by arg using arg Recommended actions 20393, Load and start rejected Description Load and start of program, via System IO, was rejected. The reason is that write access is held by arg using arg Recommended actions 20394, Motors On and Start rejected. Description Motors On and Start/restart of program, via System IO, was rejected. The reason is that write access is held by arg using arg Recommended actions 20395, Load rejected Description Load of program via System IO, was rejected. The reason is that write access is held by arg using arg 6 Trouble shooting by Event log 131 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20396, Manual interrupt rejected Description Manual interrupt of program, via System IO, was rejected in task arg . Manual interrupt is not allowed during synchronized movement. 20397, Manual interrupt rejected Description Manual interrupt of program, via System IO, was rejected in task arg . The interrupt is connected to arg , which is not a valid RAPID procedure. Consequences arg will not be executed. Probable causes 1. arg does not exist. 2. arg is not a procedure (PROC) that takes zero (0) parameters. Recommended actions Make sure that arg is an existing procedure (PROC) that takes zero (0) parameters. 20398, Automatic Mode Rejected Description A stopped static/semistatic task (alias background task) could not be started when automatic mode was requested. Consequences The system can not enter automatic mode. Probable causes A stopped static/semistatic task could not be started. Recommended actions 1) Switch back to manual mode. 2) Make sure that all static/semistatic tasks has a program/module containing the configured production entry. 3) Make sure that no static/semistatic task has any syntax errors. 4) Switch back to automatic mode and confirm. 20399, Static/Semistatic task started Description At least on static/semistatic task (alias background task) was not executing after startup in automatic mode. Consequences Execution was started in at least one static/semistatic task. Probable causes System was switched to automatic mode during warm start. Recommended actions None, system has automatically reset debug settings. To keep debug settings in auto: 1) Switch back to auto mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to NO. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20400, Debug Settings In Auto Description A static/semistatic task (alias background task) has been stopped. Consequences The static/semistatic task will not be started. System will not be in full production mode in auto. Recommended actions For full production mode: 1) Switch back to manual mode. 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to Yes. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20401, Too many CFG instances Description There are too many instances arg of type arg in topic arg . Consequences The wrong instance may be used and cause unexpected behavior. Probable causes There are multiple instances of arg of type arg in topic arg . Recommended actions Remove all instances but one. 20440, Failed to initialize FW upgrade framework Description The firmware upgrade framework for hardware boards could not be initialized Consequences No firmware upgrade of hardware boards will be performed Probable causes An invalid xml file in the controller installation: arg Recommended actions For developers: - Correct the file. Use the hw_compatibility.xsd schema to verify. 6 Trouble shooting by Event log 132 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. For other users: - Reinstall the system. 20441, Failed to initialize firmware patch Description Failed to initialize the firmware patch handling for hardware boards. Consequences No firmware patches for hardware boards will be applied Probable causes The firmware patch file was invalid: arg Recommended actions Correct the patch file. Use the schema hw_compatibility.xsd to verify. 20443, Multiple firmware upgrade restarts Description A new restart to firmware upgrade mode was ordered after two consecutive upgrade restarts. Consequences No further restart to firmware upgrade mode was performed. Probable causes Firmware upgrade of a hardware board has most likely failed. The board's firmware or hardware may be corrupt. Recommended actions Check the event log for previous error messages. 20450, SC arg CBC Speed exceeded Description Cyclic Brake Check (CBC) speed limit is exceeded in Safety Controller (SC) on Mechanical unit arg , when Brake check is required Recommended actions Decrease speed and execute Brake check 20451, SC arg Not synchronized Description Safety Controller (SC) arg is not synchronized with supervised Mechanical units. Recommended actions Move all Mechanical units supervised by Safety Controller arg to the synchronization positions defined in the Safety Configuration. 20452, SC arg Synchronized Description Safety Controller (SC) arg is now synchronized to supervised Mechanical units. Safety supervision can be used. 20453, SC arg Wrong Sync. Position Description The positions of the supervised Mechanical units do not match the synchronization positions defined in the Safety Configuration for Safety Controller (SC) arg on axis arg . Recommended actions - Check that all supervised Mechanical units are positioned at the configured synchronization position. - Check that the synchronization switch is working properly. - Check that motor calibration and revolution counters are updated and correct. - Check that the synchronization position in the Safety Configuration is correct. - Check for configuration error. - Download Motor calibration values. - Check if axis 4 or 6 is configured as independent, if YES, check that the EPS configuration is configured likewise. 20454, SC arg Servo-Lag Limit exceeded Description Safety Controller (SC) arg detected a too big difference between the ordered and actual position, for Mechanical unit arg on axis arg . Recommended actions - Check for collision. - If using external axis, check Servo Lag settings in the Safety Configuration. - If using Soft Servo, Check that the Operational Safety Range (OSR) Tolerance in the Safety Configuration is not set too low - Verify that revolution counters are updated. - Check for communication problems to the Main Computer, Axis Computer or the Serial Measurement Board. - Check if tool weight is correctly defined. 20455, SC arg Incorrect Position Value Description Incorrect position value from Serial Measurement Board detected by Safety Controller (SC) arg on Mechanical unit arg . Recommended actions - Check resolver and resolver connections. - Replace Serial Measurement Board. - Replace resolver. 20456, SC arg Reference Data Timeout Description The Robot Controller has stopped sending reference data to Safety Controller (SC) arg . Recommended actions 1. Check previous error logs for possible causes.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	134	6 Trouble shooting by Event log 131 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20396, Manual interrupt rejected Description Manual interrupt of program, via System IO, was rejected in task arg . Manual interrupt is not allowed during synchronized movement. 20397, Manual interrupt rejected Description Manual interrupt of program, via System IO, was rejected in task arg . The interrupt is connected to arg , which is not a valid RAPID procedure. Consequences arg will not be executed. Probable causes 1. arg does not exist. 2. arg is not a procedure (PROC) that takes zero (0) parameters. Recommended actions Make sure that arg is an existing procedure (PROC) that takes zero (0) parameters. 20398, Automatic Mode Rejected Description A stopped static/semistatic task (alias background task) could not be started when automatic mode was requested. Consequences The system can not enter automatic mode. Probable causes A stopped static/semistatic task could not be started. Recommended actions 1) Switch back to manual mode. 2) Make sure that all static/semistatic tasks has a program/module containing the configured production entry. 3) Make sure that no static/semistatic task has any syntax errors. 4) Switch back to automatic mode and confirm. 20399, Static/Semistatic task started Description At least on static/semistatic task (alias background task) was not executing after startup in automatic mode. Consequences Execution was started in at least one static/semistatic task. Probable causes System was switched to automatic mode during warm start. Recommended actions None, system has automatically reset debug settings. To keep debug settings in auto: 1) Switch back to auto mode 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to NO. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20400, Debug Settings In Auto Description A static/semistatic task (alias background task) has been stopped. Consequences The static/semistatic task will not be started. System will not be in full production mode in auto. Recommended actions For full production mode: 1) Switch back to manual mode. 2) Set system parameter Controller/Auto Condition Reset/ AllDebugSettings/Reset to Yes. 3) Switch back to automatic mode and confirm. 4) For more info, see the Technical Reference Manual - System Parameters. 20401, Too many CFG instances Description There are too many instances arg of type arg in topic arg . Consequences The wrong instance may be used and cause unexpected behavior. Probable causes There are multiple instances of arg of type arg in topic arg . Recommended actions Remove all instances but one. 20440, Failed to initialize FW upgrade framework Description The firmware upgrade framework for hardware boards could not be initialized Consequences No firmware upgrade of hardware boards will be performed Probable causes An invalid xml file in the controller installation: arg Recommended actions For developers: - Correct the file. Use the hw_compatibility.xsd schema to verify. 6 Trouble shooting by Event log 132 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. For other users: - Reinstall the system. 20441, Failed to initialize firmware patch Description Failed to initialize the firmware patch handling for hardware boards. Consequences No firmware patches for hardware boards will be applied Probable causes The firmware patch file was invalid: arg Recommended actions Correct the patch file. Use the schema hw_compatibility.xsd to verify. 20443, Multiple firmware upgrade restarts Description A new restart to firmware upgrade mode was ordered after two consecutive upgrade restarts. Consequences No further restart to firmware upgrade mode was performed. Probable causes Firmware upgrade of a hardware board has most likely failed. The board's firmware or hardware may be corrupt. Recommended actions Check the event log for previous error messages. 20450, SC arg CBC Speed exceeded Description Cyclic Brake Check (CBC) speed limit is exceeded in Safety Controller (SC) on Mechanical unit arg , when Brake check is required Recommended actions Decrease speed and execute Brake check 20451, SC arg Not synchronized Description Safety Controller (SC) arg is not synchronized with supervised Mechanical units. Recommended actions Move all Mechanical units supervised by Safety Controller arg to the synchronization positions defined in the Safety Configuration. 20452, SC arg Synchronized Description Safety Controller (SC) arg is now synchronized to supervised Mechanical units. Safety supervision can be used. 20453, SC arg Wrong Sync. Position Description The positions of the supervised Mechanical units do not match the synchronization positions defined in the Safety Configuration for Safety Controller (SC) arg on axis arg . Recommended actions - Check that all supervised Mechanical units are positioned at the configured synchronization position. - Check that the synchronization switch is working properly. - Check that motor calibration and revolution counters are updated and correct. - Check that the synchronization position in the Safety Configuration is correct. - Check for configuration error. - Download Motor calibration values. - Check if axis 4 or 6 is configured as independent, if YES, check that the EPS configuration is configured likewise. 20454, SC arg Servo-Lag Limit exceeded Description Safety Controller (SC) arg detected a too big difference between the ordered and actual position, for Mechanical unit arg on axis arg . Recommended actions - Check for collision. - If using external axis, check Servo Lag settings in the Safety Configuration. - If using Soft Servo, Check that the Operational Safety Range (OSR) Tolerance in the Safety Configuration is not set too low - Verify that revolution counters are updated. - Check for communication problems to the Main Computer, Axis Computer or the Serial Measurement Board. - Check if tool weight is correctly defined. 20455, SC arg Incorrect Position Value Description Incorrect position value from Serial Measurement Board detected by Safety Controller (SC) arg on Mechanical unit arg . Recommended actions - Check resolver and resolver connections. - Replace Serial Measurement Board. - Replace resolver. 20456, SC arg Reference Data Timeout Description The Robot Controller has stopped sending reference data to Safety Controller (SC) arg . Recommended actions 1. Check previous error logs for possible causes. 6 Trouble shooting by Event log 133 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 2. Restart System. 20457, SC arg Corrupt Safety Configuration Description The Safety Configuration for Safety Controller (SC) arg is corrupt or contains invalid data. Recommended actions - Warm start Robot Controller. - Download a Safety Configuration to the Safety Controller. - Reinstall System. 20458, SC arg Internal Failure Description Internal Failure in Safety Controller (SC) arg . Recommended actions - Check Safety Controller cabling. - Check Safety Controller health on LED - Replace Safety Controller if remaining error 20459, SC arg Input/Output Failure Description I/O Error on Safety Controller (SC) arg . Recommended actions - Check Safety Controller cabling. - Check Safety Controller health. Warm start Robot Controller, after performing recommended actions. 20460, SC arg Safety Configuration not found Description Failed to retrieve Safety Configuration for Safety Controller (SC) arg . Recommended actions - Warm start Robot Controller. - Download a Safety Configuration to the SC. - Reinstall System. 20461, SC arg Robot Configuration not found Description Failed to retrieve Robot Configuration for Safety Controller (SC) arg . Recommended actions - Warm start Robot Controller. - Reinstall System. 20462, SC arg Calibration Offset not found Description Failed to retrieve Motor Calibration offsets for Safety Controller (SC) arg . Recommended actions Download new Calibration offsets to the SC. 20463, SC arg Safety Configuration downloaded Description Download of Safety Configuration was successful for Safety Controller (SC) arg . 20464, SC arg OSR Limit exceeded Description Safety Controller (SC) arg detected a too big difference between the ordered and actual position inside Operational Safety Range (OSR) , for Mechanical unit arg on axis arg . Recommended actions - Check for collision. - Check that Operational Safety Range (OSR) Tolerance in the Safety Configuration is not set too low. - Synchronize the Safety Controller, if the revolution counters have been updated since last synchronization. 20465, SC arg SAS Speed exceeded Description Safe Axis Speed (SAS) violation on Mechanical unit arg Axis arg on Safety Controller (SC) Recommended actions Decrease speed on Axis arg 20466, SC arg Input/Output Failure Description I/O Error on Safety Controller (SC) arg I/O arg Type arg Type 1: Input Type 2: Output Probable causes - Wrong connection to I/O terminals on SC - Two channel I/O mismatch Recommended actions - Check SC cabling. - Check SC health. Warm start Robot Controller, after performing recommended actions.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	135	6 Trouble shooting by Event log 132 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. For other users: - Reinstall the system. 20441, Failed to initialize firmware patch Description Failed to initialize the firmware patch handling for hardware boards. Consequences No firmware patches for hardware boards will be applied Probable causes The firmware patch file was invalid: arg Recommended actions Correct the patch file. Use the schema hw_compatibility.xsd to verify. 20443, Multiple firmware upgrade restarts Description A new restart to firmware upgrade mode was ordered after two consecutive upgrade restarts. Consequences No further restart to firmware upgrade mode was performed. Probable causes Firmware upgrade of a hardware board has most likely failed. The board's firmware or hardware may be corrupt. Recommended actions Check the event log for previous error messages. 20450, SC arg CBC Speed exceeded Description Cyclic Brake Check (CBC) speed limit is exceeded in Safety Controller (SC) on Mechanical unit arg , when Brake check is required Recommended actions Decrease speed and execute Brake check 20451, SC arg Not synchronized Description Safety Controller (SC) arg is not synchronized with supervised Mechanical units. Recommended actions Move all Mechanical units supervised by Safety Controller arg to the synchronization positions defined in the Safety Configuration. 20452, SC arg Synchronized Description Safety Controller (SC) arg is now synchronized to supervised Mechanical units. Safety supervision can be used. 20453, SC arg Wrong Sync. Position Description The positions of the supervised Mechanical units do not match the synchronization positions defined in the Safety Configuration for Safety Controller (SC) arg on axis arg . Recommended actions - Check that all supervised Mechanical units are positioned at the configured synchronization position. - Check that the synchronization switch is working properly. - Check that motor calibration and revolution counters are updated and correct. - Check that the synchronization position in the Safety Configuration is correct. - Check for configuration error. - Download Motor calibration values. - Check if axis 4 or 6 is configured as independent, if YES, check that the EPS configuration is configured likewise. 20454, SC arg Servo-Lag Limit exceeded Description Safety Controller (SC) arg detected a too big difference between the ordered and actual position, for Mechanical unit arg on axis arg . Recommended actions - Check for collision. - If using external axis, check Servo Lag settings in the Safety Configuration. - If using Soft Servo, Check that the Operational Safety Range (OSR) Tolerance in the Safety Configuration is not set too low - Verify that revolution counters are updated. - Check for communication problems to the Main Computer, Axis Computer or the Serial Measurement Board. - Check if tool weight is correctly defined. 20455, SC arg Incorrect Position Value Description Incorrect position value from Serial Measurement Board detected by Safety Controller (SC) arg on Mechanical unit arg . Recommended actions - Check resolver and resolver connections. - Replace Serial Measurement Board. - Replace resolver. 20456, SC arg Reference Data Timeout Description The Robot Controller has stopped sending reference data to Safety Controller (SC) arg . Recommended actions 1. Check previous error logs for possible causes. 6 Trouble shooting by Event log 133 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 2. Restart System. 20457, SC arg Corrupt Safety Configuration Description The Safety Configuration for Safety Controller (SC) arg is corrupt or contains invalid data. Recommended actions - Warm start Robot Controller. - Download a Safety Configuration to the Safety Controller. - Reinstall System. 20458, SC arg Internal Failure Description Internal Failure in Safety Controller (SC) arg . Recommended actions - Check Safety Controller cabling. - Check Safety Controller health on LED - Replace Safety Controller if remaining error 20459, SC arg Input/Output Failure Description I/O Error on Safety Controller (SC) arg . Recommended actions - Check Safety Controller cabling. - Check Safety Controller health. Warm start Robot Controller, after performing recommended actions. 20460, SC arg Safety Configuration not found Description Failed to retrieve Safety Configuration for Safety Controller (SC) arg . Recommended actions - Warm start Robot Controller. - Download a Safety Configuration to the SC. - Reinstall System. 20461, SC arg Robot Configuration not found Description Failed to retrieve Robot Configuration for Safety Controller (SC) arg . Recommended actions - Warm start Robot Controller. - Reinstall System. 20462, SC arg Calibration Offset not found Description Failed to retrieve Motor Calibration offsets for Safety Controller (SC) arg . Recommended actions Download new Calibration offsets to the SC. 20463, SC arg Safety Configuration downloaded Description Download of Safety Configuration was successful for Safety Controller (SC) arg . 20464, SC arg OSR Limit exceeded Description Safety Controller (SC) arg detected a too big difference between the ordered and actual position inside Operational Safety Range (OSR) , for Mechanical unit arg on axis arg . Recommended actions - Check for collision. - Check that Operational Safety Range (OSR) Tolerance in the Safety Configuration is not set too low. - Synchronize the Safety Controller, if the revolution counters have been updated since last synchronization. 20465, SC arg SAS Speed exceeded Description Safe Axis Speed (SAS) violation on Mechanical unit arg Axis arg on Safety Controller (SC) Recommended actions Decrease speed on Axis arg 20466, SC arg Input/Output Failure Description I/O Error on Safety Controller (SC) arg I/O arg Type arg Type 1: Input Type 2: Output Probable causes - Wrong connection to I/O terminals on SC - Two channel I/O mismatch Recommended actions - Check SC cabling. - Check SC health. Warm start Robot Controller, after performing recommended actions. 6 Trouble shooting by Event log 134 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20467, SC arg STS speed exceeded Description Safe reduced Tool Speed (STS) in Safety Controller (SC) on Mechanical unit arg too high. Cause arg . Probable causes 1. Tool0 speed 2. Elbow speed 3. Tool speed 4. Additional axis speed Recommended actions Reduce tool speed. 20468, SC arg STZ violation Description Safe Tool Zone (STZ) arg is violated on Mechanical unit arg . Cause arg Probable causes 1. Exceeded speed 2. Wrong tool position 3. Wrong tool orientation 4. Wrong elbow position 11. Wrong tool point 1 position 12. Wrong tool point 2 position 13. Wrong tool point 3 position 14. Wrong tool point 4 position 15. Wrong tool point 5 position 16. Wrong tool point 6 position 17. Wrong tool point 7 position 18. Wrong tool point 8 position Recommended actions - Reduce speed - Move Robot tool to safe position - Adjust tool orientation 20469, SC arg SAR violation Description Safe Axis Range (SAR) arg is violated on Mechanical unit arg Axis arg Recommended actions Move Mechanical unit to safe position 20470, SC arg Synchronization Pre-warning Description Synchronization required for Mechanical units supervised by Safety Controller (SC) arg in less than arg hour(s). Recommended actions Perform synchronization before the time limit expires. 20471, SC arg Synchronization Timeout Description Synchronization time limit expired for Safety Controller (SC) arg . Last synchronization was arg hours ago. Recommended actions Perform synchronization. 20472, SC arg New Safety Configuration Description Safety Controller (SC) arg has received a new Safety Configuration. A new PIN-code is needed to activate. Recommended actions 1. Log in as a user with Safety Configuration grants. 2. Enter new PIN-Code for the Safety Controller in the Control Panel. 20473, SC arg Dual Computer mismatch Description Safety Controller (SC) arg have had conflicting values for a Safety Output for too long. Consequences The Safety Controller has entered a Safe State and issue an error after 10 minutes of internal mismatch, if recommended actions are not performed. Probable causes - The Mechanical unit have been parked at a position on, or close to, a supervised or monitored function limit for too long time. - Internal computation error in Safety Controller. Recommended actions Move all Mechanical units’ axes and tools well inside or outside monitored and supervised function limits. 20474, SC arg I/O Supply Failure Description I/O supply voltage level for Safety Controller (SC) arg is out of range. Probable causes Either the voltage is out of limits or the voltage is missing. Recommended actions 1. Connect 24V supply with correct voltage level to I/O supply terminals. 2. Warm start Robot Controller.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	136	6 Trouble shooting by Event log 133 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 2. Restart System. 20457, SC arg Corrupt Safety Configuration Description The Safety Configuration for Safety Controller (SC) arg is corrupt or contains invalid data. Recommended actions - Warm start Robot Controller. - Download a Safety Configuration to the Safety Controller. - Reinstall System. 20458, SC arg Internal Failure Description Internal Failure in Safety Controller (SC) arg . Recommended actions - Check Safety Controller cabling. - Check Safety Controller health on LED - Replace Safety Controller if remaining error 20459, SC arg Input/Output Failure Description I/O Error on Safety Controller (SC) arg . Recommended actions - Check Safety Controller cabling. - Check Safety Controller health. Warm start Robot Controller, after performing recommended actions. 20460, SC arg Safety Configuration not found Description Failed to retrieve Safety Configuration for Safety Controller (SC) arg . Recommended actions - Warm start Robot Controller. - Download a Safety Configuration to the SC. - Reinstall System. 20461, SC arg Robot Configuration not found Description Failed to retrieve Robot Configuration for Safety Controller (SC) arg . Recommended actions - Warm start Robot Controller. - Reinstall System. 20462, SC arg Calibration Offset not found Description Failed to retrieve Motor Calibration offsets for Safety Controller (SC) arg . Recommended actions Download new Calibration offsets to the SC. 20463, SC arg Safety Configuration downloaded Description Download of Safety Configuration was successful for Safety Controller (SC) arg . 20464, SC arg OSR Limit exceeded Description Safety Controller (SC) arg detected a too big difference between the ordered and actual position inside Operational Safety Range (OSR) , for Mechanical unit arg on axis arg . Recommended actions - Check for collision. - Check that Operational Safety Range (OSR) Tolerance in the Safety Configuration is not set too low. - Synchronize the Safety Controller, if the revolution counters have been updated since last synchronization. 20465, SC arg SAS Speed exceeded Description Safe Axis Speed (SAS) violation on Mechanical unit arg Axis arg on Safety Controller (SC) Recommended actions Decrease speed on Axis arg 20466, SC arg Input/Output Failure Description I/O Error on Safety Controller (SC) arg I/O arg Type arg Type 1: Input Type 2: Output Probable causes - Wrong connection to I/O terminals on SC - Two channel I/O mismatch Recommended actions - Check SC cabling. - Check SC health. Warm start Robot Controller, after performing recommended actions. 6 Trouble shooting by Event log 134 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20467, SC arg STS speed exceeded Description Safe reduced Tool Speed (STS) in Safety Controller (SC) on Mechanical unit arg too high. Cause arg . Probable causes 1. Tool0 speed 2. Elbow speed 3. Tool speed 4. Additional axis speed Recommended actions Reduce tool speed. 20468, SC arg STZ violation Description Safe Tool Zone (STZ) arg is violated on Mechanical unit arg . Cause arg Probable causes 1. Exceeded speed 2. Wrong tool position 3. Wrong tool orientation 4. Wrong elbow position 11. Wrong tool point 1 position 12. Wrong tool point 2 position 13. Wrong tool point 3 position 14. Wrong tool point 4 position 15. Wrong tool point 5 position 16. Wrong tool point 6 position 17. Wrong tool point 7 position 18. Wrong tool point 8 position Recommended actions - Reduce speed - Move Robot tool to safe position - Adjust tool orientation 20469, SC arg SAR violation Description Safe Axis Range (SAR) arg is violated on Mechanical unit arg Axis arg Recommended actions Move Mechanical unit to safe position 20470, SC arg Synchronization Pre-warning Description Synchronization required for Mechanical units supervised by Safety Controller (SC) arg in less than arg hour(s). Recommended actions Perform synchronization before the time limit expires. 20471, SC arg Synchronization Timeout Description Synchronization time limit expired for Safety Controller (SC) arg . Last synchronization was arg hours ago. Recommended actions Perform synchronization. 20472, SC arg New Safety Configuration Description Safety Controller (SC) arg has received a new Safety Configuration. A new PIN-code is needed to activate. Recommended actions 1. Log in as a user with Safety Configuration grants. 2. Enter new PIN-Code for the Safety Controller in the Control Panel. 20473, SC arg Dual Computer mismatch Description Safety Controller (SC) arg have had conflicting values for a Safety Output for too long. Consequences The Safety Controller has entered a Safe State and issue an error after 10 minutes of internal mismatch, if recommended actions are not performed. Probable causes - The Mechanical unit have been parked at a position on, or close to, a supervised or monitored function limit for too long time. - Internal computation error in Safety Controller. Recommended actions Move all Mechanical units’ axes and tools well inside or outside monitored and supervised function limits. 20474, SC arg I/O Supply Failure Description I/O supply voltage level for Safety Controller (SC) arg is out of range. Probable causes Either the voltage is out of limits or the voltage is missing. Recommended actions 1. Connect 24V supply with correct voltage level to I/O supply terminals. 2. Warm start Robot Controller. 6 Trouble shooting by Event log 135 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20475, SC arg Synchronization rejected Description Safety Controller (SC) arg is not correctly configured for synchronization. Probable causes - Safety Configuration PIN is not set or is incorrect. - Safety Configuration is empty. - Safety Configuration is corrupt or missing. - Safety Controller connected to the wrong SMB bus. - I/O Power supply missing. Recommended actions Verify and check possible causes 20476, SC arg Disabled Description Safety Controller (SC) arg is disabled. Consequences All safety supervision has been disabled in the Safety Controller. Risk for Safety hazards. Recommended actions Download a Safety Configuration to the Safety Controller. 20477, SC arg SMB Communication Failure Description Safety Controller (SC) arg failed to communicate with Serial Measurement Board (SMB). Recommended actions 1. Make sure that the cabling from SMB to Safety Controller is connected to the right SMB connector and functional. 2. Restart System. 20478, SC arg Main Supply Failure Description The main power supply voltage for Safety Controller (SC) arg is out of range. Probable causes Either the voltage is out of limit or the voltage is missing. Recommended actions 1. Check Safety Controller cabling. 2. Check voltage from power supply. 3. Warm start Robot Controller. 20479, SC arg Additional Axis missing Description An Additional Axis that is supervised by Safety Controller (SC) arg is no longer present in the System Configuration. Recommended actions Reinstall the supervised Additional Axis, or Download a Safety Configuration without supervision of the Additional Axis. 20480, SC arg SST violation Description Safe Stand Still (SST) arg in Safety Controller (SC) is violated on Mechanical unit arg Axis arg . Recommended actions - Verify Rapid program - Verify process equipment - Check that movement is not ongoing when SST is active - Check previous elog messages 20481, SC arg OVR active Description Override Operation (OVR) active on Safety Controller (SC) arg SafeMove will stop the robot after approximately 20 minutes with OVR active. Speed is limited to 250 mm/s or 18 degrees/s. Recommended actions Deactivate signal connected to OVR input 20482, SC arg OVR time out Description Override Operation (OVR) has been active too long time on Safety Controller (SC) arg . Recommended actions 1. Warmstart Robot Controller 2. Toggle signal connected to OVR input 3. Activate Confirm stop by pressing Motors On push button 4. Jog Robot back into working area 5. Deactivate signal connected to OVR input 20483, SC arg CBC soon required Description Cyclic Brake Check (CBC) required in less than arg hours. Recommended actions Perform a Brake Check before the time limit expires.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	137	6 Trouble shooting by Event log 134 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20467, SC arg STS speed exceeded Description Safe reduced Tool Speed (STS) in Safety Controller (SC) on Mechanical unit arg too high. Cause arg . Probable causes 1. Tool0 speed 2. Elbow speed 3. Tool speed 4. Additional axis speed Recommended actions Reduce tool speed. 20468, SC arg STZ violation Description Safe Tool Zone (STZ) arg is violated on Mechanical unit arg . Cause arg Probable causes 1. Exceeded speed 2. Wrong tool position 3. Wrong tool orientation 4. Wrong elbow position 11. Wrong tool point 1 position 12. Wrong tool point 2 position 13. Wrong tool point 3 position 14. Wrong tool point 4 position 15. Wrong tool point 5 position 16. Wrong tool point 6 position 17. Wrong tool point 7 position 18. Wrong tool point 8 position Recommended actions - Reduce speed - Move Robot tool to safe position - Adjust tool orientation 20469, SC arg SAR violation Description Safe Axis Range (SAR) arg is violated on Mechanical unit arg Axis arg Recommended actions Move Mechanical unit to safe position 20470, SC arg Synchronization Pre-warning Description Synchronization required for Mechanical units supervised by Safety Controller (SC) arg in less than arg hour(s). Recommended actions Perform synchronization before the time limit expires. 20471, SC arg Synchronization Timeout Description Synchronization time limit expired for Safety Controller (SC) arg . Last synchronization was arg hours ago. Recommended actions Perform synchronization. 20472, SC arg New Safety Configuration Description Safety Controller (SC) arg has received a new Safety Configuration. A new PIN-code is needed to activate. Recommended actions 1. Log in as a user with Safety Configuration grants. 2. Enter new PIN-Code for the Safety Controller in the Control Panel. 20473, SC arg Dual Computer mismatch Description Safety Controller (SC) arg have had conflicting values for a Safety Output for too long. Consequences The Safety Controller has entered a Safe State and issue an error after 10 minutes of internal mismatch, if recommended actions are not performed. Probable causes - The Mechanical unit have been parked at a position on, or close to, a supervised or monitored function limit for too long time. - Internal computation error in Safety Controller. Recommended actions Move all Mechanical units’ axes and tools well inside or outside monitored and supervised function limits. 20474, SC arg I/O Supply Failure Description I/O supply voltage level for Safety Controller (SC) arg is out of range. Probable causes Either the voltage is out of limits or the voltage is missing. Recommended actions 1. Connect 24V supply with correct voltage level to I/O supply terminals. 2. Warm start Robot Controller. 6 Trouble shooting by Event log 135 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20475, SC arg Synchronization rejected Description Safety Controller (SC) arg is not correctly configured for synchronization. Probable causes - Safety Configuration PIN is not set or is incorrect. - Safety Configuration is empty. - Safety Configuration is corrupt or missing. - Safety Controller connected to the wrong SMB bus. - I/O Power supply missing. Recommended actions Verify and check possible causes 20476, SC arg Disabled Description Safety Controller (SC) arg is disabled. Consequences All safety supervision has been disabled in the Safety Controller. Risk for Safety hazards. Recommended actions Download a Safety Configuration to the Safety Controller. 20477, SC arg SMB Communication Failure Description Safety Controller (SC) arg failed to communicate with Serial Measurement Board (SMB). Recommended actions 1. Make sure that the cabling from SMB to Safety Controller is connected to the right SMB connector and functional. 2. Restart System. 20478, SC arg Main Supply Failure Description The main power supply voltage for Safety Controller (SC) arg is out of range. Probable causes Either the voltage is out of limit or the voltage is missing. Recommended actions 1. Check Safety Controller cabling. 2. Check voltage from power supply. 3. Warm start Robot Controller. 20479, SC arg Additional Axis missing Description An Additional Axis that is supervised by Safety Controller (SC) arg is no longer present in the System Configuration. Recommended actions Reinstall the supervised Additional Axis, or Download a Safety Configuration without supervision of the Additional Axis. 20480, SC arg SST violation Description Safe Stand Still (SST) arg in Safety Controller (SC) is violated on Mechanical unit arg Axis arg . Recommended actions - Verify Rapid program - Verify process equipment - Check that movement is not ongoing when SST is active - Check previous elog messages 20481, SC arg OVR active Description Override Operation (OVR) active on Safety Controller (SC) arg SafeMove will stop the robot after approximately 20 minutes with OVR active. Speed is limited to 250 mm/s or 18 degrees/s. Recommended actions Deactivate signal connected to OVR input 20482, SC arg OVR time out Description Override Operation (OVR) has been active too long time on Safety Controller (SC) arg . Recommended actions 1. Warmstart Robot Controller 2. Toggle signal connected to OVR input 3. Activate Confirm stop by pressing Motors On push button 4. Jog Robot back into working area 5. Deactivate signal connected to OVR input 20483, SC arg CBC soon required Description Cyclic Brake Check (CBC) required in less than arg hours. Recommended actions Perform a Brake Check before the time limit expires. 6 Trouble shooting by Event log 136 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20484, SC arg CBC Time Limit expired Description Cyclic Brake Check (CBC) time limit expired in Safety Controller (SC). Last Brake Check was executed arg hours ago. Recommended actions Perform a Brake Check. 20485, SC arg Too low brake torque Description Too low brake torque in Safety Controller (SC) on Mechanical unit arg . Probable causes - Axis has not been tested. - Worn out brake(s). Recommended actions - Check that the failing axis is activated - If failing axis is activated replace brake(s)as soon as possible. 20486, SC arg CBC incorrect Description Safety Controller (SC) has detected that the last Cyclic Brake Check (CBC) on Mechanical unit arg was incorrect. Recommended actions - Perform a new Brake Check. - Check previous elogs. 20487, SC arg Unsynchronized speed exceeded Description Exceeded Axis speed when Safety Controller (SC) arg was unsynchronized. Recommended actions Jog Mechanical unit to synch position with low axis speed. Reduce speed to 250 mm/s or 18 degrees/s. 20488, SC arg Unsynchronized time limit expired Description Available time to move the Robot when unsynchronized has expired for Safety Controller (SC) arg . Recommended actions 1. Do a Confirm stop by pressing the Motors ON push button or activate System input 2. Synchronize SC arg . 20489, SC arg has been disabled Description Safety Controller (SC) arg has been disabled and no supervision functions are active. Probable causes Either a C-start has been performed or it's the first startup of SC. Recommended actions Download a Configuration to SC arg . 20490, SC arg OVR Speed exceeded Description Override (OVR) Speed limit exceeded on Mechanical unit arg . Probable causes If Override (OVR) is active, then OVR speed limitations will be active Recommended actions - Decrease speed. - Deactivate OVR. 20491, SC arg Override active during startup Description Override digital input was active during startup on SC arg 20492, SC arg SST violation in Brake test Description Movement detected during Brake test on Safety Controller (SC) arg Mechanical unit arg Axis arg Probable causes - Interrupted braketest. - Worn out Brakes. Recommended actions - Restart CBC. - Replace Brake. 20493, SC arg SBR triggered Description Safe Brake Ramp (SBR) on Safety Controller (SC) was interrupted by a Class 0 stop due to slow deceleration on Mechanical unit arg . This is normal and occurs in cases when a stop1 is to slow. Check for other safety controller elog. Recommended actions - Change parameter value for SBR in motion configuration - Trigger a new stop to test the Brake Ramp. - If this happens frequently, check the Application manual for Mechanical units configuration.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	138	6 Trouble shooting by Event log 135 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20475, SC arg Synchronization rejected Description Safety Controller (SC) arg is not correctly configured for synchronization. Probable causes - Safety Configuration PIN is not set or is incorrect. - Safety Configuration is empty. - Safety Configuration is corrupt or missing. - Safety Controller connected to the wrong SMB bus. - I/O Power supply missing. Recommended actions Verify and check possible causes 20476, SC arg Disabled Description Safety Controller (SC) arg is disabled. Consequences All safety supervision has been disabled in the Safety Controller. Risk for Safety hazards. Recommended actions Download a Safety Configuration to the Safety Controller. 20477, SC arg SMB Communication Failure Description Safety Controller (SC) arg failed to communicate with Serial Measurement Board (SMB). Recommended actions 1. Make sure that the cabling from SMB to Safety Controller is connected to the right SMB connector and functional. 2. Restart System. 20478, SC arg Main Supply Failure Description The main power supply voltage for Safety Controller (SC) arg is out of range. Probable causes Either the voltage is out of limit or the voltage is missing. Recommended actions 1. Check Safety Controller cabling. 2. Check voltage from power supply. 3. Warm start Robot Controller. 20479, SC arg Additional Axis missing Description An Additional Axis that is supervised by Safety Controller (SC) arg is no longer present in the System Configuration. Recommended actions Reinstall the supervised Additional Axis, or Download a Safety Configuration without supervision of the Additional Axis. 20480, SC arg SST violation Description Safe Stand Still (SST) arg in Safety Controller (SC) is violated on Mechanical unit arg Axis arg . Recommended actions - Verify Rapid program - Verify process equipment - Check that movement is not ongoing when SST is active - Check previous elog messages 20481, SC arg OVR active Description Override Operation (OVR) active on Safety Controller (SC) arg SafeMove will stop the robot after approximately 20 minutes with OVR active. Speed is limited to 250 mm/s or 18 degrees/s. Recommended actions Deactivate signal connected to OVR input 20482, SC arg OVR time out Description Override Operation (OVR) has been active too long time on Safety Controller (SC) arg . Recommended actions 1. Warmstart Robot Controller 2. Toggle signal connected to OVR input 3. Activate Confirm stop by pressing Motors On push button 4. Jog Robot back into working area 5. Deactivate signal connected to OVR input 20483, SC arg CBC soon required Description Cyclic Brake Check (CBC) required in less than arg hours. Recommended actions Perform a Brake Check before the time limit expires. 6 Trouble shooting by Event log 136 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20484, SC arg CBC Time Limit expired Description Cyclic Brake Check (CBC) time limit expired in Safety Controller (SC). Last Brake Check was executed arg hours ago. Recommended actions Perform a Brake Check. 20485, SC arg Too low brake torque Description Too low brake torque in Safety Controller (SC) on Mechanical unit arg . Probable causes - Axis has not been tested. - Worn out brake(s). Recommended actions - Check that the failing axis is activated - If failing axis is activated replace brake(s)as soon as possible. 20486, SC arg CBC incorrect Description Safety Controller (SC) has detected that the last Cyclic Brake Check (CBC) on Mechanical unit arg was incorrect. Recommended actions - Perform a new Brake Check. - Check previous elogs. 20487, SC arg Unsynchronized speed exceeded Description Exceeded Axis speed when Safety Controller (SC) arg was unsynchronized. Recommended actions Jog Mechanical unit to synch position with low axis speed. Reduce speed to 250 mm/s or 18 degrees/s. 20488, SC arg Unsynchronized time limit expired Description Available time to move the Robot when unsynchronized has expired for Safety Controller (SC) arg . Recommended actions 1. Do a Confirm stop by pressing the Motors ON push button or activate System input 2. Synchronize SC arg . 20489, SC arg has been disabled Description Safety Controller (SC) arg has been disabled and no supervision functions are active. Probable causes Either a C-start has been performed or it's the first startup of SC. Recommended actions Download a Configuration to SC arg . 20490, SC arg OVR Speed exceeded Description Override (OVR) Speed limit exceeded on Mechanical unit arg . Probable causes If Override (OVR) is active, then OVR speed limitations will be active Recommended actions - Decrease speed. - Deactivate OVR. 20491, SC arg Override active during startup Description Override digital input was active during startup on SC arg 20492, SC arg SST violation in Brake test Description Movement detected during Brake test on Safety Controller (SC) arg Mechanical unit arg Axis arg Probable causes - Interrupted braketest. - Worn out Brakes. Recommended actions - Restart CBC. - Replace Brake. 20493, SC arg SBR triggered Description Safe Brake Ramp (SBR) on Safety Controller (SC) was interrupted by a Class 0 stop due to slow deceleration on Mechanical unit arg . This is normal and occurs in cases when a stop1 is to slow. Check for other safety controller elog. Recommended actions - Change parameter value for SBR in motion configuration - Trigger a new stop to test the Brake Ramp. - If this happens frequently, check the Application manual for Mechanical units configuration. 6 Trouble shooting by Event log 137 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20494, SC arg Tool change incorrect Description Incorrect tool change with Tool arg on Mechanical unit arg Recommended actions - Check if correct tool. - Decrease speed if needed. - Perform a new tool change. 20501, ES panel open Description The emergency stop panel has previously been broken, and while broken, an attempt was made to operate the robot. Consequences The system remains in the Emergency Stop status. Probable causes An attempt has been made to manoeuvre a control, e.g. the enabling device. Recommended actions 1) To resume operation, first reset the emergency stop panel button. 2) Then switch the system back to state Motors ON by pressing the Motors ON button on the Control Module. 20502, ES pendant open Description The emergency stop pendant has previously been broken, and while broken, an attempt was made to operate the robot. Consequences The system remains in the Emergency Stop status. Probable causes An attempt has been made to manoeuvre a control, e.g. the enabling device. Recommended actions 1) To resume operation, first reset the emergency stop pendant button. 2) Then switch the system back to state Motors ON by pressing the Motors ON button on the Control Module. 20503, ES ext.cat.0 open Description The emergency stop external has previously been broken, and while broken, an attempt was made to operate the robot. Consequences The system remains in the Emergency Stop status. Probable causes An attempt has been made to manoeuvre a control, e.g. the enabling device. Recommended actions 1) To resume operation, first reset the emergency stop external button. 2) Then switch the system back to state Motors ON by pressing the Motors ON button on the Control Module. 20505, Delayed stop open Description Delayed stop open. Consequences The system goes to status SYS HALT. Recommended actions 1) To resume operation, first reset the delayed stop button. 2) Then switch the system back to state Motors ON by pressing the Motors ON button on the Control Module. 20506, Test Stop open Description The Test Mode Safeguarded Stop circuit has been broken. Consequences The system goes to status SYS HALT. Probable causes One or more of the switch connected in series with the Test Mode Safeguarded Stop circuit have been opened, which may be causes by a large number of faults. This is only possible while in the Manual operational mode Recommended actions 1) Locate the switch, reset it and restart the system. 2) Check cables and connections. 20507, Hardware chain open Description Relays (KA16 and KA17) on Safety Interface Board (SIB) not activated. Consequences Motor on command rejected. Recommended actions Press motor ON button to close the chain. 20521, Test Stop conflict Description Status conflict for the Test Stop chain. Consequences The system goes to status SYS HALT.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	139	6 Trouble shooting by Event log 136 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20484, SC arg CBC Time Limit expired Description Cyclic Brake Check (CBC) time limit expired in Safety Controller (SC). Last Brake Check was executed arg hours ago. Recommended actions Perform a Brake Check. 20485, SC arg Too low brake torque Description Too low brake torque in Safety Controller (SC) on Mechanical unit arg . Probable causes - Axis has not been tested. - Worn out brake(s). Recommended actions - Check that the failing axis is activated - If failing axis is activated replace brake(s)as soon as possible. 20486, SC arg CBC incorrect Description Safety Controller (SC) has detected that the last Cyclic Brake Check (CBC) on Mechanical unit arg was incorrect. Recommended actions - Perform a new Brake Check. - Check previous elogs. 20487, SC arg Unsynchronized speed exceeded Description Exceeded Axis speed when Safety Controller (SC) arg was unsynchronized. Recommended actions Jog Mechanical unit to synch position with low axis speed. Reduce speed to 250 mm/s or 18 degrees/s. 20488, SC arg Unsynchronized time limit expired Description Available time to move the Robot when unsynchronized has expired for Safety Controller (SC) arg . Recommended actions 1. Do a Confirm stop by pressing the Motors ON push button or activate System input 2. Synchronize SC arg . 20489, SC arg has been disabled Description Safety Controller (SC) arg has been disabled and no supervision functions are active. Probable causes Either a C-start has been performed or it's the first startup of SC. Recommended actions Download a Configuration to SC arg . 20490, SC arg OVR Speed exceeded Description Override (OVR) Speed limit exceeded on Mechanical unit arg . Probable causes If Override (OVR) is active, then OVR speed limitations will be active Recommended actions - Decrease speed. - Deactivate OVR. 20491, SC arg Override active during startup Description Override digital input was active during startup on SC arg 20492, SC arg SST violation in Brake test Description Movement detected during Brake test on Safety Controller (SC) arg Mechanical unit arg Axis arg Probable causes - Interrupted braketest. - Worn out Brakes. Recommended actions - Restart CBC. - Replace Brake. 20493, SC arg SBR triggered Description Safe Brake Ramp (SBR) on Safety Controller (SC) was interrupted by a Class 0 stop due to slow deceleration on Mechanical unit arg . This is normal and occurs in cases when a stop1 is to slow. Check for other safety controller elog. Recommended actions - Change parameter value for SBR in motion configuration - Trigger a new stop to test the Brake Ramp. - If this happens frequently, check the Application manual for Mechanical units configuration. 6 Trouble shooting by Event log 137 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20494, SC arg Tool change incorrect Description Incorrect tool change with Tool arg on Mechanical unit arg Recommended actions - Check if correct tool. - Decrease speed if needed. - Perform a new tool change. 20501, ES panel open Description The emergency stop panel has previously been broken, and while broken, an attempt was made to operate the robot. Consequences The system remains in the Emergency Stop status. Probable causes An attempt has been made to manoeuvre a control, e.g. the enabling device. Recommended actions 1) To resume operation, first reset the emergency stop panel button. 2) Then switch the system back to state Motors ON by pressing the Motors ON button on the Control Module. 20502, ES pendant open Description The emergency stop pendant has previously been broken, and while broken, an attempt was made to operate the robot. Consequences The system remains in the Emergency Stop status. Probable causes An attempt has been made to manoeuvre a control, e.g. the enabling device. Recommended actions 1) To resume operation, first reset the emergency stop pendant button. 2) Then switch the system back to state Motors ON by pressing the Motors ON button on the Control Module. 20503, ES ext.cat.0 open Description The emergency stop external has previously been broken, and while broken, an attempt was made to operate the robot. Consequences The system remains in the Emergency Stop status. Probable causes An attempt has been made to manoeuvre a control, e.g. the enabling device. Recommended actions 1) To resume operation, first reset the emergency stop external button. 2) Then switch the system back to state Motors ON by pressing the Motors ON button on the Control Module. 20505, Delayed stop open Description Delayed stop open. Consequences The system goes to status SYS HALT. Recommended actions 1) To resume operation, first reset the delayed stop button. 2) Then switch the system back to state Motors ON by pressing the Motors ON button on the Control Module. 20506, Test Stop open Description The Test Mode Safeguarded Stop circuit has been broken. Consequences The system goes to status SYS HALT. Probable causes One or more of the switch connected in series with the Test Mode Safeguarded Stop circuit have been opened, which may be causes by a large number of faults. This is only possible while in the Manual operational mode Recommended actions 1) Locate the switch, reset it and restart the system. 2) Check cables and connections. 20507, Hardware chain open Description Relays (KA16 and KA17) on Safety Interface Board (SIB) not activated. Consequences Motor on command rejected. Recommended actions Press motor ON button to close the chain. 20521, Test Stop conflict Description Status conflict for the Test Stop chain. Consequences The system goes to status SYS HALT. 6 Trouble shooting by Event log 138 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Please check the two-channel safety guard that caused the status conflict. 20525, ES panel conflict Description Status conflict for the Emergency Stop panel chain. Consequences The system goes to status emergency stop. Recommended actions Please check the two-channel safety guard that caused the status conflict. 20526, ES pendant conflict Description Status conflict for the Emergency Stop pendant chain. Consequences The system goes to status emergency stop. Recommended actions Please check the two-channel safety guard that caused the status conflict. 20527, ES ext.cat.0 conflict Description Status conflict for the Emergency Stop ext.cat.0 chain. Consequences The system goes to status emergency stop. Recommended actions Please check the two-channel safety guard that caused the status conflict. 20528, HV Interlock input conflict Description Only one of the two input signals in the high voltage chains is opened. Consequences Paint enable chain opens. Recommended actions Please check the two-channel safety guard that caused the status conflict. 20529, Cabin Interlock input conflict Description Only one of the two input signals in cabin interlock chains is opened. Consequences Paint enable chain opens. Recommended actions Check cables and connections. 20531, Delayed Stop conflict Description Status conflict for the delayed stop circuit. Consequences The system goes to status SYS HALT. Recommended actions Check cables and connections. 20534, Mode selector conflict Description Any of the connections to the mode selector are faulty. Consequences The system goes to status SYS HALT. Recommended actions Check cables and connections. 20535, AUX Interlock conflict Description Only one of the two AUX interlock chains was opened. Normally used on CBS door interlock. Consequences Paint enable chain opens. Recommended actions Check cables and connections. 20536, Motor on chain conflict Description Only one of the two motor on chain signals in run chain is opened. Consequences The system goes to status SYS HALT. Recommended actions Check cables and connections. 20556, Enable 2 AXC 1 open Description Status active when enable from Axis Computer 1 open. Consequences The system goes to status SYS HALT.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	140	6 Trouble shooting by Event log 137 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20494, SC arg Tool change incorrect Description Incorrect tool change with Tool arg on Mechanical unit arg Recommended actions - Check if correct tool. - Decrease speed if needed. - Perform a new tool change. 20501, ES panel open Description The emergency stop panel has previously been broken, and while broken, an attempt was made to operate the robot. Consequences The system remains in the Emergency Stop status. Probable causes An attempt has been made to manoeuvre a control, e.g. the enabling device. Recommended actions 1) To resume operation, first reset the emergency stop panel button. 2) Then switch the system back to state Motors ON by pressing the Motors ON button on the Control Module. 20502, ES pendant open Description The emergency stop pendant has previously been broken, and while broken, an attempt was made to operate the robot. Consequences The system remains in the Emergency Stop status. Probable causes An attempt has been made to manoeuvre a control, e.g. the enabling device. Recommended actions 1) To resume operation, first reset the emergency stop pendant button. 2) Then switch the system back to state Motors ON by pressing the Motors ON button on the Control Module. 20503, ES ext.cat.0 open Description The emergency stop external has previously been broken, and while broken, an attempt was made to operate the robot. Consequences The system remains in the Emergency Stop status. Probable causes An attempt has been made to manoeuvre a control, e.g. the enabling device. Recommended actions 1) To resume operation, first reset the emergency stop external button. 2) Then switch the system back to state Motors ON by pressing the Motors ON button on the Control Module. 20505, Delayed stop open Description Delayed stop open. Consequences The system goes to status SYS HALT. Recommended actions 1) To resume operation, first reset the delayed stop button. 2) Then switch the system back to state Motors ON by pressing the Motors ON button on the Control Module. 20506, Test Stop open Description The Test Mode Safeguarded Stop circuit has been broken. Consequences The system goes to status SYS HALT. Probable causes One or more of the switch connected in series with the Test Mode Safeguarded Stop circuit have been opened, which may be causes by a large number of faults. This is only possible while in the Manual operational mode Recommended actions 1) Locate the switch, reset it and restart the system. 2) Check cables and connections. 20507, Hardware chain open Description Relays (KA16 and KA17) on Safety Interface Board (SIB) not activated. Consequences Motor on command rejected. Recommended actions Press motor ON button to close the chain. 20521, Test Stop conflict Description Status conflict for the Test Stop chain. Consequences The system goes to status SYS HALT. 6 Trouble shooting by Event log 138 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Please check the two-channel safety guard that caused the status conflict. 20525, ES panel conflict Description Status conflict for the Emergency Stop panel chain. Consequences The system goes to status emergency stop. Recommended actions Please check the two-channel safety guard that caused the status conflict. 20526, ES pendant conflict Description Status conflict for the Emergency Stop pendant chain. Consequences The system goes to status emergency stop. Recommended actions Please check the two-channel safety guard that caused the status conflict. 20527, ES ext.cat.0 conflict Description Status conflict for the Emergency Stop ext.cat.0 chain. Consequences The system goes to status emergency stop. Recommended actions Please check the two-channel safety guard that caused the status conflict. 20528, HV Interlock input conflict Description Only one of the two input signals in the high voltage chains is opened. Consequences Paint enable chain opens. Recommended actions Please check the two-channel safety guard that caused the status conflict. 20529, Cabin Interlock input conflict Description Only one of the two input signals in cabin interlock chains is opened. Consequences Paint enable chain opens. Recommended actions Check cables and connections. 20531, Delayed Stop conflict Description Status conflict for the delayed stop circuit. Consequences The system goes to status SYS HALT. Recommended actions Check cables and connections. 20534, Mode selector conflict Description Any of the connections to the mode selector are faulty. Consequences The system goes to status SYS HALT. Recommended actions Check cables and connections. 20535, AUX Interlock conflict Description Only one of the two AUX interlock chains was opened. Normally used on CBS door interlock. Consequences Paint enable chain opens. Recommended actions Check cables and connections. 20536, Motor on chain conflict Description Only one of the two motor on chain signals in run chain is opened. Consequences The system goes to status SYS HALT. Recommended actions Check cables and connections. 20556, Enable 2 AXC 1 open Description Status active when enable from Axis Computer 1 open. Consequences The system goes to status SYS HALT. 6 Trouble shooting by Event log 139 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1. Check other error messages for primary fault reason. 2. If no other error messages, please check line voltage for one phase missing. 20557, Enable 2 AXC 2 open Description Status active when enable from Axis Computer 2 open. Consequences The system goes to status SYS HALT. Recommended actions 1. Check other error messages for primary fault reason. 2. If no other error messages, please check line voltage for one phase missing. 20558, Manipulator fault Description Status active when power to manipulator arg connected to Manipulator Interface Board (MIB) arg is lost, or manipulator's enable chain conditions is not OK. Consequences The system goes to status SYS HALT. Recommended actions 1. Check the power to the manipulator. 2. Check that the enable chain on Manipulator Controller Board (MCOB) is OK. 20559, Collision sensor active Description Status active when digital collision sensor on Manipulator Controller Board (MCOB) is active. Consequences The system goes to status SYS HALT. Recommended actions Check the collision sensors connected to MCOB. 20560, Axis limit on MCOB Description Status active when limit sensor on Manipulator Controller Board (MCOB) is active. Consequences The system goes to status SYS HALT. Recommended actions Check the limit sensors connected to MCOB. 20561, MCOB software has opened enable chain Description Status active when Manipulator Controller Board (MCOB) software has opened the enable chain on MCOB. Consequences The system goes to status SYS HALT. Recommended actions Check the MCOB software. 20562, Reset ES fault Description Status active when Reset Emergency Stop input is activated for more than 3 seconds. Consequences The system goes to status SYS HALT. Recommended actions 1. Check the connection of external reset of Emergency Stop. 2. Check the motor on push button. 20563, Servo disconnect open Description Status active when Servo disconnect switch on system arg is off. Consequences The system goes to status SYS HALT. Recommended actions If Servo disconnect switch is not installed, check the disable link on Manipulator Interface Board (MIB). 20564, Brake rel. on axes 1 & 7 Description Status active when manual brake release on axes 1 and 7 enabled. Consequences The system goes to status SYS HALT. Recommended actions Check switch for manual brake release of axes 1 and 7. 20565, External enable 1 open Description Status active when external enable 1 on Manipulator Controller Board (MCOB) is open. Consequences The system goes to status SYS HALT.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	141	6 Trouble shooting by Event log 138 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Please check the two-channel safety guard that caused the status conflict. 20525, ES panel conflict Description Status conflict for the Emergency Stop panel chain. Consequences The system goes to status emergency stop. Recommended actions Please check the two-channel safety guard that caused the status conflict. 20526, ES pendant conflict Description Status conflict for the Emergency Stop pendant chain. Consequences The system goes to status emergency stop. Recommended actions Please check the two-channel safety guard that caused the status conflict. 20527, ES ext.cat.0 conflict Description Status conflict for the Emergency Stop ext.cat.0 chain. Consequences The system goes to status emergency stop. Recommended actions Please check the two-channel safety guard that caused the status conflict. 20528, HV Interlock input conflict Description Only one of the two input signals in the high voltage chains is opened. Consequences Paint enable chain opens. Recommended actions Please check the two-channel safety guard that caused the status conflict. 20529, Cabin Interlock input conflict Description Only one of the two input signals in cabin interlock chains is opened. Consequences Paint enable chain opens. Recommended actions Check cables and connections. 20531, Delayed Stop conflict Description Status conflict for the delayed stop circuit. Consequences The system goes to status SYS HALT. Recommended actions Check cables and connections. 20534, Mode selector conflict Description Any of the connections to the mode selector are faulty. Consequences The system goes to status SYS HALT. Recommended actions Check cables and connections. 20535, AUX Interlock conflict Description Only one of the two AUX interlock chains was opened. Normally used on CBS door interlock. Consequences Paint enable chain opens. Recommended actions Check cables and connections. 20536, Motor on chain conflict Description Only one of the two motor on chain signals in run chain is opened. Consequences The system goes to status SYS HALT. Recommended actions Check cables and connections. 20556, Enable 2 AXC 1 open Description Status active when enable from Axis Computer 1 open. Consequences The system goes to status SYS HALT. 6 Trouble shooting by Event log 139 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1. Check other error messages for primary fault reason. 2. If no other error messages, please check line voltage for one phase missing. 20557, Enable 2 AXC 2 open Description Status active when enable from Axis Computer 2 open. Consequences The system goes to status SYS HALT. Recommended actions 1. Check other error messages for primary fault reason. 2. If no other error messages, please check line voltage for one phase missing. 20558, Manipulator fault Description Status active when power to manipulator arg connected to Manipulator Interface Board (MIB) arg is lost, or manipulator's enable chain conditions is not OK. Consequences The system goes to status SYS HALT. Recommended actions 1. Check the power to the manipulator. 2. Check that the enable chain on Manipulator Controller Board (MCOB) is OK. 20559, Collision sensor active Description Status active when digital collision sensor on Manipulator Controller Board (MCOB) is active. Consequences The system goes to status SYS HALT. Recommended actions Check the collision sensors connected to MCOB. 20560, Axis limit on MCOB Description Status active when limit sensor on Manipulator Controller Board (MCOB) is active. Consequences The system goes to status SYS HALT. Recommended actions Check the limit sensors connected to MCOB. 20561, MCOB software has opened enable chain Description Status active when Manipulator Controller Board (MCOB) software has opened the enable chain on MCOB. Consequences The system goes to status SYS HALT. Recommended actions Check the MCOB software. 20562, Reset ES fault Description Status active when Reset Emergency Stop input is activated for more than 3 seconds. Consequences The system goes to status SYS HALT. Recommended actions 1. Check the connection of external reset of Emergency Stop. 2. Check the motor on push button. 20563, Servo disconnect open Description Status active when Servo disconnect switch on system arg is off. Consequences The system goes to status SYS HALT. Recommended actions If Servo disconnect switch is not installed, check the disable link on Manipulator Interface Board (MIB). 20564, Brake rel. on axes 1 & 7 Description Status active when manual brake release on axes 1 and 7 enabled. Consequences The system goes to status SYS HALT. Recommended actions Check switch for manual brake release of axes 1 and 7. 20565, External enable 1 open Description Status active when external enable 1 on Manipulator Controller Board (MCOB) is open. Consequences The system goes to status SYS HALT. 6 Trouble shooting by Event log 140 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Check connection on MCCB X25. 20566, External enable 2 open Description Status active when external enable 2 on Manipulator Controller Board (MCOB) is open. Consequences The system goes to status SYS HALT. Recommended actions Check connection on MCCB X43. 20567, Power low on MCOB Description Status active when power below 16V on Manipulator Controller Board (MCOB). Consequences The system goes to status SYS HALT. Recommended actions Check power on MCOB. 20568, Hardware enable open on MCOB Description Status active when firmware on Manipulator Controller Board (MCOB) has opened the enable chain. Consequences The system goes to status SYS HALT. 20569, Watchdog fault on MCOB Description Status active when watchdog on Manipulator Controller Board (MCOB) fails. Consequences The system goes to status SYS HALT. 20570, TPU wiring error Description Status active when Process Interface Board (PIB) detects fault on emergency stop pendant and enabling device signals (glitch test). Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections to Teach Pendant Unit (TPU). 2. Check Pendant Interface Board (TIB) and Manipulator Interface Board (MIB). 20571, HV Interlock open Description Paint system High Voltage (HV) interlock is opened by external interlock connection. Consequences Paint enable chain opens. Recommended actions Check manual switch for disconnecting of the HV system. 20572, Cabin Interlock open Description Cabin Interlock is opened by external interlock connection. Consequences Paint enable chain opens. Recommended actions Check cabin ventilation and other cabin safety functions. 20573, Controller ID is Missing Description Controller ID is the controller's unique identity. It is by default equal to the serial number of the controller's cabinet. The software configuration of the controller is missing this identity information. Probable causes This may happen if the storage media of the controller has been replaced or reformatted. Recommended actions Read the serial number of the controller from the controller cabinet to find out what the controller ID should be. Use RobotStudio tools to set this value for the controller. 20574, Process Interlock open Description Process Interlock is opened by external interlock connection. Consequences Paint enable chain opens. Recommended actions Check manual switch for disconnecting of the process system. 20575, AUX Interlock open Description AUX Interlock is opened by external interlock connection. Normally used for Cartridge Bell System (CBS).
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	142	6 Trouble shooting by Event log 139 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1. Check other error messages for primary fault reason. 2. If no other error messages, please check line voltage for one phase missing. 20557, Enable 2 AXC 2 open Description Status active when enable from Axis Computer 2 open. Consequences The system goes to status SYS HALT. Recommended actions 1. Check other error messages for primary fault reason. 2. If no other error messages, please check line voltage for one phase missing. 20558, Manipulator fault Description Status active when power to manipulator arg connected to Manipulator Interface Board (MIB) arg is lost, or manipulator's enable chain conditions is not OK. Consequences The system goes to status SYS HALT. Recommended actions 1. Check the power to the manipulator. 2. Check that the enable chain on Manipulator Controller Board (MCOB) is OK. 20559, Collision sensor active Description Status active when digital collision sensor on Manipulator Controller Board (MCOB) is active. Consequences The system goes to status SYS HALT. Recommended actions Check the collision sensors connected to MCOB. 20560, Axis limit on MCOB Description Status active when limit sensor on Manipulator Controller Board (MCOB) is active. Consequences The system goes to status SYS HALT. Recommended actions Check the limit sensors connected to MCOB. 20561, MCOB software has opened enable chain Description Status active when Manipulator Controller Board (MCOB) software has opened the enable chain on MCOB. Consequences The system goes to status SYS HALT. Recommended actions Check the MCOB software. 20562, Reset ES fault Description Status active when Reset Emergency Stop input is activated for more than 3 seconds. Consequences The system goes to status SYS HALT. Recommended actions 1. Check the connection of external reset of Emergency Stop. 2. Check the motor on push button. 20563, Servo disconnect open Description Status active when Servo disconnect switch on system arg is off. Consequences The system goes to status SYS HALT. Recommended actions If Servo disconnect switch is not installed, check the disable link on Manipulator Interface Board (MIB). 20564, Brake rel. on axes 1 & 7 Description Status active when manual brake release on axes 1 and 7 enabled. Consequences The system goes to status SYS HALT. Recommended actions Check switch for manual brake release of axes 1 and 7. 20565, External enable 1 open Description Status active when external enable 1 on Manipulator Controller Board (MCOB) is open. Consequences The system goes to status SYS HALT. 6 Trouble shooting by Event log 140 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Check connection on MCCB X25. 20566, External enable 2 open Description Status active when external enable 2 on Manipulator Controller Board (MCOB) is open. Consequences The system goes to status SYS HALT. Recommended actions Check connection on MCCB X43. 20567, Power low on MCOB Description Status active when power below 16V on Manipulator Controller Board (MCOB). Consequences The system goes to status SYS HALT. Recommended actions Check power on MCOB. 20568, Hardware enable open on MCOB Description Status active when firmware on Manipulator Controller Board (MCOB) has opened the enable chain. Consequences The system goes to status SYS HALT. 20569, Watchdog fault on MCOB Description Status active when watchdog on Manipulator Controller Board (MCOB) fails. Consequences The system goes to status SYS HALT. 20570, TPU wiring error Description Status active when Process Interface Board (PIB) detects fault on emergency stop pendant and enabling device signals (glitch test). Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections to Teach Pendant Unit (TPU). 2. Check Pendant Interface Board (TIB) and Manipulator Interface Board (MIB). 20571, HV Interlock open Description Paint system High Voltage (HV) interlock is opened by external interlock connection. Consequences Paint enable chain opens. Recommended actions Check manual switch for disconnecting of the HV system. 20572, Cabin Interlock open Description Cabin Interlock is opened by external interlock connection. Consequences Paint enable chain opens. Recommended actions Check cabin ventilation and other cabin safety functions. 20573, Controller ID is Missing Description Controller ID is the controller's unique identity. It is by default equal to the serial number of the controller's cabinet. The software configuration of the controller is missing this identity information. Probable causes This may happen if the storage media of the controller has been replaced or reformatted. Recommended actions Read the serial number of the controller from the controller cabinet to find out what the controller ID should be. Use RobotStudio tools to set this value for the controller. 20574, Process Interlock open Description Process Interlock is opened by external interlock connection. Consequences Paint enable chain opens. Recommended actions Check manual switch for disconnecting of the process system. 20575, AUX Interlock open Description AUX Interlock is opened by external interlock connection. Normally used for Cartridge Bell System (CBS). 6 Trouble shooting by Event log 141 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences Paint enable chain opens. Recommended actions Check cables and equipments connected to AUX inputs. 20576, System 2 Interlock open Description System 2 Interlock is opened. Normally used for Cartridge Bell System (CBS) or paint pumps Consequences Paint enable chain opens. Recommended actions Check cables and equipments connected to system 2. 20577, HV ON open Description High Voltage (HV) switch on operating panel is opened. Consequences Paint enable chain opens. Recommended actions Give acknowledge on motor ON and switch on the HV key to close the HV interlock chain. 20581, SPI communication towards SIB is down Description Status active when cyclic enable 1 test fails from Safety Interface Board (SIB). Consequences The system goes to status SYS HALT. Recommended actions 1. Check status on Serial Peripheral Interface (SPI) status. 2. Check cables between Process Interface Board (PIB) abd SIB. 20582, SPI communication towards MIB is down Description Status active when cyclic enable 1 test fails from Manipulator Interface Board (MIB) arg . Consequences The system goes to status SYS HALT. Recommended actions Check cables and Serial Peripheral Interface (SPI) status. 2. Check cables between SIB and Manipulator Interface Board (MIB). 20583, Watchdog towards PIB software fails Description Status active when firmware on Process Interface Board (PIB) discover watchdog fault between PIB firmware and PIB software. Consequences The system goes to status SYS HALT. Probable causes Too high processor load on PIB software. 20584, Fault on internal SPI Description Status active when firmware on Process Interface Board (PIB) discover watchdog fault towards Safety Interface Board (SIB) and Manipulator Interface Board (MIB). Consequences The system goes to status SYS HALT. Probable causes Serial Peripheral Interface (SPI) communication is down on SPI 1. Recommended actions Check cables between PIB, SIB and MIB. 20585, Enable chain opened from IPS Description Status active when enable chain is opened from signal Safety/PibSw/ Enable. Consequences The system goes to status SYS HALT. Recommended actions Check the actuator connected to signal Safety/PibSw/Enable. 20586, Watchdog fault towards PIB firmware Description Status active when software on Process Interface Board (PIB) discover watchdog fault towards PIB firmware caused by fault on FPGA. Consequences The system goes to status SYS HALT. 20587, Watchdog fault towards PIB firmware Description Status active when software on Process Interface Board (PIB) discover watchdog fault towards PIB firmware caused by fault on the In-System Micro Controller. Consequences The system goes to status SYS HALT.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	143	6 Trouble shooting by Event log 140 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Check connection on MCCB X25. 20566, External enable 2 open Description Status active when external enable 2 on Manipulator Controller Board (MCOB) is open. Consequences The system goes to status SYS HALT. Recommended actions Check connection on MCCB X43. 20567, Power low on MCOB Description Status active when power below 16V on Manipulator Controller Board (MCOB). Consequences The system goes to status SYS HALT. Recommended actions Check power on MCOB. 20568, Hardware enable open on MCOB Description Status active when firmware on Manipulator Controller Board (MCOB) has opened the enable chain. Consequences The system goes to status SYS HALT. 20569, Watchdog fault on MCOB Description Status active when watchdog on Manipulator Controller Board (MCOB) fails. Consequences The system goes to status SYS HALT. 20570, TPU wiring error Description Status active when Process Interface Board (PIB) detects fault on emergency stop pendant and enabling device signals (glitch test). Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections to Teach Pendant Unit (TPU). 2. Check Pendant Interface Board (TIB) and Manipulator Interface Board (MIB). 20571, HV Interlock open Description Paint system High Voltage (HV) interlock is opened by external interlock connection. Consequences Paint enable chain opens. Recommended actions Check manual switch for disconnecting of the HV system. 20572, Cabin Interlock open Description Cabin Interlock is opened by external interlock connection. Consequences Paint enable chain opens. Recommended actions Check cabin ventilation and other cabin safety functions. 20573, Controller ID is Missing Description Controller ID is the controller's unique identity. It is by default equal to the serial number of the controller's cabinet. The software configuration of the controller is missing this identity information. Probable causes This may happen if the storage media of the controller has been replaced or reformatted. Recommended actions Read the serial number of the controller from the controller cabinet to find out what the controller ID should be. Use RobotStudio tools to set this value for the controller. 20574, Process Interlock open Description Process Interlock is opened by external interlock connection. Consequences Paint enable chain opens. Recommended actions Check manual switch for disconnecting of the process system. 20575, AUX Interlock open Description AUX Interlock is opened by external interlock connection. Normally used for Cartridge Bell System (CBS). 6 Trouble shooting by Event log 141 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences Paint enable chain opens. Recommended actions Check cables and equipments connected to AUX inputs. 20576, System 2 Interlock open Description System 2 Interlock is opened. Normally used for Cartridge Bell System (CBS) or paint pumps Consequences Paint enable chain opens. Recommended actions Check cables and equipments connected to system 2. 20577, HV ON open Description High Voltage (HV) switch on operating panel is opened. Consequences Paint enable chain opens. Recommended actions Give acknowledge on motor ON and switch on the HV key to close the HV interlock chain. 20581, SPI communication towards SIB is down Description Status active when cyclic enable 1 test fails from Safety Interface Board (SIB). Consequences The system goes to status SYS HALT. Recommended actions 1. Check status on Serial Peripheral Interface (SPI) status. 2. Check cables between Process Interface Board (PIB) abd SIB. 20582, SPI communication towards MIB is down Description Status active when cyclic enable 1 test fails from Manipulator Interface Board (MIB) arg . Consequences The system goes to status SYS HALT. Recommended actions Check cables and Serial Peripheral Interface (SPI) status. 2. Check cables between SIB and Manipulator Interface Board (MIB). 20583, Watchdog towards PIB software fails Description Status active when firmware on Process Interface Board (PIB) discover watchdog fault between PIB firmware and PIB software. Consequences The system goes to status SYS HALT. Probable causes Too high processor load on PIB software. 20584, Fault on internal SPI Description Status active when firmware on Process Interface Board (PIB) discover watchdog fault towards Safety Interface Board (SIB) and Manipulator Interface Board (MIB). Consequences The system goes to status SYS HALT. Probable causes Serial Peripheral Interface (SPI) communication is down on SPI 1. Recommended actions Check cables between PIB, SIB and MIB. 20585, Enable chain opened from IPS Description Status active when enable chain is opened from signal Safety/PibSw/ Enable. Consequences The system goes to status SYS HALT. Recommended actions Check the actuator connected to signal Safety/PibSw/Enable. 20586, Watchdog fault towards PIB firmware Description Status active when software on Process Interface Board (PIB) discover watchdog fault towards PIB firmware caused by fault on FPGA. Consequences The system goes to status SYS HALT. 20587, Watchdog fault towards PIB firmware Description Status active when software on Process Interface Board (PIB) discover watchdog fault towards PIB firmware caused by fault on the In-System Micro Controller. Consequences The system goes to status SYS HALT. 6 Trouble shooting by Event log 142 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes Firmware not running. 20588, Watchdog fault between PIB and MC Description Status active when software on Process Interface Board (PIB) discover watchdog fault towards Main Computer (MC). Consequences The system goes to status SYS FAIL. Recommended actions Check ethernet cable between PIB and MC. 20589, Watchdog fault between PIB and MCOB Description Status active when agent connection on CAN between Process Interface Board (PIB) and Manipulator Controller Board (MCOB) is down. Consequences The system goes to status SYS HALT. Recommended actions 1. Check CAN cables. 2. Check MCOB status. 20590, Open circuit mask not set Description The open circuit mask for brakes on Manipulator Controller Board (MCOB) is not set. The mask should be set from Process Interface Board (PIB) during start-up. Consequences This message will be given every time the brakes are released, until the open circuit mask on MCOB is set. Probable causes IPS configuration on PIB is not loaded or configuration file for brake settings is missing. Recommended actions 1. Check that IPS configuration is loaded during start-up. 2. Check that IPS configuration file for brake settings are installed on PIB. 20591, TPU hot plug timeout Description The TPU hot plug button is pressed for too long time. Consequences The system goes to status SYS HALT. Recommended actions Press motor ON button to close the chain. 20600, Unofficial RobotWare release Description The current RobotWare is not an officially supported release. Unofficial RobotWare releases may only be used for time-limited test and validation purposes. Consequences ABB will not provide long-term support on unofficial releases. Recommended actions If this is a production system, install an official RobotWare release as soon as possible. 20601, Too long paths when unpacking RobotWare files Description The RobotWare installation package was not properly unpacked on the controller. Some files in the package have a path that is too long and could not be handled by the controller software. During the installation process the controller software was upgraded to handle longer paths, so a re-installation of the system should solve the problem. Consequences Some RobotWare files are missing on the controller and your system may not be able to operate properly. Recommended actions Re-install the system by using SystemBuilder. If the error is still present after the re-installation, contact customer support. 20602, Unofficial RobotWare image Description The current RobotWare main computer image is not the original, and is hence not officially supported. Consequences ABB will not provide long-term support on unofficial RobotWare releases. Probable causes The officially released main computer image has been replaced, e.g., for the purpose of collecting diagnostic data for a specific problem. Recommended actions If this is a production system, install an official RobotWare release as soon as possible.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	144	6 Trouble shooting by Event log 141 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences Paint enable chain opens. Recommended actions Check cables and equipments connected to AUX inputs. 20576, System 2 Interlock open Description System 2 Interlock is opened. Normally used for Cartridge Bell System (CBS) or paint pumps Consequences Paint enable chain opens. Recommended actions Check cables and equipments connected to system 2. 20577, HV ON open Description High Voltage (HV) switch on operating panel is opened. Consequences Paint enable chain opens. Recommended actions Give acknowledge on motor ON and switch on the HV key to close the HV interlock chain. 20581, SPI communication towards SIB is down Description Status active when cyclic enable 1 test fails from Safety Interface Board (SIB). Consequences The system goes to status SYS HALT. Recommended actions 1. Check status on Serial Peripheral Interface (SPI) status. 2. Check cables between Process Interface Board (PIB) abd SIB. 20582, SPI communication towards MIB is down Description Status active when cyclic enable 1 test fails from Manipulator Interface Board (MIB) arg . Consequences The system goes to status SYS HALT. Recommended actions Check cables and Serial Peripheral Interface (SPI) status. 2. Check cables between SIB and Manipulator Interface Board (MIB). 20583, Watchdog towards PIB software fails Description Status active when firmware on Process Interface Board (PIB) discover watchdog fault between PIB firmware and PIB software. Consequences The system goes to status SYS HALT. Probable causes Too high processor load on PIB software. 20584, Fault on internal SPI Description Status active when firmware on Process Interface Board (PIB) discover watchdog fault towards Safety Interface Board (SIB) and Manipulator Interface Board (MIB). Consequences The system goes to status SYS HALT. Probable causes Serial Peripheral Interface (SPI) communication is down on SPI 1. Recommended actions Check cables between PIB, SIB and MIB. 20585, Enable chain opened from IPS Description Status active when enable chain is opened from signal Safety/PibSw/ Enable. Consequences The system goes to status SYS HALT. Recommended actions Check the actuator connected to signal Safety/PibSw/Enable. 20586, Watchdog fault towards PIB firmware Description Status active when software on Process Interface Board (PIB) discover watchdog fault towards PIB firmware caused by fault on FPGA. Consequences The system goes to status SYS HALT. 20587, Watchdog fault towards PIB firmware Description Status active when software on Process Interface Board (PIB) discover watchdog fault towards PIB firmware caused by fault on the In-System Micro Controller. Consequences The system goes to status SYS HALT. 6 Trouble shooting by Event log 142 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes Firmware not running. 20588, Watchdog fault between PIB and MC Description Status active when software on Process Interface Board (PIB) discover watchdog fault towards Main Computer (MC). Consequences The system goes to status SYS FAIL. Recommended actions Check ethernet cable between PIB and MC. 20589, Watchdog fault between PIB and MCOB Description Status active when agent connection on CAN between Process Interface Board (PIB) and Manipulator Controller Board (MCOB) is down. Consequences The system goes to status SYS HALT. Recommended actions 1. Check CAN cables. 2. Check MCOB status. 20590, Open circuit mask not set Description The open circuit mask for brakes on Manipulator Controller Board (MCOB) is not set. The mask should be set from Process Interface Board (PIB) during start-up. Consequences This message will be given every time the brakes are released, until the open circuit mask on MCOB is set. Probable causes IPS configuration on PIB is not loaded or configuration file for brake settings is missing. Recommended actions 1. Check that IPS configuration is loaded during start-up. 2. Check that IPS configuration file for brake settings are installed on PIB. 20591, TPU hot plug timeout Description The TPU hot plug button is pressed for too long time. Consequences The system goes to status SYS HALT. Recommended actions Press motor ON button to close the chain. 20600, Unofficial RobotWare release Description The current RobotWare is not an officially supported release. Unofficial RobotWare releases may only be used for time-limited test and validation purposes. Consequences ABB will not provide long-term support on unofficial releases. Recommended actions If this is a production system, install an official RobotWare release as soon as possible. 20601, Too long paths when unpacking RobotWare files Description The RobotWare installation package was not properly unpacked on the controller. Some files in the package have a path that is too long and could not be handled by the controller software. During the installation process the controller software was upgraded to handle longer paths, so a re-installation of the system should solve the problem. Consequences Some RobotWare files are missing on the controller and your system may not be able to operate properly. Recommended actions Re-install the system by using SystemBuilder. If the error is still present after the re-installation, contact customer support. 20602, Unofficial RobotWare image Description The current RobotWare main computer image is not the original, and is hence not officially supported. Consequences ABB will not provide long-term support on unofficial RobotWare releases. Probable causes The officially released main computer image has been replaced, e.g., for the purpose of collecting diagnostic data for a specific problem. Recommended actions If this is a production system, install an official RobotWare release as soon as possible. 6 Trouble shooting by Event log 143 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20610, Motor phase short circuit Description The drive unit for joint arg has reported short circuit. The joint is connected to drive module arg with unit position arg and node arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. Probable causes 1) Short circuit in cables or connectors between the phases or to ground. 2) Short circuit in motor between the phases or to ground. Recommended actions 1) Check/replace cables and connectors. 2) Check/replace motor. 20620, The system has entered an internal test mode Description A feature to perform ABB Robotics internal tests has been enabled in arg . Consequences The system may not behave as expected. Recommended actions Restart the system when the test has been performed. If this was an unexpected message, please contact your contact your local ABB representative for assistance. 31810, DeviceNet master/slave board is missing Description The DeviceNet master/slave board does not work. Consequences No communication on the Devicenet is possible. Probable causes The DeviceNet master/slave board is either malfunctioning or missing. Recommended actions 1. Make sure a DeviceNet master/slave board is installed. 2. Replace the board if faulty. 31811, Second DeviceNet master/slave board is missing Description Dual option is configured but only one DeviceNet master/slave board is installed. Consequences Only one DeviceNet bus is available. Probable causes The Second DeviceNet master/slave board is either malfunctioning or missing. Recommended actions 1. Make sure a Second DeviceNet master/slave board is installed. 2. Replace the Second board if faulty. 31812, Incompatible DeviceNet Boards Description The system has detected incompatible types of DeviceNet boards. Consequences No communication on the DeviceNet is possible. Probable causes Incompatible types of DeviceNet boards have been installed in the system. Recommended actions Make sure that compatible board types are installed. 31910, Profibus-DP master/slave board is missing Description The Profibus-DP master/slave board does not work. Consequences No communication on the Profibus is possible. Probable causes The Profibus-DP master/slave board is either malfunctioning or missing. Recommended actions 1. Make sure a Profibus-DP master/slave board is installed. 2. Replace the board if faulty. 31911, Profibus board update error Description The RobotWare software was not able to download new driver software to the Profibus-DP master/slave board. The arg channel (ch arg ) of the Profibus board could not be programmed. Internal error code: arg . Consequences No communication on the Profibus is possible. Probable causes The RobotWare software may be corrupt or the board hardware may be malfunctioning.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	145	6 Trouble shooting by Event log 142 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes Firmware not running. 20588, Watchdog fault between PIB and MC Description Status active when software on Process Interface Board (PIB) discover watchdog fault towards Main Computer (MC). Consequences The system goes to status SYS FAIL. Recommended actions Check ethernet cable between PIB and MC. 20589, Watchdog fault between PIB and MCOB Description Status active when agent connection on CAN between Process Interface Board (PIB) and Manipulator Controller Board (MCOB) is down. Consequences The system goes to status SYS HALT. Recommended actions 1. Check CAN cables. 2. Check MCOB status. 20590, Open circuit mask not set Description The open circuit mask for brakes on Manipulator Controller Board (MCOB) is not set. The mask should be set from Process Interface Board (PIB) during start-up. Consequences This message will be given every time the brakes are released, until the open circuit mask on MCOB is set. Probable causes IPS configuration on PIB is not loaded or configuration file for brake settings is missing. Recommended actions 1. Check that IPS configuration is loaded during start-up. 2. Check that IPS configuration file for brake settings are installed on PIB. 20591, TPU hot plug timeout Description The TPU hot plug button is pressed for too long time. Consequences The system goes to status SYS HALT. Recommended actions Press motor ON button to close the chain. 20600, Unofficial RobotWare release Description The current RobotWare is not an officially supported release. Unofficial RobotWare releases may only be used for time-limited test and validation purposes. Consequences ABB will not provide long-term support on unofficial releases. Recommended actions If this is a production system, install an official RobotWare release as soon as possible. 20601, Too long paths when unpacking RobotWare files Description The RobotWare installation package was not properly unpacked on the controller. Some files in the package have a path that is too long and could not be handled by the controller software. During the installation process the controller software was upgraded to handle longer paths, so a re-installation of the system should solve the problem. Consequences Some RobotWare files are missing on the controller and your system may not be able to operate properly. Recommended actions Re-install the system by using SystemBuilder. If the error is still present after the re-installation, contact customer support. 20602, Unofficial RobotWare image Description The current RobotWare main computer image is not the original, and is hence not officially supported. Consequences ABB will not provide long-term support on unofficial RobotWare releases. Probable causes The officially released main computer image has been replaced, e.g., for the purpose of collecting diagnostic data for a specific problem. Recommended actions If this is a production system, install an official RobotWare release as soon as possible. 6 Trouble shooting by Event log 143 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20610, Motor phase short circuit Description The drive unit for joint arg has reported short circuit. The joint is connected to drive module arg with unit position arg and node arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. Probable causes 1) Short circuit in cables or connectors between the phases or to ground. 2) Short circuit in motor between the phases or to ground. Recommended actions 1) Check/replace cables and connectors. 2) Check/replace motor. 20620, The system has entered an internal test mode Description A feature to perform ABB Robotics internal tests has been enabled in arg . Consequences The system may not behave as expected. Recommended actions Restart the system when the test has been performed. If this was an unexpected message, please contact your contact your local ABB representative for assistance. 31810, DeviceNet master/slave board is missing Description The DeviceNet master/slave board does not work. Consequences No communication on the Devicenet is possible. Probable causes The DeviceNet master/slave board is either malfunctioning or missing. Recommended actions 1. Make sure a DeviceNet master/slave board is installed. 2. Replace the board if faulty. 31811, Second DeviceNet master/slave board is missing Description Dual option is configured but only one DeviceNet master/slave board is installed. Consequences Only one DeviceNet bus is available. Probable causes The Second DeviceNet master/slave board is either malfunctioning or missing. Recommended actions 1. Make sure a Second DeviceNet master/slave board is installed. 2. Replace the Second board if faulty. 31812, Incompatible DeviceNet Boards Description The system has detected incompatible types of DeviceNet boards. Consequences No communication on the DeviceNet is possible. Probable causes Incompatible types of DeviceNet boards have been installed in the system. Recommended actions Make sure that compatible board types are installed. 31910, Profibus-DP master/slave board is missing Description The Profibus-DP master/slave board does not work. Consequences No communication on the Profibus is possible. Probable causes The Profibus-DP master/slave board is either malfunctioning or missing. Recommended actions 1. Make sure a Profibus-DP master/slave board is installed. 2. Replace the board if faulty. 31911, Profibus board update error Description The RobotWare software was not able to download new driver software to the Profibus-DP master/slave board. The arg channel (ch arg ) of the Profibus board could not be programmed. Internal error code: arg . Consequences No communication on the Profibus is possible. Probable causes The RobotWare software may be corrupt or the board hardware may be malfunctioning. 6 Trouble shooting by Event log 144 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1. Restart the system to reattempt downloading the software. 2. Reinstall the present system files. 3. Create and run a new system to download the driver software. 4. Replace the board if faulty. 31912, Profibus-DP master/slave board failure Description The Profibus-DP master/slave board did not start up correctly. Consequences No communication on the Profibus is possible. Probable causes The Profibus-DP master/slave board hardware may be malfunctioning. Recommended actions 1. Restart the system. 2. Replace the Profibus-DP master/slave board if faulty. 31913, Profibus-DP master/slave board internal error Description The Profibus-DP master/slave board reported internal error arg . Consequences No communication on the Profibus is possible. Probable causes The Profibus-DP master/slave board hardware may be malfunctioning. Recommended actions 1. Restart the system. 2. Replace the Profibus-DP master/slave board if faulty. 31914, Profibus startup error Description - Profibus master bus error Error code arg . Check cabling, terminators and modules then restart. Recommended actions 31915, Profibus Bus Error Description Profibus master bus error. Internal error Error code arg . Consequences Certain expected associated errors may be delayed. Probable causes Faulty profibus cabling, terminators and/or module(s). Duplicated profibus addresses. Recommended actions Check cabling, terminators and modules. 31916, Profibus bus OK Description - Profibus regained contact on the master bus. Recommended actions 31917, Profibus-DP master/slave board exception Description A fatal error has occurred on the Profibus-DP master/slave board. arg channel in task arg . Parameters arg Consequences No communication on the Profibus is possible. Probable causes The Profibus-DP master/slave board hardware may be malfunctioning. Recommended actions 1. Restart the system. 2. Replace the Profibus-DP master/slave board if faulty. 32500, Robot Communication Card is missing Description The system cannot contact the Robot Communication Card. Consequences No communication with the Safety System is possible. The system goes to status SYS FAIL. Probable causes The Robot Communication Card is either malfunctioning or missing. Recommended actions 1. Make sure a Robot Communication Card is installed. 2. Replace the unit if faulty. 32501, Incorrect RCC firmware Description The FPGAR11-Firmware on the RCC (DSQC602) is of an incompatible version. Current version: arg . arg Requested version: arg . arg Recommended actions 1. Replace the DSQC602 board 2. Restart the system
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	146	6 Trouble shooting by Event log 143 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 20610, Motor phase short circuit Description The drive unit for joint arg has reported short circuit. The joint is connected to drive module arg with unit position arg and node arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. Probable causes 1) Short circuit in cables or connectors between the phases or to ground. 2) Short circuit in motor between the phases or to ground. Recommended actions 1) Check/replace cables and connectors. 2) Check/replace motor. 20620, The system has entered an internal test mode Description A feature to perform ABB Robotics internal tests has been enabled in arg . Consequences The system may not behave as expected. Recommended actions Restart the system when the test has been performed. If this was an unexpected message, please contact your contact your local ABB representative for assistance. 31810, DeviceNet master/slave board is missing Description The DeviceNet master/slave board does not work. Consequences No communication on the Devicenet is possible. Probable causes The DeviceNet master/slave board is either malfunctioning or missing. Recommended actions 1. Make sure a DeviceNet master/slave board is installed. 2. Replace the board if faulty. 31811, Second DeviceNet master/slave board is missing Description Dual option is configured but only one DeviceNet master/slave board is installed. Consequences Only one DeviceNet bus is available. Probable causes The Second DeviceNet master/slave board is either malfunctioning or missing. Recommended actions 1. Make sure a Second DeviceNet master/slave board is installed. 2. Replace the Second board if faulty. 31812, Incompatible DeviceNet Boards Description The system has detected incompatible types of DeviceNet boards. Consequences No communication on the DeviceNet is possible. Probable causes Incompatible types of DeviceNet boards have been installed in the system. Recommended actions Make sure that compatible board types are installed. 31910, Profibus-DP master/slave board is missing Description The Profibus-DP master/slave board does not work. Consequences No communication on the Profibus is possible. Probable causes The Profibus-DP master/slave board is either malfunctioning or missing. Recommended actions 1. Make sure a Profibus-DP master/slave board is installed. 2. Replace the board if faulty. 31911, Profibus board update error Description The RobotWare software was not able to download new driver software to the Profibus-DP master/slave board. The arg channel (ch arg ) of the Profibus board could not be programmed. Internal error code: arg . Consequences No communication on the Profibus is possible. Probable causes The RobotWare software may be corrupt or the board hardware may be malfunctioning. 6 Trouble shooting by Event log 144 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1. Restart the system to reattempt downloading the software. 2. Reinstall the present system files. 3. Create and run a new system to download the driver software. 4. Replace the board if faulty. 31912, Profibus-DP master/slave board failure Description The Profibus-DP master/slave board did not start up correctly. Consequences No communication on the Profibus is possible. Probable causes The Profibus-DP master/slave board hardware may be malfunctioning. Recommended actions 1. Restart the system. 2. Replace the Profibus-DP master/slave board if faulty. 31913, Profibus-DP master/slave board internal error Description The Profibus-DP master/slave board reported internal error arg . Consequences No communication on the Profibus is possible. Probable causes The Profibus-DP master/slave board hardware may be malfunctioning. Recommended actions 1. Restart the system. 2. Replace the Profibus-DP master/slave board if faulty. 31914, Profibus startup error Description - Profibus master bus error Error code arg . Check cabling, terminators and modules then restart. Recommended actions 31915, Profibus Bus Error Description Profibus master bus error. Internal error Error code arg . Consequences Certain expected associated errors may be delayed. Probable causes Faulty profibus cabling, terminators and/or module(s). Duplicated profibus addresses. Recommended actions Check cabling, terminators and modules. 31916, Profibus bus OK Description - Profibus regained contact on the master bus. Recommended actions 31917, Profibus-DP master/slave board exception Description A fatal error has occurred on the Profibus-DP master/slave board. arg channel in task arg . Parameters arg Consequences No communication on the Profibus is possible. Probable causes The Profibus-DP master/slave board hardware may be malfunctioning. Recommended actions 1. Restart the system. 2. Replace the Profibus-DP master/slave board if faulty. 32500, Robot Communication Card is missing Description The system cannot contact the Robot Communication Card. Consequences No communication with the Safety System is possible. The system goes to status SYS FAIL. Probable causes The Robot Communication Card is either malfunctioning or missing. Recommended actions 1. Make sure a Robot Communication Card is installed. 2. Replace the unit if faulty. 32501, Incorrect RCC firmware Description The FPGAR11-Firmware on the RCC (DSQC602) is of an incompatible version. Current version: arg . arg Requested version: arg . arg Recommended actions 1. Replace the DSQC602 board 2. Restart the system 6 Trouble shooting by Event log 145 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 32502, Can't find file Description The system cannot find the file: [ arg ] Recommended actions Reinstall the system 32503, Requested info not in file Description The system cannot find information about what software to download to HardWare ID=" arg ", Version=" arg ", Revision=" arg " in file [ arg ]. Probable causes The file has either been damaged, or the actual hardware version of the unit is not supported. Recommended actions 1. Reinstall the system 2. Replace the unit to a version which is supported by this SW-release. 32530, No Communication With The Safety System Description There is no serial communication between the Safety System and the robot communication card. Consequences The system goes to status SYS FAIL. Probable causes Probably hardware fault in cable between Safety System and Robot Communication Card. The Safety System, or it's power supply, may also be faulty. Recommended actions 1) Restart the system to resume operation. 2) Make sure the cable between robot communication card and Safety System is working and correctly connected. 3) Check the Safety System power supply. 4) Replace the unit if faulty. 32540, Drive unit firmware reflash started Description In drive module arg , a required upgrade of the firmware in the drive unit at unit position arg has started. The old firmware revision arg is replaced with revision arg . Recommended actions Wait for the firmware upgrade process to complete. Do not turn off system power! 32541, Drive unit firmware reflash complete Description In drive module arg , the upgrade of the firmware in the drive unit with unit position arg is completed. New revision is arg . 32542, Drive unit hardware not supported Description In drive module arg , the system cannot use the drive unit with hardware identity arg because the hardware revision arg is not supported. Consequences The system is unable to use the drive unit. The system goes to System Failure state. Probable causes The RobotWare version is too old to support the drive unit. Recommended actions 1) Upgrade the system to a RobotWare version supporting the drive unit revision. 2) Replace the drive unit to one with compatible revision. 32543, Drive unit firmware reflash failed Description In drive module arg , the upgrade of the firmware in the drive unit at unit position arg failed. Consequences The required upgrade of the drive unit firmware is not performed. Recommended actions 1) Check other hardware eventlog messages for detailed explanation of the error condition. 2) Try again by restart the system using the main power switch. 32544, Drive unit firmware file not found Description The file arg , required to upgrade a drive unit’s firmware, is not found. Consequences The required upgrade of the drive unit firmware is not performed. Probable causes The RobotWare installation does not contain the firmware file. Recommended actions Reinstall the system. 32545, Drive unit firmware file type error Description The file arg , required to upgrade a drive unit’s firmware, is of wrong type.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	147	6 Trouble shooting by Event log 144 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1. Restart the system to reattempt downloading the software. 2. Reinstall the present system files. 3. Create and run a new system to download the driver software. 4. Replace the board if faulty. 31912, Profibus-DP master/slave board failure Description The Profibus-DP master/slave board did not start up correctly. Consequences No communication on the Profibus is possible. Probable causes The Profibus-DP master/slave board hardware may be malfunctioning. Recommended actions 1. Restart the system. 2. Replace the Profibus-DP master/slave board if faulty. 31913, Profibus-DP master/slave board internal error Description The Profibus-DP master/slave board reported internal error arg . Consequences No communication on the Profibus is possible. Probable causes The Profibus-DP master/slave board hardware may be malfunctioning. Recommended actions 1. Restart the system. 2. Replace the Profibus-DP master/slave board if faulty. 31914, Profibus startup error Description - Profibus master bus error Error code arg . Check cabling, terminators and modules then restart. Recommended actions 31915, Profibus Bus Error Description Profibus master bus error. Internal error Error code arg . Consequences Certain expected associated errors may be delayed. Probable causes Faulty profibus cabling, terminators and/or module(s). Duplicated profibus addresses. Recommended actions Check cabling, terminators and modules. 31916, Profibus bus OK Description - Profibus regained contact on the master bus. Recommended actions 31917, Profibus-DP master/slave board exception Description A fatal error has occurred on the Profibus-DP master/slave board. arg channel in task arg . Parameters arg Consequences No communication on the Profibus is possible. Probable causes The Profibus-DP master/slave board hardware may be malfunctioning. Recommended actions 1. Restart the system. 2. Replace the Profibus-DP master/slave board if faulty. 32500, Robot Communication Card is missing Description The system cannot contact the Robot Communication Card. Consequences No communication with the Safety System is possible. The system goes to status SYS FAIL. Probable causes The Robot Communication Card is either malfunctioning or missing. Recommended actions 1. Make sure a Robot Communication Card is installed. 2. Replace the unit if faulty. 32501, Incorrect RCC firmware Description The FPGAR11-Firmware on the RCC (DSQC602) is of an incompatible version. Current version: arg . arg Requested version: arg . arg Recommended actions 1. Replace the DSQC602 board 2. Restart the system 6 Trouble shooting by Event log 145 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 32502, Can't find file Description The system cannot find the file: [ arg ] Recommended actions Reinstall the system 32503, Requested info not in file Description The system cannot find information about what software to download to HardWare ID=" arg ", Version=" arg ", Revision=" arg " in file [ arg ]. Probable causes The file has either been damaged, or the actual hardware version of the unit is not supported. Recommended actions 1. Reinstall the system 2. Replace the unit to a version which is supported by this SW-release. 32530, No Communication With The Safety System Description There is no serial communication between the Safety System and the robot communication card. Consequences The system goes to status SYS FAIL. Probable causes Probably hardware fault in cable between Safety System and Robot Communication Card. The Safety System, or it's power supply, may also be faulty. Recommended actions 1) Restart the system to resume operation. 2) Make sure the cable between robot communication card and Safety System is working and correctly connected. 3) Check the Safety System power supply. 4) Replace the unit if faulty. 32540, Drive unit firmware reflash started Description In drive module arg , a required upgrade of the firmware in the drive unit at unit position arg has started. The old firmware revision arg is replaced with revision arg . Recommended actions Wait for the firmware upgrade process to complete. Do not turn off system power! 32541, Drive unit firmware reflash complete Description In drive module arg , the upgrade of the firmware in the drive unit with unit position arg is completed. New revision is arg . 32542, Drive unit hardware not supported Description In drive module arg , the system cannot use the drive unit with hardware identity arg because the hardware revision arg is not supported. Consequences The system is unable to use the drive unit. The system goes to System Failure state. Probable causes The RobotWare version is too old to support the drive unit. Recommended actions 1) Upgrade the system to a RobotWare version supporting the drive unit revision. 2) Replace the drive unit to one with compatible revision. 32543, Drive unit firmware reflash failed Description In drive module arg , the upgrade of the firmware in the drive unit at unit position arg failed. Consequences The required upgrade of the drive unit firmware is not performed. Recommended actions 1) Check other hardware eventlog messages for detailed explanation of the error condition. 2) Try again by restart the system using the main power switch. 32544, Drive unit firmware file not found Description The file arg , required to upgrade a drive unit’s firmware, is not found. Consequences The required upgrade of the drive unit firmware is not performed. Probable causes The RobotWare installation does not contain the firmware file. Recommended actions Reinstall the system. 32545, Drive unit firmware file type error Description The file arg , required to upgrade a drive unit’s firmware, is of wrong type. 6 Trouble shooting by Event log 146 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences The required upgrade of the drive unit firmware is not performed. Probable causes The RobotWare installation is faulty. Recommended actions Reinstall the system. 32546, Drive unit firmware file error Description The file arg , required to upgrade a drive unit’s firmware, is not usable because it failed the integrity check. Consequences The required upgrade of the drive unit firmware is not performed. Probable causes The RobotWare installation is faulty. Recommended actions Reinstall the system. 32550, Firmware reflash started Description A required update of the arg firmware has started. File used: [ arg ]. Recommended actions Wait for the reflash to complete 32551, Firmware reflash completed Description The update of arg firmware has completed successfully. 32552, Firmware reflash failed Description The update of arg firmware failed. Internal errorcode: arg Recommended actions 1. Check other error messages for detailed explanation 2. Restart the system 3. Reinstall the system 4. Replace the arg 32553, Firmware file is corrupt Description The firmware file [ arg ] is corrupt. Internal errorcode: arg Recommended actions Reinstall the system 32554, Firmware file not found Description The firmware file [ arg ] is not found. Recommended actions Reinstall the system 32555, Safety System Unit Not Supported Description The system cannot use the Safety System unit arg , revision arg . Consequences The system is unable to use the affected hardware. Recommended actions 1. Change the affected hardware to a compatible version. 32560, Axis computer firmware reflash started Description In drive module arg , a required upgrade of the firmware in the axis computer arg with hardware identity arg has started. The old firmware revision arg is replaced with revision arg . Recommended actions Wait for the firmware upgrade process to complete. Do not turn off system power! 32561, Axis computer firmware reflash complete Description In drive module arg , the upgrade of the firmware in the axis computer arg with hardware identity arg is completed. New revision is arg . 32562, Axis computer communication error Description The system failed to communicate with the axis computer in drive module arg when trying to read firmware information. Consequences The system is unable to determine if an upgrade is required of the firmware in the affected drive module. The system goes to System Failure state. Probable causes This may be due to a cable break, bad connector or high levels of interference in the cable between the main computer and the axis computer. Recommended actions 1) Make sure the cable between the main computer and the axis computer is not damaged and that both connectors are correctly connected.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	148	6 Trouble shooting by Event log 145 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 32502, Can't find file Description The system cannot find the file: [ arg ] Recommended actions Reinstall the system 32503, Requested info not in file Description The system cannot find information about what software to download to HardWare ID=" arg ", Version=" arg ", Revision=" arg " in file [ arg ]. Probable causes The file has either been damaged, or the actual hardware version of the unit is not supported. Recommended actions 1. Reinstall the system 2. Replace the unit to a version which is supported by this SW-release. 32530, No Communication With The Safety System Description There is no serial communication between the Safety System and the robot communication card. Consequences The system goes to status SYS FAIL. Probable causes Probably hardware fault in cable between Safety System and Robot Communication Card. The Safety System, or it's power supply, may also be faulty. Recommended actions 1) Restart the system to resume operation. 2) Make sure the cable between robot communication card and Safety System is working and correctly connected. 3) Check the Safety System power supply. 4) Replace the unit if faulty. 32540, Drive unit firmware reflash started Description In drive module arg , a required upgrade of the firmware in the drive unit at unit position arg has started. The old firmware revision arg is replaced with revision arg . Recommended actions Wait for the firmware upgrade process to complete. Do not turn off system power! 32541, Drive unit firmware reflash complete Description In drive module arg , the upgrade of the firmware in the drive unit with unit position arg is completed. New revision is arg . 32542, Drive unit hardware not supported Description In drive module arg , the system cannot use the drive unit with hardware identity arg because the hardware revision arg is not supported. Consequences The system is unable to use the drive unit. The system goes to System Failure state. Probable causes The RobotWare version is too old to support the drive unit. Recommended actions 1) Upgrade the system to a RobotWare version supporting the drive unit revision. 2) Replace the drive unit to one with compatible revision. 32543, Drive unit firmware reflash failed Description In drive module arg , the upgrade of the firmware in the drive unit at unit position arg failed. Consequences The required upgrade of the drive unit firmware is not performed. Recommended actions 1) Check other hardware eventlog messages for detailed explanation of the error condition. 2) Try again by restart the system using the main power switch. 32544, Drive unit firmware file not found Description The file arg , required to upgrade a drive unit’s firmware, is not found. Consequences The required upgrade of the drive unit firmware is not performed. Probable causes The RobotWare installation does not contain the firmware file. Recommended actions Reinstall the system. 32545, Drive unit firmware file type error Description The file arg , required to upgrade a drive unit’s firmware, is of wrong type. 6 Trouble shooting by Event log 146 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences The required upgrade of the drive unit firmware is not performed. Probable causes The RobotWare installation is faulty. Recommended actions Reinstall the system. 32546, Drive unit firmware file error Description The file arg , required to upgrade a drive unit’s firmware, is not usable because it failed the integrity check. Consequences The required upgrade of the drive unit firmware is not performed. Probable causes The RobotWare installation is faulty. Recommended actions Reinstall the system. 32550, Firmware reflash started Description A required update of the arg firmware has started. File used: [ arg ]. Recommended actions Wait for the reflash to complete 32551, Firmware reflash completed Description The update of arg firmware has completed successfully. 32552, Firmware reflash failed Description The update of arg firmware failed. Internal errorcode: arg Recommended actions 1. Check other error messages for detailed explanation 2. Restart the system 3. Reinstall the system 4. Replace the arg 32553, Firmware file is corrupt Description The firmware file [ arg ] is corrupt. Internal errorcode: arg Recommended actions Reinstall the system 32554, Firmware file not found Description The firmware file [ arg ] is not found. Recommended actions Reinstall the system 32555, Safety System Unit Not Supported Description The system cannot use the Safety System unit arg , revision arg . Consequences The system is unable to use the affected hardware. Recommended actions 1. Change the affected hardware to a compatible version. 32560, Axis computer firmware reflash started Description In drive module arg , a required upgrade of the firmware in the axis computer arg with hardware identity arg has started. The old firmware revision arg is replaced with revision arg . Recommended actions Wait for the firmware upgrade process to complete. Do not turn off system power! 32561, Axis computer firmware reflash complete Description In drive module arg , the upgrade of the firmware in the axis computer arg with hardware identity arg is completed. New revision is arg . 32562, Axis computer communication error Description The system failed to communicate with the axis computer in drive module arg when trying to read firmware information. Consequences The system is unable to determine if an upgrade is required of the firmware in the affected drive module. The system goes to System Failure state. Probable causes This may be due to a cable break, bad connector or high levels of interference in the cable between the main computer and the axis computer. Recommended actions 1) Make sure the cable between the main computer and the axis computer is not damaged and that both connectors are correctly connected. 6 Trouble shooting by Event log 147 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 2) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling. 32563, Axis computer hardware not supported Description In drive module arg , the system cannot use the axis computer with hardware identity arg because the hardware revision arg is not supported. Consequences The system is unable to use the axis computer. The system goes to System Failure state. Probable causes The RobotWare version is too old to support the axis computer unit. Recommended actions 1) Replace the axis computer to one with compatible revision. 2) Upgrade the system to a RobotWare version supporting the axis computer revision. 32564, Axis computer firmware reflash failed Description In drive module arg , the upgrade of the firmware in the axis computer arg with hardware identity arg failed. Consequences The required upgrade of the axis computer firmware is not performed. Recommended actions 1) Check other hardware eventlog messages for detailed explanation of the error condition. 2) Retry again by restarting the system using the main power switch. 32565, Axis computer firmware file not found Description The file arg , required to upgrade an axis computer’s firmware, is not found. Consequences The required upgrade of the axis computer firmware is not performed. Probable causes The RobotWare installation does not contain the firmware file. Recommended actions Reinstall the system. 32567, Axis computer firmware file type error Description The file arg , required to upgrade an axis computer firmware, is of wrong type. Consequences The required upgrade of the axis computer’s firmware is not performed. Probable causes The firmware file is corrupt. Recommended actions Reinstall the system. 32568, Axis computer firmware file error Description The file arg , required to upgrade an axis computer’s firmware, is not usable because it failed the integrity check. Consequences The required upgrade of the axis computer firmware is not performed. Probable causes The firmware file is corrupt. Recommended actions Reinstall the system. 32569, Corrupt axis computer hardware Description In drive module arg , the axis computer flash memory has a corrupt content. Recommended actions 1. Retry again by restarting the system using the main power switch. 2. If the problem remains then replace the axis computer. 32570, Firmware reflash started Description A required update of the arg firmware has started. Replacing old firmware version: [ arg ]. Recommended actions Wait for the reflash to complete 32571, Firmware reflash completed Description The update of arg firmware has completed successfully. New version: [ arg ]. Internal code:[ arg ] 32572, Firmware reflash failed Description The upgrade of arg firmware failed. Current version: arg . Internal errorcode: arg .
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	149	6 Trouble shooting by Event log 146 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences The required upgrade of the drive unit firmware is not performed. Probable causes The RobotWare installation is faulty. Recommended actions Reinstall the system. 32546, Drive unit firmware file error Description The file arg , required to upgrade a drive unit’s firmware, is not usable because it failed the integrity check. Consequences The required upgrade of the drive unit firmware is not performed. Probable causes The RobotWare installation is faulty. Recommended actions Reinstall the system. 32550, Firmware reflash started Description A required update of the arg firmware has started. File used: [ arg ]. Recommended actions Wait for the reflash to complete 32551, Firmware reflash completed Description The update of arg firmware has completed successfully. 32552, Firmware reflash failed Description The update of arg firmware failed. Internal errorcode: arg Recommended actions 1. Check other error messages for detailed explanation 2. Restart the system 3. Reinstall the system 4. Replace the arg 32553, Firmware file is corrupt Description The firmware file [ arg ] is corrupt. Internal errorcode: arg Recommended actions Reinstall the system 32554, Firmware file not found Description The firmware file [ arg ] is not found. Recommended actions Reinstall the system 32555, Safety System Unit Not Supported Description The system cannot use the Safety System unit arg , revision arg . Consequences The system is unable to use the affected hardware. Recommended actions 1. Change the affected hardware to a compatible version. 32560, Axis computer firmware reflash started Description In drive module arg , a required upgrade of the firmware in the axis computer arg with hardware identity arg has started. The old firmware revision arg is replaced with revision arg . Recommended actions Wait for the firmware upgrade process to complete. Do not turn off system power! 32561, Axis computer firmware reflash complete Description In drive module arg , the upgrade of the firmware in the axis computer arg with hardware identity arg is completed. New revision is arg . 32562, Axis computer communication error Description The system failed to communicate with the axis computer in drive module arg when trying to read firmware information. Consequences The system is unable to determine if an upgrade is required of the firmware in the affected drive module. The system goes to System Failure state. Probable causes This may be due to a cable break, bad connector or high levels of interference in the cable between the main computer and the axis computer. Recommended actions 1) Make sure the cable between the main computer and the axis computer is not damaged and that both connectors are correctly connected. 6 Trouble shooting by Event log 147 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 2) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling. 32563, Axis computer hardware not supported Description In drive module arg , the system cannot use the axis computer with hardware identity arg because the hardware revision arg is not supported. Consequences The system is unable to use the axis computer. The system goes to System Failure state. Probable causes The RobotWare version is too old to support the axis computer unit. Recommended actions 1) Replace the axis computer to one with compatible revision. 2) Upgrade the system to a RobotWare version supporting the axis computer revision. 32564, Axis computer firmware reflash failed Description In drive module arg , the upgrade of the firmware in the axis computer arg with hardware identity arg failed. Consequences The required upgrade of the axis computer firmware is not performed. Recommended actions 1) Check other hardware eventlog messages for detailed explanation of the error condition. 2) Retry again by restarting the system using the main power switch. 32565, Axis computer firmware file not found Description The file arg , required to upgrade an axis computer’s firmware, is not found. Consequences The required upgrade of the axis computer firmware is not performed. Probable causes The RobotWare installation does not contain the firmware file. Recommended actions Reinstall the system. 32567, Axis computer firmware file type error Description The file arg , required to upgrade an axis computer firmware, is of wrong type. Consequences The required upgrade of the axis computer’s firmware is not performed. Probable causes The firmware file is corrupt. Recommended actions Reinstall the system. 32568, Axis computer firmware file error Description The file arg , required to upgrade an axis computer’s firmware, is not usable because it failed the integrity check. Consequences The required upgrade of the axis computer firmware is not performed. Probable causes The firmware file is corrupt. Recommended actions Reinstall the system. 32569, Corrupt axis computer hardware Description In drive module arg , the axis computer flash memory has a corrupt content. Recommended actions 1. Retry again by restarting the system using the main power switch. 2. If the problem remains then replace the axis computer. 32570, Firmware reflash started Description A required update of the arg firmware has started. Replacing old firmware version: [ arg ]. Recommended actions Wait for the reflash to complete 32571, Firmware reflash completed Description The update of arg firmware has completed successfully. New version: [ arg ]. Internal code:[ arg ] 32572, Firmware reflash failed Description The upgrade of arg firmware failed. Current version: arg . Internal errorcode: arg . 6 Trouble shooting by Event log 148 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1. Check other hardware eventlog messages for detailed explanation of the error condition. 2. Reinstall the system. 32573, Unable to download firmware file Description The firmware file arg is not found. Internal error code: arg . Recommended actions Reinstall the system. 32574, Corrupt axis computer hardware Description The arg flash memory has a corrupt content. Internal error code: arg . Recommended actions 1. Check other hardware eventlog messages for detailed explanation of the error condition. 2. Restart the system. 3. If failure occurs again, replace the axis computer. 32575, Found no axis computer board Description System failed to detect any connected axis computer. Recommended actions 1. Check system for axis computer board. 2. Check ethernet cables between the main computer and the axis computer. 3. Restart the system. 32576, Axis firmware: No communication Description The system failed to communicate with axis board arg when trying to check the firmware version. Consequences The system is unable to check and if necessary upgrade the firmware in the affected axis computer. Recommended actions 1. Check system for axis computer board. 2. Check ethernet cables between the main computer and the axis computer. 3. Restart system. 32577, Axis computer hardware data error Description In drive module arg , the axis computer has corrupt information stored on the unit. Consequences The system goes to System Failure state. Probable causes The integrity check of the axis computer information stored on the unit has failed. Recommended actions 1) Retry again by restarting the system using the main power switch. 2) Replace the faulty axis computer. 32580, Firmware reflash started Description A required update of the arg firmware has started. Internal code: [ arg ]. File: [ arg ]. Recommended actions Wait for the reflash to complete 32581, Firmware reflash completed Description The update of arg firmware has completed successfully . Internal code:[ arg ] Recommended actions No action required 32582, Firmware reflash failed Description The update of arg firmware failed. Internal errorcode: arg Recommended actions 1. Check other error messages for detailed explanation. 2. Reinstall the system. 32583, Firmware file corrupt Description The update of arg firmware failed. The firmware file [ arg ] is corrupt. Internal errorcode: arg . Recommended actions Reinstall the system 32584, Firmware file not found Description The update of arg firmware failed. The firmware file [ arg ] is not found. Internal errorcode: arg .
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	150	6 Trouble shooting by Event log 147 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 2) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling. 32563, Axis computer hardware not supported Description In drive module arg , the system cannot use the axis computer with hardware identity arg because the hardware revision arg is not supported. Consequences The system is unable to use the axis computer. The system goes to System Failure state. Probable causes The RobotWare version is too old to support the axis computer unit. Recommended actions 1) Replace the axis computer to one with compatible revision. 2) Upgrade the system to a RobotWare version supporting the axis computer revision. 32564, Axis computer firmware reflash failed Description In drive module arg , the upgrade of the firmware in the axis computer arg with hardware identity arg failed. Consequences The required upgrade of the axis computer firmware is not performed. Recommended actions 1) Check other hardware eventlog messages for detailed explanation of the error condition. 2) Retry again by restarting the system using the main power switch. 32565, Axis computer firmware file not found Description The file arg , required to upgrade an axis computer’s firmware, is not found. Consequences The required upgrade of the axis computer firmware is not performed. Probable causes The RobotWare installation does not contain the firmware file. Recommended actions Reinstall the system. 32567, Axis computer firmware file type error Description The file arg , required to upgrade an axis computer firmware, is of wrong type. Consequences The required upgrade of the axis computer’s firmware is not performed. Probable causes The firmware file is corrupt. Recommended actions Reinstall the system. 32568, Axis computer firmware file error Description The file arg , required to upgrade an axis computer’s firmware, is not usable because it failed the integrity check. Consequences The required upgrade of the axis computer firmware is not performed. Probable causes The firmware file is corrupt. Recommended actions Reinstall the system. 32569, Corrupt axis computer hardware Description In drive module arg , the axis computer flash memory has a corrupt content. Recommended actions 1. Retry again by restarting the system using the main power switch. 2. If the problem remains then replace the axis computer. 32570, Firmware reflash started Description A required update of the arg firmware has started. Replacing old firmware version: [ arg ]. Recommended actions Wait for the reflash to complete 32571, Firmware reflash completed Description The update of arg firmware has completed successfully. New version: [ arg ]. Internal code:[ arg ] 32572, Firmware reflash failed Description The upgrade of arg firmware failed. Current version: arg . Internal errorcode: arg . 6 Trouble shooting by Event log 148 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1. Check other hardware eventlog messages for detailed explanation of the error condition. 2. Reinstall the system. 32573, Unable to download firmware file Description The firmware file arg is not found. Internal error code: arg . Recommended actions Reinstall the system. 32574, Corrupt axis computer hardware Description The arg flash memory has a corrupt content. Internal error code: arg . Recommended actions 1. Check other hardware eventlog messages for detailed explanation of the error condition. 2. Restart the system. 3. If failure occurs again, replace the axis computer. 32575, Found no axis computer board Description System failed to detect any connected axis computer. Recommended actions 1. Check system for axis computer board. 2. Check ethernet cables between the main computer and the axis computer. 3. Restart the system. 32576, Axis firmware: No communication Description The system failed to communicate with axis board arg when trying to check the firmware version. Consequences The system is unable to check and if necessary upgrade the firmware in the affected axis computer. Recommended actions 1. Check system for axis computer board. 2. Check ethernet cables between the main computer and the axis computer. 3. Restart system. 32577, Axis computer hardware data error Description In drive module arg , the axis computer has corrupt information stored on the unit. Consequences The system goes to System Failure state. Probable causes The integrity check of the axis computer information stored on the unit has failed. Recommended actions 1) Retry again by restarting the system using the main power switch. 2) Replace the faulty axis computer. 32580, Firmware reflash started Description A required update of the arg firmware has started. Internal code: [ arg ]. File: [ arg ]. Recommended actions Wait for the reflash to complete 32581, Firmware reflash completed Description The update of arg firmware has completed successfully . Internal code:[ arg ] Recommended actions No action required 32582, Firmware reflash failed Description The update of arg firmware failed. Internal errorcode: arg Recommended actions 1. Check other error messages for detailed explanation. 2. Reinstall the system. 32583, Firmware file corrupt Description The update of arg firmware failed. The firmware file [ arg ] is corrupt. Internal errorcode: arg . Recommended actions Reinstall the system 32584, Firmware file not found Description The update of arg firmware failed. The firmware file [ arg ] is not found. Internal errorcode: arg . 6 Trouble shooting by Event log 149 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Reinstall the system 32585, No Safety System Found By Axis Computer Description Axis computer failed to detect the Safety System. Recommended actions 1. Check communication cables between the axis computer and the Safety System. 2. Check power supply to the Safety System. 3. Restart the system 32590, Firmware reflash started Description A required update of the arg firmware in drive module arg has started. File: [ arg ]. Recommended actions Wait for the reflash to complete, this will take approximately 3.5 minutes. 32591, Firmware reflash completed Description The update of arg firmware in drive module arg has sucessfully completed. Recommended actions No action required 32592, Firmware reflash failed Description The update of arg firmware in drive module arg has failed. Recommended actions 1. Check other error messages for detailed explanation. 2. Reinstall the system. 32593, Firmware file corrupt Description The update of arg firmware in drive module arg has failed. The firmware file [ arg ] is corrupt. Recommended actions Reinstall the system 32594, Firmware file not found Description The update of arg firmware in drive module arg has failed. The firmware file [ arg ] is not found. Recommended actions Reinstall the system 32601, Interbus master/slave board is missing Description The Interbus master/slave board does not work. Consequences No communication on the Interbus is possible. Probable causes The Interbus master/slave board is either malfunctioning or missing. Recommended actions 1) Make sure a Interbus master/slave board is installed. 2) Replace the board if faulty. 32651, Serial port hardware is not accessible Description The system has tried to address the serial port arg , and failed. Consequences The optional serial port hardware can not be accessed. The connector and the physical channel using the connector will not be available for use. Probable causes The serial port hardware is missing or malfunctioning. Recommended actions 1) Make sure the required serial port hardware has been correctly installed and is not faulty. 2) Replace the serial port hardware. 33503, Revolution counter update failure Description Update of the revolution counter for joint arg failed. Consequences Joint not synchronized Probable causes 1. Joint missing or not active 2. Measurement system error Recommended actions 1. Check if joint active 2. Check configuration files 3. Check measurement system
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	151	6 Trouble shooting by Event log 148 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1. Check other hardware eventlog messages for detailed explanation of the error condition. 2. Reinstall the system. 32573, Unable to download firmware file Description The firmware file arg is not found. Internal error code: arg . Recommended actions Reinstall the system. 32574, Corrupt axis computer hardware Description The arg flash memory has a corrupt content. Internal error code: arg . Recommended actions 1. Check other hardware eventlog messages for detailed explanation of the error condition. 2. Restart the system. 3. If failure occurs again, replace the axis computer. 32575, Found no axis computer board Description System failed to detect any connected axis computer. Recommended actions 1. Check system for axis computer board. 2. Check ethernet cables between the main computer and the axis computer. 3. Restart the system. 32576, Axis firmware: No communication Description The system failed to communicate with axis board arg when trying to check the firmware version. Consequences The system is unable to check and if necessary upgrade the firmware in the affected axis computer. Recommended actions 1. Check system for axis computer board. 2. Check ethernet cables between the main computer and the axis computer. 3. Restart system. 32577, Axis computer hardware data error Description In drive module arg , the axis computer has corrupt information stored on the unit. Consequences The system goes to System Failure state. Probable causes The integrity check of the axis computer information stored on the unit has failed. Recommended actions 1) Retry again by restarting the system using the main power switch. 2) Replace the faulty axis computer. 32580, Firmware reflash started Description A required update of the arg firmware has started. Internal code: [ arg ]. File: [ arg ]. Recommended actions Wait for the reflash to complete 32581, Firmware reflash completed Description The update of arg firmware has completed successfully . Internal code:[ arg ] Recommended actions No action required 32582, Firmware reflash failed Description The update of arg firmware failed. Internal errorcode: arg Recommended actions 1. Check other error messages for detailed explanation. 2. Reinstall the system. 32583, Firmware file corrupt Description The update of arg firmware failed. The firmware file [ arg ] is corrupt. Internal errorcode: arg . Recommended actions Reinstall the system 32584, Firmware file not found Description The update of arg firmware failed. The firmware file [ arg ] is not found. Internal errorcode: arg . 6 Trouble shooting by Event log 149 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Reinstall the system 32585, No Safety System Found By Axis Computer Description Axis computer failed to detect the Safety System. Recommended actions 1. Check communication cables between the axis computer and the Safety System. 2. Check power supply to the Safety System. 3. Restart the system 32590, Firmware reflash started Description A required update of the arg firmware in drive module arg has started. File: [ arg ]. Recommended actions Wait for the reflash to complete, this will take approximately 3.5 minutes. 32591, Firmware reflash completed Description The update of arg firmware in drive module arg has sucessfully completed. Recommended actions No action required 32592, Firmware reflash failed Description The update of arg firmware in drive module arg has failed. Recommended actions 1. Check other error messages for detailed explanation. 2. Reinstall the system. 32593, Firmware file corrupt Description The update of arg firmware in drive module arg has failed. The firmware file [ arg ] is corrupt. Recommended actions Reinstall the system 32594, Firmware file not found Description The update of arg firmware in drive module arg has failed. The firmware file [ arg ] is not found. Recommended actions Reinstall the system 32601, Interbus master/slave board is missing Description The Interbus master/slave board does not work. Consequences No communication on the Interbus is possible. Probable causes The Interbus master/slave board is either malfunctioning or missing. Recommended actions 1) Make sure a Interbus master/slave board is installed. 2) Replace the board if faulty. 32651, Serial port hardware is not accessible Description The system has tried to address the serial port arg , and failed. Consequences The optional serial port hardware can not be accessed. The connector and the physical channel using the connector will not be available for use. Probable causes The serial port hardware is missing or malfunctioning. Recommended actions 1) Make sure the required serial port hardware has been correctly installed and is not faulty. 2) Replace the serial port hardware. 33503, Revolution counter update failure Description Update of the revolution counter for joint arg failed. Consequences Joint not synchronized Probable causes 1. Joint missing or not active 2. Measurement system error Recommended actions 1. Check if joint active 2. Check configuration files 3. Check measurement system 6 Trouble shooting by Event log 150 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 33601, Fieldbus Adapter is missing Description The Fieldbus Adapter is missing. Consequences No communication with the Fieldbus Adapter is possible. Probable causes The Fieldbus Adapter is either malfunctioning or missing. Recommended actions 1. Make sure a Fieldbus Adapter is installed. 2. Replace the module if faulty. 34100, Drive system not supported Description The configured drive system in drive module arg is not of type Drive System '04. Consequences The system goes to System Failure state. Probable causes 1. Wrong drive module key used, i.e., the configuration does not match hardware. 2. Wrong hardware used in the system. Recommended actions 1. Reinstall the system with a drive module key that matches the hardware. 2. Replace the drive module with one that supports Drive System '04. 34101, Drive system not supported Description The configured drive system in drive module arg is not of type Drive System '09. Consequences The system goes to System Failure state. Probable causes 1. Wrong drive module key used, i.e., the configuration does not match hardware. 2. Wrong hardware used in the system. Recommended actions 1. Reinstall the system with a drive module key that matches the hardware. 2. Replace the drive module with one that supports Drive System '09. 34200, Lost communication with all drive units Description In drive module arg , the axis computer has lost communication with all drive units. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. Probable causes Communication problem between drive units and the axis computer. Recommended actions 1) Check that all cables are properly connected. 2) Check that the drive units have logic power. 3) Check/replace Ethernet cables. 4) Check for other hardware eventlog messages. 5) Check the event log for power supply unit error messages. 6) Check the cabling between the power supply unit and the drive unit. 7) Check the 24V output from the power supply unit. 34201, Connected drive unit not configured Description The drive unit in drive module arg with drive unit position arg is connected but not used in the configuration. Consequences Operation will be possible, but the extra drive unit will not be used. Probable causes The drive unit is not used in the configuration. Recommended actions 1) Remove extra drive unit if not needed. 2) Reinstall the system with a drive module key supporting the extra drive unit. 34202, Lost communication with drive unit Description In drive module arg , the axis computer has lost communication with the drive unit at unit position arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. Probable causes Communication problem between the drive unit and the axis computer. Recommended actions 1) Check that all cables are properly connected. 2) Check that the drive unit has logic power. 3) Check/replace Ethernet cables. 4) Check for other hardware eventlog messages. 5) Check the event log for power supply unit error messages. 6) Check the cabling between the power supply unit and the drive unit. 7) Check the 24V output from the power supply unit.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	152	6 Trouble shooting by Event log 149 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Reinstall the system 32585, No Safety System Found By Axis Computer Description Axis computer failed to detect the Safety System. Recommended actions 1. Check communication cables between the axis computer and the Safety System. 2. Check power supply to the Safety System. 3. Restart the system 32590, Firmware reflash started Description A required update of the arg firmware in drive module arg has started. File: [ arg ]. Recommended actions Wait for the reflash to complete, this will take approximately 3.5 minutes. 32591, Firmware reflash completed Description The update of arg firmware in drive module arg has sucessfully completed. Recommended actions No action required 32592, Firmware reflash failed Description The update of arg firmware in drive module arg has failed. Recommended actions 1. Check other error messages for detailed explanation. 2. Reinstall the system. 32593, Firmware file corrupt Description The update of arg firmware in drive module arg has failed. The firmware file [ arg ] is corrupt. Recommended actions Reinstall the system 32594, Firmware file not found Description The update of arg firmware in drive module arg has failed. The firmware file [ arg ] is not found. Recommended actions Reinstall the system 32601, Interbus master/slave board is missing Description The Interbus master/slave board does not work. Consequences No communication on the Interbus is possible. Probable causes The Interbus master/slave board is either malfunctioning or missing. Recommended actions 1) Make sure a Interbus master/slave board is installed. 2) Replace the board if faulty. 32651, Serial port hardware is not accessible Description The system has tried to address the serial port arg , and failed. Consequences The optional serial port hardware can not be accessed. The connector and the physical channel using the connector will not be available for use. Probable causes The serial port hardware is missing or malfunctioning. Recommended actions 1) Make sure the required serial port hardware has been correctly installed and is not faulty. 2) Replace the serial port hardware. 33503, Revolution counter update failure Description Update of the revolution counter for joint arg failed. Consequences Joint not synchronized Probable causes 1. Joint missing or not active 2. Measurement system error Recommended actions 1. Check if joint active 2. Check configuration files 3. Check measurement system 6 Trouble shooting by Event log 150 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 33601, Fieldbus Adapter is missing Description The Fieldbus Adapter is missing. Consequences No communication with the Fieldbus Adapter is possible. Probable causes The Fieldbus Adapter is either malfunctioning or missing. Recommended actions 1. Make sure a Fieldbus Adapter is installed. 2. Replace the module if faulty. 34100, Drive system not supported Description The configured drive system in drive module arg is not of type Drive System '04. Consequences The system goes to System Failure state. Probable causes 1. Wrong drive module key used, i.e., the configuration does not match hardware. 2. Wrong hardware used in the system. Recommended actions 1. Reinstall the system with a drive module key that matches the hardware. 2. Replace the drive module with one that supports Drive System '04. 34101, Drive system not supported Description The configured drive system in drive module arg is not of type Drive System '09. Consequences The system goes to System Failure state. Probable causes 1. Wrong drive module key used, i.e., the configuration does not match hardware. 2. Wrong hardware used in the system. Recommended actions 1. Reinstall the system with a drive module key that matches the hardware. 2. Replace the drive module with one that supports Drive System '09. 34200, Lost communication with all drive units Description In drive module arg , the axis computer has lost communication with all drive units. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. Probable causes Communication problem between drive units and the axis computer. Recommended actions 1) Check that all cables are properly connected. 2) Check that the drive units have logic power. 3) Check/replace Ethernet cables. 4) Check for other hardware eventlog messages. 5) Check the event log for power supply unit error messages. 6) Check the cabling between the power supply unit and the drive unit. 7) Check the 24V output from the power supply unit. 34201, Connected drive unit not configured Description The drive unit in drive module arg with drive unit position arg is connected but not used in the configuration. Consequences Operation will be possible, but the extra drive unit will not be used. Probable causes The drive unit is not used in the configuration. Recommended actions 1) Remove extra drive unit if not needed. 2) Reinstall the system with a drive module key supporting the extra drive unit. 34202, Lost communication with drive unit Description In drive module arg , the axis computer has lost communication with the drive unit at unit position arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. Probable causes Communication problem between the drive unit and the axis computer. Recommended actions 1) Check that all cables are properly connected. 2) Check that the drive unit has logic power. 3) Check/replace Ethernet cables. 4) Check for other hardware eventlog messages. 5) Check the event log for power supply unit error messages. 6) Check the cabling between the power supply unit and the drive unit. 7) Check the 24V output from the power supply unit. 6 Trouble shooting by Event log 151 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 34203, Motor current too high Description The motor current is too high for joint arg , connected to drive module arg with the drive unit at unit position arg and node arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes 1) The motor configuration is incorrect. 2) The axis load may be too high or the motor may have stalled (maybe due to a collision). 3) The motor is too small for the drive unit. 4) Short circuit between motor phases or ground. Recommended actions 1) Check that the motor configuration is correct. 2) Check that the robot has not collided. 3) If possible, reduce the speed of the user program. 4) Check that the axis load is not too high for the motor. 5) Verify that the maximum motor current is not too small compared to the maximum current of the drive unit. 6) Check the motor cable and motor by measuring their resistance respectively. Disconnect before measuring. 34251, Incoming mains phase missing Description In drive module arg , the rectifier unit at drive unit position arg has detected a power loss in one phase. Consequences The system may stop with DC link too low voltage. Probable causes 1) Incoming mains voltage loss of one phase. 2) Some malfunction in cabling or internal 3-phase components. 3) The rectifier unit is faulty. Recommended actions 1) Check all incoming mains phases to the cabinet. 2) Check all internal 3-phase components (main switch, mains filter, fuse, contactors) and cabling in the drive module. 34252, Incoming mains missing Description In drive module arg , the rectifier unit at drive unit position arg has detected a mains voltage loss. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes 1) Incoming mains voltage loss. 2) Some malfunction in the cabling or in internal 3-phase components. 3) The rectifier unit is faulty. Recommended actions 1) Check the incoming mains voltage. 2) Check all the internal 3-phase components (main switch, mains filter, fuse, contactors) and cabling in the drive module. 34255, Rectifier temperature error Description In drive module arg , the rectifier unit at drive unit position arg has reached a too high temperature level. Consequences No operation will be possible until the rectifier has cooled down. The system goes to Motors Off state. Probable causes 1) The cooling fans may be faulty or the air flow may be obstructed. 2) The ambient temperature may be too high. 3) The system may be running with a too high torque for extended periods of time. Recommended actions 1) Verify that the fans are running and that the air flow is not obstructed. 2) Verify that the ambient temperature does not exceed the cabinet's temperature rating. 3) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration. 4) Reduce the static torque due to gravity or external forces. 34256, Rectifier temperature warning Description In drive module arg , the rectifier unit at drive unit position arg is approaching a too high temperature level. Consequences It is possible to continue but the margin to maximum allowed temperature is too low to sustain long term operation. Probable causes 1) The cooling fans may be faulty or the air flow may be obstructed. 2) The ambient temperature may be too high. 3) The system may be running with a too high torque for extended periods of time. Recommended actions 1) Verify that the fans are running and that the air flow is not obstructed. 2) Verify that the ambient temperature does not exceed the cabinet's temperature rating.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	153	6 Trouble shooting by Event log 150 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 33601, Fieldbus Adapter is missing Description The Fieldbus Adapter is missing. Consequences No communication with the Fieldbus Adapter is possible. Probable causes The Fieldbus Adapter is either malfunctioning or missing. Recommended actions 1. Make sure a Fieldbus Adapter is installed. 2. Replace the module if faulty. 34100, Drive system not supported Description The configured drive system in drive module arg is not of type Drive System '04. Consequences The system goes to System Failure state. Probable causes 1. Wrong drive module key used, i.e., the configuration does not match hardware. 2. Wrong hardware used in the system. Recommended actions 1. Reinstall the system with a drive module key that matches the hardware. 2. Replace the drive module with one that supports Drive System '04. 34101, Drive system not supported Description The configured drive system in drive module arg is not of type Drive System '09. Consequences The system goes to System Failure state. Probable causes 1. Wrong drive module key used, i.e., the configuration does not match hardware. 2. Wrong hardware used in the system. Recommended actions 1. Reinstall the system with a drive module key that matches the hardware. 2. Replace the drive module with one that supports Drive System '09. 34200, Lost communication with all drive units Description In drive module arg , the axis computer has lost communication with all drive units. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. Probable causes Communication problem between drive units and the axis computer. Recommended actions 1) Check that all cables are properly connected. 2) Check that the drive units have logic power. 3) Check/replace Ethernet cables. 4) Check for other hardware eventlog messages. 5) Check the event log for power supply unit error messages. 6) Check the cabling between the power supply unit and the drive unit. 7) Check the 24V output from the power supply unit. 34201, Connected drive unit not configured Description The drive unit in drive module arg with drive unit position arg is connected but not used in the configuration. Consequences Operation will be possible, but the extra drive unit will not be used. Probable causes The drive unit is not used in the configuration. Recommended actions 1) Remove extra drive unit if not needed. 2) Reinstall the system with a drive module key supporting the extra drive unit. 34202, Lost communication with drive unit Description In drive module arg , the axis computer has lost communication with the drive unit at unit position arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. Probable causes Communication problem between the drive unit and the axis computer. Recommended actions 1) Check that all cables are properly connected. 2) Check that the drive unit has logic power. 3) Check/replace Ethernet cables. 4) Check for other hardware eventlog messages. 5) Check the event log for power supply unit error messages. 6) Check the cabling between the power supply unit and the drive unit. 7) Check the 24V output from the power supply unit. 6 Trouble shooting by Event log 151 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 34203, Motor current too high Description The motor current is too high for joint arg , connected to drive module arg with the drive unit at unit position arg and node arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes 1) The motor configuration is incorrect. 2) The axis load may be too high or the motor may have stalled (maybe due to a collision). 3) The motor is too small for the drive unit. 4) Short circuit between motor phases or ground. Recommended actions 1) Check that the motor configuration is correct. 2) Check that the robot has not collided. 3) If possible, reduce the speed of the user program. 4) Check that the axis load is not too high for the motor. 5) Verify that the maximum motor current is not too small compared to the maximum current of the drive unit. 6) Check the motor cable and motor by measuring their resistance respectively. Disconnect before measuring. 34251, Incoming mains phase missing Description In drive module arg , the rectifier unit at drive unit position arg has detected a power loss in one phase. Consequences The system may stop with DC link too low voltage. Probable causes 1) Incoming mains voltage loss of one phase. 2) Some malfunction in cabling or internal 3-phase components. 3) The rectifier unit is faulty. Recommended actions 1) Check all incoming mains phases to the cabinet. 2) Check all internal 3-phase components (main switch, mains filter, fuse, contactors) and cabling in the drive module. 34252, Incoming mains missing Description In drive module arg , the rectifier unit at drive unit position arg has detected a mains voltage loss. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes 1) Incoming mains voltage loss. 2) Some malfunction in the cabling or in internal 3-phase components. 3) The rectifier unit is faulty. Recommended actions 1) Check the incoming mains voltage. 2) Check all the internal 3-phase components (main switch, mains filter, fuse, contactors) and cabling in the drive module. 34255, Rectifier temperature error Description In drive module arg , the rectifier unit at drive unit position arg has reached a too high temperature level. Consequences No operation will be possible until the rectifier has cooled down. The system goes to Motors Off state. Probable causes 1) The cooling fans may be faulty or the air flow may be obstructed. 2) The ambient temperature may be too high. 3) The system may be running with a too high torque for extended periods of time. Recommended actions 1) Verify that the fans are running and that the air flow is not obstructed. 2) Verify that the ambient temperature does not exceed the cabinet's temperature rating. 3) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration. 4) Reduce the static torque due to gravity or external forces. 34256, Rectifier temperature warning Description In drive module arg , the rectifier unit at drive unit position arg is approaching a too high temperature level. Consequences It is possible to continue but the margin to maximum allowed temperature is too low to sustain long term operation. Probable causes 1) The cooling fans may be faulty or the air flow may be obstructed. 2) The ambient temperature may be too high. 3) The system may be running with a too high torque for extended periods of time. Recommended actions 1) Verify that the fans are running and that the air flow is not obstructed. 2) Verify that the ambient temperature does not exceed the cabinet's temperature rating. 6 Trouble shooting by Event log 152 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 3) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration. 4) Reduce the static torque due to gravity or external forces. 34257, Open circuit in bleeder resistor circuit Description In drive module arg , the bleeder resistor connected to the rectifier unit at drive unit position arg has too high resistance (open circuit). Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. WARNING HIGH VOLTAGE: THE DC LINK WILL NOT BE DISCHARGED WHEN THE SYSTEM IS POWERED OFF. Probable causes This may be caused by a faulty bleeder resistor cable or a faulty bleeder resistor. Recommended actions WARNING HIGH VOLTAGE CAN BE PRESENT. 1) Make sure the bleeder resistor cable is properly connected to the rectifier unit. 2) Disconnect the bleeder and check the cable and measure the bleeder resistance. The expected resistance should be approximately arg ohms. 34258, Short circuit in bleeder resistor circuit Description In drive module arg , the bleeder resistor connected to the rectifier unit at drive unit position arg is indicating a short circuit. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. WARNING HIGH VOLTAGE: THE DC LINK WILL NOT BE DISCHARGED WHEN THE SYSTEM IS POWERED OFF. Probable causes This may be caused by a faulty bleeder resistor cable or a faulty bleeder resistor. Recommended actions WARNING HIGH VOLTAGE CAN BE PRESENT. 1) Make sure the bleeder resistor cable is correctly connected to the rectifier unit. 2) Disconnect the bleeder and check the cable and measure the bleeder resistance. The expected resistance should be approximately arg ohms. 3) Check for bleeder short circuit against ground. 34261, Rectifier startup error Description In drive module arg , the inrush control relay in the rectifier unit at drive unit position arg indicates an error. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes This may be caused by a faulty rectifier inrush control relay. Recommended actions Restart the system and try again. If the problem remains then replace the unit. 34262, Incoming mains frequency warning Description In drive module arg , the incoming mains voltage has wrong frequency. The rectifier unit at drive unit position arg has reported the problem. Consequences The system may stop with DC link voltage too low. Probable causes 1) The incoming mains frequency is not within specification. 2) Short circuit between motor phases or ground. Recommended actions 1) Check and adjust incoming mains frequency. 2) Check the motor cable and motor by measuring their resistance respectively. Disconnect before measuring. 34263, Rectifier startup error Description In drive module arg , the inrush control resistor in the rectifier unit at drive unit position arg has too high resistance (open circuit). Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes This may be caused by a faulty rectifier inrush control resistor. Recommended actions Restart the system and try again. If the problem remains then replace the unit. 34264, Rectifier inrush limitation active in Motors On Description In drive module arg , the inrush control resistor in the rectifier unit at drive unit position arg is wrongly engaged. Consequences The system goes to Motors Off state to protect the hardware.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	154	6 Trouble shooting by Event log 151 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 34203, Motor current too high Description The motor current is too high for joint arg , connected to drive module arg with the drive unit at unit position arg and node arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes 1) The motor configuration is incorrect. 2) The axis load may be too high or the motor may have stalled (maybe due to a collision). 3) The motor is too small for the drive unit. 4) Short circuit between motor phases or ground. Recommended actions 1) Check that the motor configuration is correct. 2) Check that the robot has not collided. 3) If possible, reduce the speed of the user program. 4) Check that the axis load is not too high for the motor. 5) Verify that the maximum motor current is not too small compared to the maximum current of the drive unit. 6) Check the motor cable and motor by measuring their resistance respectively. Disconnect before measuring. 34251, Incoming mains phase missing Description In drive module arg , the rectifier unit at drive unit position arg has detected a power loss in one phase. Consequences The system may stop with DC link too low voltage. Probable causes 1) Incoming mains voltage loss of one phase. 2) Some malfunction in cabling or internal 3-phase components. 3) The rectifier unit is faulty. Recommended actions 1) Check all incoming mains phases to the cabinet. 2) Check all internal 3-phase components (main switch, mains filter, fuse, contactors) and cabling in the drive module. 34252, Incoming mains missing Description In drive module arg , the rectifier unit at drive unit position arg has detected a mains voltage loss. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes 1) Incoming mains voltage loss. 2) Some malfunction in the cabling or in internal 3-phase components. 3) The rectifier unit is faulty. Recommended actions 1) Check the incoming mains voltage. 2) Check all the internal 3-phase components (main switch, mains filter, fuse, contactors) and cabling in the drive module. 34255, Rectifier temperature error Description In drive module arg , the rectifier unit at drive unit position arg has reached a too high temperature level. Consequences No operation will be possible until the rectifier has cooled down. The system goes to Motors Off state. Probable causes 1) The cooling fans may be faulty or the air flow may be obstructed. 2) The ambient temperature may be too high. 3) The system may be running with a too high torque for extended periods of time. Recommended actions 1) Verify that the fans are running and that the air flow is not obstructed. 2) Verify that the ambient temperature does not exceed the cabinet's temperature rating. 3) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration. 4) Reduce the static torque due to gravity or external forces. 34256, Rectifier temperature warning Description In drive module arg , the rectifier unit at drive unit position arg is approaching a too high temperature level. Consequences It is possible to continue but the margin to maximum allowed temperature is too low to sustain long term operation. Probable causes 1) The cooling fans may be faulty or the air flow may be obstructed. 2) The ambient temperature may be too high. 3) The system may be running with a too high torque for extended periods of time. Recommended actions 1) Verify that the fans are running and that the air flow is not obstructed. 2) Verify that the ambient temperature does not exceed the cabinet's temperature rating. 6 Trouble shooting by Event log 152 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 3) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration. 4) Reduce the static torque due to gravity or external forces. 34257, Open circuit in bleeder resistor circuit Description In drive module arg , the bleeder resistor connected to the rectifier unit at drive unit position arg has too high resistance (open circuit). Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. WARNING HIGH VOLTAGE: THE DC LINK WILL NOT BE DISCHARGED WHEN THE SYSTEM IS POWERED OFF. Probable causes This may be caused by a faulty bleeder resistor cable or a faulty bleeder resistor. Recommended actions WARNING HIGH VOLTAGE CAN BE PRESENT. 1) Make sure the bleeder resistor cable is properly connected to the rectifier unit. 2) Disconnect the bleeder and check the cable and measure the bleeder resistance. The expected resistance should be approximately arg ohms. 34258, Short circuit in bleeder resistor circuit Description In drive module arg , the bleeder resistor connected to the rectifier unit at drive unit position arg is indicating a short circuit. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. WARNING HIGH VOLTAGE: THE DC LINK WILL NOT BE DISCHARGED WHEN THE SYSTEM IS POWERED OFF. Probable causes This may be caused by a faulty bleeder resistor cable or a faulty bleeder resistor. Recommended actions WARNING HIGH VOLTAGE CAN BE PRESENT. 1) Make sure the bleeder resistor cable is correctly connected to the rectifier unit. 2) Disconnect the bleeder and check the cable and measure the bleeder resistance. The expected resistance should be approximately arg ohms. 3) Check for bleeder short circuit against ground. 34261, Rectifier startup error Description In drive module arg , the inrush control relay in the rectifier unit at drive unit position arg indicates an error. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes This may be caused by a faulty rectifier inrush control relay. Recommended actions Restart the system and try again. If the problem remains then replace the unit. 34262, Incoming mains frequency warning Description In drive module arg , the incoming mains voltage has wrong frequency. The rectifier unit at drive unit position arg has reported the problem. Consequences The system may stop with DC link voltage too low. Probable causes 1) The incoming mains frequency is not within specification. 2) Short circuit between motor phases or ground. Recommended actions 1) Check and adjust incoming mains frequency. 2) Check the motor cable and motor by measuring their resistance respectively. Disconnect before measuring. 34263, Rectifier startup error Description In drive module arg , the inrush control resistor in the rectifier unit at drive unit position arg has too high resistance (open circuit). Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes This may be caused by a faulty rectifier inrush control resistor. Recommended actions Restart the system and try again. If the problem remains then replace the unit. 34264, Rectifier inrush limitation active in Motors On Description In drive module arg , the inrush control resistor in the rectifier unit at drive unit position arg is wrongly engaged. Consequences The system goes to Motors Off state to protect the hardware. 6 Trouble shooting by Event log 153 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes This error occur when the DC link voltage becomes too low and all mains phases are missing. Recommended actions 1) Check the hardware eventlog for other errors. 2) Check incoming mains voltage. 3) Check that the correct voltage is selected with jumpers on the transformer (optional). 4) Check all internal 3-phase components (main switch, mains filter, fuse, contactors) and cabling in the drive module. 34265, DC link short circuit error Description In drive module arg , the DC link in the rectifier unit at drive unit position arg is short circuit. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes 1) DC link cables for an additional drive unit is damaged or wrongly connected. 2) Internal error in rectifier unit or drive unit. Recommended actions Check DC link cables and connectors. 34266, Rectifier inrush limitation and bleeder active Description In drive module arg , with rectifier unit at drive unit position arg , the inrush control resistor is active at the same time as the bleeder resistor is active. The inrush control resistor is located in the rectifier unit. The bleeder resistor is connected to the rectifier unit or the drive unit with embedded rectifier. Consequences The system goes to Motors Off state to protect the hardware. Probable causes This problem is most likely to occur when the incoming mains voltage is too high to the rectifier. Recommended actions 1) Check that the incoming mains voltage is according to specification for the drive unit. 2) Check that the correct voltage is selected with jumpers on the transformer (optional). 34267, Too many rectifiers connected Description In drive module arg the system has detected more rectifers than the system can handle. The limit was reached when drive unit at unit position arg was detected. Consequences No operation will be possible until the fault is corrected. The system goes to System Failure state. Probable causes 1) Too many drive unit that are equippted with rectifiers are connected. 2) Recommended actions 1) Verify that the proper drive units types are connected to the drive unit communication link. 2) Disconnect unused drive unit(s). 34300, Unknown drive unit type Description In drive module arg , the drive unit at unit position arg has an unknown hardware identity arg . Consequences No operation will be possible until the fault is corrected. The system goes to System Failure state. Probable causes The drive unit is either unsupported or faulty. Recommended actions 1) Verify that the drive unit is supported by the RobotWare version. Upgrade RobotWare if needed. 2) Replace drive unit. 34303, Motor current warning Description For joint arg , the current controller detected a too large torque current deviation for the motor. The joint is connected to drive module arg in the drive unit at unit position arg and node arg . Consequences Operation will be possible but system is close to a stopping error. Probable causes 1) The motor data in the configuration files may be wrong. 2) The motor cables are not correctly connected or damaged. 3) Short circuit in motor cable between phase to phase or phase to ground. 4) The DC link voltage may be too low. 5) The incoming mains voltage is not within specification.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	155	6 Trouble shooting by Event log 152 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 3) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration. 4) Reduce the static torque due to gravity or external forces. 34257, Open circuit in bleeder resistor circuit Description In drive module arg , the bleeder resistor connected to the rectifier unit at drive unit position arg has too high resistance (open circuit). Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. WARNING HIGH VOLTAGE: THE DC LINK WILL NOT BE DISCHARGED WHEN THE SYSTEM IS POWERED OFF. Probable causes This may be caused by a faulty bleeder resistor cable or a faulty bleeder resistor. Recommended actions WARNING HIGH VOLTAGE CAN BE PRESENT. 1) Make sure the bleeder resistor cable is properly connected to the rectifier unit. 2) Disconnect the bleeder and check the cable and measure the bleeder resistance. The expected resistance should be approximately arg ohms. 34258, Short circuit in bleeder resistor circuit Description In drive module arg , the bleeder resistor connected to the rectifier unit at drive unit position arg is indicating a short circuit. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. WARNING HIGH VOLTAGE: THE DC LINK WILL NOT BE DISCHARGED WHEN THE SYSTEM IS POWERED OFF. Probable causes This may be caused by a faulty bleeder resistor cable or a faulty bleeder resistor. Recommended actions WARNING HIGH VOLTAGE CAN BE PRESENT. 1) Make sure the bleeder resistor cable is correctly connected to the rectifier unit. 2) Disconnect the bleeder and check the cable and measure the bleeder resistance. The expected resistance should be approximately arg ohms. 3) Check for bleeder short circuit against ground. 34261, Rectifier startup error Description In drive module arg , the inrush control relay in the rectifier unit at drive unit position arg indicates an error. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes This may be caused by a faulty rectifier inrush control relay. Recommended actions Restart the system and try again. If the problem remains then replace the unit. 34262, Incoming mains frequency warning Description In drive module arg , the incoming mains voltage has wrong frequency. The rectifier unit at drive unit position arg has reported the problem. Consequences The system may stop with DC link voltage too low. Probable causes 1) The incoming mains frequency is not within specification. 2) Short circuit between motor phases or ground. Recommended actions 1) Check and adjust incoming mains frequency. 2) Check the motor cable and motor by measuring their resistance respectively. Disconnect before measuring. 34263, Rectifier startup error Description In drive module arg , the inrush control resistor in the rectifier unit at drive unit position arg has too high resistance (open circuit). Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes This may be caused by a faulty rectifier inrush control resistor. Recommended actions Restart the system and try again. If the problem remains then replace the unit. 34264, Rectifier inrush limitation active in Motors On Description In drive module arg , the inrush control resistor in the rectifier unit at drive unit position arg is wrongly engaged. Consequences The system goes to Motors Off state to protect the hardware. 6 Trouble shooting by Event log 153 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes This error occur when the DC link voltage becomes too low and all mains phases are missing. Recommended actions 1) Check the hardware eventlog for other errors. 2) Check incoming mains voltage. 3) Check that the correct voltage is selected with jumpers on the transformer (optional). 4) Check all internal 3-phase components (main switch, mains filter, fuse, contactors) and cabling in the drive module. 34265, DC link short circuit error Description In drive module arg , the DC link in the rectifier unit at drive unit position arg is short circuit. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes 1) DC link cables for an additional drive unit is damaged or wrongly connected. 2) Internal error in rectifier unit or drive unit. Recommended actions Check DC link cables and connectors. 34266, Rectifier inrush limitation and bleeder active Description In drive module arg , with rectifier unit at drive unit position arg , the inrush control resistor is active at the same time as the bleeder resistor is active. The inrush control resistor is located in the rectifier unit. The bleeder resistor is connected to the rectifier unit or the drive unit with embedded rectifier. Consequences The system goes to Motors Off state to protect the hardware. Probable causes This problem is most likely to occur when the incoming mains voltage is too high to the rectifier. Recommended actions 1) Check that the incoming mains voltage is according to specification for the drive unit. 2) Check that the correct voltage is selected with jumpers on the transformer (optional). 34267, Too many rectifiers connected Description In drive module arg the system has detected more rectifers than the system can handle. The limit was reached when drive unit at unit position arg was detected. Consequences No operation will be possible until the fault is corrected. The system goes to System Failure state. Probable causes 1) Too many drive unit that are equippted with rectifiers are connected. 2) Recommended actions 1) Verify that the proper drive units types are connected to the drive unit communication link. 2) Disconnect unused drive unit(s). 34300, Unknown drive unit type Description In drive module arg , the drive unit at unit position arg has an unknown hardware identity arg . Consequences No operation will be possible until the fault is corrected. The system goes to System Failure state. Probable causes The drive unit is either unsupported or faulty. Recommended actions 1) Verify that the drive unit is supported by the RobotWare version. Upgrade RobotWare if needed. 2) Replace drive unit. 34303, Motor current warning Description For joint arg , the current controller detected a too large torque current deviation for the motor. The joint is connected to drive module arg in the drive unit at unit position arg and node arg . Consequences Operation will be possible but system is close to a stopping error. Probable causes 1) The motor data in the configuration files may be wrong. 2) The motor cables are not correctly connected or damaged. 3) Short circuit in motor cable between phase to phase or phase to ground. 4) The DC link voltage may be too low. 5) The incoming mains voltage is not within specification. 6 Trouble shooting by Event log 154 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Verify that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Verify that the motor cables are not damaged or badly connected. 3) Verify that the motor cables has no short circuits internally or to ground. 4) Verify that no DC link errors are present in the event log. 5) Verify that the incoming mains voltage is within the specification. 34304, Motor current warning Description For joint arg , the current controller detected a too large current deviation for the motor. The joint is connected to drive module arg in the drive unit at unit position arg and node arg . Consequences Operation will be possible but system is close to a stopping error. Probable causes 1) The motor data in the configuration files may be wrong. 2) The motor cables are not correctly connected or damaged. 3) Short circuit in motor cable between phase to phase or phase to ground. 4) The DC link voltage may be too low. 5) The incoming mains voltage is not within specification. Recommended actions 1) Verify that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Verify that the motor cables are not damaged or badly connected. 3) Verify that the motor cables has no short circuits internally or to ground. 4) Verify that no DC link errors are present in the event log. 5) Verify that the incoming mains voltage is within the specification. 34306, Drive unit temperature error Description The drive unit for joint arg has reached a too high temperature level. The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes 1) The cooling fans may be faulty or the air flow may be obstructed. 2) The cooling fins are covered by dust reducing the cooling effect. 3) The ambient temperature may be too high. 4) The joint may be running with a too high torque for extended periods of time. Recommended actions 1) Verify that the fans are running and that the air flow is not obstructed. 2) Clean the cooling fins. 3) Verify that the ambient temperature does not exceed the cabinet's temperature rating. 4) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration. 5) Reduce the static torque due to gravity or external forces. 34307, Drive unit temperature warning Description The drive unit for joint arg is approaching a too high temperature level. The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences It is possible to continue but the margin to maximum allowed temperature is too low to sustain long term operation. Probable causes 1) The cooling fans may be faulty or the air flow may be obstructed. 2) The cooling fins are covered by dust reducing the cooling effect. 3) The ambient temperature may be too high. 4) The joint may be running with a too high torque for extended periods of time. Recommended actions 1) Verify that the fans are running and that the air flow is not obstructed. 2) Clean the cooling fins. 3) Verify that the ambient temperature does not exceed the cabinet's temperature rating. 4) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration. 5) Reduce the static torque due to gravity or external forces. 34308, Drive unit critical temperature error Description The drive unit for joint arg has reached a critical high temperature level. The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. Probable causes 1) The cooling fans may be faulty or the air flow may be obstructed. 2) The cooling fins are covered by dust reducing the cooling effect. 3) The ambient temperature may be too high. 4) The joint may be running with a too high torque for extended periods of time.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	156	6 Trouble shooting by Event log 153 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes This error occur when the DC link voltage becomes too low and all mains phases are missing. Recommended actions 1) Check the hardware eventlog for other errors. 2) Check incoming mains voltage. 3) Check that the correct voltage is selected with jumpers on the transformer (optional). 4) Check all internal 3-phase components (main switch, mains filter, fuse, contactors) and cabling in the drive module. 34265, DC link short circuit error Description In drive module arg , the DC link in the rectifier unit at drive unit position arg is short circuit. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes 1) DC link cables for an additional drive unit is damaged or wrongly connected. 2) Internal error in rectifier unit or drive unit. Recommended actions Check DC link cables and connectors. 34266, Rectifier inrush limitation and bleeder active Description In drive module arg , with rectifier unit at drive unit position arg , the inrush control resistor is active at the same time as the bleeder resistor is active. The inrush control resistor is located in the rectifier unit. The bleeder resistor is connected to the rectifier unit or the drive unit with embedded rectifier. Consequences The system goes to Motors Off state to protect the hardware. Probable causes This problem is most likely to occur when the incoming mains voltage is too high to the rectifier. Recommended actions 1) Check that the incoming mains voltage is according to specification for the drive unit. 2) Check that the correct voltage is selected with jumpers on the transformer (optional). 34267, Too many rectifiers connected Description In drive module arg the system has detected more rectifers than the system can handle. The limit was reached when drive unit at unit position arg was detected. Consequences No operation will be possible until the fault is corrected. The system goes to System Failure state. Probable causes 1) Too many drive unit that are equippted with rectifiers are connected. 2) Recommended actions 1) Verify that the proper drive units types are connected to the drive unit communication link. 2) Disconnect unused drive unit(s). 34300, Unknown drive unit type Description In drive module arg , the drive unit at unit position arg has an unknown hardware identity arg . Consequences No operation will be possible until the fault is corrected. The system goes to System Failure state. Probable causes The drive unit is either unsupported or faulty. Recommended actions 1) Verify that the drive unit is supported by the RobotWare version. Upgrade RobotWare if needed. 2) Replace drive unit. 34303, Motor current warning Description For joint arg , the current controller detected a too large torque current deviation for the motor. The joint is connected to drive module arg in the drive unit at unit position arg and node arg . Consequences Operation will be possible but system is close to a stopping error. Probable causes 1) The motor data in the configuration files may be wrong. 2) The motor cables are not correctly connected or damaged. 3) Short circuit in motor cable between phase to phase or phase to ground. 4) The DC link voltage may be too low. 5) The incoming mains voltage is not within specification. 6 Trouble shooting by Event log 154 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Verify that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Verify that the motor cables are not damaged or badly connected. 3) Verify that the motor cables has no short circuits internally or to ground. 4) Verify that no DC link errors are present in the event log. 5) Verify that the incoming mains voltage is within the specification. 34304, Motor current warning Description For joint arg , the current controller detected a too large current deviation for the motor. The joint is connected to drive module arg in the drive unit at unit position arg and node arg . Consequences Operation will be possible but system is close to a stopping error. Probable causes 1) The motor data in the configuration files may be wrong. 2) The motor cables are not correctly connected or damaged. 3) Short circuit in motor cable between phase to phase or phase to ground. 4) The DC link voltage may be too low. 5) The incoming mains voltage is not within specification. Recommended actions 1) Verify that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Verify that the motor cables are not damaged or badly connected. 3) Verify that the motor cables has no short circuits internally or to ground. 4) Verify that no DC link errors are present in the event log. 5) Verify that the incoming mains voltage is within the specification. 34306, Drive unit temperature error Description The drive unit for joint arg has reached a too high temperature level. The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes 1) The cooling fans may be faulty or the air flow may be obstructed. 2) The cooling fins are covered by dust reducing the cooling effect. 3) The ambient temperature may be too high. 4) The joint may be running with a too high torque for extended periods of time. Recommended actions 1) Verify that the fans are running and that the air flow is not obstructed. 2) Clean the cooling fins. 3) Verify that the ambient temperature does not exceed the cabinet's temperature rating. 4) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration. 5) Reduce the static torque due to gravity or external forces. 34307, Drive unit temperature warning Description The drive unit for joint arg is approaching a too high temperature level. The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences It is possible to continue but the margin to maximum allowed temperature is too low to sustain long term operation. Probable causes 1) The cooling fans may be faulty or the air flow may be obstructed. 2) The cooling fins are covered by dust reducing the cooling effect. 3) The ambient temperature may be too high. 4) The joint may be running with a too high torque for extended periods of time. Recommended actions 1) Verify that the fans are running and that the air flow is not obstructed. 2) Clean the cooling fins. 3) Verify that the ambient temperature does not exceed the cabinet's temperature rating. 4) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration. 5) Reduce the static torque due to gravity or external forces. 34308, Drive unit critical temperature error Description The drive unit for joint arg has reached a critical high temperature level. The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. Probable causes 1) The cooling fans may be faulty or the air flow may be obstructed. 2) The cooling fins are covered by dust reducing the cooling effect. 3) The ambient temperature may be too high. 4) The joint may be running with a too high torque for extended periods of time. 6 Trouble shooting by Event log 155 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Verify that the fans are running and that the air flow is not obstructed. 2) Clean the cooling fins. 3) Verify that the ambient temperature does not exceed the cabinet's temperature rating. 4) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration. 5) Reduce the static torque due to gravity or external forces. 34309, Drive transistor current too high Description The drive unit transistor current is too high for joint arg . The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes 1) The motor configuration is incorrect. 2) The axis load may be too high or the motor may have stalled (maybe due to a collision). 3) Short circuit between motor phases or ground. Recommended actions 1) Check that the motor configuration is correct. 2) Check that the robot has not collided. 3) If possible, reduce the speed of the user program. 4) Check that the axis load is not too high for the drive unit. 5) Check the motor cable and motor by measuring their resistance respectively. Disconnect before measuring. 34311, Drive inverter saturated warning Description The drive unit for joint arg has reached maximum output voltage. The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences Operation will be possible but system is close to a stopping error. Probable causes 1) The motor is not properly connected to the drive unit. 2) The motor data in the configuration is not correct. 3) The DC link voltage is too low. 4) Short circuit between motor phases or ground. Recommended actions 1) Check motor cables and connectors. 2) Check configuration of motor parameters. 3) Check for other hardware eventlog messages. 4) Check incoming mains voltage to the rectifier unit. 5) Check the motor cable and motor by measuring their resistance respectively. Disconnect before measuring. 34312, Missing drive unit Description For joint arg , the system cannot find configured drive unit. The joint is configured for drive module arg , in the drive unit at unit position arg . Consequences The system goes to System Failure state. Probable causes A joint is configured but drive unit is not found. Recommended actions 1) Verify that the drive module contains the drive unit for the configured joint. 2) Verify that the configuration for the drive unit position is correct. 3) Verify that the cables between drive units are correctly inserted in the correct connector position. 4) If the cable is correctly connected, then it may be damaged and should be replaced. 5) Check the event log for power supply unit error messages. 6) Check the cabling between the power supply unit and the drive unit. 7) Check the 24V output from the power supply unit. 34313, Wrong type of drive unit Description In drive module arg , the hardware identity for drive unit at unit position arg is different from the one specified in the configuration. Installed drive unit hardware identity is arg , and the configured identity is arg . Consequences No operation will be possible until the fault is corrected. The system goes to System Failure state. Probable causes The drive unit type does not match the one specified in the installation key. Recommended actions 1) Verify that the drive unit positions are correct, i.e., the Ethernet cables are correctly connected. 2) Verify that the drive module key match the installed hardware. 3) Replace the drive unit with the one specified in the drive module key. 34314, Missing drive unit node Description For joint arg , the drive unit does not support the node number configured. The joint is configured for drive module arg , in the drive unit at unit position arg with node arg .
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	157	6 Trouble shooting by Event log 154 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Verify that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Verify that the motor cables are not damaged or badly connected. 3) Verify that the motor cables has no short circuits internally or to ground. 4) Verify that no DC link errors are present in the event log. 5) Verify that the incoming mains voltage is within the specification. 34304, Motor current warning Description For joint arg , the current controller detected a too large current deviation for the motor. The joint is connected to drive module arg in the drive unit at unit position arg and node arg . Consequences Operation will be possible but system is close to a stopping error. Probable causes 1) The motor data in the configuration files may be wrong. 2) The motor cables are not correctly connected or damaged. 3) Short circuit in motor cable between phase to phase or phase to ground. 4) The DC link voltage may be too low. 5) The incoming mains voltage is not within specification. Recommended actions 1) Verify that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Verify that the motor cables are not damaged or badly connected. 3) Verify that the motor cables has no short circuits internally or to ground. 4) Verify that no DC link errors are present in the event log. 5) Verify that the incoming mains voltage is within the specification. 34306, Drive unit temperature error Description The drive unit for joint arg has reached a too high temperature level. The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes 1) The cooling fans may be faulty or the air flow may be obstructed. 2) The cooling fins are covered by dust reducing the cooling effect. 3) The ambient temperature may be too high. 4) The joint may be running with a too high torque for extended periods of time. Recommended actions 1) Verify that the fans are running and that the air flow is not obstructed. 2) Clean the cooling fins. 3) Verify that the ambient temperature does not exceed the cabinet's temperature rating. 4) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration. 5) Reduce the static torque due to gravity or external forces. 34307, Drive unit temperature warning Description The drive unit for joint arg is approaching a too high temperature level. The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences It is possible to continue but the margin to maximum allowed temperature is too low to sustain long term operation. Probable causes 1) The cooling fans may be faulty or the air flow may be obstructed. 2) The cooling fins are covered by dust reducing the cooling effect. 3) The ambient temperature may be too high. 4) The joint may be running with a too high torque for extended periods of time. Recommended actions 1) Verify that the fans are running and that the air flow is not obstructed. 2) Clean the cooling fins. 3) Verify that the ambient temperature does not exceed the cabinet's temperature rating. 4) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration. 5) Reduce the static torque due to gravity or external forces. 34308, Drive unit critical temperature error Description The drive unit for joint arg has reached a critical high temperature level. The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. Probable causes 1) The cooling fans may be faulty or the air flow may be obstructed. 2) The cooling fins are covered by dust reducing the cooling effect. 3) The ambient temperature may be too high. 4) The joint may be running with a too high torque for extended periods of time. 6 Trouble shooting by Event log 155 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Verify that the fans are running and that the air flow is not obstructed. 2) Clean the cooling fins. 3) Verify that the ambient temperature does not exceed the cabinet's temperature rating. 4) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration. 5) Reduce the static torque due to gravity or external forces. 34309, Drive transistor current too high Description The drive unit transistor current is too high for joint arg . The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes 1) The motor configuration is incorrect. 2) The axis load may be too high or the motor may have stalled (maybe due to a collision). 3) Short circuit between motor phases or ground. Recommended actions 1) Check that the motor configuration is correct. 2) Check that the robot has not collided. 3) If possible, reduce the speed of the user program. 4) Check that the axis load is not too high for the drive unit. 5) Check the motor cable and motor by measuring their resistance respectively. Disconnect before measuring. 34311, Drive inverter saturated warning Description The drive unit for joint arg has reached maximum output voltage. The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences Operation will be possible but system is close to a stopping error. Probable causes 1) The motor is not properly connected to the drive unit. 2) The motor data in the configuration is not correct. 3) The DC link voltage is too low. 4) Short circuit between motor phases or ground. Recommended actions 1) Check motor cables and connectors. 2) Check configuration of motor parameters. 3) Check for other hardware eventlog messages. 4) Check incoming mains voltage to the rectifier unit. 5) Check the motor cable and motor by measuring their resistance respectively. Disconnect before measuring. 34312, Missing drive unit Description For joint arg , the system cannot find configured drive unit. The joint is configured for drive module arg , in the drive unit at unit position arg . Consequences The system goes to System Failure state. Probable causes A joint is configured but drive unit is not found. Recommended actions 1) Verify that the drive module contains the drive unit for the configured joint. 2) Verify that the configuration for the drive unit position is correct. 3) Verify that the cables between drive units are correctly inserted in the correct connector position. 4) If the cable is correctly connected, then it may be damaged and should be replaced. 5) Check the event log for power supply unit error messages. 6) Check the cabling between the power supply unit and the drive unit. 7) Check the 24V output from the power supply unit. 34313, Wrong type of drive unit Description In drive module arg , the hardware identity for drive unit at unit position arg is different from the one specified in the configuration. Installed drive unit hardware identity is arg , and the configured identity is arg . Consequences No operation will be possible until the fault is corrected. The system goes to System Failure state. Probable causes The drive unit type does not match the one specified in the installation key. Recommended actions 1) Verify that the drive unit positions are correct, i.e., the Ethernet cables are correctly connected. 2) Verify that the drive module key match the installed hardware. 3) Replace the drive unit with the one specified in the drive module key. 34314, Missing drive unit node Description For joint arg , the drive unit does not support the node number configured. The joint is configured for drive module arg , in the drive unit at unit position arg with node arg . 6 Trouble shooting by Event log 156 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences The system goes to System Failure state. Probable causes The configured drive unit node is not supported for the configured type of drive unit. Recommended actions Check the drive unit node number in the configuration. 34316, Motor current error Description For joint arg , the current controller detected a too large torque current deviation for the motor. The joint is connected to drive module arg in the drive unit at unit position arg and node arg . Consequences The system goes to Motors Off state. Probable causes 1) The motor data in the configuration files may be wrong. 2) The motor cables are not correctly connected or damaged. 3) Short circuit in motor cable between phase to phase or phase to ground. 4) The DC link voltage may be too low. 5) The incoming mains voltage is not within specification. Recommended actions 1) Verify that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Verify that the motor cables are not damaged or badly connected. 3) Verify that the motor cables has no short circuits internally or to ground. 4) Verify that no DC link errors are present in the event log. 5) Verify that the incoming mains voltage is within the specification. 34317, Motor current error Description For joint arg , the current controller detected a too large current deviation for the motor. The joint is connected to drive module arg in the drive unit at unit position arg and node arg . Consequences The system goes to Motors Off state. Probable causes 1) The motor data in the configuration files may be wrong. 2) The motor cables are not correctly connected or damaged. 3) Short circuit in motor cable between phase to phase or phase to ground. 4) The DC link voltage may be too low. 5) The incoming mains voltage is not within specification. Recommended actions 1) Verify that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Verify that the motor cables are not damaged or badly connected. 3) Verify that the motor cables has no short circuits internally or to ground. 4) Verify that no DC link errors are present in the event log. 5) Verify that the incoming mains voltage is within the specification. 34318, Drive inverter saturated error Description The drive unit for joint arg has reached maximum output voltage. The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences The system goes to Motors Off state Probable causes 1) The motor is not properly connected to the drive unit. 2) The motor data in the configuration is not correct. 3) The DC link voltage is too low. 4) Short circuit between motor phases or ground. Recommended actions 1) Check motor cables and connectors. 2) Check configuration of motor parameters. 3) Check for other hardware eventlog messages. 4) Check incoming mains voltage to the rectifier unit. 5) Check the motor cable and motor by measuring their resistance respectively. Disconnect before measuring. 34319, Drive unit critical error Description The drive unit for joint arg gives an unspecified error, but is likely due to over temperature or short circuit. The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. Probable causes 1) The cooling fans may be faulty or the air flow may be obstructed. 2) The cooling fins are covered by dust reducing the cooling effect. 3) The ambient temperature may be too high. 4) The joint may be running with a too high torque for extended periods of time. 5) Short circuit in cables or connectors between the phases or to ground. 6) Short circuit in motor between the phases or to ground.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	158	6 Trouble shooting by Event log 155 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Verify that the fans are running and that the air flow is not obstructed. 2) Clean the cooling fins. 3) Verify that the ambient temperature does not exceed the cabinet's temperature rating. 4) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration. 5) Reduce the static torque due to gravity or external forces. 34309, Drive transistor current too high Description The drive unit transistor current is too high for joint arg . The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes 1) The motor configuration is incorrect. 2) The axis load may be too high or the motor may have stalled (maybe due to a collision). 3) Short circuit between motor phases or ground. Recommended actions 1) Check that the motor configuration is correct. 2) Check that the robot has not collided. 3) If possible, reduce the speed of the user program. 4) Check that the axis load is not too high for the drive unit. 5) Check the motor cable and motor by measuring their resistance respectively. Disconnect before measuring. 34311, Drive inverter saturated warning Description The drive unit for joint arg has reached maximum output voltage. The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences Operation will be possible but system is close to a stopping error. Probable causes 1) The motor is not properly connected to the drive unit. 2) The motor data in the configuration is not correct. 3) The DC link voltage is too low. 4) Short circuit between motor phases or ground. Recommended actions 1) Check motor cables and connectors. 2) Check configuration of motor parameters. 3) Check for other hardware eventlog messages. 4) Check incoming mains voltage to the rectifier unit. 5) Check the motor cable and motor by measuring their resistance respectively. Disconnect before measuring. 34312, Missing drive unit Description For joint arg , the system cannot find configured drive unit. The joint is configured for drive module arg , in the drive unit at unit position arg . Consequences The system goes to System Failure state. Probable causes A joint is configured but drive unit is not found. Recommended actions 1) Verify that the drive module contains the drive unit for the configured joint. 2) Verify that the configuration for the drive unit position is correct. 3) Verify that the cables between drive units are correctly inserted in the correct connector position. 4) If the cable is correctly connected, then it may be damaged and should be replaced. 5) Check the event log for power supply unit error messages. 6) Check the cabling between the power supply unit and the drive unit. 7) Check the 24V output from the power supply unit. 34313, Wrong type of drive unit Description In drive module arg , the hardware identity for drive unit at unit position arg is different from the one specified in the configuration. Installed drive unit hardware identity is arg , and the configured identity is arg . Consequences No operation will be possible until the fault is corrected. The system goes to System Failure state. Probable causes The drive unit type does not match the one specified in the installation key. Recommended actions 1) Verify that the drive unit positions are correct, i.e., the Ethernet cables are correctly connected. 2) Verify that the drive module key match the installed hardware. 3) Replace the drive unit with the one specified in the drive module key. 34314, Missing drive unit node Description For joint arg , the drive unit does not support the node number configured. The joint is configured for drive module arg , in the drive unit at unit position arg with node arg . 6 Trouble shooting by Event log 156 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences The system goes to System Failure state. Probable causes The configured drive unit node is not supported for the configured type of drive unit. Recommended actions Check the drive unit node number in the configuration. 34316, Motor current error Description For joint arg , the current controller detected a too large torque current deviation for the motor. The joint is connected to drive module arg in the drive unit at unit position arg and node arg . Consequences The system goes to Motors Off state. Probable causes 1) The motor data in the configuration files may be wrong. 2) The motor cables are not correctly connected or damaged. 3) Short circuit in motor cable between phase to phase or phase to ground. 4) The DC link voltage may be too low. 5) The incoming mains voltage is not within specification. Recommended actions 1) Verify that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Verify that the motor cables are not damaged or badly connected. 3) Verify that the motor cables has no short circuits internally or to ground. 4) Verify that no DC link errors are present in the event log. 5) Verify that the incoming mains voltage is within the specification. 34317, Motor current error Description For joint arg , the current controller detected a too large current deviation for the motor. The joint is connected to drive module arg in the drive unit at unit position arg and node arg . Consequences The system goes to Motors Off state. Probable causes 1) The motor data in the configuration files may be wrong. 2) The motor cables are not correctly connected or damaged. 3) Short circuit in motor cable between phase to phase or phase to ground. 4) The DC link voltage may be too low. 5) The incoming mains voltage is not within specification. Recommended actions 1) Verify that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Verify that the motor cables are not damaged or badly connected. 3) Verify that the motor cables has no short circuits internally or to ground. 4) Verify that no DC link errors are present in the event log. 5) Verify that the incoming mains voltage is within the specification. 34318, Drive inverter saturated error Description The drive unit for joint arg has reached maximum output voltage. The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences The system goes to Motors Off state Probable causes 1) The motor is not properly connected to the drive unit. 2) The motor data in the configuration is not correct. 3) The DC link voltage is too low. 4) Short circuit between motor phases or ground. Recommended actions 1) Check motor cables and connectors. 2) Check configuration of motor parameters. 3) Check for other hardware eventlog messages. 4) Check incoming mains voltage to the rectifier unit. 5) Check the motor cable and motor by measuring their resistance respectively. Disconnect before measuring. 34319, Drive unit critical error Description The drive unit for joint arg gives an unspecified error, but is likely due to over temperature or short circuit. The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. Probable causes 1) The cooling fans may be faulty or the air flow may be obstructed. 2) The cooling fins are covered by dust reducing the cooling effect. 3) The ambient temperature may be too high. 4) The joint may be running with a too high torque for extended periods of time. 5) Short circuit in cables or connectors between the phases or to ground. 6) Short circuit in motor between the phases or to ground. 6 Trouble shooting by Event log 157 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Verify that the fans are running and that the air flow is not obstructed. 2) Clean the cooling fins. 3) Verify that the ambient temperature does not exceed the cabinet's temperature rating. 4) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration. 5) Reduce the static torque due to gravity or external forces. 6) Check/replace cables and connectors. 7) Check/replace motor. 34320, Too many drive nodes connected Description In drive module arg the system has detected more drive nodes than the system can handle. The limit was reached when drive unit at unit position arg was detected. Consequences No operation will be possible until the fault is corrected. The system goes to System Failure state. Probable causes 1) Too many drive units is connected to the drive unit communication link. 2) Too many drive unit that are equippted with many drive nodes are connected. Recommended actions 1) Verify that the proper drive units types are connected to the drive unit communication link. 2) Disconnect unused drive unit(s). 34400, DC link voltage too high Description In drive module arg , the drive unit at unit position arg has a DC link voltage that is too high. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. WARNING HIGH VOLTAGE: THE DC LINK MAY BE DISCHARGED VERY SLOWLY (APPROXIMATELY 1 HOUR) WHEN THE SYSTEM IS POWERED OFF. Probable causes 1) The bleeder resistor is not connected or faulty. 2) The user program may contain too much deceleration of the manipulator's axes. This fault is more likely if the system contains additional axes. Recommended actions WARNING HIGH VOLTAGE CAN BE PRESENT. 1) Make sure the bleeder resistor cable is properly connected to the rectifier unit. 2) Disconnect the bleeder and check the cable and measure the bleeder resistance. The expected resistance should be approximately arg ohms. 3) Rewrite the user program to reduce the amount of hard decelerations. 34401, DC link voltage too low warning Description In drive module arg , the drive unit at unit position arg has a DC link voltage that is close to minimum limit. Consequences Operation will be possible but the system is close to a stopping error. Probable causes The incoming mains voltage to the rectifier unit is out of specification. Recommended actions 1) Check for other hardware eventlog messages regarding mains voltage problem. 2) Check incoming mains voltage. 3) Check that the correct voltage is selected with jumpers on the transformer (optional). 4) Check all internal 3-phase components (main switch, mains filter, fuse, contactors) and cabling in the drive module. 34402, DC link voltage too low Description In drive module arg , the DC link voltage is too low for the drive unit at unit position arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes The incoming mains voltage to the rectifier unit is out of specification. Recommended actions 1) Check for other hardware eventlog messages regarding mains voltage problem. 2) Check incoming mains voltage. 3) Check that the correct voltage is selected with jumpers on the transformer (optional). 4) Check all internal 3-phase components (main switch, mains filter, fuse, contactors) and cabling in the drive module. 34404, DC link voltage is critically high Description In drive module arg , the drive unit at unit position arg has a DC link voltage that is critically high. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	159	6 Trouble shooting by Event log 156 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences The system goes to System Failure state. Probable causes The configured drive unit node is not supported for the configured type of drive unit. Recommended actions Check the drive unit node number in the configuration. 34316, Motor current error Description For joint arg , the current controller detected a too large torque current deviation for the motor. The joint is connected to drive module arg in the drive unit at unit position arg and node arg . Consequences The system goes to Motors Off state. Probable causes 1) The motor data in the configuration files may be wrong. 2) The motor cables are not correctly connected or damaged. 3) Short circuit in motor cable between phase to phase or phase to ground. 4) The DC link voltage may be too low. 5) The incoming mains voltage is not within specification. Recommended actions 1) Verify that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Verify that the motor cables are not damaged or badly connected. 3) Verify that the motor cables has no short circuits internally or to ground. 4) Verify that no DC link errors are present in the event log. 5) Verify that the incoming mains voltage is within the specification. 34317, Motor current error Description For joint arg , the current controller detected a too large current deviation for the motor. The joint is connected to drive module arg in the drive unit at unit position arg and node arg . Consequences The system goes to Motors Off state. Probable causes 1) The motor data in the configuration files may be wrong. 2) The motor cables are not correctly connected or damaged. 3) Short circuit in motor cable between phase to phase or phase to ground. 4) The DC link voltage may be too low. 5) The incoming mains voltage is not within specification. Recommended actions 1) Verify that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Verify that the motor cables are not damaged or badly connected. 3) Verify that the motor cables has no short circuits internally or to ground. 4) Verify that no DC link errors are present in the event log. 5) Verify that the incoming mains voltage is within the specification. 34318, Drive inverter saturated error Description The drive unit for joint arg has reached maximum output voltage. The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences The system goes to Motors Off state Probable causes 1) The motor is not properly connected to the drive unit. 2) The motor data in the configuration is not correct. 3) The DC link voltage is too low. 4) Short circuit between motor phases or ground. Recommended actions 1) Check motor cables and connectors. 2) Check configuration of motor parameters. 3) Check for other hardware eventlog messages. 4) Check incoming mains voltage to the rectifier unit. 5) Check the motor cable and motor by measuring their resistance respectively. Disconnect before measuring. 34319, Drive unit critical error Description The drive unit for joint arg gives an unspecified error, but is likely due to over temperature or short circuit. The joint is connected to drive module arg with the drive unit at unit position arg and node arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. Probable causes 1) The cooling fans may be faulty or the air flow may be obstructed. 2) The cooling fins are covered by dust reducing the cooling effect. 3) The ambient temperature may be too high. 4) The joint may be running with a too high torque for extended periods of time. 5) Short circuit in cables or connectors between the phases or to ground. 6) Short circuit in motor between the phases or to ground. 6 Trouble shooting by Event log 157 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Verify that the fans are running and that the air flow is not obstructed. 2) Clean the cooling fins. 3) Verify that the ambient temperature does not exceed the cabinet's temperature rating. 4) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration. 5) Reduce the static torque due to gravity or external forces. 6) Check/replace cables and connectors. 7) Check/replace motor. 34320, Too many drive nodes connected Description In drive module arg the system has detected more drive nodes than the system can handle. The limit was reached when drive unit at unit position arg was detected. Consequences No operation will be possible until the fault is corrected. The system goes to System Failure state. Probable causes 1) Too many drive units is connected to the drive unit communication link. 2) Too many drive unit that are equippted with many drive nodes are connected. Recommended actions 1) Verify that the proper drive units types are connected to the drive unit communication link. 2) Disconnect unused drive unit(s). 34400, DC link voltage too high Description In drive module arg , the drive unit at unit position arg has a DC link voltage that is too high. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. WARNING HIGH VOLTAGE: THE DC LINK MAY BE DISCHARGED VERY SLOWLY (APPROXIMATELY 1 HOUR) WHEN THE SYSTEM IS POWERED OFF. Probable causes 1) The bleeder resistor is not connected or faulty. 2) The user program may contain too much deceleration of the manipulator's axes. This fault is more likely if the system contains additional axes. Recommended actions WARNING HIGH VOLTAGE CAN BE PRESENT. 1) Make sure the bleeder resistor cable is properly connected to the rectifier unit. 2) Disconnect the bleeder and check the cable and measure the bleeder resistance. The expected resistance should be approximately arg ohms. 3) Rewrite the user program to reduce the amount of hard decelerations. 34401, DC link voltage too low warning Description In drive module arg , the drive unit at unit position arg has a DC link voltage that is close to minimum limit. Consequences Operation will be possible but the system is close to a stopping error. Probable causes The incoming mains voltage to the rectifier unit is out of specification. Recommended actions 1) Check for other hardware eventlog messages regarding mains voltage problem. 2) Check incoming mains voltage. 3) Check that the correct voltage is selected with jumpers on the transformer (optional). 4) Check all internal 3-phase components (main switch, mains filter, fuse, contactors) and cabling in the drive module. 34402, DC link voltage too low Description In drive module arg , the DC link voltage is too low for the drive unit at unit position arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes The incoming mains voltage to the rectifier unit is out of specification. Recommended actions 1) Check for other hardware eventlog messages regarding mains voltage problem. 2) Check incoming mains voltage. 3) Check that the correct voltage is selected with jumpers on the transformer (optional). 4) Check all internal 3-phase components (main switch, mains filter, fuse, contactors) and cabling in the drive module. 34404, DC link voltage is critically high Description In drive module arg , the drive unit at unit position arg has a DC link voltage that is critically high. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. 6 Trouble shooting by Event log 158 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. WARNING HIGH VOLTAGE: THE DC LINK MAY BE DISCHARGED VERY SLOWLY (APPROXIMATELY 1 HOUR) WHEN THE SYSTEM IS POWERED OFF. Probable causes 1) The bleeder resistor is not connected or faulty. 2) The user program may contain too much deceleration of the manipulator's axes. This fault is more likely if the system contains additional axes. Recommended actions WARNING HIGH VOLTAGE CAN BE PRESENT. 1) Make sure the bleeder resistor cable is properly connected to the rectifier unit. 2) Disconnect the bleeder and check the cable and measure the bleeder resistance. The expected resistance should be approximately arg ohms. 3) Rewrite the user program to reduce the amount of hard decelerations. 34405, DC link voltage too high warning Description In drive module arg , the drive unit at unit position arg has a DC link voltage that is close to maximum limit. Consequences Operation will be possible but the system is close to a stopping error. WARNING HIGH VOLTAGE: THE DC LINK MAY BE DISCHARGED VERY SLOWLY (APPROXIMATELY 1 HOUR) WHEN THE SYSTEM IS POWERED OFF. Probable causes 1) The bleeder resistor is not connected or faulty. 2) The user program may contain too much deceleration of the manipulator's axes. This fault is more likely if the system contains additional axes. Recommended actions WARNING HIGH VOLTAGE CAN BE PRESENT. 1) Make sure the bleeder resistor cable is properly connected to the rectifier unit. 2) Disconnect the bleeder and check the cable and measure the bleeder resistance. The expected resistance should be approximately arg ohms. 3) Rewrite the user program to reduce the amount of hard decelerations. 34406, Drive unit power supply error Description In drive module arg , the drive unit with unit position arg has detected problem with the logic power. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. Probable causes The 24V logic supply to the drive is temporary or constantly lost. Recommended actions 1) Check the event log for power supply unit error messages. 2) Check the cabling between the power supply unit and the drive unit. 3) Check the 24V output from the power supply unit. 34407, Drive unit internal error Description In drive module arg , the drive unit at unit position arg has indicated an internal error. Consequences The system goes to System Failure state with zero torque. Probable causes An internal error has occurred in the drive unit firmware. Recommended actions Restart the system by using the main power switch. 34408, Drive unit hardware data error Description In drive module arg , the drive unit at unit position arg has corrupt information stored on the unit. Consequences The system goes to System Failure state. Probable causes The integrity check of the drive unit information stored on the drive unit has failed. Recommended actions 1) Retry again by restarting the system using the main power switch. 2) Replace the faulty drive unit. 34409, Drive unit startup error Description The system has failed to complete the initialization phase of a drive unit. The drive unit is located in drive module arg at unit position arg . Consequences The system goes to System Failure state. Probable causes The system has failed to complete the initialization phase of the drive unit. Recommended actions 1) Retry by restarting the system using the main power switch. 2) Check for other hardware eventlog messages.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	160	6 Trouble shooting by Event log 157 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Verify that the fans are running and that the air flow is not obstructed. 2) Clean the cooling fins. 3) Verify that the ambient temperature does not exceed the cabinet's temperature rating. 4) If possible, rewrite the user program to reduce the amount of hard acceleration and hard deceleration. 5) Reduce the static torque due to gravity or external forces. 6) Check/replace cables and connectors. 7) Check/replace motor. 34320, Too many drive nodes connected Description In drive module arg the system has detected more drive nodes than the system can handle. The limit was reached when drive unit at unit position arg was detected. Consequences No operation will be possible until the fault is corrected. The system goes to System Failure state. Probable causes 1) Too many drive units is connected to the drive unit communication link. 2) Too many drive unit that are equippted with many drive nodes are connected. Recommended actions 1) Verify that the proper drive units types are connected to the drive unit communication link. 2) Disconnect unused drive unit(s). 34400, DC link voltage too high Description In drive module arg , the drive unit at unit position arg has a DC link voltage that is too high. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. WARNING HIGH VOLTAGE: THE DC LINK MAY BE DISCHARGED VERY SLOWLY (APPROXIMATELY 1 HOUR) WHEN THE SYSTEM IS POWERED OFF. Probable causes 1) The bleeder resistor is not connected or faulty. 2) The user program may contain too much deceleration of the manipulator's axes. This fault is more likely if the system contains additional axes. Recommended actions WARNING HIGH VOLTAGE CAN BE PRESENT. 1) Make sure the bleeder resistor cable is properly connected to the rectifier unit. 2) Disconnect the bleeder and check the cable and measure the bleeder resistance. The expected resistance should be approximately arg ohms. 3) Rewrite the user program to reduce the amount of hard decelerations. 34401, DC link voltage too low warning Description In drive module arg , the drive unit at unit position arg has a DC link voltage that is close to minimum limit. Consequences Operation will be possible but the system is close to a stopping error. Probable causes The incoming mains voltage to the rectifier unit is out of specification. Recommended actions 1) Check for other hardware eventlog messages regarding mains voltage problem. 2) Check incoming mains voltage. 3) Check that the correct voltage is selected with jumpers on the transformer (optional). 4) Check all internal 3-phase components (main switch, mains filter, fuse, contactors) and cabling in the drive module. 34402, DC link voltage too low Description In drive module arg , the DC link voltage is too low for the drive unit at unit position arg . Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state. Probable causes The incoming mains voltage to the rectifier unit is out of specification. Recommended actions 1) Check for other hardware eventlog messages regarding mains voltage problem. 2) Check incoming mains voltage. 3) Check that the correct voltage is selected with jumpers on the transformer (optional). 4) Check all internal 3-phase components (main switch, mains filter, fuse, contactors) and cabling in the drive module. 34404, DC link voltage is critically high Description In drive module arg , the drive unit at unit position arg has a DC link voltage that is critically high. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. 6 Trouble shooting by Event log 158 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. WARNING HIGH VOLTAGE: THE DC LINK MAY BE DISCHARGED VERY SLOWLY (APPROXIMATELY 1 HOUR) WHEN THE SYSTEM IS POWERED OFF. Probable causes 1) The bleeder resistor is not connected or faulty. 2) The user program may contain too much deceleration of the manipulator's axes. This fault is more likely if the system contains additional axes. Recommended actions WARNING HIGH VOLTAGE CAN BE PRESENT. 1) Make sure the bleeder resistor cable is properly connected to the rectifier unit. 2) Disconnect the bleeder and check the cable and measure the bleeder resistance. The expected resistance should be approximately arg ohms. 3) Rewrite the user program to reduce the amount of hard decelerations. 34405, DC link voltage too high warning Description In drive module arg , the drive unit at unit position arg has a DC link voltage that is close to maximum limit. Consequences Operation will be possible but the system is close to a stopping error. WARNING HIGH VOLTAGE: THE DC LINK MAY BE DISCHARGED VERY SLOWLY (APPROXIMATELY 1 HOUR) WHEN THE SYSTEM IS POWERED OFF. Probable causes 1) The bleeder resistor is not connected or faulty. 2) The user program may contain too much deceleration of the manipulator's axes. This fault is more likely if the system contains additional axes. Recommended actions WARNING HIGH VOLTAGE CAN BE PRESENT. 1) Make sure the bleeder resistor cable is properly connected to the rectifier unit. 2) Disconnect the bleeder and check the cable and measure the bleeder resistance. The expected resistance should be approximately arg ohms. 3) Rewrite the user program to reduce the amount of hard decelerations. 34406, Drive unit power supply error Description In drive module arg , the drive unit with unit position arg has detected problem with the logic power. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. Probable causes The 24V logic supply to the drive is temporary or constantly lost. Recommended actions 1) Check the event log for power supply unit error messages. 2) Check the cabling between the power supply unit and the drive unit. 3) Check the 24V output from the power supply unit. 34407, Drive unit internal error Description In drive module arg , the drive unit at unit position arg has indicated an internal error. Consequences The system goes to System Failure state with zero torque. Probable causes An internal error has occurred in the drive unit firmware. Recommended actions Restart the system by using the main power switch. 34408, Drive unit hardware data error Description In drive module arg , the drive unit at unit position arg has corrupt information stored on the unit. Consequences The system goes to System Failure state. Probable causes The integrity check of the drive unit information stored on the drive unit has failed. Recommended actions 1) Retry again by restarting the system using the main power switch. 2) Replace the faulty drive unit. 34409, Drive unit startup error Description The system has failed to complete the initialization phase of a drive unit. The drive unit is located in drive module arg at unit position arg . Consequences The system goes to System Failure state. Probable causes The system has failed to complete the initialization phase of the drive unit. Recommended actions 1) Retry by restarting the system using the main power switch. 2) Check for other hardware eventlog messages. 6 Trouble shooting by Event log 159 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 34410, Too many drive units connected Description In drive module arg the system has detected more drive units than the system can handle. The maximum number of drive units supported is arg , but arg was detected. Consequences No operation will be possible until the fault is corrected. The system goes to System Failure state. Probable causes 1) Too many drive unit that are connected. Recommended actions 1) Disconnect unused drive unit(s). 37001, Motors ON contactor activation error Description Motors ON contactor arg in drive module arg failed to close when ordered. Consequences The mechanical unit can not be run manually or automatically. Probable causes 1) The runchain for the contactor is open. 2) There are problems in the contactor itself, either mechanical or electrical. 3) The teach pendant enabling device may have been toggled too quickly, or the system may not be configured correctly. On rare occasions, this fault may occur in combination with other faults, in which case this may be found in the error log. Recommended actions 1) To resume normal operation, first acknowledge the error, then release the enabling device and press it again after approx. one second. 2) Check cables and connections on the Safety System. 3) Check any other error log messages coinciding in time with this one for clues. 4) Check the system motion configuration regarding Motors ON relay. How to check the configuration file is detailed in the Trouble Shooting Manual. 37043, Safety signals overloaded Description The AC_ON or SPEED signals draw too much current. Consequences The Safety System shuts down the signals, causing the system to go to either status SYS FAIL (for AC_ON) or status SYS HALT (for SPEED). Probable causes A load connected to the circuit may be too high, or the Safety System may be malfunctioning. See the Circuit Diagram! Recommended actions 1) Check all loads connected to the AC_ON and SPEED circuits 2) Check the Safety System cabling and connectors, and replace any faulty unit if required. 37044, Overload on Panel Board digital output signals Description The Panel Board User Digital outputs draw too much current. Consequences The Panel Board shuts down the signals, causing the system to go to status SYS HALT. Probable causes A load connected to the circuit may be too high, or the Panel Board may be malfunctioning. See the Circuit Diagram! Recommended actions 1) Check all loads connected to the User Digital outputs 2) Check the Panel Board cabling and connectors, and replace any faulty unit if required. 37045, Faulty External Computer fan Description The External Computer fan in the Control Module spins too slowly. Consequences No system consequence. The Control Module temperature will rise. Probable causes Faulty fan, cabling or power supply. See the Circuit Diagram! Recommended actions 1) Check the cabling to the External Computer fan. 2) Check the fan, and replace any faulty unit if required. 37046, Safety signals overloaded Description The 24 V PANEL supply draws too much current. Consequences The Safety System shuts down the signal, causing the system to go to status SYS HALT. Probable causes A load connected to the circuit may be too high, or the Safety System unit may be malfunctioning. See the Circuit Diagram! Recommended actions 1) Check all loads connected to the 24V PANEL circuit. 2) Check cabling on the Safety System.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	161	6 Trouble shooting by Event log 158 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. WARNING HIGH VOLTAGE: THE DC LINK MAY BE DISCHARGED VERY SLOWLY (APPROXIMATELY 1 HOUR) WHEN THE SYSTEM IS POWERED OFF. Probable causes 1) The bleeder resistor is not connected or faulty. 2) The user program may contain too much deceleration of the manipulator's axes. This fault is more likely if the system contains additional axes. Recommended actions WARNING HIGH VOLTAGE CAN BE PRESENT. 1) Make sure the bleeder resistor cable is properly connected to the rectifier unit. 2) Disconnect the bleeder and check the cable and measure the bleeder resistance. The expected resistance should be approximately arg ohms. 3) Rewrite the user program to reduce the amount of hard decelerations. 34405, DC link voltage too high warning Description In drive module arg , the drive unit at unit position arg has a DC link voltage that is close to maximum limit. Consequences Operation will be possible but the system is close to a stopping error. WARNING HIGH VOLTAGE: THE DC LINK MAY BE DISCHARGED VERY SLOWLY (APPROXIMATELY 1 HOUR) WHEN THE SYSTEM IS POWERED OFF. Probable causes 1) The bleeder resistor is not connected or faulty. 2) The user program may contain too much deceleration of the manipulator's axes. This fault is more likely if the system contains additional axes. Recommended actions WARNING HIGH VOLTAGE CAN BE PRESENT. 1) Make sure the bleeder resistor cable is properly connected to the rectifier unit. 2) Disconnect the bleeder and check the cable and measure the bleeder resistance. The expected resistance should be approximately arg ohms. 3) Rewrite the user program to reduce the amount of hard decelerations. 34406, Drive unit power supply error Description In drive module arg , the drive unit with unit position arg has detected problem with the logic power. Consequences No operation will be possible until the fault is corrected. The system goes to Motors Off state with zero torque. Probable causes The 24V logic supply to the drive is temporary or constantly lost. Recommended actions 1) Check the event log for power supply unit error messages. 2) Check the cabling between the power supply unit and the drive unit. 3) Check the 24V output from the power supply unit. 34407, Drive unit internal error Description In drive module arg , the drive unit at unit position arg has indicated an internal error. Consequences The system goes to System Failure state with zero torque. Probable causes An internal error has occurred in the drive unit firmware. Recommended actions Restart the system by using the main power switch. 34408, Drive unit hardware data error Description In drive module arg , the drive unit at unit position arg has corrupt information stored on the unit. Consequences The system goes to System Failure state. Probable causes The integrity check of the drive unit information stored on the drive unit has failed. Recommended actions 1) Retry again by restarting the system using the main power switch. 2) Replace the faulty drive unit. 34409, Drive unit startup error Description The system has failed to complete the initialization phase of a drive unit. The drive unit is located in drive module arg at unit position arg . Consequences The system goes to System Failure state. Probable causes The system has failed to complete the initialization phase of the drive unit. Recommended actions 1) Retry by restarting the system using the main power switch. 2) Check for other hardware eventlog messages. 6 Trouble shooting by Event log 159 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 34410, Too many drive units connected Description In drive module arg the system has detected more drive units than the system can handle. The maximum number of drive units supported is arg , but arg was detected. Consequences No operation will be possible until the fault is corrected. The system goes to System Failure state. Probable causes 1) Too many drive unit that are connected. Recommended actions 1) Disconnect unused drive unit(s). 37001, Motors ON contactor activation error Description Motors ON contactor arg in drive module arg failed to close when ordered. Consequences The mechanical unit can not be run manually or automatically. Probable causes 1) The runchain for the contactor is open. 2) There are problems in the contactor itself, either mechanical or electrical. 3) The teach pendant enabling device may have been toggled too quickly, or the system may not be configured correctly. On rare occasions, this fault may occur in combination with other faults, in which case this may be found in the error log. Recommended actions 1) To resume normal operation, first acknowledge the error, then release the enabling device and press it again after approx. one second. 2) Check cables and connections on the Safety System. 3) Check any other error log messages coinciding in time with this one for clues. 4) Check the system motion configuration regarding Motors ON relay. How to check the configuration file is detailed in the Trouble Shooting Manual. 37043, Safety signals overloaded Description The AC_ON or SPEED signals draw too much current. Consequences The Safety System shuts down the signals, causing the system to go to either status SYS FAIL (for AC_ON) or status SYS HALT (for SPEED). Probable causes A load connected to the circuit may be too high, or the Safety System may be malfunctioning. See the Circuit Diagram! Recommended actions 1) Check all loads connected to the AC_ON and SPEED circuits 2) Check the Safety System cabling and connectors, and replace any faulty unit if required. 37044, Overload on Panel Board digital output signals Description The Panel Board User Digital outputs draw too much current. Consequences The Panel Board shuts down the signals, causing the system to go to status SYS HALT. Probable causes A load connected to the circuit may be too high, or the Panel Board may be malfunctioning. See the Circuit Diagram! Recommended actions 1) Check all loads connected to the User Digital outputs 2) Check the Panel Board cabling and connectors, and replace any faulty unit if required. 37045, Faulty External Computer fan Description The External Computer fan in the Control Module spins too slowly. Consequences No system consequence. The Control Module temperature will rise. Probable causes Faulty fan, cabling or power supply. See the Circuit Diagram! Recommended actions 1) Check the cabling to the External Computer fan. 2) Check the fan, and replace any faulty unit if required. 37046, Safety signals overloaded Description The 24 V PANEL supply draws too much current. Consequences The Safety System shuts down the signal, causing the system to go to status SYS HALT. Probable causes A load connected to the circuit may be too high, or the Safety System unit may be malfunctioning. See the Circuit Diagram! Recommended actions 1) Check all loads connected to the 24V PANEL circuit. 2) Check cabling on the Safety System. 6 Trouble shooting by Event log 160 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 37049, Activation contactor activation error Description The activation relay for mechanical unit arg failed to close. Consequences The mechanical unit can not be run manually or automatically. Probable causes The activation relay configured within the system may be faulty, or the system may not be configured correctly. Recommended actions 1) Check the contactor and make sure its connections are connected correctly. 2) Check the system motion configuration regarding the activation relay. How to check the configuration file is detailed in the Trouble Shooting Manual. 37050, Overtemperature in main computer Description The temperature in the main computer unit or the main computer processor is too high. Consequences The system might get damaged. Probable causes The unit may be overloaded, its fans may be malfunctioning or the air flow may be restricted. Recommended actions 1) Make sure the fans are operating. 2) Check that air flow to the unit fans is not restricted. 37053, Low CMOS battery voltage level Description The CMOS battery on the computer board is empty. Consequences On restart, the system will use an erroneous setup or no restart will be possible. Probable causes Faulty battery. Recommended actions 1. Replace the CMOS battery 37054, Faulty Computer Unit fan Description The fans in the Computer Unit spin too slowly. Consequences No system consequence. The Computer Unit temperature will rise. Probable causes Faulty fan, cabling or power supply. See the Circuit Diagram! Recommended actions 1) Check the cabling to the Computer Unit fan. 2) Check the fan. 3) Check the fan power supply. 4) Replace the faulty component if required. 37056, Cooling fan error Description Cooling unit fan has stopped or is rotating very slowly (Less than arg rpm). Recommended actions 1. Check the fan cables. 2. Replace the fan. 37062, Computer Module power supply warning Description The arg V voltage of the Computer Module power supply is arg V, which is out of the allowed range. Consequences - Probable causes The power supply unit, cabling, input voltage to the power supply or the output load may cause the faulty voltage level. See the Trouble Shooting Manual and Circuit Diagram! Recommended actions 1) Check all cabling to the power supply unit. 2) Measure the output and input voltage levels. 3) Replace the faulty unit if required. 37069, Faulty backup Power Supply Description The backup energy bank in the Control Module supplying the backup voltage is faulty. Consequences After switching the power off, a B type restart must be performed. No system data changes will be saved at power off. Probable causes This may be caused by a faulty backup energy bank, cabling or charger. Recommended actions Do not turn the main power off until battery has been charged, or the system may perform a cold start! 1) Check the backup energy bank cabling and connectors. 2) Check the backup energy bank. 3) Check the power supply.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	162	6 Trouble shooting by Event log 159 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 34410, Too many drive units connected Description In drive module arg the system has detected more drive units than the system can handle. The maximum number of drive units supported is arg , but arg was detected. Consequences No operation will be possible until the fault is corrected. The system goes to System Failure state. Probable causes 1) Too many drive unit that are connected. Recommended actions 1) Disconnect unused drive unit(s). 37001, Motors ON contactor activation error Description Motors ON contactor arg in drive module arg failed to close when ordered. Consequences The mechanical unit can not be run manually or automatically. Probable causes 1) The runchain for the contactor is open. 2) There are problems in the contactor itself, either mechanical or electrical. 3) The teach pendant enabling device may have been toggled too quickly, or the system may not be configured correctly. On rare occasions, this fault may occur in combination with other faults, in which case this may be found in the error log. Recommended actions 1) To resume normal operation, first acknowledge the error, then release the enabling device and press it again after approx. one second. 2) Check cables and connections on the Safety System. 3) Check any other error log messages coinciding in time with this one for clues. 4) Check the system motion configuration regarding Motors ON relay. How to check the configuration file is detailed in the Trouble Shooting Manual. 37043, Safety signals overloaded Description The AC_ON or SPEED signals draw too much current. Consequences The Safety System shuts down the signals, causing the system to go to either status SYS FAIL (for AC_ON) or status SYS HALT (for SPEED). Probable causes A load connected to the circuit may be too high, or the Safety System may be malfunctioning. See the Circuit Diagram! Recommended actions 1) Check all loads connected to the AC_ON and SPEED circuits 2) Check the Safety System cabling and connectors, and replace any faulty unit if required. 37044, Overload on Panel Board digital output signals Description The Panel Board User Digital outputs draw too much current. Consequences The Panel Board shuts down the signals, causing the system to go to status SYS HALT. Probable causes A load connected to the circuit may be too high, or the Panel Board may be malfunctioning. See the Circuit Diagram! Recommended actions 1) Check all loads connected to the User Digital outputs 2) Check the Panel Board cabling and connectors, and replace any faulty unit if required. 37045, Faulty External Computer fan Description The External Computer fan in the Control Module spins too slowly. Consequences No system consequence. The Control Module temperature will rise. Probable causes Faulty fan, cabling or power supply. See the Circuit Diagram! Recommended actions 1) Check the cabling to the External Computer fan. 2) Check the fan, and replace any faulty unit if required. 37046, Safety signals overloaded Description The 24 V PANEL supply draws too much current. Consequences The Safety System shuts down the signal, causing the system to go to status SYS HALT. Probable causes A load connected to the circuit may be too high, or the Safety System unit may be malfunctioning. See the Circuit Diagram! Recommended actions 1) Check all loads connected to the 24V PANEL circuit. 2) Check cabling on the Safety System. 6 Trouble shooting by Event log 160 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 37049, Activation contactor activation error Description The activation relay for mechanical unit arg failed to close. Consequences The mechanical unit can not be run manually or automatically. Probable causes The activation relay configured within the system may be faulty, or the system may not be configured correctly. Recommended actions 1) Check the contactor and make sure its connections are connected correctly. 2) Check the system motion configuration regarding the activation relay. How to check the configuration file is detailed in the Trouble Shooting Manual. 37050, Overtemperature in main computer Description The temperature in the main computer unit or the main computer processor is too high. Consequences The system might get damaged. Probable causes The unit may be overloaded, its fans may be malfunctioning or the air flow may be restricted. Recommended actions 1) Make sure the fans are operating. 2) Check that air flow to the unit fans is not restricted. 37053, Low CMOS battery voltage level Description The CMOS battery on the computer board is empty. Consequences On restart, the system will use an erroneous setup or no restart will be possible. Probable causes Faulty battery. Recommended actions 1. Replace the CMOS battery 37054, Faulty Computer Unit fan Description The fans in the Computer Unit spin too slowly. Consequences No system consequence. The Computer Unit temperature will rise. Probable causes Faulty fan, cabling or power supply. See the Circuit Diagram! Recommended actions 1) Check the cabling to the Computer Unit fan. 2) Check the fan. 3) Check the fan power supply. 4) Replace the faulty component if required. 37056, Cooling fan error Description Cooling unit fan has stopped or is rotating very slowly (Less than arg rpm). Recommended actions 1. Check the fan cables. 2. Replace the fan. 37062, Computer Module power supply warning Description The arg V voltage of the Computer Module power supply is arg V, which is out of the allowed range. Consequences - Probable causes The power supply unit, cabling, input voltage to the power supply or the output load may cause the faulty voltage level. See the Trouble Shooting Manual and Circuit Diagram! Recommended actions 1) Check all cabling to the power supply unit. 2) Measure the output and input voltage levels. 3) Replace the faulty unit if required. 37069, Faulty backup Power Supply Description The backup energy bank in the Control Module supplying the backup voltage is faulty. Consequences After switching the power off, a B type restart must be performed. No system data changes will be saved at power off. Probable causes This may be caused by a faulty backup energy bank, cabling or charger. Recommended actions Do not turn the main power off until battery has been charged, or the system may perform a cold start! 1) Check the backup energy bank cabling and connectors. 2) Check the backup energy bank. 3) Check the power supply. 6 Trouble shooting by Event log 161 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 4) Replace the faulty unit if required. 37070, Overtemp in Control Module Power Supply Description The temperature in the control module power supply is too high. Consequences The system is shut down immediately. Probable causes This may be caused by poor cooling, too high a load on the power supply or by a faulty power supply. Recommended actions 1) Check the cooling fan. 2) Check the output power. 3) Replace any faulty unit if required. 37074, Purge pressure too low Description Purge system number arg assosiated with Manipulator Interface Board (MIB) arg . Recommended actions Check the purge air supply and search for leaks in: 1. The purge unit. 2. The flexible hose conduit. 3. The manipulator itself. 37075, Purge pressure too high Description Purge system number arg assosiated with Manipulator Interface Board (MIB) arg . Recommended actions Check the purge unit and the air supply. 37076, Unexpected low purge flow Description Purge system number arg assosiated with Manipulator Interface Board (MIB) arg . Recommended actions Check the purge unit and the air supply. Search for leaks in the purge system. 37077, Unexpected high purge flow Description Purge system number arg assosiated with Manipulator Interface Board (MIB) arg . Recommended actions Check the purge unit and the air supply. 37078, Purge timers differ Description Unacceptable divergence between Process Interface Board (PIB) and Manipulator Interface Board (MIB) arg purge timers. Consequences The purge timer will be restarted. Recommended actions 1. Check Serial Peripheral Interface (SPI) cables. 2. Replace MIB if faulty. 3. Replace PIB if faulty. 37080, Purge configuration not valid. Description The Purge Time Key on Manipulator Interface Board (MIB) arg X19 is not valid. Consequences Default time (300s) is used. Probable causes Faulty or missing Purge Time Key. Recommended actions 1. Check that the Purge Time Key is correctly mounted. 2. Replace Purge Time Key. 37081, Purge timers differ Description Unacceptable divergence between CPLD and FPGA firmware on Manipulator Interface Board (MIB) arg purge timers. Consequences The purge timer will be restarted. Recommended actions Replace MIB if faulty. 37082, Divergence between PIB and MIB outputs Description Process Interface Board (PIB) and Manipulator Interface Board (MIB) arg are not agreed concerned to output status for purge relay and power relay. Consequences Purge sequence is restarted.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	163	6 Trouble shooting by Event log 160 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 37049, Activation contactor activation error Description The activation relay for mechanical unit arg failed to close. Consequences The mechanical unit can not be run manually or automatically. Probable causes The activation relay configured within the system may be faulty, or the system may not be configured correctly. Recommended actions 1) Check the contactor and make sure its connections are connected correctly. 2) Check the system motion configuration regarding the activation relay. How to check the configuration file is detailed in the Trouble Shooting Manual. 37050, Overtemperature in main computer Description The temperature in the main computer unit or the main computer processor is too high. Consequences The system might get damaged. Probable causes The unit may be overloaded, its fans may be malfunctioning or the air flow may be restricted. Recommended actions 1) Make sure the fans are operating. 2) Check that air flow to the unit fans is not restricted. 37053, Low CMOS battery voltage level Description The CMOS battery on the computer board is empty. Consequences On restart, the system will use an erroneous setup or no restart will be possible. Probable causes Faulty battery. Recommended actions 1. Replace the CMOS battery 37054, Faulty Computer Unit fan Description The fans in the Computer Unit spin too slowly. Consequences No system consequence. The Computer Unit temperature will rise. Probable causes Faulty fan, cabling or power supply. See the Circuit Diagram! Recommended actions 1) Check the cabling to the Computer Unit fan. 2) Check the fan. 3) Check the fan power supply. 4) Replace the faulty component if required. 37056, Cooling fan error Description Cooling unit fan has stopped or is rotating very slowly (Less than arg rpm). Recommended actions 1. Check the fan cables. 2. Replace the fan. 37062, Computer Module power supply warning Description The arg V voltage of the Computer Module power supply is arg V, which is out of the allowed range. Consequences - Probable causes The power supply unit, cabling, input voltage to the power supply or the output load may cause the faulty voltage level. See the Trouble Shooting Manual and Circuit Diagram! Recommended actions 1) Check all cabling to the power supply unit. 2) Measure the output and input voltage levels. 3) Replace the faulty unit if required. 37069, Faulty backup Power Supply Description The backup energy bank in the Control Module supplying the backup voltage is faulty. Consequences After switching the power off, a B type restart must be performed. No system data changes will be saved at power off. Probable causes This may be caused by a faulty backup energy bank, cabling or charger. Recommended actions Do not turn the main power off until battery has been charged, or the system may perform a cold start! 1) Check the backup energy bank cabling and connectors. 2) Check the backup energy bank. 3) Check the power supply. 6 Trouble shooting by Event log 161 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 4) Replace the faulty unit if required. 37070, Overtemp in Control Module Power Supply Description The temperature in the control module power supply is too high. Consequences The system is shut down immediately. Probable causes This may be caused by poor cooling, too high a load on the power supply or by a faulty power supply. Recommended actions 1) Check the cooling fan. 2) Check the output power. 3) Replace any faulty unit if required. 37074, Purge pressure too low Description Purge system number arg assosiated with Manipulator Interface Board (MIB) arg . Recommended actions Check the purge air supply and search for leaks in: 1. The purge unit. 2. The flexible hose conduit. 3. The manipulator itself. 37075, Purge pressure too high Description Purge system number arg assosiated with Manipulator Interface Board (MIB) arg . Recommended actions Check the purge unit and the air supply. 37076, Unexpected low purge flow Description Purge system number arg assosiated with Manipulator Interface Board (MIB) arg . Recommended actions Check the purge unit and the air supply. Search for leaks in the purge system. 37077, Unexpected high purge flow Description Purge system number arg assosiated with Manipulator Interface Board (MIB) arg . Recommended actions Check the purge unit and the air supply. 37078, Purge timers differ Description Unacceptable divergence between Process Interface Board (PIB) and Manipulator Interface Board (MIB) arg purge timers. Consequences The purge timer will be restarted. Recommended actions 1. Check Serial Peripheral Interface (SPI) cables. 2. Replace MIB if faulty. 3. Replace PIB if faulty. 37080, Purge configuration not valid. Description The Purge Time Key on Manipulator Interface Board (MIB) arg X19 is not valid. Consequences Default time (300s) is used. Probable causes Faulty or missing Purge Time Key. Recommended actions 1. Check that the Purge Time Key is correctly mounted. 2. Replace Purge Time Key. 37081, Purge timers differ Description Unacceptable divergence between CPLD and FPGA firmware on Manipulator Interface Board (MIB) arg purge timers. Consequences The purge timer will be restarted. Recommended actions Replace MIB if faulty. 37082, Divergence between PIB and MIB outputs Description Process Interface Board (PIB) and Manipulator Interface Board (MIB) arg are not agreed concerned to output status for purge relay and power relay. Consequences Purge sequence is restarted. 6 Trouble shooting by Event log 162 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 37090, Temp. too high, sensor arg Description System overheat detected. Sensors 1-7: motor 1-7, sensor 8: Serial measurement board. Run chain has been opened. Recommended actions 37094, Activate connection error Description Could not activate arg . Connection relay input arg indicates no connection. Recommended actions 1. Check that if mechanical unit is connected. 2. Check the connection relay input signal setup. 37095, Brake power fault Description The supervision of brake power on Manipulator Controller Board (MCOB) has detected fault on the power signal and turned ON all brakes. Recommended actions 1. Check brake power on MCOB. 2. Check brake power relay in cabinet. 3. Check for disturbances on the brake power signal on MCOB/MCB. 4. Check for short circuit on brakes. 37096, Brake power fault Description The supervision of brake power on Manipulator Controller Board (MCOB/MCB) has detected fault on the power signal and turned ON all brakes. Recommended actions 1. Check brake power on MCOB/MCB. 2. Check brake power relay in cabinet. 3. Check for disturbances on the brake power signal on MCOB/MCB. 37097, Brake short circuit fault Description The supervision of brakes on Manipulator Controller Board (MCOB/ MCB) has detected a short circuit on axis arg and turned ON all brakes. Recommended actions 1. Check for short circuit on brakes. 37098, Brake open circuit fault Description The supervision of brakes on Manipulator Controller Board (MCOB/ MCB) has detected an open circuit on axis arg and turned ON all brakes. Recommended actions 1. Check for open circuit on brakes. 37099, Temp. too high, sensor arg Description System overheat detected on motors, Serial measurement unit (SMU) or process equipment. Run chain has been opened. Recommended actions Sensors 1-8: Robot motors 1-8 Sensor 9: SMU Sensors 10-14: Process 1-5 Please refer to current robot config. for more details. 37100, I/O node flash disk error Description Flash name: arg Flash disk function: arg Error description: arg Recommended actions Report error. 37101, Brake Failure Description The brakes for mechanical unit arg fail to engage. Consequences The mechanical unit may collapse when the motors are turned off. Probable causes The configuration of brake relay may be incorrect, or the brake relay may be faulty If an external brake relay is being used, the relay must be correctly defined in the motion configuration file. Recommended actions 1) Check that the external brake relay (if used) is correctly defined in the configuration file. 2) Check that the corresponding I/O signal is correctly defined in the I/O configuration file. How to check the configuration files is detailed in the Trouble Shooting Manual.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	164	6 Trouble shooting by Event log 161 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 4) Replace the faulty unit if required. 37070, Overtemp in Control Module Power Supply Description The temperature in the control module power supply is too high. Consequences The system is shut down immediately. Probable causes This may be caused by poor cooling, too high a load on the power supply or by a faulty power supply. Recommended actions 1) Check the cooling fan. 2) Check the output power. 3) Replace any faulty unit if required. 37074, Purge pressure too low Description Purge system number arg assosiated with Manipulator Interface Board (MIB) arg . Recommended actions Check the purge air supply and search for leaks in: 1. The purge unit. 2. The flexible hose conduit. 3. The manipulator itself. 37075, Purge pressure too high Description Purge system number arg assosiated with Manipulator Interface Board (MIB) arg . Recommended actions Check the purge unit and the air supply. 37076, Unexpected low purge flow Description Purge system number arg assosiated with Manipulator Interface Board (MIB) arg . Recommended actions Check the purge unit and the air supply. Search for leaks in the purge system. 37077, Unexpected high purge flow Description Purge system number arg assosiated with Manipulator Interface Board (MIB) arg . Recommended actions Check the purge unit and the air supply. 37078, Purge timers differ Description Unacceptable divergence between Process Interface Board (PIB) and Manipulator Interface Board (MIB) arg purge timers. Consequences The purge timer will be restarted. Recommended actions 1. Check Serial Peripheral Interface (SPI) cables. 2. Replace MIB if faulty. 3. Replace PIB if faulty. 37080, Purge configuration not valid. Description The Purge Time Key on Manipulator Interface Board (MIB) arg X19 is not valid. Consequences Default time (300s) is used. Probable causes Faulty or missing Purge Time Key. Recommended actions 1. Check that the Purge Time Key is correctly mounted. 2. Replace Purge Time Key. 37081, Purge timers differ Description Unacceptable divergence between CPLD and FPGA firmware on Manipulator Interface Board (MIB) arg purge timers. Consequences The purge timer will be restarted. Recommended actions Replace MIB if faulty. 37082, Divergence between PIB and MIB outputs Description Process Interface Board (PIB) and Manipulator Interface Board (MIB) arg are not agreed concerned to output status for purge relay and power relay. Consequences Purge sequence is restarted. 6 Trouble shooting by Event log 162 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 37090, Temp. too high, sensor arg Description System overheat detected. Sensors 1-7: motor 1-7, sensor 8: Serial measurement board. Run chain has been opened. Recommended actions 37094, Activate connection error Description Could not activate arg . Connection relay input arg indicates no connection. Recommended actions 1. Check that if mechanical unit is connected. 2. Check the connection relay input signal setup. 37095, Brake power fault Description The supervision of brake power on Manipulator Controller Board (MCOB) has detected fault on the power signal and turned ON all brakes. Recommended actions 1. Check brake power on MCOB. 2. Check brake power relay in cabinet. 3. Check for disturbances on the brake power signal on MCOB/MCB. 4. Check for short circuit on brakes. 37096, Brake power fault Description The supervision of brake power on Manipulator Controller Board (MCOB/MCB) has detected fault on the power signal and turned ON all brakes. Recommended actions 1. Check brake power on MCOB/MCB. 2. Check brake power relay in cabinet. 3. Check for disturbances on the brake power signal on MCOB/MCB. 37097, Brake short circuit fault Description The supervision of brakes on Manipulator Controller Board (MCOB/ MCB) has detected a short circuit on axis arg and turned ON all brakes. Recommended actions 1. Check for short circuit on brakes. 37098, Brake open circuit fault Description The supervision of brakes on Manipulator Controller Board (MCOB/ MCB) has detected an open circuit on axis arg and turned ON all brakes. Recommended actions 1. Check for open circuit on brakes. 37099, Temp. too high, sensor arg Description System overheat detected on motors, Serial measurement unit (SMU) or process equipment. Run chain has been opened. Recommended actions Sensors 1-8: Robot motors 1-8 Sensor 9: SMU Sensors 10-14: Process 1-5 Please refer to current robot config. for more details. 37100, I/O node flash disk error Description Flash name: arg Flash disk function: arg Error description: arg Recommended actions Report error. 37101, Brake Failure Description The brakes for mechanical unit arg fail to engage. Consequences The mechanical unit may collapse when the motors are turned off. Probable causes The configuration of brake relay may be incorrect, or the brake relay may be faulty If an external brake relay is being used, the relay must be correctly defined in the motion configuration file. Recommended actions 1) Check that the external brake relay (if used) is correctly defined in the configuration file. 2) Check that the corresponding I/O signal is correctly defined in the I/O configuration file. How to check the configuration files is detailed in the Trouble Shooting Manual. 6 Trouble shooting by Event log 163 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 37102, Power supply warning, faulty 24V COOL level Description The 24V COOL output of the Control Module Power Supply is out of range. Consequences No system consequence. Probable causes The Control Module Power Supply unit cabling or the output load may cause the faulty voltage level. The power supplies are shown in the Trouble Shooting Manual and the Circuit Diagram! Recommended actions 1) Check all cabling to the Control Module Power Supply unit. 2) Check the output voltage level, and replace any faulty unit if required. 37103, Power supply warning, faulty 24V SYS level Description The 24V SYS output of the Control Module Power Supply is out of range. Consequences No system consequence. Probable causes The Control Module Power Supply unit, cabling or the output load may cause the faulty voltage level. The power supplies are shown in the Trouble Shooting Manual and the Circuit Diagram! Recommended actions 1) Check all cabling to the Control Module Power Supply unit. 2) Check the output voltage level, and replace any faulty unit if required. 37104, There is no backup voltage available! Description The backup energy bank maintaining the backup voltage is not functional. Consequences After switching the power off, a B type restart must be performed. No system data changes will be saved at power off. Probable causes This may be caused by a faulty backup energy bank, cabling or charger. Recommended actions Before working on the system, perform a controlled shutdown to ensure all system data is correctly saved. 1) Check the cables and connectors of the backup energy bank. 2) Check the backup energy bank. 3) Check the power supply. 4) Replace the faulty unit if required. 37105, Regained communication with Power Supply Description The main computer has regained communication with the Control Module Power Supply. 37106, Low backup energy bank voltage level Description The voltage in the computer unit backup energy bank is too low to be functional. Consequences No system consequence. No system data changes will be saved at power off. Probable causes This may be caused by a faulty backup energy bank, cabling or charger. Recommended actions Before working on the system, perform a controlled shutdown to ensure all system data is correctly saved. 1) Check the cables and connectors of the backup energy bank. 2) Check the backup energy bank. 3) Check the power supply. 4) Replace the faulty unit if required. 37107, Faulty backup energy bank Description The backup energy bank in the Control Module maintaining the backup voltage is not functional. Consequences If switching the power off, a B type restart must be performed. No backup will be made at power off. Probable causes This may be caused by a faulty backup energy bank, cabling or charger. Recommended actions Before working on the system, perform a controlled shutdown to ensure all system data is correctly saved. 1) Check the backup energy bank cable and connector. 2) Check the backup energy bank. 3) Replace the faulty unit if required.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	165	6 Trouble shooting by Event log 162 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 37090, Temp. too high, sensor arg Description System overheat detected. Sensors 1-7: motor 1-7, sensor 8: Serial measurement board. Run chain has been opened. Recommended actions 37094, Activate connection error Description Could not activate arg . Connection relay input arg indicates no connection. Recommended actions 1. Check that if mechanical unit is connected. 2. Check the connection relay input signal setup. 37095, Brake power fault Description The supervision of brake power on Manipulator Controller Board (MCOB) has detected fault on the power signal and turned ON all brakes. Recommended actions 1. Check brake power on MCOB. 2. Check brake power relay in cabinet. 3. Check for disturbances on the brake power signal on MCOB/MCB. 4. Check for short circuit on brakes. 37096, Brake power fault Description The supervision of brake power on Manipulator Controller Board (MCOB/MCB) has detected fault on the power signal and turned ON all brakes. Recommended actions 1. Check brake power on MCOB/MCB. 2. Check brake power relay in cabinet. 3. Check for disturbances on the brake power signal on MCOB/MCB. 37097, Brake short circuit fault Description The supervision of brakes on Manipulator Controller Board (MCOB/ MCB) has detected a short circuit on axis arg and turned ON all brakes. Recommended actions 1. Check for short circuit on brakes. 37098, Brake open circuit fault Description The supervision of brakes on Manipulator Controller Board (MCOB/ MCB) has detected an open circuit on axis arg and turned ON all brakes. Recommended actions 1. Check for open circuit on brakes. 37099, Temp. too high, sensor arg Description System overheat detected on motors, Serial measurement unit (SMU) or process equipment. Run chain has been opened. Recommended actions Sensors 1-8: Robot motors 1-8 Sensor 9: SMU Sensors 10-14: Process 1-5 Please refer to current robot config. for more details. 37100, I/O node flash disk error Description Flash name: arg Flash disk function: arg Error description: arg Recommended actions Report error. 37101, Brake Failure Description The brakes for mechanical unit arg fail to engage. Consequences The mechanical unit may collapse when the motors are turned off. Probable causes The configuration of brake relay may be incorrect, or the brake relay may be faulty If an external brake relay is being used, the relay must be correctly defined in the motion configuration file. Recommended actions 1) Check that the external brake relay (if used) is correctly defined in the configuration file. 2) Check that the corresponding I/O signal is correctly defined in the I/O configuration file. How to check the configuration files is detailed in the Trouble Shooting Manual. 6 Trouble shooting by Event log 163 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 37102, Power supply warning, faulty 24V COOL level Description The 24V COOL output of the Control Module Power Supply is out of range. Consequences No system consequence. Probable causes The Control Module Power Supply unit cabling or the output load may cause the faulty voltage level. The power supplies are shown in the Trouble Shooting Manual and the Circuit Diagram! Recommended actions 1) Check all cabling to the Control Module Power Supply unit. 2) Check the output voltage level, and replace any faulty unit if required. 37103, Power supply warning, faulty 24V SYS level Description The 24V SYS output of the Control Module Power Supply is out of range. Consequences No system consequence. Probable causes The Control Module Power Supply unit, cabling or the output load may cause the faulty voltage level. The power supplies are shown in the Trouble Shooting Manual and the Circuit Diagram! Recommended actions 1) Check all cabling to the Control Module Power Supply unit. 2) Check the output voltage level, and replace any faulty unit if required. 37104, There is no backup voltage available! Description The backup energy bank maintaining the backup voltage is not functional. Consequences After switching the power off, a B type restart must be performed. No system data changes will be saved at power off. Probable causes This may be caused by a faulty backup energy bank, cabling or charger. Recommended actions Before working on the system, perform a controlled shutdown to ensure all system data is correctly saved. 1) Check the cables and connectors of the backup energy bank. 2) Check the backup energy bank. 3) Check the power supply. 4) Replace the faulty unit if required. 37105, Regained communication with Power Supply Description The main computer has regained communication with the Control Module Power Supply. 37106, Low backup energy bank voltage level Description The voltage in the computer unit backup energy bank is too low to be functional. Consequences No system consequence. No system data changes will be saved at power off. Probable causes This may be caused by a faulty backup energy bank, cabling or charger. Recommended actions Before working on the system, perform a controlled shutdown to ensure all system data is correctly saved. 1) Check the cables and connectors of the backup energy bank. 2) Check the backup energy bank. 3) Check the power supply. 4) Replace the faulty unit if required. 37107, Faulty backup energy bank Description The backup energy bank in the Control Module maintaining the backup voltage is not functional. Consequences If switching the power off, a B type restart must be performed. No backup will be made at power off. Probable causes This may be caused by a faulty backup energy bank, cabling or charger. Recommended actions Before working on the system, perform a controlled shutdown to ensure all system data is correctly saved. 1) Check the backup energy bank cable and connector. 2) Check the backup energy bank. 3) Replace the faulty unit if required. 6 Trouble shooting by Event log 164 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 37108, Lost communication: Power Supply and Computer Description The main computer has lost communication with the Control Module Power Supply. Consequences The main computer cannot retrieve status info or switch the power supply off. No system data changes will be saved at power off. Probable causes The USB cable from the main computer to the Control Module Power Supply may be faulty or disconnected, or the power supply may be faulty. Recommended actions Before working on the system, perform a controlled shutdown to ensure all system data is correctly saved. 1) Check the cabling and connectors to the Control Module Power Supply. 2) Check the power supply unit, and replace any faulty unit if required. 37200, Power fault: Emergency Stop supply Description Power fault on 24V Emergency Stop supply. Feedback from Safety Interface Board (SIB). Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 37201, Power fault: 24V Failsafe supply Description Power fault on 24V Failsafe supply. Feedback from Safety Interface Board (SIB). Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 37202, Power fault: 24V I/O supply Description Power fault on 24V I/O supply. Feedback from Safety Interface Board (SIB). Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 37203, Power fault: 24V SYS supply Description Power fault reported when 24V SYS < 18V. Feedback from Manipulator Interface Board (MIB) arg . Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 37204, Power fault: 24V I/O supply Description Power fault reported when 24V I/O < 18V. Feedback from Manipulator Interface Board (MIB) arg . Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 37205, Power fault: 12V Purge supply Description Power fault reported when 12V Purge < 10.8V. Feedback from Manipulator Interface Board (MIB) arg . Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 37206, Power fault: 12V TPU supply Description Power fault on 12V Teach Pendant Unit (TPU) supply. Feedback from Pendant Interface Board (TIB). Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	166	6 Trouble shooting by Event log 163 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 37102, Power supply warning, faulty 24V COOL level Description The 24V COOL output of the Control Module Power Supply is out of range. Consequences No system consequence. Probable causes The Control Module Power Supply unit cabling or the output load may cause the faulty voltage level. The power supplies are shown in the Trouble Shooting Manual and the Circuit Diagram! Recommended actions 1) Check all cabling to the Control Module Power Supply unit. 2) Check the output voltage level, and replace any faulty unit if required. 37103, Power supply warning, faulty 24V SYS level Description The 24V SYS output of the Control Module Power Supply is out of range. Consequences No system consequence. Probable causes The Control Module Power Supply unit, cabling or the output load may cause the faulty voltage level. The power supplies are shown in the Trouble Shooting Manual and the Circuit Diagram! Recommended actions 1) Check all cabling to the Control Module Power Supply unit. 2) Check the output voltage level, and replace any faulty unit if required. 37104, There is no backup voltage available! Description The backup energy bank maintaining the backup voltage is not functional. Consequences After switching the power off, a B type restart must be performed. No system data changes will be saved at power off. Probable causes This may be caused by a faulty backup energy bank, cabling or charger. Recommended actions Before working on the system, perform a controlled shutdown to ensure all system data is correctly saved. 1) Check the cables and connectors of the backup energy bank. 2) Check the backup energy bank. 3) Check the power supply. 4) Replace the faulty unit if required. 37105, Regained communication with Power Supply Description The main computer has regained communication with the Control Module Power Supply. 37106, Low backup energy bank voltage level Description The voltage in the computer unit backup energy bank is too low to be functional. Consequences No system consequence. No system data changes will be saved at power off. Probable causes This may be caused by a faulty backup energy bank, cabling or charger. Recommended actions Before working on the system, perform a controlled shutdown to ensure all system data is correctly saved. 1) Check the cables and connectors of the backup energy bank. 2) Check the backup energy bank. 3) Check the power supply. 4) Replace the faulty unit if required. 37107, Faulty backup energy bank Description The backup energy bank in the Control Module maintaining the backup voltage is not functional. Consequences If switching the power off, a B type restart must be performed. No backup will be made at power off. Probable causes This may be caused by a faulty backup energy bank, cabling or charger. Recommended actions Before working on the system, perform a controlled shutdown to ensure all system data is correctly saved. 1) Check the backup energy bank cable and connector. 2) Check the backup energy bank. 3) Replace the faulty unit if required. 6 Trouble shooting by Event log 164 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 37108, Lost communication: Power Supply and Computer Description The main computer has lost communication with the Control Module Power Supply. Consequences The main computer cannot retrieve status info or switch the power supply off. No system data changes will be saved at power off. Probable causes The USB cable from the main computer to the Control Module Power Supply may be faulty or disconnected, or the power supply may be faulty. Recommended actions Before working on the system, perform a controlled shutdown to ensure all system data is correctly saved. 1) Check the cabling and connectors to the Control Module Power Supply. 2) Check the power supply unit, and replace any faulty unit if required. 37200, Power fault: Emergency Stop supply Description Power fault on 24V Emergency Stop supply. Feedback from Safety Interface Board (SIB). Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 37201, Power fault: 24V Failsafe supply Description Power fault on 24V Failsafe supply. Feedback from Safety Interface Board (SIB). Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 37202, Power fault: 24V I/O supply Description Power fault on 24V I/O supply. Feedback from Safety Interface Board (SIB). Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 37203, Power fault: 24V SYS supply Description Power fault reported when 24V SYS < 18V. Feedback from Manipulator Interface Board (MIB) arg . Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 37204, Power fault: 24V I/O supply Description Power fault reported when 24V I/O < 18V. Feedback from Manipulator Interface Board (MIB) arg . Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 37205, Power fault: 12V Purge supply Description Power fault reported when 12V Purge < 10.8V. Feedback from Manipulator Interface Board (MIB) arg . Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 37206, Power fault: 12V TPU supply Description Power fault on 12V Teach Pendant Unit (TPU) supply. Feedback from Pendant Interface Board (TIB). Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 6 Trouble shooting by Event log 165 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 37207, Battery charge low. Description Less than 2 months until the battery backup to Serial Measurement Board (SMB) is discharged. Counting from first time this message was displayed. The battery is mounted on Manipulator Interface Board (MIB). Recommended actions Replace battery mounted on MIB. 37208, Overtemperature in transformer Description The temperature in the transformer is too high. Consequences The system goes to status SYS HALT. Probable causes The unit may be overloaded, its fans may be malfunctioning or the air flow may be restricted. Recommended actions 1) Make sure the fans are operating. 2) Check that air flow to the unit fans is not restricted. 37209, Overtemperature in cabinet Description The temperature in the cabinet is too high. Consequences The system goes to status SYS HALT. Probable causes The unit may be overloaded, its fans may be malfunctioning or the air flow may be restricted. Recommended actions 1) Make sure the fans are operating. 2) Check that air flow to the unit fans is not restricted. 37210, Fault on contactor KM1 Description A fault is observed on motor contactor KM1. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check contactor. 37211, Fault on contactor KM2 Description A fault is observed on motor contactor KM2. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check contactor. 37212, Fault on contactor KM101 Description A fault is observed on motor contactor KM101. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check contactor. 37213, Fault on contactor KM102 Description A fault is observed on motor contactor KM102. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check contactor. 37214, Run chain 1 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Run chain 1 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37215, Run chain 2 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Run chain 2 feedback signals.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	167	6 Trouble shooting by Event log 164 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 37108, Lost communication: Power Supply and Computer Description The main computer has lost communication with the Control Module Power Supply. Consequences The main computer cannot retrieve status info or switch the power supply off. No system data changes will be saved at power off. Probable causes The USB cable from the main computer to the Control Module Power Supply may be faulty or disconnected, or the power supply may be faulty. Recommended actions Before working on the system, perform a controlled shutdown to ensure all system data is correctly saved. 1) Check the cabling and connectors to the Control Module Power Supply. 2) Check the power supply unit, and replace any faulty unit if required. 37200, Power fault: Emergency Stop supply Description Power fault on 24V Emergency Stop supply. Feedback from Safety Interface Board (SIB). Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 37201, Power fault: 24V Failsafe supply Description Power fault on 24V Failsafe supply. Feedback from Safety Interface Board (SIB). Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 37202, Power fault: 24V I/O supply Description Power fault on 24V I/O supply. Feedback from Safety Interface Board (SIB). Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 37203, Power fault: 24V SYS supply Description Power fault reported when 24V SYS < 18V. Feedback from Manipulator Interface Board (MIB) arg . Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 37204, Power fault: 24V I/O supply Description Power fault reported when 24V I/O < 18V. Feedback from Manipulator Interface Board (MIB) arg . Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 37205, Power fault: 12V Purge supply Description Power fault reported when 12V Purge < 10.8V. Feedback from Manipulator Interface Board (MIB) arg . Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 37206, Power fault: 12V TPU supply Description Power fault on 12V Teach Pendant Unit (TPU) supply. Feedback from Pendant Interface Board (TIB). Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check power supply. 6 Trouble shooting by Event log 165 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 37207, Battery charge low. Description Less than 2 months until the battery backup to Serial Measurement Board (SMB) is discharged. Counting from first time this message was displayed. The battery is mounted on Manipulator Interface Board (MIB). Recommended actions Replace battery mounted on MIB. 37208, Overtemperature in transformer Description The temperature in the transformer is too high. Consequences The system goes to status SYS HALT. Probable causes The unit may be overloaded, its fans may be malfunctioning or the air flow may be restricted. Recommended actions 1) Make sure the fans are operating. 2) Check that air flow to the unit fans is not restricted. 37209, Overtemperature in cabinet Description The temperature in the cabinet is too high. Consequences The system goes to status SYS HALT. Probable causes The unit may be overloaded, its fans may be malfunctioning or the air flow may be restricted. Recommended actions 1) Make sure the fans are operating. 2) Check that air flow to the unit fans is not restricted. 37210, Fault on contactor KM1 Description A fault is observed on motor contactor KM1. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check contactor. 37211, Fault on contactor KM2 Description A fault is observed on motor contactor KM2. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check contactor. 37212, Fault on contactor KM101 Description A fault is observed on motor contactor KM101. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check contactor. 37213, Fault on contactor KM102 Description A fault is observed on motor contactor KM102. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check contactor. 37214, Run chain 1 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Run chain 1 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37215, Run chain 2 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Run chain 2 feedback signals. 6 Trouble shooting by Event log 166 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37216, Brake chain 1 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Brake chain 1 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37217, Brake chain 2 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Brake chain 2 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37218, Cabin Interlock chain 1 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Cabin Interlock chain 1 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37219, Cabin Interlock chain 2 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Cabin Interlock chain 2 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37220, HV Interlock chain 1 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on High Voltage (HV) Interlock chain 1 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37221, HV Interlock chain 2 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on High Voltage (HV) Interlock chain 2 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37222, System 2 Interlock chain feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on System 2 Interlock chain feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	168	6 Trouble shooting by Event log 165 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 37207, Battery charge low. Description Less than 2 months until the battery backup to Serial Measurement Board (SMB) is discharged. Counting from first time this message was displayed. The battery is mounted on Manipulator Interface Board (MIB). Recommended actions Replace battery mounted on MIB. 37208, Overtemperature in transformer Description The temperature in the transformer is too high. Consequences The system goes to status SYS HALT. Probable causes The unit may be overloaded, its fans may be malfunctioning or the air flow may be restricted. Recommended actions 1) Make sure the fans are operating. 2) Check that air flow to the unit fans is not restricted. 37209, Overtemperature in cabinet Description The temperature in the cabinet is too high. Consequences The system goes to status SYS HALT. Probable causes The unit may be overloaded, its fans may be malfunctioning or the air flow may be restricted. Recommended actions 1) Make sure the fans are operating. 2) Check that air flow to the unit fans is not restricted. 37210, Fault on contactor KM1 Description A fault is observed on motor contactor KM1. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check contactor. 37211, Fault on contactor KM2 Description A fault is observed on motor contactor KM2. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check contactor. 37212, Fault on contactor KM101 Description A fault is observed on motor contactor KM101. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check contactor. 37213, Fault on contactor KM102 Description A fault is observed on motor contactor KM102. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Check contactor. 37214, Run chain 1 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Run chain 1 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37215, Run chain 2 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Run chain 2 feedback signals. 6 Trouble shooting by Event log 166 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37216, Brake chain 1 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Brake chain 1 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37217, Brake chain 2 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Brake chain 2 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37218, Cabin Interlock chain 1 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Cabin Interlock chain 1 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37219, Cabin Interlock chain 2 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Cabin Interlock chain 2 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37220, HV Interlock chain 1 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on High Voltage (HV) Interlock chain 1 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37221, HV Interlock chain 2 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on High Voltage (HV) Interlock chain 2 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37222, System 2 Interlock chain feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on System 2 Interlock chain feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 6 Trouble shooting by Event log 167 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 37223, Main relay chain feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Main relay chain feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37224, Cabin Interlock chain 1 conflict Description Divergence on Cabin Interlock chain 1 between input and output signals on Safety Interface Board (SIB). Consequences Paint enable chain opens. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 37225, Cabin Interlock chain 2 conflict Description Divergence on Cabin Interlock chain 2 between input and output signals on Safety Interface Board (SIB). Consequences Paint enable chain opens. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 37226, HV Interlock chain 1 conflict Description Divergence on High Voltage (HV) Interlock chain 1 between input and output signals on Safety Interface Board (SIB). Consequences Paint enable chain opens. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 37227, HV Interlock chain 2 conflict Description Divergence on High Voltage (HV) Interlock chain 2 between input and output signals on Safety Interface Board (SIB). Consequences Paint enable chain opens. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 37228, Cabin Interlock chain conflict from SIB Description Only one of the two Cabin Interlock chains is opened. Reported from Safety Interface Board (SIB). Consequences Paint enable chain opens. Recommended actions Replace SIB if faulty. 37229, HV Interlock chain conflict from SIB Description Only one of the two High Voltage (HV) Interlock chains is opened. Reported from Safety Interface Board (SIB). Consequences Paint enable chain opens. Recommended actions Replace SIB if faulty. 37230, Brake Performance Warning Description The Cyclic Brake Check indicates that the brake for the mechanical unit arg axis no arg has not full braking torque. Consequences This is only a warning and no immediate action need to be taken. 37231, Brake Performance Error Description The Cyclic Brake Check has found that the brake for the mechanical unit arg axis no arg has too low braking torque. This brake will not be approved by the Safety Controller for Drive Module no arg . Consequences WARNING: The brake performance is too low for this axis.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	169	6 Trouble shooting by Event log 166 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37216, Brake chain 1 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Brake chain 1 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37217, Brake chain 2 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Brake chain 2 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37218, Cabin Interlock chain 1 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Cabin Interlock chain 1 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37219, Cabin Interlock chain 2 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Cabin Interlock chain 2 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37220, HV Interlock chain 1 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on High Voltage (HV) Interlock chain 1 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37221, HV Interlock chain 2 feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on High Voltage (HV) Interlock chain 2 feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37222, System 2 Interlock chain feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on System 2 Interlock chain feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 6 Trouble shooting by Event log 167 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 37223, Main relay chain feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Main relay chain feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37224, Cabin Interlock chain 1 conflict Description Divergence on Cabin Interlock chain 1 between input and output signals on Safety Interface Board (SIB). Consequences Paint enable chain opens. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 37225, Cabin Interlock chain 2 conflict Description Divergence on Cabin Interlock chain 2 between input and output signals on Safety Interface Board (SIB). Consequences Paint enable chain opens. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 37226, HV Interlock chain 1 conflict Description Divergence on High Voltage (HV) Interlock chain 1 between input and output signals on Safety Interface Board (SIB). Consequences Paint enable chain opens. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 37227, HV Interlock chain 2 conflict Description Divergence on High Voltage (HV) Interlock chain 2 between input and output signals on Safety Interface Board (SIB). Consequences Paint enable chain opens. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 37228, Cabin Interlock chain conflict from SIB Description Only one of the two Cabin Interlock chains is opened. Reported from Safety Interface Board (SIB). Consequences Paint enable chain opens. Recommended actions Replace SIB if faulty. 37229, HV Interlock chain conflict from SIB Description Only one of the two High Voltage (HV) Interlock chains is opened. Reported from Safety Interface Board (SIB). Consequences Paint enable chain opens. Recommended actions Replace SIB if faulty. 37230, Brake Performance Warning Description The Cyclic Brake Check indicates that the brake for the mechanical unit arg axis no arg has not full braking torque. Consequences This is only a warning and no immediate action need to be taken. 37231, Brake Performance Error Description The Cyclic Brake Check has found that the brake for the mechanical unit arg axis no arg has too low braking torque. This brake will not be approved by the Safety Controller for Drive Module no arg . Consequences WARNING: The brake performance is too low for this axis. 6 Trouble shooting by Event log 168 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Until the brake has approved braking torque, it is only possible to move the robot with the specified "Reduced max speed (mm/s)" according to the setup in the Configurator for Cylic Brake Check. Recommended actions 1) Run the Cycle Brake Check once more. 2) Exchange the motor with its brake. 37232, Cyclic Brake Check Configuration Error Description The Cyclic Brake Check has found that the brake for the mechanical unit arg axis no arg has no defined brake torque requirement level. Consequences The Cyclic Brake Check will continue but no valid brake check will be done for this axis. Probable causes The motion configuration data are not correct specified for this axis. Recommended actions The motion configuration data are not correct specified for this axis: 1) Specify a value for parameter max_static_arm_torque if axis shell be tested. 2) Deactivate Cyclic Brake Check in motion configuration if axis not to be tested. 37233, Cyclic Brake Check Configuration Error Description The Cyclic Brake Check has found that the brake for the mechanical unit arg axis no arg should be tested according to the configuration. But the actual mechanical unit can not be included in the Safety Controller, because activation/deactivation at runtime is allowed. Consequences The Cyclic Brake Check will continue with other mechanical units. Probable causes The motion configuration data are not correct specified for this axis. Recommended actions The motion configuration data are not correct specified for this axis: 1) Cyclic Brake Check has been specified but should not be done for this axis 2) The mechanical unit must be active at startup and deactivation must not be allowed 37240, Cabin Interlock chain conflict from MIB Description Only one of the two cabin interlock chains is opened. Reported from Manipulator Interface Board (MIB) arg . Consequences Paint enable chain opens. Recommended actions Replace MIB if faulty. 37241, HV Interlock chain conflict from MIB Description Only one of the two High Voltage (HV) chains is opened. Reported from Manipulator Interface Board (MIB) arg . Consequences Paint enable chain opens. Recommended actions Replace MIB if faulty. 37242, Run chain conflict from SIB Description Only one of the two run chain feedback signals from Safety Interface Board (SIB) was opened. Consequences The system goes to status SYS HALT. Recommended actions Replace SIB if faulty. 37243, Brake chain conflict from SIB Description Only one of the two brake chain signals from Safety Interface Board (SIB) was opened. Consequences The system goes to status SYS HALT. Recommended actions Replace SIB if faulty. 37244, Run chain conflict from MIB arg Description Only one of the two run chain feedback signals from Manipulator Interface Board (MIB) was opened. Consequences The system goes to status SYS HALT. Recommended actions Replace MIB if faulty. 37245, Brake chain conflict from MIB arg Description Only one of the two brake chain feedback signals from Manipulator Interface Board (MIB) was opened.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	170	6 Trouble shooting by Event log 167 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 37223, Main relay chain feedback conflict Description Safety Interface Board (SIB) and Manipulator Interface Board (MIB) arg reports divergence on Main relay chain feedback signals. Consequences The system goes to status SYS HALT. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 3. Replace MIB if faulty. 37224, Cabin Interlock chain 1 conflict Description Divergence on Cabin Interlock chain 1 between input and output signals on Safety Interface Board (SIB). Consequences Paint enable chain opens. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 37225, Cabin Interlock chain 2 conflict Description Divergence on Cabin Interlock chain 2 between input and output signals on Safety Interface Board (SIB). Consequences Paint enable chain opens. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 37226, HV Interlock chain 1 conflict Description Divergence on High Voltage (HV) Interlock chain 1 between input and output signals on Safety Interface Board (SIB). Consequences Paint enable chain opens. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 37227, HV Interlock chain 2 conflict Description Divergence on High Voltage (HV) Interlock chain 2 between input and output signals on Safety Interface Board (SIB). Consequences Paint enable chain opens. Recommended actions 1. Check cables and connections. 2. Replace SIB if faulty. 37228, Cabin Interlock chain conflict from SIB Description Only one of the two Cabin Interlock chains is opened. Reported from Safety Interface Board (SIB). Consequences Paint enable chain opens. Recommended actions Replace SIB if faulty. 37229, HV Interlock chain conflict from SIB Description Only one of the two High Voltage (HV) Interlock chains is opened. Reported from Safety Interface Board (SIB). Consequences Paint enable chain opens. Recommended actions Replace SIB if faulty. 37230, Brake Performance Warning Description The Cyclic Brake Check indicates that the brake for the mechanical unit arg axis no arg has not full braking torque. Consequences This is only a warning and no immediate action need to be taken. 37231, Brake Performance Error Description The Cyclic Brake Check has found that the brake for the mechanical unit arg axis no arg has too low braking torque. This brake will not be approved by the Safety Controller for Drive Module no arg . Consequences WARNING: The brake performance is too low for this axis. 6 Trouble shooting by Event log 168 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Until the brake has approved braking torque, it is only possible to move the robot with the specified "Reduced max speed (mm/s)" according to the setup in the Configurator for Cylic Brake Check. Recommended actions 1) Run the Cycle Brake Check once more. 2) Exchange the motor with its brake. 37232, Cyclic Brake Check Configuration Error Description The Cyclic Brake Check has found that the brake for the mechanical unit arg axis no arg has no defined brake torque requirement level. Consequences The Cyclic Brake Check will continue but no valid brake check will be done for this axis. Probable causes The motion configuration data are not correct specified for this axis. Recommended actions The motion configuration data are not correct specified for this axis: 1) Specify a value for parameter max_static_arm_torque if axis shell be tested. 2) Deactivate Cyclic Brake Check in motion configuration if axis not to be tested. 37233, Cyclic Brake Check Configuration Error Description The Cyclic Brake Check has found that the brake for the mechanical unit arg axis no arg should be tested according to the configuration. But the actual mechanical unit can not be included in the Safety Controller, because activation/deactivation at runtime is allowed. Consequences The Cyclic Brake Check will continue with other mechanical units. Probable causes The motion configuration data are not correct specified for this axis. Recommended actions The motion configuration data are not correct specified for this axis: 1) Cyclic Brake Check has been specified but should not be done for this axis 2) The mechanical unit must be active at startup and deactivation must not be allowed 37240, Cabin Interlock chain conflict from MIB Description Only one of the two cabin interlock chains is opened. Reported from Manipulator Interface Board (MIB) arg . Consequences Paint enable chain opens. Recommended actions Replace MIB if faulty. 37241, HV Interlock chain conflict from MIB Description Only one of the two High Voltage (HV) chains is opened. Reported from Manipulator Interface Board (MIB) arg . Consequences Paint enable chain opens. Recommended actions Replace MIB if faulty. 37242, Run chain conflict from SIB Description Only one of the two run chain feedback signals from Safety Interface Board (SIB) was opened. Consequences The system goes to status SYS HALT. Recommended actions Replace SIB if faulty. 37243, Brake chain conflict from SIB Description Only one of the two brake chain signals from Safety Interface Board (SIB) was opened. Consequences The system goes to status SYS HALT. Recommended actions Replace SIB if faulty. 37244, Run chain conflict from MIB arg Description Only one of the two run chain feedback signals from Manipulator Interface Board (MIB) was opened. Consequences The system goes to status SYS HALT. Recommended actions Replace MIB if faulty. 37245, Brake chain conflict from MIB arg Description Only one of the two brake chain feedback signals from Manipulator Interface Board (MIB) was opened. 6 Trouble shooting by Event log 169 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences The system goes to status SYS HALT. Recommended actions Replace MIB if faulty. 37246, Emergency Stop relay conflict Description Only one of the two Emergency Stop chains was opened internal on Safety Interface Board (SIB). Consequences The system remains in the Emergency Stop status. Recommended actions 1. Press emergency stop and reset emergency stop once again. 2. Replace SIB if faulty. 37247, Circulation Fan arg malfunction Description Circulation fan for the drive systems at the cabinet rear side has stopped or is rotating very slowly. Consequences The drive systems temperature will rise. Probable causes Faulty fan, cabling or power supply. See the Circuit Diagram! Recommended actions 1. Check the fan cables. 2. Check the power supply. 3. Check the fan. 37248, Circulation Fan arg malfunction Description Circulation fan in the cabinet front door has stopped or is rotating very slowly. Consequences The temperature in the cabinet will rise. Probable causes Faulty fan, cabling or power supply. See the Circuit Diagram! Recommended actions 1. Check the fan cables. 2. Check the power supply. 3. Check the fan. 37501, Filesystem unknown: USB Device Description The filesystem type on the USB device with logical unit arg is not supported. Consequences The USB device with the logical unit arg cannot be accessed. The filesystem is of type arg . The file(s) on the USB device with logical number arg will not be accessible. Probable causes The filesystem is formatted with an unsupported file system type. Recommended actions Format the USB device with the FAT32 filesystem. 37502, Mass storage device removed Description The mass storage device was removed. Consequences The system goes to sys fail. The filesystem on the mass storage device could be corrupt. The file(s) on the mass storage device could be corrupt. The file(s) on the mass storage device will not be accessible. Probable causes The mass storage device was removed or there was a malfunction of the mass storage device. Recommended actions Check that the mass storage device firmly is in place. If the problem persists, try with another device. 38100, Configuration failure Description Drive Module has detected configuration failure at measurement link. Drive module: arg Measurement link: arg Board node: arg Recommended actions - Check configuration for measurement link. - Check configuration for measurement board. - Check configuration for measurement nodes. 38101, SMB Communication Failure Description A transmission failure has been detected between the axis computer and the serial measurement board on measurement link arg in Drive Module arg . Consequences The system goes to status SYS FAIL and loses its calibration information.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	171	6 Trouble shooting by Event log 168 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Until the brake has approved braking torque, it is only possible to move the robot with the specified "Reduced max speed (mm/s)" according to the setup in the Configurator for Cylic Brake Check. Recommended actions 1) Run the Cycle Brake Check once more. 2) Exchange the motor with its brake. 37232, Cyclic Brake Check Configuration Error Description The Cyclic Brake Check has found that the brake for the mechanical unit arg axis no arg has no defined brake torque requirement level. Consequences The Cyclic Brake Check will continue but no valid brake check will be done for this axis. Probable causes The motion configuration data are not correct specified for this axis. Recommended actions The motion configuration data are not correct specified for this axis: 1) Specify a value for parameter max_static_arm_torque if axis shell be tested. 2) Deactivate Cyclic Brake Check in motion configuration if axis not to be tested. 37233, Cyclic Brake Check Configuration Error Description The Cyclic Brake Check has found that the brake for the mechanical unit arg axis no arg should be tested according to the configuration. But the actual mechanical unit can not be included in the Safety Controller, because activation/deactivation at runtime is allowed. Consequences The Cyclic Brake Check will continue with other mechanical units. Probable causes The motion configuration data are not correct specified for this axis. Recommended actions The motion configuration data are not correct specified for this axis: 1) Cyclic Brake Check has been specified but should not be done for this axis 2) The mechanical unit must be active at startup and deactivation must not be allowed 37240, Cabin Interlock chain conflict from MIB Description Only one of the two cabin interlock chains is opened. Reported from Manipulator Interface Board (MIB) arg . Consequences Paint enable chain opens. Recommended actions Replace MIB if faulty. 37241, HV Interlock chain conflict from MIB Description Only one of the two High Voltage (HV) chains is opened. Reported from Manipulator Interface Board (MIB) arg . Consequences Paint enable chain opens. Recommended actions Replace MIB if faulty. 37242, Run chain conflict from SIB Description Only one of the two run chain feedback signals from Safety Interface Board (SIB) was opened. Consequences The system goes to status SYS HALT. Recommended actions Replace SIB if faulty. 37243, Brake chain conflict from SIB Description Only one of the two brake chain signals from Safety Interface Board (SIB) was opened. Consequences The system goes to status SYS HALT. Recommended actions Replace SIB if faulty. 37244, Run chain conflict from MIB arg Description Only one of the two run chain feedback signals from Manipulator Interface Board (MIB) was opened. Consequences The system goes to status SYS HALT. Recommended actions Replace MIB if faulty. 37245, Brake chain conflict from MIB arg Description Only one of the two brake chain feedback signals from Manipulator Interface Board (MIB) was opened. 6 Trouble shooting by Event log 169 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences The system goes to status SYS HALT. Recommended actions Replace MIB if faulty. 37246, Emergency Stop relay conflict Description Only one of the two Emergency Stop chains was opened internal on Safety Interface Board (SIB). Consequences The system remains in the Emergency Stop status. Recommended actions 1. Press emergency stop and reset emergency stop once again. 2. Replace SIB if faulty. 37247, Circulation Fan arg malfunction Description Circulation fan for the drive systems at the cabinet rear side has stopped or is rotating very slowly. Consequences The drive systems temperature will rise. Probable causes Faulty fan, cabling or power supply. See the Circuit Diagram! Recommended actions 1. Check the fan cables. 2. Check the power supply. 3. Check the fan. 37248, Circulation Fan arg malfunction Description Circulation fan in the cabinet front door has stopped or is rotating very slowly. Consequences The temperature in the cabinet will rise. Probable causes Faulty fan, cabling or power supply. See the Circuit Diagram! Recommended actions 1. Check the fan cables. 2. Check the power supply. 3. Check the fan. 37501, Filesystem unknown: USB Device Description The filesystem type on the USB device with logical unit arg is not supported. Consequences The USB device with the logical unit arg cannot be accessed. The filesystem is of type arg . The file(s) on the USB device with logical number arg will not be accessible. Probable causes The filesystem is formatted with an unsupported file system type. Recommended actions Format the USB device with the FAT32 filesystem. 37502, Mass storage device removed Description The mass storage device was removed. Consequences The system goes to sys fail. The filesystem on the mass storage device could be corrupt. The file(s) on the mass storage device could be corrupt. The file(s) on the mass storage device will not be accessible. Probable causes The mass storage device was removed or there was a malfunction of the mass storage device. Recommended actions Check that the mass storage device firmly is in place. If the problem persists, try with another device. 38100, Configuration failure Description Drive Module has detected configuration failure at measurement link. Drive module: arg Measurement link: arg Board node: arg Recommended actions - Check configuration for measurement link. - Check configuration for measurement board. - Check configuration for measurement nodes. 38101, SMB Communication Failure Description A transmission failure has been detected between the axis computer and the serial measurement board on measurement link arg in Drive Module arg . Consequences The system goes to status SYS FAIL and loses its calibration information. 6 Trouble shooting by Event log 170 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes This may be caused by bad connections or cables (screening), especially if non-ABB cables are used for additional axes. Possible causes are also faulty serial measurement board or axis computer. Recommended actions 1) Reset the robot's revolution counters as detailed in the robot Product Manual. 2) Make sure the cable between serial measurement board and axis computer is connected correctly, and that it meets the specification set by ABB. 3) Make sure the cable screen is correctly connected at both ends. 4) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling. 5) Make sure the serial measurement board and axis computer are fully functional. Replace any faulty unit. 38102, Internal failure Description The measurement system has detected a hardware or software fault on measurement link arg in Drive Module arg . Consequences The system goes to status SYS HALT and loses its calibration information. Probable causes This may be caused by some temporary disturbance in the robot cell or by a faulty axis computer. Recommended actions 1) Restart the system. 2) Reset the robot's revolution counters as detailed in the robot Product Manual. 3) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling. 4) Make sure the axis computer is fully functional. Replace any faulty unit. 38103, Lost communication with the SMB Description The communication has been lost between the axis computer and the serial measurement board on measurement link arg in Drive Module arg . Consequences The system goes to status SYS HALT and loses its calibration information. Probable causes This may be caused by bad connections or cables (screening), especially if non-ABB cables are used for additional axes. Possible causes are also faulty serial measurement board or axis computer. Recommended actions 1) Reset the robot's revolution counters as detailed in the robot Product Manual. 2) Make sure the cable between serial measurement board and axis computer is connected correctly, and that it meets the specification set by ABB. 3) Make sure the cable screen is correctly connected at both ends. 4) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling. 5) Make sure the serial measurement board and axis computer are fully functional. Replace any faulty unit. 38104, Overspeed During Teach Mode Description One or more axes of the robot connected to drive module arg has exceeded the maximum speed for teach mode operation. Consequences The system goes to status SYS HALT. Probable causes The robot may have been moved manually while in state Motors OFF. The error may also be caused by a misadjustment in the relation, commutation, between motor shaft and resolver on an additional axis, primarily during installation. Recommended actions 1) Press the Enabling Device to attempt resuming operation. 2) Check other event log messages occuring at the same time to determine the actual cause. 3) Perform a re-commutation of the motor at hand. How to do this is specified in the Additional Axes Manual. 38105, Data not found. Description Configuration data for measurement board not found. System will use default data. Drive module: arg Measurement link: arg Board node: arg Recommended actions Check configuration. 38200, Battery backup lost Description The battery backup to serial measurement board (SMB) arg in the robot connected to drive module arg on measurement link arg has been lost. Consequences When the SMB battery power supply is interrupted, the robot will lose the revolution counter data. This warning will also repeatedly be logged.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	172	6 Trouble shooting by Event log 169 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences The system goes to status SYS HALT. Recommended actions Replace MIB if faulty. 37246, Emergency Stop relay conflict Description Only one of the two Emergency Stop chains was opened internal on Safety Interface Board (SIB). Consequences The system remains in the Emergency Stop status. Recommended actions 1. Press emergency stop and reset emergency stop once again. 2. Replace SIB if faulty. 37247, Circulation Fan arg malfunction Description Circulation fan for the drive systems at the cabinet rear side has stopped or is rotating very slowly. Consequences The drive systems temperature will rise. Probable causes Faulty fan, cabling or power supply. See the Circuit Diagram! Recommended actions 1. Check the fan cables. 2. Check the power supply. 3. Check the fan. 37248, Circulation Fan arg malfunction Description Circulation fan in the cabinet front door has stopped or is rotating very slowly. Consequences The temperature in the cabinet will rise. Probable causes Faulty fan, cabling or power supply. See the Circuit Diagram! Recommended actions 1. Check the fan cables. 2. Check the power supply. 3. Check the fan. 37501, Filesystem unknown: USB Device Description The filesystem type on the USB device with logical unit arg is not supported. Consequences The USB device with the logical unit arg cannot be accessed. The filesystem is of type arg . The file(s) on the USB device with logical number arg will not be accessible. Probable causes The filesystem is formatted with an unsupported file system type. Recommended actions Format the USB device with the FAT32 filesystem. 37502, Mass storage device removed Description The mass storage device was removed. Consequences The system goes to sys fail. The filesystem on the mass storage device could be corrupt. The file(s) on the mass storage device could be corrupt. The file(s) on the mass storage device will not be accessible. Probable causes The mass storage device was removed or there was a malfunction of the mass storage device. Recommended actions Check that the mass storage device firmly is in place. If the problem persists, try with another device. 38100, Configuration failure Description Drive Module has detected configuration failure at measurement link. Drive module: arg Measurement link: arg Board node: arg Recommended actions - Check configuration for measurement link. - Check configuration for measurement board. - Check configuration for measurement nodes. 38101, SMB Communication Failure Description A transmission failure has been detected between the axis computer and the serial measurement board on measurement link arg in Drive Module arg . Consequences The system goes to status SYS FAIL and loses its calibration information. 6 Trouble shooting by Event log 170 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes This may be caused by bad connections or cables (screening), especially if non-ABB cables are used for additional axes. Possible causes are also faulty serial measurement board or axis computer. Recommended actions 1) Reset the robot's revolution counters as detailed in the robot Product Manual. 2) Make sure the cable between serial measurement board and axis computer is connected correctly, and that it meets the specification set by ABB. 3) Make sure the cable screen is correctly connected at both ends. 4) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling. 5) Make sure the serial measurement board and axis computer are fully functional. Replace any faulty unit. 38102, Internal failure Description The measurement system has detected a hardware or software fault on measurement link arg in Drive Module arg . Consequences The system goes to status SYS HALT and loses its calibration information. Probable causes This may be caused by some temporary disturbance in the robot cell or by a faulty axis computer. Recommended actions 1) Restart the system. 2) Reset the robot's revolution counters as detailed in the robot Product Manual. 3) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling. 4) Make sure the axis computer is fully functional. Replace any faulty unit. 38103, Lost communication with the SMB Description The communication has been lost between the axis computer and the serial measurement board on measurement link arg in Drive Module arg . Consequences The system goes to status SYS HALT and loses its calibration information. Probable causes This may be caused by bad connections or cables (screening), especially if non-ABB cables are used for additional axes. Possible causes are also faulty serial measurement board or axis computer. Recommended actions 1) Reset the robot's revolution counters as detailed in the robot Product Manual. 2) Make sure the cable between serial measurement board and axis computer is connected correctly, and that it meets the specification set by ABB. 3) Make sure the cable screen is correctly connected at both ends. 4) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling. 5) Make sure the serial measurement board and axis computer are fully functional. Replace any faulty unit. 38104, Overspeed During Teach Mode Description One or more axes of the robot connected to drive module arg has exceeded the maximum speed for teach mode operation. Consequences The system goes to status SYS HALT. Probable causes The robot may have been moved manually while in state Motors OFF. The error may also be caused by a misadjustment in the relation, commutation, between motor shaft and resolver on an additional axis, primarily during installation. Recommended actions 1) Press the Enabling Device to attempt resuming operation. 2) Check other event log messages occuring at the same time to determine the actual cause. 3) Perform a re-commutation of the motor at hand. How to do this is specified in the Additional Axes Manual. 38105, Data not found. Description Configuration data for measurement board not found. System will use default data. Drive module: arg Measurement link: arg Board node: arg Recommended actions Check configuration. 38200, Battery backup lost Description The battery backup to serial measurement board (SMB) arg in the robot connected to drive module arg on measurement link arg has been lost. Consequences When the SMB battery power supply is interrupted, the robot will lose the revolution counter data. This warning will also repeatedly be logged. 6 Trouble shooting by Event log 171 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes This may be due to an SMB battery that is discharged or not connected. For some robot models, the SMB battery power is supplied through a jumper in the robot signal cable (refer to the IRC5 Circuit Diagram), and disconnecting the cable interrupts the battery power supply. Some earlier robot versions used rechargeable batteries, and these must be charged for at least 18 hrs before working correctly. Recommended actions 1) Make sure a charged SMB battery is connected to the board. 2) NOTE! Disconnecting the robot signal cable may disconnect the SMB battery power supply, triggering the battery warning to be logged. 3) Reset the battery power warning by updating the revolution counters as detailed in the Calibration or Product Manual. 4) Replace the battery if discharged. 38201, Serial Board not found Description Serial Measurement Board not found on measurement link. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Check system configuration parameters. - Check connections and cables to Serial Measurement Board. - Replace Serial Measurement Board. 38203, SMB offset X error Description Offset error for X signal at Serial Measurement Board. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Replace Serial Measurement Board. 38204, SMB offset Y error Description Offset error for Y signal at Serial Measurement Board. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Replace Serial Measurement Board 38205, SMB Linearity Error Description Linearity error for X-Y signal difference at Serial Measurement Board. System may still operate with warning. System will not function with error. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Replace Serial Measurement Board. 38206, SMB Linearity X Error Description Linearity error for X signal on Serial Measurement Board. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Replace Serial Measurement Board. 38207, SMB Linearity Y Error Description Linearity error for Y signal at Serial Measurement Board. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Replace Serial Measurement Board. 38208, Resolver error Description Too high voltage from X or Y resolver signals. Sum of squared X and Y exceeds max. Joint: arg Drive module: arg Measurement link: arg Measurement board: arg Board node: arg Recommended actions - Check resolver and resolver connections. - Replace Serial Measurement Board. - Replace resolver.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	173	6 Trouble shooting by Event log 170 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes This may be caused by bad connections or cables (screening), especially if non-ABB cables are used for additional axes. Possible causes are also faulty serial measurement board or axis computer. Recommended actions 1) Reset the robot's revolution counters as detailed in the robot Product Manual. 2) Make sure the cable between serial measurement board and axis computer is connected correctly, and that it meets the specification set by ABB. 3) Make sure the cable screen is correctly connected at both ends. 4) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling. 5) Make sure the serial measurement board and axis computer are fully functional. Replace any faulty unit. 38102, Internal failure Description The measurement system has detected a hardware or software fault on measurement link arg in Drive Module arg . Consequences The system goes to status SYS HALT and loses its calibration information. Probable causes This may be caused by some temporary disturbance in the robot cell or by a faulty axis computer. Recommended actions 1) Restart the system. 2) Reset the robot's revolution counters as detailed in the robot Product Manual. 3) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling. 4) Make sure the axis computer is fully functional. Replace any faulty unit. 38103, Lost communication with the SMB Description The communication has been lost between the axis computer and the serial measurement board on measurement link arg in Drive Module arg . Consequences The system goes to status SYS HALT and loses its calibration information. Probable causes This may be caused by bad connections or cables (screening), especially if non-ABB cables are used for additional axes. Possible causes are also faulty serial measurement board or axis computer. Recommended actions 1) Reset the robot's revolution counters as detailed in the robot Product Manual. 2) Make sure the cable between serial measurement board and axis computer is connected correctly, and that it meets the specification set by ABB. 3) Make sure the cable screen is correctly connected at both ends. 4) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling. 5) Make sure the serial measurement board and axis computer are fully functional. Replace any faulty unit. 38104, Overspeed During Teach Mode Description One or more axes of the robot connected to drive module arg has exceeded the maximum speed for teach mode operation. Consequences The system goes to status SYS HALT. Probable causes The robot may have been moved manually while in state Motors OFF. The error may also be caused by a misadjustment in the relation, commutation, between motor shaft and resolver on an additional axis, primarily during installation. Recommended actions 1) Press the Enabling Device to attempt resuming operation. 2) Check other event log messages occuring at the same time to determine the actual cause. 3) Perform a re-commutation of the motor at hand. How to do this is specified in the Additional Axes Manual. 38105, Data not found. Description Configuration data for measurement board not found. System will use default data. Drive module: arg Measurement link: arg Board node: arg Recommended actions Check configuration. 38200, Battery backup lost Description The battery backup to serial measurement board (SMB) arg in the robot connected to drive module arg on measurement link arg has been lost. Consequences When the SMB battery power supply is interrupted, the robot will lose the revolution counter data. This warning will also repeatedly be logged. 6 Trouble shooting by Event log 171 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes This may be due to an SMB battery that is discharged or not connected. For some robot models, the SMB battery power is supplied through a jumper in the robot signal cable (refer to the IRC5 Circuit Diagram), and disconnecting the cable interrupts the battery power supply. Some earlier robot versions used rechargeable batteries, and these must be charged for at least 18 hrs before working correctly. Recommended actions 1) Make sure a charged SMB battery is connected to the board. 2) NOTE! Disconnecting the robot signal cable may disconnect the SMB battery power supply, triggering the battery warning to be logged. 3) Reset the battery power warning by updating the revolution counters as detailed in the Calibration or Product Manual. 4) Replace the battery if discharged. 38201, Serial Board not found Description Serial Measurement Board not found on measurement link. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Check system configuration parameters. - Check connections and cables to Serial Measurement Board. - Replace Serial Measurement Board. 38203, SMB offset X error Description Offset error for X signal at Serial Measurement Board. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Replace Serial Measurement Board. 38204, SMB offset Y error Description Offset error for Y signal at Serial Measurement Board. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Replace Serial Measurement Board 38205, SMB Linearity Error Description Linearity error for X-Y signal difference at Serial Measurement Board. System may still operate with warning. System will not function with error. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Replace Serial Measurement Board. 38206, SMB Linearity X Error Description Linearity error for X signal on Serial Measurement Board. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Replace Serial Measurement Board. 38207, SMB Linearity Y Error Description Linearity error for Y signal at Serial Measurement Board. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Replace Serial Measurement Board. 38208, Resolver error Description Too high voltage from X or Y resolver signals. Sum of squared X and Y exceeds max. Joint: arg Drive module: arg Measurement link: arg Measurement board: arg Board node: arg Recommended actions - Check resolver and resolver connections. - Replace Serial Measurement Board. - Replace resolver. 6 Trouble shooting by Event log 172 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 38209, Resolver error Description Too low voltage from X or Y resolver signals. Sum of squared X and Y too low. Joint: arg Drive module: arg Measurement link: arg Measurement board: arg Board node: arg Recommended actions - Check resolver and resolver connections. - Replace Serial Measurement Board. - Replace resolver. 38210, Transmission fault. Description Serial Measurement Board SMS communication failed. Status: arg Drive module: arg Measurement link: arg Measurement board: arg Board node: arg Recommended actions - Restart system. - Check cable and connectors for SMB communication. - Replace the Serial Measurement Board. 38211, Functionality error. Description The Serial Measurement Board does not support 7 axes. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Check configurations of the 7th axis. - Replace Serial Measurement Board to a board with 7 axes functionality. 38212, Data not found. Description Configuration data for Serial Measurement Board not found. System will use default data. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Check configuration. 38213, Battery charge low. Description Less than 2 months until battery on Serial Measurement Board is discharged. Counting from first time this message was displayed. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Replace battery on serial measurement. 38214, Battery failure. Description Transportation shut down of battery failed. The battery will still be in normal mode. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Retry shut down. - Replace serial measurement board. 38215, Battery supervision failure. Description Failure occurred during reset of battery supervision circuit in Serial Measurement Board. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Repete update of revolution counter for joint connected to the SMB. - Replace serial measurement board. 38230, PMC card not connected correctly Description The PMC card that is configured in the motion configuration is not connected or is not working correctly. Consequences The application that needs this PMC card can not be ran. Probable causes The PMC card is not connected or the card is broken. Recommended actions Please check the PMC card that is attached to the axis computer in the drive module arg .
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	174	6 Trouble shooting by Event log 171 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes This may be due to an SMB battery that is discharged or not connected. For some robot models, the SMB battery power is supplied through a jumper in the robot signal cable (refer to the IRC5 Circuit Diagram), and disconnecting the cable interrupts the battery power supply. Some earlier robot versions used rechargeable batteries, and these must be charged for at least 18 hrs before working correctly. Recommended actions 1) Make sure a charged SMB battery is connected to the board. 2) NOTE! Disconnecting the robot signal cable may disconnect the SMB battery power supply, triggering the battery warning to be logged. 3) Reset the battery power warning by updating the revolution counters as detailed in the Calibration or Product Manual. 4) Replace the battery if discharged. 38201, Serial Board not found Description Serial Measurement Board not found on measurement link. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Check system configuration parameters. - Check connections and cables to Serial Measurement Board. - Replace Serial Measurement Board. 38203, SMB offset X error Description Offset error for X signal at Serial Measurement Board. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Replace Serial Measurement Board. 38204, SMB offset Y error Description Offset error for Y signal at Serial Measurement Board. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Replace Serial Measurement Board 38205, SMB Linearity Error Description Linearity error for X-Y signal difference at Serial Measurement Board. System may still operate with warning. System will not function with error. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Replace Serial Measurement Board. 38206, SMB Linearity X Error Description Linearity error for X signal on Serial Measurement Board. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Replace Serial Measurement Board. 38207, SMB Linearity Y Error Description Linearity error for Y signal at Serial Measurement Board. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Replace Serial Measurement Board. 38208, Resolver error Description Too high voltage from X or Y resolver signals. Sum of squared X and Y exceeds max. Joint: arg Drive module: arg Measurement link: arg Measurement board: arg Board node: arg Recommended actions - Check resolver and resolver connections. - Replace Serial Measurement Board. - Replace resolver. 6 Trouble shooting by Event log 172 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 38209, Resolver error Description Too low voltage from X or Y resolver signals. Sum of squared X and Y too low. Joint: arg Drive module: arg Measurement link: arg Measurement board: arg Board node: arg Recommended actions - Check resolver and resolver connections. - Replace Serial Measurement Board. - Replace resolver. 38210, Transmission fault. Description Serial Measurement Board SMS communication failed. Status: arg Drive module: arg Measurement link: arg Measurement board: arg Board node: arg Recommended actions - Restart system. - Check cable and connectors for SMB communication. - Replace the Serial Measurement Board. 38211, Functionality error. Description The Serial Measurement Board does not support 7 axes. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Check configurations of the 7th axis. - Replace Serial Measurement Board to a board with 7 axes functionality. 38212, Data not found. Description Configuration data for Serial Measurement Board not found. System will use default data. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Check configuration. 38213, Battery charge low. Description Less than 2 months until battery on Serial Measurement Board is discharged. Counting from first time this message was displayed. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Replace battery on serial measurement. 38214, Battery failure. Description Transportation shut down of battery failed. The battery will still be in normal mode. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Retry shut down. - Replace serial measurement board. 38215, Battery supervision failure. Description Failure occurred during reset of battery supervision circuit in Serial Measurement Board. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Repete update of revolution counter for joint connected to the SMB. - Replace serial measurement board. 38230, PMC card not connected correctly Description The PMC card that is configured in the motion configuration is not connected or is not working correctly. Consequences The application that needs this PMC card can not be ran. Probable causes The PMC card is not connected or the card is broken. Recommended actions Please check the PMC card that is attached to the axis computer in the drive module arg . 6 Trouble shooting by Event log 173 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 38231, PMC card can not be started Description The PMC card that is configured in the motion configuration is not set up correctly and can not be started. Consequences The application that uses this PMC card can not be ran. Probable causes The error is problably a error in the motion configuration. Recommended actions Please check the limits for channels for this card in the motion configuration. 38232, PMC max channels reached Description The PMC card that is configured in the motion configuration is not set up correctly and can not be started. Consequences The application that uses this PMC card can not be ran. Probable causes The error is problably a error in the motion configuration. Recommended actions Please check the limits for channels for this card in the motion configuration. 38233, Force sensor safety channel error Description The safety channel in the cable between the force sensor and measurment board is under configured safety channel voltage level. The force sensor is connected to the axis computer in drive module arg . Consequences The system will go to SYS HALT and the application that uses this sensor can not be ran until cable is connected or replaced. Safety channel supervision can be disconnected in the motion configuraion. Probable causes 1. The cable is not attached correctly. 2. The cable has damage to the connectors or the cable itself. 3. The sensor cable does not have satefy channel. Recommended actions Assure that the cable is connected properlly and inspect the connectors at both ends of the cable and the cable itself. Replace if damaged. 38234, Max Force or Torque reached Description The measurend force or torque in the force sensor attached to the axis computer in drive module arg has higher value than it is configured for. Consequences The system will not stop due to this. Probable causes The appliced force or torque on the sensor is higher that configured. Too high ordered reference can be the cause. The configuration might also be faulty. Recommended actions Check the force and torque references in the program and if the environment have applied too high force or torque to the sensor. 38235, Saturation warning of force sensor input Description The analog input values of the measurment board connected to the force sensor have saturated and the time in saturation has reached the warning level. The measurment board is connected to the axis computer in drive module arg Recommended actions Check the load that was applied to the force/torque sensor. Check that the cable, sensor and measurment board is not damaged. Increase the system parameter: time in satuartion before warning 38236, Saturation error of of force sensor input Description The analog input values of the measurment board connected to the force sensor have saturated and the time in saturation has reached the error level. The measurment board is connected to the axis computer in drive module arg Consequences system will stop Recommended actions Check the load that was applied to the force/torque sensor. Check that the cable, sensor and measurment board is not damaged. Increase the system parameter: time in satuartion before error 38237, Configuration error for Force Measurement Board Description The configuration input values for the Force Measurement Board connected to the force sensor is erroneous. The board is connected to drive module arg , link arg . Consequences The system goes to System Failure state.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	175	6 Trouble shooting by Event log 172 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 38209, Resolver error Description Too low voltage from X or Y resolver signals. Sum of squared X and Y too low. Joint: arg Drive module: arg Measurement link: arg Measurement board: arg Board node: arg Recommended actions - Check resolver and resolver connections. - Replace Serial Measurement Board. - Replace resolver. 38210, Transmission fault. Description Serial Measurement Board SMS communication failed. Status: arg Drive module: arg Measurement link: arg Measurement board: arg Board node: arg Recommended actions - Restart system. - Check cable and connectors for SMB communication. - Replace the Serial Measurement Board. 38211, Functionality error. Description The Serial Measurement Board does not support 7 axes. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Check configurations of the 7th axis. - Replace Serial Measurement Board to a board with 7 axes functionality. 38212, Data not found. Description Configuration data for Serial Measurement Board not found. System will use default data. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Check configuration. 38213, Battery charge low. Description Less than 2 months until battery on Serial Measurement Board is discharged. Counting from first time this message was displayed. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Replace battery on serial measurement. 38214, Battery failure. Description Transportation shut down of battery failed. The battery will still be in normal mode. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Retry shut down. - Replace serial measurement board. 38215, Battery supervision failure. Description Failure occurred during reset of battery supervision circuit in Serial Measurement Board. Drive module: arg Measurement link: arg Measurement board: arg Recommended actions - Repete update of revolution counter for joint connected to the SMB. - Replace serial measurement board. 38230, PMC card not connected correctly Description The PMC card that is configured in the motion configuration is not connected or is not working correctly. Consequences The application that needs this PMC card can not be ran. Probable causes The PMC card is not connected or the card is broken. Recommended actions Please check the PMC card that is attached to the axis computer in the drive module arg . 6 Trouble shooting by Event log 173 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 38231, PMC card can not be started Description The PMC card that is configured in the motion configuration is not set up correctly and can not be started. Consequences The application that uses this PMC card can not be ran. Probable causes The error is problably a error in the motion configuration. Recommended actions Please check the limits for channels for this card in the motion configuration. 38232, PMC max channels reached Description The PMC card that is configured in the motion configuration is not set up correctly and can not be started. Consequences The application that uses this PMC card can not be ran. Probable causes The error is problably a error in the motion configuration. Recommended actions Please check the limits for channels for this card in the motion configuration. 38233, Force sensor safety channel error Description The safety channel in the cable between the force sensor and measurment board is under configured safety channel voltage level. The force sensor is connected to the axis computer in drive module arg . Consequences The system will go to SYS HALT and the application that uses this sensor can not be ran until cable is connected or replaced. Safety channel supervision can be disconnected in the motion configuraion. Probable causes 1. The cable is not attached correctly. 2. The cable has damage to the connectors or the cable itself. 3. The sensor cable does not have satefy channel. Recommended actions Assure that the cable is connected properlly and inspect the connectors at both ends of the cable and the cable itself. Replace if damaged. 38234, Max Force or Torque reached Description The measurend force or torque in the force sensor attached to the axis computer in drive module arg has higher value than it is configured for. Consequences The system will not stop due to this. Probable causes The appliced force or torque on the sensor is higher that configured. Too high ordered reference can be the cause. The configuration might also be faulty. Recommended actions Check the force and torque references in the program and if the environment have applied too high force or torque to the sensor. 38235, Saturation warning of force sensor input Description The analog input values of the measurment board connected to the force sensor have saturated and the time in saturation has reached the warning level. The measurment board is connected to the axis computer in drive module arg Recommended actions Check the load that was applied to the force/torque sensor. Check that the cable, sensor and measurment board is not damaged. Increase the system parameter: time in satuartion before warning 38236, Saturation error of of force sensor input Description The analog input values of the measurment board connected to the force sensor have saturated and the time in saturation has reached the error level. The measurment board is connected to the axis computer in drive module arg Consequences system will stop Recommended actions Check the load that was applied to the force/torque sensor. Check that the cable, sensor and measurment board is not damaged. Increase the system parameter: time in satuartion before error 38237, Configuration error for Force Measurement Board Description The configuration input values for the Force Measurement Board connected to the force sensor is erroneous. The board is connected to drive module arg , link arg . Consequences The system goes to System Failure state. 6 Trouble shooting by Event log 174 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Check the configuration. 39401, Torque Current Reference Error Description The torque-current reference is increasing too quickly for joint arg , connected to drive module arg . Consequences - Probable causes The resolver feedback may be poor or the speed loop gain may be badly adjusted. Recommended actions 1) Check the resolver cable and the resolver grounding for this joint. If this joint is an additional axis, then check that the motor data in the configuration file is correct. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Reduce the gain of the speed loop. 39402, Motor Angle Reference Warning Description The motor angle reference is increasing too quickly for joint arg , connected to drive module arg . Consequences - Probable causes The resolver feedback may be poor or the speed loop gain may be badly adjusted. Recommended actions 1) Check the resolver cable and the resolver grounding for this joint. If this joint is an additional axis, then check that the motor data in the configuration file is correct. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Reduce the gain of the speed loop. 39403, Torque Loop Undercurrent Description The torque-current controller detected too low current for joint arg , connected to drive module arg . Consequences - Probable causes The motor data in the configuration files may be wrong or the DC bus voltage may be too low. Recommended actions 1) Check that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Check that no DC bus errors are present in the event log. 3) Check that the incoming mains voltage is within the specification. 4) Check that the motor cables are not damaged or badly connected. 39404, Torque Loop Overcurrent Description The field-current controller detected too high current for joint arg , connected to drive module arg . Consequences - Probable causes The motor data in the configuration files may be wrong. Recommended actions 1) Check that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Check that no DC bus errors are present in the event log. 3) Check that the incoming mains voltage is within the specification. 4) Check that the motor cables are not damaged or badly connected. 39405, Maximum PWM Reached in Torque Controller Description The torque-current control loop has been saturated for joint arg , connected to drive module arg . Consequences - Probable causes The mains voltage may be too low or the motor windings or motor cables may be broken. Recommended actions 1) Check that no DC bus errors are present in the event log. 2) Check that the incoming mains voltage is within specified limits. 3) Check the motor cables and motor windings for open circuits. 39406, Field Loop overcurrent Description The field-current control loop has produced too high current for joint arg , connected to drive module arg . Consequences -
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	176	6 Trouble shooting by Event log 173 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 38231, PMC card can not be started Description The PMC card that is configured in the motion configuration is not set up correctly and can not be started. Consequences The application that uses this PMC card can not be ran. Probable causes The error is problably a error in the motion configuration. Recommended actions Please check the limits for channels for this card in the motion configuration. 38232, PMC max channels reached Description The PMC card that is configured in the motion configuration is not set up correctly and can not be started. Consequences The application that uses this PMC card can not be ran. Probable causes The error is problably a error in the motion configuration. Recommended actions Please check the limits for channels for this card in the motion configuration. 38233, Force sensor safety channel error Description The safety channel in the cable between the force sensor and measurment board is under configured safety channel voltage level. The force sensor is connected to the axis computer in drive module arg . Consequences The system will go to SYS HALT and the application that uses this sensor can not be ran until cable is connected or replaced. Safety channel supervision can be disconnected in the motion configuraion. Probable causes 1. The cable is not attached correctly. 2. The cable has damage to the connectors or the cable itself. 3. The sensor cable does not have satefy channel. Recommended actions Assure that the cable is connected properlly and inspect the connectors at both ends of the cable and the cable itself. Replace if damaged. 38234, Max Force or Torque reached Description The measurend force or torque in the force sensor attached to the axis computer in drive module arg has higher value than it is configured for. Consequences The system will not stop due to this. Probable causes The appliced force or torque on the sensor is higher that configured. Too high ordered reference can be the cause. The configuration might also be faulty. Recommended actions Check the force and torque references in the program and if the environment have applied too high force or torque to the sensor. 38235, Saturation warning of force sensor input Description The analog input values of the measurment board connected to the force sensor have saturated and the time in saturation has reached the warning level. The measurment board is connected to the axis computer in drive module arg Recommended actions Check the load that was applied to the force/torque sensor. Check that the cable, sensor and measurment board is not damaged. Increase the system parameter: time in satuartion before warning 38236, Saturation error of of force sensor input Description The analog input values of the measurment board connected to the force sensor have saturated and the time in saturation has reached the error level. The measurment board is connected to the axis computer in drive module arg Consequences system will stop Recommended actions Check the load that was applied to the force/torque sensor. Check that the cable, sensor and measurment board is not damaged. Increase the system parameter: time in satuartion before error 38237, Configuration error for Force Measurement Board Description The configuration input values for the Force Measurement Board connected to the force sensor is erroneous. The board is connected to drive module arg , link arg . Consequences The system goes to System Failure state. 6 Trouble shooting by Event log 174 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Check the configuration. 39401, Torque Current Reference Error Description The torque-current reference is increasing too quickly for joint arg , connected to drive module arg . Consequences - Probable causes The resolver feedback may be poor or the speed loop gain may be badly adjusted. Recommended actions 1) Check the resolver cable and the resolver grounding for this joint. If this joint is an additional axis, then check that the motor data in the configuration file is correct. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Reduce the gain of the speed loop. 39402, Motor Angle Reference Warning Description The motor angle reference is increasing too quickly for joint arg , connected to drive module arg . Consequences - Probable causes The resolver feedback may be poor or the speed loop gain may be badly adjusted. Recommended actions 1) Check the resolver cable and the resolver grounding for this joint. If this joint is an additional axis, then check that the motor data in the configuration file is correct. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Reduce the gain of the speed loop. 39403, Torque Loop Undercurrent Description The torque-current controller detected too low current for joint arg , connected to drive module arg . Consequences - Probable causes The motor data in the configuration files may be wrong or the DC bus voltage may be too low. Recommended actions 1) Check that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Check that no DC bus errors are present in the event log. 3) Check that the incoming mains voltage is within the specification. 4) Check that the motor cables are not damaged or badly connected. 39404, Torque Loop Overcurrent Description The field-current controller detected too high current for joint arg , connected to drive module arg . Consequences - Probable causes The motor data in the configuration files may be wrong. Recommended actions 1) Check that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Check that no DC bus errors are present in the event log. 3) Check that the incoming mains voltage is within the specification. 4) Check that the motor cables are not damaged or badly connected. 39405, Maximum PWM Reached in Torque Controller Description The torque-current control loop has been saturated for joint arg , connected to drive module arg . Consequences - Probable causes The mains voltage may be too low or the motor windings or motor cables may be broken. Recommended actions 1) Check that no DC bus errors are present in the event log. 2) Check that the incoming mains voltage is within specified limits. 3) Check the motor cables and motor windings for open circuits. 39406, Field Loop overcurrent Description The field-current control loop has produced too high current for joint arg , connected to drive module arg . Consequences - 6 Trouble shooting by Event log 175 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes The motor data in the configuration files may be wrong. Recommended actions 1) Check that no DC bus errors are present in the event log. 2) Check that the incoming mains is within specified limits. 3) Check the motor cables and motor windings. 39407, Drive Unit has the wrong type code Description The type code in drive unit for joint arg in drive module arg is different from the one specified in the configuration file. Installed drive unit type is arg , and the configured type is arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The configuration file may contain incorrect values, the configuration key may be incorrect or the hardware may be of the wrong type. If the drive unit was recently replaced, a drive unit with the wrong type code may have been fitted or the key was not replaced with one for the correct hardware/software combination. Recommended actions 1) Make sure the values in the configuration file match the installed hardware. 2) Make sure the configuration key match the installed hardware/ software combination. How to check the configuration file is detailed in the Trouble Shooting Manual. 3) If the drive unit was recently replaced, make sure a unit of the correct type code is used. 39408, Rectifier Unit has the wrong type code Description The type code for rectifier unit arg in drive module arg is different from the one specified in the configuration file. Installed rectifier unit type is arg , and the configured type is arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The configuration file may contain incorrect values, the configuration key may be incorrect or the hardware may be of the wrong type. If the rectifier unit was recently replaced, a rectifier unit with the wrong type code may have been fitted or the key was not replaced with one for the correct hardware/software combination. Recommended actions 1) Make sure the values in the configuration file match the installed hardware. 2) Make sure the configuration key match the installed hardware/ software combination. How to check the configuration file is detailed in the Trouble Shooting Manual. 3) If the rectifier unit was recently replaced, make sure a unit of the correct type code is used. 39409, Capacitor Unit has the wrong type code Description The type code for capacitor unit arg in drive module arg is different from the one specified in the configuration file. Installed capacitor unit type is arg , and the configured type is arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The configuration file may contain incorrect values, the configuration key may be incorrect or the hardware may be of the wrong type. If the capacitor unit was recently replaced, a capacitor unit with the wrong type code may have been fitted or the key was not replaced with one for the correct hardware/software combination. Recommended actions 1) Make sure the values in the configuration file match the installed hardware. 2) Make sure the configuration key match the installed hardware/ software combination. How to check the configuration file is detailed in the Trouble Shooting Manual. 3) If the capacitor unit was recently replaced, make sure a unit of the correct type code is used. 39410, Drive Unit communication warning Description Many communication errors are being detected between the axis computer and drive unit number arg in drive module arg . (error rate per time unit) Consequences If the number of communication errors increases further, there is a risk that the controller will be forced to stop Probable causes External noise may interfere with the communication signals. Recommended actions 1) Check the communication link cable between the axis computer and the main drive unit is correctly connected. 2) Check that the module is properly grounded. 3) Check for external electromagnetic noise sources close to the drive module.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	177	6 Trouble shooting by Event log 174 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Check the configuration. 39401, Torque Current Reference Error Description The torque-current reference is increasing too quickly for joint arg , connected to drive module arg . Consequences - Probable causes The resolver feedback may be poor or the speed loop gain may be badly adjusted. Recommended actions 1) Check the resolver cable and the resolver grounding for this joint. If this joint is an additional axis, then check that the motor data in the configuration file is correct. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Reduce the gain of the speed loop. 39402, Motor Angle Reference Warning Description The motor angle reference is increasing too quickly for joint arg , connected to drive module arg . Consequences - Probable causes The resolver feedback may be poor or the speed loop gain may be badly adjusted. Recommended actions 1) Check the resolver cable and the resolver grounding for this joint. If this joint is an additional axis, then check that the motor data in the configuration file is correct. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Reduce the gain of the speed loop. 39403, Torque Loop Undercurrent Description The torque-current controller detected too low current for joint arg , connected to drive module arg . Consequences - Probable causes The motor data in the configuration files may be wrong or the DC bus voltage may be too low. Recommended actions 1) Check that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Check that no DC bus errors are present in the event log. 3) Check that the incoming mains voltage is within the specification. 4) Check that the motor cables are not damaged or badly connected. 39404, Torque Loop Overcurrent Description The field-current controller detected too high current for joint arg , connected to drive module arg . Consequences - Probable causes The motor data in the configuration files may be wrong. Recommended actions 1) Check that the motor data in the configuration file is correct for this joint. How to check the configuration file is detailed in the Trouble Shooting Manual. 2) Check that no DC bus errors are present in the event log. 3) Check that the incoming mains voltage is within the specification. 4) Check that the motor cables are not damaged or badly connected. 39405, Maximum PWM Reached in Torque Controller Description The torque-current control loop has been saturated for joint arg , connected to drive module arg . Consequences - Probable causes The mains voltage may be too low or the motor windings or motor cables may be broken. Recommended actions 1) Check that no DC bus errors are present in the event log. 2) Check that the incoming mains voltage is within specified limits. 3) Check the motor cables and motor windings for open circuits. 39406, Field Loop overcurrent Description The field-current control loop has produced too high current for joint arg , connected to drive module arg . Consequences - 6 Trouble shooting by Event log 175 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes The motor data in the configuration files may be wrong. Recommended actions 1) Check that no DC bus errors are present in the event log. 2) Check that the incoming mains is within specified limits. 3) Check the motor cables and motor windings. 39407, Drive Unit has the wrong type code Description The type code in drive unit for joint arg in drive module arg is different from the one specified in the configuration file. Installed drive unit type is arg , and the configured type is arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The configuration file may contain incorrect values, the configuration key may be incorrect or the hardware may be of the wrong type. If the drive unit was recently replaced, a drive unit with the wrong type code may have been fitted or the key was not replaced with one for the correct hardware/software combination. Recommended actions 1) Make sure the values in the configuration file match the installed hardware. 2) Make sure the configuration key match the installed hardware/ software combination. How to check the configuration file is detailed in the Trouble Shooting Manual. 3) If the drive unit was recently replaced, make sure a unit of the correct type code is used. 39408, Rectifier Unit has the wrong type code Description The type code for rectifier unit arg in drive module arg is different from the one specified in the configuration file. Installed rectifier unit type is arg , and the configured type is arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The configuration file may contain incorrect values, the configuration key may be incorrect or the hardware may be of the wrong type. If the rectifier unit was recently replaced, a rectifier unit with the wrong type code may have been fitted or the key was not replaced with one for the correct hardware/software combination. Recommended actions 1) Make sure the values in the configuration file match the installed hardware. 2) Make sure the configuration key match the installed hardware/ software combination. How to check the configuration file is detailed in the Trouble Shooting Manual. 3) If the rectifier unit was recently replaced, make sure a unit of the correct type code is used. 39409, Capacitor Unit has the wrong type code Description The type code for capacitor unit arg in drive module arg is different from the one specified in the configuration file. Installed capacitor unit type is arg , and the configured type is arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The configuration file may contain incorrect values, the configuration key may be incorrect or the hardware may be of the wrong type. If the capacitor unit was recently replaced, a capacitor unit with the wrong type code may have been fitted or the key was not replaced with one for the correct hardware/software combination. Recommended actions 1) Make sure the values in the configuration file match the installed hardware. 2) Make sure the configuration key match the installed hardware/ software combination. How to check the configuration file is detailed in the Trouble Shooting Manual. 3) If the capacitor unit was recently replaced, make sure a unit of the correct type code is used. 39410, Drive Unit communication warning Description Many communication errors are being detected between the axis computer and drive unit number arg in drive module arg . (error rate per time unit) Consequences If the number of communication errors increases further, there is a risk that the controller will be forced to stop Probable causes External noise may interfere with the communication signals. Recommended actions 1) Check the communication link cable between the axis computer and the main drive unit is correctly connected. 2) Check that the module is properly grounded. 3) Check for external electromagnetic noise sources close to the drive module. 6 Trouble shooting by Event log 176 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 39411, Too Many communication errors Description Four or more consecutive communication packets have been lost between the axis computer and drive unit arg in drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes There may be a break in the communication link cable between the axis computer and the main drive unit, the drive module may be incorrectly grounded or excessive noise may interfere with the communication signals. Recommended actions 1) Check the communication link cable between the axis computer and the main drive unit is correctly connected. 2) Check that the module is properly grounded. 3) Check for external electromagnetic noise sources close to the drive module. 39412, Too Many Missed Reference Updates Description Too many missed communication packets have been detected for joint arg , in drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes There may be a break in the communication link cable between the axis computer and the main drive unit, the drive module may be incorrectly grounded or excessive noise may interfere with the communication signals. Recommended actions 1) Check the communication link cable between the axis computer and the main drive unit is correctly connected. 2) Check that the module is properly grounded. 3) Check for external electromagnetic noise sources close to the drive module.. 39413, Drive Software Not Synchronised Description The axis computer software in drive module arg has become unsynchronised with the drive software for joint arg . This is an unstable software state. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes There may be glitches in the system timing. Recommended actions 1) Restart the controller. 2) If the problem persists, contact your local ABB representative.. 39414, Unknown Capacitor Type Code Description The type code for the capacitor unit arg in drive module arg is not recognised by the system. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The wrong type of capacitor unit may have been fitted or the capacitor version used is not supported by the software. Recommended actions 1) Check the type of capacitor unit fitted. Replace if it is the wrong type. 2) If the problem persists, contact your local ABB representative. 39415, Communication with the Drive Unit Lost Description Communication with drive unit number arg in drive module arg has been lost. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes There may be a break in the communication link cable between the axis computer and the main drive unit, the drive module may be incorrectly grounded or excessive noise may interfere with the communication signals. Recommended actions 1) Check the communication link cable between the axis computer and the main drive unit is correctly connected. 2) Check that the module is properly grounded. 3) Check for external electromagnetic noise sources close to the drive module.. 39416, Drive Unit Not Responding Description The main drive unit in drive module arg is not responding. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	178	6 Trouble shooting by Event log 175 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes The motor data in the configuration files may be wrong. Recommended actions 1) Check that no DC bus errors are present in the event log. 2) Check that the incoming mains is within specified limits. 3) Check the motor cables and motor windings. 39407, Drive Unit has the wrong type code Description The type code in drive unit for joint arg in drive module arg is different from the one specified in the configuration file. Installed drive unit type is arg , and the configured type is arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The configuration file may contain incorrect values, the configuration key may be incorrect or the hardware may be of the wrong type. If the drive unit was recently replaced, a drive unit with the wrong type code may have been fitted or the key was not replaced with one for the correct hardware/software combination. Recommended actions 1) Make sure the values in the configuration file match the installed hardware. 2) Make sure the configuration key match the installed hardware/ software combination. How to check the configuration file is detailed in the Trouble Shooting Manual. 3) If the drive unit was recently replaced, make sure a unit of the correct type code is used. 39408, Rectifier Unit has the wrong type code Description The type code for rectifier unit arg in drive module arg is different from the one specified in the configuration file. Installed rectifier unit type is arg , and the configured type is arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The configuration file may contain incorrect values, the configuration key may be incorrect or the hardware may be of the wrong type. If the rectifier unit was recently replaced, a rectifier unit with the wrong type code may have been fitted or the key was not replaced with one for the correct hardware/software combination. Recommended actions 1) Make sure the values in the configuration file match the installed hardware. 2) Make sure the configuration key match the installed hardware/ software combination. How to check the configuration file is detailed in the Trouble Shooting Manual. 3) If the rectifier unit was recently replaced, make sure a unit of the correct type code is used. 39409, Capacitor Unit has the wrong type code Description The type code for capacitor unit arg in drive module arg is different from the one specified in the configuration file. Installed capacitor unit type is arg , and the configured type is arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The configuration file may contain incorrect values, the configuration key may be incorrect or the hardware may be of the wrong type. If the capacitor unit was recently replaced, a capacitor unit with the wrong type code may have been fitted or the key was not replaced with one for the correct hardware/software combination. Recommended actions 1) Make sure the values in the configuration file match the installed hardware. 2) Make sure the configuration key match the installed hardware/ software combination. How to check the configuration file is detailed in the Trouble Shooting Manual. 3) If the capacitor unit was recently replaced, make sure a unit of the correct type code is used. 39410, Drive Unit communication warning Description Many communication errors are being detected between the axis computer and drive unit number arg in drive module arg . (error rate per time unit) Consequences If the number of communication errors increases further, there is a risk that the controller will be forced to stop Probable causes External noise may interfere with the communication signals. Recommended actions 1) Check the communication link cable between the axis computer and the main drive unit is correctly connected. 2) Check that the module is properly grounded. 3) Check for external electromagnetic noise sources close to the drive module. 6 Trouble shooting by Event log 176 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 39411, Too Many communication errors Description Four or more consecutive communication packets have been lost between the axis computer and drive unit arg in drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes There may be a break in the communication link cable between the axis computer and the main drive unit, the drive module may be incorrectly grounded or excessive noise may interfere with the communication signals. Recommended actions 1) Check the communication link cable between the axis computer and the main drive unit is correctly connected. 2) Check that the module is properly grounded. 3) Check for external electromagnetic noise sources close to the drive module. 39412, Too Many Missed Reference Updates Description Too many missed communication packets have been detected for joint arg , in drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes There may be a break in the communication link cable between the axis computer and the main drive unit, the drive module may be incorrectly grounded or excessive noise may interfere with the communication signals. Recommended actions 1) Check the communication link cable between the axis computer and the main drive unit is correctly connected. 2) Check that the module is properly grounded. 3) Check for external electromagnetic noise sources close to the drive module.. 39413, Drive Software Not Synchronised Description The axis computer software in drive module arg has become unsynchronised with the drive software for joint arg . This is an unstable software state. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes There may be glitches in the system timing. Recommended actions 1) Restart the controller. 2) If the problem persists, contact your local ABB representative.. 39414, Unknown Capacitor Type Code Description The type code for the capacitor unit arg in drive module arg is not recognised by the system. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The wrong type of capacitor unit may have been fitted or the capacitor version used is not supported by the software. Recommended actions 1) Check the type of capacitor unit fitted. Replace if it is the wrong type. 2) If the problem persists, contact your local ABB representative. 39415, Communication with the Drive Unit Lost Description Communication with drive unit number arg in drive module arg has been lost. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes There may be a break in the communication link cable between the axis computer and the main drive unit, the drive module may be incorrectly grounded or excessive noise may interfere with the communication signals. Recommended actions 1) Check the communication link cable between the axis computer and the main drive unit is correctly connected. 2) Check that the module is properly grounded. 3) Check for external electromagnetic noise sources close to the drive module.. 39416, Drive Unit Not Responding Description The main drive unit in drive module arg is not responding. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. 6 Trouble shooting by Event log 177 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes There may be a break in the communication link cable between the axis computer and the main drive unit, or there may be a lock-up in the software. Recommended actions 1) Check the communication link cable between the axis computer and the main drive unit is correctly connected. 2) Restart the controller. 3) If the problem persists, contact your local ABB representative. 39417, Cannot find Drive Software Version File Description The system cannot locate a valid drive version file on the disk. The file may have been erased my mistake. Without this file it is not possible to check if the drive units software needs updating. Recommended actions Contact your local ABB representative. 39418, Unknown Drive Unit type code Description The type code for the drive unit arg in drive module arg is not recognised by the system. Installed drive unit type is arg , and the configured type is arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The connection to the drive unit may be bad or the hardware may be faulty. Recommended actions 1) Make sure the cable connections on the drive unit are correct. 2) Make sure the drive unit is one supported by this controller. 3) If the drive unit was recently replaced, make sure a unit of the correct type code is used. 39419, Unknown Rectifier type code Description The type code for the rectifier unit arg in drive module arg is not recognised by the system. Installed rectifier unit type is arg , and the configured type is arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The connection to the drive unit may be bad or the hardware may be faulty. Recommended actions 1) Make sure the cable connections on the rectifier unit unit are correct. 2) Make sure the rectifier unit is one supported by this controller. 3) If the rectifier unit was recently replaced, make sure a unit of the correct type code is used. 39420, Drive Unit built in test failure Description Drive unit number arg in drive module arg has detected an internal hardware failure. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The test software is not working correctly, or the actual hardware is faulty. Recommended actions 1) Perform a shutdown and then restart the system. 2) If the problem persists, isolate the faulty drive unit and replace it. 39421, Drive Unit configuration test failure Description Drive unit number arg in drive module arg has detected an internal error. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The connection to the drive unit may be bad or incorrect hardware may have been fitted. Recommended actions 1) Perform a shutdown and then restart the system. 2) If the problem persists, isolate the faulty drive unit and replace it. 39422, Drive Unit watchdog timeout Description The time limit for watchdog timer for drive unit number arg in drive module arg has expired. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The connection to the drive unit may be bad or incorrect hardware may have been fitted. It may also be caused by an internal error in the drive unit.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	179	6 Trouble shooting by Event log 176 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 39411, Too Many communication errors Description Four or more consecutive communication packets have been lost between the axis computer and drive unit arg in drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes There may be a break in the communication link cable between the axis computer and the main drive unit, the drive module may be incorrectly grounded or excessive noise may interfere with the communication signals. Recommended actions 1) Check the communication link cable between the axis computer and the main drive unit is correctly connected. 2) Check that the module is properly grounded. 3) Check for external electromagnetic noise sources close to the drive module. 39412, Too Many Missed Reference Updates Description Too many missed communication packets have been detected for joint arg , in drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes There may be a break in the communication link cable between the axis computer and the main drive unit, the drive module may be incorrectly grounded or excessive noise may interfere with the communication signals. Recommended actions 1) Check the communication link cable between the axis computer and the main drive unit is correctly connected. 2) Check that the module is properly grounded. 3) Check for external electromagnetic noise sources close to the drive module.. 39413, Drive Software Not Synchronised Description The axis computer software in drive module arg has become unsynchronised with the drive software for joint arg . This is an unstable software state. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes There may be glitches in the system timing. Recommended actions 1) Restart the controller. 2) If the problem persists, contact your local ABB representative.. 39414, Unknown Capacitor Type Code Description The type code for the capacitor unit arg in drive module arg is not recognised by the system. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The wrong type of capacitor unit may have been fitted or the capacitor version used is not supported by the software. Recommended actions 1) Check the type of capacitor unit fitted. Replace if it is the wrong type. 2) If the problem persists, contact your local ABB representative. 39415, Communication with the Drive Unit Lost Description Communication with drive unit number arg in drive module arg has been lost. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes There may be a break in the communication link cable between the axis computer and the main drive unit, the drive module may be incorrectly grounded or excessive noise may interfere with the communication signals. Recommended actions 1) Check the communication link cable between the axis computer and the main drive unit is correctly connected. 2) Check that the module is properly grounded. 3) Check for external electromagnetic noise sources close to the drive module.. 39416, Drive Unit Not Responding Description The main drive unit in drive module arg is not responding. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. 6 Trouble shooting by Event log 177 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes There may be a break in the communication link cable between the axis computer and the main drive unit, or there may be a lock-up in the software. Recommended actions 1) Check the communication link cable between the axis computer and the main drive unit is correctly connected. 2) Restart the controller. 3) If the problem persists, contact your local ABB representative. 39417, Cannot find Drive Software Version File Description The system cannot locate a valid drive version file on the disk. The file may have been erased my mistake. Without this file it is not possible to check if the drive units software needs updating. Recommended actions Contact your local ABB representative. 39418, Unknown Drive Unit type code Description The type code for the drive unit arg in drive module arg is not recognised by the system. Installed drive unit type is arg , and the configured type is arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The connection to the drive unit may be bad or the hardware may be faulty. Recommended actions 1) Make sure the cable connections on the drive unit are correct. 2) Make sure the drive unit is one supported by this controller. 3) If the drive unit was recently replaced, make sure a unit of the correct type code is used. 39419, Unknown Rectifier type code Description The type code for the rectifier unit arg in drive module arg is not recognised by the system. Installed rectifier unit type is arg , and the configured type is arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The connection to the drive unit may be bad or the hardware may be faulty. Recommended actions 1) Make sure the cable connections on the rectifier unit unit are correct. 2) Make sure the rectifier unit is one supported by this controller. 3) If the rectifier unit was recently replaced, make sure a unit of the correct type code is used. 39420, Drive Unit built in test failure Description Drive unit number arg in drive module arg has detected an internal hardware failure. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The test software is not working correctly, or the actual hardware is faulty. Recommended actions 1) Perform a shutdown and then restart the system. 2) If the problem persists, isolate the faulty drive unit and replace it. 39421, Drive Unit configuration test failure Description Drive unit number arg in drive module arg has detected an internal error. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The connection to the drive unit may be bad or incorrect hardware may have been fitted. Recommended actions 1) Perform a shutdown and then restart the system. 2) If the problem persists, isolate the faulty drive unit and replace it. 39422, Drive Unit watchdog timeout Description The time limit for watchdog timer for drive unit number arg in drive module arg has expired. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The connection to the drive unit may be bad or incorrect hardware may have been fitted. It may also be caused by an internal error in the drive unit. 6 Trouble shooting by Event log 178 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Perform a shutdown and then restart the system. 2) If the problem persists, isolate the faulty drive unit and replace it. 39423, Drive Unit Internal Warning Description Internal measurement warning for drive unit number arg in drive module arg . supervision code = arg Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes There may be problems with the control cable, the DC link connection (bus bar or cable) or internal hardware. Recommended actions 1) Check the control cables and DC link connection (bus bar or cable) are correctly inserted for this unit. 2) Restart the system. 39424, Drive Unit internal error Description Internal measurement warning for drive unit number arg in drive module arg . Supervision Code = arg Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The connection to the drive unit may be bad or incorrect hardware may have been fitted. It may also be caused by faulty control cable, DC link connection (bus bar or cable) or internal hardware. Recommended actions 1) Make sure the control cables and DC link connection (bus bar or cable) are correctly connected for this unit. 2) Perform a shutdown and then restart the system. 3) If the problem persists, isolate the faulty unit and replace it. 39425, Drive Unit measurement failure Description A current measurement circuit in drive unit number arg , drive module arg , attached to joint arg has failed. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty or lacking DC link connection between the rectifier and drive units. Recommended actions 1) Make sure the DC link connection (bus bar or cable) is correctly connected between the rectifier and drive unit. 2) Check the indication LEDs on the rectifier and drive units. The significance of the LEDs is described in the Trouble Shooting Manual. 39426, Rectifier internal failure Description The rectifier on communication link arg attached to drive module arg has detected an internal failure. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty or lacking signal connection between the rectifier and drive units. Recommended actions 1) Make sure the signal cable is correctly connected between the rectifier and drive unit. 2) Check the indication LEDs on the rectifier and drive units. The significance of the LEDs is described in the Trouble Shooting Manual. 39427, Rectifier communication missing Description The communication with the rectifier on drive comm link arg , drive module arg has been lost. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty or lacking signal connection between the rectifier and drive units. Recommended actions 1) Make sure the signal cable is correctly connected between the rectifier and drive unit. 2) Perform a shutdown and then restart the system. 3) If the problem persists, isolate the faulty unit and replace it. 39428, Rectifier startup error Description The rectifier on drive comm link arg , drive module arg has detected a startup error.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	180	6 Trouble shooting by Event log 177 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes There may be a break in the communication link cable between the axis computer and the main drive unit, or there may be a lock-up in the software. Recommended actions 1) Check the communication link cable between the axis computer and the main drive unit is correctly connected. 2) Restart the controller. 3) If the problem persists, contact your local ABB representative. 39417, Cannot find Drive Software Version File Description The system cannot locate a valid drive version file on the disk. The file may have been erased my mistake. Without this file it is not possible to check if the drive units software needs updating. Recommended actions Contact your local ABB representative. 39418, Unknown Drive Unit type code Description The type code for the drive unit arg in drive module arg is not recognised by the system. Installed drive unit type is arg , and the configured type is arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The connection to the drive unit may be bad or the hardware may be faulty. Recommended actions 1) Make sure the cable connections on the drive unit are correct. 2) Make sure the drive unit is one supported by this controller. 3) If the drive unit was recently replaced, make sure a unit of the correct type code is used. 39419, Unknown Rectifier type code Description The type code for the rectifier unit arg in drive module arg is not recognised by the system. Installed rectifier unit type is arg , and the configured type is arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The connection to the drive unit may be bad or the hardware may be faulty. Recommended actions 1) Make sure the cable connections on the rectifier unit unit are correct. 2) Make sure the rectifier unit is one supported by this controller. 3) If the rectifier unit was recently replaced, make sure a unit of the correct type code is used. 39420, Drive Unit built in test failure Description Drive unit number arg in drive module arg has detected an internal hardware failure. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The test software is not working correctly, or the actual hardware is faulty. Recommended actions 1) Perform a shutdown and then restart the system. 2) If the problem persists, isolate the faulty drive unit and replace it. 39421, Drive Unit configuration test failure Description Drive unit number arg in drive module arg has detected an internal error. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The connection to the drive unit may be bad or incorrect hardware may have been fitted. Recommended actions 1) Perform a shutdown and then restart the system. 2) If the problem persists, isolate the faulty drive unit and replace it. 39422, Drive Unit watchdog timeout Description The time limit for watchdog timer for drive unit number arg in drive module arg has expired. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The connection to the drive unit may be bad or incorrect hardware may have been fitted. It may also be caused by an internal error in the drive unit. 6 Trouble shooting by Event log 178 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Perform a shutdown and then restart the system. 2) If the problem persists, isolate the faulty drive unit and replace it. 39423, Drive Unit Internal Warning Description Internal measurement warning for drive unit number arg in drive module arg . supervision code = arg Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes There may be problems with the control cable, the DC link connection (bus bar or cable) or internal hardware. Recommended actions 1) Check the control cables and DC link connection (bus bar or cable) are correctly inserted for this unit. 2) Restart the system. 39424, Drive Unit internal error Description Internal measurement warning for drive unit number arg in drive module arg . Supervision Code = arg Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The connection to the drive unit may be bad or incorrect hardware may have been fitted. It may also be caused by faulty control cable, DC link connection (bus bar or cable) or internal hardware. Recommended actions 1) Make sure the control cables and DC link connection (bus bar or cable) are correctly connected for this unit. 2) Perform a shutdown and then restart the system. 3) If the problem persists, isolate the faulty unit and replace it. 39425, Drive Unit measurement failure Description A current measurement circuit in drive unit number arg , drive module arg , attached to joint arg has failed. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty or lacking DC link connection between the rectifier and drive units. Recommended actions 1) Make sure the DC link connection (bus bar or cable) is correctly connected between the rectifier and drive unit. 2) Check the indication LEDs on the rectifier and drive units. The significance of the LEDs is described in the Trouble Shooting Manual. 39426, Rectifier internal failure Description The rectifier on communication link arg attached to drive module arg has detected an internal failure. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty or lacking signal connection between the rectifier and drive units. Recommended actions 1) Make sure the signal cable is correctly connected between the rectifier and drive unit. 2) Check the indication LEDs on the rectifier and drive units. The significance of the LEDs is described in the Trouble Shooting Manual. 39427, Rectifier communication missing Description The communication with the rectifier on drive comm link arg , drive module arg has been lost. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty or lacking signal connection between the rectifier and drive units. Recommended actions 1) Make sure the signal cable is correctly connected between the rectifier and drive unit. 2) Perform a shutdown and then restart the system. 3) If the problem persists, isolate the faulty unit and replace it. 39428, Rectifier startup error Description The rectifier on drive comm link arg , drive module arg has detected a startup error. 6 Trouble shooting by Event log 179 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by an internal error in the rectifier unit. Recommended actions 1) Make sure the signal cable is correctly connected between the rectifier and drive unit. 2) Perform a shutdown and then restart the system. 3) If the problem persists, isolate the faulty rectifier unit and replace it. 39431, Update of Drive Unit Software in Progress Description The drive unit software in drive module arg is being updated. Please wait for the upgrade to be completed. This will take approximately 3.5 minutes. NOTE: Please do not turn off the power or restart the controller until the download is complete. Recommended actions Please wait... 39432, Incompatible boot version in drive unit Description The boot version in drive module arg is version arg , which is not allowed. The latest allowed boot version is arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The boot version is not compatible with the hardware version. Recommended actions 1) Replace the drive unit with one using a boot version equal to or greater than the latest allowed one. 39434, Drive Unit Start Failure Description The drive unit in drive module arg failed to start. drive boot status = arg . drive dsp1 status = arg Consequences The robot can not be operated. Probable causes A number of errors may cause this. Recommended actions 1) Switch the main power off to the module and then switch it back on. Note that a normal restart will NOT suffice! 2) If the problem persists, replace the drive unit. 39435, Cannot find additional axis drive unit Description The system cannot detect an additional axis drive for joint arg in drive module arg . Consequences System goes to SYS_FAIL. Probable causes This can be due to: 1) Having an additional axis configured but not having a drive unit in the drive module. 2) Having an external drive unit but not connecting the cable to the X arg connector position on the main drive unit. 3) Damaged cable between the additional axis drive and the main drive unit. Recommended actions 1) Check the drive module contains enough additional axis drives. 2) Check that the configuration key does not define more external drive units then are connected in the drive module 3) Check the cable between the additional axis drive unit and to the main drive unit is correctly inserted in the right connector position. 4) If the cable exists and is correctly inserted, then it may be damaged and should be replaced. 39440, Open circuit in bleeder resistor circuit Description The bleeder resistor connected to the rectifier on drive link arg , drive module arg , is an open circuit. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty bleeder resistor cable or bleeder resistor. Recommended actions 1) Make sure the bleeder resistor cable is correctly connected to the rectifier unit. 2) Make sure the cable and resistor is working correctly by measuring their resistance respectively. Disconnect before measuring. 3) Replace any faulty component. 39441, Short circuit in bleeder resistor circuit Description The bleeder resistor connected to the rectifier on drive link arg , drive module arg , is a short circuit.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	181	6 Trouble shooting by Event log 178 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 1) Perform a shutdown and then restart the system. 2) If the problem persists, isolate the faulty drive unit and replace it. 39423, Drive Unit Internal Warning Description Internal measurement warning for drive unit number arg in drive module arg . supervision code = arg Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes There may be problems with the control cable, the DC link connection (bus bar or cable) or internal hardware. Recommended actions 1) Check the control cables and DC link connection (bus bar or cable) are correctly inserted for this unit. 2) Restart the system. 39424, Drive Unit internal error Description Internal measurement warning for drive unit number arg in drive module arg . Supervision Code = arg Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The connection to the drive unit may be bad or incorrect hardware may have been fitted. It may also be caused by faulty control cable, DC link connection (bus bar or cable) or internal hardware. Recommended actions 1) Make sure the control cables and DC link connection (bus bar or cable) are correctly connected for this unit. 2) Perform a shutdown and then restart the system. 3) If the problem persists, isolate the faulty unit and replace it. 39425, Drive Unit measurement failure Description A current measurement circuit in drive unit number arg , drive module arg , attached to joint arg has failed. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty or lacking DC link connection between the rectifier and drive units. Recommended actions 1) Make sure the DC link connection (bus bar or cable) is correctly connected between the rectifier and drive unit. 2) Check the indication LEDs on the rectifier and drive units. The significance of the LEDs is described in the Trouble Shooting Manual. 39426, Rectifier internal failure Description The rectifier on communication link arg attached to drive module arg has detected an internal failure. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty or lacking signal connection between the rectifier and drive units. Recommended actions 1) Make sure the signal cable is correctly connected between the rectifier and drive unit. 2) Check the indication LEDs on the rectifier and drive units. The significance of the LEDs is described in the Trouble Shooting Manual. 39427, Rectifier communication missing Description The communication with the rectifier on drive comm link arg , drive module arg has been lost. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty or lacking signal connection between the rectifier and drive units. Recommended actions 1) Make sure the signal cable is correctly connected between the rectifier and drive unit. 2) Perform a shutdown and then restart the system. 3) If the problem persists, isolate the faulty unit and replace it. 39428, Rectifier startup error Description The rectifier on drive comm link arg , drive module arg has detected a startup error. 6 Trouble shooting by Event log 179 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by an internal error in the rectifier unit. Recommended actions 1) Make sure the signal cable is correctly connected between the rectifier and drive unit. 2) Perform a shutdown and then restart the system. 3) If the problem persists, isolate the faulty rectifier unit and replace it. 39431, Update of Drive Unit Software in Progress Description The drive unit software in drive module arg is being updated. Please wait for the upgrade to be completed. This will take approximately 3.5 minutes. NOTE: Please do not turn off the power or restart the controller until the download is complete. Recommended actions Please wait... 39432, Incompatible boot version in drive unit Description The boot version in drive module arg is version arg , which is not allowed. The latest allowed boot version is arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The boot version is not compatible with the hardware version. Recommended actions 1) Replace the drive unit with one using a boot version equal to or greater than the latest allowed one. 39434, Drive Unit Start Failure Description The drive unit in drive module arg failed to start. drive boot status = arg . drive dsp1 status = arg Consequences The robot can not be operated. Probable causes A number of errors may cause this. Recommended actions 1) Switch the main power off to the module and then switch it back on. Note that a normal restart will NOT suffice! 2) If the problem persists, replace the drive unit. 39435, Cannot find additional axis drive unit Description The system cannot detect an additional axis drive for joint arg in drive module arg . Consequences System goes to SYS_FAIL. Probable causes This can be due to: 1) Having an additional axis configured but not having a drive unit in the drive module. 2) Having an external drive unit but not connecting the cable to the X arg connector position on the main drive unit. 3) Damaged cable between the additional axis drive and the main drive unit. Recommended actions 1) Check the drive module contains enough additional axis drives. 2) Check that the configuration key does not define more external drive units then are connected in the drive module 3) Check the cable between the additional axis drive unit and to the main drive unit is correctly inserted in the right connector position. 4) If the cable exists and is correctly inserted, then it may be damaged and should be replaced. 39440, Open circuit in bleeder resistor circuit Description The bleeder resistor connected to the rectifier on drive link arg , drive module arg , is an open circuit. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty bleeder resistor cable or bleeder resistor. Recommended actions 1) Make sure the bleeder resistor cable is correctly connected to the rectifier unit. 2) Make sure the cable and resistor is working correctly by measuring their resistance respectively. Disconnect before measuring. 3) Replace any faulty component. 39441, Short circuit in bleeder resistor circuit Description The bleeder resistor connected to the rectifier on drive link arg , drive module arg , is a short circuit. 6 Trouble shooting by Event log 180 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty bleeder resistor cable or bleeder resistor. Recommended actions 1) Make sure the bleeder resistor cable is correctly connected to the rectifier unit. 2) Make sure the cable and resistor is working correctly by measuring their resistance respectively. Disconnect before measuring. 3) Replace any faulty component. 39442, Bleeder Resistance Too Low Description The bleeder resistance is too low for the rectifier on drive comm link arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The bleeders may have the wrong resistance value or one of the bleeders may have failed, causing a short circuit. Recommended actions 1) Check the bleeder resistors to see that they are the correct resistance value for this drive module configuration. 2) Check that none of the resistors have failed. How to check the configuration file is detailed in the Trouble Shooting Manual. 39443, Bleeder Resistor Overload Warning Description The power consumed by the bleeder resistors is approaching overload for the rectifier on drive communication link arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The user program may contain too much hard braking of the manipulators, which is more likely if the system contains additional axes. Recommended actions 1) Rewrite the user program to reduce the amount of hard braking. 39444, Bleeder resistor overload error Description The bleeder resistors have been overloaded for the rectifier on drive communication link arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The user program may contain too much hard braking or too high a payload of the manipulators. This is more likely if the system contains additional axes. Recommended actions 1) Rewrite the user program to reduce the amount of hard braking. 39450, Faulty Fan Unit Power Supply Description The power supply for the fan unit in drive module arg is not within its allowed voltage limits. Consequences - Probable causes The main fan power supply unit may be faulty or the supply to this power supply unit may not be within its allowed voltage limits. Recommended actions 1) Check the fan cable is correctly inserted. 2) Check that all fans are working. 3) Check the input voltage to the main fan power supply unit. Replace any faulty unit. 39451, Fan Unit Malfunction Description The fan unit in drive module arg has malfunctioned. Consequences - Probable causes The fan unit may be faulty, a loss of power supply or the fan power cable may not be connected correctly. Recommended actions 1) Make sure the fan cable is correctly connected. 2) Make sure all fans are working and that air flow is not obstructed. 3) Measure the output voltage from the drive unit supplying the fan. Replace any faulty unit. 39452, Axis Computer Cooling Fan Malfunction Description The cooling fan for the axis computer in drive module arg has malfunctioned. Recommended actions 1)Check that the fan cable is correctly inserted. 2) Replace the faulty fan unit.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	182	6 Trouble shooting by Event log 179 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by an internal error in the rectifier unit. Recommended actions 1) Make sure the signal cable is correctly connected between the rectifier and drive unit. 2) Perform a shutdown and then restart the system. 3) If the problem persists, isolate the faulty rectifier unit and replace it. 39431, Update of Drive Unit Software in Progress Description The drive unit software in drive module arg is being updated. Please wait for the upgrade to be completed. This will take approximately 3.5 minutes. NOTE: Please do not turn off the power or restart the controller until the download is complete. Recommended actions Please wait... 39432, Incompatible boot version in drive unit Description The boot version in drive module arg is version arg , which is not allowed. The latest allowed boot version is arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The boot version is not compatible with the hardware version. Recommended actions 1) Replace the drive unit with one using a boot version equal to or greater than the latest allowed one. 39434, Drive Unit Start Failure Description The drive unit in drive module arg failed to start. drive boot status = arg . drive dsp1 status = arg Consequences The robot can not be operated. Probable causes A number of errors may cause this. Recommended actions 1) Switch the main power off to the module and then switch it back on. Note that a normal restart will NOT suffice! 2) If the problem persists, replace the drive unit. 39435, Cannot find additional axis drive unit Description The system cannot detect an additional axis drive for joint arg in drive module arg . Consequences System goes to SYS_FAIL. Probable causes This can be due to: 1) Having an additional axis configured but not having a drive unit in the drive module. 2) Having an external drive unit but not connecting the cable to the X arg connector position on the main drive unit. 3) Damaged cable between the additional axis drive and the main drive unit. Recommended actions 1) Check the drive module contains enough additional axis drives. 2) Check that the configuration key does not define more external drive units then are connected in the drive module 3) Check the cable between the additional axis drive unit and to the main drive unit is correctly inserted in the right connector position. 4) If the cable exists and is correctly inserted, then it may be damaged and should be replaced. 39440, Open circuit in bleeder resistor circuit Description The bleeder resistor connected to the rectifier on drive link arg , drive module arg , is an open circuit. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty bleeder resistor cable or bleeder resistor. Recommended actions 1) Make sure the bleeder resistor cable is correctly connected to the rectifier unit. 2) Make sure the cable and resistor is working correctly by measuring their resistance respectively. Disconnect before measuring. 3) Replace any faulty component. 39441, Short circuit in bleeder resistor circuit Description The bleeder resistor connected to the rectifier on drive link arg , drive module arg , is a short circuit. 6 Trouble shooting by Event log 180 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty bleeder resistor cable or bleeder resistor. Recommended actions 1) Make sure the bleeder resistor cable is correctly connected to the rectifier unit. 2) Make sure the cable and resistor is working correctly by measuring their resistance respectively. Disconnect before measuring. 3) Replace any faulty component. 39442, Bleeder Resistance Too Low Description The bleeder resistance is too low for the rectifier on drive comm link arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The bleeders may have the wrong resistance value or one of the bleeders may have failed, causing a short circuit. Recommended actions 1) Check the bleeder resistors to see that they are the correct resistance value for this drive module configuration. 2) Check that none of the resistors have failed. How to check the configuration file is detailed in the Trouble Shooting Manual. 39443, Bleeder Resistor Overload Warning Description The power consumed by the bleeder resistors is approaching overload for the rectifier on drive communication link arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The user program may contain too much hard braking of the manipulators, which is more likely if the system contains additional axes. Recommended actions 1) Rewrite the user program to reduce the amount of hard braking. 39444, Bleeder resistor overload error Description The bleeder resistors have been overloaded for the rectifier on drive communication link arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The user program may contain too much hard braking or too high a payload of the manipulators. This is more likely if the system contains additional axes. Recommended actions 1) Rewrite the user program to reduce the amount of hard braking. 39450, Faulty Fan Unit Power Supply Description The power supply for the fan unit in drive module arg is not within its allowed voltage limits. Consequences - Probable causes The main fan power supply unit may be faulty or the supply to this power supply unit may not be within its allowed voltage limits. Recommended actions 1) Check the fan cable is correctly inserted. 2) Check that all fans are working. 3) Check the input voltage to the main fan power supply unit. Replace any faulty unit. 39451, Fan Unit Malfunction Description The fan unit in drive module arg has malfunctioned. Consequences - Probable causes The fan unit may be faulty, a loss of power supply or the fan power cable may not be connected correctly. Recommended actions 1) Make sure the fan cable is correctly connected. 2) Make sure all fans are working and that air flow is not obstructed. 3) Measure the output voltage from the drive unit supplying the fan. Replace any faulty unit. 39452, Axis Computer Cooling Fan Malfunction Description The cooling fan for the axis computer in drive module arg has malfunctioned. Recommended actions 1)Check that the fan cable is correctly inserted. 2) Replace the faulty fan unit. 6 Trouble shooting by Event log 181 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 39453, Transformer Cooling Fan Malfunction Description The cooling fan for the transformer supplying drive module arg has malfunctioned. Recommended actions Check if fan cable is correctly inserted. 2) Replace the faulty fan unit. 39460, DC Link Voltage Too Low Description The DC link voltage is too low for the rectifier on drive communication link arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The DC link bus bar may be incorrectly connected or the three-phase mains power may be interrupted while the robot is in the Motors ON state. The mains contactor may also have been opened whilst the robot is in Motors ON state (breaking the safety chain). The incoming main power supply may also be too low. Recommended actions 1) Make sure the DC link bus bar is correctly connected. 2) Make sure the mains supply has not been interrupted. 3) Make sure the safety chain has not been broken. 4) Make sure the Drive Module Power Supply output voltage is within acceptable limits as specified in the Product Manual. 39461, DC Link Voltage Too High Description The DC link voltage is too high for the rectifier on drive communication link arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The user program may contain too much hard braking of the manipulators, which is more likely if the system contains additional axes. The brake resistors may also be faulty. Recommended actions 1) Check the bleeder resistors to see that they are the correct resistance value for this drive module configuration. 2) Check that none of the resistors have failed. 3) If possible, rewrite the user program to reduce the amount of hard braking. 39462, DC Link Voltage at Critical Description The DC link voltage is critically high for the rectifier on drive communication link arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The user program may contain too much hard braking of the manipulators, which is more likely if the system contains additional axes. The brake resistors may also be faulty. Recommended actions 1) Check the bleeder resistors to see that they are the correct resistance value for this drive module configuration. 2) Check that none of the resistors have failed. 3) Rewrite the user program to reduce the amount of hard braking. 39463, Motor Phase Short Circuit Warning Description A brief short circuit was detected in the motor/motor cable for the motor attached to joint arg in drive module arg . Consequences - Probable causes This may be due to dust or metal fragments contaminating the contacts or motor windings. Recommended actions No action is required if the problem does not persist. 39464, Short circuit in Motor phase circuit Description The motor or motor cable for joint arg in drive module arg , drive unit number arg , is a short circuit. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty motor or motor cable. It may also be caused by contamination in the contactors for the cables or a failure of the motor windings. Recommended actions 1) Make sure the motor cable is correctly connected to the drive unit. 2) Check the cable and motor by measuring their resistance respectively. Disconnect before measuring. 3) Replace any faulty component.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	183	6 Trouble shooting by Event log 180 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty bleeder resistor cable or bleeder resistor. Recommended actions 1) Make sure the bleeder resistor cable is correctly connected to the rectifier unit. 2) Make sure the cable and resistor is working correctly by measuring their resistance respectively. Disconnect before measuring. 3) Replace any faulty component. 39442, Bleeder Resistance Too Low Description The bleeder resistance is too low for the rectifier on drive comm link arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The bleeders may have the wrong resistance value or one of the bleeders may have failed, causing a short circuit. Recommended actions 1) Check the bleeder resistors to see that they are the correct resistance value for this drive module configuration. 2) Check that none of the resistors have failed. How to check the configuration file is detailed in the Trouble Shooting Manual. 39443, Bleeder Resistor Overload Warning Description The power consumed by the bleeder resistors is approaching overload for the rectifier on drive communication link arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The user program may contain too much hard braking of the manipulators, which is more likely if the system contains additional axes. Recommended actions 1) Rewrite the user program to reduce the amount of hard braking. 39444, Bleeder resistor overload error Description The bleeder resistors have been overloaded for the rectifier on drive communication link arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The user program may contain too much hard braking or too high a payload of the manipulators. This is more likely if the system contains additional axes. Recommended actions 1) Rewrite the user program to reduce the amount of hard braking. 39450, Faulty Fan Unit Power Supply Description The power supply for the fan unit in drive module arg is not within its allowed voltage limits. Consequences - Probable causes The main fan power supply unit may be faulty or the supply to this power supply unit may not be within its allowed voltage limits. Recommended actions 1) Check the fan cable is correctly inserted. 2) Check that all fans are working. 3) Check the input voltage to the main fan power supply unit. Replace any faulty unit. 39451, Fan Unit Malfunction Description The fan unit in drive module arg has malfunctioned. Consequences - Probable causes The fan unit may be faulty, a loss of power supply or the fan power cable may not be connected correctly. Recommended actions 1) Make sure the fan cable is correctly connected. 2) Make sure all fans are working and that air flow is not obstructed. 3) Measure the output voltage from the drive unit supplying the fan. Replace any faulty unit. 39452, Axis Computer Cooling Fan Malfunction Description The cooling fan for the axis computer in drive module arg has malfunctioned. Recommended actions 1)Check that the fan cable is correctly inserted. 2) Replace the faulty fan unit. 6 Trouble shooting by Event log 181 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 39453, Transformer Cooling Fan Malfunction Description The cooling fan for the transformer supplying drive module arg has malfunctioned. Recommended actions Check if fan cable is correctly inserted. 2) Replace the faulty fan unit. 39460, DC Link Voltage Too Low Description The DC link voltage is too low for the rectifier on drive communication link arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The DC link bus bar may be incorrectly connected or the three-phase mains power may be interrupted while the robot is in the Motors ON state. The mains contactor may also have been opened whilst the robot is in Motors ON state (breaking the safety chain). The incoming main power supply may also be too low. Recommended actions 1) Make sure the DC link bus bar is correctly connected. 2) Make sure the mains supply has not been interrupted. 3) Make sure the safety chain has not been broken. 4) Make sure the Drive Module Power Supply output voltage is within acceptable limits as specified in the Product Manual. 39461, DC Link Voltage Too High Description The DC link voltage is too high for the rectifier on drive communication link arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The user program may contain too much hard braking of the manipulators, which is more likely if the system contains additional axes. The brake resistors may also be faulty. Recommended actions 1) Check the bleeder resistors to see that they are the correct resistance value for this drive module configuration. 2) Check that none of the resistors have failed. 3) If possible, rewrite the user program to reduce the amount of hard braking. 39462, DC Link Voltage at Critical Description The DC link voltage is critically high for the rectifier on drive communication link arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The user program may contain too much hard braking of the manipulators, which is more likely if the system contains additional axes. The brake resistors may also be faulty. Recommended actions 1) Check the bleeder resistors to see that they are the correct resistance value for this drive module configuration. 2) Check that none of the resistors have failed. 3) Rewrite the user program to reduce the amount of hard braking. 39463, Motor Phase Short Circuit Warning Description A brief short circuit was detected in the motor/motor cable for the motor attached to joint arg in drive module arg . Consequences - Probable causes This may be due to dust or metal fragments contaminating the contacts or motor windings. Recommended actions No action is required if the problem does not persist. 39464, Short circuit in Motor phase circuit Description The motor or motor cable for joint arg in drive module arg , drive unit number arg , is a short circuit. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty motor or motor cable. It may also be caused by contamination in the contactors for the cables or a failure of the motor windings. Recommended actions 1) Make sure the motor cable is correctly connected to the drive unit. 2) Check the cable and motor by measuring their resistance respectively. Disconnect before measuring. 3) Replace any faulty component. 6 Trouble shooting by Event log 182 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 39465, Motor current warning Description The motor current is higher than the allowed for joint arg in drive module arg , drive unit number arg . Consequences - Probable causes The motor load may be too high or the motor may have stalled (maybe due to a collision). Recommended actions 1) Check that the robot has not collided with anything. 2) If possible, reduce the speed of the user program. 3) If the axis is an additional axis, check that the motor load is not too high for the drive unit. 39466, Motor Current Overload Description The motor current is too high for joint arg in drive module arg , drive unit number arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The motor load may be too high or the motor may have stalled (maybe due to a collision). Recommended actions 1) Check that the robot has not collided. 2) If possible, reduce the speed of the user program. 3) If the axis is an additional axis, check that the motor load is not too high for the drive unit. 39467, Drive Unit Temperature Warning Description The temperature has risen above the warning level in drive unit number arg , drive module arg , which is the lowest abnormal level of three. Consequences - Probable causes The ambient temperature may be too high, the cooling fans may have failed or the user program may consume more current than the drive system can supply. Recommended actions 1) Check that the fans are running and that the air flow is not obstructed. 2) Check that the ambient temperature does not exceed the cabinet rating. 3) If the system contains additional axes then check that motors are not too large for the drive units. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 39468, Drive Unit Temperature Alarm Description The temperature has risen above the alarm level in drive unit number arg , drive module arg , which is the second abnormal level of three. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The ambient temperature may be too high, the cooling fans may have failed or the user program may consume more current than the drive system can supply. Recommended actions 1) Check that the fans are running and that the air flow is not obstructed. 2) Check that the ambient temperature does not exceed the cabinet rating. 3) If the system contains additional axes then check that motors are not too large for the drive units. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 39469, Drive Unit Temperature Critical Description The temperature has risen above the critical level in drive unit number arg , drive module arg , which is the top abnormal level of three. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The ambient temperature may be too high, the cooling fans may have failed or the user program may consume more current than the drive system can supply. Recommended actions 1) Check that the fans are running and that the air flow is not obstructed. 2) Check that the ambient temperature does not exceed the cabinet rating. 3) If the system contains additional axes then check that motors are not too large for the drive units. 4) If possible, rewrite the user program to reduce the amount of hard acceleration.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	184	6 Trouble shooting by Event log 181 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 39453, Transformer Cooling Fan Malfunction Description The cooling fan for the transformer supplying drive module arg has malfunctioned. Recommended actions Check if fan cable is correctly inserted. 2) Replace the faulty fan unit. 39460, DC Link Voltage Too Low Description The DC link voltage is too low for the rectifier on drive communication link arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The DC link bus bar may be incorrectly connected or the three-phase mains power may be interrupted while the robot is in the Motors ON state. The mains contactor may also have been opened whilst the robot is in Motors ON state (breaking the safety chain). The incoming main power supply may also be too low. Recommended actions 1) Make sure the DC link bus bar is correctly connected. 2) Make sure the mains supply has not been interrupted. 3) Make sure the safety chain has not been broken. 4) Make sure the Drive Module Power Supply output voltage is within acceptable limits as specified in the Product Manual. 39461, DC Link Voltage Too High Description The DC link voltage is too high for the rectifier on drive communication link arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The user program may contain too much hard braking of the manipulators, which is more likely if the system contains additional axes. The brake resistors may also be faulty. Recommended actions 1) Check the bleeder resistors to see that they are the correct resistance value for this drive module configuration. 2) Check that none of the resistors have failed. 3) If possible, rewrite the user program to reduce the amount of hard braking. 39462, DC Link Voltage at Critical Description The DC link voltage is critically high for the rectifier on drive communication link arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The user program may contain too much hard braking of the manipulators, which is more likely if the system contains additional axes. The brake resistors may also be faulty. Recommended actions 1) Check the bleeder resistors to see that they are the correct resistance value for this drive module configuration. 2) Check that none of the resistors have failed. 3) Rewrite the user program to reduce the amount of hard braking. 39463, Motor Phase Short Circuit Warning Description A brief short circuit was detected in the motor/motor cable for the motor attached to joint arg in drive module arg . Consequences - Probable causes This may be due to dust or metal fragments contaminating the contacts or motor windings. Recommended actions No action is required if the problem does not persist. 39464, Short circuit in Motor phase circuit Description The motor or motor cable for joint arg in drive module arg , drive unit number arg , is a short circuit. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by a faulty motor or motor cable. It may also be caused by contamination in the contactors for the cables or a failure of the motor windings. Recommended actions 1) Make sure the motor cable is correctly connected to the drive unit. 2) Check the cable and motor by measuring their resistance respectively. Disconnect before measuring. 3) Replace any faulty component. 6 Trouble shooting by Event log 182 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 39465, Motor current warning Description The motor current is higher than the allowed for joint arg in drive module arg , drive unit number arg . Consequences - Probable causes The motor load may be too high or the motor may have stalled (maybe due to a collision). Recommended actions 1) Check that the robot has not collided with anything. 2) If possible, reduce the speed of the user program. 3) If the axis is an additional axis, check that the motor load is not too high for the drive unit. 39466, Motor Current Overload Description The motor current is too high for joint arg in drive module arg , drive unit number arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The motor load may be too high or the motor may have stalled (maybe due to a collision). Recommended actions 1) Check that the robot has not collided. 2) If possible, reduce the speed of the user program. 3) If the axis is an additional axis, check that the motor load is not too high for the drive unit. 39467, Drive Unit Temperature Warning Description The temperature has risen above the warning level in drive unit number arg , drive module arg , which is the lowest abnormal level of three. Consequences - Probable causes The ambient temperature may be too high, the cooling fans may have failed or the user program may consume more current than the drive system can supply. Recommended actions 1) Check that the fans are running and that the air flow is not obstructed. 2) Check that the ambient temperature does not exceed the cabinet rating. 3) If the system contains additional axes then check that motors are not too large for the drive units. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 39468, Drive Unit Temperature Alarm Description The temperature has risen above the alarm level in drive unit number arg , drive module arg , which is the second abnormal level of three. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The ambient temperature may be too high, the cooling fans may have failed or the user program may consume more current than the drive system can supply. Recommended actions 1) Check that the fans are running and that the air flow is not obstructed. 2) Check that the ambient temperature does not exceed the cabinet rating. 3) If the system contains additional axes then check that motors are not too large for the drive units. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 39469, Drive Unit Temperature Critical Description The temperature has risen above the critical level in drive unit number arg , drive module arg , which is the top abnormal level of three. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The ambient temperature may be too high, the cooling fans may have failed or the user program may consume more current than the drive system can supply. Recommended actions 1) Check that the fans are running and that the air flow is not obstructed. 2) Check that the ambient temperature does not exceed the cabinet rating. 3) If the system contains additional axes then check that motors are not too large for the drive units. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 6 Trouble shooting by Event log 183 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 39470, Power Semiconductor Warning Description The power semiconductor is approaching overload for joint arg , in drive unit number arg , drive module arg . Consequences - Probable causes The motor load may be too high, the motor may have stalled (maybe due to a collision), the motor load may be too high or there may not be enough cooling. Recommended actions 1) Check that the robot has not collided. 2) Check that the fans are running and that the air flow is not obstructed. 3) Check that the ambient temperature does not exceed the cabinet rating. 4) If the system contains additional axes then check that motors are not too large for the drive units. 5) If possible, rewrite the user program to reduce the amount of hard acceleration. 39471, Power Semiconductor Overload Error Description The power semiconductor has been overloaded for joint arg , in drive unit number arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The motor load may be too high, the motor may have stalled (maybe due to a collision), the motor load may be too high or there may not be enough cooling. Recommended actions 1) Check that the robot has not collided. 2) Check that the fans are running and that the air flow is not obstructed. 3) Check that the ambient temperature does not exceed the cabinet rating. 4) If the system contains additional axes then check that motors are not too large for the drive units. 5) If possible, rewrite the user program to reduce the amount of hard acceleration. 39472, Incoming Mains Phase Missing Description The rectifier connected to communication link arg in drive module arg detects a power loss in one phase. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by an actual mains power loss, some malfunction in the Motors ON contactors or its cabling or in another part of the three phase chain inside the cabinet. On rare occasions, this fault may occur in combination with other faults, in which case this may be found in the error log. Recommended actions 1) Make sure the mains switch is closed and that there is mains voltage present. No volts means the problem is in mains cable connector or the factory power supply. 2) If the voltage is OK, disconnect the input mains cable and measure the resistance of all three phases across all the components in the 3 phase supply chain. Start from the contactor closest to the rectifier and work backwards towards the mains switch. The contactors can be closed manually to perform the test. Refer to the electrical drawings for the cabinet. 3) Check the indication LEDs on the rectifier unit. The significance of these is described in the Trouble Shooting Manual. 4) If the voltage is OK, check any other error log messages coinciding in time with this one for clues. 39473, All Incoming Mains Phases Missing Description The rectifier connected to communication link arg in drive module arg detects a power loss in one or more phases. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by an actual mains power loss, some malfunction in the Motors ON contactors or its cabling or in another part of the three phase chain inside the cabinet. On rare occasions, this fault may occur in combination with other faults, in which case this may be found in the error log. Recommended actions 1) Make sure the mains switch is closed and that there is mains voltage present. No volts means the problem is in mains cable connector or the factory power supply. 2) If the voltage is OK, disconnect the input mains cable and measure the resistance of all three phases across all the components in the 3 phase supply chain. Start from the contactor closest to the rectifier and work backwards towards the mains switch. The contactors can be closed manually to perform the test. Refer to the electrical drawings for the cabinet. 3) Check the indication LEDs on the rectifier unit. The significance of these is described in the Trouble Shooting Manual. 4) If the voltage is OK, check any other error log messages coinciding in time with this one for clues.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	185	6 Trouble shooting by Event log 182 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 39465, Motor current warning Description The motor current is higher than the allowed for joint arg in drive module arg , drive unit number arg . Consequences - Probable causes The motor load may be too high or the motor may have stalled (maybe due to a collision). Recommended actions 1) Check that the robot has not collided with anything. 2) If possible, reduce the speed of the user program. 3) If the axis is an additional axis, check that the motor load is not too high for the drive unit. 39466, Motor Current Overload Description The motor current is too high for joint arg in drive module arg , drive unit number arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The motor load may be too high or the motor may have stalled (maybe due to a collision). Recommended actions 1) Check that the robot has not collided. 2) If possible, reduce the speed of the user program. 3) If the axis is an additional axis, check that the motor load is not too high for the drive unit. 39467, Drive Unit Temperature Warning Description The temperature has risen above the warning level in drive unit number arg , drive module arg , which is the lowest abnormal level of three. Consequences - Probable causes The ambient temperature may be too high, the cooling fans may have failed or the user program may consume more current than the drive system can supply. Recommended actions 1) Check that the fans are running and that the air flow is not obstructed. 2) Check that the ambient temperature does not exceed the cabinet rating. 3) If the system contains additional axes then check that motors are not too large for the drive units. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 39468, Drive Unit Temperature Alarm Description The temperature has risen above the alarm level in drive unit number arg , drive module arg , which is the second abnormal level of three. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The ambient temperature may be too high, the cooling fans may have failed or the user program may consume more current than the drive system can supply. Recommended actions 1) Check that the fans are running and that the air flow is not obstructed. 2) Check that the ambient temperature does not exceed the cabinet rating. 3) If the system contains additional axes then check that motors are not too large for the drive units. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 39469, Drive Unit Temperature Critical Description The temperature has risen above the critical level in drive unit number arg , drive module arg , which is the top abnormal level of three. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The ambient temperature may be too high, the cooling fans may have failed or the user program may consume more current than the drive system can supply. Recommended actions 1) Check that the fans are running and that the air flow is not obstructed. 2) Check that the ambient temperature does not exceed the cabinet rating. 3) If the system contains additional axes then check that motors are not too large for the drive units. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 6 Trouble shooting by Event log 183 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 39470, Power Semiconductor Warning Description The power semiconductor is approaching overload for joint arg , in drive unit number arg , drive module arg . Consequences - Probable causes The motor load may be too high, the motor may have stalled (maybe due to a collision), the motor load may be too high or there may not be enough cooling. Recommended actions 1) Check that the robot has not collided. 2) Check that the fans are running and that the air flow is not obstructed. 3) Check that the ambient temperature does not exceed the cabinet rating. 4) If the system contains additional axes then check that motors are not too large for the drive units. 5) If possible, rewrite the user program to reduce the amount of hard acceleration. 39471, Power Semiconductor Overload Error Description The power semiconductor has been overloaded for joint arg , in drive unit number arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The motor load may be too high, the motor may have stalled (maybe due to a collision), the motor load may be too high or there may not be enough cooling. Recommended actions 1) Check that the robot has not collided. 2) Check that the fans are running and that the air flow is not obstructed. 3) Check that the ambient temperature does not exceed the cabinet rating. 4) If the system contains additional axes then check that motors are not too large for the drive units. 5) If possible, rewrite the user program to reduce the amount of hard acceleration. 39472, Incoming Mains Phase Missing Description The rectifier connected to communication link arg in drive module arg detects a power loss in one phase. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by an actual mains power loss, some malfunction in the Motors ON contactors or its cabling or in another part of the three phase chain inside the cabinet. On rare occasions, this fault may occur in combination with other faults, in which case this may be found in the error log. Recommended actions 1) Make sure the mains switch is closed and that there is mains voltage present. No volts means the problem is in mains cable connector or the factory power supply. 2) If the voltage is OK, disconnect the input mains cable and measure the resistance of all three phases across all the components in the 3 phase supply chain. Start from the contactor closest to the rectifier and work backwards towards the mains switch. The contactors can be closed manually to perform the test. Refer to the electrical drawings for the cabinet. 3) Check the indication LEDs on the rectifier unit. The significance of these is described in the Trouble Shooting Manual. 4) If the voltage is OK, check any other error log messages coinciding in time with this one for clues. 39473, All Incoming Mains Phases Missing Description The rectifier connected to communication link arg in drive module arg detects a power loss in one or more phases. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by an actual mains power loss, some malfunction in the Motors ON contactors or its cabling or in another part of the three phase chain inside the cabinet. On rare occasions, this fault may occur in combination with other faults, in which case this may be found in the error log. Recommended actions 1) Make sure the mains switch is closed and that there is mains voltage present. No volts means the problem is in mains cable connector or the factory power supply. 2) If the voltage is OK, disconnect the input mains cable and measure the resistance of all three phases across all the components in the 3 phase supply chain. Start from the contactor closest to the rectifier and work backwards towards the mains switch. The contactors can be closed manually to perform the test. Refer to the electrical drawings for the cabinet. 3) Check the indication LEDs on the rectifier unit. The significance of these is described in the Trouble Shooting Manual. 4) If the voltage is OK, check any other error log messages coinciding in time with this one for clues. 6 Trouble shooting by Event log 184 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 39474, Rectifier Current Warning Description The rectifier connected to drive communication link arg in drive module arg is approaching overload. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The total motor current may be greater than that which the rectifier can supply. Recommended actions 1) If possible, rewrite the user program to reduce the amount of hard acceleration. 39475, Rectifier Current Error Description The rectifier connected to drive communication link arg in drive module arg has reached overload. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The total motor current may be greater than that which the rectifier can supply. Recommended actions 1) If possible, rewrite the user program to reduce the amount of hard acceleration. 39476, Rectifier Temperature Warning Description The temperature in the rectifier unit connected to drive communication link arg in drive module arg is approaching a too high a level. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The cooling fans may be faulty or the air flow may be obstructed. The ambient temperature may be too high or the system may be running with a too high load for extended periods. Recommended actions 1) Check that the fans are running and that the air flow is not obstructed. 2) Check that the ambient temperature does not exceed the cabinet rating. 3) If the system contains additional axes then check that motors are not too large for the drive units. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 39477, Rectifier Temperature Error Description The temperature in the rectifier unit connected to drive communication link arg in drive module arg has reached a too high a level. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The cooling fans may be faulty or the air flow may be obstructed. The ambient temperature may be too high or the system may be running with a too high load for extended periods. Recommended actions 1) Check that the fans are running and that the air flow is not obstructed. 2) Check that the ambient temperature does not exceed the cabinet rating. 3) If the system contains additional axes then check that motors are not too large for the drive units. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 39478, Internal Motor PTC Temperature Error Description The temperature in one or more robot motors connected to drive module arg is has reached a too high a level. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The motor may have stalled (possibly due to a collision), the motor may be overloaded or the ambient temperature may be higher than the rated level for the robot. Recommended actions 1) Check that the robot has not collided. 2) Check that the ambient temperature does not exceed the robot rating. 3) Allow the robot to cool down, and then run the system again. Replace any motors damaged by the excessive heat. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 39479, External Motor PTC Temperature Error Description One or more additional axis motors connected to drive module arg is has reached a too high a level.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	186	6 Trouble shooting by Event log 183 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 39470, Power Semiconductor Warning Description The power semiconductor is approaching overload for joint arg , in drive unit number arg , drive module arg . Consequences - Probable causes The motor load may be too high, the motor may have stalled (maybe due to a collision), the motor load may be too high or there may not be enough cooling. Recommended actions 1) Check that the robot has not collided. 2) Check that the fans are running and that the air flow is not obstructed. 3) Check that the ambient temperature does not exceed the cabinet rating. 4) If the system contains additional axes then check that motors are not too large for the drive units. 5) If possible, rewrite the user program to reduce the amount of hard acceleration. 39471, Power Semiconductor Overload Error Description The power semiconductor has been overloaded for joint arg , in drive unit number arg , drive module arg . Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The motor load may be too high, the motor may have stalled (maybe due to a collision), the motor load may be too high or there may not be enough cooling. Recommended actions 1) Check that the robot has not collided. 2) Check that the fans are running and that the air flow is not obstructed. 3) Check that the ambient temperature does not exceed the cabinet rating. 4) If the system contains additional axes then check that motors are not too large for the drive units. 5) If possible, rewrite the user program to reduce the amount of hard acceleration. 39472, Incoming Mains Phase Missing Description The rectifier connected to communication link arg in drive module arg detects a power loss in one phase. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by an actual mains power loss, some malfunction in the Motors ON contactors or its cabling or in another part of the three phase chain inside the cabinet. On rare occasions, this fault may occur in combination with other faults, in which case this may be found in the error log. Recommended actions 1) Make sure the mains switch is closed and that there is mains voltage present. No volts means the problem is in mains cable connector or the factory power supply. 2) If the voltage is OK, disconnect the input mains cable and measure the resistance of all three phases across all the components in the 3 phase supply chain. Start from the contactor closest to the rectifier and work backwards towards the mains switch. The contactors can be closed manually to perform the test. Refer to the electrical drawings for the cabinet. 3) Check the indication LEDs on the rectifier unit. The significance of these is described in the Trouble Shooting Manual. 4) If the voltage is OK, check any other error log messages coinciding in time with this one for clues. 39473, All Incoming Mains Phases Missing Description The rectifier connected to communication link arg in drive module arg detects a power loss in one or more phases. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes This may be caused by an actual mains power loss, some malfunction in the Motors ON contactors or its cabling or in another part of the three phase chain inside the cabinet. On rare occasions, this fault may occur in combination with other faults, in which case this may be found in the error log. Recommended actions 1) Make sure the mains switch is closed and that there is mains voltage present. No volts means the problem is in mains cable connector or the factory power supply. 2) If the voltage is OK, disconnect the input mains cable and measure the resistance of all three phases across all the components in the 3 phase supply chain. Start from the contactor closest to the rectifier and work backwards towards the mains switch. The contactors can be closed manually to perform the test. Refer to the electrical drawings for the cabinet. 3) Check the indication LEDs on the rectifier unit. The significance of these is described in the Trouble Shooting Manual. 4) If the voltage is OK, check any other error log messages coinciding in time with this one for clues. 6 Trouble shooting by Event log 184 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 39474, Rectifier Current Warning Description The rectifier connected to drive communication link arg in drive module arg is approaching overload. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The total motor current may be greater than that which the rectifier can supply. Recommended actions 1) If possible, rewrite the user program to reduce the amount of hard acceleration. 39475, Rectifier Current Error Description The rectifier connected to drive communication link arg in drive module arg has reached overload. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The total motor current may be greater than that which the rectifier can supply. Recommended actions 1) If possible, rewrite the user program to reduce the amount of hard acceleration. 39476, Rectifier Temperature Warning Description The temperature in the rectifier unit connected to drive communication link arg in drive module arg is approaching a too high a level. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The cooling fans may be faulty or the air flow may be obstructed. The ambient temperature may be too high or the system may be running with a too high load for extended periods. Recommended actions 1) Check that the fans are running and that the air flow is not obstructed. 2) Check that the ambient temperature does not exceed the cabinet rating. 3) If the system contains additional axes then check that motors are not too large for the drive units. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 39477, Rectifier Temperature Error Description The temperature in the rectifier unit connected to drive communication link arg in drive module arg has reached a too high a level. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The cooling fans may be faulty or the air flow may be obstructed. The ambient temperature may be too high or the system may be running with a too high load for extended periods. Recommended actions 1) Check that the fans are running and that the air flow is not obstructed. 2) Check that the ambient temperature does not exceed the cabinet rating. 3) If the system contains additional axes then check that motors are not too large for the drive units. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 39478, Internal Motor PTC Temperature Error Description The temperature in one or more robot motors connected to drive module arg is has reached a too high a level. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The motor may have stalled (possibly due to a collision), the motor may be overloaded or the ambient temperature may be higher than the rated level for the robot. Recommended actions 1) Check that the robot has not collided. 2) Check that the ambient temperature does not exceed the robot rating. 3) Allow the robot to cool down, and then run the system again. Replace any motors damaged by the excessive heat. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 39479, External Motor PTC Temperature Error Description One or more additional axis motors connected to drive module arg is has reached a too high a level. 6 Trouble shooting by Event log 185 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The motor may have stalled (possibly due to a collision), the motor may be overloaded or the ambient temperature may be higher than the rated level for the robot. Recommended actions 1) Check that the additional axis has not collided. 2) Check that the ambient temperature does not exceed the rating. 3) Allow the motor to cool down, and then run the system again. Replace any motors damaged by the excessive heat. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 39482, Mains Voltage Too High Description The mains voltage detected in drive module arg is too high. Consequences The robot can not be operated. Probable causes The mains transformer may be incorrectly wired or the external supply voltage may be too high. Recommended actions 1) Measure the incoming mains voltage at the main contactor in the drive module. Make sure it is within the range specified for this module. 2) Check the wiring of the mains transformer as detailed in the robot Product Manual. 39483, DC Link Short Circuit Description A short circuit has been detected on the DC link of drive module arg . Consequences The robot can not be operated. Probable causes The DC bus bar may be badly connected or its contact surfaces may be contaminated causing a short circuit. Recommended actions 1) Check that all DC link bus bars have been correctly connected. 2) Check that all contacts are free from contamination. 39484, Run chain open in motor on state Description Run chain arg is open when system is in motor on state. The problem occurred in drive system arg . Consequences System goes to SYS_HALT. Probable causes 1) Cables and connections on the Safety System are unplugged or damaged. 2) The contactor for this run chain in the drive module may be stuck due to mechanical problem in contactor itself. 3) The help contactor on the contactor can suffer from bad galvanic behavior or faulty cable to the Safety System. Recommended actions 1) Check if a motor contactor is stucked. 2) Replace faulty motor contactor. 39485, Run chain close in motor off state Description Run chain arg is open when system is in motor on state. The problem occurred in drive system arg . Consequences System goes to SYS_HALT. Probable causes 1) The contactor for this run chain placed in the drive module has been pulled down manually. 2) The contactor has been welded in close position. Recommended actions 1) If the contactor is not released and stays in pulled position, shut down the system and replace the contactor. 2) If the contactor has been pulled down manually, take this message as a warning only. 39486, DC Link Not Connected Description The DC Link connection to the drive serving joint arg in drive module arg , drive unit number arg is missing or is not properly connected. Consequences The system goes to SYS_HALT. Probable causes 1) The DC Bussbar is either missing or is not properly connected. 2) If the bussbar is correctly connected. The drive unit reporting the error may have a fault. Recommended actions 1) Check the DC Bussbar is properly connected to all the drive units 39500, Logic Voltage to Drive Unit Warning Description The 24V supply from the Drive Module Power Supply to the main drive unit in drive module arg is out of range.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	187	6 Trouble shooting by Event log 184 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 39474, Rectifier Current Warning Description The rectifier connected to drive communication link arg in drive module arg is approaching overload. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The total motor current may be greater than that which the rectifier can supply. Recommended actions 1) If possible, rewrite the user program to reduce the amount of hard acceleration. 39475, Rectifier Current Error Description The rectifier connected to drive communication link arg in drive module arg has reached overload. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The total motor current may be greater than that which the rectifier can supply. Recommended actions 1) If possible, rewrite the user program to reduce the amount of hard acceleration. 39476, Rectifier Temperature Warning Description The temperature in the rectifier unit connected to drive communication link arg in drive module arg is approaching a too high a level. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The cooling fans may be faulty or the air flow may be obstructed. The ambient temperature may be too high or the system may be running with a too high load for extended periods. Recommended actions 1) Check that the fans are running and that the air flow is not obstructed. 2) Check that the ambient temperature does not exceed the cabinet rating. 3) If the system contains additional axes then check that motors are not too large for the drive units. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 39477, Rectifier Temperature Error Description The temperature in the rectifier unit connected to drive communication link arg in drive module arg has reached a too high a level. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The cooling fans may be faulty or the air flow may be obstructed. The ambient temperature may be too high or the system may be running with a too high load for extended periods. Recommended actions 1) Check that the fans are running and that the air flow is not obstructed. 2) Check that the ambient temperature does not exceed the cabinet rating. 3) If the system contains additional axes then check that motors are not too large for the drive units. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 39478, Internal Motor PTC Temperature Error Description The temperature in one or more robot motors connected to drive module arg is has reached a too high a level. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The motor may have stalled (possibly due to a collision), the motor may be overloaded or the ambient temperature may be higher than the rated level for the robot. Recommended actions 1) Check that the robot has not collided. 2) Check that the ambient temperature does not exceed the robot rating. 3) Allow the robot to cool down, and then run the system again. Replace any motors damaged by the excessive heat. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 39479, External Motor PTC Temperature Error Description One or more additional axis motors connected to drive module arg is has reached a too high a level. 6 Trouble shooting by Event log 185 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The motor may have stalled (possibly due to a collision), the motor may be overloaded or the ambient temperature may be higher than the rated level for the robot. Recommended actions 1) Check that the additional axis has not collided. 2) Check that the ambient temperature does not exceed the rating. 3) Allow the motor to cool down, and then run the system again. Replace any motors damaged by the excessive heat. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 39482, Mains Voltage Too High Description The mains voltage detected in drive module arg is too high. Consequences The robot can not be operated. Probable causes The mains transformer may be incorrectly wired or the external supply voltage may be too high. Recommended actions 1) Measure the incoming mains voltage at the main contactor in the drive module. Make sure it is within the range specified for this module. 2) Check the wiring of the mains transformer as detailed in the robot Product Manual. 39483, DC Link Short Circuit Description A short circuit has been detected on the DC link of drive module arg . Consequences The robot can not be operated. Probable causes The DC bus bar may be badly connected or its contact surfaces may be contaminated causing a short circuit. Recommended actions 1) Check that all DC link bus bars have been correctly connected. 2) Check that all contacts are free from contamination. 39484, Run chain open in motor on state Description Run chain arg is open when system is in motor on state. The problem occurred in drive system arg . Consequences System goes to SYS_HALT. Probable causes 1) Cables and connections on the Safety System are unplugged or damaged. 2) The contactor for this run chain in the drive module may be stuck due to mechanical problem in contactor itself. 3) The help contactor on the contactor can suffer from bad galvanic behavior or faulty cable to the Safety System. Recommended actions 1) Check if a motor contactor is stucked. 2) Replace faulty motor contactor. 39485, Run chain close in motor off state Description Run chain arg is open when system is in motor on state. The problem occurred in drive system arg . Consequences System goes to SYS_HALT. Probable causes 1) The contactor for this run chain placed in the drive module has been pulled down manually. 2) The contactor has been welded in close position. Recommended actions 1) If the contactor is not released and stays in pulled position, shut down the system and replace the contactor. 2) If the contactor has been pulled down manually, take this message as a warning only. 39486, DC Link Not Connected Description The DC Link connection to the drive serving joint arg in drive module arg , drive unit number arg is missing or is not properly connected. Consequences The system goes to SYS_HALT. Probable causes 1) The DC Bussbar is either missing or is not properly connected. 2) If the bussbar is correctly connected. The drive unit reporting the error may have a fault. Recommended actions 1) Check the DC Bussbar is properly connected to all the drive units 39500, Logic Voltage to Drive Unit Warning Description The 24V supply from the Drive Module Power Supply to the main drive unit in drive module arg is out of range. 6 Trouble shooting by Event log 186 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences - Probable causes The 24V supply from the Drive Module Power Supply may be out of range. Recommended actions 1) Make sure the power cable from the Drive Module Power Supply to the main drive unit is connected correctly. 2) Check if the power supply unit LED is red. The full meaning of all LED indications are described in the Trouble Shooting Manual, IRC5. 39501, Logic Voltage to Drive Unit Error Description The 24V supply to the main drive unit in drive module arg is out of range. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The 24V supply from the power supply unit may be out of range. Recommended actions 1) Make sure the power cable from the power supply unit to the main drive unit is connected correctly. 2) Check if the power supply unit LED is red. The full meaning of all LED indications are described in the Trouble Shooting Manual, IRC5. 39502, Logic Voltage to Rectifier Error Description The 24V to the rectifier in drive module arg is out of range. Consequences - Probable causes The cable between the drive unit and the rectifier may be badly connected, or the power supply voltage to the drive unit may be out of range. Recommended actions 1) Check that the power cable between the power supply unit and the rectifier unit has been connected correctly. 2) Check the 24 V voltage in the power cable to the drive unit.. 39503, Power Supply Overtemperature Description The temperature in the Drive Module Power Supply of drive module arg has reached a critical level. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The fan unit may be faulty, the cooling air flow may be obstructed or the ambient temperature may be too high. Recommended actions 1) NOTE! Do not try to restart the controller for approx. ten minutes to let it cool down. 2) Make sure the fans are running and that the air flow is not obstructed. 3) Make sure the ambient temperature does not exceed the drive module rating. 4) Make sure the power supply connectors are correctly connected to the axis computer. 39504, Power Supply to Brakes Overload Description The brake power circuit in drive module arg draws too much current. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The brake power cable may be faulty (short circuit), or additional axis motors with brakes consuming too much power may be used. The fault may also occur if the cable from the power supply unit is not correctly connected to the drive module. Recommended actions 1) Make sure the power supply cable is correctly connected to the drive module. 2) Check the brake supply cable for short circuits. 3) Make sure the total current consumed by additional axes' motors does not exceed the specification for the drive module. 4) Make sure the power supply connectors are correctly connected to the axis computer. 5) Make sure the 24 V BRAKE voltage is within specified limits. See the Circuit Diagram in the Product Manual, IRC5. 39505, Mains Voltage to Power Supply Lost Description The mains power supply to the power supply unit in Drive Module arg is missing. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS FAIL.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	188	6 Trouble shooting by Event log 185 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The motor may have stalled (possibly due to a collision), the motor may be overloaded or the ambient temperature may be higher than the rated level for the robot. Recommended actions 1) Check that the additional axis has not collided. 2) Check that the ambient temperature does not exceed the rating. 3) Allow the motor to cool down, and then run the system again. Replace any motors damaged by the excessive heat. 4) If possible, rewrite the user program to reduce the amount of hard acceleration. 39482, Mains Voltage Too High Description The mains voltage detected in drive module arg is too high. Consequences The robot can not be operated. Probable causes The mains transformer may be incorrectly wired or the external supply voltage may be too high. Recommended actions 1) Measure the incoming mains voltage at the main contactor in the drive module. Make sure it is within the range specified for this module. 2) Check the wiring of the mains transformer as detailed in the robot Product Manual. 39483, DC Link Short Circuit Description A short circuit has been detected on the DC link of drive module arg . Consequences The robot can not be operated. Probable causes The DC bus bar may be badly connected or its contact surfaces may be contaminated causing a short circuit. Recommended actions 1) Check that all DC link bus bars have been correctly connected. 2) Check that all contacts are free from contamination. 39484, Run chain open in motor on state Description Run chain arg is open when system is in motor on state. The problem occurred in drive system arg . Consequences System goes to SYS_HALT. Probable causes 1) Cables and connections on the Safety System are unplugged or damaged. 2) The contactor for this run chain in the drive module may be stuck due to mechanical problem in contactor itself. 3) The help contactor on the contactor can suffer from bad galvanic behavior or faulty cable to the Safety System. Recommended actions 1) Check if a motor contactor is stucked. 2) Replace faulty motor contactor. 39485, Run chain close in motor off state Description Run chain arg is open when system is in motor on state. The problem occurred in drive system arg . Consequences System goes to SYS_HALT. Probable causes 1) The contactor for this run chain placed in the drive module has been pulled down manually. 2) The contactor has been welded in close position. Recommended actions 1) If the contactor is not released and stays in pulled position, shut down the system and replace the contactor. 2) If the contactor has been pulled down manually, take this message as a warning only. 39486, DC Link Not Connected Description The DC Link connection to the drive serving joint arg in drive module arg , drive unit number arg is missing or is not properly connected. Consequences The system goes to SYS_HALT. Probable causes 1) The DC Bussbar is either missing or is not properly connected. 2) If the bussbar is correctly connected. The drive unit reporting the error may have a fault. Recommended actions 1) Check the DC Bussbar is properly connected to all the drive units 39500, Logic Voltage to Drive Unit Warning Description The 24V supply from the Drive Module Power Supply to the main drive unit in drive module arg is out of range. 6 Trouble shooting by Event log 186 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences - Probable causes The 24V supply from the Drive Module Power Supply may be out of range. Recommended actions 1) Make sure the power cable from the Drive Module Power Supply to the main drive unit is connected correctly. 2) Check if the power supply unit LED is red. The full meaning of all LED indications are described in the Trouble Shooting Manual, IRC5. 39501, Logic Voltage to Drive Unit Error Description The 24V supply to the main drive unit in drive module arg is out of range. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The 24V supply from the power supply unit may be out of range. Recommended actions 1) Make sure the power cable from the power supply unit to the main drive unit is connected correctly. 2) Check if the power supply unit LED is red. The full meaning of all LED indications are described in the Trouble Shooting Manual, IRC5. 39502, Logic Voltage to Rectifier Error Description The 24V to the rectifier in drive module arg is out of range. Consequences - Probable causes The cable between the drive unit and the rectifier may be badly connected, or the power supply voltage to the drive unit may be out of range. Recommended actions 1) Check that the power cable between the power supply unit and the rectifier unit has been connected correctly. 2) Check the 24 V voltage in the power cable to the drive unit.. 39503, Power Supply Overtemperature Description The temperature in the Drive Module Power Supply of drive module arg has reached a critical level. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The fan unit may be faulty, the cooling air flow may be obstructed or the ambient temperature may be too high. Recommended actions 1) NOTE! Do not try to restart the controller for approx. ten minutes to let it cool down. 2) Make sure the fans are running and that the air flow is not obstructed. 3) Make sure the ambient temperature does not exceed the drive module rating. 4) Make sure the power supply connectors are correctly connected to the axis computer. 39504, Power Supply to Brakes Overload Description The brake power circuit in drive module arg draws too much current. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The brake power cable may be faulty (short circuit), or additional axis motors with brakes consuming too much power may be used. The fault may also occur if the cable from the power supply unit is not correctly connected to the drive module. Recommended actions 1) Make sure the power supply cable is correctly connected to the drive module. 2) Check the brake supply cable for short circuits. 3) Make sure the total current consumed by additional axes' motors does not exceed the specification for the drive module. 4) Make sure the power supply connectors are correctly connected to the axis computer. 5) Make sure the 24 V BRAKE voltage is within specified limits. See the Circuit Diagram in the Product Manual, IRC5. 39505, Mains Voltage to Power Supply Lost Description The mains power supply to the power supply unit in Drive Module arg is missing. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS FAIL. 6 Trouble shooting by Event log 187 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes The main power switch on the Drive Module may be turned off. The incoming mains cable may be faulty (break), or the circuit breaker for the power supply may have tripped. The fault may also occur if the connector from the power supply unit is not correctly connected to the axis computer. Recommended actions 1) Check that the main power switch in turned on for the Drive Module and restart the system. 2) Check that the connector from the power supply unit is correctly connected to the axis computer. 3) Measure the voltage at the mains contactor to ensure that the mains is present. 4) Check that the power supply fuses/circuit breakers in the drive module have not tripped. 39520, Communication lost with Drive Module Description The main computer has lost contact with drive module arg . Consequences The system goes to status SYS HALT No operation will be possible until the fault has been corrected. Probable causes This may be due to a cable break, badly connected connector or high levels of interference in the cable. Recommended actions 1) Make sure the cable between Control Module and Drive Module is not damaged and that both connectors are correctly connected. 2) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling. 39521, Drive Module Communication Warning Description There are a large number of communication errors being detected on the ethernet link to drive module arg . This can be due to external noise sources interfering with the cable. Recommended actions Check that there are no electromagnetic interference sources running near the cable or the drive or computer modules. 39522, Axis computer not found Description The axis computer in drive module arg is not connected to the main computer. Consequences The system goes to status SYS FAIL. No operation will be possible until the fault has been corrected. Probable causes This may be due to a cable break, badly connected connectors or loss of power supply. Recommended actions 1) Make sure the main power switch on Drive Module arg has been switched ON. 2) Make sure the cable between Control Module and Drive Module is not damaged and that both connectors are correctly connected. 3) Make sure the cable is connected to the correct AXC connector on the Main Computer Unit Robot Communication Card or EtherNet Board (if the MultiMove option has been installed). 4) Restart the system. 5) Make sure the Power Supply Unit in Drive Module arg is working correctly. 39523, Unused Axis computer connected Description Axis computer in the drive module arg is connected to the main computer but not in use. Probable causes This can be due to configuration problem. Recommended actions 1. Disconnect the unused axis computer or setup the system to use the axis computer. 2. Restart the system. 39524, Drive Module Command timeout Description Drive Module arg does not respond to command arg . The system has stopped the program for safety reasons. Recommended actions 1. Check that drive module is powered on. 2. Check the cable between the main computer and axis computer. 3. Restart the system. 39525, Drive Module startup error Description The system has failed to complete the initialization phase of drive module arg . Consequences The system goes to System Failure state. Probable causes The system has failed to complete the initialization phase of the drive module. Recommended actions 1) Retry by restarting the system using the main power switch. 2) Check for other hardware eventlog messages.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	189	6 Trouble shooting by Event log 186 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Consequences - Probable causes The 24V supply from the Drive Module Power Supply may be out of range. Recommended actions 1) Make sure the power cable from the Drive Module Power Supply to the main drive unit is connected correctly. 2) Check if the power supply unit LED is red. The full meaning of all LED indications are described in the Trouble Shooting Manual, IRC5. 39501, Logic Voltage to Drive Unit Error Description The 24V supply to the main drive unit in drive module arg is out of range. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The 24V supply from the power supply unit may be out of range. Recommended actions 1) Make sure the power cable from the power supply unit to the main drive unit is connected correctly. 2) Check if the power supply unit LED is red. The full meaning of all LED indications are described in the Trouble Shooting Manual, IRC5. 39502, Logic Voltage to Rectifier Error Description The 24V to the rectifier in drive module arg is out of range. Consequences - Probable causes The cable between the drive unit and the rectifier may be badly connected, or the power supply voltage to the drive unit may be out of range. Recommended actions 1) Check that the power cable between the power supply unit and the rectifier unit has been connected correctly. 2) Check the 24 V voltage in the power cable to the drive unit.. 39503, Power Supply Overtemperature Description The temperature in the Drive Module Power Supply of drive module arg has reached a critical level. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The fan unit may be faulty, the cooling air flow may be obstructed or the ambient temperature may be too high. Recommended actions 1) NOTE! Do not try to restart the controller for approx. ten minutes to let it cool down. 2) Make sure the fans are running and that the air flow is not obstructed. 3) Make sure the ambient temperature does not exceed the drive module rating. 4) Make sure the power supply connectors are correctly connected to the axis computer. 39504, Power Supply to Brakes Overload Description The brake power circuit in drive module arg draws too much current. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS HALT. Probable causes The brake power cable may be faulty (short circuit), or additional axis motors with brakes consuming too much power may be used. The fault may also occur if the cable from the power supply unit is not correctly connected to the drive module. Recommended actions 1) Make sure the power supply cable is correctly connected to the drive module. 2) Check the brake supply cable for short circuits. 3) Make sure the total current consumed by additional axes' motors does not exceed the specification for the drive module. 4) Make sure the power supply connectors are correctly connected to the axis computer. 5) Make sure the 24 V BRAKE voltage is within specified limits. See the Circuit Diagram in the Product Manual, IRC5. 39505, Mains Voltage to Power Supply Lost Description The mains power supply to the power supply unit in Drive Module arg is missing. Consequences No operation will be possible until after correcting the fault. The system goes to status SYS FAIL. 6 Trouble shooting by Event log 187 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes The main power switch on the Drive Module may be turned off. The incoming mains cable may be faulty (break), or the circuit breaker for the power supply may have tripped. The fault may also occur if the connector from the power supply unit is not correctly connected to the axis computer. Recommended actions 1) Check that the main power switch in turned on for the Drive Module and restart the system. 2) Check that the connector from the power supply unit is correctly connected to the axis computer. 3) Measure the voltage at the mains contactor to ensure that the mains is present. 4) Check that the power supply fuses/circuit breakers in the drive module have not tripped. 39520, Communication lost with Drive Module Description The main computer has lost contact with drive module arg . Consequences The system goes to status SYS HALT No operation will be possible until the fault has been corrected. Probable causes This may be due to a cable break, badly connected connector or high levels of interference in the cable. Recommended actions 1) Make sure the cable between Control Module and Drive Module is not damaged and that both connectors are correctly connected. 2) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling. 39521, Drive Module Communication Warning Description There are a large number of communication errors being detected on the ethernet link to drive module arg . This can be due to external noise sources interfering with the cable. Recommended actions Check that there are no electromagnetic interference sources running near the cable or the drive or computer modules. 39522, Axis computer not found Description The axis computer in drive module arg is not connected to the main computer. Consequences The system goes to status SYS FAIL. No operation will be possible until the fault has been corrected. Probable causes This may be due to a cable break, badly connected connectors or loss of power supply. Recommended actions 1) Make sure the main power switch on Drive Module arg has been switched ON. 2) Make sure the cable between Control Module and Drive Module is not damaged and that both connectors are correctly connected. 3) Make sure the cable is connected to the correct AXC connector on the Main Computer Unit Robot Communication Card or EtherNet Board (if the MultiMove option has been installed). 4) Restart the system. 5) Make sure the Power Supply Unit in Drive Module arg is working correctly. 39523, Unused Axis computer connected Description Axis computer in the drive module arg is connected to the main computer but not in use. Probable causes This can be due to configuration problem. Recommended actions 1. Disconnect the unused axis computer or setup the system to use the axis computer. 2. Restart the system. 39524, Drive Module Command timeout Description Drive Module arg does not respond to command arg . The system has stopped the program for safety reasons. Recommended actions 1. Check that drive module is powered on. 2. Check the cable between the main computer and axis computer. 3. Restart the system. 39525, Drive Module startup error Description The system has failed to complete the initialization phase of drive module arg . Consequences The system goes to System Failure state. Probable causes The system has failed to complete the initialization phase of the drive module. Recommended actions 1) Retry by restarting the system using the main power switch. 2) Check for other hardware eventlog messages. 6 Trouble shooting by Event log 188 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 39530, Axis Computer Lost Communication With Safety System Description Communication has been lost between axis computer and the Safety System in drive module arg . Consequences System goes to status SYS FAIL. Probable causes This may be due to a faulty communication cable or connection between the axis computer and the Safety System. It may also be due to severe interference or if the Safety System has lost its power. Recommended actions 1) Check cable between the axis computer and the Safety System is intact and correctly connected. 2) Check power supply connected to the Safety System. 3) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling. 39531, Run chain glitch test not running Description The glitch test of the run chain has not been performed. The problem was discovered by the Safety System connected to the axis computer in drive module arg . Consequences System goes to status SYS HALT. Probable causes This may be due internal errors. Recommended actions Contact your local ABB support office. 40001, Argument error Description The optional argument arg has been used more than once in the same routine call. Recommended actions 1) Make sure the optional parameter is not used more than once in the same routine call. 40002, Argument error Description The argument arg has been specified for more than one parameter. Recommended actions The parameter list, from which the parameter is selected, contains parameters mutually exclusive. 1) Make sure the argument is used for one parameter only. 40003, Argument error Description An argument for the required parameter arg was expected, but the optional argument arg was found. Recommended actions 1) Make sure all arguments are specified in the same order as the parameters for the routine called. 40004, Argument error Description The argument for REF parameter arg is not a data reference. Recommended actions 1) Make sure the argument is a data or a parameter reference. 40005, Argument error Description The argument for INOUT parameter arg is not a variable or persistent reference, or it is read-only. Recommended actions 1) Make sure the argument is a variable or a persistent variable parameter or a persistent parameter reference and that it is NOT read- only. 2) Also make sure the argument is NOT written within brackets (). 40006, Argument error Description Parameter arg is missing an optional argument value. Recommended actions The only parameters that may be specified by a name only are "switch" parameters. All others must be assigned a value. 1) Make sure parameter has a value. 40007, Argument error Description The optional argument arg is not found in its correct position in the argument list. Recommended actions 1) Make sure all arguments are specified in the same order as the parameters for the routine called. 40008, Argument error Description A reference to the optional parameter arg is missing.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	190	6 Trouble shooting by Event log 187 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Probable causes The main power switch on the Drive Module may be turned off. The incoming mains cable may be faulty (break), or the circuit breaker for the power supply may have tripped. The fault may also occur if the connector from the power supply unit is not correctly connected to the axis computer. Recommended actions 1) Check that the main power switch in turned on for the Drive Module and restart the system. 2) Check that the connector from the power supply unit is correctly connected to the axis computer. 3) Measure the voltage at the mains contactor to ensure that the mains is present. 4) Check that the power supply fuses/circuit breakers in the drive module have not tripped. 39520, Communication lost with Drive Module Description The main computer has lost contact with drive module arg . Consequences The system goes to status SYS HALT No operation will be possible until the fault has been corrected. Probable causes This may be due to a cable break, badly connected connector or high levels of interference in the cable. Recommended actions 1) Make sure the cable between Control Module and Drive Module is not damaged and that both connectors are correctly connected. 2) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling. 39521, Drive Module Communication Warning Description There are a large number of communication errors being detected on the ethernet link to drive module arg . This can be due to external noise sources interfering with the cable. Recommended actions Check that there are no electromagnetic interference sources running near the cable or the drive or computer modules. 39522, Axis computer not found Description The axis computer in drive module arg is not connected to the main computer. Consequences The system goes to status SYS FAIL. No operation will be possible until the fault has been corrected. Probable causes This may be due to a cable break, badly connected connectors or loss of power supply. Recommended actions 1) Make sure the main power switch on Drive Module arg has been switched ON. 2) Make sure the cable between Control Module and Drive Module is not damaged and that both connectors are correctly connected. 3) Make sure the cable is connected to the correct AXC connector on the Main Computer Unit Robot Communication Card or EtherNet Board (if the MultiMove option has been installed). 4) Restart the system. 5) Make sure the Power Supply Unit in Drive Module arg is working correctly. 39523, Unused Axis computer connected Description Axis computer in the drive module arg is connected to the main computer but not in use. Probable causes This can be due to configuration problem. Recommended actions 1. Disconnect the unused axis computer or setup the system to use the axis computer. 2. Restart the system. 39524, Drive Module Command timeout Description Drive Module arg does not respond to command arg . The system has stopped the program for safety reasons. Recommended actions 1. Check that drive module is powered on. 2. Check the cable between the main computer and axis computer. 3. Restart the system. 39525, Drive Module startup error Description The system has failed to complete the initialization phase of drive module arg . Consequences The system goes to System Failure state. Probable causes The system has failed to complete the initialization phase of the drive module. Recommended actions 1) Retry by restarting the system using the main power switch. 2) Check for other hardware eventlog messages. 6 Trouble shooting by Event log 188 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 39530, Axis Computer Lost Communication With Safety System Description Communication has been lost between axis computer and the Safety System in drive module arg . Consequences System goes to status SYS FAIL. Probable causes This may be due to a faulty communication cable or connection between the axis computer and the Safety System. It may also be due to severe interference or if the Safety System has lost its power. Recommended actions 1) Check cable between the axis computer and the Safety System is intact and correctly connected. 2) Check power supply connected to the Safety System. 3) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling. 39531, Run chain glitch test not running Description The glitch test of the run chain has not been performed. The problem was discovered by the Safety System connected to the axis computer in drive module arg . Consequences System goes to status SYS HALT. Probable causes This may be due internal errors. Recommended actions Contact your local ABB support office. 40001, Argument error Description The optional argument arg has been used more than once in the same routine call. Recommended actions 1) Make sure the optional parameter is not used more than once in the same routine call. 40002, Argument error Description The argument arg has been specified for more than one parameter. Recommended actions The parameter list, from which the parameter is selected, contains parameters mutually exclusive. 1) Make sure the argument is used for one parameter only. 40003, Argument error Description An argument for the required parameter arg was expected, but the optional argument arg was found. Recommended actions 1) Make sure all arguments are specified in the same order as the parameters for the routine called. 40004, Argument error Description The argument for REF parameter arg is not a data reference. Recommended actions 1) Make sure the argument is a data or a parameter reference. 40005, Argument error Description The argument for INOUT parameter arg is not a variable or persistent reference, or it is read-only. Recommended actions 1) Make sure the argument is a variable or a persistent variable parameter or a persistent parameter reference and that it is NOT read- only. 2) Also make sure the argument is NOT written within brackets (). 40006, Argument error Description Parameter arg is missing an optional argument value. Recommended actions The only parameters that may be specified by a name only are "switch" parameters. All others must be assigned a value. 1) Make sure parameter has a value. 40007, Argument error Description The optional argument arg is not found in its correct position in the argument list. Recommended actions 1) Make sure all arguments are specified in the same order as the parameters for the routine called. 40008, Argument error Description A reference to the optional parameter arg is missing. 6 Trouble shooting by Event log 189 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Each optional parameter must have a reference argument, specified with a leading backslash character (\). 1) Change the required argument into an optional argument. 40009, Argument error Description A reference to the required parameter arg in a conditional argument is missing. Recommended actions Each conditional value for an optional parameter must refer to an optional parameter in the calling routine. 1) Change the conditional value. 40010, Argument error Description A reference to the required parameter arg in an optional argument is missing. Recommended actions Each required parameter must have a reference argument, specified with a leading backslash character (\). 1) Change the optional argument into a required argument. 40011, Argument error Description The required argument arg is not found in its correct position in the argument list. Recommended actions Make sure all arguments are specified in the same order as the parameters for the routine called. 40012, Argument error Description The "switch" argument arg has a value. Probable causes An argument corresponding to a "switch" parameter may not be assigned a value. Recommended actions 1) Remove the value. 40013, Argument error Description The call to routine arg has too few arguments. Recommended actions A routine call must supply values for all required parameters of the routine being called. The argument list must have as many arguments, as the parameter list has parameters. 1) Add more arguments to fit the parameter list. 40014, Argument error Description The call to routine arg has too many arguments. Recommended actions No arguments, more than those defined by the called routine parameter list, must be supplied. The argument list must have as many arguments, as the parameter list has parameters. 1) Remove excessive arguments from the argument list. 40015, Data declaration error Description The number of array dimensions is arg , but may be 1, 2 or 3 only. Recommended actions 1) Change the dimension expression. 40016, Data declaration error Description Too many dimensions in array definition. Recommended actions An array may have at most 3 dimensions. Rewrite the program so that no more than 3 dimensions are needed. 40017, Type error Description Indexed data arg , arg is not of array type. Recommended actions Only data that have been declared to be arrays may be indexed. 1) Remove the index or indices. 2) Declare the data to be an array. 40018, Type error Description Data arg , arg is not of record type. Recommended actions Components are only available for data of record type. 1) Check the type and name of the referenced data.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	191	6 Trouble shooting by Event log 188 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 39530, Axis Computer Lost Communication With Safety System Description Communication has been lost between axis computer and the Safety System in drive module arg . Consequences System goes to status SYS FAIL. Probable causes This may be due to a faulty communication cable or connection between the axis computer and the Safety System. It may also be due to severe interference or if the Safety System has lost its power. Recommended actions 1) Check cable between the axis computer and the Safety System is intact and correctly connected. 2) Check power supply connected to the Safety System. 3) Make sure no extreme levels of electromagnetic interference are emitted close to the robot cabling. 39531, Run chain glitch test not running Description The glitch test of the run chain has not been performed. The problem was discovered by the Safety System connected to the axis computer in drive module arg . Consequences System goes to status SYS HALT. Probable causes This may be due internal errors. Recommended actions Contact your local ABB support office. 40001, Argument error Description The optional argument arg has been used more than once in the same routine call. Recommended actions 1) Make sure the optional parameter is not used more than once in the same routine call. 40002, Argument error Description The argument arg has been specified for more than one parameter. Recommended actions The parameter list, from which the parameter is selected, contains parameters mutually exclusive. 1) Make sure the argument is used for one parameter only. 40003, Argument error Description An argument for the required parameter arg was expected, but the optional argument arg was found. Recommended actions 1) Make sure all arguments are specified in the same order as the parameters for the routine called. 40004, Argument error Description The argument for REF parameter arg is not a data reference. Recommended actions 1) Make sure the argument is a data or a parameter reference. 40005, Argument error Description The argument for INOUT parameter arg is not a variable or persistent reference, or it is read-only. Recommended actions 1) Make sure the argument is a variable or a persistent variable parameter or a persistent parameter reference and that it is NOT read- only. 2) Also make sure the argument is NOT written within brackets (). 40006, Argument error Description Parameter arg is missing an optional argument value. Recommended actions The only parameters that may be specified by a name only are "switch" parameters. All others must be assigned a value. 1) Make sure parameter has a value. 40007, Argument error Description The optional argument arg is not found in its correct position in the argument list. Recommended actions 1) Make sure all arguments are specified in the same order as the parameters for the routine called. 40008, Argument error Description A reference to the optional parameter arg is missing. 6 Trouble shooting by Event log 189 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Each optional parameter must have a reference argument, specified with a leading backslash character (\). 1) Change the required argument into an optional argument. 40009, Argument error Description A reference to the required parameter arg in a conditional argument is missing. Recommended actions Each conditional value for an optional parameter must refer to an optional parameter in the calling routine. 1) Change the conditional value. 40010, Argument error Description A reference to the required parameter arg in an optional argument is missing. Recommended actions Each required parameter must have a reference argument, specified with a leading backslash character (\). 1) Change the optional argument into a required argument. 40011, Argument error Description The required argument arg is not found in its correct position in the argument list. Recommended actions Make sure all arguments are specified in the same order as the parameters for the routine called. 40012, Argument error Description The "switch" argument arg has a value. Probable causes An argument corresponding to a "switch" parameter may not be assigned a value. Recommended actions 1) Remove the value. 40013, Argument error Description The call to routine arg has too few arguments. Recommended actions A routine call must supply values for all required parameters of the routine being called. The argument list must have as many arguments, as the parameter list has parameters. 1) Add more arguments to fit the parameter list. 40014, Argument error Description The call to routine arg has too many arguments. Recommended actions No arguments, more than those defined by the called routine parameter list, must be supplied. The argument list must have as many arguments, as the parameter list has parameters. 1) Remove excessive arguments from the argument list. 40015, Data declaration error Description The number of array dimensions is arg , but may be 1, 2 or 3 only. Recommended actions 1) Change the dimension expression. 40016, Data declaration error Description Too many dimensions in array definition. Recommended actions An array may have at most 3 dimensions. Rewrite the program so that no more than 3 dimensions are needed. 40017, Type error Description Indexed data arg , arg is not of array type. Recommended actions Only data that have been declared to be arrays may be indexed. 1) Remove the index or indices. 2) Declare the data to be an array. 40018, Type error Description Data arg , arg is not of record type. Recommended actions Components are only available for data of record type. 1) Check the type and name of the referenced data. 6 Trouble shooting by Event log 190 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 40019, Limit error Description Task arg : Error when creating the persistent variable arg . The error occurred when the persistent variable was to be inserted into the database. Program Ref. arg Consequences The created persistent variable can not be used in a RAPID program. Probable causes The program memory is full or fragmentated. Recommended actions Check if large data structures could be split into smaller blocks. Use of installed modules can save program memory. 40020, Data declaration error Description Expression arg is not a constant expression. Recommended actions Any expression contained within a data declaration must be a constant expression. 1) Make sure no expression contains variables or persistent references, or function calls. 40021, Instruction error Description Missing expression in RETURN instruction. Probable causes A RETURN instruction within a function must specify a value to be returned. Recommended actions 1) Add a value expression. 40022, Type error Description Illegal combination of operand types arg and arg for the '' operator. Recommended actions Allowed operand type combinations are: "num""num", "num""pos", "pos""num", "pos""pos" and "orient""orient". 1) Check the operand types. 40023, Instruction error Description Cannot transfer control into another instruction list. Recommended actions It is not possible to jump into a program flow instruction. 1) Make sure that the label is located in the same instruction list as the GOTO instruction, at the same or an outer level. 40024, Type error Description Illegal type arg for left operand of binary '+' or '-' operator. Recommended actions Allowed operand types for the binary "+" operator are "num", "pos" and "string", and for the binary "-" operator "num" and "pos". 1) Check the operand types. 40025, Type error Description Illegal type arg for operand of unary '+' or '-' operator. Recommended actions Allowed operand types for the unary "+" and "-" operators are "num" and "pos". 1) Check the operand types. 40026, Type error Description Illegal type arg for right operand of binary '+' or '-' operator. Recommended actions Allowed operand types for the binary "+" operator are "num", "pos" and "string", and for the binary "-" operator "num" and "pos". 1) Check the operand types. 40027, Type error Description Illegal type arg for left operand of '/', 'DIV' or 'MOD' operator. Recommended actions Allowed operand type for the "/", "DIV" or "MOD" operators is "num". 1) Check the operand types. 40028, Type error Description Illegal type arg for right operand of '/', 'DIV' or 'MOD' operator. Recommended actions Allowed operand type for the "/", "DIV" or "MOD" operators is "num". 1) Check the operand types.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	192	6 Trouble shooting by Event log 189 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Each optional parameter must have a reference argument, specified with a leading backslash character (\). 1) Change the required argument into an optional argument. 40009, Argument error Description A reference to the required parameter arg in a conditional argument is missing. Recommended actions Each conditional value for an optional parameter must refer to an optional parameter in the calling routine. 1) Change the conditional value. 40010, Argument error Description A reference to the required parameter arg in an optional argument is missing. Recommended actions Each required parameter must have a reference argument, specified with a leading backslash character (\). 1) Change the optional argument into a required argument. 40011, Argument error Description The required argument arg is not found in its correct position in the argument list. Recommended actions Make sure all arguments are specified in the same order as the parameters for the routine called. 40012, Argument error Description The "switch" argument arg has a value. Probable causes An argument corresponding to a "switch" parameter may not be assigned a value. Recommended actions 1) Remove the value. 40013, Argument error Description The call to routine arg has too few arguments. Recommended actions A routine call must supply values for all required parameters of the routine being called. The argument list must have as many arguments, as the parameter list has parameters. 1) Add more arguments to fit the parameter list. 40014, Argument error Description The call to routine arg has too many arguments. Recommended actions No arguments, more than those defined by the called routine parameter list, must be supplied. The argument list must have as many arguments, as the parameter list has parameters. 1) Remove excessive arguments from the argument list. 40015, Data declaration error Description The number of array dimensions is arg , but may be 1, 2 or 3 only. Recommended actions 1) Change the dimension expression. 40016, Data declaration error Description Too many dimensions in array definition. Recommended actions An array may have at most 3 dimensions. Rewrite the program so that no more than 3 dimensions are needed. 40017, Type error Description Indexed data arg , arg is not of array type. Recommended actions Only data that have been declared to be arrays may be indexed. 1) Remove the index or indices. 2) Declare the data to be an array. 40018, Type error Description Data arg , arg is not of record type. Recommended actions Components are only available for data of record type. 1) Check the type and name of the referenced data. 6 Trouble shooting by Event log 190 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 40019, Limit error Description Task arg : Error when creating the persistent variable arg . The error occurred when the persistent variable was to be inserted into the database. Program Ref. arg Consequences The created persistent variable can not be used in a RAPID program. Probable causes The program memory is full or fragmentated. Recommended actions Check if large data structures could be split into smaller blocks. Use of installed modules can save program memory. 40020, Data declaration error Description Expression arg is not a constant expression. Recommended actions Any expression contained within a data declaration must be a constant expression. 1) Make sure no expression contains variables or persistent references, or function calls. 40021, Instruction error Description Missing expression in RETURN instruction. Probable causes A RETURN instruction within a function must specify a value to be returned. Recommended actions 1) Add a value expression. 40022, Type error Description Illegal combination of operand types arg and arg for the '' operator. Recommended actions Allowed operand type combinations are: "num""num", "num""pos", "pos""num", "pos""pos" and "orient""orient". 1) Check the operand types. 40023, Instruction error Description Cannot transfer control into another instruction list. Recommended actions It is not possible to jump into a program flow instruction. 1) Make sure that the label is located in the same instruction list as the GOTO instruction, at the same or an outer level. 40024, Type error Description Illegal type arg for left operand of binary '+' or '-' operator. Recommended actions Allowed operand types for the binary "+" operator are "num", "pos" and "string", and for the binary "-" operator "num" and "pos". 1) Check the operand types. 40025, Type error Description Illegal type arg for operand of unary '+' or '-' operator. Recommended actions Allowed operand types for the unary "+" and "-" operators are "num" and "pos". 1) Check the operand types. 40026, Type error Description Illegal type arg for right operand of binary '+' or '-' operator. Recommended actions Allowed operand types for the binary "+" operator are "num", "pos" and "string", and for the binary "-" operator "num" and "pos". 1) Check the operand types. 40027, Type error Description Illegal type arg for left operand of '/', 'DIV' or 'MOD' operator. Recommended actions Allowed operand type for the "/", "DIV" or "MOD" operators is "num". 1) Check the operand types. 40028, Type error Description Illegal type arg for right operand of '/', 'DIV' or 'MOD' operator. Recommended actions Allowed operand type for the "/", "DIV" or "MOD" operators is "num". 1) Check the operand types. 6 Trouble shooting by Event log 191 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 40029, Type error Description Illegal type arg for left operand of '<', '<=', '>' or '>=' operator. Recommended actions Allowed operand type for the "<", "<=", ">" or ">=" operators is "num". 1) Check the operand types. 40030, Type error Description Illegal type arg for right operand of '<', '<=', '>' or '>=' operator. Recommended actions Allowed operand type for the "<", "<=", ">" or ">=" operators is "num". 1) Check the operand types. 40031, Type error Description Illegal type arg for left operand of '' operator. Recommended actions Allowed operand types for the "" operator are "num", "pos" or "orient". 1) Check the operand types. 40032, Type error Description Illegal type arg for right operand of '' operator. Recommended actions Allowed operand types for the "" operator are "num", "pos" or "orient". 1) Check the operand types. 40033, Type error Description Illegal type arg for operand of 'NOT' operator. Recommended actions Allowed operand type for the "NOT" operator is "bool". 1) Check the operand types. 40034, Type error Description Illegal type arg for left operand of 'OR', 'XOR' or 'AND' operator. Recommended actions Allowed operand type for the "OR", "XOR" or "AND" operators is "bool". 1) Check the operand types. 40035, Type error Description Illegal type arg for right operand of 'OR', 'XOR' or 'AND' operator. Recommended actions Allowed operand type for the "OR", "XOR" or "AND" operators is "bool". 1) Check the operand types. 40036, Type error Description Incorrect number of indices in index list for array arg with arg dimension(s). Recommended actions 1) Make sure that the number of indices in the index list corresponds to the number of dimensions of the indexed data array. 40037, Data declaration error Description LOCAL illegal in routine constant declaration. Recommended actions Only program data declarations may have the LOCAL attribute. Remove the LOCAL attribute or move the declaration outside of the routine. 40038, Data declaration error Description LOCAL illegal in routine variable declaration Recommended actions Only program data declarations may have the LOCAL attribute. Remove the LOCAL attribute or move the declaration outside of the routine. 40039, Name error Description Constant name arg ambiguous. Recommended actions Routine data must have names that are unique within the routine. Program data must have names that are unique within the module. Rename the data or change the conflicting name.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	193	6 Trouble shooting by Event log 190 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 40019, Limit error Description Task arg : Error when creating the persistent variable arg . The error occurred when the persistent variable was to be inserted into the database. Program Ref. arg Consequences The created persistent variable can not be used in a RAPID program. Probable causes The program memory is full or fragmentated. Recommended actions Check if large data structures could be split into smaller blocks. Use of installed modules can save program memory. 40020, Data declaration error Description Expression arg is not a constant expression. Recommended actions Any expression contained within a data declaration must be a constant expression. 1) Make sure no expression contains variables or persistent references, or function calls. 40021, Instruction error Description Missing expression in RETURN instruction. Probable causes A RETURN instruction within a function must specify a value to be returned. Recommended actions 1) Add a value expression. 40022, Type error Description Illegal combination of operand types arg and arg for the '' operator. Recommended actions Allowed operand type combinations are: "num""num", "num""pos", "pos""num", "pos""pos" and "orient""orient". 1) Check the operand types. 40023, Instruction error Description Cannot transfer control into another instruction list. Recommended actions It is not possible to jump into a program flow instruction. 1) Make sure that the label is located in the same instruction list as the GOTO instruction, at the same or an outer level. 40024, Type error Description Illegal type arg for left operand of binary '+' or '-' operator. Recommended actions Allowed operand types for the binary "+" operator are "num", "pos" and "string", and for the binary "-" operator "num" and "pos". 1) Check the operand types. 40025, Type error Description Illegal type arg for operand of unary '+' or '-' operator. Recommended actions Allowed operand types for the unary "+" and "-" operators are "num" and "pos". 1) Check the operand types. 40026, Type error Description Illegal type arg for right operand of binary '+' or '-' operator. Recommended actions Allowed operand types for the binary "+" operator are "num", "pos" and "string", and for the binary "-" operator "num" and "pos". 1) Check the operand types. 40027, Type error Description Illegal type arg for left operand of '/', 'DIV' or 'MOD' operator. Recommended actions Allowed operand type for the "/", "DIV" or "MOD" operators is "num". 1) Check the operand types. 40028, Type error Description Illegal type arg for right operand of '/', 'DIV' or 'MOD' operator. Recommended actions Allowed operand type for the "/", "DIV" or "MOD" operators is "num". 1) Check the operand types. 6 Trouble shooting by Event log 191 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 40029, Type error Description Illegal type arg for left operand of '<', '<=', '>' or '>=' operator. Recommended actions Allowed operand type for the "<", "<=", ">" or ">=" operators is "num". 1) Check the operand types. 40030, Type error Description Illegal type arg for right operand of '<', '<=', '>' or '>=' operator. Recommended actions Allowed operand type for the "<", "<=", ">" or ">=" operators is "num". 1) Check the operand types. 40031, Type error Description Illegal type arg for left operand of '' operator. Recommended actions Allowed operand types for the "" operator are "num", "pos" or "orient". 1) Check the operand types. 40032, Type error Description Illegal type arg for right operand of '' operator. Recommended actions Allowed operand types for the "" operator are "num", "pos" or "orient". 1) Check the operand types. 40033, Type error Description Illegal type arg for operand of 'NOT' operator. Recommended actions Allowed operand type for the "NOT" operator is "bool". 1) Check the operand types. 40034, Type error Description Illegal type arg for left operand of 'OR', 'XOR' or 'AND' operator. Recommended actions Allowed operand type for the "OR", "XOR" or "AND" operators is "bool". 1) Check the operand types. 40035, Type error Description Illegal type arg for right operand of 'OR', 'XOR' or 'AND' operator. Recommended actions Allowed operand type for the "OR", "XOR" or "AND" operators is "bool". 1) Check the operand types. 40036, Type error Description Incorrect number of indices in index list for array arg with arg dimension(s). Recommended actions 1) Make sure that the number of indices in the index list corresponds to the number of dimensions of the indexed data array. 40037, Data declaration error Description LOCAL illegal in routine constant declaration. Recommended actions Only program data declarations may have the LOCAL attribute. Remove the LOCAL attribute or move the declaration outside of the routine. 40038, Data declaration error Description LOCAL illegal in routine variable declaration Recommended actions Only program data declarations may have the LOCAL attribute. Remove the LOCAL attribute or move the declaration outside of the routine. 40039, Name error Description Constant name arg ambiguous. Recommended actions Routine data must have names that are unique within the routine. Program data must have names that are unique within the module. Rename the data or change the conflicting name. 6 Trouble shooting by Event log 192 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 40040, Name error Description Global constant name arg ambiguous. Recommended actions Global data must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the data or change the conflicting name. 40041, Name error Description Global persistent name arg ambiguous. Recommended actions Global data must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the data or change the conflicting name. 40042, Name error Description Global routine name arg ambiguous. Recommended actions Global routines must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the routine or change the conflicting name. 40043, Name error Description Global variable name arg ambiguous. Recommended actions Global data must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the data or change the conflicting name. 40044, Name error Description Label name arg ambiguous. Recommended actions Labels must have names that are unique within the routine. Rename the label or change the conflicting name. 40045, Name error Description Module name arg ambiguous. Recommended actions Modules must have names that are unique among all the global types, global data, global routines and modules in the entire program. Rename the module or change the conflicting name. 40046, Name error Description Parameter name arg ambiguous. Recommended actions Parameters must have names that are unique within the routine. Rename the parameter or change the conflicting name. 40047, Name error Description Persistent name arg ambiguous Recommended actions Program data must have names that are unique within the module. Rename the data or change the conflicting name. 40048, Name error Description Routine name arg ambiguous. Recommended actions Routines must have names that are unique within the module. Rename the routine or change the conflicting name. 40049, Name error Description Variable name arg ambiguous. Recommended actions Routine data must have names that are unique within the routine. Program data must have names that are unique within the module. Rename the data or change the conflicting name. 40050, Type error Description Operand types arg and arg for binary '+' or '-' operator not equal Recommended actions The two operands of the '+' and '-' operators must have equal type. Check the operand types. 40051, Type error Description Operand types arg and arg for '=' or '<>' operator not equal
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	194	6 Trouble shooting by Event log 191 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 40029, Type error Description Illegal type arg for left operand of '<', '<=', '>' or '>=' operator. Recommended actions Allowed operand type for the "<", "<=", ">" or ">=" operators is "num". 1) Check the operand types. 40030, Type error Description Illegal type arg for right operand of '<', '<=', '>' or '>=' operator. Recommended actions Allowed operand type for the "<", "<=", ">" or ">=" operators is "num". 1) Check the operand types. 40031, Type error Description Illegal type arg for left operand of '' operator. Recommended actions Allowed operand types for the "" operator are "num", "pos" or "orient". 1) Check the operand types. 40032, Type error Description Illegal type arg for right operand of '' operator. Recommended actions Allowed operand types for the "" operator are "num", "pos" or "orient". 1) Check the operand types. 40033, Type error Description Illegal type arg for operand of 'NOT' operator. Recommended actions Allowed operand type for the "NOT" operator is "bool". 1) Check the operand types. 40034, Type error Description Illegal type arg for left operand of 'OR', 'XOR' or 'AND' operator. Recommended actions Allowed operand type for the "OR", "XOR" or "AND" operators is "bool". 1) Check the operand types. 40035, Type error Description Illegal type arg for right operand of 'OR', 'XOR' or 'AND' operator. Recommended actions Allowed operand type for the "OR", "XOR" or "AND" operators is "bool". 1) Check the operand types. 40036, Type error Description Incorrect number of indices in index list for array arg with arg dimension(s). Recommended actions 1) Make sure that the number of indices in the index list corresponds to the number of dimensions of the indexed data array. 40037, Data declaration error Description LOCAL illegal in routine constant declaration. Recommended actions Only program data declarations may have the LOCAL attribute. Remove the LOCAL attribute or move the declaration outside of the routine. 40038, Data declaration error Description LOCAL illegal in routine variable declaration Recommended actions Only program data declarations may have the LOCAL attribute. Remove the LOCAL attribute or move the declaration outside of the routine. 40039, Name error Description Constant name arg ambiguous. Recommended actions Routine data must have names that are unique within the routine. Program data must have names that are unique within the module. Rename the data or change the conflicting name. 6 Trouble shooting by Event log 192 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 40040, Name error Description Global constant name arg ambiguous. Recommended actions Global data must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the data or change the conflicting name. 40041, Name error Description Global persistent name arg ambiguous. Recommended actions Global data must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the data or change the conflicting name. 40042, Name error Description Global routine name arg ambiguous. Recommended actions Global routines must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the routine or change the conflicting name. 40043, Name error Description Global variable name arg ambiguous. Recommended actions Global data must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the data or change the conflicting name. 40044, Name error Description Label name arg ambiguous. Recommended actions Labels must have names that are unique within the routine. Rename the label or change the conflicting name. 40045, Name error Description Module name arg ambiguous. Recommended actions Modules must have names that are unique among all the global types, global data, global routines and modules in the entire program. Rename the module or change the conflicting name. 40046, Name error Description Parameter name arg ambiguous. Recommended actions Parameters must have names that are unique within the routine. Rename the parameter or change the conflicting name. 40047, Name error Description Persistent name arg ambiguous Recommended actions Program data must have names that are unique within the module. Rename the data or change the conflicting name. 40048, Name error Description Routine name arg ambiguous. Recommended actions Routines must have names that are unique within the module. Rename the routine or change the conflicting name. 40049, Name error Description Variable name arg ambiguous. Recommended actions Routine data must have names that are unique within the routine. Program data must have names that are unique within the module. Rename the data or change the conflicting name. 40050, Type error Description Operand types arg and arg for binary '+' or '-' operator not equal Recommended actions The two operands of the '+' and '-' operators must have equal type. Check the operand types. 40051, Type error Description Operand types arg and arg for '=' or '<>' operator not equal 6 Trouble shooting by Event log 193 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions The two operands of the '=' and '<>' operators must have equal type. Check the operand types. 40052, Instruction error Description RETURN with expression only allowed in function Recommended actions In a procedure or trap the return instruction must not specify a return value expression. Remove the expression. 40054, Type error Description Different dimension of array type ( arg ) and aggregate ( arg ) Recommended actions Make sure that the number of expressions in the aggregate is the same as the dimension of the data array. 40055, Type error Description Assignment target type arg is not value or semi-value type. Recommended actions The type, of the data to be assigned a value, must be a value or semi- value type. Data of non-value types may only be set by special type specific predefined instructions or functions. 40056, Type error Description Type arg for left operand of '=' or '<>' operator not value or semi-value type Recommended actions The '=' and '<>' operators may only be applied to expressions of value or semi-value type. If comparisons are to be made, special type specific predefined functions are needed. 40057, Type error Description Type arg for right operand of '=' or '<>' operator not value or semi- value type Recommended actions The '=' and '<>' operators may only be applied to expressions of value or semi-value type. If comparisons are to be made, special type specific predefined functions are needed. 40058, Type error Description TEST expression type arg not value or semi-value type Recommended actions The TEST instruction may only be applied to an expression of value or semi-value type. If comparisons are to be made, special type specific predefined functions are needed. 40059, Data declaration error Description Place holder for value expression not allowed in definition of named constant Recommended actions Complete the data declaration or change the data name to a place holder. 40060, Data declaration error Description Place holder for array dimension not allowed in definition of named constant or variable Recommended actions Complete the data declaration or change the data name to a place holder. 40061, Routine declaration error Description Place holder for parameter array dimensions not allowed in definition of named routine Recommended actions Complete the parameter declaration or change the routine name to a place holder. 40062, Name error Description Place holder for parameter name not allowed in definition of named routine Recommended actions Complete the routine declaration or change the routine name to a place holder. 40063, Data declaration error Description Place holder for initial value expression not allowed in definition of named persistent
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	195	6 Trouble shooting by Event log 192 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 40040, Name error Description Global constant name arg ambiguous. Recommended actions Global data must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the data or change the conflicting name. 40041, Name error Description Global persistent name arg ambiguous. Recommended actions Global data must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the data or change the conflicting name. 40042, Name error Description Global routine name arg ambiguous. Recommended actions Global routines must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the routine or change the conflicting name. 40043, Name error Description Global variable name arg ambiguous. Recommended actions Global data must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the data or change the conflicting name. 40044, Name error Description Label name arg ambiguous. Recommended actions Labels must have names that are unique within the routine. Rename the label or change the conflicting name. 40045, Name error Description Module name arg ambiguous. Recommended actions Modules must have names that are unique among all the global types, global data, global routines and modules in the entire program. Rename the module or change the conflicting name. 40046, Name error Description Parameter name arg ambiguous. Recommended actions Parameters must have names that are unique within the routine. Rename the parameter or change the conflicting name. 40047, Name error Description Persistent name arg ambiguous Recommended actions Program data must have names that are unique within the module. Rename the data or change the conflicting name. 40048, Name error Description Routine name arg ambiguous. Recommended actions Routines must have names that are unique within the module. Rename the routine or change the conflicting name. 40049, Name error Description Variable name arg ambiguous. Recommended actions Routine data must have names that are unique within the routine. Program data must have names that are unique within the module. Rename the data or change the conflicting name. 40050, Type error Description Operand types arg and arg for binary '+' or '-' operator not equal Recommended actions The two operands of the '+' and '-' operators must have equal type. Check the operand types. 40051, Type error Description Operand types arg and arg for '=' or '<>' operator not equal 6 Trouble shooting by Event log 193 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions The two operands of the '=' and '<>' operators must have equal type. Check the operand types. 40052, Instruction error Description RETURN with expression only allowed in function Recommended actions In a procedure or trap the return instruction must not specify a return value expression. Remove the expression. 40054, Type error Description Different dimension of array type ( arg ) and aggregate ( arg ) Recommended actions Make sure that the number of expressions in the aggregate is the same as the dimension of the data array. 40055, Type error Description Assignment target type arg is not value or semi-value type. Recommended actions The type, of the data to be assigned a value, must be a value or semi- value type. Data of non-value types may only be set by special type specific predefined instructions or functions. 40056, Type error Description Type arg for left operand of '=' or '<>' operator not value or semi-value type Recommended actions The '=' and '<>' operators may only be applied to expressions of value or semi-value type. If comparisons are to be made, special type specific predefined functions are needed. 40057, Type error Description Type arg for right operand of '=' or '<>' operator not value or semi- value type Recommended actions The '=' and '<>' operators may only be applied to expressions of value or semi-value type. If comparisons are to be made, special type specific predefined functions are needed. 40058, Type error Description TEST expression type arg not value or semi-value type Recommended actions The TEST instruction may only be applied to an expression of value or semi-value type. If comparisons are to be made, special type specific predefined functions are needed. 40059, Data declaration error Description Place holder for value expression not allowed in definition of named constant Recommended actions Complete the data declaration or change the data name to a place holder. 40060, Data declaration error Description Place holder for array dimension not allowed in definition of named constant or variable Recommended actions Complete the data declaration or change the data name to a place holder. 40061, Routine declaration error Description Place holder for parameter array dimensions not allowed in definition of named routine Recommended actions Complete the parameter declaration or change the routine name to a place holder. 40062, Name error Description Place holder for parameter name not allowed in definition of named routine Recommended actions Complete the routine declaration or change the routine name to a place holder. 40063, Data declaration error Description Place holder for initial value expression not allowed in definition of named persistent 6 Trouble shooting by Event log 194 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Complete the data declaration or change the data name to a place holder. 40064, Routine declaration error Description Place holder for parameter not allowed in definition of named routine Recommended actions Complete the parameter declaration, remove the place holder or change the routine name to a place holder. 40065, Reference error Description Place holder for type not allowed in definition of named data, record component or routine Recommended actions Complete the data or routine declaration or change the data or routine name to a place holder. 40066, Data declaration error Description Place holder for initial value expression not allowed in definition of named variable Recommended actions Complete the data declaration or change the data name to a place holder. 40067, Type error Description Too few components in record aggregate of type arg Recommended actions Make sure that the number of expressions in the aggregate is the same as the number of components in the record type. 40068, Type error Description Too many components in record aggregate of type arg Recommended actions Make sure that the number of expressions in the aggregate is the same as the number of components in the record type. 40069, Reference error Description Data reference arg is ambiguous Recommended actions At least one other object sharing the same name as the referred data is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40070, Reference error Description function reference arg is ambiguous Recommended actions At least one other object sharing the same name as the referred function is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40071, Reference error Description Label reference arg is ambiguous Recommended actions At least one other object sharing the same name as the referred label is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40072, Reference error Description Procedure reference arg is ambiguous Recommended actions At least one other object sharing the same name as the referred procedure is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40073, Reference error Description Trap reference arg is ambiguous. Recommended actions At least one other object sharing the same name as the referred trap is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40074, Reference error Description arg not entire data reference Recommended actions The specified name identifies an object other than data. Check if the desired
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	196	6 Trouble shooting by Event log 193 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions The two operands of the '=' and '<>' operators must have equal type. Check the operand types. 40052, Instruction error Description RETURN with expression only allowed in function Recommended actions In a procedure or trap the return instruction must not specify a return value expression. Remove the expression. 40054, Type error Description Different dimension of array type ( arg ) and aggregate ( arg ) Recommended actions Make sure that the number of expressions in the aggregate is the same as the dimension of the data array. 40055, Type error Description Assignment target type arg is not value or semi-value type. Recommended actions The type, of the data to be assigned a value, must be a value or semi- value type. Data of non-value types may only be set by special type specific predefined instructions or functions. 40056, Type error Description Type arg for left operand of '=' or '<>' operator not value or semi-value type Recommended actions The '=' and '<>' operators may only be applied to expressions of value or semi-value type. If comparisons are to be made, special type specific predefined functions are needed. 40057, Type error Description Type arg for right operand of '=' or '<>' operator not value or semi- value type Recommended actions The '=' and '<>' operators may only be applied to expressions of value or semi-value type. If comparisons are to be made, special type specific predefined functions are needed. 40058, Type error Description TEST expression type arg not value or semi-value type Recommended actions The TEST instruction may only be applied to an expression of value or semi-value type. If comparisons are to be made, special type specific predefined functions are needed. 40059, Data declaration error Description Place holder for value expression not allowed in definition of named constant Recommended actions Complete the data declaration or change the data name to a place holder. 40060, Data declaration error Description Place holder for array dimension not allowed in definition of named constant or variable Recommended actions Complete the data declaration or change the data name to a place holder. 40061, Routine declaration error Description Place holder for parameter array dimensions not allowed in definition of named routine Recommended actions Complete the parameter declaration or change the routine name to a place holder. 40062, Name error Description Place holder for parameter name not allowed in definition of named routine Recommended actions Complete the routine declaration or change the routine name to a place holder. 40063, Data declaration error Description Place holder for initial value expression not allowed in definition of named persistent 6 Trouble shooting by Event log 194 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Complete the data declaration or change the data name to a place holder. 40064, Routine declaration error Description Place holder for parameter not allowed in definition of named routine Recommended actions Complete the parameter declaration, remove the place holder or change the routine name to a place holder. 40065, Reference error Description Place holder for type not allowed in definition of named data, record component or routine Recommended actions Complete the data or routine declaration or change the data or routine name to a place holder. 40066, Data declaration error Description Place holder for initial value expression not allowed in definition of named variable Recommended actions Complete the data declaration or change the data name to a place holder. 40067, Type error Description Too few components in record aggregate of type arg Recommended actions Make sure that the number of expressions in the aggregate is the same as the number of components in the record type. 40068, Type error Description Too many components in record aggregate of type arg Recommended actions Make sure that the number of expressions in the aggregate is the same as the number of components in the record type. 40069, Reference error Description Data reference arg is ambiguous Recommended actions At least one other object sharing the same name as the referred data is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40070, Reference error Description function reference arg is ambiguous Recommended actions At least one other object sharing the same name as the referred function is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40071, Reference error Description Label reference arg is ambiguous Recommended actions At least one other object sharing the same name as the referred label is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40072, Reference error Description Procedure reference arg is ambiguous Recommended actions At least one other object sharing the same name as the referred procedure is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40073, Reference error Description Trap reference arg is ambiguous. Recommended actions At least one other object sharing the same name as the referred trap is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40074, Reference error Description arg not entire data reference Recommended actions The specified name identifies an object other than data. Check if the desired 6 Trouble shooting by Event log 195 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. data is hidden by some other object with the same name. 40075, Reference error Description arg not function reference Recommended actions The specified name identifies an object other than a function. Check if the desired function is hidden by some other object with the same name. 40076, Reference error Description arg not label reference Recommended actions The specified name identifies an object other than a label. Check if the desired label is hidden by some other object with the same name. 40077, Reference error Description arg not optional parameter reference in conditional argument value Recommended actions The specified name identifies an object other than an optional parameter. Change the name to refer to an optional parameter. 40078, Reference error Description arg not optional parameter reference Recommended actions The specified name identifies an object other than an optional parameter. Change the name to refer to an optional parameter. 40079, Reference error Description Task arg : arg is not a procedure reference Recommended actions The specified name identifies an object other than a procedure. Check if the desired procedure is hidden by some other object with the same name. 40080, Reference error Description arg not required parameter reference Recommended actions The specified name identifies an object other than a required parameter. Change the name to refer to a required parameter. 40081, Reference error Description arg not trap reference Recommended actions The specified name identifies an object other than a trap. Check if the desired trap is hidden by some other object with the same name. 40082, Reference error Description arg not type name Recommended actions The specified name identifies an object other than a type. Check if the desired type is hidden by some other object with the same name. 40083, Type error Description arg not value type Recommended actions Only variables that lack initial value,
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	197	6 Trouble shooting by Event log 194 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions Complete the data declaration or change the data name to a place holder. 40064, Routine declaration error Description Place holder for parameter not allowed in definition of named routine Recommended actions Complete the parameter declaration, remove the place holder or change the routine name to a place holder. 40065, Reference error Description Place holder for type not allowed in definition of named data, record component or routine Recommended actions Complete the data or routine declaration or change the data or routine name to a place holder. 40066, Data declaration error Description Place holder for initial value expression not allowed in definition of named variable Recommended actions Complete the data declaration or change the data name to a place holder. 40067, Type error Description Too few components in record aggregate of type arg Recommended actions Make sure that the number of expressions in the aggregate is the same as the number of components in the record type. 40068, Type error Description Too many components in record aggregate of type arg Recommended actions Make sure that the number of expressions in the aggregate is the same as the number of components in the record type. 40069, Reference error Description Data reference arg is ambiguous Recommended actions At least one other object sharing the same name as the referred data is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40070, Reference error Description function reference arg is ambiguous Recommended actions At least one other object sharing the same name as the referred function is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40071, Reference error Description Label reference arg is ambiguous Recommended actions At least one other object sharing the same name as the referred label is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40072, Reference error Description Procedure reference arg is ambiguous Recommended actions At least one other object sharing the same name as the referred procedure is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40073, Reference error Description Trap reference arg is ambiguous. Recommended actions At least one other object sharing the same name as the referred trap is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40074, Reference error Description arg not entire data reference Recommended actions The specified name identifies an object other than data. Check if the desired 6 Trouble shooting by Event log 195 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. data is hidden by some other object with the same name. 40075, Reference error Description arg not function reference Recommended actions The specified name identifies an object other than a function. Check if the desired function is hidden by some other object with the same name. 40076, Reference error Description arg not label reference Recommended actions The specified name identifies an object other than a label. Check if the desired label is hidden by some other object with the same name. 40077, Reference error Description arg not optional parameter reference in conditional argument value Recommended actions The specified name identifies an object other than an optional parameter. Change the name to refer to an optional parameter. 40078, Reference error Description arg not optional parameter reference Recommended actions The specified name identifies an object other than an optional parameter. Change the name to refer to an optional parameter. 40079, Reference error Description Task arg : arg is not a procedure reference Recommended actions The specified name identifies an object other than a procedure. Check if the desired procedure is hidden by some other object with the same name. 40080, Reference error Description arg not required parameter reference Recommended actions The specified name identifies an object other than a required parameter. Change the name to refer to a required parameter. 40081, Reference error Description arg not trap reference Recommended actions The specified name identifies an object other than a trap. Check if the desired trap is hidden by some other object with the same name. 40082, Reference error Description arg not type name Recommended actions The specified name identifies an object other than a type. Check if the desired type is hidden by some other object with the same name. 40083, Type error Description arg not value type Recommended actions Only variables that lack initial value, 6 Trouble shooting by Event log 196 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. and 'VAR' mode parameters may be of semi-value or non-value type. 40086, Reference error Description Reference to unknown label arg Recommended actions The routine contains no label (or other object) with the specified name. 40087, Reference error Description Reference to unknown optional parameter arg Recommended actions The called routine contains no optional parameter (or other object) with the specified name. 40089, Reference error Description Reference to unknown record component arg Recommended actions The record type contains no record component with the specified name. 40090, Reference error Description Reference to unknown required parameter arg Recommended actions The called routine contains no required parameter (or other object) with the specified name. 40092, Reference error Description Unknown type name arg Recommended actions No data type (or other object) with the specified name is visible from this program position. 40093, Instruction error Description Assignment target is read only Recommended actions The data to be assigned a value may not be a constant, read only variable or read only persistent. 40094, Data declaration error Description Persistent declaration not allowed in routine Recommended actions Persistents may only be declared at module level. Move the persistent declaration from the routine. 40095, Instruction error Description RAISE without expression only allowed in error handler Recommended actions Add an error number expression to the RAISE instruction. 40096, Instruction error Description RETRY only allowed in error handler Recommended actions The RETRY instruction may only be used in error handlers. Remove it. 40097, Instruction error Description TRYNEXT only allowed in error handler Recommended actions The TRYNEXT instruction may only be used
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	198	6 Trouble shooting by Event log 195 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. data is hidden by some other object with the same name. 40075, Reference error Description arg not function reference Recommended actions The specified name identifies an object other than a function. Check if the desired function is hidden by some other object with the same name. 40076, Reference error Description arg not label reference Recommended actions The specified name identifies an object other than a label. Check if the desired label is hidden by some other object with the same name. 40077, Reference error Description arg not optional parameter reference in conditional argument value Recommended actions The specified name identifies an object other than an optional parameter. Change the name to refer to an optional parameter. 40078, Reference error Description arg not optional parameter reference Recommended actions The specified name identifies an object other than an optional parameter. Change the name to refer to an optional parameter. 40079, Reference error Description Task arg : arg is not a procedure reference Recommended actions The specified name identifies an object other than a procedure. Check if the desired procedure is hidden by some other object with the same name. 40080, Reference error Description arg not required parameter reference Recommended actions The specified name identifies an object other than a required parameter. Change the name to refer to a required parameter. 40081, Reference error Description arg not trap reference Recommended actions The specified name identifies an object other than a trap. Check if the desired trap is hidden by some other object with the same name. 40082, Reference error Description arg not type name Recommended actions The specified name identifies an object other than a type. Check if the desired type is hidden by some other object with the same name. 40083, Type error Description arg not value type Recommended actions Only variables that lack initial value, 6 Trouble shooting by Event log 196 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. and 'VAR' mode parameters may be of semi-value or non-value type. 40086, Reference error Description Reference to unknown label arg Recommended actions The routine contains no label (or other object) with the specified name. 40087, Reference error Description Reference to unknown optional parameter arg Recommended actions The called routine contains no optional parameter (or other object) with the specified name. 40089, Reference error Description Reference to unknown record component arg Recommended actions The record type contains no record component with the specified name. 40090, Reference error Description Reference to unknown required parameter arg Recommended actions The called routine contains no required parameter (or other object) with the specified name. 40092, Reference error Description Unknown type name arg Recommended actions No data type (or other object) with the specified name is visible from this program position. 40093, Instruction error Description Assignment target is read only Recommended actions The data to be assigned a value may not be a constant, read only variable or read only persistent. 40094, Data declaration error Description Persistent declaration not allowed in routine Recommended actions Persistents may only be declared at module level. Move the persistent declaration from the routine. 40095, Instruction error Description RAISE without expression only allowed in error handler Recommended actions Add an error number expression to the RAISE instruction. 40096, Instruction error Description RETRY only allowed in error handler Recommended actions The RETRY instruction may only be used in error handlers. Remove it. 40097, Instruction error Description TRYNEXT only allowed in error handler Recommended actions The TRYNEXT instruction may only be used 6 Trouble shooting by Event log 197 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. in error handlers. Remove it. 40098, Parameter error Description 'switch' parameter must have transfer mode IN Recommended actions Remove the parameter transfer mode specifier. If IN transfer mode is not sufficient, change the data type of the parameter. 40099, Parameter error Description 'switch' parameter cannot be dimensioned Recommended actions Remove the array dimension specification, or change the data type of the parameter. 40100, Parameter error Description 'switch' only allowed for optional parameter Recommended actions Change the parameter into an optional parameter, or change the data type of the parameter. If the object is not a parameter, change the data type. 40101, Type error Description Type mismatch of expected type arg and found type arg Recommended actions The expression is not of the expected data type. 40102, Type error Description Type mismatch of aggregate, expected type arg Recommended actions The aggregate does not match the expected data type. 40103, Type error Description Persistent arg , arg type mismatch Recommended actions There is already a persistent data with the same name but with another data type. Rename the persistent, or change its data type. 40104, Data declaration error Description Cannot determine array dimensions (circular constant references ?) Recommended actions Check that any referred constants are correctly defined. If so, the program is too complex. Try to rewrite the declarations. 40105, Data declaration error Description Cannot determine type of constant value (circular constant references ?) Recommended actions Check that any referred constants are correctly defined. If so, the program is too complex. Try to rewrite the declarations. 40106, Data declaration error Description Cannot evaluate constant value expression (circular constant references ?) Recommended actions Check that any referred constants are correctly defined. If so, the program is too complex. Try to rewrite the
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	199	6 Trouble shooting by Event log 196 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. and 'VAR' mode parameters may be of semi-value or non-value type. 40086, Reference error Description Reference to unknown label arg Recommended actions The routine contains no label (or other object) with the specified name. 40087, Reference error Description Reference to unknown optional parameter arg Recommended actions The called routine contains no optional parameter (or other object) with the specified name. 40089, Reference error Description Reference to unknown record component arg Recommended actions The record type contains no record component with the specified name. 40090, Reference error Description Reference to unknown required parameter arg Recommended actions The called routine contains no required parameter (or other object) with the specified name. 40092, Reference error Description Unknown type name arg Recommended actions No data type (or other object) with the specified name is visible from this program position. 40093, Instruction error Description Assignment target is read only Recommended actions The data to be assigned a value may not be a constant, read only variable or read only persistent. 40094, Data declaration error Description Persistent declaration not allowed in routine Recommended actions Persistents may only be declared at module level. Move the persistent declaration from the routine. 40095, Instruction error Description RAISE without expression only allowed in error handler Recommended actions Add an error number expression to the RAISE instruction. 40096, Instruction error Description RETRY only allowed in error handler Recommended actions The RETRY instruction may only be used in error handlers. Remove it. 40097, Instruction error Description TRYNEXT only allowed in error handler Recommended actions The TRYNEXT instruction may only be used 6 Trouble shooting by Event log 197 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. in error handlers. Remove it. 40098, Parameter error Description 'switch' parameter must have transfer mode IN Recommended actions Remove the parameter transfer mode specifier. If IN transfer mode is not sufficient, change the data type of the parameter. 40099, Parameter error Description 'switch' parameter cannot be dimensioned Recommended actions Remove the array dimension specification, or change the data type of the parameter. 40100, Parameter error Description 'switch' only allowed for optional parameter Recommended actions Change the parameter into an optional parameter, or change the data type of the parameter. If the object is not a parameter, change the data type. 40101, Type error Description Type mismatch of expected type arg and found type arg Recommended actions The expression is not of the expected data type. 40102, Type error Description Type mismatch of aggregate, expected type arg Recommended actions The aggregate does not match the expected data type. 40103, Type error Description Persistent arg , arg type mismatch Recommended actions There is already a persistent data with the same name but with another data type. Rename the persistent, or change its data type. 40104, Data declaration error Description Cannot determine array dimensions (circular constant references ?) Recommended actions Check that any referred constants are correctly defined. If so, the program is too complex. Try to rewrite the declarations. 40105, Data declaration error Description Cannot determine type of constant value (circular constant references ?) Recommended actions Check that any referred constants are correctly defined. If so, the program is too complex. Try to rewrite the declarations. 40106, Data declaration error Description Cannot evaluate constant value expression (circular constant references ?) Recommended actions Check that any referred constants are correctly defined. If so, the program is too complex. Try to rewrite the 6 Trouble shooting by Event log 198 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. declarations. 40107, Data declaration error Description Cannot determine type of variable value (circular constant references?) Recommended actions Check that any referred constants are correctly defined. If so, the program is too complex. Try to rewrite the declarations. 40108, Type error Description Unknown aggregate type Recommended actions An aggregate may not be used in this position since there is no expected data type. Declare data with the desired data type and aggregate value. Use the name of the data instead of the aggregate. 40109, Type definition error Description Cannot determine type of record component arg (circular type definitions?) Recommended actions Check that the type of the component is correctly defined. If so, it could be a circular definition, the type of a component could not refer to the its own record type. 40110, Reference error Description Record name arg is ambiguous Recommended actions At least one other object sharing the same name as the referred record name is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40111, Name error Description Global record name arg ambiguous Recommended actions Global type must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the record or change the conflicting name. 40112, Reference error Description Alias name arg is ambiguous Recommended actions At least one other object sharing the same name as the referred alias name is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40113, Name error Description Global alias name arg ambiguous Recommended actions Global type must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the alias or change the conflicting name. 40114, Type definition error Description Type reference of alias name arg is an alias type Recommended actions Check that the type of the component is correctly defined. If so, it could be a circular definition. The type of a component could not refer to its own record type.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	200	6 Trouble shooting by Event log 197 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. in error handlers. Remove it. 40098, Parameter error Description 'switch' parameter must have transfer mode IN Recommended actions Remove the parameter transfer mode specifier. If IN transfer mode is not sufficient, change the data type of the parameter. 40099, Parameter error Description 'switch' parameter cannot be dimensioned Recommended actions Remove the array dimension specification, or change the data type of the parameter. 40100, Parameter error Description 'switch' only allowed for optional parameter Recommended actions Change the parameter into an optional parameter, or change the data type of the parameter. If the object is not a parameter, change the data type. 40101, Type error Description Type mismatch of expected type arg and found type arg Recommended actions The expression is not of the expected data type. 40102, Type error Description Type mismatch of aggregate, expected type arg Recommended actions The aggregate does not match the expected data type. 40103, Type error Description Persistent arg , arg type mismatch Recommended actions There is already a persistent data with the same name but with another data type. Rename the persistent, or change its data type. 40104, Data declaration error Description Cannot determine array dimensions (circular constant references ?) Recommended actions Check that any referred constants are correctly defined. If so, the program is too complex. Try to rewrite the declarations. 40105, Data declaration error Description Cannot determine type of constant value (circular constant references ?) Recommended actions Check that any referred constants are correctly defined. If so, the program is too complex. Try to rewrite the declarations. 40106, Data declaration error Description Cannot evaluate constant value expression (circular constant references ?) Recommended actions Check that any referred constants are correctly defined. If so, the program is too complex. Try to rewrite the 6 Trouble shooting by Event log 198 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. declarations. 40107, Data declaration error Description Cannot determine type of variable value (circular constant references?) Recommended actions Check that any referred constants are correctly defined. If so, the program is too complex. Try to rewrite the declarations. 40108, Type error Description Unknown aggregate type Recommended actions An aggregate may not be used in this position since there is no expected data type. Declare data with the desired data type and aggregate value. Use the name of the data instead of the aggregate. 40109, Type definition error Description Cannot determine type of record component arg (circular type definitions?) Recommended actions Check that the type of the component is correctly defined. If so, it could be a circular definition, the type of a component could not refer to the its own record type. 40110, Reference error Description Record name arg is ambiguous Recommended actions At least one other object sharing the same name as the referred record name is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40111, Name error Description Global record name arg ambiguous Recommended actions Global type must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the record or change the conflicting name. 40112, Reference error Description Alias name arg is ambiguous Recommended actions At least one other object sharing the same name as the referred alias name is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40113, Name error Description Global alias name arg ambiguous Recommended actions Global type must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the alias or change the conflicting name. 40114, Type definition error Description Type reference of alias name arg is an alias type Recommended actions Check that the type of the component is correctly defined. If so, it could be a circular definition. The type of a component could not refer to its own record type. 6 Trouble shooting by Event log 199 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 40115, Type definition error Description Cannot determine type of alias arg (circular type definitions?) Recommended actions Check that the type of the alias is correctly defined. If so, it could be a circular definition, the type of an alias could not refer to a record that use this alias as a component. 40116, Reference error Description Record component name arg is ambiguous Recommended actions At least one other object sharing the same name as the referred component is visible from this program position. Make sure that all object names fulfill the aming rules regarding uniqueness. 40117, Type definition error Description Place holder for record component not allowed in definition of named record Recommended actions Complete the definition or change the data name to a place holder. 40119, Reference error Description Cannot use the semi-value type arg for record components Recommended actions 40120, Reference error Description Illegal reference to installed task object arg from shared object Recommended actions Install the referred object shared, or install the referring ReaL object/ archive or RAPID module in each task (not shared). 40121, Reference error Description Cannot use semi-value type for arrays Recommended actions 40122, Reference error Description arg not procedure reference Recommended actions The specified name identifies an object other than a procedure. Check if the desired procedure is hidden by some other object with the same name. 40123, Argument error Description Argument for 'PERS' parameter arg is not a persistent reference or is read only Recommended actions Make sure the argument is just a persistent or persistent parameter reference and that it is writable. Do not use () around the argument. 40124, Argument error Description Argument for 'VAR' parameter arg is not variable reference or is read only Recommended actions Make sure the argument is just a variable or variable parameter reference and that it is writable. Do not use () around the argument. 40125, Instruction error Description The Interrupt number is not static variable reference, or it is shared, or it is read only Recommended actions Make sure the interrupt number is just a variable or variable parameter reference. The variable must be static and not shared. The variable may not be read only.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	201	6 Trouble shooting by Event log 198 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. declarations. 40107, Data declaration error Description Cannot determine type of variable value (circular constant references?) Recommended actions Check that any referred constants are correctly defined. If so, the program is too complex. Try to rewrite the declarations. 40108, Type error Description Unknown aggregate type Recommended actions An aggregate may not be used in this position since there is no expected data type. Declare data with the desired data type and aggregate value. Use the name of the data instead of the aggregate. 40109, Type definition error Description Cannot determine type of record component arg (circular type definitions?) Recommended actions Check that the type of the component is correctly defined. If so, it could be a circular definition, the type of a component could not refer to the its own record type. 40110, Reference error Description Record name arg is ambiguous Recommended actions At least one other object sharing the same name as the referred record name is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40111, Name error Description Global record name arg ambiguous Recommended actions Global type must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the record or change the conflicting name. 40112, Reference error Description Alias name arg is ambiguous Recommended actions At least one other object sharing the same name as the referred alias name is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40113, Name error Description Global alias name arg ambiguous Recommended actions Global type must have names that are unique among all the global types, data, global routines and modules in the entire program. Rename the alias or change the conflicting name. 40114, Type definition error Description Type reference of alias name arg is an alias type Recommended actions Check that the type of the component is correctly defined. If so, it could be a circular definition. The type of a component could not refer to its own record type. 6 Trouble shooting by Event log 199 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 40115, Type definition error Description Cannot determine type of alias arg (circular type definitions?) Recommended actions Check that the type of the alias is correctly defined. If so, it could be a circular definition, the type of an alias could not refer to a record that use this alias as a component. 40116, Reference error Description Record component name arg is ambiguous Recommended actions At least one other object sharing the same name as the referred component is visible from this program position. Make sure that all object names fulfill the aming rules regarding uniqueness. 40117, Type definition error Description Place holder for record component not allowed in definition of named record Recommended actions Complete the definition or change the data name to a place holder. 40119, Reference error Description Cannot use the semi-value type arg for record components Recommended actions 40120, Reference error Description Illegal reference to installed task object arg from shared object Recommended actions Install the referred object shared, or install the referring ReaL object/ archive or RAPID module in each task (not shared). 40121, Reference error Description Cannot use semi-value type for arrays Recommended actions 40122, Reference error Description arg not procedure reference Recommended actions The specified name identifies an object other than a procedure. Check if the desired procedure is hidden by some other object with the same name. 40123, Argument error Description Argument for 'PERS' parameter arg is not a persistent reference or is read only Recommended actions Make sure the argument is just a persistent or persistent parameter reference and that it is writable. Do not use () around the argument. 40124, Argument error Description Argument for 'VAR' parameter arg is not variable reference or is read only Recommended actions Make sure the argument is just a variable or variable parameter reference and that it is writable. Do not use () around the argument. 40125, Instruction error Description The Interrupt number is not static variable reference, or it is shared, or it is read only Recommended actions Make sure the interrupt number is just a variable or variable parameter reference. The variable must be static and not shared. The variable may not be read only. 6 Trouble shooting by Event log 200 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 40126, Value error Description Integer value arg is too large Recommended actions The value of the expression must be an integer value. The current value is outside the integer range. 40127, Value error Description arg is not an integer value Recommended actions The value of the expression must be an exact integer value. The current value has a fraction part. 40128, Reference error Description Reference to unknown entire data arg Recommended actions No data (or other object) with the specified name is visible from this program position. 40129, Reference error Description Reference to unknown function arg Recommended actions No function (or other object) with the specified name is visible from this program position. 40130, Reference error Description Reference to unknown procedure arg Recommended actions No procedure (or other object) with the specified name is visible from this program position. 40131, Reference error Description Reference to unknown trap arg Recommended actions No trap (or other object) with the specified name is visible from this program position. 40135, Syntax error. Description Expected arg Recommended actions 40136, Syntax error Description Unexpected arg Recommended actions 40137, Syntax error Description Expected arg but found arg Recommended actions 40138, Syntax error Description Syntax error, stack backed up Recommended actions 40139, Syntax error Description Syntax error, parsing terminated Recommended actions 40140, Numerical value for symbol arg is out of range. Description Numerical value for symbol arg is out of range. Recommended actions Make the value smaller 40141, String too long Description The string arg is too long. Recommended actions Make the string shorter. 40142, TxId is out of range Description The Text identifier arg is out of range.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	202	6 Trouble shooting by Event log 199 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 40115, Type definition error Description Cannot determine type of alias arg (circular type definitions?) Recommended actions Check that the type of the alias is correctly defined. If so, it could be a circular definition, the type of an alias could not refer to a record that use this alias as a component. 40116, Reference error Description Record component name arg is ambiguous Recommended actions At least one other object sharing the same name as the referred component is visible from this program position. Make sure that all object names fulfill the aming rules regarding uniqueness. 40117, Type definition error Description Place holder for record component not allowed in definition of named record Recommended actions Complete the definition or change the data name to a place holder. 40119, Reference error Description Cannot use the semi-value type arg for record components Recommended actions 40120, Reference error Description Illegal reference to installed task object arg from shared object Recommended actions Install the referred object shared, or install the referring ReaL object/ archive or RAPID module in each task (not shared). 40121, Reference error Description Cannot use semi-value type for arrays Recommended actions 40122, Reference error Description arg not procedure reference Recommended actions The specified name identifies an object other than a procedure. Check if the desired procedure is hidden by some other object with the same name. 40123, Argument error Description Argument for 'PERS' parameter arg is not a persistent reference or is read only Recommended actions Make sure the argument is just a persistent or persistent parameter reference and that it is writable. Do not use () around the argument. 40124, Argument error Description Argument for 'VAR' parameter arg is not variable reference or is read only Recommended actions Make sure the argument is just a variable or variable parameter reference and that it is writable. Do not use () around the argument. 40125, Instruction error Description The Interrupt number is not static variable reference, or it is shared, or it is read only Recommended actions Make sure the interrupt number is just a variable or variable parameter reference. The variable must be static and not shared. The variable may not be read only. 6 Trouble shooting by Event log 200 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 40126, Value error Description Integer value arg is too large Recommended actions The value of the expression must be an integer value. The current value is outside the integer range. 40127, Value error Description arg is not an integer value Recommended actions The value of the expression must be an exact integer value. The current value has a fraction part. 40128, Reference error Description Reference to unknown entire data arg Recommended actions No data (or other object) with the specified name is visible from this program position. 40129, Reference error Description Reference to unknown function arg Recommended actions No function (or other object) with the specified name is visible from this program position. 40130, Reference error Description Reference to unknown procedure arg Recommended actions No procedure (or other object) with the specified name is visible from this program position. 40131, Reference error Description Reference to unknown trap arg Recommended actions No trap (or other object) with the specified name is visible from this program position. 40135, Syntax error. Description Expected arg Recommended actions 40136, Syntax error Description Unexpected arg Recommended actions 40137, Syntax error Description Expected arg but found arg Recommended actions 40138, Syntax error Description Syntax error, stack backed up Recommended actions 40139, Syntax error Description Syntax error, parsing terminated Recommended actions 40140, Numerical value for symbol arg is out of range. Description Numerical value for symbol arg is out of range. Recommended actions Make the value smaller 40141, String too long Description The string arg is too long. Recommended actions Make the string shorter. 40142, TxId is out of range Description The Text identifier arg is out of range. 6 Trouble shooting by Event log 201 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 40143, Aggregate is out of range Description The aggregate arg is out of range. Recommended actions Make the aggregate smaller 40144, Integer out of range Description The integer arg is out of range. Recommended actions Make the integer smaller. 40145, Parser stack is full Description The parser stack is full. Recommended actions Reduce program complexity 40146, Not enough heap space. Description There is not enough heap space to fulfill the action. Recommended actions Rewrite your program 40147, Identifier is reserved word in current language Description The identifier arg is a reserved word in current language. Recommended actions Change the name of the identifier 40148, Identifier too long Description The name of the identifier arg is too long. Recommended actions Rename the identifier with a shorter name. 40149, Placeholder too long Description The placeholder arg is too long. Recommended actions Rename the placeholder with a shorter name. 40150, Unexpected unknown token Description Unexpected unknown token. Recommended actions Remove the unknown token. 40151, Initial value of PERS not updated. Description The initial value of PERS: arg will not be updated. A PERS with the same name in another task has already an initial value of the PERS. Recommended actions Check the value in the Program Data window to see that the PERS have the correct value. if necessary, unload modules with that PERS from all tasks and reload with new initial value. The PERS is of type: arg . 40152, Data declaration error Description TASK illegal in routine variable declaration Recommended actions Only program data declarations may have the TASK attribute. Remove the TASK attribute or move the declaration outside of the routine. 40155, Argument error Description Task arg : Argument for 'PERS' parameter arg is not persistent reference or is read only Recommended actions Make sure the argument is just a persistent or persistent parameter reference and that it is writable. Do not use () around the argument. 40156, Argument error Description Task arg : Argument for 'VAR' parameter arg is not variable reference or is read only Recommended actions Make sure the argument is just a variable or variable parameter reference and that it is writable.
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	203	6 Trouble shooting by Event log 200 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. 40126, Value error Description Integer value arg is too large Recommended actions The value of the expression must be an integer value. The current value is outside the integer range. 40127, Value error Description arg is not an integer value Recommended actions The value of the expression must be an exact integer value. The current value has a fraction part. 40128, Reference error Description Reference to unknown entire data arg Recommended actions No data (or other object) with the specified name is visible from this program position. 40129, Reference error Description Reference to unknown function arg Recommended actions No function (or other object) with the specified name is visible from this program position. 40130, Reference error Description Reference to unknown procedure arg Recommended actions No procedure (or other object) with the specified name is visible from this program position. 40131, Reference error Description Reference to unknown trap arg Recommended actions No trap (or other object) with the specified name is visible from this program position. 40135, Syntax error. Description Expected arg Recommended actions 40136, Syntax error Description Unexpected arg Recommended actions 40137, Syntax error Description Expected arg but found arg Recommended actions 40138, Syntax error Description Syntax error, stack backed up Recommended actions 40139, Syntax error Description Syntax error, parsing terminated Recommended actions 40140, Numerical value for symbol arg is out of range. Description Numerical value for symbol arg is out of range. Recommended actions Make the value smaller 40141, String too long Description The string arg is too long. Recommended actions Make the string shorter. 40142, TxId is out of range Description The Text identifier arg is out of range. 6 Trouble shooting by Event log 201 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 40143, Aggregate is out of range Description The aggregate arg is out of range. Recommended actions Make the aggregate smaller 40144, Integer out of range Description The integer arg is out of range. Recommended actions Make the integer smaller. 40145, Parser stack is full Description The parser stack is full. Recommended actions Reduce program complexity 40146, Not enough heap space. Description There is not enough heap space to fulfill the action. Recommended actions Rewrite your program 40147, Identifier is reserved word in current language Description The identifier arg is a reserved word in current language. Recommended actions Change the name of the identifier 40148, Identifier too long Description The name of the identifier arg is too long. Recommended actions Rename the identifier with a shorter name. 40149, Placeholder too long Description The placeholder arg is too long. Recommended actions Rename the placeholder with a shorter name. 40150, Unexpected unknown token Description Unexpected unknown token. Recommended actions Remove the unknown token. 40151, Initial value of PERS not updated. Description The initial value of PERS: arg will not be updated. A PERS with the same name in another task has already an initial value of the PERS. Recommended actions Check the value in the Program Data window to see that the PERS have the correct value. if necessary, unload modules with that PERS from all tasks and reload with new initial value. The PERS is of type: arg . 40152, Data declaration error Description TASK illegal in routine variable declaration Recommended actions Only program data declarations may have the TASK attribute. Remove the TASK attribute or move the declaration outside of the routine. 40155, Argument error Description Task arg : Argument for 'PERS' parameter arg is not persistent reference or is read only Recommended actions Make sure the argument is just a persistent or persistent parameter reference and that it is writable. Do not use () around the argument. 40156, Argument error Description Task arg : Argument for 'VAR' parameter arg is not variable reference or is read only Recommended actions Make sure the argument is just a variable or variable parameter reference and that it is writable. 6 Trouble shooting by Event log 202 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Do not use () around the argument. 40157, Instruction error Description Task arg : Interrupt number is not a static variable reference, is shared, or is read only. Recommended actions Make sure the interrupt number is just a variable or variable parameter reference. The variable must be static and not shared. The variable may not be read only. 40158, Value error Description Task arg : Integer value arg too large Recommended actions The value of the expression must be an integer value. The current value is outside the integer range. 40159, Value error Description Task arg : arg not integer value Recommended actions The value of the expression must be an exact integer value. The current value has a fraction part. 40160, Errors in RAPID program. Description Task arg : There are errors in the RAPID program. Recommended actions Check for RAPID errors using Check program in the Program editor and correct the program. 40161, Option is missing. Description The instruction arg requires the option arg . Consequences The program will not execute properly. Probable causes The system image doesn't include the required option. Recommended actions Update the system image with the required option. 40162, Errors in RAPID program. Description Task arg : There are errors in the RAPID program. Recommended actions Take the following actions to be able to debug the program: 1 Change the type of the task to NORMAL. 2 Restart the controller. 3 Check for RAPID errors and correct the program. 40165, Reference error Description Task arg : Reference to unknown entire data arg Recommended actions No data (or other object) with the specified name is visible from this program position. 40166, Reference error Description Task arg : Reference to unknown function arg Recommended actions No function (or other object) with the specified name is visible from this program position. 40168, Reference error Description Task arg : Reference to unknown procedure arg Recommended actions No procedure (or other object) with the specified name is visible from this program position. To avoid run time errors like this, add code in error handler to handle this. ERRNO will be set to "ERR_REFUNKPRC". 40170, Reference error Description Task arg : Reference to unknown trap arg
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	204	6 Trouble shooting by Event log 201 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions 40143, Aggregate is out of range Description The aggregate arg is out of range. Recommended actions Make the aggregate smaller 40144, Integer out of range Description The integer arg is out of range. Recommended actions Make the integer smaller. 40145, Parser stack is full Description The parser stack is full. Recommended actions Reduce program complexity 40146, Not enough heap space. Description There is not enough heap space to fulfill the action. Recommended actions Rewrite your program 40147, Identifier is reserved word in current language Description The identifier arg is a reserved word in current language. Recommended actions Change the name of the identifier 40148, Identifier too long Description The name of the identifier arg is too long. Recommended actions Rename the identifier with a shorter name. 40149, Placeholder too long Description The placeholder arg is too long. Recommended actions Rename the placeholder with a shorter name. 40150, Unexpected unknown token Description Unexpected unknown token. Recommended actions Remove the unknown token. 40151, Initial value of PERS not updated. Description The initial value of PERS: arg will not be updated. A PERS with the same name in another task has already an initial value of the PERS. Recommended actions Check the value in the Program Data window to see that the PERS have the correct value. if necessary, unload modules with that PERS from all tasks and reload with new initial value. The PERS is of type: arg . 40152, Data declaration error Description TASK illegal in routine variable declaration Recommended actions Only program data declarations may have the TASK attribute. Remove the TASK attribute or move the declaration outside of the routine. 40155, Argument error Description Task arg : Argument for 'PERS' parameter arg is not persistent reference or is read only Recommended actions Make sure the argument is just a persistent or persistent parameter reference and that it is writable. Do not use () around the argument. 40156, Argument error Description Task arg : Argument for 'VAR' parameter arg is not variable reference or is read only Recommended actions Make sure the argument is just a variable or variable parameter reference and that it is writable. 6 Trouble shooting by Event log 202 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Do not use () around the argument. 40157, Instruction error Description Task arg : Interrupt number is not a static variable reference, is shared, or is read only. Recommended actions Make sure the interrupt number is just a variable or variable parameter reference. The variable must be static and not shared. The variable may not be read only. 40158, Value error Description Task arg : Integer value arg too large Recommended actions The value of the expression must be an integer value. The current value is outside the integer range. 40159, Value error Description Task arg : arg not integer value Recommended actions The value of the expression must be an exact integer value. The current value has a fraction part. 40160, Errors in RAPID program. Description Task arg : There are errors in the RAPID program. Recommended actions Check for RAPID errors using Check program in the Program editor and correct the program. 40161, Option is missing. Description The instruction arg requires the option arg . Consequences The program will not execute properly. Probable causes The system image doesn't include the required option. Recommended actions Update the system image with the required option. 40162, Errors in RAPID program. Description Task arg : There are errors in the RAPID program. Recommended actions Take the following actions to be able to debug the program: 1 Change the type of the task to NORMAL. 2 Restart the controller. 3 Check for RAPID errors and correct the program. 40165, Reference error Description Task arg : Reference to unknown entire data arg Recommended actions No data (or other object) with the specified name is visible from this program position. 40166, Reference error Description Task arg : Reference to unknown function arg Recommended actions No function (or other object) with the specified name is visible from this program position. 40168, Reference error Description Task arg : Reference to unknown procedure arg Recommended actions No procedure (or other object) with the specified name is visible from this program position. To avoid run time errors like this, add code in error handler to handle this. ERRNO will be set to "ERR_REFUNKPRC". 40170, Reference error Description Task arg : Reference to unknown trap arg 6 Trouble shooting by Event log 203 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions No trap (or other object) with the specified name is visible from this program position. 40171, Reference error Description Task arg : Reference to unknown data (or other object) found during execution of module arg . Recommended actions Check the program for unresolved references. 40172, Reference error Description Task arg : Reference to unknown module arg . Recommended actions No module (or other object) with the specified name is visible from this program position. Check the program for incorrect module reference or if the module is missing. 40173, Reference error Description Task arg : Reference to object arg that is not a module. Recommended actions The specified name identifies an object other than a module. Check the program for incorrect module reference. 40174, Reference error Description Task arg : Reference to module arg is ambiguous. Recommended actions At least one other object sharing the same name as the referred module is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40175, Reference error Description Task arg : Reference to procedure arg is ambiguous. Recommended actions At least one other object sharing the same name as the referred procedure is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40191, Instruction error Description Task arg : Variable and trap routine already connected Recommended actions It is not legal to connect a specific variable with a trap routine more than once. 40192, Argument error Description Task arg : arg is second present conditional argument for excluding parameters Recommended actions Arguments may not be present for more than one parameter from a list of parameters that exclude each other. 40193, Execution error Description Task arg : Late binding procedure call error arg Recommended actions There is an error in the procedure call instruction. See previous message for the actual cause. 40194, Value error Description Task arg : Division by zero Recommended actions Cannot divide by 0. Rewrite the program so that the divide operation is not executed when the divisor is 0. 40195, Limit error Description Task arg : The configured maximum number of RETRYs ( arg retries)
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	205	6 Trouble shooting by Event log 202 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Do not use () around the argument. 40157, Instruction error Description Task arg : Interrupt number is not a static variable reference, is shared, or is read only. Recommended actions Make sure the interrupt number is just a variable or variable parameter reference. The variable must be static and not shared. The variable may not be read only. 40158, Value error Description Task arg : Integer value arg too large Recommended actions The value of the expression must be an integer value. The current value is outside the integer range. 40159, Value error Description Task arg : arg not integer value Recommended actions The value of the expression must be an exact integer value. The current value has a fraction part. 40160, Errors in RAPID program. Description Task arg : There are errors in the RAPID program. Recommended actions Check for RAPID errors using Check program in the Program editor and correct the program. 40161, Option is missing. Description The instruction arg requires the option arg . Consequences The program will not execute properly. Probable causes The system image doesn't include the required option. Recommended actions Update the system image with the required option. 40162, Errors in RAPID program. Description Task arg : There are errors in the RAPID program. Recommended actions Take the following actions to be able to debug the program: 1 Change the type of the task to NORMAL. 2 Restart the controller. 3 Check for RAPID errors and correct the program. 40165, Reference error Description Task arg : Reference to unknown entire data arg Recommended actions No data (or other object) with the specified name is visible from this program position. 40166, Reference error Description Task arg : Reference to unknown function arg Recommended actions No function (or other object) with the specified name is visible from this program position. 40168, Reference error Description Task arg : Reference to unknown procedure arg Recommended actions No procedure (or other object) with the specified name is visible from this program position. To avoid run time errors like this, add code in error handler to handle this. ERRNO will be set to "ERR_REFUNKPRC". 40170, Reference error Description Task arg : Reference to unknown trap arg 6 Trouble shooting by Event log 203 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions No trap (or other object) with the specified name is visible from this program position. 40171, Reference error Description Task arg : Reference to unknown data (or other object) found during execution of module arg . Recommended actions Check the program for unresolved references. 40172, Reference error Description Task arg : Reference to unknown module arg . Recommended actions No module (or other object) with the specified name is visible from this program position. Check the program for incorrect module reference or if the module is missing. 40173, Reference error Description Task arg : Reference to object arg that is not a module. Recommended actions The specified name identifies an object other than a module. Check the program for incorrect module reference. 40174, Reference error Description Task arg : Reference to module arg is ambiguous. Recommended actions At least one other object sharing the same name as the referred module is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40175, Reference error Description Task arg : Reference to procedure arg is ambiguous. Recommended actions At least one other object sharing the same name as the referred procedure is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40191, Instruction error Description Task arg : Variable and trap routine already connected Recommended actions It is not legal to connect a specific variable with a trap routine more than once. 40192, Argument error Description Task arg : arg is second present conditional argument for excluding parameters Recommended actions Arguments may not be present for more than one parameter from a list of parameters that exclude each other. 40193, Execution error Description Task arg : Late binding procedure call error arg Recommended actions There is an error in the procedure call instruction. See previous message for the actual cause. 40194, Value error Description Task arg : Division by zero Recommended actions Cannot divide by 0. Rewrite the program so that the divide operation is not executed when the divisor is 0. 40195, Limit error Description Task arg : The configured maximum number of RETRYs ( arg retries) 6 Trouble shooting by Event log 204 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. is exceeded. Recommended actions The error correction performed before the RETRY instruction is executed, is probably not enough to cure the error. Check the error handler. 40196, Instruction error Description Task arg : Attempt to execute place holder Recommended actions Remove the place holder or the instruction containing it, or make the instruction complete. Then continue execution. 40197, Execution error Description Task arg : Function does not return any value Recommended actions The end of the function has been reached without a RETURN instruction being executed. Add a RETURN instruction specifying a function return value. 40198, Value error Description Task arg : Illegal orientation value arg Recommended actions Attempt to use illegal orientation (quaternion) value 40199, Value error Description Task arg : Illegal error number arg in arg . Recommended actions Use error numbers in the range 1-90 or book error numbers with the instruction BookErrNo. 40200, Limit error Description Task arg : No more interrupt number available Recommended actions There is a limited number of interrupt numbers available. Rewrite the program to use fewer interrupt numbers. This message may also occur as a consequence of a system error. 40202, Type error Description Task arg : Dimensions arg and arg of conformant array dimension number arg are incompatible Recommended actions The array is not of the expected size. Array assignment may only be performed on arrays of identical size. 40203, Reference error Description Task arg : Optional parameter arg not present Recommended actions The value of a non-present optional parameter may not be referred. Use the predefined function 'Present' to check the presence of the parameter before using its value. 40204, Value error Description Task arg : Array index arg for dimension number arg out of bounds (1- arg ) Recommended actions The array index value is non-positive or violates the declared size of the array. 40205, Value error Description Task arg : Rapid String arg too long
ABB_IRC5_Operating_Troubleshooting_Manual	https://library.e.abb.com/public/e6617595547fc6c2c1257cc5004451bd/Operating%20manual_Trouble%20shooting_3HAC020738-001_revK_en.pdf	206	6 Trouble shooting by Event log 203 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions No trap (or other object) with the specified name is visible from this program position. 40171, Reference error Description Task arg : Reference to unknown data (or other object) found during execution of module arg . Recommended actions Check the program for unresolved references. 40172, Reference error Description Task arg : Reference to unknown module arg . Recommended actions No module (or other object) with the specified name is visible from this program position. Check the program for incorrect module reference or if the module is missing. 40173, Reference error Description Task arg : Reference to object arg that is not a module. Recommended actions The specified name identifies an object other than a module. Check the program for incorrect module reference. 40174, Reference error Description Task arg : Reference to module arg is ambiguous. Recommended actions At least one other object sharing the same name as the referred module is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40175, Reference error Description Task arg : Reference to procedure arg is ambiguous. Recommended actions At least one other object sharing the same name as the referred procedure is visible from this program position. Make sure that all object names fulfill the naming rules regarding uniqueness. 40191, Instruction error Description Task arg : Variable and trap routine already connected Recommended actions It is not legal to connect a specific variable with a trap routine more than once. 40192, Argument error Description Task arg : arg is second present conditional argument for excluding parameters Recommended actions Arguments may not be present for more than one parameter from a list of parameters that exclude each other. 40193, Execution error Description Task arg : Late binding procedure call error arg Recommended actions There is an error in the procedure call instruction. See previous message for the actual cause. 40194, Value error Description Task arg : Division by zero Recommended actions Cannot divide by 0. Rewrite the program so that the divide operation is not executed when the divisor is 0. 40195, Limit error Description Task arg : The configured maximum number of RETRYs ( arg retries) 6 Trouble shooting by Event log 204 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. is exceeded. Recommended actions The error correction performed before the RETRY instruction is executed, is probably not enough to cure the error. Check the error handler. 40196, Instruction error Description Task arg : Attempt to execute place holder Recommended actions Remove the place holder or the instruction containing it, or make the instruction complete. Then continue execution. 40197, Execution error Description Task arg : Function does not return any value Recommended actions The end of the function has been reached without a RETURN instruction being executed. Add a RETURN instruction specifying a function return value. 40198, Value error Description Task arg : Illegal orientation value arg Recommended actions Attempt to use illegal orientation (quaternion) value 40199, Value error Description Task arg : Illegal error number arg in arg . Recommended actions Use error numbers in the range 1-90 or book error numbers with the instruction BookErrNo. 40200, Limit error Description Task arg : No more interrupt number available Recommended actions There is a limited number of interrupt numbers available. Rewrite the program to use fewer interrupt numbers. This message may also occur as a consequence of a system error. 40202, Type error Description Task arg : Dimensions arg and arg of conformant array dimension number arg are incompatible Recommended actions The array is not of the expected size. Array assignment may only be performed on arrays of identical size. 40203, Reference error Description Task arg : Optional parameter arg not present Recommended actions The value of a non-present optional parameter may not be referred. Use the predefined function 'Present' to check the presence of the parameter before using its value. 40204, Value error Description Task arg : Array index arg for dimension number arg out of bounds (1- arg ) Recommended actions The array index value is non-positive or violates the declared size of the array. 40205, Value error Description Task arg : Rapid String arg too long 6 Trouble shooting by Event log 205 3HAC020738-001 Revision: K © Copyright 2005-2010 ABB. All rights reserved. Recommended actions String value exceeds the maximum allowed length. Rewrite the program to use strings of less length. 40206, Interrupt queue full Description Execution of all normal tasks has stopped. Too many interrupts has occurred in arg while executing a trap routine. Consequences The system goes to blocked state and can not be restarted before moving the program pointer to an arbitrary position. Probable causes Too many interrupts has occurred while executing a trap routine. This can be caused by heavy CPU load. Recommended actions 1) Minimize execution time in the trap routine. 2) Disable/enable interrupts while executing a trap routine using the Isleep or Iwatch commands. 40207, Value error Description Task arg : Illegal error number arg in arg Recommended actions Error numbers used in an ERROR handler must be positive. 40208, Error event queue full Description Task arg : The program was already executing an error event when a new event occurred. Recommended actions Attend the cause of the error event and restart the program. 40209, Error context already consumed Description An error event in task arg has occurred. The context of the RAPID instruction that has generated this event is however already consumed. No error handling is therefore possible to execute. Recommended actions Attend the cause of the error event and restart the program. 40210, Interrupt removed from queue Description All interrupts have been deleted from the interrupt queue in task arg . Consequences No trap routines, connected with the interrupt, may be executed. Probable causes -The program has been stopped -A service routine or an event routine may be executing. -The program is executing in step mode. Recommended actions - 40221, Execution error Description Task arg : Execution aborted Recommended actions Execution was aborted due to a fatal error. 40222, Limit error Description Task arg : Execution stack overflow Recommended actions The program is too complex to execute. Probably the program contains recursive routines. 40223, Execution error Description The execution of task arg has been stopped by a runtime error. Consequences The program execution is immediately halted. Probable causes The program error is considered UNRECOVERABLE so no error recovery attempt by an error handler routine (if used) was allowed. The actual cause of the error may vary, and is likely to be specified in an event log message logged simultaneously as this one. Recommended actions 1) Check other event log messages logged simultaneously to determine the actual cause. 40224, Execution error Description Task arg : Illegal return code arg from ReaL routine This is always caused by an internal error in the ReaL routine.

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.