Mitsubishi Electric FX5 User Manual page 154

Error code Error details and causes
(Hexadecimal)
C1D3H A dedicated instruction not supported by the communication
method of the connection was executed.
C400H The SP.ECPRTCL instruction was executed when "Predefined
protocol ready (SD10692)" was "0".
C401H • The control data of the SP.ECPRTCL instruction specified a
protocol number not registered in the CPU module.
• The SP.ECPRTCL instruction was executed while the protocol
setting data was not written.
C404H The cancel request was received while the protocol was executed,
and the SP.ECPRTCL instruction was finished abnormally.
C405H The protocol number set value is out of range in the control data of
the SP.ECPRTCL instruction.
C410H The receive waiting time timed out.
C411H The received data is larger than 2046 bytes.
C417H The data length or data quantity of the received data is out of
range.
C431H The connection was closed during the SP.ECPRTCL instruction
execution.
C614H The response monitoring timer is timed out.
CEE0H The devices supporting iQSS which were detected by the other
peripheral device, or other iQSS functions were executed while the
automatic detection of connected devices is in process.
CEE1H Incorrect frame is received.
CEE2H Incorrect frame is received.
13 TROUBLESHOOTING
152
13.4 Error Codes
Action
• Check that the dedicated instruction can be executed by the
specified communication method. Correct the program if the
instruction cannot be executed.
• Check that there is no error in the connection specification of the
dedicated instruction.
• Execute the SP.ECPRTCL instruction after "Predefined protocol
ready (SD10692)" has become "1".
• Execute the SP.ECPRTCL instruction after rewriting the protocol
setting data to the CPU module.
• If the error occurs again even after rewriting, replace the CPU
module.
• Check whether the specified protocol number is correct.
• Check the presence/absence of protocol registration (SD10722 to
SD10725), and then check whether the specified protocol number
is registered.
• Write the protocol setting data, and then execute the SP.ECPRTCL
instruction.
Check the canceled protocol in the control data of the SP.ECPRTCL
instruction (execution count result) and eliminate the cause of the
cancellation.
Correct the protocol number set value.
• Check if the cable is disconnected.
• Correct the specified connection number of the external device
connection configuration setting, and execute the protocol again.
• Check that there is no error in the external device.
• Check that the sending from the external device is not interrupted.
• Check that there is no data lost due to a receive error.
• Check that there is no error in the data (packet) sent by the
external device.
• Check the data sent from the external device.
• When sending data larger than 2046 bytes from the external
device, divide the data into several portions and execute data
sending several times.
• Check the maximum allowable data length and specify the
maximum length or less in the data length storage area.
• Check the maximum allowable data quantity, and specify the
maximum quantity or less in the data quantity storage area.
• Check the operation of the external device.
• Check the connection open status with the external device.
• Open the connection with the external device again and execute
the instruction.
Since access to the file may take some time, check the setting value
of "Response monitoring timer" in "FTP Server Settings" under
"Application Settings".
Execute the other function after the automatic detection of connected
devices is completed.
• Check the operating status and connection status of the target
device.
• Check the connection of an Ethernet cable and a 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.
• Check the operating status and connection status of the target
device.
• Check the connection of an Ethernet cable and a 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.