Appendix
System error messages
Errors that occur within the controller can either be hardware (head connection errors, etc.), or software related (improper settings, etc.). While the controller operates in RUN mode, any error occurrence can be detected via the ERROR terminal which turns on in the event of an error.
Head connection
Error Number |
Error Message |
Cause |
10001 |
No head has been found. Please turn off the controller and connect to Head A, then reboot the controller. |
An error occurred in the connection with the head. The head is being used beyond its rating. (For example, the ambient temperature of the head is beyond the specification, or a non-supported head cable is being used.) |
10002 |
Head B is not connected. |
An unconnected head is specified in the tool settings. |
10003 |
Undetected head is connected. Turn off the controller and check the head model. |
A head which is not supported by the controller is connected. |
10004 |
No head can be recognized. Please turn off the controller and connect to Head A, then reboot the controller. |
|
10005 |
Only Head B is connected. When using only one head, Head A should be used. Please turn off the controller and connect to Head A, then reboot the controller. |
|
10030 |
An old head version is connected. Unsupported functions will be disabled. |
An old head version is connected and functions that are not compatible with that head are set. |
External unit
Error Number |
Error Message |
Cause |
10105 |
An external unit that cannot be recognized is connected. Turn off the controller and check the model of the external unit. |
An external unit that is not supported by the controller is connected. |
System File
Error Number |
Error Message |
Cause |
11001 |
Unable to load the selected program file. The program will be started with initialized settings. |
The last used (saved) Program file is corrupt or has been deleted. The Program that was exported using the Program backup does not contain the open Program. |
11002 |
Failed to load because the image memory of the program is beyond the size. Some settings will be initialized. |
|
11003 |
Failed to load the global setting. The global setting will be started with initialized settings. |
|
11004 |
Unable to load the program file due to unsupported version. The program will be started with initialized settings. |
The data in the specified Program was created with an incompatible version. |
11005 |
Unable to load the program file due to checksum errors. The program will be started with initialized settings. |
The specified Program file has a checksum error. |
11006 |
Unable to load the program file due to damage. The program will be started with initialized settings. |
The data in the specified Program file is corrupt and cannot be used. |
11011 |
Failed to load because the resource memory of the program is beyond the size. |
|
11031 |
If hold mode is turned off, the function to trigger multiple times is not available. The device will start with the function to trigger multiple times disabled. |
Hold mode is turned off when multiple trigger is enabled. |
11032 |
Dependency between tools is cycling. |
In the check when going into operation mode, there is a circular reference in the dependency between tools. |
SD Card
Error Number |
Error Message |
Cause |
12001 |
Failed to access SD Card 1. |
|
12002 |
Failed to access SD Card 2. |
|
12003 |
SD Card 1 is full. |
The SD memory card is full. |
12004 |
SD Card 2 is full. |
|
12005 |
Insert SD Card 1. |
|
12006 |
Insert SD Card 2. |
|
12007 |
Cannot find SD Card 1. Be sure to keep the SD card 1 inserted during the power on. |
SD Card 1 was removed while the power was ON. |
12008 |
Execute the eject operation before removing the SD Card 2. The SD card and files may be damaged. |
The SD card was removed without using the [Remove SD Card 2] function. |
12009 |
SD Card 1 is write-protected. |
The write-protect switch on SD Card 1 is enabled. |
12010 |
SD Card 2 is write-protected. |
The write-protect switch on SD Card 2 is enabled. |
12012 |
Unable to export to SD Card 2 due to a full output buffer. |
SD Card 2 output buffer is full. |
12014 |
Please turn off the power and reboot after having inserted the firmware SD card. |
No firmware SD card is in the slot. |
12101 |
Connect the USB HDD. |
|
12102 |
Failed to access the USB HDD. |
|
12103 |
Unable to output to the USB HDD due to a full output buffer. |
The output buffer for output to the USB HDD is full. |
12104 |
The USB HDD is full. |
There is not enough free space on the USB HDD. |
12105 |
The USB HDD is write-protected. |
The write-protect switch on the USB HDD is enabled. |
12106 |
Execute the Remove USB HDD operation before removing the USB HDD. The USB HDD and files may be damaged. |
The USB HDD was removed without using the [Remove USB HDD] function. |
12107 |
An unsupported USB device was connected. Please remove the connected USB device. |
A device other than mass storage class devices, such as a mouse, is connected to the USB 3.0 connector. |
12108 |
The format of the USB HDD is incorrect. Please format it. |
The controller could not recognize the format of the USB HDD. |
RS-232C
Error Number |
Error Message |
Cause |
13101 |
An RS-232C communication time out error has occurred. |
RS-232C communication has been down for 60 or more seconds with data output via the RS-232C port specified in the output settings. |
13102 |
Unable to output to RS-232C due to a full output buffer. |
The controller output buffer for outputting via the RS-232C port is full. |
Ethernet
Error Number |
Error Message |
Cause |
13201 |
Ethernet cable is not connected. |
An error occurred with the Ethernet cable when data output via the Ethernet is specified in the output settings. |
13202 |
An Ethernet communication time out error has occurred. |
Ethernet communication has been down for 10 or more seconds when data output via the Ethernet is specified in the output settings. |
13203 |
Failed in the Ethernet (Non-Procedural) communication. |
An error occurred with the Ethernet communication when data output via Ethernet is specified in the output settings. |
13204 |
Unable to output to Ethernet due to a full output buffer. |
The controller output buffer for outputting via the Ethernet port is full. |
PLC-Link
Error Number |
Error Message |
Cause |
13301 |
Failed to establish a link with the PLC. |
An error occurred in the PLC-Link communication connection with the [Field network] settings in [Global] set to [PLC-Link]. |
13302 |
Unable to output to the PLC-Link due to a full output buffer. |
The controller output buffer for outputting via PLC-Link is full. (Image First) |
13303 |
The delay of the handshake control causes skipping of the PLC communication result output. |
As the amount of data output overflows the buffer, data output is suspended partially. |
Terminal I/O
Error Number |
Error Message |
Cause |
13401 |
Unable to make the terminal output due to a full output buffer. |
The output buffer for output via the terminal is full. |
13402 |
The delay of the handshake control causes skipping of the I/O terminal output. |
As the amount of data output overflows the buffer, data output is suspended partially. |
FTP
Error Number |
Error Message |
Cause |
13501 |
Failed to connect to FTP server. |
|
13502 |
Failed to log in to FTP server. |
The user ID and/or password for logging in to the FTP server is incorrect. |
13503 |
Timeout error occurred during output to FTP server. |
The controller logged in and began writing a file but was unable to complete the process within the specified time. |
13504 |
Failed to output the file to FTP server. |
The controller was able to log into the FTP server, but was not able to create a file. |
13510 |
FTP output failed due to a full buffer. |
The output buffer for output via FTP is full. Reduce the amount of data to be output, so that the data for each measurement is output at a slower rate than they are output to the FTP. Or, extend the time between triggers/processing to allow for data to be output. Note: Results data are not written when the buffer is full. |
EtherNet/IP
Error Number |
Error Message |
Cause |
13601 |
Ethernet/IP communication failed. |
An error occurred in the EtherNet/IP communication connection with the [Field network] settings in [Global] set to [EtherNet/IP]. |
13602 |
Ethernet/IP output failed due to a full buffer. |
The controller output buffer for outputting via the EtherNet/IP port is full. |
13603 |
The delay of the handshake control causes skipping of the EtherNet/IP communication result output. |
As the amount of data output overflows the buffer, data output is suspended partially. |
13604 |
The EtherNet/IP unit cannot be recognized. |
EtherNet/IP unit was not recognized and the controller cannot use EtherNet/IP communication. |
PROFINET
Error Number |
Error Message |
Cause |
13701 |
PROFINET communication failed. |
An error occurred in the PROFINET communication connection with the [Field network] settings in [Global] set to [PROFINET]. |
13702 |
PROFINET output failed due to a full buffer. |
The output buffer for output via PROFINET is full. |
13703 |
The delay of the handshake control causes skipping of the PROFINET communication result output. |
As the amount of data output overflows the buffer, data output is suspended partially. |
13704 |
The PROFINET unit cannot be recognized. |
The PROFINET unit is not recognized and the controller cannot use PROFINET communication. |
EtherCAT
Error Number |
Error Message |
Cause |
13801 |
EtherCAT communication has failed. |
Communication was interrupted. (When recovery is possible, recovery occurs automatically.) |
13802 |
EtherCAT output failed due to a full buffer. |
The controller output buffer for outputting via EtherCAT is full. |
13803 |
The delay of the handshake causes skipping of the EtherCAT communication result output. |
When the EtherCAT handshake is on, a delayed handshake caused results output via EtherCAT to be skipped. |
13804 |
EtherCAT unit is not recognized. |
The EtherCAT unit is not recognized and the controller cannot use EtherCAT communication. |
Processing Memory
Error Number |
Error Message |
Cause |
14001 |
Insufficient processing memory. |
Processing memory space available is insufficient. |
Firmware
Error Number |
Error Message |
Cause |
14301 |
The controller was booted using an unsupported firmware. Please turn off the power once and then update the firmware. |
The controller was started with a firmware version not supported by the controller. |
14501 |
Communication expansion unit n* is not found. Please turn off the power temporarily and check the connection of the expansion units. *n: communication expansion unit number (1 to 16) |
|
14502 |
Expansion unit initialization failed. Please turn off the power temporarily and check the connection of the expansion units. |
|
14503 |
The internal temperature of the controller is high. As this may cause a breakdown, please check the installation condition and ambient temperature. |
There is a problem with the controller installation, or the ambient temperature has exceeded the rated value. (e.g.: Ventilation holes are blocked.) |
14504 |
The internal temperature of the controller has exceeded the prescribed value. Please turn off the power temporarily and check the installation condition and ambient temperature. |
|
14506 |
Overcurrent was detected on the connected USB device. Please check the device connected to the USB. |
|
14507 |
The configuration of the connected expansion units is invalid. Please turn off the power temporarily and check the configuration of the expansion units. |
An expansion unit that cannot be used on the controller is connected. |
Normal errors
General
Error Number |
Error Message |
30006 |
IP address collision has occurred between the controller and other system on the network. |
Execution Errors
Error Number |
Error Message |
20003 |
Detect line failed. |
20004 |
Circle/arc detection failed. |
20005 |
Point detection failed. |
20006 |
Standard model line detection failed. |
20008 |
The timeout error has occurred. |
20018 |
The settings of the tool to be referenced are invalid. |
20034 |
Not measurable. |
20042 |
Pitch detection failed. |
20050 |
Contour detection failed. |
20051 |
The maximum detectable limit has been exceeded. |
20052 |
There is no reference image. |
20053 |
No contours were found that match the base contour. |
20054 |
Fitting failed. |
20090 |
No measurements were performed in the measurement period. |
20091 |
The measurement result of the referenced tool is invalid (ALARM). |
20099 |
Tool execution error has occurred. |
20112 |
Position adjustment failed. |