Mitsubishi FX3U-ENET, Руководство пользователя

Страница: 263 / 298

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