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
Error
Corrective action
messages on
on GOT side
GOT
With no file
operation being
The file is not
executed on GX
found.
Developer or GX
Works2, re-execute
the file reading.
• Read/write of values of the file register specified for
the recipe function
Error
Corrective action
messages on
on GOT side
GOT
With no file
operation on GX
358 PLC file
Works3, GX
access failure.
Works2, GX
Confirm PLC
Developer, turn ON
*1
the trigger device
drive.
for the recipe
function again.
*1
The numerical value indicates the system alarm No.
• Reading TC monitor set value in the system monitor
function
Error
Corrective action
messages on
on GOT side
GOT
With no file
operation being
No message
executed on GX
is displayed.
Works3, GX
(The TC set
Works2, GX
value space
Developer, re-
is blank.)
execute the TC
monitor.
31 - 50
31. FA TRANSPARENT FUNCTION
31.7 Precautions
Error messages on
Corrective action
GX Developer and
on GX Developer
GX Works2
and GX Works2
With no file reading
being executed in
the ladder monitor
File access failure.
function for
Please retry.
MELSEC-Q, re-
execute the file
operation.
Error messages on
Corrective action
GX Works3, GX
on GX Works3, GX
Works2, GX
Works2, GX
Developer
Developer
File access failure.
Execute the file
Please retry.
access operation
again with the
PLC file system
recipe in-process
error. Unable to
signal in GOT
communicate with
system information
PLC.
OFF.
Error messages on
Corrective action
GX Works3, GX
on GX Works3, GX
Works2, GX
Works2, GX
Developer
Developer
With no TC set
File access failure.
value being read,
Please retry.
re-execute the file
operation.
• Reading the special module monitor CPU
Malfunction log
Error
Corrective action
messages on
on GOT side
GOT
With no file
operation being
executed on GX
Works3, GX
Communicati
Works2, GX
on error
Developer, re-
execute the CPU
malfunction log
reading.
• Backup/restore
Error
Corrective action
messages on
on GOT side
GOT
With no file
operation being
executed on GX
Backup
Developer or GX
Works2, re-execute
the backup.
With no file
operation being
executed on GX
Restore
Developer or GX
Works2, re-execute
the restore.
• SFC monitor file reading
Error
Corrective action
messages on
on GOT side
GOT
With no file
operation being
executed on GX
-
Developer or GX
Works2, re-execute
the file reading.
• Reading/Writing files of ladder edit
Error
Corrective action
messages on
on GOT side
GOT
With no file
operation being
executed on GX
Read
Developer or GX
Works2, re-execute
the file reading.
With no file
operation being
executed on GX
Write
Developer or GX
Works2, re-execute
the file writing.
Error messages on
Corrective action
GX Works3, GX
on GX Works3, GX
Works2, GX
Works2, GX
Developer
Developer
With no special
module monitor
File access failure.
CPU malfunction
Please retry.
log being read,
execute the file
operation.
Error messages on
Corrective action
GX Developer and
on GX Developer
GX Works2
and GX Works2
With no backup
being executed,
-
execute the file
operation.
With no restore
being executed,
-
execute the file
operation.
Error messages on
Corrective action
GX Developer and
on GX Developer
GX Works2
and GX Works2
With no special
module monitor
CPU malfunction
-
log being read,
execute the file
operation.
Error messages on
Corrective action
GX Developer and
on GX Developer
GX Works2
and GX Works2
With no file reading
being executed on
-
ladder edit,
execute the file
operation.
With no file writing
being executed on
-
ladder edit,
execute the file
operation.
Advertisement
Chapters
Table of Contents
