11 - 33
MELSEC-F
TROUBLESHOOTING11
11 - 33
*1See Section 11.1 when the value of BFM#27 is "0000H" or when the display LED COM.ERR (communication error
detection display) lights up.
(Check an error code that is stored in the buffer memory in reaction to an error occurrence, then check the contents
of the error and take corrective actions by referring to Section 11.4.)
*2Error code s not found in the error code list may be returned to the external device side if the communication data
settings on the Ethernet module side (see Section 4.6) and the data code settings on the external device side are
different.
The Ethernet module cannot decode commands correctly if data with different data codes is received. The Ethernet
module returns error responses according to the communication data code settings.
[example] When communication is performed using a fixed buffer.
*3If the FG ( )terminals of the Ethernet module are not set, the communication line is closed (disconnected) due to
the effects of noise, and as a result communication with an external device may not be performed.
Is initial
processing normally completed
(BFM#27=
"0001H")
NO
(BFM#27=
"0001H")
YES
Check and fix the faulty part for each
communication processing.
Sending error in fixed buffer communication See Subsection 11.5.1.
Receiving error in fixed buffer communication See Subsection 11.5.2.
Error in the MC protocol communication See Subsection 11.5.3.
Send error during communication by e-mail See Subsection 11.5.4.
1)
Perform initial processing.
(See Subsection 5.2.1.)
If the initial processing parameters set
with FX Configurator-EN-L and the
sequence program for initial processing
overlap, delete the sequence program
for initial processing.
60H00H
Text
End code
Subheader
Data length
Subheader
External device side
(Set to binary code)
The external device side
receives this portion
as an end code.
45H30H35H34H
Subheader
Ethernet module side
(Set to ASCII code)