Table of Contents
Advertisement
When performing [Read to PLC], [Write to
PLC] and other file operations on GX
Works3, GX Works2, GX Developer
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, GX Developer.
In this case, take the following corrective action:
• File reading in the ladder monitor function for
MELSEC-Q
Corrective
Error messages
action on GOT
on GOT
side
With no file
operation being
executed on
The file is not
GX Developer
found.
or GX Works2,
re-execute the
file reading.
• Read/write of values of the file register specified for
the recipe function
Corrective
Error messages
action on GOT
on GOT
side
With no file
operation on
GX Works3,GX
358 PLC file
Works2,GX
access failure.
Developer, turn
Confirm PLC
ON the trigger
*1
drive.
device for the
recipe function
again.
• Reading TC monitor set value in the system monitor
function
Corrective
Error messages
action on GOT
on GOT
side
With no file
operation being
No message is
executed on
displayed.
GX Works3,GX
(The TC set
Works2,GX
value space is
Developer, re-
blank.)
execute the TC
monitor.
*1
The numerical indicates the system alarm No.
23 - 88
23. FA TRANSPARENT FUNCTION
23.7 Precautions
Corrective
Error messages
action on GX
on GX Developer
Developer and
and GX Works2
GX Works2
With no file
reading being
executed in the
File access
ladder monitor
failure.
function for
Please retry.
MELSEC-Q,
re-execute the
file operation.
Corrective
Error messages
action on GX
on GX Developer
Developer and
and GX Works2
GX Works2
File access
Execute the
failure.
file access
Please retry.
operation
again with the
recipe in-
PLC file system
process signal
error. Unable to
in GOT system
communicate
information
with PLC.
OFF.
Corrective
Error messages
action on GX
on GX Developer
Developer and
and GX Works2
GX Works2
With no TC set
File access
value being
failure.
read, re-
Please retry.
execute the file
operation.
• Reading the special module monitor CPU
Malfunction log
Corrective
Error messages
action on GOT
on GOT
side
With no file
operation being
executed on
GX Works3,GX
Communication
Works2,GX
error
Developer, re-
execute the
CPU
malfunction log
reading.
• Backup/restore
Corrective
Error messages
action on GOT
on GOT
side
With no file
operation being
executed on
Backup
GX Developer
or GX Works2,
re-execute the
backup.
With no file
operation being
executed on
Restore
GX Developer
or GX Works2,
re-execute the
restore.
• SFC monitor file reading
Corrective
Error messages
action on GOT
on GOT
side
With no file
operation being
executed on
GX Works3,GX
―
Works2,GX
Developer, re-
execute the file
reading.
Corrective
Error messages
action on GX
on GX Developer
Developer and
and GX Works2
GX Works2
With no special
module
File access
monitor
failure.
malfunction log
Please retry.
being read,
execute the file
operation.
Corrective
Error messages
action on GX
on GX Developer
Developer and
and GX Works2
GX Works2
With no
backup being
―
executed,
execute the file
operation.
With no restore
being
―
executed,
execute the file
operation.
Corrective
Error messages
action on GX
on GX Developer
Developer and
and GX Works2
GX Works2
With no special
module
monitor CPU
―
malfunction log
being read,
execute the file
operation.
Hide quick links:
Advertisement
Chapters
Table of Contents
