Error Code |
Error Message |
Cause and Troubleshooting |
RYAA001 |
The specified shared memory already exists. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA002 |
The specified shared memory does not exist. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA003 |
A shared memory already exists, but its memory size is less than specified. |
Please close another application or restart the OS. |
RYAA004 |
Cannot create a shared memory due to insufficiency of memory or resource. |
Please close another application or restart the OS. |
RYAA005 |
Could not start TdasEngine because it is already in execution or termination. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA006 |
Could not stop TdasEngine because it is already in suspension or termination. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA007 |
Could not register the operation in TdasEngine. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA008 |
Cannot execute State Transition of TdaInfo because a small service is now in transition. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA009 |
The device name ( **** ) specified as the destination Node does not exist. |
The defined names of connected devices are different between the master and slave display units. The connected devices names must match. |
RYAA010 |
Cannot execute the operation due to the invalid state of the small service. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA011 |
Cannot execute the operation because the small service is not in operation. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA012 |
Cannot execute the operation because the small service is in error suspension. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA013 |
The I/F of an unsupported small service was called. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA016 |
Could not register the item because of insufficient memory. |
Please close another application or restart the OS. |
RYAA017 |
Accessed a device in which no item is registered. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA018 |
Accessed an out-of-range device. |
A device beyond the valid device range was accessed. |
RYAA019 |
Failed to register the specified cluster because an invalid item is specified in it. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA020 |
The specified data type is invalid. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA021 |
The specified access type is illegal. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA022 |
The specified data type is illegal. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA023 |
The no. of data you specified is too many to write. (Please reduce it to **** or fewer.) |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA024 |
The operation result to write is below the lower limit value. |
The value to write was out of range. Please change the setting to write an in-range value. |
RYAA025 |
The operation result to write is beyond the upper limit value. |
The value to write was out of range. Please change the setting to write an in-range value. |
RYAA026 |
Could not send processing request to the network destination due to insufficient memory. |
Please close another application or restart the OS. |
RYAA027 |
The specified group was not found. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA028 |
The two compared access tickets differ in their nodes, equipment, or devices. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA029 |
The specified access ticket is not for this node. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA030 |
Could not register the cache because of insufficient memory. |
Please close another application or restart the OS. |
RYAA032 |
The access ticket you tried to use in block access is not of the block type. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA033 |
The small service to process was not found. |
A fatal error occurred. Run transfer again. Or, use GP-Pro EX to run forced transfer. Then transfer again. |
RYAA034 |
The size of block access to the device exceeded the limit. |
The max buffer size for Device Block Write/Read is 10KB. Please set a size less than that. |
RYAA035 |
A different network project is being used. |
Please transfer the project file with GP-Pro EX again. |
RYAA037 |
The no. of requests/the buffer size of requests to Read/Write via network at a time exceeded the limit( **** ). |
Please recheck the settings of requests from and GP-Pro EX to the network destination, and redesign the system to limit the no. of requests to the max value. |
RYAA048 |
A communication error occurred during communication with the destination node. Please confirm that the network connection to the node has been properly established. |
Check that the network and cables between this display unit and the target unit are properly established and connected. |
RYAA049 |
The destination node did not respond within the specified time. Please confirm that the network connection to the node has been properly established. |
The response from the client is not within the timeout period set for the client. |
RYAA050 |
The destination node did not respond within the specified time. Please confirm that the network connection to the node has been properly established. |
The response from the server is not within the timeout period set for the server. |
RYAA051 |
Communication with the destination Node stopped because the destination or local Node closed. |
Set the display unit that is connected to the Run screen. |
RYAA064 |
Failed to read the device. |
The data may have been read into an illegal or undefined device address. Please specify a proper device address. |
RYAA065 |
Failed to write the device. |
The data may have been written into an illegal or undefined device address. Please specify a proper device address. |
RYAA069 |
The specified request is not supported. |
Please upgrade GP-Pro EX to a supported version by transferring the system. |
RYAA070 |
The specified request is not supported. |
Please upgrade GP-Pro EX to a supported version by transferring the system. |
RYAA080 |
The project ID of the network project file is different. (A different network project is being used. |
Please transfer the project file again with GP-Pro EX. |
RYAA081 |
The network project file does not have necessary data. |
Please transfer the project file again with GP-Pro EX. |
RYAA082 |
The network project file is damaged. |
Please transfer the project file again with GP-Pro EX. If it not enough, please transfer the project file with GP-Pro EX again. |
RYAA083 |
The network project file does not exist. |
Please transfer the project file again with GP-Pro EX. If it not enough, please transfer the project file with GP-Pro EX again. |
RYAA090 |
Unable to connect to server. Exceeding client limit. |
Terminate GP-Viewer EX that has been connected and try the connection again. |
RYAA091 |
Unable to connect to server. Server settings have changed. |
Try connecting to the server again. |
RYAA092 |
Unable to connect to server. Server authentication failed. |
Try connecting to the server again. |
RYAA093 |
Unable to connect to server. Server is starting up. |
Try connecting to the server again. |
RYAA096 |
Failed to transfer data to display unit.(****) |
Please confirm that the PLC connected to the display unit works properly. Please transfer the project file again with GP-Pro EX. |
RYAA097 |
Failed to read the device from display unit. |
Accessed an read-protect area. Please change the setting to avoid this. |
RYAA098 |
Failed to write the device to display unit. |
Accessed an write-protect area. Please change the setting to avoid this. |
RYAA099 |
In device access to the display unit, the device number was out of range. |
An invalid device was specified. Attempted to access a nonexistent device. |
RYAA100 |
Failed to transfer data to display unit. (The destination Node does not respond.) |
The Destination Node does not respond. Check the following:
Please transfer the project file again with GP-Pro EX. |
RYAA101 |
Failed to read the device from display unit. |
The Destination Node does not respond. Check the following:
|
RYAA102 |
Failed to write the device to display unit. |
The Destination Node does not respond. Check the following:
|
RYAA103 |
Operation was interrupted because the display unit was not online anymore. |
The process was interrupted because the display unit was not online anymore. In order to complete the processing, set the display unit to the Run screen and repeat the processing. |
RYAA112 |
Failed to update SRAM data. |
Forcibly transfer the system using GP-Pro EX. |
RYAA113 |
No accessing SRAM while processing. |
Forcibly transfer the system using GP-Pro EX. |
RYAA114 |
Unsupported request was set when accessing SRAM. |
Forcibly transfer the system using GP-Pro EX. |
RYAA115 |
Could not retrieve SRAM data because of insufficient memory. |
Please close another application or restart the OS. |
RYAA116 |
Could not register periodical SRAM update because of insufficient memory. |
Please close another application or restart the OS. |
RYAA125 |
Screen changes are not permitted from the client. |
The screen switch request was rejected. Check the following:
|