Mitsubishi Electric GOT2000 Series, Connection Manual

Page: 1216 / 1224

22 - 160
22.8 Precautions
22.8.2 When using GX Works3, GX Works2
■1.
When [monitor conditions] have been set on GX Works3, GX Works2
(1) Monitoring performance of the GOT is temporarily suspended.
(2) The GOT cannot respond to the touch switch operation and numerical/ascii inputs.
(3) Writing to PLC results in a system alarm occurrence and displays the message, "315 Device writing error.
Correct device.".
(4) While setting the monitor conditions, do not perform any operation which makes the GOT restart (e.g.
downloading project data, changing utility data).
Doing so may display a system alarm, "402 Communication timeout. Confirm communication pathway or modules."
when the GOT restarts.
When the monitor conditions setting for the PLC CPU has not been cancelled, reconnect GX Works3, GX Works2 to
cancel the setting.(An error may be output when the monitor conditions setting is cancelled.)
(5) When the time check of GX Works3, GX Works2 is set to 30 seconds or more in the monitor condition
settings, the message "402 Communication timeout. Confirm communication pathway or modules." may
appear.
Set the time check time of GX Works3, GX Works2 to 30 seconds or less.
■2.
When exiting GX Works3, GX Works2
For 45 seconds after GX Works3, GX Works2 has been exited, the GOT continues monitoring at the same speed as
when the FA transparent function is working.
■3.
When performing [Read to PLC], [Write to PLC] and other file operations on GX Works3,
GX Works2
If any of the following GOT functions is executed during the file operation such as [Read to PLC] or [Write to PLC], an
error may occur on the GOT, GX Works3, GX Works2.
In this case, take the following corrective action:
• File reading in the ladder monitor function for MELSEC-Q
• Read/write of values of the file register specified for the recipe function
*1 The numerical indicates the system alarm No.
• Reading TC monitor set value in the system monitor function
• Reading the special module monitor CPU Malfunction log
Error messages on GOT Corrective action on GOT side Error messages on GX Works2 Corrective action on GX Works2
The file is not found.
With no file operation being
executed on GX Works2, re-
execute the file reading.
File access failure.
Please retry.
With no file reading being executed
in the ladder monitor function for
MELSEC-Q, re-execute the file
operation.
Error messages on GOT Corrective action on GOT side Error messages on GX Works2 Corrective action on GX Works2
358 PLC file access failure.
Confirm PLC drive.
*1
With no file operation on GX
Works3, GX Works2, turn ON the
trigger device for the recipe
function again.
File access failure.
Please retry.
Execute the file access operation
again with the recipe in-process
signal in GOT system information
OFF.
PLC file system error. Unable to
communicate with PLC.
Error messages on GOT Corrective action on GOT side Error messages on GX Works2 Corrective action on GX Works2
No message is displayed.
(The TC set value space is blank.)
With no file operation being
executed on GX Works3, GX
Works2, re-execute the TC
monitor.
File access failure.
Please retry. With no TC set value being read,
re-execute the file operation.
Error messages on GOT Corrective action on GOT side Error messages on GX Works2 Corrective action on GX Works2
Communication error
With no file operation being
executed on GX Works3, GX
Works2, re-execute the CPU
malfunction log reading.
File access failure.
Please retry.
With no special module monitor
malfunction log being read,
execute the file operation.