Code Number 5000 ~
| No. | Message | Countermeasure | Note 1 | Note 2 | Error Solution |
|---|---|---|---|---|---|
| 5000 | Servo control gate array failure. | Do one of the following: - Check the short-circuit and improper connection of the peripheral equipment wiring. (Emergency and I/O connectors) - Replace the main board. - Replace the additional axis unit. | Reboot | ||
| 5002 | Motor driver not mounted. | Do one of the following: - Check whether the motor driver is mounted. - Check the model setting and hardware setting. - Replace the motor driver. - Replace the MAIN board. | Reboot | ||
| 5005 | Encoder division setting failure. | Check the model setting. | Reboot | ||
| 5007 | Encoder multi-turn beyond maximum range. | Do one of the following: - Reset the encoder. - Replace the motor. | Reboot | ||
| 5008 | Position is out of range. | Do one of the following: - Reset the encoder. - Replace the MAIN board. - Replace the motor. | Reboot | ||
| 5009 | No encoder response. | Do one of the following: - Check the model setting. - Check the signal cable connection. - Replace the main board and encoder I/F board. | Reboot | ||
| 5010 | Failed to initialize encoder. | Do one of the following: - Reboot the Controller. - Check the robot configuration. - Check the signal cable connection. - Replace the main board and encoder I/F board. | Reboot | ||
| 5011 | Failed to communicate with encoder. | Do one of the following: - Reboot the Controller. - Check the robot configuration. - Check the signal cable connection. - Replace the main board and encoder I/F board. | Reboot | ||
| 5012 | Servo CPU watchdog timer detected a failure. | Do one of the following: - Reboot the Controller. - Check the noise countermeasure. - Replace the MAIN board. | Reboot | ||
| 5013 | Current control circuit WDT detected a failure. | Do one of the following: - Reboot the Controller. - Check the power cable connection. - Check the 15V power supply and cable connection. - Check the noise countermeasure. - Replace the MAIN board. | Reboot | ||
| 5014 | The main board is not compatible with the robot. | Do one of the following: - Check the robot configuration. - Replace it with a main board that is compatible with the robot. | Reboot | ||
| 5015 | The encoder was reset. | Reboot the Controller. | Reboot | ||
| 5016 | Encoder data backup power supply failure. | Do one of the following: - Check the signal cable connection. - Replace the encoder batteries and reset the encoder. | Reboot | ||
| 5017 | Encoder data backup data failure. | Do one of the following: - Reset the encoder. - Check the signal cable connection. | Reboot | ||
| 5019 | Encoder position failure. | Do one of the following: - Reset the encoder. - Replace the motor. (Encoder failure) | Reboot | ||
| 5020 | Speed is too high when encoder power supply is on. | Do one of the following: - Check the interference with the other devices. - Check that robot operation has been stopped and reboot the Controller. - Reset the encoder. | Reboot | ||
| 5022 | R/D transducer failure. | Do one of the following: - Check the signal wiring of the manipulator (loose pin, disconnection, short). - Reset the encoder. | Reboot | ||
| 5023 | G sensor communication failure. | Do one of the following: - Check the signal wiring connection. - Check the signal wiring of the manipulator (loose pin, disconnection, short). - Check the noise countermeasures. - Replace the control board. - Replace the MAIN board. | Reboot | ||
| 5024 | G sensor data failure. | Replace the control board. | Reboot | ||
| 5025 | The multi rotational data and the R/D conversion data is different. | Check the noise countermeasure. | Reboot | ||
| 5026 | Resolver excitation signal disconnected. | Do one of the following: - Check the signal wiring of the manipulator (loose pin, disconnection, short). - Reset the encoder. | Reboot | ||
| 5027 | S-DSP detected the communication error in DSP. | Do one of the following: - Reboot the Controller. - Check the noise countermeasure. - Replace the MAIN board. | Reboot | ||
| 5028 | Current feedback data error detected. | Do one of the following: - Reboot the Controller. - Check the noise countermeasure. - Replace the MAIN board. | Reboot | ||
| 5029 | D-DSP communication failure. | Do one of the following: - Reboot the Controller. - Check the noise countermeasure. - Replace the MAIN board. | Reboot | ||
| 5030 | Speed is too high when encoder power supply is off. | Do one of the following: - Reset the encoder. - Replace the motor. | Reboot | ||
| 5031 | Encoder speed is too high. | Do one of the following: - Reset the encoder. - Replace the motor. | Reboot | ||
| 5032 | Servo alarm A. | Reboot the Controller. | Reboot | ||
| 5033 | Failed to initialize G sensor. | Do one of the following: - Reboot the Controller. - Check the signal cable connection. - Check the noise countermeasure. | Reboot | ||
| 5034 | Encoder reset failed. | Do one of the following: - Reboot the Controller. - Reset the encoder again. - Check the signal cable connection. - Replace the motor. (Encoder failure) - Check the noise countermeasures. | Reboot | ||
| 5040 | Motor torque output failure in high power state. | Do one of the following: - Specify the Weight/Inertia setting. - Check the load. - Check the model setting. - Check the robot. (Smoothness, backlash, non-smooth motion, loose belt tension, brake, belt slipping) - Check interference with peripheral equipment. (Collision, contact) - Check the power cable connection. - Check the robot power wiring. (loose pin, disconnection, short). - Check power supply voltage. (Low power supply voltage) - Replace the motor driver. - Replace the MAIN board. - Replace the motor. | Reset | ||
| 5041 | Motor torque output failure in low power state. | Do one of the following: - Check the model setting. - Check the robot. (Smoothness, backlash, non-smooth motion, loose belt tension, brake) - Check interference with peripheral equipment. (Collision, contact) - Check the power cable connection. - Check the robot power wiring. (loose pin, disconnection, short). - Check power supply voltage. (Low power supply voltage) - Replace the motor driver. - Replace the MAIN board. - Replace the motor. | Reset | ||
| 5042 | Position error overflow in high power state. | Do one of the following: - Specify the Weight/Inertia setting. - Check the load. - Check the model setting. - Check the robot. (Smoothness, backlash, non-smooth motion, loose belt tension, brake, belt slipping) - Check interference with peripheral equipment. (Collision, contact) - Check the power cable connection. - Check the robot power wiring. (loose pin, disconnection, short). - Check power supply voltage. (Low power supply voltage) - Replace the motor driver. - Replace the MAIN board. - Replace the motor. | Reset | ||
| 5043 | Position error overflow in low power state. | Do one of the following: - Check the model setting. - Check the robot. (Smoothness, backlash, non-smooth motion, loose belt tension, brake) - Check interference with peripheral equipment. (Collision, contact) - Check the power cable connection. - Check the robot power wiring. (loose pin, disconnection, short). - Check power supply voltage. (Low power supply voltage) - Replace the motor driver. - Replace the MAIN board. - Replace the motor. | Reset | ||
| 5044 | Speed error overflow in high power state. | Do one of the following: - Specify the Weight/Inertia setting. - Check the load. - Check the model setting. - Check the robot. (Smoothness, backlash, non-smooth motion, loose belt tension, brake, belt slipping) - Check interference with peripheral equipment. (Collision, contact) - Check the power cable connection. - Check the robot power wiring. (loose pin, disconnection, short). - Check power supply voltage. (Low power supply voltage) - Replace the motor driver. - Replace the MAIN board. - Replace the motor. | Reset | ||
| 5045 | Speed error overflow in low power state. | Do one of the following: - Check the model setting. - Check the robot. (Smoothness, backlash, non-smooth motion, loose belt tension, brake) - Check interference with peripheral equipment. (Collision, contact) - Check the power cable connection. - Check the robot power wiring. (loose pin, disconnection, short). - Check power supply voltage. (Low power supply voltage) - Replace the motor driver. - Replace the MAIN board. - Replace the motor. | Reset | ||
| 5046 | Speed error in high power state. | Do one of the following: - Reduce the CP motion SpeedS value. - Change the orientation of the CP motion. - Specify the Weight/Inertia setting. - Check the load. - Check the robot. (Smoothness, backlash, non-smooth motion, loose belt tension, brake, belt slipping) - Check interference with peripheral equipment. (Collision, contact) - Check the model setting. - Check the power cable connection. - Check the signal cable connection. - Check the robot power wiring. (loose pin, disconnection, short). - Check power supply voltage. (Low power supply voltage) - Replace the motor driver. - Replace the MAIN board. - Replace the motor. | Reset | ||
| 5047 | Speed error in low power state. | Do one of the following: - Check the motion in high power state. - Check the model setting. - Check the robot. (Smoothness, backlash, non-smooth motion, loose belt tension, brake) - Check interference with peripheral equipment. (Collision, contact) - Check the power cable connection. - Check the signal cable connection. - Check the robot power wiring. (loose pin, disconnection, short). - Check power supply voltage. (Low power supply voltage) - Replace the motor driver. - Replace the MAIN board. - Replace the motor. | Reset | ||
| 5048 | Main power circuit overvoltage. | Do one of the following: - Specify the Weight/Inertia setting. - Check the load. - Check the model setting. - Check the robot. (Smoothness, backlash, non-smooth motion, loose belt tension, brake) - Check interference with peripheral equipment. (Collision, contact) - Check the power cable connection. - Check the robot power wiring. (loose pin, disconnection, short). - Check power supply voltage. (Low power supply voltage) - Check the regeneration unit. - Replace the motor driver. - Replace the MAIN board. - Replace the motor. | Reset | ||
| 5049 | Motor driver overcurrent. | Do one of the following: - Check the short-circuit and earth fault of the power line. - Replace the motor driver. - Replace the MAIN board. | Reset | ||
| 5050 | Speed error detected during torque control. | Check if motion speed during torque control is within the specified range. | Reset | ||
| 5051 | Motor driver PWM drive 15V power supply error. | Do one of the following: - Reboot the Controller. - Check the DPU and cable connection. - Replace the motor driver. - Replace the MAIN board. | Reset | ||
| 5054 | Motor overload. | Do one of the following: - Lower the motion duty. - Lower Accel. - Check the Weight/Inertia setting. - Check the robot. (Backlash, large load, loose belt tension, brake) | Reset | ||
| 5055 | Motor overload. | Do one of the following: - Lower the motion duty. - Lower Accel. - Check the Weight/Inertia setting. - Check the robot. (Backlash, large load, loose belt tension, brake) | Reset | ||
| 5056 | G sensor data has changed rapidly. | Do one of the following: - Check the noise countermeasure. - Replace the control board. | Reset | ||
| 5057 | Collision detected in high power mode (robot motion error detection). | Collision detection (detection of robot motion error) was functioned. Detect the following errors: - Robot arm collision and contact - Torque overflow due to insufficient Weight and Inertia settings - Torque overflow due to complex motion of multi-joints and swinging long object - Torque overflow due to power supply voltage drop - Error handling due to hardware error or software misoperation: Do one of the following: - Check if the robot arm is colliding with or contacting peripheral objects and change the arrangement to avoid interference - Check for torque overflow In case of torque overflow: Check if Weight and Inertia settings are appropriate and then correct In case of complex motion: Adjust acceleration to avoid torque overflow Check and correct power supply voltage In case of simultaneous error: See "Epson RC+ User's Guide - Collision detection function (robot motion error detection function)” | Reset | ||
| 5058 | Collision detected in low power mode (robot motion error detection). | Collision detection (detection of robot motion error) was functioned. Detect the following errors: - Robot arm collision and contact - Hand weight grasp exceeds specifications, torque overflow due to grasping long object Error handling due to hardware error or software misoperation: Do one of the following. - Check if the robot arm is colliding with or contacting peripheral objects and change the arrangement to avoid interference - Check hand weight and correct - In case of 6-axis robot axis no. 4, 5: Check torque overflow - In case of torque overflow: Change to grasp in high power mode - In case of simultaneous error: See "Epson RC+ User's Guide - Collision detection function (robot motion error detection function)” | Reset | ||
| 5059 | Frequent G sensor communication error. | Do one of the following: - Check the signal cable connection. - Check the noise countermeasure. | Reset | ||
| 5072 | Servo alarm B. | Do one of the following: - Reset the Controller. - Reboot the Controller. | Reset | ||
| 5080 | Motor overload. | Do one of the following: - Lower the motion duty. - Lower Accel. - Check the Weight/Inertia setting. - Check the robot. (Backlash, large load, loose belt tension, brake) | Reset | ||
| 5098 | Encoder temperature is too high. | Do one of the following: - Wait until the temperature of the encoder decreases. - Lower the motion duty. - Check the Weight/Inertia setting. - Check the robot. (Backlash, large load, loose belt tension, brake) | Reset | ||
| 5099 | Motor driver temperature is too high. | Do one of the following: - Clean the cooling fan filter. - Lower the motion duty. - Check the Weight/Inertia setting. - Lower the ambient temperature. | Reset | ||
| 5112 | Servo alarm C. | Reboot the Controller. | Reset | ||
| 5120 | Servo CPU system error detected. | Do one of the following: - Reboot the Controller. - Check the noise countermeasure. - Replace the MAIN board. | Reboot | ||
| 5510 | Force control calculation error. | Do one of the following: - Reboot the Controller. - Reinstall the firmware. - Replace the controller. | Reset | ||
| 5511 | Coordinate transformation error in force control. | Do one of the following: - Check whether the coordinate out of the motion range is not specified. - Check whether the robot moves outside of the motion range during the execution of force control. | Reset | ||
| 5520 | Error in Mass, Damper, or Spring properties or a combination thereof. | Check the parameter combination. Check whether the Mass property value is too small for the Damper property. | Reset | ||
| 5521 | The coordinate system mode other than the custom mode is specified for the Force Sensor which is not associated with the robot. | Check association with the robot. Check if the direction other than the Custom coordinate is specified for the Orientation property of the force coordinate system object for the sensor which is not associated with the robot. | Reset | ||
| 5522 | Undefined data is selected. | The specified Tool, Local, or MP number may be undefined. Check if the specified parameter is defined. | Reset | ||
| 5523 | A parameter which cannot be continued when CF continues force control was specified. | Check the force control object and the force coordinate object used by motion commands before and after continuing force control via the CF parameter. | Reset | ||
| 5530 | The specified time has passed after resetting the Force Sensor. | Execute the Reset property for the force sensor object. | Reset | ||
| 5531 | Approached the singularity point while executing force control. | Do one of the following: - Check whether the coordinates near the singularity is specified. - Check whether the robot moves to the vicinity of the singularity during the execution of force control. - Review the installation position of the robot. | Reset | ||
| 5532 | Buffer for force sensor averaging is saturated. | Shorten the time between AvgForceClear and AvgForce to be within 10 minutes. | Stop task | ||
| 5533 | The continuous time for CF to execute force control has passed. | Check if the motion command interval is one minute or less. | Reset | ||
| 5535 | Force control cannot be executed when V or W are not set to 0 on a SCARA robot. | Set 0 for the Orientation property or V and W in the current command position for Base, Tool, Local, and FCS objects. | Stop task Reset | ||
| 5536 | Force control is not supported for this robot model. | Do one of the following: - Check if the specified robot is correct. - Check if the Controller firmware supports the robot model. | Reset | ||
| 5537 | Deceleration processing failed. | Change the force trigger object TillStopMode property to G_STANDARD_STOP. | Reset | ||
| 5540 | Force Sensor transmission error. | Do one of the following: - Execute the force sensor object Reboot property. - Check the force sensor wiring. - Reboot the force sensor. - Please inquire with us if a similar error occurs even after the above countermeasures are taken. | Reset | ||
| 5541 | Force Sensor reception error. | Do one of the following: - Execute the force sensor object Reboot property. - Check the force sensor wiring. - Reboot the force sensor. - Please inquire with us if a similar error occurs even after the above countermeasures are taken. | Reset | ||
| 5542 | Force Sensor in use. | Check whether the force sensor Reset or Reboot property are running in another task. | Reset | ||
| 5543 | Force Sensor communication error. | Do one of the following: - Execute the force sensor object Reboot property. - Check the force sensor wiring. - Reboot the force sensor. - Please inquire with us if a similar error occurs even after the above countermeasures are taken. | Reset | ||
| 5544 | Element error of Force Sensor. | This error may occur if a long time passed without resetting the force sensor. Do one of the following: - Execute the Reset property for the force sensor object. - Check whether force exceeding the rated value is applied to the Force Sensor. - Reboot the force sensor. - Please inquire with us if a similar error occurs even after the above countermeasures are taken. | Reset | ||
| 5545 | Circuit error 1 of Force Sensor. | Do one of the following: - Execute the Reset property for the force sensor object. - Reboot the force sensor. - Please inquire with us if a similar error occurs even after the above countermeasures are taken. | Reset | ||
| 5546 | Circuit error 2 of Force Sensor. | Do one of the following: - Execute the Reset property for the force sensor object. - Reboot the force sensor. - If a similar error occurs even after the above countermeasures are taken, check if the tip of the robot arm has a vibration. | Reset | ||
| 5547 | High temperature error of the Force Sensor. | Do one of the following: - Execute the Reset property for the force sensor object. - Check the ambient temperature. - Check if the force sensor is subjected to rapid temperature change. - Reboot the force sensor. - Please inquire with us if a similar error occurs even after the above countermeasures are taken. | Reset | ||
| 5548 | Force Sensor detected force exceeding the rated value. | Do one of the following: - Execute the Reset property for the force sensor object. - Check whether force exceeding the rated value is applied to the Force Sensor. - Reboot the force sensor. - Please inquire with us if a similar error occurs even after the above countermeasures are taken. | Reset | ||
| 5549 | Force sensor not connected. | Do one of the following: - Check the force sensor wiring. - Reboot the force sensor. - Please inquire with us if a similar error occurs even after the above countermeasures are taken. | Reset | ||
| 5550 | Force sensing of the Force Sensor is off. | Do one of the following: - Check the force sensor configuration. - Reboot the force sensor. | Reset | ||
| 5551 | A force sensor not supported on the controller is connected. | Do one of the following: - Check whether the controller firmware supports the Force Sensor. - Check the force sensor wiring. - Reboot the force sensor. | Reset | ||
| 5552 | Configuration of the force sensor failure. | Check the force sensor configuration. | Reset | ||
| 5553 | Unsupported function is executed on the connected force sensor. | Do one of the following: - Check the force sensor configuration. - Review the program. | Reset | ||
| 5560 | Force sensor drift correction error. | Do one of the following: - Check the force sensor wiring. - Reboot the force sensor. | Reset | ||
| 5800 | Failed to initialize force control. | Do one of the following: - Reboot the Controller. - Reinstall the controller firmware. - Replace the controller. | Reboot | ||
| 5802 | Force control calculation error. | Do one of the following: - Reboot the Controller. - Reinstall the controller firmware. - Replace the controller. | Stop task | ||
| 5803 | Force Sensor failed to connect with the robot. | Check connection setting of the Force Sensor. | Stop task | ||
| 5810 | Force control parameter error. | Check the range of the specified parameter. | Stop task | ||
| 5811 | Force control object parameter out of range. Note 1: Parameter type Note 2: Axis | Check the force control object property value. | 1: Number 2: Coordinate System 3: Enabled 4: Mass 5: Damper 6: Spring 7: TargetForce PriorityMode 8: TargetForce 9: LimitSpeed 10: LimitAccel | 1:Fx 2:Fy 3:Fz 4:Tx 5:Ty 6:Tz Or 1:J2:S3:R | Stop task |
| 5812 | Force control object LimitSpeed or LimitAccel property is lower than the robot speed or acceleration setting. | Check the Speed, SpeedS, SpeedR, Accel, AccelS, AccelR, LimitSpeed and LimitAccel values. | Stop task | ||
| 5813 | Force control object Enabled properties are all FALSE. | Enable the Enabled property for at least one axis. | Stop task | ||
| 5814 | Force control cannot be executed when V or W are not set to 0 on a SCARA robot or when Tx or Ty_Enabled is set to true. | Do one of the following: - Disable Tx and Ty Enabled. - Set 0 for the Orientation property or V and W in the current command position for Base, Tool, Local, and FCS objects. | Stop task | ||
| 5815 | Force trigger object parameter out of range. Note 1: Parameter type Note 2: Axis | Check the force trigger object property value. | 1:Number 2:ForceSensor 3:Coordinate System 4:TriggerMode 5:Operator 6:Enabled 7:FMag_Axes 8:TMag_Axes 9: Polarity 10:UpperLevel 11:LowerLevel 12:UpperLevel is smaller than LowerLevel 13:LPF_Enabled 14:LPF_TimeConstant | 1:Fx 2:Fy 3:Fz 4:Tx 5:Ty 6:Tz 7:Fmag 8:Tmag | Stop task |
| 5816 | Force coordinate system object parameter out of range. Note 1: Parameter type Note 2: Axis | Check the force coordinate object property value. | 1:Number 2:Position 3:Orientation_Mode 4:Orientation_UVW 5:Orientation_RobotLocal | 1:X2:Y3:Z or 1:U2:V3:W | Stop task |
| 5817 | Force monitor object parameter out of range. Note 1: Parameter type Note 2: Axis | Check the force monitor object property value. | 1:Number 2:ForceSensor 3:Coordinate System 4:FMag_Axes 5:TMag_Axes 6:LPF_Enabled 7:LPF_TimeConstant | Stop task | |
| 5818 | Force Motion Restriction Object parameter is out of the range. | Check the force motion restriction object property value. | 1:Number 3:Coordinate System 6:Dist_Axes 7:Rot_Axes 8:UpperLevel 9:LowerLevel 10: UpperLevel is smaller than LowerLevel 11:Operator 12:ForceSensor 13:HoldTimeThresh 14:DatumPoint 15:RobotLocal 16:RobotTool 17:TriggerMode 18:Enabled | Stop task | |
| 5819 | Specified duration of FCKeep is out of the allowable range. | Check if the specified duration is 600 seconds or less. | Stop task | ||
| 5830 | Force control cannot resume from the pause. | Abort the motion. If SF_LimitSpeedSEnable is On, this error may occur. SF_LimitSpeedSEnable is On by default. Turn it Off. For details, refer to "SPEL+ Language Reference - SF_LimitSpeedSEnable". | Stop task | ||
| 5831 | Cannot execute this command during force control. | Abort force control with FCEnd and try again. | Stop task | ||
| 5832 | Cannot execute the motion command which has no Force Control Object during force control. | Check if the motion command directly after continuing force control via CF contains force control. | Stop task | ||
| 5833 | Cannot use gravity compensation. | Gravity compensation is not available with this force sensor and robot combination. Set MP0. | Stop task | ||
| 5834 | Unsupported function is executed on the connected force sensor. | Do one of the following: - Check the force sensor configuration. - Review the program. | Stop task | ||
| 5840 | Force Sensor in use. | Check whether the force sensor Reset or Reboot property are running in another task. | Stop task | ||
| 5841 | Failed to reset force sensor. Note 1: Detailed error information | Do one of the following. - When the parameter is omitted or FG_RESET_FINE is specified, specify FG_RESET_WAIT_VIBRATION for the parameter. - When FG_RESET_WAIT_VIBRATION is specified, adjust the reset timing via Wait statement or remove the external vibration source. | 1: Timeout because Fine condition is not satisfied. 2: Timeout because vibration did not stop. | Stop task | |
| 5901 | Failed to allocate memory (force control). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Reset Reboot | ||
| 5903 | An unsupported robot number was specified. | Do one of the following: - Check the robot configuration. - Check the robot number specified in the SPEL command. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Stop task Reset | ||
| 5904 | Failed to allocate memory (force control). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Reset | ||
| 5906 | An unsupported number was specified in the force object. | Do one of the following: - Check the force object definition. - Check the force object number specified in the SPEL command. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Stop task Reset | ||
| 5907 | Specified force data number was not defined. | Stop the task and do one of the following: - Check the force object definition. - Check the force object number specified in the SPEL command. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Stop task Reset | ||
| 5908 | Specified force coordinate system data number was not defined. | Stop the task and do one of the following: - Check the force coordinate system object number definition. - Check the force coordinate system object number specified in the SPEL command. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Stop task | ||
| 5909 | A force object that cannot be deleted or changed was specified. | Stop the task and check the force object specified in the SPEL command. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Stop task | ||
| 5910 | An unsupported value parameter was specified. | Stop the task and check the parameter data specified in the SPEL command. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Stop task | ||
| 5911 | The upper threshold is less than the lower threshold. | Stop the task and check the parameter data specified in the SPEL command. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Stop task | ||
| 5912 | An unsupported quantity parameter was specified (command). | Stop the task and check the parameter data specified in the SPEL command. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Number of parameters | Stop task | |
| 5913 | An unsupported quantity parameter was specified (function). | Stop the task and check the parameter data specified in the SPEL command. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Number of parameters | Stop task | |
| 5914 | An unsupported data type parameter was specified. | Stop the task and check the parameter data specified in the SPEL command. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Stop task | ||
| 5918 | Specified force data label cannot be found. | Specify a defined valid force data label. | - | ||
| 5921 | Duplicate label names found. | Do one of the following: - Correct the force data label name included in the project. - Rebuild the project. - Synchronize the project or transfer it via restore. | - | ||
| 5927 | Cannot read the force data from the force file. | The force data is invalid and cannot be read. Re-create the force file. | 0: FC1: FCS2: FT3: FM4: MASS | Force data number | - |
| 5928 | Failed to allocate memory (force control). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Reset Reboot | ||
| 5929 | The specified force file could not be opened. | Do one of the following: - Check the specified force file name. - Restore the project that was operating correctly. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task Reset | ||
| 5930 | A label name that exceeds the upper limit length was specified. | Do one of the following: - Stop the task and check the label name specified in the SPEL command. Targets are the commands corresponding to the function name and row number in the system history. Refer to "Label Property" in the reference manual for correction instructions. - Correct the force data label name included in the project. - Rebuild the project. - Synchronize the project or transfer it via restore. | Stop task Reset | ||
| 5931 | A comment that exceeds the upper limit length was specified. | Do one of the following: - Stop the task and check the comment specified in the SPEL command. Targets are the commands corresponding to the function name and row number in the system history. Refer to "Description Property" in the reference manual for correction instructions. - Correct the force data comment included in the project. - Rebuild the project. - Synchronize the project or transfer it via restore. | Stop task | ||
| 5932 | An invalid force file was specified. | Do one of the following: - Check the specified force file name. - Restore the project that was operating correctly. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task Reset | ||
| 5933 | An invalid force file was specified. | Do one of the following: - Check the specified file name. - Restore the project that was operating correctly. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task Reset | ||
| 5934 | Failed to access the force file. | Stop the task and do one of the following: - Check the controller capacity. - Check the file path name specified in the SPEL command. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Robot number | Stop task | |
| 5940 | An unsupported label name force data was specified (the first character is not an alphabet). | Do one of the following: - Check the parameter specified in the SPEL command of the specified project. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. - Correct the force data label name included in the project. - Rebuild the project. - Synchronize the project or transfer it via restore. | Stop task Reset | ||
| 5941 | An unsupported label name force data was specified (only alphanumeric characters and underscores can be used). | Do one of the following: - Check the parameter specified in the SPEL command of the specified project. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. - Correct the force data label name included in the project. - Rebuild the project. - Synchronize the project or transfer it via restore. | - | ||
| 5944 | A force file name with a different version was specified. | Do one of the following: - Check the specified force file name. - Restore the project that was operating correctly. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task Reset |