Mitsubishi 900 Series User Manual page 101

Error
Error Message
Code
File system error occurred in
356
the PLC
The specified drive of PLC is
357
abnormal
358 File of PLC access failure
Processing is from another
359
peripheral device
360 Division error due to divisor of 0
Contradiction in magnitude rela-
370 tionship of upper and lower limit
values
402 Communication time-out
403 SIO request status error
Specified station doesn't access
406
for out of range
Other network accessed by
407
MNET10 module
The specification of E71 cannot
421
be written
It is not communicate between
422
the CPU and E71
9 - 4
9.2 Error Code and Error Message List
Definition
When the file register name is designated and then
the recipe function is operated, an error occurs in
the designated file register.
When the file register name is designated and then
the recipe function is operated, there is a fault in
the PLC drive.
When the file register name is designated and then
the recipe function is operated, the PLC file regis-
ter could not be accessed.
When the file register name is designated and then
the recipe function is operated, other peripheral
devices begin processing for the file register.
Divisor 0 occurred in the data operation formula
Upper and lower limit values have been set as
[upper limit lower limit]
Time-out error occurred during communication
At the time of receive during RS-422/RS-232C
communication, any of overrun error, parity bit
error and framing error occurred.
(1) The station number specified for CC-Link con-
nection (via G4) is other than that of the master/
local station.
(2) Access was made to the CPU other than the
QCPU.
Access was made to the other network at the time
of MELSECNET connection (network system)
The Ethernet module on the PLC side has been
set for write disable.
The CPU is faulty or communication cannot be
made between the CPU and PLC side Ethernet
module.
Action
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.
1. Check the designated PLC drive, and then oper-
ate 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.
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 func-
tion again).
2. Check whether the memory card is write-pro-
tected, and then operate the recipe function
again.
Wait until the peripheral devices finish operating,
and then operate the recipe function again.
Reconsider the data operation formula to avoid the
divisor of 0
Check the upper and lower limit value setting and
correct them to be [upper limit
1. Check for any disconnected cable or improperly
fitted communication board/communication
module
2. This may occur if the programmable logic con-
troller 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 com-
mand.
Check the cable connection status, the communi-
cation board/communication module mounting sta-
tus, the PLC status, and the communication link
transmission speed.
Check the station number of the monitor screen
data.
Check the network number in the screen data to
avoid access to the other network
Set the PLC side Ethernet module for write enable.
Check the CPU for any fault using GX Developer
or like. (Check the buffer memory.)
lower limit]