Mitsubishi Electric FX3U-ENET User Manual page 260

11 TROUBLESHOOTING
communication protocol
(TCP/UDP) match that of
the external device?
Was the "0001
from BFM#1610 to 1617?
Is the read value of
BFM#1610 to 1617 "0004
count (procedure) or byte
count (non-procedure) set at the
head of the fixed
Check the communication status of
the external device.
Does the external
device operate normally?
open errors or initial errors
in the error log area?
The Ethernet module hardware on the
sending side may be faulty.
Consult your nearest branch office or
dealer with the details of the errors.
11 - 38
1)
Does the
NO
YES
NO
" written to
H
YES
NO
"?
H
YES
Is the word
NO
buffer?
YES
NO
YES
Are there any
NO
YES
POINT
If the external device communicates normally, the following conditions occur.
For TCP communication
When the external device's open status is complete, LEDs C1-C8, which are in
correspondence with connections 1-8, turn on.
For UDP communication
When external device communication is possible, LEDs C1-C8, which are in
correspondence with connections 1-8, turn on.
Match the protocol with the
communication protocol (TCP/UDP) of
the external device. (For details, see
Section 5.5.)
Correct the write condition of
BFM#1610 to 1617.
Check the fixed buffer transfer error
code of BFM#125, 135, 145, 155,
165, 175,185, 195.
Write the data length.
Fix the faulty part of the external
device. (If the receiving side is also an
Ethernet module, see Section 11.4.)
Check and fix the faulty part.
MELSEC-F
11 - 38