8 - 4 8 - 4
MELSEC-GOT
8 ERROR CODES AND ERROR MESSAGES
Error
Code
Error Message
Definition
Action
356
File system error occurred in
the PLC
When the file register name is designated and
then the recipe function is operated, an error
occurs in the designated file register.
1. Check the file register name, and then
operate the recipe function again.
2. Apply Format PLC memory to the designated
PLC drive with the GX Developer, and then
operate the recipe function again.
357
The specified drive of PLC is
abnormal
When the file register name is designated and
then the recipe function is operated, there is a
fault in the PLC drive.
1. Check the designated PLC drive, and then
operate the recipe function again.
2. Apply Format PLC memory to the designated
PLC drive with the GX Developer, and then
operate the recipe function again.
358
File of PLC access failure
When the file register name is designated and
then the recipe function is operated, the PLC file
register could not be accessed.
1. Check the designated PLC drive/ file register
name, and then operate the recipe function
again (If drive 0 was designated, change to a
different drive, and then operate the recipe
function again).
2. Check whether the memory card is write-
protected, and then operate the recipe
function again.
359
Processing is from another
peripheral device
When the file register name is designated and
then the recipe function is operated, other
peripheral devices begin processing for the file
register.
Wait until the peripheral devices finish operating,
and then operate the recipe function again.
360
Division error due to divisor of
0
Divisor 0 occurred in the data operation formula
Reconsider the data operation formula to avoid
the divisor of 0
370
Contradiction in magnitude
relationship of upper and lower
limit values
Upper and lower limit values have been set as
[upper limit lower limit]
Check the upper and lower limit value setting
and correct them to be [upper limit lower limit]
402
Communication time-out
Time-out error occurred during communication
1. Check for any disconnected cable or
improperly fitted communication
board/communication module
2. This may occur if the programmable logic
controller load is increased while accessing
another station. In this case, move the other
station's data to the local station's
programmable logic controller, and monitor
with the local station.
3. If the sequence scan is long, insert a COM
command.
403
SIO request status error
At the time of receive during RS-422/RS-232C
communication, any of overrun error, parity bit
error and framing error occurred.
Check the cable connection status, the
communication board/communication module
mounting status, the PLC status, and the
communication link transmission speed.
406
Specified station doesn’t
access for out of range
(1) The station number specified for CC-Link
connection (via G4) is other than that of the
master/local station.
(2) Access was made to the CPU other than the
QCPU.
Check the station number of the monitor screen
data.
407
Other network accessed by
MNET10 module
Access was made to the other network at the
time of MELSECNET connection (network
system)
Check the network number in the screen data to
avoid access to the other network.
421
The specification of E71
cannot be written
The Ethernet module on the PLC side has been
set for write disable.
Set the PLC side Ethernet module for write
enable.
422
It is not communicate between
the CPU and E71
The CPU is faulty or communication cannot be
made between the CPU and PLC side Ethernet
module.
Check the CPU for any fault using GX
Developer or like. (Check the buffer memory.)
