Code Number 1000 ~
| No. | Message | Countermeasure | Note 1 | Note 2 | Error Solution |
|---|---|---|---|---|---|
| 1001 | A system error has occurred. (invalid parameter) | Do one of the following: - Reboot the Controller. - Restore the backup file that was operating correctly. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1002 | Cannot access the specified data. | Do one of the following. - Review the Controller setting. - Check the connection of the board mounted on the controller. - Make sure the specified file is accessible. - Restore the backup file that was operating correctly. - Update the controller firmware with the update tool. | - | - | |
| 1003 | The connection password is invalid. | - Enter the connection password set on the controller. | - | - | |
| 1004 | Cannot use the specified backup data or update tool because this version is not supported. | Do one of the following. - Update the controller firmware with the update tool. - Check the specified backup data. - Use a new update tool. Cannot revert the controller to the old version. - Update RC+ to the latest version. | - | - | |
| 1005 | Cannot restore with the specified backup data because the serial number is different. | Select backup data with the same serial numbers and try again. | - | - | |
| 1006 | Cannot restore with the specified backup data because the robot model is different. | Select backup data with the same robot models and try again. | - | - | |
| 1007 | Cannot restore with the specified backup data because the controller type is different. | Select backup data with the same controller types and try again. | - | - | |
| 1008 | Failed to initialize TP because an unsupported TP has been detected. | Do one of the following. - Reconnect a TP supported on the controller. - If this error occurs repeatedly, contact us. | - | - | |
| 1010 | R-I/O number was specified for the Remote I/O function. | Set a remote I/O command other than the following I/O number: - Real time I/O - Hand-I/O | - | - | |
| 1011 | The specified I/O number cannot be assigned to the remote I/O signal because it is unsupported by the selected fieldbus slave. | Do one of the following. - Check the fieldbus slave screen size, the specified bit, and reset the remote I/O command. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1012 | The specified I/O number cannot be assigned to the remote I/O signal because it is unsupported by the selected fieldbus master. | Do one of the following. - Check the fieldbus master screen size, the specified bit, and reset the remote I/O command. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1013 | Failed to resize Fieldbus slave area due to bits in use in remote I/O. | Do one of the following. - Check the connected fieldbus board type and I/O range, check the size, then try again. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1015 | The configured Hand I/O number was specified for the remote I/O function. | - Check the specified I/O number. The following I/O numbers that are in use cannot be specified: - Real time I/O - Hand setting - Function block | - | - | |
| 1016 | The PLC remote settings are invalid (data size, reserved I/O number, PLC vendor type). | Do one of the following. - Specify the necessary PLC vendor type function block size. - Check the function block usage. - Check the specified I/O number. The following I/O numbers that are in use cannot be specified: - Real time I/O - Hand setting - Function block | - | - | |
| 1020 | A system error has occurred. (recovery mode called) | Reboot the controller in normal mode and try again. The restore function and update tool required for controller recovery can be executed. | - | - | |
| 1021 | This operation cannot be executed because the controller failed to initialize. | Do one of the following. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1022 | This operation cannot be executed because the SPEL project is not open. | 1. Open a project. 2. Rebuild the project. | - | - | |
| 1023 | This operation cannot be executed because the SPEL project is already open. | Close the project and try again. | - | - | |
| 1024 | The current setting restricts execution from Remote I/O. | Do the following in order and change the settings. 1. Set the control device to remote I/O. 2. Do one of the following: - Disconnect the RC+ and controller and set the system to Auto mode. - Enable remote I/O in the RC+ Run window. | - | - | |
| 1025 | This operation is not supported in TEACH mode. | Set the controller operation mode to Auto and try again. | - | - | |
| 1026 | This operation can only be executed from TP in TEACH mode. | Do one of the following. - Execute again from TP. - Set the controller operation mode to Auto and try again. | - | - | |
| 1027 | This operation is not supported in Auto mode. | Set the controller operation mode to Program and try again. | - | - | |
| 1028 | This operation can only be executed from device control in Auto mode. | Do one of the following. - Execute the operation again from the currently-set control device. - Change the control device and try again. - Set the controller operation mode to Program and try again. | - | - | |
| 1030 | The specified control device does not have permission to change the controller's operation mode. | Use TP to change the mode from TEACH or TEST mode. | - | - | |
| 1031 | Cannot perform this operation while a task is running. | End unnecessary tasks or wait for the task to finish and try again. | - | - | |
| 1032 | The number of running tasks has already reached the maximum limit. | End unnecessary tasks or wait for the task to finish and try again. | - | - | |
| 1033 | Cannot perform this operation while the asynchronous robot motion command is running. | Stop the motion or wait for the task to finish and try again. | - | - | |
| 1034 | The specified asynchronous command is already complete. | Check if the robot motion is proceeding as intended. | - | - | |
| 1035 | The current setting allows execution only from Remote I/O. | Do one of the following: - Set controller operation mode to Program, confirm that remote I/O is disabled in the Epson RC+ Run window, then try again. - Change the control device and try again. | - | - | |
| 1037 | The current setting allows execution only from Remote Ethernet. | Do one of the following: - Set controller operation mode to Program, confirm that remote Ethernet is disabled in the Epson RC+ Run window, then try again. - Change the control device and try again. | - | - | |
| 1039 | Cannot perform this operation while a task is running. | End unnecessary tasks or wait for the task to finish and try again. | - | - | |
| 1040 | This operation is not supported on the connected controller. | Do one of the following: - Check the controller model. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1041 | Cannot perform this operation during emergency stop status. | Clear the emergency stop status and execute the command again. | - | - | |
| 1042 | Cannot perform this operation during safeguard is enabled. | Disable the safeguard (safety fence closed) and then execute the task again. | - | - | |
| 1043 | Cannot perform this operation during Error status. | Do the following in order. 1. Check the error in the system history. 2. Remedy the error. 3. Execute again. | - | - | |
| 1045 | Cannot perform this operation because the controller is waiting for INPUT command. | Wait for the INPUT command to finish and try again. | - | - | |
| 1046 | Cannot perform this operation during file transfer. | Wait for file transfer to finish and try again. | - | - | |
| 1047 | Cannot cancel this command because it is executed from other devices. | Stop the command from the device it was executed on. | - | - | |
| 1048 | Cannot perform this operation because a drop in the power supply voltage was detected. | Cannot execute after low voltage was detected. Do the following in order. 1. Check the controller power status. 2. Reboot the Controller. | - | Reboot | |
| 1049 | This control device does not have permission to change the controller's operation mode. | Execute the operation again from the control device changed in the current operation mode. | - | - | |
| 1050 | The specifed password is too long. | Do one of the following: - Check the password length and try again. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1051 | Failed to back up the controller settings to USB memory. | Do one of the following: - Check the USB memory connection and try again. - Use another USB memory and try again. - Reboot the controller and try again. | - | - | |
| 1052 | Backup of controller settings has already started. | Auto backup could be running on the controller. Wait for it to end and try again. | - | - | |
| 1053 | This operation is not supported in TEST mode. | Set the controller operation mode to TEACH or Auto and try again. | - | Stop task | |
| 1054 | Cannot perform this operation except from TP in TEST mode. | Do one of the following: - Execute again from TP. - Set the controller operation mode to TEACH or AUTO and try again. | - | Stop task | |
| 1055 | Cannot execute the background task. | Do one of the following: - Stop any unnecessary background tasks. - Check that the program contains the BGMain function and rebuild it. | - | Stop task | |
| 1056 | The current setting prohibits operation from TP. | Stop the task and do one of the following: - Execute the operation from the currently-set control device. - Set the controller operation mode to TEACH or TEST and try again. - Enable TP in the Epson RC+ Run window and try again. - Change the control device and try again. | - | Stop task | |
| 1057 | The current setting allows operation only from the set TP. | Stop the task and do one of the following: - Execute the operation from the currently-set TP. - Set controller operation mode to Program, confirm that TP is disabled in the Epson RC+ Run window, then try again. - Change the control device and try again. | - | Stop task | |
| 1058 | Cannot perform this operation except in T2 mode. | Stop the task, set the TP mode change key switch to Teach/T2, and try again. | - | Stop task | |
| 1059 | T2 mode is prohibited. | - Check the operation mode of the controller you want to change. - T2 mode cannot be used on RC800-A controllers that comply with UL standards. | - | - | |
| 1065 | Cannot reboot the controller because it is saving data. | Wait and try again. | - | - | |
| 1100 | Failed to access the file. | Do one of the following: - Check the file name. - Reduce the number of files to transfer. - Delete unnecessary files. - Reduce the number of restore targets in the restore data selection dialog. - Check the backup folders specified in backup. - Check the backup data specified in restore. - Reboot the Controller. - Update the controller firmware with the update tool. - Replace the controller SD. | - | - | |
| 1102 | Failed to access system settings. | Do one of the following: - Execute again. - Reboot the Controller. - Update the controller firmware with the update tool. - Replace the controller SD. - If this error occurs repeatedly, contact us. | - | - | |
| 1103 | The specified file is not found. | Do one of the following: - Check the specified backup files for executing restore. - Update the controller firmware with the update tool. - Reinstall Epson RC+. | - | - | |
| 1104 | SPEL project configuration file is not found. | Synchronize the project file or transfer it via restore. | - | Reset | |
| 1105 | Object file is not found. | Do one of the following: - Rebuild the project. - Synchronize the project or transfer it via restore. | - | Reset | |
| 1106 | The specified point file does not exist. | Do one of the following: - Synchronize the project or transfer the project that contains the required point file via restore. - Create the required point file. - Check the point file settings in the project. | - | Reset | |
| 1107 | The specified SPEL project is not supported by the current compiler version. | Do one of the following: - Rebuild the SPEL project in the compiler version supported on the controller. - Specify the SPEL project for the compiler version supported on the controller. - Synchronize or transfer the SPEL project for the compiler version supported on the controller or transfer the project via restore. | - | Reset | |
| 1108 | The specified SPEL project needs to be built. | Do one of the following: - Rebuild the project. - Synchronize the project or transfer it via restore. | - | Reset | |
| 1111 | Conveyor file is not found. | Do one of the following: - Synchronize the project or transfer the project that contains the required conveyor file via restore. - Configure the necessary conveyor settings and create the file. - Check the conveyor file settings in the project. | - | - | |
| 1112 | Force files are not found. | Do one of the following: - Synchronize the project or transfer the project that contains the required force file via restore. - Create the necessary force file. - Check the force file settings in the project. | - | Reset | |
| 1114 | The number of SPEL projects that can be created in the controller has already reached the maximum limit. | Do one of the following: - Delete files in an application that supports multiple projects. - Update the controller firmware with the update tool. | - | - | |
| 1120 | Failed to load the system settings. (file corrupted) | Do one of the following: - Execute again. - Reboot the Controller. - Update the controller firmware with the update tool. - Replace the controller SD. - If this error occurs repeatedly, contact us. | - | - | |
| 1121 | Failed to load SPEL project settings. (file corrupted) | Synchronize the project or transfer it via restore. | - | Reset | |
| 1122 | Failed to open the Point file. (file corrupted) | Do one of the following: - Synchronize the project or transfer the project that contains the required point file via restore. - Recreate the required point file. - Check the point file settings in the project. | - | Reset | |
| 1123 | Failed to open the I/O label file. (file corrupted) | Do one of the following: - Synchronize the project or transfer the project that contains the required I/O label files via restore. - Configure the necessary I/O labels again and then create the I/O label files. - Check the I/O label file settings in the project. | - | Reset | |
| 1124 | Failed to open the User Errors file. (file corrupted) | Do one of the following: - Synchronize the project or transfer the project that contains the required user error files via restore. - Configure the necessary user error again and then create the user error files. - Check the user error file settings in the project. | - | Reset | |
| 1125 | Failed to open the Error message file. (file corrupted) | Do one of the following: - Reinstall Epson RC+. - Contact your supplier. | - | - | |
| 1126 | Failed to load the Software option information. (file corrupted) | Do the following in order. 1. Reboot the Controller. 2. Update the controller firmware with the update tool. 3. Reconfigure the software option. | - | - | |
| 1127 | Failed to load the Vision file. (file corrupted) | Do one of the following: - Synchronize the project or transfer the project that contains the required vision files via restore. - Create the required vision files. - Check the vision file settings in the project. | - | Reset | |
| 1128 | Failed to restore the controller settings. (file corruption) | Do one of the following: - Check the specified backup data and try again. - Acquire the backup data again. - Reboot the controller and try again. | - | - | |
| 1130 | No item in the system history. | If the same error occurs, reboot the controller. | - | - | |
| 1131 | Failed to detect USB memory. | Do one of the following: - Check the USB memory connection and try again. - Use another USB memory and try again. - Reboot the controller and try again. | - | - | |
| 1132 | Failed to access the file. | Do one of the following: - Check the controller capacity and backup file size. - Check the control device connection. - Update the controller firmware with the update tool. - Reboot the Controller. - Check the control device connection. - Replace the controller SD. - Replace the controller board. - If this error occurs repeatedly, contact us. | - | Reset | |
| 1133 | Failed to delete file. | Check the file name and path and try again. | - | - | |
| 1134 | Failed to acquire the GUI Builder file. | Do one of the following: - Synchronize the project or transfer the project that contains the required GUI Builder files via restore. - Design the required GUI and recreate the GUI Builder file. - Check the GUI Builder file settings in the project. | - | Reset | |
| 1138 | Failed to read the force guide file. | Do one of the following: - Synchronize the project or transfer the project that contains the required force guide files via restore. - Create the necessary force guide file. - Check the force file guide settings in the project. | - | Reset | |
| 1139 | Failed to read the part feeder file. | Do one of the following. - Synchronize the project or transfer the project that contains the required part feeder files via restore. - Configure the necessary part feeder files again and then create the files. - Check the part feeder file settings in the project. | - | Reset | |
| 1140 | Failed to read the object file. | Do one of the following: - Rebuild the project. - Synchronize the project or transfer it via restore. | - | Reset | |
| 1141 | Failed to acquire SPEL project settings. | Synchronize the project or transfer it via restore. | - | Reset | |
| 1142 | Failed to acquire SPEL project settings. | Synchronize the project or transfer it via restore. | - | Reset | |
| 1143 | Failed to backup controller settings. | Do one of the following: - Execute again. - When backing up to USB memory, use different USB memory and try again. - Reboot the controller and try again. | - | - | |
| 1144 | Failed to backup controller settings. | Do one of the following: - Execute again. - When backing up to USB memory, use different USB memory and try again. - Reboot the controller and try again. | - | - | |
| 1145 | Failed to read the configured conveyor file. | Do one of the following: - Synchronize the project or transfer the project that contains the required conveyor file via restore. - Configure the necessary conveyor settings and create the file. - Check the conveyor file settings in the project. | - | Reset | |
| 1146 | Failed to read the configured conveyor file. | Do one of the following: - Synchronize the project or transfer the project that contains the required conveyor file via restore. - Configure the necessary conveyor settings and create the file. - Check the conveyor file settings in the project. | - | Reset | |
| 1150 | Failed to acquire the system history file (format mismatch). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - Replace the controller SD. | - | - | |
| 1151 | Failed to acquire the system history file (mapping error). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - Replace the controller SD. | - | - | |
| 1152 | Failed to acquire the system history file. | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - Replace the controller SD. | - | - | |
| 1153 | Failed to acquire the system history file. | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - Replace the controller SD. | - | - | |
| 1155 | Failed to acquire settings. | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - Replace the controller SD. - Replace the controller board. - Reinstall Epson RC+ if a virtual controller connection error occurs. - If this error occurs repeatedly, contact us. | - | Reset | |
| 1156 | Failed to save settings. | Do one of the following: - Reboot the Controller. - Restore the backup file that was operating correctly. - Update the controller firmware with the update tool. - Replace the controller SD. - Replace the controller board. - Reinstall Epson RC+ if a virtual controller connection error occurs. - If this error occurs repeatedly, contact us. | - | Reset | |
| 1157 | Failed to acquire settings. | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - Replace the controller SD. - Replace the controller board. - Reinstall Epson RC+ if a virtual controller connection error occurs. - If this error occurs repeatedly, contact us. | - | Reset | |
| 1158 | Failed to save settings. | Do one of the following: - Reboot the Controller. - Restore the backup file that was operating correctly. - Update the controller firmware with the update tool. - Replace the controller SD. - Replace the controller board. - Reinstall Epson RC+ if a virtual controller connection error occurs. - If this error occurs repeatedly, contact us. | - | Reset | |
| 1160 | Failed to acquire settings (MCD). | Do one of the following: - Reboot the Controller. - Restore the backup file that was operating correctly. - Update the controller firmware with the update tool. - Replace the controller SD. - If this error occurs repeatedly, contact us. | - | - | |
| 1161 | Failed to acquire settings (MCD). | Do one of the following: - Reboot the Controller. - Restore the backup file that was operating correctly. - Update the controller firmware with the update tool. - Replace the controller SD. - Reinstall Epson RC+ if a virtual controller connection error occurs. - If this error occurs repeatedly, contact us. | - | - | |
| 1163 | Failed to save settings (MCD). | Do one of the following. - Reboot the Controller. - Restore the backup file that was operating correctly. - Update the controller firmware with the update tool. - Replace the controller SD. - Replace the controller board. - If this error occurs repeatedly, contact us. | - | - | |
| 1165 | Failed to get system settings of MT robot. (MPD) | Correct the issue or update using the MT setup tool. | - | - | |
| 1166 | Failed to get system settings of MT robot. (MPD) | Correct the issue or update using the MT setup tool. | - | - | |
| 1168 | Failed to get system settings of MT robot. (MPD) | Correct the issue or update using the MT setup tool. | - | - | |
| 1170 | Failed to get system settings of MT robot. (MPL) | Do one of the following. - Execute again. - Reboot the Controller. - Update the controller firmware with the update tool. - Replace the controller SD. - Reinstall Epson RC+ if a virtual controller connection error occurs. - If this error occurs repeatedly, contact us. | - | - | |
| 1171 | Failed to get system settings of MT robot. (MPL) | Do one of the following. - Execute again. - Reboot the Controller. - Update the controller firmware with the update tool. - Replace the controller SD. - If this error occurs repeatedly, contact us. | - | - | |
| 1181 | Failed to initialize robot parameters. | Do the following in order. 1. Reboot the Controller. 2. Reconfigure the robot. | - | - | |
| 1182 | Could not restore due to new version of specified backup data. | Do one of the following: - Update the controller firmware with the update tool. - Check the specified backup data. | - | - | |
| 1183 | Could not restore due to new version of specified backup data. | Do one of the following: - Update the controller firmware with the update tool. - Check the specified backup data. | - | - | |
| 1184 | Restore failed. A number of backup data files that exceeds the upper limit was specified. | Do one of the following: - Remove projects in the restore data selection dialog. - Create backup data with a reduced number of project files in the virtual controller, then try again. | - | - | |
| 1185 | Failed to read backup data. | Do one of the following: - Execute again. - Check the backup data when restoring. - When backing up to USB memory, use different USB memory and try again. - Reboot the controller and try again. | - | - | |
| 1186 | Failed to restore controller settings. | Do one of the following: - Check the specified backup data and try again. - Acquire the backup data again. - Reboot the controller and try again. | - | - | |
| 1187 | Failed to backup controller settings. | Do one of the following: - Execute again. - When backing up to USB memory, use different USB memory and try again. - Reboot the controller and try again. - Update the controller firmware with the update tool. - Replace the controller SD. - Reinstall Epson RC+ if a virtual controller connection error occurs. - If this error occurs repeatedly, contact us. | - | - | |
| 1189 | Could not restore due to an unsupported version of the specified backup data. | Do one of the following: - Check the specified backup data. - Update the controller firmware with the update tool. | - | - | |
| 1190 | Failed to restore the specified backup data because this version is not supported. (the backup data is newer) | Do one of the following: - Check the specified backup data. - Update the controller firmware with the update tool. | - | - | |
| 1191 | Failed to restore because the specified backup data does not include SPEL project. | Do one of the following: - Check the specified backup data. - Remove projects from the restore target. | - | - | |
| 1192 | Failed to restore because the number of robots is different. | Do one of the following: - Check the specified backup data. - Connect and configure the necessary robots and try again. | - | - | |
| 1193 | Failed to restore because the information of robots is different. | Do one of the following: - Check the specified backup data. - Configure the necessary additional axis and try again. - Remove calibration data in the restore data selection dialog. - Specify actual controller backup data. | - | - | |
| 1194 | Failed to restore because the specified backup data includes a drive unit. | Check the specified backup data and try again. | - | - | |
| 1195 | Failed to backup controller settings. (mapping) | Do one of the following: - Execute again. - When backing up to USB memory, use different USB memory and try again. - Reboot the controller and try again. | - | - | |
| 1196 | Failed to backup controller settings. | Do one of the following: - Execute again. - When backing up to USB memory, use different USB memory and try again. - Reboot the controller and try again. | - | - | |
| 1197 | Failed to backup controller settings. | Do one of the following: - Execute again. - When backing up to USB memory, use different USB memory and try again. - Reboot the controller and try again. | - | - | |
| 1198 | Failed to restore because the Vision hardware configuration needs to be restored together with the project. | If you selected Vision hardware settings as a restore target, select a project also. | - | - | |
| 1200 | Failed to build SPEL project. (compile) | Do the following in order. 1. Check the error that occurred in the control device status window. 2. Correct the section where the program error occurred. | - | - | |
| 1201 | Failed to build SPEL project. (link) | Do the following: 1. Check the error that occurred in the control device status window. 2. Correct the section where the program error occurred. | - | - | |
| 1250 | The user defined remote output I/O registration name is not defined. | Do one of the following: - Check the user defined remote output I/O settings. - Update the controller firmware with the update tool. | - | - | |
| 1251 | The user defined remote output I/O conditional expression is not defined. | Do one of the following: - Check the user defined remote output I/O settings. - Update the controller firmware with the update tool. | - | - | |
| 1252 | An unsupported robot number was specified. | Do one of the following: - Check the robot connection and settings and try again. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1260 | An unregistered robot was specified. | Do one of the following: - Check the robot registration. - Restore the backup file that was operating correctly. - Update the controller firmware with the update tool. | - | - | |
| 1261 | Failed to set the alarm. (getting scheduled occurrence date) | Do one of the following: - Execute again. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1262 | Failed to set the alarm. | Do one of the following: - Execute again. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1263 | Failed to set the alarm. (alarm number out of range) | Do one of the following: - Execute again. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1264 | Failed to set the alarm. (alarm disabled) | Do one of the following: - Execute again. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1270 | The part feeder type in the PF file and the controller settings are different. | Do one of the following: - Re-register the feeder settings in Epson RC+ - Menu - [Setup] - [System Configuration]. - Synchronize the project or transfer it via restore. | - | Reset | |
| 1271 | Communication with the specified part feeder failed. | Do one of the following: - Check that the Ethernet connection between the part feeder and the Controller is functioning normally (have cables become disconnected, is there a hub failure or a lack of power supply to the hub, etc.). - Check the power supply to the part feeder. - Check that part feeder network settings (IP address, IP mask, port) are correct. | - | - | |
| 1272 | Failed to initialize part feeder output port. | Do one of the following: - Check the Ethernet connection between the part feeder and controller. Specifically, check for cable disconnections, network hub failures, and lack of power supply to the hub. - Check the power supply to the part feeder. - Check that part feeder network settings (IP address, IP mask, port) are correct. | - | - | |
| 1273 | Failed to change part feeder parameters. | Do one of the following: - Check the Ethernet connection between the part feeder and controller. Specifically, check for cable disconnections, hub failures, and lack of power supply to the hub. - Check the power supply to the part feeder. - Check that part feeder network settings (IP address, IP mask, port) are correct. | - | - | |
| 1290 | A system error has occurred. (force monitor number out of allowable range) | Do one of the following: - Reboot the Controller. - Restore the backup file that was operating correctly. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1291 | The force monitor is already used on another device. | Check the connections and force monitor usage status of other PCs and control devices and try again. | - | - | |
| 1292 | Failed to load the Force Guide file. (sequence, object information) | Do one of the following: - Synchronize the project or transfer the project that contains the required force guide files via restore. - Create the necessary force guide file. - Check the force file guide settings in the project. | - | Reset | |
| 1293 | Failed to set the Force Sensor because the specified robot type is joint type or Cartesian type | Specify the robot number for the robot type for which you want to set the Force Sensor. The robot type must be other than joint type or Cartesian coordinate type. | |||
| 1400 | Failed to load the Force Guide file. (file error) | Do one of the following: - Synchronize the project or transfer the project that contains the required force guide files via restore. - Create the necessary force guide file. - Check the force file guide settings in the project. | - | Reset | |
| 1401 | Failed to load the Force Guide file. (file path) | Configure the force guide files again. | - | - | |
| 1402 | Failed to load the Force Guide file. (file open) | Do one of the following: - Synchronize the project or transfer the project that contains the required force guide files via restore. - Create the necessary force guide file. - Check the force file guide settings in the project. | - | Reset | |
| 1403 | Failed to load the Force Guide file. (file open) | Do one of the following: - Synchronize the project or transfer the project that contains the required force guide files via restore. - Create the necessary force guide file. - Check the force file guide settings in the project. | - | - | |
| 1404 | An unsupported value was specified in the force guide sequence number. | Do one of the following: - Synchronize the project or transfer the project that contains the required force guide files via restore. - Create the necessary force guide file. - Check the force file guide settings in the project. | - | - | |
| 1405 | An unsupported value was specified in the force guide object number. | Do one of the following: - Synchronize the project or transfer the project that contains the required force guide files via restore. - Create the necessary force guide file. - Check the force file guide settings in the project. | - | - | |
| 1406 | An unsupported value was specified in the force guide sequence properties. | Do one of the following: - Synchronize the project or transfer the project that contains the required force guide files via restore. - Create the necessary force guide file. - Check the force file guide settings in the project. | - | Reset | |
| 1407 | An unsupported value was specified in the force guide object properties. | Do one of the following: - Synchronize the project or transfer the project that contains the required force guide files via restore. - Create the necessary force guide file. - Check the force file guide settings in the project. | - | - | |
| 1408 | An unsupported value was specified in the force guide object type. | Do one of the following: - Synchronize the project or transfer the project that contains the required force guide files via restore. - Create the necessary force guide file. - Check the force file guide settings in the project. | - | - | |
| 1409 | An unsupported value was specified in the force guide parameters. | Do one of the following: - Synchronize the project or transfer the project that contains the required force guide files via restore. - Create the necessary force guide file. - Check the force file guide settings in the project. | - | - | |
| 1410 | Failed to load the Force Guide file. (unsupported version). | Do one of the following to reset the Controller: - Synchronize the project or transfer the project that contains the required force guide file via restore. - Create the necessary force guide file. - Check the force file guide settings in the project. | - | - | |
| 1411 | An unsupported value was specified in the force guide properties. | Do one of the following: - Synchronize the project or transfer the project that contains the required force guide files via restore. - Create the necessary force guide file. - Check the force file guide settings in the project. | - | - | |
| 1412 | Decision object was set at the top of the force guide sequence. | Do one of the following: - Synchronize the project or transfer the project that contains the required force guide files via restore. - Create the necessary force guide file. - Check the force file guide settings in the project. | - | - | |
| 1413 | Specified Force Guide object as ConditionObject is disabled. | Do one of the following: - Synchronize the project or transfer the project that contains the required force guide files via restore. - Create the necessary force guide file. - Check the force file guide settings in the project. | - | - | |
| 1414 | Failed to load the Part Feeding file. | Do one of the following. - Synchronize the project or transfer the project that contains the required part feeder files via restore. - Configure the necessary part feeder files again and then create the files. - Check the part feeder file settings in the project. | - | Reset | |
| 1420 | Program conversion processing failed. | Do one of the following: - Rebuild the project. - Synchronize the project or transfer it via restore. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1421 | Failed to allocate memory. | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1423 | Program conversion processing failed (conversion file path). | Do one of the following: - Rebuild the project. - Synchronize the project or transfer it via restore. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1424 | Program conversion processing failed (prg file path). | Do one of the following: - Rebuild the project. - Synchronize the project or transfer it via restore. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1425 | Program conversion processing failed (command file path). | Do one of the following: - Rebuild the project. - Synchronize the project or transfer it via restore. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1426 | Program conversion processing failed (conversion file error). | Do one of the following: - Rebuild the project. - Synchronize the project or transfer it via restore. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1427 | Program conversion processing failed (command file error). | Do one of the following: - Rebuild the project. - Synchronize the project or transfer it via restore. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1428 | Program conversion processing failed. | Do one of the following: - Rebuild the project. - Synchronize the project or transfer it via restore. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1429 | Program conversion processing failed (prg file error). | Do one of the following: - Rebuild the project. - Synchronize the project or transfer it via restore. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1501 | Command was not completed within the specified time. | Do one of the following: - Wait and try again. - Check the connection between Epson RC+ and the controller. | 1: Communication timeout 2: Disconnected USB cable 3: USB reception error 4: USB communication stopped | Reset | |
| 1502 | The control device and controller have been disconnected. | Do the following in order. 1. Check the USB or LAN cable connection. 2. If necessary, check the network status. 3. Reconnect on the control device. 4. Reset the Controller. | 1: Communication timeout 2: Disconnected USB cable 3: USB reception error 4: USB communication stopped | Reset | |
| 1503 | The control device and controller have been disconnected during task execution. | Do one of the following: - Check the controller settings and then execute the task. - Check if there are any unnecessary devices connected in addition to the currently connected control device. | - | Reset | |
| 1504 | The remote Ethernet and controller have been disconnected. | Do the following in order. 1. Check the connection between the remote Ethernet device and controller. 2. Reconnect on the control device. 3. Reset the Controller. | - | Reset | |
| 1506 | The TP and controller have been disconnected. | Do the following in order. 1. Check the connection between the TP and controller. 2. Reconnect on the control device. 3. Reset the Controller. | - | Reset | |
| 1510 | Invalid IP Address was specified. | Check the IP address specification and try again. | - | - | |
| 1511 | A configured or scheduled connection on the system was specified. | Do one of the following: - Set a different IP address. - Set a different port number. - Remove unnecessary IP addresses from settings. - Remove unnecessary port numbers from settings. | - | - | |
| 1512 | A gateway address scheduled on the system was specified. | Set a different gateway address. | - | - | |
| 1513 | A global IP address without a connection authentication password or an invalid IP address was specified. | Do one of the following: - Set the connection authentication password and then the IP address. - Use a private IP address. - Check the IP address specification and try again. | - | - | |
| 1514 | The connection destination setting or password is invalid. | Check the connection destination setting and password. | - | - | |
| 1523 | Communication between the vision camera and controller failed (socket handle acquisition). | Reboot the Controller. | - | - | |
| 1524 | Communication between the vision camera and controller failed (connection). | Do one of the following, then try again: - Check the connection between the compact vision and controller. - Check the connection between Epson RC+ and the controller. | - | - | |
| 1526 | Communication between the vision camera and controller failed (transmission). | Do one of the following, then try again: - Check the connection between the compact vision and controller. - Check the connection between Epson RC+ and the controller. | - | - | |
| 1527 | Communication between the vision function and controller failed (server read). | Do one of the following, then try again: - Check the connection between the compact vision and controller. - Check the connection between Epson RC+ and the controller. | - | - | |
| 1528 | Failed to configure vision camera option settings. | Do one of the following, then try again: - Check the settings. - Check the connection between the compact vision and controller. - Check the connection between Epson RC+ and the controller. | - | - | |
| 1529 | Vision communication initialization failed. | Reboot the Controller. | - | - | |
| 1530 | Communication between the vision function and controller failed (server not connected). | Do one of the following, then try again: - Check the connection between the compact vision and controller. - Check the connection between Epson RC+ and the controller. | - | - | |
| 1531 | Communication between the vision camera and controller failed (no available socket). | Do one of the following, then try again: - Check if the number of connected vision devices exceeded the upper limit. - Check the connection between the compact vision and controller. - Check the connection between Epson RC+ and the controller. | - | - | |
| 1532 | Communication between the vision function and controller failed (transmission timeout). | Do one of the following, then try again: - Check the connection between the compact vision and controller. - Check the connection between Epson RC+ and the controller. | - | - | |
| 1533 | Communication between the vision function and controller failed (reception timeout). | Do one of the following, then try again: - Check the connection between the compact vision and controller. - Check the connection between Epson RC+ and the controller. | - | - | |
| 1534 | Communication between the vision function and controller failed. | Do one of the following, then try again: - Check the connection between the compact vision and controller. - Check the connection between Epson RC+ and the controller. | - | - | |
| 1550 | Failed to initialize Ethernet communications. | Do one of the following: - Check the Ethernet cable connection. - Reboot the Controller. | - | - | |
| 1551 | The control device and controller USB have been disconnected. | Do the following in order. 1. Check the USB cable connection. 2. Reconnect on the control device. 3. Reset the Controller. | - | Reset | |
| 1552 | Failed to communicate with TP. | Do one of the following: - Check the connection with TP. - Reboot the Controller. | - | - | |
| 1553 | Failed to communicate with control device. | Check the control device connection and perform the operation again. | - | - | |
| 1555 | Ethernet communication failed (transmission). | Do one of the following: - Check the connection between Epson RC+ and the controller. - If a router is used between the PC and controller, confirm that the DHCP function is disabled. | - | - | |
| 1556 | Ethernet communication failed (reception). | Do one of the following: - Check the connection between Epson RC+ and the controller. - If a router is used between the PC and controller, confirm that the DHCP function is disabled. | - | - | |
| 1557 | Failed to communicate with the control device via USB while a command was executing (transmission). | Do the following in order. 1. Check the USB cable connection. 2. Execute the task or command again. | - | - | |
| 1558 | Failed to communicate with the control device via USB while a command was executing (reception). | Do the following in order. 1. Check the USB cable connection. 2. Execute the task or command again. | - | - | |
| 1559 | A data size that exceeds the communication buffer was specified. | Do one of the following: - Reboot the Controller. - Reboot Epson RC+ if using the RC+ cooperative function. - Please inquire with us if a similar error occurs even after rebooting the controller. | - | - | |
| 1582 | A system error has occurred. (parser - transmission error) | Reset the controller and do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | Reset | |
| 1583 | A system error has occurred. (parser - initialization error) | Reset the controller and do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | Reset | |
| 1584 | A system error has occurred. (parser - connection error) | Reset the controller and do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | Reset | |
| 1585 | A system error has occurred. (parser - invalid parameter) | Reset the controller and do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | Reset | |
| 1586 | A system error has occurred. (parser - busy) | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | Reset Stop task | |
| 1587 | A system error has occurred. (parser - invalid data received) | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | Reset Stop task | |
| 1700 | Failed to initialize TP. | Do one of the following: - Check the connection between controller and TP. - Reboot the Controller. - If this error occurs repeatedly, contact us. | - | - | |
| 1701 | Failed to initialize TP. | Do one of the following: - Check the connection between controller and TP. - Reboot the Controller. - If this error occurs repeatedly, contact us. | - | - | |
| 1702 | Failed to initialize TP. | Do one of the following: - Check the connection between controller and TP. - Reboot the Controller. - If this error occurs repeatedly, contact us. | - | - | |
| 1703 | Failed to load the TP screen data file. | Do one of the following: - Check the connection between controller and TP. - Reboot the Controller. - If this error occurs repeatedly, contact us. | - | - | |
| 1704 | Failed to load the TP screen data file. | Do one of the following: - Check the connection between controller and TP. - Reboot the Controller. - If this error occurs repeatedly, contact us. | - | - | |
| 1706 | Failed to initialize the TP serial port. | Do one of the following: - Check the connection between controller and TP. - Reboot the Controller. - If this error occurs repeatedly, contact us. | - | - | |
| 1708 | Failed to load the key table for TP. | Do one of the following: - Check the connection between controller and TP. - Reboot the Controller. - If this error occurs repeatedly, contact us. | - | - | |
| 1709 | Failed to change the language for TP. | Do one of the following: - Check the connection between controller and TP. - Reboot the Controller. - If this error occurs repeatedly, contact us. | - | - | |
| 1710 | Failed to display the screen for TP. | Do one of the following: - Check the connection between controller and TP. - Reboot the Controller. - If this error occurs repeatedly, contact us. | - | - | |
| 1800 | The specified controller is already connected to a PC or TP4. | Only one Epson RC+ can be connected to the controller at one time. Check the connection between Epson RC+ and the controller. | - | - | |
| 1802 | A command was executed without connecting to the controller. | Check the connection between Epson RC+ and the controller. | - | - | |
| 1803 | PC file access failed due to Epson RC+ cooperative function. | Stop the task and do one of the following: - Check the file path 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. - Check SPEL command drive selection. - Reboot Epson RC+. - Please inquire with us if a similar error occurs even after rebooting the controller. | - | Stop task | |
| 1804 | Failed to allocate memory necessary for executing the cooperative function with Epson RC+. | Stop the task and do one of the following: - Reboot the connected Epson RC+. - Please inquire with us if a similar error occurs even after rebooting the controller. | - | Stop task | |
| 1805 | Connection between the PC and controller failed. | Check that the controller is running and the communication cable is connected. | - | - | |
| 1806 | Connection between the PC and controller failed (Ethernet connection timeout). | Check the connection between Epson RC+ and the controller. | - | - | |
| 1807 | Connection between the PC and controller failed (USB connection timeout). | Check the connection between Epson RC+ and the controller. | - | - | |
| 1808 | Connection between the PC and controller failed (USB port recognition error). | Do one of the following to reset the controller: - - Check the USB cable connection between the controller and Epson RC+. - Reinstall Epson RC+. | - | - | |
| 1809 | Failed to connect to Epson RC+ cooperative function. | Stop the task and do one of the following: - Check the connection between Epson RC+ and the controller. - Reboot Epson RC+. - Reboot the PC Epson RC+ is running on. | - | Stop task | |
| 1810 | Failed to connect to Epson RC+ cooperative function. | Stop the task and do one of the following: - Check the connection between Epson RC+ and the controller. - Reboot Epson RC+. - Reboot the PC Epson RC+ is running on. | - | Stop task | |
| 1812 | The connected controller is not supported. | Do one of the following: - Check the connection between the PC and controller. - Use Epson RC+ 6.0 or earlier. | - | - | |
| 1813 | Connection between Epson RC+ and the controller failed (Ethernet connection type difference). | Do one of the following: - Check the connection between the PC and controller. - Check the connection destination setting controller series. | - | - | |
| 1814 | The USB port is not ready. | Do one of the following: - Wait a while and connect again. - Check that the controller is running and the communication cable is connected. | - | - | |
| 1815 | Cannot recognize USB cable connection. | Check that the controller is running and the USB cable is connected. | - | - | |
| 1851 | An unsupported command was executed. | Do one of the following: - Review the contents of the SPEL program. - Rebuild the project. | - | - | |
| 1852 | A system error has occurred. | Do one of the following. - Reboot Epson RC+. - Reboot the PC. - Reinstall Epson RC+. | - | - | |
| 1861 | Failed to initialize Epson RC+. (SimulatorMNG) | Do one of the following: - Reboot Epson RC+. - Reboot the PC. - Reinstall Epson RC+. | - | - | |
| 1862 | Failed to initialize Epson RC+. (WBProxy) | Do one of the following: - Reboot Epson RC+. - Reboot the PC. - Reinstall Epson RC+. | - | - | |
| 1863 | Invalid parameters. | Do one of the following: - Reboot Epson RC+. - Reboot the PC. - Reinstall Epson RC+. | - | - | |
| 1864 | Virtual controller does not exist. | Reinstall Epson RC+. | - | - | |
| 1865 | Failed to start virtual controller. | Do one of the following: - Retry after a while. - Reboot the PC. | - | - | |
| 1866 | Failed to terminate virtual controller. | Reboot the PC. | - | - | |
| 1867 | This operation can only be executed in dry run mode. | Enable dry run mode. | - | - | |
| 1868 | Directory does not exist. | Failed to install Epson RC+. Reinstall Epson RC+. | - | - | |
| 1872 | Failed to acquire the actual controller information file. | Do one of the following: - Recreate the connection destination. - Reinstall Epson RC+. | - | - | |
| 1873 | Failed to acquire the virtual controller information file. | Do one of the following: - Recreate the connection destination. - Reinstall Epson RC+. | - | - | |
| 1874 | Failed to add virtual controller. | Failed to install Epson RC+. Reinstall Epson RC+. | - | - | |
| 1875 | Failed to register simulator object. | Do one of the following: - Recreate the virtual controller connection destination. - Reinstall Epson RC+. | - | - | |
| 1876 | Failed to read simulator object. | Do one of the following: - Recreate the virtual controller connection destination. - Reinstall Epson RC+. | - | - | |
| 1877 | Failed to delete simulator object. | Do one of the following: - Recreate the virtual controller connection destination. - Reinstall Epson RC+. | - | - | |
| 1878 | Failed to change simulator object. | Do one of the following: - Recreate the virtual controller connection destination. - Reinstall Epson RC+. | - | - | |
| 1879 | Other virtual controllers are running. | Other virtual controllers are being used on another Epson RC+. End Epson RC+ and then reboot it. | - | - | |
| 1880 | Cannot execute during controller reboot. | Reboot the controller, wait, and try again. | - | - | |
| 1901 | This operation is not supported with the current settings. | Do one of the following: - Check the command. - Switch to the virtual or actual controller and then execute. - Check the control device and then execute. - Check the operation. - Update the controller firmware with the update tool. - Reinstall Epson RC+. - If this error occurs repeatedly, contact us. | - | Reset | |
| 1902 | A system error has occurred. (unsupported parameter) | Do one of the following: - Rebuild the project. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - | |
| 1903 | A system error has occurred. | Do one of the following. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | Reset | |
| 1904 | Failed to restore due to the large size of the backup data. | Do one of the following: - Check the specified backup data. - Delete unnecessary files from the specified backup data project folder. - Select something other than the project files and try again. | - | - | |
| 1905 | System error notification. | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - Reinstall Epson RC+. - If this error occurs repeatedly, contact us. | - | Reboot | |
| 1906 | The upgrade license deadline does not match. | Contact your supplier and update the upgrade license. | - | - | |
| 1907 | Failed to initialize controller internal communication. | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - Reinstall Epson RC+. - If this error occurs repeatedly, contact us. | - | Reboot | |
| 1908 | Controller internal communication failed. | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - Reinstall Epson RC+. - If this error occurs repeatedly, contact us. | - | Reboot | |
| 1910 | Failed to save reboot log. | Settings may have been reset, so check before performing the operation. | - | - | |
| 1920 | USB connection failed. | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | - |