Error | Error message | Action | Channel No. | |
code | storage | |||
|
| |||
|
|
|
|
|
| Channel (CH.No.1 to 2) to communicate with a controller is not set. |
| |
| Communication channel not set. | • After setting the Communication Settings on the GT Designer3, |
| |
480 | download it to the GOT. | *1 | ||
Set channel number on Utility. | ||||
| ||||
|
| • Change the channel assignment in the Communication Setting on the |
| |
|
| utility. |
| |
|
|
|
| |
487 | Please turn on the PLC and the | Turn the power of the PLC and GOT on again. |
| |
GOT again. |
| |||
|
|
|
| |
|
| Inactive channel No. has been set in the project data. |
| |
| Inactive channel has been | • Check whether any unnecessary channel No. has been set in the |
| |
489 | selected at Communication | project data. | *1 | |
| Settings. | • Check whether channel Nos. set in the project data are set in the |
| |
|
| Communication Settings. |
| |
|
|
|
| |
500 | Warning! | The voltage of the GOT |
| |
is low. | Replace the GOT |
| ||
|
|
|
| |
|
| The value that is input as clock data is out of the input enabled range. |
| |
510 | Clock data input out of range | In this case, the input value is not accepted. |
| |
Confirm the input range of the value to be input as clock data, and input |
| |||
|
|
| ||
|
| the proper value again. |
| |
|
|
|
| |
|
| The capacity for the buffering area is insufficient in the build in flash |
| |
520 | Insufficient Flash ROM capacity | memory |
| |
|
| • Confirm whether there are no mistakes in specified buffering area size. |
| |
|
|
|
| |
| Insufficient user memory (RAM) | The capacity for the buffering area is insufficient in the user memory |
| |
521 | (RAM) |
| ||
capacity |
| |||
|
| • Confirm whether there are no mistakes in specified buffering area size. |
| |
|
| The old file of different contents has been deleted and a new file has been |
| |
522 | Unnecessary file deleted to | created. |
| |
create new file. | Note that the old file is deleted and the new file is created if the file of the |
| ||
|
| same name with different contents exists when creating files. |
| |
|
|
|
| |
524 | Device writing error. | Error occurred while writing in the device. |
| |
Correct device. | Correct the device. |
| ||
|
|
|
| |
525 | Unable to read/write alarm log | Unable to read the alarm log file saved by the different project. |
| |
files under different projects. | Confirm where to store the alarm log file and alarm log file. |
| ||
|
|
|
| |
526 | File conversion failed. | The file specified for the file conversion does not exist. |
| |
Check the settings for specifying a file to be converted. |
| |||
|
|
| ||
|
|
|
| |
| Error in SRAM. Failed to write | The error may be caused by a failure in the GOT main unit. Please |
| |
528 | consult your local Mitsubishi (Electric System) Service center or |
| ||
data. |
| |||
|
| representative. |
| |
529 | Data error in SRAM. | Error in SRAM data due to battery voltage low, etc. |
| |
Check the battery life. | Confirm the battery status. |
| ||
|
|
|
| |
| Improper monitor device. | The channel of the specified monitor target does not exist or the channel |
| |
530 | is not the monitor target. |
| ||
Confirm monitor channel. |
| |||
|
| Confirm the monitor target channel of the screen data. |
| |
535 | Cannot open image file. | Confirm whether any file exists in the SD card or USB memory. |
| |
|
|
|
| |
| Image file error or invalid file | • Confirm whether image files in the SD card or USB memory are |
| |
536 | normal. |
| ||
format. |
| |||
|
| • Confirm whether any image file of invalid format is stored. |
|
18 - 18 | 18. TROUBLESHOOTING |
| 18.2 Error Message and System Alarm |