Filter
Top Products
22 - 70
22. FA TRANSPARENT FUNCTION
22.7 Precautions
When performing [Read to PLC], [Write to
PLC] and other file operations on GX
Developer, 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 Developer,
or 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
• Reading TC monitor set value in the system monitor
function
*1 The numerical indicates the system alarm No.
• Reading the special module monitor CPU
Malfunction log
• Backup/restore
• SFC monitor file reading
Error messages
on GOT
Corrective
action on GOT
side
Error messages
on GX Developer
and GX Works2
Corrective
action on GX
Developer and
GX Works2
The file is not
found.
With no file
operation being
executed on
GX Developer
or 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 Developer
and GX Works2
Corrective
action on GX
Developer and
GX Works2
358 PLC file
access failure.
Confirm PLC
drive.
*1
With no file
operation on
GX Developer
or 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 Developer
and GX Works2
Corrective
action on GX
Developer and
GX Works2
No message is
displayed.
(The TC set
value space is
blank.)
With no file
operation being
executed on
GX Developer
or 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 Developer
and GX Works2
Corrective
action on GX
Developer and
GX Works2
Communication
error
With no file
operation being
executed on
GX Developer
or 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.
Error messages
on GOT
Corrective
action on GOT
side
Error messages
on GX Developer
and GX Works2
Corrective
action on GX
Developer and
GX Works2
Backup
With no file
operation being
executed on
GX Developer
or GX Works2,
re-execute the
backup.
―
With no
backup being
executed,
execute the file
operation.
Restore
With no file
operation being
executed on
GX Developer
or GX Works2,
re-execute the
restore.
―
With no restore
being
executed,
execute the file
operation.
Error messages
on GOT
Corrective
action on GOT
side
Error messages
on GX Developer
and GX Works2
Corrective
action on GX
Developer and
GX Works2
―
With no file
operation being
executed on
GX Developer
or GX Works2,
re-execute the
file reading.
―
With no special
module
monitor CPU
malfunction log
being read,
execute the file
operation.