When an error occurs, an error message appears on the bottom (or top) portion of the screen area.
For details about showing and hiding error messages, refer to the following.
System Menu - Offline, CF/USB (or SD/USB), Error, Reset
The following describes the cause of errors and their solution.
Errors starting with RHxx (Errors that occur when there are connection issues)
Errors starting with RAAA (Application errors)
Errors starting with RAAE (Run time errors)
Errors starting with RHxx (Errors that occur when connection is not working well)
The following error messages are displayed when there is a problem in the communication with the connected device (PLC etc).
The following error messages are common to all drivers (device/PLC types). For the specific errors of each device/PLC types, please refer to "GP-Pro EX Device/PLC Connection Manual".
When using multiple drivers, the first 2 letters of the error code may display "RH", "RJ", "RK", or "RM".
Error Code |
Error Message |
Cause |
Solution |
RHxx006 |
(Driver Name): (Port Name) - Received data has parity error |
An error occurred due to a lack of receiving data. The cause could be the noise or loose connection. |
Please check the noise suppression and connector's insertion. If Memory-Link method is used, please check if the Data Length/Parity Bit of host side and the display side have the same settings. |
RHxx007 |
(Driver Name): (Port Name) - Received data has framing error |
||
RHxx008 |
(Driver Name): This model does not use Ethernet |
An error occurred when a Ethernet driver is selected in GP-Pro EX as the [Device/PLC], but the project is transferred to a display model which cannot use Ethernet. |
Please check if the display unit supports Ethernet. If it does, please check if the Display Type settings in the GP-Pro EX editor are correct. |
RHxx009 |
(Driver Name): (Port Name) Cannot use the port |
An error occurred when two or more driver types are selected to an identical COM port. An error occurrs when the USB/SIO (RS-422/485) port flow control setting is not correct. |
Please check the [Port] settings in GP-Pro EX's [Device/PLC]. When you are using the USB/RS-422/485 conversion adapter, set [Flow Control] to [None]. |
RHxx010 |
(Driver Name): TCP port number ***** is overlapped, or it is not completed to close the last TCP connection |
TCP port number of the display unit side is overlapped, or the device/PLC is reset during communication. |
(1) Check that the UDP port number in [Ethernet settings] does not overlap with the UDP port number in [Communication Settings]. If the UDP port number is overlapped, allocate a different port number. (2) Reset the display unit. |
RHxx011 |
(Driver Name): Connection was closed |
An error occurred in the connection environment during communication. |
Please check if the network environment is normal. Please specify the cause via procedures such as directly connecting PC, display unit and device/PLC, and then checking if IP address is recognized via PING command. |
RHxx012 |
(Driver Name): UDP Port number is overlapped |
An error occurred when UDP port number of touch panel side is overlapped. |
Check that the UDP port number in [Ethernet settings] does not overlap with the UDP port number in [Communication Settings]. If the UDP port number is overlapped, allocate a different port number. |
RHxx013 |
(Driver Name): COM1: The 9th pin has not been set to VCC (5V Power Supply). Please check your cable or connected equipment. |
9th pin of COM1 is connected as RI input. (For example, set to use Isolation Unit (RS-232C Type)) |
Please designate [RI] in [RI/VCC] settings of GP-Pro EX's [Device/PLC]. |
RHxx033 |
(Node Name): Error has been responded for initial communication command (Error Code: (Decimal)[(Hex)]) |
Device/PLC is returning an error code on a communication request from the display unit. |
Please check the device/PLC manual for details on receive error codes. |
RHxx034 |
(Node Name): Error has been responded for device read command (Error Code: (Decimal)[(Hex)]) |
Device/PLC is returning an error code on a read request from the display unit. |
|
RHxx035 |
(Node Name): Error has been responded for device write command (Error Code: (Decimal)[(Hex)]) |
Device/PLC is returning an error code on a write request from the display unit. |
|
RHxx036 |
(Node Name): Error has been responded for device read command (Error Code: (Decimal)[(Hex)] There are out of range devices) |
Device/PLC cannot recognize the Read request of the address set via the display unit side, and return the error code. It might be set to request the address which is out of PLC address range on the display unit side. |
(1) Please check the manual of device/PLC in use for the detail of receiving error codes. (2) Please check if the address set is within the device/PLC device address range in use.*1 |
RHxx037 |
(Node Name): Error has been responded for device write command (Error Code: (Decimal)[(Hex)] There are out of range devices) |
The Device/PLC cannot recognize the Write request of the address set on the display unit side, and returns the error code. It might be set to request an address which is out of the PLC address range on the display unit side. |
|
RHxx038 |
(Node Name): Error has been responded for device read command (Error Code: (Decimal)[(Hex)] There are write only devices) |
Device/PLC cannot recognize the Read request of the address set via the display unit side, and return the error code. It might be set to request the write only address of device/PLC on the display unit side. |
(1) Please check the manual of device/PLC in use for the detail of receiving error codes. (2) Please check if the address is set to read the write only address. *1 |
RHxx039 |
(Node Name): Error has been responded for device write command (Error Code: (Decimal)[(Hex)] There are read only devices) |
The Device/PLC cannot recognize the Write request of the address set on the display unit side, and returns the error code. It might be set to request the read only address of device/PLC on the display unit side. |
(1) Please check the manual of device/PLC in use for the detail of receiving error codes. (2) Please check if the address is set to write to the read-only address. *1 |
RHxx040 |
(Node Name): Illegal response for initial communication command |
An error occurred on device/PLC side |
Please check that the communication settings or the connected device settings are specified properly. |
RHxx041 |
|||
RHxx042 |
|||
RHxx043 |
Checksum error response for initial communication command |
||
RHxx044 |
(Node Name): Checksum error response for device read command |
||
RHxx045 |
(Node Name): Checksum error response for device write command |
An error occurred on device/PLC side |
Please check that the communication settings or the connected device settings are specified properly. |
RHxx049 |
(Node Name): Unknown devices exist in read devices |
Wrong device and address are created via Indirect Address Designation. |
Please check if settings of Indirect Address Designation are within the recognizable address range. |
RHxx050 |
(Node Name): Unknown devices exist in write devices |
||
RHxx051 |
(Node Name): Out of range devices exist in read devices (Address: (Device Address)) |
In the Data Display (Text Display) or D-script (memcpy or memset), area from the start address to the end address is not within the address range. |
Please check if the settings which is across multiple addresses, such as Data Display (Text Display) or D-script, are within the address range.*1 |
RHxx052 |
(Node Name): Out of range devices exist in write devices (Address: (Device Address)) |
||
RHxx053 |
(Node Name): You cannot read the write only device (Address: (Device Address)) |
The Protocol driver detected read-out of the write only device, or write-in of the read only device |
(1) Please check the manual of device/PLC in use for the detail of receiving error codes. (2) Please check if the address is set to read the write only address. If Parts that perform reading operation such as Lamps and Data Display are used, please set the read address. |
RHxx054 |
(Node Name): You cannot write the read only device (Address: (Device Address)) |
||
RHxx065 |
(Node Name): TCP connection open error (IP Address: (IP Address)) |
IP address and port number of device/PLC are not recognized. |
(1) Please check the settings of IP address and Port number on display unit side and device/PLC side. (2) Please check if the network environment is normal. |
RHxx066 |
(Node Name): UDP target not found (IP Address: (IP Address)) |
||
RHxx067 |
(Node Name): Response timed out for initial communication command |
The causes could be the following:
|
(1) Please check if the communication settings of display unit side and device/PLC side are the same. Please refer to "GP-Pro EX Device/PLC Connection Manual" for the details. (2) Please reconfirm the wiring. Please check the cable and connector's insertion. About wire connection, please refer to "GP-Pro EX Device/PLC Connection Manual" for the details. When using COM 2, please check if Online Adaptor (CA4-ADPONL-01) is connected. (3) Please reconfirm the GP-Pro EX [Device/PLC Settings]. |
RHxx068 |
|||
RHxx069 |
(Node Name): Response timed out for device write command |
||
RHxx070 |
(Node Name): The cable has been disconnected or the target has been powered off |
The command cannot be sent due to the cause that the device/PLC power is not ON or cable is unplugged, etc. |
(1) Transferring to GP3**1 series using GP3**0 series. Check if the Display Type settings match the display model in use. (2) Please check if the device/PLC power is ON. (3) Please check if the cable wiring is correct, and if cable is connected properly. |
RHxx071 |
(Node Name): The extend unit (Unit Name) is not implemented |
The Expansion Unit is not recognized. |
Please check if the Expansion Unit is correctly attached. |
RHxx072 |
(Node Name): Illegal read request because this device has been off scan |
A read request was made through sampling, extended D-script, Pro-Server EX, to the device in off-scan mode. |
A read request was made through sampling, extended D-script, Pro-Server EX, to the device for which communication scan has been stopped. Turn OFF the appropriate bit*2 between LS9550 and LS9559 and start the communication scan of the connected device. |
RHxx073 |
(Node Name): Illegal write request because this device has been off scan |
A write request was made through a script, a touch, Pro-Server EX, to the device in off-scan mode. |
A write request was made through a switch, D-script, extended D-script, Pro-Server EX, to the device for which communication scan has been stopped. Turn OFF the appropriate bit*2 between LS9550 and LS9559 and start the communication scan of the connected device. |
RHxx084 |
(Node Name): Too many requests to write. The request was ignored. |
A write operation was continued at timing which exceeds the processing speed of the communication driver. Example) For a connected device set up with a baud rate of 9600, if you continue to write with the same timing as tag scan counter updates. |
Check if a D-script or other setting has been specified which continues writing at fast speed. This error may occur when you use D-script with a bit that changes ON/OFF at a high rate (such as the LS9400 tag scan counter) to continually write to a device that communicates at a low speed (such as 9600 bps). |
RHxx085 |
(Node Name): Too many requests to read. The request was ignored. |
A read operation was continued at timing which exceeds the processing speed of the communication driver. Example) When reading continuously, with the same timing as tag scan counter updates, from a connected device that has a baud rate of 9600. |
Check if a D-script or other setting has been specified which continues reading at fast speed. This error may occur when you use D-script with a bit that changes ON/OFF at a high rate (such as the LS9400 tag scan counter) to continually read from a device that communicates at a low speed (such as 9600 bps). |
RHxx088 |
COM1: The station number of Multilink function duplicates that of another device |
The station number of Multilink function duplicates that of another device. |
Verify the station number and re-set it so it does not duplicate. |
RHxx089 |
COM1: The address of the Multilink communication information is different from the other station |
The address of the Multilink communication information is different from the other station |
Set the Multilink communication information address to the same address on the Multilink Network. |
RHxx090 |
Response timed out from external device |
Multilink communication surveillance timeout lapsed (60 seconds). |
Verify network. |
RHxx091 |
COM1: Checksum error response for Multilink command |
Checksum error occurs. |
Verify communication settings. |
RHxx092 |
COM1: Failed to update the Multilink communication information |
Failed to update the Multilink communication information |
Verify Multilink communication information and communication settings |
RHxx093 |
COM1: Since cannot join to Multilink token, the request was unreceivable |
Write request and read requests occurred (except for read requests that run all the time). Communication has failed for 2 hours. |
Add the display unit to the list of Multilink stations. Check if any display units are monopolizing the PLC for more than 2 hours. |
*1 If the error occurred in all screens, please check the addresses set via functions which operate in all screens, such as System Data Area, Alarm, Global D-script, Global Window and Sampling (Historical Trend Graph). To check the addresses, from the System Settings in GP-Pro EX, select [Peripheral List] and see [List of Device/PLC Management Addresses].5.4.13 System Settings [Peripheral List] Settings Guide
If the error occurred in specific screens, please check the addresses via functions which operate in specific screens.
*2 The setting range of the bit addresses for controlling running and stopping communication scans are internal device addresses LS9550 to LS9557. Each device/ PLC address starting from Bit 0 is assigned sequentially to each driver's device/PLC starting from the first unit.
Example, you can set the bit addresses of LS9550 to control communication scans for units 1 to 16 in Driver1.
LS9550
Bit 0: Scans ON/OFF Driver1's first PLC.
Stops the scan (scans OFF) of Driver1's first PLC by turning ON Bit 0. Turn OFF Bit 0 to resume the scan.
You cannot stop the communication scan of a device specified with the System Area Start Address. However, if you are not using the System Data Area, you can stop the communication scan.5.4.6 System Settings [Display Unit] - [System Area] Settings Guide
You can set the LS area addresses with 32 bits on some devices/PLCs. In this case, the bottom 16 bits are used for bit addresses controlling the communication scan.
When you turn OFF the communication scan, the displayed part's data will remain. However, if you change screens and then display the screen again, the part's data will not be displayed.
Errors starting with RAAA (Application errors)
The following error is displayed during simulation.
Error Code |
Error Message |
Cause and Troubleshooting |
Browse |
|||||||||||||
RAAA001 |
No project data exists. (Transfer a project.) |
No project file exists. Transfer a project. |
|
|||||||||||||
RAAA002 |
The project data size exceeds the capacity. |
The project data size exceeds the maximum capacity*. Or, the number of screens exceeds 16,000 files. Reference the GP-Pro EX Project Information, and make sure it does not exceed the general capacity. * The maximum capacity of the project data size varies depending on the Display model. (Example: 8 MB for GP-3500T). |
||||||||||||||
RAAA003 |
The project data is invalid. (Transfer the project again.) |
There is an error in the project file. Transfer the project again. |
|
|||||||||||||
RAAA004 |
The system screen is invalid. (Execute forced transfer.) |
The system screen does not exist or is invalid. Force a transfer. |
||||||||||||||
RAAA005 |
The specified initial screen number does not exist. |
The screen cannot display because the screen number designated in the Initial Screen Settings does not exist in the project. Change the initial screen number or add the screen. The screen number designated in the parentheses is displayed. |
|
|||||||||||||
RAAA006 |
Project contains unsupported functions and cannot be displayed. |
The current model includes functions which the runtime program cannot recognize. Please remove the unsupported function and transfer again. The editor and runtime versions may not match. Update the runtime version. |
- |
|||||||||||||
RAAA007 |
The no. of parts in the screen exceeds the limit. (MAX 384) |
The number of parts that can be operated on a single screen has reached the upper limit. The number of parts exceeds the limit during a screen change or when opening a window. Make sure to set parts within the permitted range. |
|
|||||||||||||
RAAA008 |
The font ( **** ) does not exist. (Transfer the font with the project.) |
The font you are trying to display does not exist in the system. Download the font into the system. The following table shows the font names.
|
||||||||||||||
RAAA010 |
A CF/SD card is not inserted, or the CF card hatch is open. |
A CF Card/SD Card is not inserted, or the CF Card cover is open, so unable to access the CF Card/SD Card. Insert a CF Card/SD Card. Or close the CF card cover. |
|
|||||||||||||
RAAA011 |
Failed to start from the CF/SD Card. |
Despite DIP SW1 being turned ON, the necessary files to start from the CF Card/SD Card do not exist. Or the necessary file may have an error. Copy the startup project to the CF/SD Card again. Or, if the settings to access the CF/SD Card are not created intentionally, verify the following. Previous settings may still remain.
For the GP4000 series (excluding the GP-4100 series), the SD Card startup program may be damaged. Force the transfer of the system. |
||||||||||||||
RAAA012 |
The project data contains functions that are not supported by this model. |
When running on display unit: The current model includes functions which the runtime program cannot recognize. Change to a model that supports the feature or remove it. Please refer to the following for supported features. When running simulation: Simulation does not support all features. You can only simulate supported features. Please refer to the following for unsupported features. |
- |
|||||||||||||
RAAA013 |
USB storage location not found. |
The USB storage device cannot be accessed due to the poor connection or recognition problem. Check if the USB storage device is connected. If connected, disconnect and then reconnect the USB storage device. |
||||||||||||||
RAAA014 |
Failed to start from USB storage. |
The file required for startup from the USB storage device does not exist. Or the necessary file may have an error. Check that the startup file "r:boot.cfg" and the "r:pj001" folder are located directly under the USB storage. For the GP4000 series (excluding the GP-4100 series) and LT4000 series, the USB storage startup program may be damaged. Force the transfer of the system. |
||||||||||||||
RAAA015 |
Unable to go off-line. |
Offline mode files do not exist, or are damaged. Please run a forced transfer. |
- |
|||||||||||||
RAAA016 |
Bitmap font unavailable. (Please transfer a project with this font.) |
You are using a font that is not registered in the [Image Font] settings. Add fonts used in the project, and transfer again. |
||||||||||||||
RAAA017 |
Not supporting the format of the CF/SD Card being used. |
External storage has been formatted in a format not supported. If external storage with capacity over 2GB has been formatted as FAT16, reformat as FAT32. |
||||||||||||||
RAAA018 |
Unable to use USB storage. Its capacity level is unsupported. |
|||||||||||||||
RAAA019 |
Because the image font is set, it is not possible to display it. |
When the System Settings [Synchronize with Text Table] are turned ON, the Data Display (Text Display) cannot use image fonts. Please change to Standard Font or Stroke Font. |
||||||||||||||
RAAA022 |
Cannot remove the "SD Card". |
Unable to remove the SD Card because the SD Card is being accessed. Stop the function that is accessing the SD Card. |
||||||||||||||
RAAA023 |
Cannot remove the "USB storage". |
Unable to remove the USB storage because the USB storage is being accessed. Stop the function that is accessing the USB storage. |
||||||||||||||
RAAA050 |
When changing the clock data, the data write to the clock IC failed. The IC chip may be broken. Set up value is invalid as clock data. Please specify proper clock data. |
- |
||||||||||||||
RAAA051 |
Low battery |
Rechargeable battery has run out. Supply power to the display unit and fully recharge the battery. Battery will be charged up to the level at which it can run backup 24 hours after the power is turned ON. It takes approximately 96 hours (4 days) to complete charging. |
|
|||||||||||||
RAAA052 |
There is a problem with the hardware. |
(****) indicates where the problem is in the Display. For example, when an error occurred with the LAN port, "LAN" is displayed. This may be caused by a fault in the display unit. Please contact the Pro-face customer care center. |
- |
|||||||||||||
RAAA053 |
Running out of power in the backup battery. Please change the battery. |
You have reached approximately one month before the rechargeable battery runs out. It is necessary to replace the battery. For details regarding the replacing method, refer to the Hardware Manual. |
Hardware manual of the display unit you are using |
|||||||||||||
RAAA054 |
The backup data has been deleted. |
Data in the backup memory (SRAM) has been deleted due to the backup battery running out. |
- |
|||||||||||||
RAAA055 |
Clock data has been initialized. |
The clock data has been initialized due to the clock data running out. |
|
|||||||||||||
RAAA060 |
Failed to save backup data |
Failed to save backup data to internal memory. Please run back up again. If this occurs frequently, the maximum possible number of saves to internal memory may have been exceeded, or the unit is damaged. Please contact the Pro-face customer care center. |
- |
|||||||||||||
RAAA061 |
Failed to read backup data |
There is a problem with the backup data saved to internal memory. Previously, while saving the backup the power may have been disconnected. Please run back up again. If this occurs even though the backup is run again, the maximum possible number of saves to internal memory may have been exceeded, or the unit is damaged. Please contact the Pro-face customer care center. |
||||||||||||||
RAAA062 |
Unable to use backup data |
Unable to save or read backup data in internal memory. The maximum possible number of saves to internal memory may have been exceeded, or the unit is damaged. Please contact the Pro-face customer care center. |
||||||||||||||
RAAA063 |
Failed to get clock data |
Device/PLC is not supporting updating the clock. Please check if the device/PLC supports clock updates. |
||||||||||||||
RAAA100 |
The system start device address is incorrect. |
The system device start address is not set correctly or has an error. Set the correct address while in offline mode, or transfer a project. |
|
|||||||||||||
RAAA101 |
Illegal/Undefined Device Address |
Appears when the device address used by a part or function is invalid. Edit the device address, and transfer again to recover. |
- |
|||||||||||||
RAAA102 |
Failed to read from the Device/PLC. |
Failed to read from the device/PLC. Confirm the connection status, such as whether the communication cable is disconnected, etc. The part name is entered in the parentheses. |
- |
|||||||||||||
RAAA103 |
The specified address is incorrect. |
The designated address is incorrect. Make sure to set the correct address. The part name is entered in the parentheses. |
- |
|||||||||||||
RAAA110 |
Remote PC Access error. Unable to recover. |
An internal initialization error or system error occurred. Restart the display unit, or review the screen settings. |
|
|||||||||||||
RAAA111 |
Unable to certify Remote PC Access server. |
The password is invalid. Check if the password matches the password specified on the Server PC. |
||||||||||||||
RAAA112 |
Failed to connect to Remote PC Access server. |
No Server PC is found. Or failed to connect to the server. Check if the IP address matches with that for the Server PC. Check if the Server PC is active. Check the settings on the Server PC. Check if the Server PC Firewall is enabled. |
||||||||||||||
RAAA113 |
Connecting to Remote PC Access server. |
The previous disconnection process is not completed. Wait for a while (75 seconds maximum), and then retry connecting to the server. |
- |
|||||||||||||
RAAA114 |
Missing Remote PC Access license key code. Enter key code in offline mode. |
With GP-Pro EX, the RPA function key code has not been set up. Enter an RPA key code in offline mode. |
||||||||||||||
RAAA115 |
PC input is restricted. |
[Touch Input Inhibition] is set in the RPA window display. Disable the setting of [Touch Input Inhibition]. |
||||||||||||||
RAAA120 |
D-Script Error (The specified function does not exist or the function has an error.) |
The function called in the D-Script does not exist. Or there is an error in the function. Check the command format. |
|
|||||||||||||
RAAA121 |
D-Script Error (These functions are nested to 10 levels or more.) |
Functions in the D-Script are nested to 10 levels or more. Reduce the levels in the "if" and "loop" structures. * A nesting level is when function A calls function B, and then again when function B calls function C (function calling level). |
||||||||||||||
RAAA122 |
D-Script Error (An expression exists, that is not supported by this version.) |
An incompatible function was found in the project's D-Script. Update the runtime version. |
- |
|||||||||||||
RAAA123 |
D-Script Error (The SIO operation function is used in a condition where no Device/PLC has been set.) |
SIO Operation functions are used in a D-Script while the device/PLC settings are not set. Configure the device/PLC settings. |
||||||||||||||
RAAA124 |
The D-Script has an error. |
There is an error in the used D-Script. Check the command format. |
|
|||||||||||||
RAAA130 |
Global D-Script Error. (The Total Number of Global D-Scripts exceeds the maximum of 32.) |
The total number of Global D-Scripts exceeds the limit. The maximum number of Global D-Scripts available is 32 (each function also counts as one script). |
||||||||||||||
RAAA131 |
Global D-Script Error. |
The total of all devices in the Global D-Script exceeds the limit of 255 devices. Reduce the number of used devices by using the Memory Operation function, etc. |
||||||||||||||
RAAA132 |
Global D-Script Error (The specified function does not exist or the function has an error.) |
The function called in the Global D-Script does not exist. Or there is an error in the function. Check the command format. |
|
|||||||||||||
RAAA133 |
Global D-Script Error (These functions are nested to 10 levels or more.) |
Functions in the Global D-Script are nested to 10 levels or more. Reduce the levels in the "if" and "loop" structures. * A nesting level is when function A calls function B, and then again when function B calls function C (function calling level). |
||||||||||||||
RAAA134 |
Global D-Script Error (An expression exists, that is not supported by this version.) |
An incompatible function was found in the project's Global D-Script. Update the runtime version. |
- |
|||||||||||||
RAAA135 |
Global D-Script Error (The SIO operation function is used in a condition where no Device/PLC has been set.) |
SIO Operation functions are used in a Global D-Script while the device/PLC settings are not set. Configure the device/PLC settings. |
||||||||||||||
RAAA136 |
The Global D-script has an error. |
There is an error in the used Global D-Script. Check the command format. |
|
|||||||||||||
RAAA140 |
Extended D-Script Error (The total no. of functions exceeds the maximum of 255.) |
The total number of Extended Scripts exceeds the limit. The maximum number of Extended Scripts is 255. Reduce the number of scripts by combining two scripts into one, etc. |
||||||||||||||
RAAA141 |
Extended D-Script Error (The specified function does not exist or the function has an error.) |
A function called in the Extended Script does not exist. Or there is an error in the function. Check the command format. |
|
|||||||||||||
RAAA142 |
Extended D-Script Error (These functions are nested to 10 levels or more.) |
Functions in the Extended Script are nested to 10 levels or more. Reduce the levels in the "if" and "loop" structures. * A nesting level is when function A calls function B, and then again when function B calls function C (function calling level). |
||||||||||||||
RAAA143 |
Extended D-Script Error (An expression exists, that is not supported by this version.) |
An incompatible function was found in the project's Extended Script. Update the runtime version. |
- |
|||||||||||||
RAAA144 |
Extended D-Script Error (The SIO operation function is used in a condition where no Device/PLC has been set.) |
SIO Operation functions are used in a Extended Script while the device/PLC settings are not set. Configure the device/PLC settings. |
||||||||||||||
RAAA145 |
The Extended D-Script has an error. |
There is an error in the used Extended Script. Check the command format. |
|
|||||||||||||
RAAA150 |
Incorrect password. |
The security feature's password input is incorrect. Confirm that the input is correct (upper-case/lower-case letters, and so on) and enter the password again. |
||||||||||||||
RAAA151 |
Change the screen from the host. |
This appears when a screen change occurs from the PLC (host) by the forced screen change method, and you cancel the displayed password input. If you want to cancel, make sure to use a cancel notification bit and return to the previous screen from the PLC (host). |
- |
|||||||||||||
RAAA152 |
Cannot use the COM port. |
This appears when the COM port you are trying to use is already in use by another feature. Check the settings again. |
||||||||||||||
RAAA153 |
No dictionary file was found. |
The Japanese FEP dictionary file does not exist in internal memory or in the CF Card/SD Card. Transfer the project data again. |
- |
|||||||||||||
RAAA154 |
The specified filing data cannot be used with this project. |
This appears if the designated filing data does not match the project data when transferring filing data from external storage to backup memory (SRAM). Make sure to use filing data that matches the project data. |
||||||||||||||
RAAA155 |
The IP address duplicates that of another device. Please change the address of either this machine or the other. (IP:***.***.***.***, |
A machine with the same IP address exists on the network. Change the IP address of this machine or of the other machine. |
|
|||||||||||||
RAAA156 |
The COM port 9-pin could not be set to VCC (5V power supply). Please check your cable or connected equipment. |
The COM port 9-pin could not be set to VCC (5V power supply). Check the COM port connection cable and the machine it is connected to. Then reset the machine or verify the project's script settings are set to a 5V power supply. |
||||||||||||||
RAAA157 |
Cannot put the Device/PLC into offscan state when the system start device address is assigned to it. |
The connected device (main PLC) assigned to the system start device address has been set to off-scan mode. You cannot normally set the main PLC to off-scan mode. However, it can be set by changing the setting to not use the system data area. Otherwise, cancel the off-scan setting. |
|
|||||||||||||
RAAA158 |
Communication problem with the conversion adapter. |
No conversion adapter is connected although the system is set to Enable. Connect the conversion adapter. |
|
|||||||||||||
RAAA160 |
Function Expansion Memory is not installed (extended alarms). |
The project file is configured to use function expansion memory, but the display device does not have function expansion memory installed. There are two solutions below. Select the appropriate method.
|
- |
|||||||||||||
RAAA161 |
Function Expansion Memory is not installed (extended text table). |
The project file is configured to use function expansion memory, but the display device does not have function expansion memory installed. There are two solutions below. Select the appropriate method.
|
- |
|||||||||||||
RAAA162 |
It cannot be used due to abnormalities in the Enhanced Recipe Data (%s). |
An abnormality has occurred in the Enhanced Recipe Data for some reason. Transfer the Enhanced Recipe Data. |
- |
|||||||||||||
RAAA163 |
Save processing for the Enhanced Recipe Data (GroupID=%05d) did not complete. |
Element values edited with the Enhanced Recipe Data List are displayed when a project is terminated or when the display unit's power runs out while saving. Verify whether the edited element values are normal. |
- |
|||||||||||||
RAAA170 |
The password is invalid. |
The security feature's password input is incorrect. Confirm that the input is correct (upper-case/lower-case letters, and so on) and enter the password again. |
||||||||||||||
RAAA171 |
The password is a duplicate. |
The password has already been registered. Please set up a different password. |
|
|||||||||||||
RAAA172 |
User ID has not been registered |
Attempted to login with an unregistered User ID. Input the registered User ID. |
||||||||||||||
RAAA174 |
New password does not match |
Password entered in [Confirm Password] does not match [New Password]. Input the correct password. |
||||||||||||||
RAAA175 |
It is necessary to log in. |
You must login to update the security information. |
||||||||||||||
RAAA176 |
Duplicate User ID given. |
The same User ID has already been registered. Please set up a different User ID. |
|
|||||||||||||
RAAA177 |
Reached the maximum number. |
Exceeded the maximum number (100) of User ID's. Please remove unnecessary User ID's. |
||||||||||||||
RAAA200 |
Error occurred at system startup. Use the Transfer Tool to run a forced transfer operation. Error occurred at system startup. Use the Transfer Tool to run a forced transfer operation. |
Error found in the necessary files for startup. Use the Transfer Tool to run a forced transfer operation. |
- |
|||||||||||||
RAAA201 |
Error found in the font data. Use the Transfer Tool to run a forced transfer operation. |
- |
||||||||||||||
RAAA202 |
Error found in the LAN configuration file. Use the Transfer Tool to run a forced transfer operation. |
- |
||||||||||||||
RAAA203 |
There are issues in part of the project file. Use the Transfer Tool to run a forced transfer operation. |
- |
||||||||||||||
RAAA204 |
Did not succeed to start the Runtime System. Use the Transfer Tool to run a forced transfer operation. |
- |
||||||||||||||
RAAA205 |
Error occurred at system startup. Use the Transfer Tool to run a forced transfer operation. |
- |
||||||||||||||
RAAA206 |
Error occurred during initialization of the internal memory. Use the Transfer Tool to run a forced transfer operation. |
- |
*1IP addresses are shown as decimal, MAC addresses are shown as hexadecimal.
Error Code |
Error Message |
Cause and Solution |
Browse |
RAAE001 |
Unable to restore history data. |
If the history data file is damaged, the checksum of the history data file does not match, and the previous history data is abnormal, this error message appears. In this case, restart the display unit after clearing the history data. |
- |
RAAE002 |
History data too big. Unable to restore history data. |
If the volume of the stored history data file is larger than the size specified in the GP-Pro EX, and the previous history data is abnormal, this error message appears. Normally, this error does not occur but may occur when a history data file is exchanged. In this case, restart the display unit after clearing the history data. |
- |
RAAE003 |
There is no history to restore. Unable to restore history data. |
If no history data file exists and the previous history data file is also not normal, this error message appears. When the system fails while saving a history data file or a history data file is deleted, this error occurs. In this case, restart the display unit after clearing the history data. |
- |
RAAE004 |
Recent history data is corrupted. Restoring previous history data. |
If no history data file exists and the previous history data file is normal, this error message appears. When the system fails while saving a history data file or a history data file is deleted, this error occurs. In this case, restore the previously saved history data and then restart the display unit. |
- |
RAAE005 |
Recent history data is too big. Restoring previous history data. |
If the volume of the stored history data file is larger than the size specified in GP-Pro EX, and the previous history data is normal, this error message appears. Normally, this error does not occur but may occur when a history data file is exchanged. In this case, restore the previously saved history data and then restart the display unit. |
- |
RAAE006 |
Recent history data does not exist. Restoring previous history data. |
If the system failed while saving a history data file, this error message appears. When the history data file has already been opened by other software, or the history data file storage folder does not exist, this error occurs. In this case, the current history data cannot be saved. |
- |
RAAE007 |
Failed to save the backup file. |
This message appears when the system cannot open or fails to save the history data file. In this case, the current history data cannot be saved. |
- |
RAAE008 |
The write filter is enabled. A file cannot be output to a drive that has this setting enabled. |
The write filter (write protection) is set in Windows XP Embedded. In this case, the current history data cannot be saved. |
- |
RAAE009 |
[LanSys.cfg] File is missing. Using initial value. |
If no Lansys.cfg file exists, this error message appears. In this case, the local node name and port settings will be reset to the initial settings. Re-enter the local node name and port while in offline mode. |
- |
RAAE010 |
[system.cfg] File is missing. Using initial value. |
If no system.cfg file exists, this error message appears. In this case, all settings in [Display Unit] will be reset to the initial settings. Transfer the project file again. |
- |
RAAE011 |
[CF/SD Card] path is too long (MAX:200) |
The CF Card/SD Card reference destination path specified in the [Project (F)] menu [Property (I)] - [Destination Folder (C)] is too long. |
|
RAAE012 |
[USB Storage] path is too long. (MAX:200) |
The USB storage destination path is too long. From the [Project (F)] menu, point to [Information (I)], and click [Destination (C)]. |
Some error numbers staring with REAA are displayed when Pro-Server EX is used. For details on these errors, refer to Pro-Server EX Reference Manual.
Error numbers starting with REAA may not disappear from the display screen even when [Clear at Recovery] is specified for the display device off-line mode. The error message is cleared on screen change.5.4.2.3 Display Unit [Display] - Menu and Error Settings
Error Code |
Error Message |
Cause and Solution |
Browse |
REAA010 |
Transfer NPX changes: Unable to run Action/Data Transfer (***). Reason: *** |
NPX information does not match between the transmission source and destination nodes for the "Action/Data Transfer". Please transfer the network project to all associated nodes for the "Action/Data Transfer". |
- |
REAA011 |
Individual transfer setups do not match. As a result, unable to run Action/Data Transfer. |
[Compare NPX project on connection] setting does not match between the transmission source and destination nodes for the "Action/Data Transfer". In order to use the [Compare NPX project on connection] setting's [Changes] option, all associated nodes must be use the same setting. Please transfer the network project to all associated nodes. |
- |
REAA012 |
Data transfer information in the source and destination nodes do not match. |
NPX information does not match between the transmission source and destination nodes for the "Action/Data Transfer". Please transfer the network project to all associated nodes for the "Action/Data Transfer". |
- |
REAA013 |
Data transfer information in the source and destination nodes do not match. (Location does not match ***) |
NPX information does not match between the transmission source and destination nodes for the "Action/Data Transfer". Please transfer the network project to all associated nodes for the "Action/Data Transfer". |
- |
REAA014 |
Data transfer destination node and runtime versions are not compatible. |
Runtime version does not match between the transmission source and destination nodes for the "Action/Data Transfer". Please update the runtime version in all associated nodes for the "Action/Data Transfer". |
- |
REAA016 |
Could not use the *** port (number: ***) |
Opening the *** (UDP or TCP) port number ( *** ) failed. The system port number may have already been used. Please check the system port number and use available one. |
- |
REAA017 |
Attempted to access a write-protect area (***) |
You cannot write to the write-protected area (LS0000 to LS0019, LS2032 to LS2095, LS9000 to LS9999) using a D-script or across the network. Please do not write data to the write-protected area using a D-script or across the network. |
- |
REAA018 |
Attempted to access a device outside the address range ( *** ) ***) |
A device beyond the valid device range was accessed. Be sure to use the address in the device range. |
Enter the correct Transfer operation password. |
REAA021 |
An invalid ID has (Node, Device, Address) has been specified. |
An invalid ID was specified. Attempted to access a nonexistent device. Force the transfer of the files. |
|
REAA026 |
Illegal/Undefined Device Address |
An invalid device was specified. Attempted to access a nonexistent device. Force the transfer of the files. |
|
REAA029 |
Unable to use device's Device ID ([indirect device]) |
You are specifying a device ID that is not registered in the project or a device ID that is not the same series as the [Indirect Device]. Please specify a device ID that matches the [Indirect Device] series. When an indirect device address is specified to the following parts, after the device ID that does not exist is specified, when it is switched to a device ID that exists, an error message is displayed. An error message is displayed; however, subsequently, it operates properly.
|
|
REAA064 |
A communication error occurred during communication with the destination node. Please confirm that the network connection to the node has been properly established. |
A: Server is down. (Server is not running.) B: Network failure. C: Server is busy. GP-Viewer EX on another machine is retrieving screen and storage data. D: Server is busy. GP-Viewer EX on another machine is updating screen data on the server. |
Check that the network and cables between this display unit and the target unit are properly established and connected. When this display unit is an Ethernet Multilink slave, confirm that the master display unit is a compatible model. |
REAA065 |
The destination node did not respond within the specified time. 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. |
|
REAA071 |
Connection failed. Runtime versions do not match. |
Operation cannot be started because the runtime versions between the master and slave units are different. |
Forcibly transfer the system using GP-Pro EX. |
REAA072 |
Unable to run process. Ethernet Multi-link integrity check is incomplete. |
The connection availability check from the slave unit to the master unit may not be completed because the master and slave unit connection may not have established or has just been established. |
The connection availability check from the slave unit to the master unit may not be completed because the master and slave unit connection may not have established or has just been established. Check the connection between the master and slave units. Or, try the process again. |
REAA080 |
Can not load Web Server |
The system file may have been deleted. Forcibly transfer the system using GP-Pro EX. |
|
REAA081 |
Web Server is not transferred |
The system file may have been deleted. Forcibly transfer the system using GP-Pro EX. |
|
REAA082 |
Can not start Web Server |
The system file may have been deleted. Forcibly transfer the system using GP-Pro EX. |
|
REAA089 |
In the Ethernet Multilink Settings, this display unit's IP address or invalid one is set up as the Master IP Address. Please check the settings and transfer the project data again, or change this display unit's IP address. |
The slave display unit's master IP address is the IP address of this node, or the IP address is invalid. Consequently, communication cannot be started and runtime cannot be initiated |
Change the master GP's IP address in the message and transfer the screen project again. Or, change the IP address of this display unit. |
REAA090 |
Access to the master node denied. |
The IP address filtering function is enabled but the IP address of the display unit has not been registered. |
Register the IP address of the display unit. |
REAA091 |
Exceeded maximum communication capacity for Ethernet Multilink devices. |
The amount of communication traffic of the connected device may exceed the upper limit. |
Check the traffic volume. |
REAA092 |
Exceeded maximum number of slave connections. |
The number of connected slave display units may exceed the upper limit. |
Check that the number of connected slave display units is 16 or less. |
REAA093 |
Ethernet Multilink slave cannot use this feature. |
This function is not available with an Ethernet Multilink slave display unit. |
An Ethernet Multilink slave display unit cannot perform this function |
REAA094 |
Unable to communicate. Settings do not match the device/PLC configuration on the master. |
The configurations of the connected devices are different between the master and slave display units. |
Check the connected device configuration of the slave display unit. |
REAA095 |
Connection failed. System Language Settings do not match. |
The system language settings are different between the master and slave display units. |
Set the system language setting of the slave display units to the same as that of the master display unit. |
Error Code |
Error Message |
Cause and Solution |
Browse |
RFAA020 |
Password for send and receive is invalid. Validation failed |
Password for send and receive is incorrect. |
- |
Error Code |
Error Message |
Cause and Solution |
Browse |
RFAF001 |
Can not use Port |
An unusable port is specified as the Web Server port. Change the port number used by Web Server using GP-Pro EX or while in offline mode. Change the settings of the other function that is using the port number used by Web Server or stop Web Server. |
|
Unrecoverable Errors
Error Message |
Cause and Solution |
Browse |
Detected an unrecoverable error. To recover, touch Reset or restart the display unit. |
Touch [Reset] and restart the display unit. If the error is not resolved even after restarting, contact the "Pro-face Customer Care Center". |
- |
When the display unit's internal system will not start correctly
When there is a problem with the files related to starting the system, the following error messages will be displayed on the forced transfer screen. Transfer the system data again with the transfer tools.
For details about the transfer tools, please see 34.12.1 Transfer Settings Guide.
Error Message |
Affected Files |
Cause and Solution |
Start up Error: Boot.cfg |
BOOT.CFG |
Boot.cfg file, needed for startup, is deleted or damaged. Try a forced transfer of the project file. |
Start up Error: Default Font |
****** .FNT |
Default font data is deleted or damaged. Try a forced transfer of the project file. |
Start up Error: LanSys.cfg |
LANSYS.CFG |
LAN settings file is damaged. Try a forced transfer of the project file. |
Start up Error: System.cfg |
SYSTEM.CFG |
Files needed to start the system (system settings files) do not exist. Try a forced transfer of the project file. |
Start up Error: CF memory loader |
BOOT.CFG |
Abnormal Boot.cfg file data in the CF card during startup . Try loading again by changing the CF card or by another method. |
Start up Error: CF MOUNT Error |
- |
CF card read failed during startup. CF card read failed during startup. |
Start up Error: Runtime Load NG |
BOOT.CFG |
GP internal system data is deleted or damaged Try a forced transfer of the project file. |
Start up Error: Runtime Start NG |
- |
The following error may have occurred during runtime startup. Try a forced transfer of the project file.
|
Compulsion Transfer Mode (DipSW2=ON) |
- |
Forced transfer when dip switch 2 is ON.*1 |
Compulsion Transfer Mode |
- |
Forced transfer display that appears when touching the bottom-left or bottom-right part of the screen at startup.*1 |
*1This item does not indicate an error and is a screen that displays normally.
When the display unit's internal system will not start properly (when using GP-4100 series, GP-4201TM, or GP-4301TM)
When there is a problem with the files related to starting the system, the following error messages will be displayed on the forced transfer screen. Transfer the system data again with the transfer tools.
Error Message |
Affected Files |
Cause and Solution |
Error:Boot.cfg |
BOOT.CFG |
Boot.cfg file, needed for startup, is deleted or damaged. Try a forced transfer of the project file. |
Error:System.cfg |
SYSTEM.CFG |
Files needed to start the system (system settings files) do not exist. Try a forced transfer of the project file. |
Error:Runtime Load NG |
Run****.PAK |
Runtime system data is deleted or damaged. Try a forced transfer of the project file. |
Error:Runtime Start NG |
- |
The following error may have occurred during runtime startup.
|
Forced Transfer Mode |
- |
Forced transfer display that appears when touching the bottom-left or bottom-right part of the screen at startup.*1 |
*1This item does not indicate an error and is a screen that displays normally.
When an abnormal file is detected during the display unit's startup
When there is a problem with the files needed after the system starts up, the following error messages will be displayed on the normal transfer screen. After fixing the problem, transfer the files again with the transfer tools.
For details about the transfer tools, please see 34.11 Installing Only the Transfer Tool.
Error Message |
Cause and Solution |
Browse |
Cannot read the file ( **** ) required for startup. Please transfer the project data again. |
A file needed for startup could not be read. Transfer again and restore the system. The file name displayed inside the brackets is either abnormal or does not exist. |
- |
An illegal or undetermined Device Address exists ( ***** ). Please check the settings and transfer the project data again. |
Appears when the device address used by a part or function is invalid. The part or function name using the invalid address is displayed in the brackets. However, sometimes the brackets are not displayed. Edit the device address, and transfer again to recover. |
|
The number of devices/PLCs exceeds the maximum setting. Please check the settings then transfer the project again. |
The number of devices/PLCs exceeds the maximum setting. (Large-scale units: 4, medium-scale units: 2) Reconfirm the project settings and transfer it again. |
|
There are features unsupported by this model. Please check the settings then transfer the project again. |
This problem occurs when you create a new screen by selecting [GP-33** Series] for [Display Unit] and [Greater Than Or Equal To Rev*-4] for [Revision] and transfer the resulting project file to the GP-3300 series Rev 3 or earlier. You need to transfer a project file created with the setting of Rev. 3 or earlier. |
|
Unable to open I/O Driver with this Runtime version. |
The I/O driver version is out of date. Transfer an I/O driver that is version GP-Pro EX v2.51 or later. |
- |
Problem files detected at startup (when using GP-4100 series, GP-4201TM, or GP-4301TM)
When there is a problem with the files needed after the system starts up, the following error messages will be displayed on the normal transfer screen. After fixing the problem, transfer the files again with the transfer tools.
Error Message |
Cause and Solution |
Browse |
Cannot read the file ( **** ) required for startup. |
A file needed for startup could not be read. Transfer again and restore the system. The file name displayed inside the brackets is either abnormal or does not exist. |
- |
An illegal or undetermined Device Address exists ( ***** ). |
Appears when the device address used by a part or function is invalid. The part or function name using the invalid address is displayed in the brackets. However, sometimes the brackets are not displayed. Edit the device address, and transfer again to recover. |
|
The number of devices/PLCs exceeds the maximum setting. |
The number of devices/PLCs exceeds the maximum setting. Set the number of devices to 1, and transfer again. |
When creating a recipe (CSV data) index file in offline mode
Error Message |
Cause and Solution |
Browse |
CF/SD Card is missing. |
1. CF Card/SD Card is not inserted. 2. The CF/SD Card is not formatted. |
|
USB storage is missing. |
The USB storage is not inserted. Insert the USB storage. |
|
CSV file is missing. |
The FILE folder does not exist or there is no CSV data file in the folder. Or, there are CSV files but they are invalid for CSV transfer. Save the CSV data files onto external storage and try the transfer again. If an index file already exists, the original file will remain. |
|
Failed to write to file. |
The external storage is faulty or the index file is read-only. Use external storage which can read and write properly. If the index file is read-only, unprotect it and try writing again. |
While performing [Transfer from CF to SRAM] (or [Transfer from SD to SRAM]) in offline mode
Error Message |
Cause and Solution |
Browse |
This is a file of a different size from the SRAM size of the unit. |
The file size for the backup data transferred from the CF Card/SD Card and differs from the size of the backup memory (SRAM) used by the display unit. Transfer the backup data of the same size. |
- |
It is created with a model of a different data format or of a different version. |
The backup data created with a model having no data compatibility is transferred to the backup memory (SRAM). Transfer compatible backup data. |