hit counter script

Mitsubishi Electric FX5 User Manual page 436

Melsec iq-f series
Hide thumbs Also See for FX5:
Table of Contents

Advertisement

Error
Error name
code
41CDH
File related error
41D0H
File related error
41D8H
File related error
41DFH
File related error
41EBH
File related error
41FBH
File related error
41FEH
File related error
4269H
Any other error
4270H
Data logging
function error
4271H
Data logging
function error
4276H
Data logging
function error
4277H
Data logging
function error
4278H
Data logging
function error
APPX
434
Appendix 3 Error Code
Error details and cause
• An access to the file is prohibited in the system.
■When CPU Module Logging Configuration Tool is used
• The data logging was started in a state that files (or folders)
cannot be created or accessed because a file (or folder)
with the same name exists. Or, files (folders) cannot be
created or accessed while the data logging is being
performed or the logged data is being saved.
• The specified drive (memory) has no free space. Or, the
number of files in the directory of the specified drive
(memory) has exceeded the maximum.
• The specified file is being accessed.
• The specified drive (memory) is write-protected.
• The file name path is too long.
• The specified file is already being processed by the
engineering tool.
• The SD memory card has not been inserted.
• The SD memory card is disabled.
• The SD memory card is disabled by SM606 (SD memory
card forced disable instruction).
■When CPU Module Logging Configuration Tool is used
• The data logging was started when the CPU module is in
the following state: no SD memory card is inserted; the
CARD LED is not on; or the SD memory card is forcibly
disabled.
• The remote RUN (function) cannot be executed.
• Data logging is being performed (data logging status: RUN
waiting (no collection), Start waiting (no collection),
Condition waiting (no collection), Pause, Collecting, Trigger
waiting (collecting before trigger), Collecting after trigger, or
Saving the logging data) to another memory.
• The specified data logging is already being performed (data
logging status: RUN waiting (no collection), Start waiting (no
collection), Condition waiting (no collection), Pause,
Collecting, Trigger waiting (collecting before trigger),
Collecting after trigger, or Saving the logging data).
• The function that cannot be executed during the data
logging (data logging status: RUN waiting (no collection),
Start waiting (no collection), Condition 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.
Action
• Do not access the specified file or subdirectory.
• Execute again after checking the file and subdirectory.
• Execute again after increasing the free space of the drive
(memory).
• Delete files in the drive (memory), and execute the function
again.
• Execute again after a while.
• Execute again after canceling the write protect of the
specified drive (memory).
• Execute again after shortening the file name path.
• Execute again after the currently performed operation is
completed.
• Insert the SD memory card.
• Remove the SD memory card, and insert it again.
• Cancel the SD memory card forced disable instruction.
• Execute the function again after a while.
• Register data logging to the memory where the data logging
is being performed. Or, stop the data logging being
performed and register again.
■When CPU Module Logging Configuration Tool is used
• Start the data logging to the memory where the data logging
is being performed. Or, stop the data logging being
performed, and start the data logging.
• Stop the data logging. Or, write, delete, or register data
logging to the setting number where no data logging is
being performed.
• 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.

Advertisement

Table of Contents
loading

Table of Contents

Save PDF