Corrective Actions To Resolve Errors; List Of Errors During Gx Works2 Online Operation - Mitsubishi Electric M800VW Series Manual

M800V/M80V Series PLC Development Manual
5 Peripheral Development Environment (GX Works2)

5.13 Corrective Actions to Resolve Errors

5.13 Corrective Actions to Resolve Errors

5.13.1 List of Errors during GX Works2 Online Operation

When an error is generated on GX Works2, the following dialog is displayed. The dialog displays error messages and error
status. Note that error status inappropriate for CNC may be displayed since some displayed error messages are meant for
MELSEC PLC. Status is displayed as the last 4 digits of the display number.
(2) Error status
CAUTION
When an error is generated in GX Works2 online function, error messages may not represent the error status of the
CNC controller correctly.
Refer to the following error list.
The following table shows the cause and remedy of errors generated during online operation with CNC controllers.
For information on other errors, refer to "Help of GX Works2".
(*) Interpret the "PLC" in the messages to "CNC controller".
Status Message
The executed function is not supported.
2056 Please check the manual and other
documentation.
The executed function is not supported.
4001
Please check the manual and other
4002
documentation.
Writing of data which exceeds the ca-
pacity of the PLC was attempted. Exe-
cute again within the capacity of the
4005 PLC.
Cannot write because the PLC is exe-
4010 cuting a RUN command. Stop the PLC,
then execute again.
The applicable drive is not ready. Check
4021 the applicable drive, then execute
again.
A file which does not exist in the PLC
4022 was specified.
(1) Error
message
Cause
The writing during RUN function was
executed.
An operation not supported by the spec-
ifications was attempted.
The maximum number of steps that can
be executed with NC has been exceed-
ed.
The PLC of the NC is running.
The specified target memory does not
exist or is not in a usable status.
Ladder program writing during RUN
was attempted to nonexistent sequence
program.
227
Remedy
Do not execute the writing during RUN
function.
Check the operation procedures.
Check the size of execution area. (Re-
fer to "5.6.4.4 Other Operations and
Checks on Error", "5.7.4.4 Other Oper-
ations and Checks on Error")
Reduce the number of steps for the rel-
evant sequence program to be execut-
ed with reference that value.
After stopping the PLC of the NC, start
execution again.
Change the target memory.
Check the editing program whether it
exists in NC or not.
IB-1501614-B