Mitsubishi Electric RD78G4 User Manual page 78

Motion module
Hide thumbs Also See for RD78G4:
Table of Contents

Advertisement

Error
Error definition and causes
code
C844H
Incorrect frame was received.
• Unsupported command
C900H
Communication failed.
C901H
The size of the request data to the external
device or response data from the external
device exceeds the range supported for
communications.
C902H
Communication was interrupted because
no response was returned from the
external device.
C903H
Failed to send request to the external
device.
CA00H
• Access to the flash ROM of the network
module failed.
• At execution of firmware update, the
number of writes to the flash ROM has
exceeded 100000.
CA01H
A firmware update file for the model that
was different from the network module was
used.
CA02H
A firmware update file with a file name or
file contents that were incorrect was used.
CA03H
The firmware update was performed while
a firmware file with the version that does
not operate on the module was specified.
CA04H
Firmware update was performed for the
network module during data link.
CA05H
An error in the firmware data was detected
during execution of the firmware update
function.
CA06H
Firmware update was performed for the
module during execution of a firmware
update.
CA07H
A sequence error of firmware update was
detected.
CA08H
Communications were not available
between the firmware update tool and the
module.
CA09H
When a firmware update file is transferred
to the target module, the user ID or
password for authentication is incorrect.
CA0AH
Firmware update could not be performed
due to the disable setting of the firmware
update.
CF40H
Incorrect frame was received.
3 TROUBLESHOOTING
76
3.5 List of Error Codes
Action
• Replace the network module with a module of the version supporting the
function that has been executed.
• If the error occurs again even after taking the above, please consult your
local Mitsubishi representative.
Do not execute communication from multiple engineering tools to the same
master station simultaneously.
Correct the size of the request data or response data to within 1500 bytes.
Execute the communication test, and if the test was completed with an error,
take corrective action.
• Correct the IP address of the external device.
• Check if the subnet mask of the external device matches the master
station.
• Execute firmware update again after resetting the module.
• If the same error occurs again, the number of writes to the flash ROM may
have exceeded 100000. Replace the module.
Check the target network module, and execute firmware update again after
resetting the module.
• Check if the file name of the firmware update file has been changed.
• Check if the firmware update file is damaged.
• After the above actions, execute firmware update again after resetting the
module.
Check that the firmware version that is appropriate for update, reset the
module and execute firmware update again.
Execute firmware update again after data link with other stations has been
stopped.
Execute firmware update again after resetting the module.
After the end of the firmware update, reset the module and execute firmware
update again.
• Check to see if multiple firmware update tools have been started, and
identical firmware updates for the same module have been executed.
• After the end of the firmware update, reset the module and execute
firmware update again.
• Check if the firmware update tool is mistakenly closed.
• Check if the switching hub and the cables are connected properly.
• Check if the communication load between the firmware update tool and the
module is too high.
• After the above actions, execute firmware update again after resetting the
module.
Enter the correct user ID and password, and execute the firmware update
again after resetting the module.
Clear the disable setting of the firmware update, and execute the firmware
update again.
• Check the operating status and connection status of the target device.
• Check the connection of the Ethernet cable and hub.
• Check the line status of Ethernet.
• Reset the CPU module and target device, and retry the operation.
If the above actions do not solve the problem, contact the manufacturer of the
target device.
Detailed
information

Advertisement

Table of Contents
loading

Table of Contents