Receiving Errors During Fixed Buffer Communication (Common To Procedure Exist And No Procedure) - Mitsubishi Electric FX3U-ENET User Manual

11 TROUBLESHOOTING
11.5.2 Receiving errors during fixed buffer communication
(common to procedure exist and no procedure)
Do the expected length
of data to be received and
the amount of data actually
received match?
Check the open status of the
connection with an external device.
Are the corresponding
connection LEDs (C1-C8) lit?
Read the open abnormal code (BFM
#124, 134...) of the communication status
storage area and check that no errors
have occurred.
Have parameter errors
Read the content of the communication
abnormal code storage area (BFM #125,
135...) corresponding to the fixed buffer
of the buffer memory and check whether
or not a communication error has occurred.
communication error occurred in the
Check that "receive" is set in the parameter
open settings.
11 - 39
POINT
Perform error code reading while the connection is open.
Receiving error
NO
YES
NO
YES
NO
occurred?
YES
Has a
NO
error log area?
YES
NO
1)
Receive is set
YES
1)
If the amount of actually received data is
smaller than the length of data expected to
be received, the subsequent processing
must allow reception of the remaining data.
If the amount of actually received data is
larger than the length of data expected to
be received, the subsequent data should
be treated as the next request message or
as unnecessary data.
(See NOTE in 11.4.4 section for further
details.)
Execute the open processing of the
applicable connection.
(For details, see Section 5.6.)
Fix the error according to the parameter
error code (see Section 11.4).
Fix the error according to the
communication error code in the error log
area (see Section 11.4).
Change parameters to "receive".
MELSEC-F
11 - 39