An I/O operation has failed. This is a generic error code that is used when an I/O operation fails but no specific information is available.

A read data operation was initiated in a situation where I/O is normally expected, but no data is available. For example, an attempt was made to read a reply message when no request command was sent.

An I/O operation cannot allocate internal buffers in a situation where buffers should always be available. This error should normally not be seen. Please report this error to customer service.

An Ethernet slave controller node or a RS-485 serial bus board is configured but could not be found. Additional information may be appended to the error message that describes the device type (Controller or RS-485 bus), the device name or controller serial number, and the network node assigned to this device. Verify that DataID 151 (Servo network node identifier) is specified correctly and that all slave controllers and RS-485 bus boards are present, configured correctly and operational.

An I/O operation has returned less data than required. This error should normally not be seen. Please report this error to customer service.

The end of a data file has been encountered before it was expected. Normally this means the data file has been corrupted. For example, when reading a GPL program file, the end of file is found before the end of a program or module.

An I/O operation or the GPL compiler has received more input than it can handle. For example, a GPL program statement or argument is longer than what can be stored in internal buffers. Try shortening the program statement or breaking it into several statements.

Indicates that the output generated by the command being executed contained too much data. In the case of the Data Logger function, this error may indicate you attempted to log too many values that were elements of special arrays. For example, the Data Logger can internally capture a maximum of 24 items. If you request a single element of "Actual joint angles in deg or mm" (DataID 3504) for a 4-axis robot, this doesn't count as one of 24, it counts as 4 of 24 items. If you specify all four elements individually, this will count as 16 of 24. For this DataID, you should specify an array index of 0. This will return all 4 joint values and will only count as 4 of 24 maximum items.

You have specified a file that does not exist. Verify that the file name is spelled correctly and that the device and directory path are correct.

You have specified a file for writing that cannot be opened. The file may not exist, the file may be protected as read only, or another thread may have the file open. Verify that the file name is spelled correctly and that the device and directory path are correct.

You have attempted to create a file that already exists.

An attempt to create a directory has failed. Normally this error should not occur. Check to ensure you are creating a directory on the /flash device in a folder that is not read only.

A write operation to a device or file has failed. Verify that the file you are writing is not read only. Verify that the file or device is open for write.

A read operation from a device or a file has failed. Verify that the file or device is open for read.

An attempt has been made to use an I/O buffer that is already in use. This error should normally not be seen. Please report this error to customer service.

An invalid ASCII character has been encountered while compiling a GPL program. Verify that your program file does not contain characters with binary values > 127 (decimal).

A file name string is invalid. It may contain invalid characters or may not have the proper directory path format. For example, the file name contained in a GPL projects.gpr file may have been corrupted.

The total file path and name string you have specified is too long. GPL restricts file name and path to a total of 128 bytes. The maximum length of any file or folder on the /flash disk is 43 bytes.

A data file or message that is validated by a checksum does not have a correct checksum value. For example, GPL system update files have a checksum value that is validated before the data is written to flash. If this error occurs during an update request, the wrong file may have been specified, or the file is corrupted.

The format of a data file does not match what is expected. For example, a GPL system update file does not contain the expected identification headers. The wrong file may have been specified, or the file is corrupted.

You have attempted to perform a file operation on a file that is not open. For example, a GPL StreamReader or StreamWriter I/O method has been used on an object that does not have an open file.

You have attempted to access a file in a way that is not allowed for the type of file. For example, you have attempted to open a directory file as a normal file.

You have attempted to access a file that is already in use. For example, you have attempted to delete a file that is open for read.

A polling I/O request has failed because no data is available. This code does not indicate a real error. Normally the I/O request should be repeated after a time delay.

A request has been made to read the timestamp for an I/O request when none is available. Normally this error is not seen.

The hardware latch circuit has detected that edges in the latch input signal are occurring too quickly to be processed. One or more latch edges have been lost. The latch circuit cannot handle duplicate latch edges in the same direction more often than once every 1.2 milliseconds. There may be noise on the latch input signal.

Latch events are occurring too quickly for the Precise Controller to service them. If a continuous stream of latch events occurs at a rapid rate, the controller may run out of time to process them. This error is more likely to occur in a servo network system. Reduce the rate of latch events or reduce the number of latch signals being used.