Code Number 2000 ~
| No. | Message | Countermeasure | Note 1 | Note 2 | Error Solution |
|---|---|---|---|---|---|
| 2000 | An unsupported SPEL command was specified (normal command). | Stop the task and do one of the following: - Rebuild the project. - Check the SPEL command usage. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for command support information and correction instructions. | Stop task | ||
| 2001 | An unsupported SPEL command was specified (motion command). | Stop the task and do one of the following: - Rebuild the project. - Check the SPEL command usage. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for command support information and correction instructions. | Stop task | ||
| 2003 | An unsupported process was found in the specified SPEL project (function argument). | Stop the task and do one of the following: - Rebuild the project. - Check the SPEL command specifications. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2004 | An unsupported process was found in the specified SPEL project (function return value). | Stop the task and do one of the following: - Rebuild the project. - Check the SPEL command specifications. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2005 | Unsupported event conditions were found in the specified SPEL project. | Stop the task and do one of the following: - Rebuild the project. - Check the SPEL command specifications. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2006 | An unsupported SPEL command was specified (I/O command). | Stop the task and check the SPEL command usage. 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 | ||
| 2007 | An event condition other than Wait that is not supported was specified. | Stop the task and do one of the following: - Rebuild the project. - Check the SPEL command specifications. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2009 | The specified task number was called in an unexpected execution order. | Stop the task and do one of the following: - Check the SPEL command execution order. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2010 | An unsupported SPEL command was specified (intermediate code error). | Stop the task and do one of the following: - Rebuild the project. - Check the SPEL command usage method. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. - Synchronize the project or transfer it via restore. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2011 | An unsupported format was specified (function argument count). | Stop the task and do one of the following: - Check the controller firmware version and use a supported format. See the reference manual for support information and correction instructions. - 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. | Stop task | ||
| 2012 | An unsupported format was specified (command argument count). | Stop the task and do one of the following: - Check the controller firmware version and use a supported format. See the reference manual for support information and correction instructions. - 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. | Stop task | ||
| 2013 | An unsupported format was specified (unknown code). | Stop the task and do one of the following: - Check the controller firmware version and use a supported format. See the reference manual for support information and correction instructions. - 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. | Stop task | ||
| 2014 | An unsupported format was specified (unknown code variable type). | Stop the task and do one of the following: - Check the controller firmware version and use a supported format. See the reference manual for support information and correction instructions. - 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. | Stop task | ||
| 2015 | An invalid SPEL project was specified (string type). | Stop the task and do one of the following: - Check the controller firmware version and use a supported format. See the reference manual for support information and correction instructions. - 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. | Stop task | ||
| 2016 | An invalid SPEL project was specified (variable type). | Stop the task and do one of the following: - Check the controller firmware version and use a supported format. See the reference manual for support information and correction instructions. - 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. | Stop task | ||
| 2017 | The necessary parameter was not specified. | Stop the task and do one of the following: - Check the parameter specified in the SPEL command. See the reference manual for correction instructions. - 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. | Stop task | ||
| 2018 | An invalid SPEL project was specified (variable size error). | Stop the task and do one of the following: - Check the controller firmware version and use a supported format. See the reference manual for support information and correction instructions. - 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. | Stop task | ||
| 2019 | An invalid SPEL project was specified (waiting on global variable). | Stop the task and 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. | Stop task | ||
| 2020 | A function call or local variable definition occurred that would exceed the upper limit of the number of stack tables. | Stop the task and do one of the following: - Check whether the nested structure is called infinitely. - Reduce the nested structure calls depth. | Stop task | ||
| 2021 | A function call or local variable definition occurred that would exceed the upper limit of the stack table area size. | Stop the task, and when using many local variables, especially string types, replace them with global variables. | Stop task | ||
| 2022 | An unsupported format was specified (stack mismatch). | Stop the task and do one of the following: - Check the controller firmware version and use a supported format. See the reference manual for support information and correction instructions. - 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. | Stop task | ||
| 2023 | An invalid SPEL project was specified (unknown tag). | Stop the task and do one of the following: - Check the controller firmware version and use a supported format. See the reference manual for support information and correction instructions. - 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. | Stop task | ||
| 2024 | The local variable in the child task exceeded the size that can be stored. | Stop the task and check the local variable used in the SPEL program. For details on the local variable, see the user's guide. | Stop task | ||
| 2025 | An unsupported format was specified (invalid function call). | Stop the task and do one of the following: - Check the controller firmware version and then check the SPEL function. See the reference manual for correction instructions. - 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. | Stop task | ||
| 2031 | Failed to initialize controller. | Do one of the following to 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. | Reboot | ||
| 2032 | A system error has occurred. (task number compliance) | Stop the task and 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. | Stop task | ||
| 2033 | Too many errors have occurred. | Remedy the error in the system history. | - | ||
| 2040 | Failed to initialize controller. (thread creation error) | 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. | - | ||
| 2041 | Failed to initialize controller. (thread creation timeout) | Reboot the Controller. | - | ||
| 2044 | Failed to execute task. (daemon process wait timeout) | Stop the task and do one of the following: - Stop the task and try again. - Reboot the Controller. | Stop task | ||
| 2045 | Failed to execute task. (task continuation wait timeout) | Stop the task and do one of the following: - Stop the task and try again. - Reboot the Controller. | Stop task | ||
| 2046 | Failed to execute task. (task abort wait timeout) | Stop the task and do one of the following: - Stop the task and try again. - Reboot the Controller. | Stop task | ||
| 2047 | Failed to execute task. (task start wait timeout) | Stop the task and do one of the following: - Stop the task and try again. - Reboot the Controller. | Stop task | ||
| 2050 | An object file that exceeds the upper limit size was specified. | Do the following in order. 1. Check the program and reduce the number of rows, etc. 2. Rebuild the project. | - | ||
| 2051 | Task running. Cannot change SPEL project. | Do one of the following: - Stop the task and try again. - Reboot the Controller. | Reset | ||
| 2052 | Failed to allocate memory (execution file). | 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. | Reboot | ||
| 2053 | SPEL project updating. Operation failed. | Wait and try again. | Stop task | ||
| 2054 | Controller and PC SPEL project not synchronized (function ID). | Do one of the following: - Synchronize the project. - Rebuild the project. | Stop task | ||
| 2055 | Controller and PC SPEL project not synchronized (local variable ID). | Do one of the following: - Synchronize the project. - Rebuild the project. | - | ||
| 2056 | Controller and PC SPEL project not synchronized (global variable ID). | Do one of the following: - Synchronize the project. - Rebuild the project. | - | ||
| 2057 | Controller and PC SPEL project not synchronized (global preserve variable ID). | Do one of the following: - Synchronize the project. - Rebuild the project. | - | ||
| 2058 | Failed to update SPEL project (variable size 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. | - | ||
| 2059 | The global variable in the specified SPEL project exceeds the size that can be stored. | Do one of the following to reset the Controller: - Check the global variable used in the SPEL program. For details on the global variable, see the user's guide. - Synchronize the project or transfer the project that was operating correctly via restore. | Reset | ||
| 2070 | Failed to initialize controller (SRAM mapping error). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - Replace the MAIN board. - If this error occurs repeatedly, contact us. | Reset Reboot | ||
| 2071 | Global preserve variable in use. Cannot update SPEL project. | Do one of the following to reset the Controller: - Check if the task has been stopped, then wait and try again. - Synchronize the project or transfer the project that was operating correctly via restore. | Reset | ||
| 2072 | The global preserve variable exceeded the size that can be stored. | Stop the task and check the global preserve variable used in the SPEL program. For details on the global preserve variable, see the user's guide. | Maximum size | The size you attempted to use | Stop task Reset |
| 2073 | Failed to update SPEL project (global preserve variable cleared). | Do one of the following: - Reset the Controller and try again. - Reboot the Controller. - 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. | Reset | ||
| 2074 | Failed to allocate memory (global preserve variable). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2100 | Failed to acquire 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. | - | ||
| 2101 | Failed to initialize controller (duplicate initialization). | 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. | - | ||
| 2102 | Failed to initialize controller (MNG). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2103 | Failed to initialize controller (internal event creation). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2104 | Failed to initialize controller (priority setting). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2105 | Failed to initialize controller (stack size setting). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2107 | Failed to initialize controller (interrupt process start). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2110 | 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. | Reboot | ||
| 2111 | Failed to initialize controller (motion). | 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. | - | ||
| 2115 | Fieldbus board count that exceeds the upper limit recognized. | Check the fieldbus board connection and reboot. | - | ||
| 2116 | Failed to initialize fieldbus (fieldbus). | Do one of the following: - Reboot the Controller. - Check the fieldbus board. - Replace the fieldbus board. | - | ||
| 2118 | Failed to initialize controller (motion open). | Do one of the following to 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. | Reboot | ||
| 2120 | Failed to allocate memory (system). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2121 | Failed to allocate memory (execution file). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Reboot | ||
| 2122 | Failed to allocate memory (robot). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Reboot | ||
| 2123 | Failed to allocate memory (event). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2124 | An unsupported fieldbus module was detected. | Do one of the following to reboot the controller. - Remove the connected fieldbus module. - Connect a supported fieldbus module. | Reboot | ||
| 2130 | 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. | - | ||
| 2131 | Failed to acquire settings (MCD mapping). | 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. | - | ||
| 2150 | Task execution failed. (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. | - | ||
| 2151 | Task execution failed. (another task is running) | 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. | - | ||
| 2152 | Task execution failed. (abnormal object file size) | 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. | - | ||
| 2153 | Jog operation failed. (jog parameter error) | 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. | - | ||
| 2154 | Jog operation failed. (during jog operation) | 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. | - | ||
| 2155 | Jog operation failed. (cannot be executed) | 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. | - | ||
| 2156 | Jog operation failed. (not set) | 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. | - | ||
| 2157 | Jog operation failed. (jog parameters cannot be changed) | 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. | - | ||
| 2158 | Failed to allocate memory. (for break point) | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2159 | An attempt was made to set a number of break points exceeding the upper limit. | Reduce unnecessary break points. | - | ||
| 2160 | Failed to get the function ID. | 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. | - | ||
| 2161 | Failed to get the local variable. | 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. | - | ||
| 2162 | The local variable exceeded the size that can be stored. | Do one of the following: - Check the size of the specified local variable. - Check the local variable used in the SPEL project. For details on the local variable, see the user's guide. | - | ||
| 2163 | A command for a paused task was specified. | Pause the task using one of the following methods and try again: - Set break points. - Execute SPEL command Halt. - Pause using the Epson RC+ execution window or the task manager. | - | ||
| 2164 | Failed to acquire the global variable. | Do one of the following: - Execute again. - Check the global variable used in the SPEL project. For details on the global variable, see the user's guide. - Reboot the Controller. - Rebuild the project. - Synchronize the project or transfer it via restore. | - | ||
| 2165 | The global variable exceeded the size that can be stored. | Do one of the following: - Review the size of the specified global variable. - Check the global variable used in the SPEL project. For details on the global variable, see the user's guide. | - | ||
| 2166 | Failed to acquire the global preserve variable. | Do one of the following: - Execute again. - Check the global preserve variable used in the SPEL project. For details on the global preserve variable, see the user's guide. - Reboot the Controller. - Rebuild the project. - Synchronize the project or transfer it via restore. | - | ||
| 2167 | The global preserve variable exceeded the size that can be stored. | Do one of the following: - Check the size of the specified global preserve variable. - Check the global preserve variable used in the SPEL project. For details on the global preserve variable, see the user's guide. | - | ||
| 2168 | Failed to initialize controller. Cannot execute (SRAM mapping 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 | ||
| 2169 | Failed to load SPEL project. (clear the Global Preserve variable) | Reset the controller and do one of the following: - Synchronize the project. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Reset | ||
| 2170 | A string that exceeds the upper limit length was detected. | Check the size of the string variable. | - | ||
| 2171 | Task cannot be executed due to voltage drop detected. | Cannot execute after low voltage was detected. Do the following in order. 1. Check the controller power status. 2. Reboot the Controller. | Reboot | ||
| 2172 | Remote I/O initialization failed. Cannot execute (duplicate initialization). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2175 | Cannot configure remote I/O. | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2176 | An error occurred during remote I/O event standby. | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2177 | 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. | - | ||
| 2178 | Failed to restore controller settings. | Do one of the following: - Execute again. - Acquire the backup data again. - Reboot the controller and try again. | - | ||
| 2181 | A task other than an RC+ API was specified. | Do one of the following: - Set the number of RC+ API tasks. - Specify the RC+ API tasks and try again. | - | ||
| 2190 | Cue data was specified in the expression for a point that does not support cue data. | Stop the task and check the parameter data type 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 | ||
| 2191 | Cannot execute AbortMotion because robot task is not running. | AbortMotion can only be used when operating the robot from a program. Execute the command from the SPEL program. | Stop task | ||
| 2192 | The specified task has already ended (AbortMotion). | Stop the task and check the SPEL command execution order. 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 | ||
| 2193 | An attempt was made to execute Recover without executing the necessary AbortMotion command. | Execute AbortMotion in advance to execute Recover WithoutMove. Stop the task and check the SPEL command execution order. 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 | ||
| 2194 | Conveyor setting error. | Stop the task and do one of the following: - A service representative will confirm that conveyor and encoder settings are correct. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2195 | Conveyor setting error. | Stop the task and do one of the following: - A service representative will confirm that conveyor and encoder settings are correct. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2196 | An unsupported parameter was specified in the conveyor number. | 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 | ||
| 2197 | A parameter that cannot be executed during conveyor tracking was specified. | Stop the task and do one of the following: - Delete LJM. - An unsupported format was specified for conveyor tracking in Arc and Arc 3. Check the format. - 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 | ||
| 2200 | An action command cannot be executed while another task is executing an action command. | Stop the task and check the SPEL command usage. 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 | ||
| 2201 | Robot not registered. | Stop the task and do one of the following: - Check the robot configuration. - Restore the backup file that was operating correctly. | Stop task | ||
| 2202 | A system error has occurred. (Motion control module status failure) | Reset the controller and do one of the following: - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Reset | ||
| 2203 | Specified Local number 0 which cannot be cleared. | Local number 0 cannot be cleared. 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 | ||
| 2204 | Specified the Arm number that is in use. | The Arm number cannot be cleared while in use. Stop the task and do one of the following: - Select an Arm number other than the one you want to specify. - Check the Arm 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. | Arm number you attempted to clear. | Stop task | |
| 2205 | Specified Arm number 0 which cannot be cleared. | Arm number 0 cannot be cleared. 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 | ||
| 2206 | Specified the Tool number that is in use. | Tool number cannot be cleared while in use. Stop the task and do one of the following: - Select a Tool number other than the one you want to specify. - Check the Tool 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. | Tool number you attempted to clear. | Stop task | |
| 2207 | Specified Tool number 0 which cannot be cleared. | Tool number 0 cannot be cleared. 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 | ||
| 2208 | Specified ECP number 0 which cannot be cleared. | You cannot clear ECP number '0'. 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 | ||
| 2209 | Specified the ECP (external control point) number that is in use. | ECP number cannot be cleared while in use. Stop the task and do one of the following: - Select an ECP (external control point) number other than the one you want to specify. - Check the ECP (external control point) 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. | The ECP number you attempted to clear | Stop task | |
| 2210 | Specified parameter 0 which is out of range for the Local number, | The command processing Local cannot specify Local number 0. 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 | ||
| 2211 | Specified VRT number 0 which cannot be cleared. | You cannot clear VRT number '0'. 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 | ||
| 2212 | Specified the VRT number that is in use. | VRT number cannot be cleared while in use. Stop the task and do one of the following: - Select a VRT number other than the one you want to specify. - Check the VRT 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. | The VRT number you attempted to clear | Stop task | |
| 2214 | An out-of-range value was specified for the VRT number. | You can choose 1 to 15 for a VRT number. 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 | ||
| 2215 | Parameters are not defined in the specified VRT number. | 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 | ||
| 2216 | An unsupported parameter was specified in the BOX number. | Available Box numbers are from 1 to 15. Do one of the following: - 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. - Restore the backup file that was operating correctly. - If this error occurs repeatedly, contact us. | Reset | ||
| 2217 | An undefined Box number was specified. | Stop the task and do one of the following: - Configure the required Box number. - Check the parameter or execution 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 | ||
| 2218 | An unsupported parameter was specified in the Plane number. | Available Box numbers are from 1 to 15. Do one of the following: - 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. - Restore the backup file that was operating correctly. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task Reset | ||
| 2219 | An undefined Plane number was specified. | Stop the task and do one of the following: - Configure the required Plane number. - Check the parameter or execution 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 | ||
| 2220 | Any Robot is not registered. | Reset the controller and do one of the following: - Check the robot configuration. - Restore the backup file that was operating correctly. | Stop task Reset | ||
| 2221 | Failed to save robot parameter setting. | Reset the controller and do one of the following: - Reboot the controller and try again. - Restore the backup data that includes the same robot parameters. - Check the parameters in the Epson RC+ robot manager and configure the settings again. | Stop task Reset | ||
| 2222 | An undefined Local number was specified. | Stop the task and do one of the following: - Configure the required Local number. - Check the parameter or execution 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. | Specified Local number | Stop task | |
| 2223 | An unsupported parameter was specified in the Local number. | You can choose 1 to 15 for a Local number. Do one of the following: - 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. - Restore the backup file that was operating correctly. - If this error occurs repeatedly, contact us. | Specified Local number | Stop task Reset | |
| 2225 | Calibration reference orientation (CalPls) has not been defined. | Stop the task and do one of the following: - Configure CalPls. - Check the parameter or execution 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 | ||
| 2226 | An unsupported parameter was specified in the Arm number. | You can choose 0 to 3 for an Arm number. According to the command, 0 is not available. Do one of the following: - 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. - If this error occurs repeatedly, contact us. | Specified Arm number | Stop task Reset | |
| 2227 | Failed to acquire Arm settings. | Reset the controller and do one of the following: - Reconfigure the Arm settings. - 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. | Specified Arm number | Reset | |
| 2228 | Standby orientation (Home position) has not been defined. | Stop the task and do one of the following: - Set the Home position (standby orientation). - Check the parameter or execution 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 | ||
| 2229 | An unsupported parameter was specified in the Tool number. | You can choose 0 to 3 for a Tool number. According to the command, 0 is not available. Do one of the following: - 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. - Restore the backup file that was operating correctly. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Specified Tool number | Reset | |
| 2230 | An undefined Tool number was specified. | Stop the task and do one of the following: - Configure the required Tool number. - Check the parameter or execution 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. - Restore the backup file that was operating correctly. - If this error occurs repeatedly, contact us. | Specified Tool number | Reset | |
| 2231 | An unsupported parameter was specified in the ECP number. | Available Tool number is from 0 to 15. According to the command, 0 is not available. Do one of the following: - 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. - Restore the backup file that was operating correctly. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | The specified ECP number | Stop task Reset | |
| 2232 | An unidentified ECP (external control point) number was specified. | Stop the task and do one of the following: - Configure the required ECP (external control point) number. - Check the parameter or execution 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. | The specified ECP number | Stop task | |
| 2233 | An axis for command execution has not been specified. | Stop the task, specify the command execution target, and try again. | Stop task | ||
| 2234 | The encoder cannot be reset because the motor mode is on. | Stop the task and do one of the following: - Turn the motor power off and then execute the command. - Check the command to execute. | Stop task | ||
| 2235 | XYLim is not defined. | Stop the task and do one of the following: - Configure XYLim. - Check the parameter or execution 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 | ||
| 2236 | Failed to save robot parameter setting. (PRM - motion settings) | Reset the controller and do one of the following: - Reboot the controller and try again. - Restore the backup data that includes the same robot parameters. - Check the parameters in the Epson RC+ robot manager and configure the settings again. | Reset | ||
| 2237 | An unsupported parameter was specified in the Pallet number. | Available Pallet numbers are from 0 to 15. Do one of the following: - 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. - Restore the backup file that was operating correctly. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task Reset | ||
| 2238 | Pallet is not defined. | Stop the task and do one of the following: - Configure the necessary Pallet. - Check the parameter or execution 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 | ||
| 2240 | A subscript that exceeds the array count definition was specified in the array variable. | Stop the task and check the array variable included in the SPEL command parameters. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | The dimensions exceeding the definition | The specified subscript | Stop task |
| 2241 | The number of dimensions specified in the array variable definition or command specification is different. | Stop the task and check the array variable dimension quantity 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 | ||
| 2242 | Division by 0 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 | ||
| 2243 | Maximum variable value exceeded. | Stop the task and match the parameter data to the data type 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 | ||
| 2244 | Minimum variable value exceeded. | Stop the task and match the parameter data to the data type 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 | ||
| 2245 | A floating point not supported by the command was specified. | This command cannot be executed for Real or DoubleE type. 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 | ||
| 2246 | Cannot calculate the specified value using the Tan 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. | Specified value | Stop task | |
| 2247 | Specified array subscript is less than 0. | Stop the task and check the array variable element quantity 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. | Specified value | Stop task | |
| 2248 | Non-array variables specified in Redim. | 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 | ||
| 2249 | A non-single dimension array was specified as Preserve in Redim. | A non-single dimension array was specified as Preserve in Redim. Stop the task and check the array variable dimension quantity 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 | ||
| 2250 | An unsupported array variable was specified. | Stop the task and check the array variable data type and element quantity 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 | ||
| 2251 | Failed to allocate memory for the element quantity specified in Redim. | Reduce the number of subscripts to be specified for Redim. Perform Redim modestly. Stop the task and check the element quantity 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 | ||
| 2252 | Failed to allocate memory for the element quantity specified in ByRef. | Reduce the array element quantity to be seen by ByRef. Stop the task and check the element quantity 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 | ||
| 2253 | Characters and numerical values were compared. | Check whether the string type and the numeric data type are not compared. Stop the task and check the parameter data type 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 | ||
| 2254 | Data quantity that exceeded the array variable element quantity was specified. | Check the number of array's subscripts and data. Stop the task and check the array variable element quantity and data quantity 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. | The number of array subscripts | The number of data to be referred or updated | Stop task |
| 2255 | A variable that exceeds the upper limit was specified. | The value that exceeds the range of Double type is 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. Also check the user's guide for variable definitions. | Stop task | ||
| 2256 | An unsupported element quantity was specified in the array variable. | Reduce the number of subscripts to be specified. Stop the task and check the array variable element quantity 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 | ||
| 2257 | An Int64 or UInt64 type variable was specified (counter variable in a For statement). | Int64 variable or UInt64 variable cannot be 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 | ||
| 2260 | An unsupported parameter was specified in the task number. | Do one of the following: - 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. - If this error occurs repeatedly, contact us. | The specified task number | Stop task | |
| 2261 | The specified task number cannot be found. | 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. | The specified task number | Stop task | |
| 2262 | An unregistered robot was specified. | The available Robot number is 1. Stop the task and do one of the following: - Configure the necessary robot. - 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. | The specified robot number | Stop task | |
| 2263 | An unsupported parameter was specified in the port number or device number. | 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. | The specified output number | Stop task | |
| 2264 | An unsupported parameter was specified for the argument. Note 1: Value. Note 2: Position. | 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. Basic: "SPEL + Language Reference" Vision: "Vision Guide Properties & Result Reference" Force: "Force Guide SPEL+ Language Reference" GUI Builder: "GUI Builder GUI Builder Reference" Part feeder: "Part Feeding Introduction & Hardware (common) & Software - Software - Part Feeding SPEL+ Command Reference" | The Added value | What number argument? | Stop task |
| 2265 | An unsupported parameter was specified in the joint number. | Available Joint number is from 1 to 9. 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. | The specified joint number | Stop task | |
| 2266 | An unsupported parameter was specified in the wait time. | Available wait time is from 0 to 2147483. 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. | The specified wait time | Stop task | |
| 2267 | An unsupported parameter was specified in the timer number. | Available timer number is from 0 to 15. 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. | The specified timer number | Stop task | |
| 2268 | An unsupported parameter was specified in the trap number. | Available trap number is from 1 to 4. 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. | Specified trap number | Stop task | |
| 2269 | An unsupported parameter was specified in the language ID. | 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. | The specified language ID | Stop task | |
| 2270 | Stack quantity parallel processing that exceeds the upper limit was specified. | Available D parameter value is from 0 to 100. Stop the task and correct the program to reduce the parallel processing stack quantity. | The specified D parameter value | Stop task | |
| 2271 | An unsupported parameter was specified in the Arch number. | You can choose 0 to 7 for an Arch number. 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. | Specified Arch number | Stop task | |
| 2272 | An unsupported value was specified in the device number. | 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. | Specified device number | Stop task | |
| 2273 | An unsupported data size was specified. | Available output data value is from 0 to 255. Stop the task and check the parameter that specifies data 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. | Output data | What number byte data is out of range? | Stop task |
| 2274 | An out-of-range value was specified for the Asin function (-1 to 1). | You can choose -1 to 1 for the Asin 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. | Stop task | ||
| 2275 | An out-of-range value was specified for the Acos function (-1 to 1). | You can choose -1 to 1 for the Acos 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. | Stop task | ||
| 2276 | An out-of-range value was passed to the Sqr function (a negative number). | You can choose a positive number for the Sqr 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. | Stop task | ||
| 2277 | An out-of-range value was passed to the Randomize function (a negative number). | 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 | ||
| 2278 | An unsupported parameter was specified in either Sin, Cos, or Tan. | 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 | ||
| 2280 | A timeout occurred with the TMOut command (Wait). | Stop the task and do one of the following: - In case of unexpected timeouts, check the parameter specified in the TMOut command. - Execute again. | Timeout period | Stop task | |
| 2281 | A timeout occurred with the TMOut command (WaitSig/SynkLock). | Stop the task and do one of the following: - In case of unexpected timeouts, check the parameter specified in the TMOut command. - Execute again. | Signal number | Timeout period | Stop task |
| 2282 | A timeout occurred with the TMOut command (WaitNet). | Stop the task and do one of the following: - In case of unexpected timeouts, check the parameter specified in the TMOut command. - Execute again. | Port number | Timeout period | Stop task |
| 2283 | A timeout occurred while configuring the display device with dispdev. | Stop the task and 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. | Stop task | ||
| 2285 | Cannot clear the specified arm calibration number because it is in use. | Stop the task, disable arm length calibration, and try again. | The arm length calibration number you tried to clear | Stop task | |
| 2286 | Specified arm calibration number 0 which cannot be cleared. | Cannot clear the arm length calibration number "0". 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 | ||
| 2287 | An out-of-range value was specified for the arm length correction number. | Reset the controller and 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. | Specified arm length calibration number | Reset | |
| 2288 | An undefined arm length correction number was specified. | Do one of the following: - Configure the required arm length calibration number. - Check the parameter or execution 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. - Reset the controller and check the arm length calibration settings. - If this error occurs repeatedly, contact us. | Specified arm length calibration number | Reset | |
| 2290 | Could not execute motion command (Find, Sense, Till, Parallel Processing, Force Monitor). | Cannot execute the motion command after using the user function in the motion command. Stop the task and check the SPEL command execution order. 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 | ||
| 2291 | A command that cannot be executed during multitasking was specified (OnErr). | Cannot execute OnErr in the motion command when using user function in the motion command. Stop the task and check the SPEL command execution order. 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 | ||
| 2292 | An I/O command was specified without specifying Forced while the safeguard was enabled (safety fence open). | Stop the task and do one of the following: - Disable the safeguard (safety fence closed) and then execute the task. - Add Forced to the execution parameter. | Stop task | ||
| 2293 | An I/O command was specified without specifying Forced during an emergency stop. | Stop the task and do one of the following: - Clear the emergency stop status and execute the command. - Add Forced to the execution parameter. | Stop task | ||
| 2294 | An I/O command was specified without specifying Forced during an error. | Stop the task and do one of the following: - Do the following in order. 1. Check the error in the system history. 2. Remedy the error. 3. Execute again. - Add Forced to the execution parameter for the command that corresponds to the function name and row number in the system history. | Stop task | ||
| 2295 | An unsupported command was specified in the NoEmgAbort task and background task. | Stop the task and check the SPEL command call. 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 | ||
| 2297 | An I/O command was specified without specifying Forced in TEACH mode. | Stop the task and do one of the following: - Execute in any mode other than TEACH. - Add Forced to the execution parameter for the command that corresponds to the function name and row number in the system history. | Stop task | ||
| 2298 | Continuation from the Trap SGClose processing task is not possible. | You cannot execute Cont and Recover statements in the Trap SGClose processing task. Stop the task and check the SPEL command execution order. 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 | ||
| 2299 | Specified an advanced task control command without controller preference settings. | Stop the task and do one of the following: - Enable the advanced task control command in controller settings. - Stop the task and check the SPEL command call. 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 | ||
| 2300 | An action command cannot be executed while another task is executing an action command. | Stop the task and check the SPEL command usage. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Task number during robot use | Stop task | |
| 2301 | Cannot execute the motion command because the enable switch cannot be correctly recognized, or the mode was changed while holding it. | Stop the task, re-grip the enable switch, and try again. | Stop task | ||
| 2302 | This command cannot be executed in a Trap Call subroutine. | Another function cannot be called from the function called by Trap Call. Stop the task and check the SPEL command execution order. 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 | ||
| 2303 | An unsupported command was specified in parallel processing (Call). | Stop the task and make sure that parallel processing or the corresponding SPEL command is not being used. 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 | ||
| 2304 | An unsupported command was specified in parallel processing (Xqt). | Stop the task and make sure that parallel processing or the corresponding SPEL command is not being used. 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 | ||
| 2305 | Cannot execute a Call statement from the command window. | Cannot execute a Call statement from the command window. Execute the command from the SPEL program. | Stop task | ||
| 2306 | Cannot execute an Xqt statement from the task started by Trap Xqt. | Cannot execute an Xqt statement from the task started by Trap Xqt. Stop the task and check the SPEL command usage. 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 | ||
| 2307 | A command that cannot be executed was specified while a task was running. | Stop the task and check the SPEL command usage. 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 | ||
| 2308 | Cannot turn on the motor because of a critical error. | Do one of the following: - Check errors that occurred before this error in the system history. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2309 | Cannot execute a motion command while the safeguard is open. | Stop the task, disable the safeguard (safety fence closed), and try again. | Stop task | ||
| 2310 | The operation command cannot be executed before the return operation. | Do one of the following, then try again: - Implement the recovery operation. - Implement continued execution. The recovery operation is implemented according to settings. - Stop the task. | Stop task | ||
| 2311 | The operation command cannot be executed during the return operation. | Do one of the following, then try again: - Wait for the recovery operation or continued execution to complete. - Stop the task. | Stop task | ||
| 2312 | Tasks cannot be executed during an emergency stop. | Stop the task, clear the emergency stop, status and execute the command. | Stop task | ||
| 2313 | Cannot continue execution immediately after opening the safeguard. | Do the following in order. Or stop the task. 1. Disable the safeguard (safety fence closed). 2. Wait at least 1.5 seconds. 3. Execute again. | Stop task | ||
| 2314 | Cannot continue execution while the safeguard is open. | Stop the task, disable the safeguard (safety fence closed), and try again. | Stop task | ||
| 2315 | No need to issue a continue command since the return operation is in progress. | Do one of the following, then try again: - Wait for the recovery operation or continued execution to complete. - Stop the task. | Stop task | ||
| 2316 | Cannot execute Continue because an error has occurred. | Stop the task and do the following in order: 1. Check the error in the system history. 2. Remedy the error. 3. Execute again. | Stop task | ||
| 2317 | Cannot execute the task because an error has occurred. | Stop the task and do the following in order: 1. Check the error in the system history. 2. Remedy the error. 3. Execute again. | Stop task | ||
| 2318 | Cannot execute the motion command because an error has occurred. | Stop the task and do the following in order: 1. Check the error in the system history. 2. Remedy the error. 3. Execute again. | Stop task | ||
| 2319 | Cannot execute an I/O command without specifying Forced during an emergency stop. | Stop the task and do one of the following: - Clear the emergency stop status and execute the command. - Add Forced to the execution parameter. | Stop task | ||
| 2320 | The function parameter called as a subroutine does not match the data type. | Stop the task and check the function parameter. 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 | ||
| 2321 | The function return value called as a subroutine does not match the data type. | Stop the task and check the function call. 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 | ||
| 2322 | Failed to process reference argument (ByRef) of function called as subroutine. | Stop the task and check the function parameter. 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 | ||
| 2323 | Failed to process the function ByRef parameter called as a subroutine. | Stop the task and check the function parameter. 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 | ||
| 2324 | The number of dimensions of the reference argument (ByRef) of the function called as a subroutine does not match. | Stop the task and check the function parameter. 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 | ||
| 2325 | The ByRef parameter was specified in Xqt. | Stop the task and check the function parameter. 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 | ||
| 2326 | A Call was executed from the command window. | Execute the command from the SPEL program. | Stop task | ||
| 2327 | Failed to Call the function called as a subroutine. | Stop the task and do one of the following: - Check the function parameter. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. - Reboot to allocate space in the temporary folder within the controller, then try again. | Stop task | ||
| 2328 | A task was executed in cooperative mode without being connected to Epson RC+. | Stop the task and do one of the following: - Connect to Epson RC+ and then execute the task again. - If cooperation mode is not necessary for executing the task, change to independent mode in controller configuration settings, then execute the task again. | Stop task | ||
| 2329 | Eval executed in Trap Call processing. | Stop the task and check the SPEL command execution order. 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 | ||
| 2330 | Trap Call/Xqt cannot specify arguments. | 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 | ||
| 2331 | Failed to process Trap Goto statement. | Do one of the following: - Stop the task and check the SPEL command execution order. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. - 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. | Stop task | ||
| 2332 | Failed to process Trap Goto statement. | Do one of the following: - Stop the task and check the SPEL command execution order. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. - 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. | Stop task | ||
| 2333 | An attempt was made to execute Trap during a scheduled execution. | Do one of the following: - Stop the task and check the SPEL command execution order. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. - 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. | Stop task | ||
| 2334 | An attempt was made to execute Trap from Trap Finish or Trap Abort. | Stop the task and check the SPEL command execution order. 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 | ||
| 2335 | This operation cannot be performed in TEACH mode (continue execution, clear error). | Do one of the following: - Execute in any mode other than TEACH. - See the reference manual and check the program for the command that corresponds to the function name and row number in the system history. | Stop task | ||
| 2336 | A command that combines parallel processing and Here was specified. | Stop the task and check the SPEL command execution order. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. For example, it must be changed to the following type of program: P999 = HereGo P999 Here :Z(0) ! D10; MemOn(1) ! | Stop task | ||
| 2337 | This command can only be executed from the GUI Builder event handler function. | Stop the task and check the SPEL command execution order. 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 | ||
| 2338 | Xqt/Input/Print # (TP) that cannot be executed in TEST Mode was specified. | Stop the task and do one of the following: - Execute in any mode other than TEST. - See the reference manual and check the program for the command that corresponds to the function name and row number in the system history. | Stop task | ||
| 2339 | This command can only be executed in Epson RC+ cooperative mode. | Change to independent mode in controller configuration settings, then connect to Epson RC+ and try again. | Stop task | ||
| 2340 | Specified value in InBCD function is an invalid BCD value. | Stop the task and check the value acquired by 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. | Tens digit | Units digit | Stop task |
| 2341 | The parameter specified for the OpBCD command is invalid as a BCD (binary coded decimal) number. | 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. | Specified value | Stop task | |
| 2342 | An I/O number set in the remote I/O function was specified. | Stop the task and do one of the following: - Check the required I/O number remote I/O settings. - Check the I/O 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. | I/O number | 1: bit 2: byte 3: word | Stop task |
| 2343 | An unsupported parameter was specified in the asynchronous output time controlled by the On/Off 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. | The specified time | Stop task | |
| 2344 | An I/O number that is not supported by the connected I/O board was specified (bit). | Stop the task and do one of the following: - Check the connections of the expansion I/O board and fieldbus I/O board required in the SPEL program. - Stop the task and check the SPEL command I/O number. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Bit number | Stop task | |
| 2345 | An I/O number that is not supported by the connected I/O board was specified (bytes). | Stop the task and do one of the following: - Check the connections of the expansion I/O board and fieldbus I/O board required in the SPEL program. - Stop the task and check the SPEL command I/O number. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Byte number | Stop task | |
| 2346 | An I/O number that is not supported by the connected I/O board was specified (word). | Stop the task and do one of the following: - Check the connections of the expansion I/O board and fieldbus I/O board required in the SPEL program. - Stop the task and check the SPEL command I/O number. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Word number | Stop task | |
| 2347 | A memory I/O number outside the supported range was specified (bit). | 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. | Bit number | Stop task | |
| 2348 | A memory I/O number outside the supported range was specified (bytes). | 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. | Byte number | Stop task | |
| 2349 | A memory I/O number outside the supported range was specified (word). | 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. | Word number | Stop task | |
| 2350 | Virtual I/O mode is disabled. A command that cannot be executed was specified. | Stop the task and do one of the following: - Enable virtual I/O mode in controller configuration settings. - See the reference manual and check the program for the command that corresponds to the function name and row number in the system history. | Stop task | ||
| 2353 | A command that cannot be executed in the command window was specified. | Execute the command from the SPEL program. | Stop task | ||
| 2354 | An I/O command was specified with the TP enable switch off. | Stop the task and do one of the following: - Execute with the TP enable switch gripped. - Switch TP to Auto mode and execute. - See the reference manual and check the program for the command that corresponds to the function name and row number in the system history. | Stop task | ||
| 2360 | Failed to acquire settings. | Do one of the following: - Restore the backup file that was operating correctly. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Reboot | ||
| 2361 | Failed to save settings. | Do one of the following: - 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. | Reboot | ||
| 2362 | Failed to acquire 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. - If this error occurs repeatedly, contact us. | Reboot | ||
| 2364 | Failed to save settings. | Do one of the following: - 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. | Reboot | ||
| 2365 | Failed to save settings. | Do one of the following: - 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. | Reboot | ||
| 2370 | String concatenation failed due to string length exceeding limit. | The maximum string length is 255. Stop the task and check the character string length 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. | Combined string length | Stop task | |
| 2371 | A string that exceeds the upper limit length was specified. | The maximum string length is 255. 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. | The specified length | Stop task | |
| 2372 | An unsupported parameter was specified after the ampersand (&) in the Val 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. | Stop task | ||
| 2373 | The Val function specified a string that cannot be converted to a number. | 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 | ||
| 2374 | The string contains an unsupported character code. | 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 | ||
| 2375 | A label name that exceeds the upper limit length 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. | 1: VRT 2: Hand | Stop task | |
| 2376 | A comment that exceeds the upper limit length 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. | 1: VRT 2: Hand | Stop task | |
| 2380 | 0 was specified in For...Next Step. | 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 | ||
| 2381 | The For...Next, GoSub, and Goto call order is invalid. | The relation between For...Next and GoSub is invalid or Goto could be going in or out of For...Next. Stop the task and check the SPEL command execution order. 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 | ||
| 2382 | An attempt was made to execute Return while OnErr was running. | Stop the task and check the SPEL command execution order. 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 | ||
| 2383 | An attempt was made to execute Return without GoSub. | Stop the task and check the SPEL command execution order. 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 | ||
| 2384 | An attempt was made to execute Case or Send without Select. | Stop the task and check the SPEL command execution order. 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 | ||
| 2385 | An attempt was made to execute EResume while GoSub was running. | Stop the task and check the SPEL command execution order. 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 | ||
| 2386 | An attempt was made to execute EResume without OnErr. | Stop the task and check the SPEL command execution order. 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 | ||
| 2391 | A command that cannot be executed during emergency stop was specified. | Stop the task, clear the emergency stop, status and execute the command. | Stop task | ||
| 2392 | Emergency stop Cannot reset directly after robot is stopped due to an error. | Emergency stop Perform a safety check of the robot and peripheral equipment after a robot is stopped due to an error. Later, reset again. | - | ||
| 2400 | Could not open the specified curve file. | Stop the task and do one of the following: - Make sure the specified file exists. - Specify a correct file. - Recreate the specified file. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2401 | Could not open the specified curve file. | Stop the task and do one of the following: - Specify a correct file. - Recreate the specified file. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2402 | Could not create the specified curve file. | Stop the task and do one of the following: - Execute again. - Check the controller storage capacity. - Reduce the file data quantity or size. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2403 | Could not create the specified curve file. | Stop the task and do one of the following: - Make sure the specified file exists. - Specify a correct file. - Recreate the specified file. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2404 | Could not create the specified curve file. | Stop the task and do one of the following: - Execute again. - Check the controller storage capacity. - Reduce the file data quantity or size. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2405 | Could not open the specified curve file. | Stop the task and do one of the following: - Make sure the specified file exists. - Specify a correct file. - Recreate the specified file. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2406 | Could not open the specified curve file. | Stop the task and do one of the following: - Make sure the specified file exists. - Specify a correct file. - Recreate the specified file. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2407 | The specified file is not a curve file. | Stop the task and do one of the following: - Specify a correct file. - Recreate the specified file. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2408 | A different version of the curve file was specified. | Stop the task and do one of the following: - Specify a correct file. - Recreate the specified file. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2409 | A curve file with a different registered robot number was specified. | Stop the task and do one of the following: - Make sure the specified file exists. - Specify a correct file. - Recreate the specified file. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2410 | Failed to allocate memory necessary for CVMove. | Stop the task and do one of the following: - Reduce the data size specified in the command. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2411 | Continuous point data that exceeds the quantity upper limit was specified. | The maximum number of points specified in the Curve statement is 1000. 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 | ||
| 2412 | Parameters that exceed the quantity upper limit were specified. | The maximum number of output commands specified in the Curve statement is 16. 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 | ||
| 2413 | A data size that exceeds the upper limit was specified. | Stop the task and do one of the following: - Reduce the file data quantity or size. - Execute again. - Check the controller storage capacity. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2414 | Continuous point data that exceeds the quantity upper limit was specified. | The maximum number of points specified continuously is 1000. 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. | Start point | End point | Stop task |
| 2415 | Could not create the specified curve file. | Stop the task and do one of the following: - Specify a correct file. - Recreate the specified file. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2416 | The specified curve file does not exist. | Stop the task and do one of the following: - Make sure the specified file exists. - Specify a correct file. - Recreate the specified file. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2417 | An output command was specified at the front of continuous point data. | Check if an output command is specified before the point data. 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 | ||
| 2430 | Failed to get error message. (file path) | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2431 | Failed to get error message. (file open) | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2432 | Failed to get error message.. (header data) | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2433 | Failed to get error message. (get file) | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2434 | Failed to get error message. (different format) | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2435 | Failed to get error message. (different version) | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2440 | Specified the File number that is in use. | Stop the task and do one of the following: - Close the file number in use and then execute. - Check the file name specified with the command that corresponds to the function name and row number in the system history. - Check the file access timing. | Stop task | ||
| 2441 | Cannot open the specified file. | Stop the task and do one of the following: - Check the file name specified with the command that corresponds to the function name and row number in the system history. - Check the file access order. | Stop task | ||
| 2442 | A file that is not open was specified. | Stop the task and do one of the following: - Check the file name specified with the command that corresponds to the function name and row number in the system history. - Check the file access order. | Stop task | ||
| 2443 | Failed to close the file because it is being used by another task. | Stop the task and do one of the following: - Wait until file use ends and try again. - Check the file specified with the command for the corresponding function name and row number in the system history. | Stop task | ||
| 2444 | Failed to save the specified file. | Do one of the following: - Stop the task and check the file 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. - Update the firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2445 | Failed to access the specified file. | Stop the task and check the file name and parameter 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 | ||
| 2446 | Specified the File number that is in use. | Stop the task and close unnecessary files. | Stop task | ||
| 2447 | To read the file you need to open it with ROpen or UOpen. | Use ROpen or UOpen that has read access to the file. | Stop task | ||
| 2448 | To write to a file, it must be opened with AOpen, WOpen or UOpen. | Use WOpen or UOpen that has written access to the file. | Stop task | ||
| 2449 | For binary operations on a file you must open it with BOpen. | Use BOpen that has binary access to the file. | Stop task | ||
| 2450 | Failed to access the specified file. | Stop the task and check the file name and parameter 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 | ||
| 2451 | Failed to save the specified file. | Stop the task and check the file 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. | Stop task | ||
| 2452 | Failed to acquire the specified file. | Stop the task and check the file 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. | Stop task | ||
| 2453 | A command not supported on the currently selected disk was specified. | Stop the task and do one of the following: - Check the disk name specified with the command that corresponds to the function name and row number in the system history. - Change the disk selection with the ChDisk command. | Stop task | ||
| 2454 | An unsupported disk 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 | ||
| 2455 | The specified drive does not exist. | Stop the task and check the drive 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. | Stop task | ||
| 2456 | The specified folder does not exist. | Stop the task and check the folder 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. | Stop task | ||
| 2460 | Specified the database number that is in use. | Stop the task and do one of the following: - Close the database you want to specify and try again. Stop the task and check the SPEL command execution order or parameters. 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 | ||
| 2461 | The specified database file is not open. | Stop the task and check the SPEL command execution order. 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 | ||
| 2462 | Specified the database number that is in use by another task. | Stop the task and do one of the following: - Close the database you want to specify and try again. Stop the task and check the SPEL command execution order or parameters. 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 | ||
| 2470 | 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 the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2471 | Failed to connect to Epson RC+ cooperative function (communication mismatch). | Stop the task and do one of the following: - Check the connection between Epson RC+ and the controller. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2472 | Failed to connect to Epson RC+ cooperative function (duplicate initialization). | Stop the task and do one of the following: - Check the connection between Epson RC+ and the controller. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2473 | Failed to connect to Epson RC+ cooperative function (busy or not initialized). | Stop the task and do one of the following: - Check the connection between Epson RC+ and the controller. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2474 | Failed to connect to Epson RC+ cooperative function (no request). | Stop the task and do one of the following: - Check the connection between Epson RC+ and the controller. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2475 | A data size that exceeds the upper limit was received. | Do one of the following: - Stop the task and check the data size received by 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 the connection between Epson RC+ and the controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2476 | 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 the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2477 | An unsupported folder was specified (linkage function with Epson RC+). | Check the folder specification and try again. | - | ||
| 2478 | A system error has occurred. (Invalid error code) | Stop the task and do one of the following: - Check the connection to Epson RC+. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2500 | An event conditional expression that exceeds the quantity upper limit was specified in the Wait statement. | The maximum number of event conditions is 8. 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 | ||
| 2501 | A bit number that was not set by the CTReset command was specified in the Ctr function. | Stop the task and check the SPEL command execution order. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | The specified bit number | Stop task | |
| 2502 | Task number is beyond the maximum executable count. | The available number of tasks that can be executed simultaneously is 32 for normal tasks, and 16 for background tasks. Stop the task and check the SPEL program. | Stop task | ||
| 2503 | A running task number was specified (Xqt). | Do one of the following: - Wait for the task to end and try again. - 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. | The specified task number | Stop task | |
| 2504 | A robot was specified during parallel processing. | Stop the task and do one of the following: - Synchronize the correct project. - See the reference manual and check the program for the command that corresponds to the function name and row number in the system history. | Stop task | ||
| 2505 | A different quantity of parameters than the input data with the Input command 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 | ||
| 2506 | Parameters that exceed the quantity upper limit were specified. | Up to 32 variables can be 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 | ||
| 2507 | Cannot execute because there are no available counters (CTReset). | The available number of the counters that can be set simultaneously is 16. Stop the task and do one of the following: - Wait until counter use ends and try again. - Check the execution order or parameter of the command that corresponds to the function name and row number in the system history. | Stop task | ||
| 2508 | An invalid SPEL project was specified. | Stop the task and 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. | Stop task | ||
| 2509 | An invalid SPEL project was specified. | Stop the task and 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. | Stop task | ||
| 2510 | An undefined I/O setting label was specified. | Do one of the following: - Define the required label in the I/O setting screen. - Stop the task and check the parameter data specified in the SPEL command or the execution order. 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 | ||
| 2511 | SyncUnlock was used without executing SyncLock. | Stop the task and check the SPEL command execution order. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Signal number | Stop task | |
| 2512 | The specified signal number is already locked with SyncLock. | The SyncLock statement cannot be executed for the second time in a row. Stop the task and check the SPEL command usage. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Signal number | Stop task | |
| 2513 | An undefined point label was specified. | Stop the task and do one of the following: - Define the required point label. - 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 | ||
| 2514 | Failed to acquire robot accumulated motor time. | Stop the task and do one of the following: - Execute again. - Reboot the Controller. | Stop task | ||
| 2515 | A negative number was specified for Date or Time. | 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 | ||
| 2516 | Failed to execute command for service personnel (get debuginfo/initialize). | Stop the task and do one of the following: - Service representatives will confirm how to use the command. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2517 | Failed to convert to date or time. | Stop the task and do one of the following: - Execute again. - Check the time set on the controller. - Reboot the Controller. | Stop task | ||
| 2518 | The end point data number specified is smaller than the start point data number. | 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. | Start point | End point | Stop task |
| 2519 | An unsupported parameter was specified in FmtStr$. | 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 | ||
| 2520 | A file name that exceeds the upper limit length was specified. | Stop the task and check the file 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. | Stop task | ||
| 2521 | A path name that exceeds the upper limit length was specified. | Stop the task and check the file 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. | Stop task | ||
| 2522 | A file name containing an unsupported character type was specified. | Stop the task and check the file 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. | Stop task | ||
| 2523 | Continuation is already running. | Stop the task and check the SPEL command usage. 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 | ||
| 2524 | A running trap task number was specified (Xqt). | Do one of the following: - Wait for the trap task to end and try again. - 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 | ||
| 2525 | A password name that exceeds the upper limit length was specified. | 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. | - | ||
| 2526 | The event conditional expression was not specified. | Stop the task and do one of the following: - Rebuild the project. - Synchronize the project or transfer it via restore. - Check the event conditional expression 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 | ||
| 2527 | A global variable that exceeds the quantity upper limit was specified in the event conditional expression. | Stop the task and check the event conditional expression 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 | ||
| 2528 | An unsupported variable was specified in the event condition (global variable). | Reset the controller and do one of the following: - Check the event conditional expression 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. - Rebuild the project. - Synchronize the project or transfer it via restore. | Reset | ||
| 2529 | Global variables specified in event conditions cannot be passed by reference. | Stop the task and check the event conditional expression 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 | ||
| 2530 | The point file quantity exceeded the upper limit. | Stop the task and do the following: Reduce the point file quantity registered in the project. | Stop task | ||
| 2531 | You cannot specify a point file for a robot other than the current robot. | Stop the task and do one of the following: - Check the specified robot number. - Check the specified point file. | Stop task | ||
| 2532 | Point data that includes undefined data was specified. | Stop the task and check the point 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 | ||
| 2533 | An error occurred in INP and OUTP. | Stop the task and do one of the following: - Service representatives will confirm how to use INP and OUTP. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2534 | The main function to be restarted is not running. | The main function must be executed in Restart call. Stop the task and check the SPEL command and execution order. 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 | ||
| 2536 | Failed to change Enable setting in Teach mode. | Stop the task and do one of the following: - Service representatives will confirm how to use the command. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2537 | An unsupported parameter was specified in VisCalib. | 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 | ||
| 2540 | A SPEL command necessary for connecting to Epson RC+ was specified. | Stop the task, check the connection between Epson RC+ and the controller, and try again. | Stop task | ||
| 2541 | A duplicate robot number was specified. | Stop the task and 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 | ||
| 2542 | An unsupported parameter was specified in the work queue number. | Available work queue numbers are from 1 to 16. 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 | ||
| 2543 | An undefined vision sequence name was specified. | Stop the task and do one of the following: - Specify the required vision sequence. - Check the vision sequence 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. - Rebuild the project. - Synchronize the project or transfer it via restore. | Stop task | ||
| 2544 | An undefined vision object name was specified. | Stop the task and do one of the following: - Set the necessary vision object. - Check the vision object 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. - Rebuild the project. - Synchronize the project or transfer it via restore. | Stop task | ||
| 2545 | An undefined vision calibration name or number was specified. | Stop the task and do one of the following: - Check vision calibration settings. - Check the vision calibration 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. - Synchronize the project or transfer it via restore. | Stop task | ||
| 2546 | Cannot turn on the motor immediately after opening the safeguard. | Stop the task and do the following in order: 1. Disable the safeguard (safety fence closed). 2. Wait at least 1.5 seconds. 3. Execute again. | Stop task | ||
| 2547 | A SPEL command that requires software option settings was specified. | Stop the task and do one of the following: - Enable the option. - Check that the connection of the USB key for the option license is proper. - Disable the SLS/SLP function from the Safety Function Manager. - Part Feeding: Wrong command format or value settings. Read the description for the corresponding command provided in Part Feeding 8.0 Introduction & Hardware (Common) & Software Software Part Feeding SPEL+ Command Reference and correct the code. - Check the SPEL command to be used. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | 1: VRT | Stop task | |
| 2548 | An attempt was made to create a quantity of force files that exceeds the upper limit. | Do one of the following: - Delete unnecessary force files. - Use existing force files. - Reboot the Controller. - Update the controller with the update tool. - Replace the controller. | Stop task | ||
| 2549 | A force file without a registered robot was specified. | Stop the task and do one of the following: - Check the specified force file robot registration. - Check the force file 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 | ||
| 2550 | A SPEL command was specified that is not supported by the connected robot (joint type robot, Cartesian coordinate type robot). | Stop the task and check the SPEL command usage. 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 | ||
| 2551 | Failed to acquire the health information. | Stop the task and do one of the following: - Execute again. - Reboot the Controller. | Stop task | ||
| 2552 | You do not have permission to change UL mode settings. | Contact a service representative to change UL Mode settings. | Stop task | ||
| 2553 | Failed to change UL mode settings. | Stop the task and do one of the following: - Execute again. - Reboot the Controller. | Stop task | ||
| 2554 | A defined label name was specified. | Stop the task and do one of the following: - 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. - Check the hand settings in controller settings. - Check the robot manager VRT settings and the label name specification. | 1: VRT | Stop task | |
| 2555 | An undefined label was specified. | Stop the task and do one of the following: - Check the parameter or execution order 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. - Define the required label in the VRT setting screen. - Define the required label in the hand setting screen. | 1: VRT2:Hand | Stop task | |
| 2557 | An error occurred in TRAP processing. | Stop the task, check Note 1 in the system history, and implement countermeasures shown for the applicable error code. | Detailed error information | Stop task | |
| 2558 | A string that exceeds the upper limit length 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 | ||
| 2559 | A command that cannot be executed while the motor is off was specified. | Stop the task and do one of the following: - Turn the motor power on and then execute the command. - Check the command to execute. | Stop task | ||
| 2560 | The current robot number does not match the RobotNumber setting in the force guided sequence. | Stop the task and do one of the following: - Select the necessary robot number. - Check the parameter or execution order 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 | |
| 2561 | The current robot type and the force guide sequence robot type do not match. | Stop the task and do one of the following: - Change the robot selection. - Reconfigure the force guide sequence RobotNumber properties. - 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 | ||
| 2562 | The force guide sequence RobotTool settings and controller Tool number do not match. | Stop the task and do one of the following: - Select the controller Tool number again. - Check the RobotTool settings used in the force guide sequence. | Tool number | Stop task | |
| 2563 | The point file name being loaded does not match the PointFile setting in the force guide sequence. | Stop the task and do one of the following: - Check the point file name specified in the force guide sequence. - Reload the project containing the specified point file. | Stop task | ||
| 2564 | A command that cannot be executed during torque control was specified. | Stop the task and do one of the following: - Check the command to execute. - Turn torque control off and then execute the command. | Stop task | ||
| 2565 | A command that cannot be executed during tracking was specified. | Stop the task and do one of the following: - Check the command to execute. - Execute the command after tracking ends. | Stop task | ||
| 2566 | A robot running a force-guided sequence was specified (FGRun). | Cannot execute the FGRun command for a robot in use. Stop the task and do one of the following: - Wait until the force guide sequence ends and try again. - Specify another robot. | Stop task | ||
| 2567 | A running force guided sequence was specified (FGGet). | Cannot execute the FGGet command for a running force guide sequence. Stop the task, wait until the force guide sequence ends, and try again. | Stop task | ||
| 2568 | An unsupported command was specified in parallel processing. | Stop the task and check the SPEL command usage. 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 | ||
| 2569 | Failed to execute Force Guide (get property). | Stop the task and do one of the following: - Execute again. - Reboot the Controller. - Synchronize the project or transfer it via restore. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2570 | An unsupported parameter was specified in the sequence number. | Sequence numbers are from 1 to 64. 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. | Sequence number | Stop task | |
| 2571 | An unsupported parameter was specified in the object number. | Stop the task and check the SPEL command or force guide sequence parameters. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Object number | Stop task | |
| 2574 | Force guide execution failed. | Stop the task and do one of the following: - Execute again. - Reboot the Controller. - Synchronize the project or transfer it via restore. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2575 | Force guide execution failed. | Stop the task and do one of the following: - Execute again. - Reboot the Controller. - Synchronize the project or transfer it via restore. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2576 | An undefined force guide sequence name was specified. | Stop the task and do one of the following: - Define the necessary force guide sequence name. - Check the force guide sequence 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. | Stop task | ||
| 2577 | An undefined force guide object name was specified. | Stop the task and do one of the following: - Define the necessary force guide object name. - Check the force guide object 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. | Stop task | ||
| 2578 | A pre-run Force Guide sequence was specified (FGGet). | Stop the task and do the following in order: 1. Execute the force guide from the specified force guide sequence. 2. Execute again. | Stop task | ||
| 2579 | Command execution failed. | Upgrade Epson RC+ and controller firmware to the latest. | Stop task | ||
| 2580 | An undefined part feeder name was specified. | Stop the task and do one of the following: - Check the necessary feeder name in Epson RC+ - Menu - [Setup] - [System Configuration]. - Stop the task and check the part feeder 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. | Stop task | ||
| 2581 | Failed to initialize part feeder. Cannot execute. | Stop the task and do one of the following: - Check the part feeder 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 that feeder network settings (IP Address, IP Mask, Port) in the specified part feeder are correct. - Check that the Ethernet connection between the specified 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 specified part feeder power supply. | Stop task | ||
| 2582 | A part feeder that is not connected was specified. | Stop the task and do one of the following: - Check the part feeder 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 that feeder network settings (IP Address, IP Mask, Port) in the specified part feeder are correct. - Check that the Ethernet connection between the specified 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 specified part feeder power supply. | Stop task | ||
| 2583 | A part feeder whose backlight mounting settings are disabled was specified. | Stop the task and do one of the following: - Check the part feeder settings in Epson RC+ - Menu - [Setup] - [System Configuration]. - Check the part feeder 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 | ||
| 2584 | A part feeder whose hopper mounting settings are disabled was specified. | Stop the task and do one of the following: - Check the part feeder settings in Epson RC+ - Menu - [Setup] - [System Configuration]. - Check the part feeder 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 | ||
| 2585 | Part feeder type does not match. | Delete and then re-register feeder settings in Epson RC+ 8.0 - Menu - [Setup] - [System Settings]. | Stop task | ||
| 2586 | Failed to configure part feeder. | Stop the task and do one of the following: - Check the Ethernet connection between the feeder and controller. Specifically, check for cable disconnections, hub failures, and lack of power supply to the hub. - Check the power supply to the feeder. - Check that feeder network settings (IP Address, IP Mask, Port) are correct. | Stop task | ||
| 2587 | A command not supported in the virtual controller was specified. | Stop the task and do one of the following: - Execute on the actual controller. - Check the command to execute. | Stop task | ||
| 2588 | Failed to acquire part feeder information. | Stop the task and do one of the following: - Check the specified part feeder connection. - Check the SPEL command usage. Targets are the commands corresponding to the function name and row number in the system history. For correction instructions see the reference manual and check the description of the relevant command in the "Part Feeding SPEL+ Command Reference". | Stop task | ||
| 2589 | A command that cannot be executed was specified in the selected part feeder. | Stop the task and do one of the following: - For PartFeeding IF-80, PF_Output command cannot be used. Review the program. - For IF-240/380/530, check if the purge gate is properly mounted. | Stop task | ||
| 2590 | Could not change the vibration set. | Stop the task and do one of the following: - Check that the Ethernet connection between the 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 feeder. - Check that feeder network settings (IP Address, IP Mask, Port) are correct. | Stop task | ||
| 2591 | The part feeder specified in PF_ReleaseFeeder has not been locked in PF_AccessFeeder. | Stop the task and check the SPEL command execution order. 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 | ||
| 2592 | The specified parts feeder is already locked with PF_AccessFeeder. | Stop the task and check the command that corresponds to the function name and row number in the system history. | Stop task | ||
| 2593 | A purge gate whose hopper mounting settings are disabled was specified. | Stop the task and do one of the following: - Check the part feeder settings in System Configuration. - Check the part feeder and purge gate connection. - Check the part feeder 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 | ||
| 2594 | Failed to set the health information. | Check if the specified robot or Controller supports the target parts. | - | ||
| 2595 | An unsupported index was specified in the vision sequence. | Stop the task and check the index specified in the SPEL command vision sequence. 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 | ||
| 2596 | An invalid index was specified for the Vision Object. | Stop the task and do one of the following: - Set the necessary vision object. - Check the index specified in the SPEL command vision object. 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 | ||
| 2597 | Invalid data type. | The format of the specified data is different for the parameter you want to set. (e.g. A Double value is specified even though it must be specified as an Integer.) Please review the value. | Stop task | ||
| 2600 | An unsupported parameter was specified in the mass property object number. | The MassProperties numbers that can be specified are from 1 to 15. 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. | Reset | ||
| 2601 | An undefined mass property object was specified. | Do one of the following: - Reset the controller and reconfigure the mass property settings. - 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. | Reset | ||
| 2602 | A mass property object that is in use was specified. | Cannot clear mass property object that is in use. Stop the task and do one of the following: - Select another mass property object. - Check the mass property 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 | ||
| 2603 | Mass property object number 0 which cannot be cleared was specified. | Cannot clear mass property object 0. Do one of the following: - 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. - Check the mass property object to be specified. | Stop task | ||
| 2610 | An unsupported parameter was specified in the hand number. | You can specify a hand number from 1 to 15. Do one of the following: - Reconfigure the hand settings. - 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. - Restore the backup file that was operating correctly. - If this error occurs repeatedly, contact us. | Reset | ||
| 2611 | An undefined hand was specified. | Stop the task and do one of the following: - Check the hand number specified in the SPEL command. - Configure the hand in the Epson RC+ – Menu – [Tools] – [Robot Manager] – [Hands] tab. | Stop task | ||
| 2612 | Invalid settings found in the specified hand. | Stop the task and do one of the following: - Check the hand number specified in the SPEL command. - Configure the hand in the Epson RC+ – Menu – [Tools] – [Robot Manager] – [Hands] tab again. | Hand number | Stop task | |
| 2613 | A robot that does not support the hand function was selected. | Stop the task and do one of the following: - Select a robot that supports the hand function. - Check the SPEL command to be used. 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 | ||
| 2614 | A hand that is in use was specified. | Stop the task and do one of the following: - Stop the other task and try again. - Check the hand 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 | ||
| 2615 | An unsupported I/O bit number was specified in the hand number. | Do one of the following: - 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. - Reset the controller and check the hand settings. - If this error occurs repeatedly, contact us. | Hand number | Stop task Reset | |
| 2616 | An assigned I/O number was specified. | Do one of the following: - Configure the I/O settings, then remove the unnecessary settings. - 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. - Reset the controller and check the hand settings. - If this error occurs repeatedly, contact us. | Hand number | Stop task Reset | |
| 2617 | A hand not supported on the event conditional expression was specified. | The event conditional expression only supports hands with one input point. Stop the task and do one of the following: - Specify a hand with one input point. - Check the SPEL command to be used and the event conditional expression. 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 | ||
| 2618 | Failed to acquire hand settings. | Do one of the following: - Restore the backup file that was operating correctly. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2619 | LJM and STM functions cannot be used together. | Do one of the following: - Delete the LJM motion command if you want to enable the STM function. - Execute the AutoSTM STM_OFF to disable AutoSTM if you want to use the LJM function. | - | ||
| 2650 | Cannot execute this command because the type of hopper configured does not support it. | Check that the hopper type for the part feeder is correct. | Stop task | ||
| 2700 | Safety function is not available for this Controller. | Use the Controller that supports Safety function. | Reset | ||
| 2702 | Communication error occurred between the safety function manager and the Safety board | Do one of the following: - Check the connection between the RC+ and the Controller and reset the Controller. - Check the connection of the Safety Board in the Controller. - Replace the Safety Board. | Error type 2: Controller detected 16: Response error 32: Difference between main and sub 64: Timeout | Reset | |
| 2708 | Safety function is not available for this robot model. | Select the Robot that supports Safety function. | Reset | ||
| 2851 | The Force Sensor which is different from the registered sensor is connected. | Do one of the following to reboot the Controller: - Check the connection. - Return to the connected force sensor. - Disable the force sensor and replace it with a new one. - For an intentional replacement, configure the connection settings including the serial number in the force sensor setting screen. | Reboot | ||
| 2852 | Cannot recognize the registered force sensor. | Do one of the following to reboot the Controller: - Check the connection. - When not using the force sensor, disable its settings. | Reboot | ||
| 2855 | A system error has occurred (unsupported function). | Do the following in order. 1. Check the power supply and the force sensor I/F unit connection. 2. Reboot the Controller. | Reboot | ||
| 2857 | The robot registered to the force sensor is not connected. | Do one of the following to reboot the Controller: - Check the robot connection. - Check the settings of the robot registered to the force sensor. - Disable the robot registered to the force sensor. | Reboot | ||
| 2858 | Failed to allocate memory (force monitor). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2859 | Failed to allocate memory (force log). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2860 | A force monitor object that is in use has been specified. | Stop the task and check the force monitor 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 | ||
| 2861 | Reached the upper limit of functions that can be executed simultaneously with the specified command. | Do the following: - Check the command or property that corresponds to the function name and row number in the system history. | - | ||
| 2862 | Failed to allocate memory (force control). | Stop the task and do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2863 | Force-guided sequence execution and RecordStart cannot be executed at the same time. | Execute after the LogStart property ends by LogEnd property. | Stop task | ||
| 2864 | Force guide sequence execution, RecordStart, and Force Monitor cannot be executed at the same time. | Execute after quitting the Force Monitor. | Stop task | ||
| 2865 | Reached the upper limit of functions that can be executed simultaneously with the specified command. | Stop the task and do one of the following: - Stop the function from the force guide force monitor screen and try again. - See the reference manual for the command that corresponds to the function name and row number in the system history. | Stop task | ||
| 2866 | Force guide sequence execution, RecordStart, and Force Monitor cannot be executed at the same time. | Execute the force monitor after quitting the RecordStart property by force guide sequence, force control monitor, or the RecordEnd property. | - | ||
| 2867 | A channel number that is in use was specified. | Stop the task and check the channel 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 | ||
| 2868 | A force monitor object that is in use has been specified. | Do one of the following: - Stop the task and check the force monitor 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. - Check the force monitor object specification. | Stop task | ||
| 2869 | The measurement time was set to a value smaller than the measurement interval. | 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 | ||
| 2870 | The product of the specified duration of measurement and the specified measurement interval is out of allowable range. | 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 | ||
| 2871 | Force guide sequence execution, RecordStart, and force monitor cannot be used at the same time. | Stop the task and do one of the following: - Stop the task or the command that is currently running. - Stop the function from the force guide force monitor screen and try again. - See the reference manual for the command that corresponds to the function name and row number in the system history. | Stop task | ||
| 2872 | Force monitor cannot be launched twice. | To start force monitor newly, quit the running force monitor and start a new one. | Stop task | ||
| 2880 | Failed to initialize the Force Sensor. | Do one of the following: - Check connection of the Force Sensor I/F board and Force Sensor. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Reboot | ||
| 2888 | A force sensor not supported on the controller has been set. | Stop the task and do one of the following: - Check the controller force sensor settings. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task Reboot | ||
| 2889 | A hand that is not supported by Force Guide has been specified for RobotHand. | Stop the task and do one of the following: - Check the hand specified in the force guide sequence. - Check the controller hand settings. | Stop task | ||
| 2900 | Failed to open TCP/IP port (server). | Stop the task and do one of the following: - Check whether the Ethernet port is set properly. - Check whether the Ethernet cable is connected properly. | Stop task | ||
| 2901 | Failed to open TCP/IP port (client). | Stop the task and do one of the following: - Check whether the Ethernet port is set properly. - Check whether the Ethernet cable is connected properly. - When using the part feeder, check if the settings are correct. | Stop task | ||
| 2902 | The destination TCP/IP port is closed. | Stop the task, check if the destination TCP/IP port specified on OpenNet is not closed, and try again. | Stop task | ||
| 2904 | Invalid IP Address was specified. | Stop the task and do one of the following: - Check the IP address 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. - When using the part feeder, check the part feeder host name specification and try again. | Stop task | ||
| 2905 | Server/Client not specified in OpenNet 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. | Stop task | ||
| 2906 | An undefined TCP/IP port was specified. | Stop the task and do one of the following: - 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. - Check whether the Ethernet port is set properly. - When using the part feeder, check if the settings are correct. | Port number | Stop task | |
| 2907 | A TCP/IP port connected on another task has been specified. | Do one of the following: - Stop the task and check the parameter data specified in the SPEL command and the execution order. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. - Specify another TCP/IP port and try again. - Stop TCP/IP communication to the PC running the virtual controller, then try again. | Port number | Stop task | |
| 2908 | An attempt was made to change the connected TCP/IP port settings. | Stop the task and check the parameter data specified in the SPEL command and the execution order. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Port number | Stop task | |
| 2909 | A TCP/IP port that is not yet connected was specified. | Stop the task and do one of the following: - Check the parameter and execution order 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. - When using the part feeder, check the connection and settings. - If this error occurs repeatedly, contact us. | Port number | Stop task | |
| 2910 | Communication with the specified TCP/IP port failed (read timeout). | Stop the task and do one of the following: - Check the TCP/IP port and execution order 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 the controller connection destination status. - Check the network status. - Check whether the Ethernet port is set properly. - When using the part feeder, check the connection and settings. | Timeout value | Stop task | |
| 2911 | Communication failed on the specified TCP/IP port. | Stop the task and do one of the following: - Check the TCP/IP port and execution order 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 the controller connection destination status. - Check the network status. - Check whether the Ethernet port is set properly. - When using the part feeder, check the connection and settings. | Stop task | ||
| 2912 | A TCP/IP port connected on another task has been specified. | Stop the task and check the parameter data specified in the SPEL command and the execution order. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Port number | Stop task | |
| 2913 | Communication failed on the specified TCP/IP port. | Stop the task and do one of the following: - Check the TCP/IP port and execution order 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 the controller connection destination status. - Check the network status. - Check whether the Ethernet port is set properly. - When using the part feeder, check the connection and settings. | Port number | Stop task | |
| 2914 | A TCP/IP port that is not connected was specified. | Stop the task and do one of the following: - Check the controller connection destination status. - Check the network status. - Check whether the Ethernet port is set properly. - Check the TCP/IP port and execution order 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. | Port number | Stop task | |
| 2915 | A data size that exceeds the upper limit was received. | The maximum length of a line is 255 bytes. Stop the task and do one of the following: - Check the data size received by 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. - When using the part feeder, check the connection and settings. | The number of bytes in a received line | Stop task | |
| 2916 | Virtual TCP/IP port processing failed (dummy file). | Stop the task and do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Port number | Stop task | |
| 2920 | Failed to connect to RS-232C port. | Stop the task and do one of the following: - Check if the RS-232C port is set properly. - Check the RS-232C cable connection. - Check the RS-232C board connection. | Stop task | ||
| 2921 | RS-232C port communication failed (read). | Stop the task and do one of the following: - Check if the RS-232C port is set properly. - Check the RS-232C cable connection. - Check the RS-232C board connection. - Check the RS-232C port and execution order 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 | ||
| 2922 | Failed to communicate with RS-232C port due to a buffer overrun. | Stop the task and do one of the following: - Reduce the transfer speed. - Reduce the data volume. | Stop task | ||
| 2926 | Cannot recognize RS-232C board. Failed to open port. | Stop the task and check the controller RS-232C board connection. | Port number | Stop task | |
| 2927 | An RS-232C port connected on another task has been specified. | Stop the task and check the parameter data specified in the SPEL command and the execution order. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Port number | Stop task | |
| 2928 | An attempt was made to change the connected RS-232C port settings. | Do one of the following: - Stop the task and check the parameter data specified in the SPEL command and the execution order. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. - Specify another RC-232C port and try again. - Stop RS-232C communication to the PC running the virtual controller, then try again. | Port number | Stop task | |
| 2929 | An attempt was made to change the settings of the RS-232C port that is not yet connected. | Stop the task and check the parameter data specified in the SPEL command and the execution order. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Port number | Stop task | |
| 2930 | RS-232C port communication failed (read timeout). | Stop the task and do one of the following: - Check if the RS-232C port is set properly. - Check the RS-232C cable connection. - Check the RS-232C board connection. - Check the RS-232C port and execution order 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. | Timeout value | Stop task | |
| 2931 | RS-232C port communication failed (read). | Stop the task and do one of the following: - Check if the RS-232C port is set properly. - Check the RS-232C cable connection. - Check the RS-232C board connection. - Check the RS-232C port and execution order 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 | ||
| 2932 | An RS-232C port connected on another task has been specified. | Stop the task and check the parameter data specified in the SPEL command and the execution order. Targets are the commands corresponding to the function name and row number in the system history. See the reference manual for correction instructions. | Port number | Stop task | |
| 2933 | RS-232C port communication failed (write). | Stop the task and do one of the following: - Check if the RS-232C port is set properly. - Check the RS-232C cable connection. - Check the RS-232C board connection. - Check the RS-232C port and execution order 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. | Port number | Stop task | |
| 2934 | A RS-232C port that is not connected was specified. | Stop the task and do one of the following: - Check the controller connection destination status. - Check the network status. - Check if the RS-232C port is set properly. - Check the RS-232C port and execution order 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 | ||
| 2935 | A data size that exceeds the upper limit was received. | The maximum length of a line is 255 bytes. Stop the task and check the data size received by 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. | The number of bytes in a received line | Stop task | |
| 2936 | Failed to process virtual RS-232C port (dummy file). | Stop the task and do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Port number | Stop task | |
| 2938 | An RS-232C port that is already connected to another task was specified (ModBus). | Stop the task and check the parameter data specified in the SPEL command and the execution order. 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 | ||
| 2950 | Failed to initialize controller (daemon thread creation error). | Do one of the following: - Reboot the Controller. - Reset the controller and update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Reset | ||
| 2951 | Failed to initialize controller (daemon thread creation timeout). | Do one of the following: - Reboot the Controller. - Reset the controller and update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Reset | ||
| 2952 | Mode change key switch input signal error detected. | Do all of the following, then reboot: - Correctly set the TP mode change key switch to TEACH or AUTO. - Check whether the TP is connected properly. | Reboot | ||
| 2953 | Enable switch input signal error detected. | Check the TP connection and reboot the controller. | Reboot | ||
| 2970 | Failed to allocate memory (MNG). | 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 | ||
| 2971 | Failed to execute SPEL command (real-time check error). | Stop the task and 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. | Stop task | ||
| 2972 | A system error has occurred (MNG standard priority). | Stop the task and do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2973 | A system error has occurred (MNG BOOST priority). | Stop the task and do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2974 | A system error has occurred (MNG DOWN priority). | Stop the task and do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Stop task | ||
| 2975 | A system error occurred (MNG event waiting). | Do one of the following: - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | Reboot | ||
| 2977 | Failed to release memory (MNG). | Try rebooting the controller. Do one of the following: - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2978 | Failed to initialize controller (MNG AddIOMem error). | Do one of the following. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2979 | Failed to initialize controller (MNG AddInPort error). | Do one of the following. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2980 | Failed to initialize controller (MNG AddOutPort error). | Do one of the following. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2981 | Failed to initialize controller (MNG AddMemPort error). | Do one of the following. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2982 | Failed to initialize controller (MNG AddOutMemPort error). | Do one of the following. - Reboot the Controller. - Update the controller firmware with the update tool. - If this error occurs repeatedly, contact us. | - | ||
| 2983 | Failed to execute SPEL command (IntervalOutBit, MNG). | Stop the task and 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. | Stop task | ||
| 2984 | Failed to execute SPEL command (CtrReset, MNG). | Stop the task and 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. | Stop task | ||
| 2985 | Failed to allocate memory. (vision response reception buffer) | 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. | Stop task | ||
| 2997 | Simulator detected a collision. | Stop the task and do one of the following: - Check the simulator environment object layout. - Check the robot operation. | Stop task | ||
| 2998 | A command not accompanied by robot motion triggered by AbortMotion was aborted. | Stop the task and check the system history. This error code is triggered when the AbortMotion command is launched and the OnErr command triggers a hook. It is equivalent to the ERROR_DOINGMOTION constant. For details, see the reference manual. | Stop task | ||
| 2999 | A robot motion command triggered by the AbortMotion command was aborted. | Stop the task and check the system history. This error code is triggered when the AbortMotion command is launched and the OnErr command triggers a hook. It is equivalent to the ERROR_NOMOTION constant. For details, see the reference manual. | Stop task |