Mitsubishi Electric MELSEC iQ-R Series User Manual page 619

Error Error name
code
4283H Debug related function
error
4288H Debug related function
error
4289H Debug related function
error
428AH Data logging function error
428CH Data logging function error
4293H Debug related function
error
4294H Debug related function
error
42C0H Redundant system related
error
42C1H Redundant system related
error
42C2H Redundant system related
error
42C3H Redundant system related
error
42C4H Redundant system related
error
42C5H Redundant system related
error
Error details and cause
• An attempt was made to register trigger logging
in a state that the specified number of records
before trigger has exceeded the number of
records that can be collected within the internal
buffer capacity.
• The request cannot be executed because the
number of characters used in the name of the
specified file exceeded its limit.
• Items that cannot be set as data collection
conditions are set.
• The data logging has started while
 Data is being written to the programmable
controller online.
 The global label assignment information is
being written to the programmable controller
(data memory).
Execution fails because any of the following files
does not exist.
• CPU parameter file
• Global label setting file
• Program file with the target program name
• Execution fails because the internal buffer
exceeds its maximum capacity.
• Execution fails because the settings of internal
buffer capacity has been changed during the
execution of functions that consume the internal
buffer.
• The SFC program was written by the online
change to the CPU module that does not support
the SFC program in the redundant mode.
• Since the operation mode is changed or the
systems were switched during the initial
processing or the initial processing (when
switched to RUN), it takes time to complete the
processing.
• The memory copy function is executed to the
CPU module that does not support the selection
writing of program restoration information while
no program restoration information is in the CPU
module of the control system.
• The request cannot be executed because the
other system is not a standby system.
• The request cannot be executed because the
operation is not supported by the other system.
• In a redundant system with redundant extension
base unit, access to a module on an extension
base unit is attempted when the standby system
is specified in "Specify Redundant CPU" in the
"Specify Connection Destination" window.
• In a redundant system with redundant extension
base unit, access to a module on an extension
base unit, such as a file operation, is attempted
either connecting the device directly to the CPU
module of the standby system or via a module on
the main base unit of the standby system.
• In a redundant system with redundant extension
base unit, access to other stations via a module
on the main base unit of the standby system and
a module on an extension base unit is attempted.
Action
• Check and correct the internal buffer capacity setting.
• Reduce the number of records before trigger.
• Rename the file within 61 one-byte characters (including
underscore, serial number (8 digits), period, and extension),
and execute the request again.
• Check and correct the data collection condition setting.
• Start the data logging after the online data write to the
programmable controller has completed.
• Start the data logging after the writing of the global label
assignment information to the programmable controller has
completed.
Write the following files to the CPU module.
• CPU parameter file
• Global label setting file
• Program file with the target program name
• Check and correct the settings of internal buffer capacity, and
then try again.
• Deactivate the functions that consume the internal buffer,
and then try again. Or, restore the internal buffer capacity to
the previous state, and then try again.
• Check that the SFC program is not written to the CPU
module that does not support the SFC program in the
redundant mode.
• Check whether the processing ends or not after a while.
• Take measures to reduce noise.
• If the same error code is displayed again even after the
redundant system is restarted, the possible cause is a
hardware failure of the CPU module, redundant function
module, or tracking cable. Please consult your local
Mitsubishi representative.
• Execute the memory copy after the program restoration
information is written to the CPU module of the control
system.
• Replace the CPU module of the control system with the one
that supports the selection writing of program restoration
information.
• Change the other system to a standby system and try again.
• Replace the CPU module with the one that supports the
requested operation and try again.
• Specify the control system in "Specify Redundant CPU" in
the "Specify Connection Destination" window and access a
module on an extension base unit.
• Access a module on an extension base unit either
connecting the device to the CPU module of the control
system directly or via a module on the main base unit of the
control system.
• Access other stations via the control system in a redundant
system with redundant extension base unit.
36 ERROR CODES
36.4 List of Error Codes
36
617