Mitsubishi Electric MELSEC iQ-R Series User Manual page 610

Process cpu module
Hide thumbs Also See for MELSEC iQ-R Series:
Table of Contents

Advertisement

Error
Error name
code
40BDH
SFC file related error
40BEH
SFC file related error
40C0H
Label communication error
40C1H
Label communication error
40C2H
Label communication error
40C3H
Label communication error
40C4H
Label communication error
40C5H
Label communication error
40C6H
Label communication error
40C7H
Label communication error
40C8H
Label communication error
40C9H
Label communication error
40CAH
Label communication error
40CBH
Label communication error
40CCH
Label communication error
36 ERROR CODES
608
36.4 List of Error Codes
Error details and cause
• Online change (SFC block) execution error
• The program cannot be changed online because
the part to be changed has an active step (a step
holding operations).
• The specified label name does not exist.
• Label access with a label name has failed
because the specified array element number is
outside the range.
• Label access with a label name has failed
because the bit array type label is not specified
by bit specification.
• Label access with a label name has failed
because the word array type label is not specified
by word specification.
• Label access with a label name has failed
because the number of labels used in the
program exceeded its limit.
• Label access with a label name has failed
because the global label setting file and global
label assignment information do not match.
• The request execution has failed because the
global label is being modified by the CPU module
specified.
• The request execution has failed because the
global label is being modified by the CPU module
specified.
• Although changes of the global label were written
to the programmable controller, the reflection
operation (STOP  RUN or Power-on and
RESET) of the global label setting file is not
performed.
• The request cannot be executed because the
data in the global label setting file being
processed and the specified consistency check
data are not the same.
• Registration of a label definition has failed
because the number of registered labels reached
its limit.
• A label definition could not be registered because
the registration target memory capacity has been
exceeded its limit.
• A label definition could not be changed, added, or
deleted because the label communication data
does not exist in the CPU module.
■When CPU Module Logging Configuration Tool is
used
• An attempt was made to change, add, or delete
labels without creating the label communication
data.
• Data are not written to the CPU module because
the data type of the specified label does not
match the size of the write data.
• Online program change has failed because the
global label setting file before modification and
the global label assignment information do not
match.
Action
• Read the program from the CPU module to match it with that
of the engineering tool, and then execute the online program
change again.
• After setting the operating status of the CPU module to
STOP, write the SFC program to the programmable
controller.
• Omit the step from the part.
• Deactivate the step.
• Check the label setting. If the "Access from External Device"
checkbox is not selected, check the checkbox.
• Specify the array element number within the set range.
• Specify the label by bit specification, and access again.
• Specify the label by word specification, and access again.
• Reduce the number of labels in the program, and access the
labels multiple times.
• Check the access from an external device of the specified
global label setting, and write the global label setting file and
the global label assignment information to the programmable
controller together.
• Execute the label access again after a while.
• After a while, write the data to the programmable controller/
execute online change or execute the label access again.
• Perform the reflection operation (STOP  RUN or Power-on
and RESET) of the global label setting file.
• Correct the details of the global label setting, and write the
file to the programmable controller again.
• Reduce the number of registered labels with the "Access
from External Device" checkbox selected.
• Reduce the number of registered labels with the "Access
from External Device" checkbox selected.
• If the data memory is specified as the registration target
memory, change the memory to the SD memory card.
• Change the settings of the functions that use the registration
target memory.
• Write the label communication data to the programmable
controller.
• Change the size of data written from the external device
(SLMP/MC protocol device) so that it matches the data type
of the label in the specified CPU module.
• Write the global label setting file and the global label
assignment information to the programmable controller
together after modification.

Advertisement

Table of Contents
loading

Table of Contents