Mitsubishi Electric MELSEC iQ-R Series User Manual page 618

Error Error name
code
4272H Debug related function
error
4275H Debug related function
error
4276H Debug related function
error
4277H Debug related function
error
4278H Debug related function
error
427AH Debug related function
error
427BH Debug related function
error
4282H Debug related function
error
36 ERROR CODES
616
36.4 List of Error Codes
Error details and cause
• The trigger logging specifying the device as a
trigger condition is being performed (data logging
status: RUN waiting (no collection), Condition
waiting (no collection), Start waiting (no
collection), Pause, Collecting, Trigger waiting
(collecting before trigger), Collecting after trigger,
or Saving the logging data).
• Auto logging is being performed.
• The function that cannot be executed during the
data logging (data logging status: RUN waiting
(no collection), Condition waiting (no collection),
Start waiting (no collection), Pause, Collecting,
Trigger waiting (collecting before trigger),
Collecting after trigger, or Saving the logging
data) was executed.
• The number of saved files exceeded the
specified number.
■When CPU Module Logging Configuration Tool is
used
• The data logging was started in a state where the
number of saved files has exceeded the specified
number. (The operation when the number of
saved files exceeded is set to "Stop".) Or, the
data logging was started in a state where the
number of saved files has exceeded the specified
number. (The operation when the number of
saved files exceeded is set to "Overwrite".)
• An attempt was made to register data logging in
a state where the saved file number has reached
its maximum, FFFFFFFF. Or, the number
reached to the maximum during the execution.
■When CPU Module Logging Configuration Tool is
used
• The data logging was started in a state where the
saved file number has reached its maximum,
FFFFFFFF. Or, the number reached to the
maximum during the execution.
• The common setting file is corrupted.
■When CPU Module Logging Configuration Tool is
used
• The data logging was started to the memory
where the corrupted common setting file exists.
• The data logging with the same file storage
destination is being performed (data logging
status: RUN waiting (no collection), Condition
waiting (no collection), Start waiting (no
collection), Pause, Collecting, Trigger waiting
(collecting before trigger), Collecting after trigger,
or Saving the logging data).
■When CPU Module Logging Configuration Tool is
used
• The data logging with the same file storage
destination is being performed (data logging
status: RUN waiting (no collection), Condition
waiting (no collection), Start waiting (no
collection), Pause, Collecting, Trigger waiting
(collecting before trigger), Collecting after trigger,
or Saving the logging data).
• The registration was performed with the internal
buffer capacity set to 0.
Action
• Change the trigger condition. Or, stop the trigger logging
being performed (data logging status: RUN waiting (no
collection), Condition waiting (no collection), Start waiting (no
collection), Pause, Collecting, Trigger waiting (collecting
before trigger), Collecting after trigger, or Saving the logging
data), and register another trigger logging.
■When CPU Module Logging Configuration Tool is used
• Change the trigger condition. Or, stop the trigger logging
being performed (data logging status: RUN waiting (no
collection), Condition waiting (no collection), Start waiting (no
collection), Pause, Collecting, Trigger waiting (collecting
before trigger), Collecting after trigger, or Saving the logging
data), and start another trigger logging.
• After the auto logging, replace the SD memory card and
execute again.
• Stop the data logging, and then execute the function.
• The number of files saved in the storage destination memory
has exceeded the setting value. Delete files, or change the
storage destination and then register.
■When CPU Module Logging Configuration Tool is used
• The number of files saved in the storage destination memory
has exceeded the setting value. Delete files or change the
storage destination, and then start the data logging.
• The saved file number in the storage target memory has
reached its maximum, FFFFFFFF. Delete files, or change the
storage destination and then register.
■When CPU Module Logging Configuration Tool is used
• The saved file number in the storage target memory has
reached its maximum, FFFFFFFF. Delete files or change the
storage target memory, and then perform the data logging.
• Write the common settings to the target memory again.
■When CPU Module Logging Configuration Tool is used
• Write the common settings to the target memory again.
• Stop the data logging destined for the same storage, and
then register. Or, change the storage destination of the file,
and then register.
■When CPU Module Logging Configuration Tool is used
• Stop the data logging destined for the same storage, and
then perform another data logging. Or, change the storage
destination of the file, and then register.
• Check and correct the internal buffer capacity setting.