T.7.2 System Errors and Errors Displayed in Offline Mode

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	Cause and Troubleshooting
Start up Error: 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	Default font data is deleted or damaged. Try a forced transfer of the project file.
Start up Error: LanSys.cfg	LAN settings file is damaged. Try a forced transfer of the project file.
Start up Error: 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: SD memory loader	Abnormal Boot.cfg file data in the SD card during startup. Replace the data on the SD card.
Start up Error: SD MOUNT Error	Failed to read SD card during SD card startup. Try loading again by changing the SD card or by another method.
Start up Error: Runtime Load NG	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. Default font load error User font load error.
Compulsion Transfer Mode (Panel Touch)	Forced transfer display that appears when touching the bottom-left or bottom-right part of the screen at startup. ^*1

When the display unit's internal system will not start properly (when using 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 Troubleshooting	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 models: 4, medium-scale models: 2) Reconfirm the project settings and transfer again.	4.4.14 System Settings [Peripheral List] Settings Guide
Unable to open I/O Driver with this Runtime version.	The I/O driver version is out of date. Check the runtime version, and transfer an I/O driver of a compatible version again.	-

Error Message	Cause and Troubleshooting	Browse
Cannot read the file required for startup. Reset and transfer the project again.	A file needed for startup could not be read. System information in the system card is not correct. Reset and transfer the project data again.	-
System Card is missing. The system card is not inserted.	Insert the system card and restart the display unit.	-
System Card is write-protected.	Cancel the write protection.	-
Security data is invalid. Reset and transfer the project again.	The security information is not correct. Reset and transfer the project data again.	-
Invalid password. Too many attempts. Reset and transfer the project again.	Incorrect passwords or user IDs were entered 5 times. Reset and transfer the project data again.	-

When an abnormal file is detected during startup (For GP6000, GPH6000, ST6000 2nd Gen series)

Error Message	Cause and Troubleshooting	Browse
Unable to load file [RootFrame.dll].	If the rootFrame.dll file is damaged or does not exist, this error message appears. In this case, re-install WinGP.	38.3.2 Installing/Uninstalling WinGP
This application has failed to start because **** .dll was not found. Re-installing the application may fix this problem.	If the WinGP system configuration file is damaged or does not exist, this error message appears. In this case, re-install WinGP.	38.3.2 Installing/Uninstalling WinGP
[.ini] Initialization file is missing. Starts up with default values.	If the PCRuntime.ini file is damaged or does not exist, this error message appears. In this case, the system will start after all settings in [Display Unit] - [WinGP Settings] are reset to the initial settings. Transfer the project file again. This message may appear if you have multiple WinGP instances running, or if you are running WinGP and GP-Viewer EX simultaneously. Exit the target application and try restarting the application.	-
Startup canceled because of error. The program is abnormally terminated.	If an error occurs for an unexpected reason during startup, this error message appears.	-
Please restart Windows.	After installation of WinGP, if you try to start WinGP without restarting Windows, this error occurs. Restart Windows first, and then start WinGP.	-
Cannot continue because the install path exceeds 200 characters.	If the WinGP installation folder is in a low-level directory or the path name is too long, this error message appears. Uninstall WinGP once, and then re-install it in a directory whose path name is within 200 characters.	38.3.2 Installing/Uninstalling WinGP
Unable to use the WinGP/API communication function. WinGP/API communication function requires installation of either the WinGP SDK or Pro-Server EX. Please confirm one of these is installed.	If the API communication is enabled and WinGP SDK has not been installed, this error message appears. In this case, re-install WinGP or install Pro-Server EX.	38.3.2 Installing/Uninstalling WinGP
Project Display Unit Setting: *** . Connected Display Unit: *** . Change display unit in the project settings and then run transfer operation.	If the model specified in a project does not match with the model of the copy destination, this error message appears. In this case, change the model specified in the project before executing the copy operation.	4.4.1 System Settings [Display] Settings Guide

If an error is detected in the connection key setting during system startup, the following error message will display.

Error Message	Cause and Troubleshooting	Browse
CF/SD Card is missing.	Cannot recognize the SD Card. 1. Correctly insert the SD Card into the SD Card slot on the display unit. 2. Make sure that the SD Card has been formatted using a file format compatible with the display unit.	M.7.2 Creating an index file for the recipe in the external storage 4.7 Usable External Storage
USB storage is missing.	Cannot recognize the USB storage. 1. Connect the USB storage to the display unit. 2. Make sure that the USB storage has been formatted using a file format compatible with the display unit.
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.

Error Message

Cause and Troubleshooting

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 SD Card 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.

Error Message	Cause and Troubleshooting
Detected an unrecoverable error. To recover, touch Reset or restart the display unit.	Touch [Reset] and restart the display unit. If restarting does not resolve the error, contact customer support.