Mitsubishi Electric GT14, User Manual

Page: 686 / 1546

31 - 50
31. FA TRANSPARENT FUNCTION
31.7 Precautions

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
• Read/write of values of the file register specified for
the recipe function
*1 The numerical value indicates the system alarm No.
• Reading TC monitor set value in the system monitor
function
• Reading the special module monitor CPU
Malfunction log
• Backup/restore
• SFC monitor file reading
• Reading/Writing files of ladder edit
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 Works3, GX
Works2, GX
Developer
Corrective action
on GX Works3, GX
Works2, GX
Developer
358 PLC file
access failure.
Confirm PLC
drive.
*1
With no file
operation on GX
Works3, GX
Works2, GX
Developer, 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 Works3, GX
Works2, GX
Developer
Corrective action
on GX Works3, GX
Works2, GX
Developer
No message
is displayed.
(The TC set
value space
is blank.)
With no file
operation being
executed on GX
Works3, GX
Works2, GX
Developer, 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 Works3, GX
Works2, GX
Developer
Corrective action
on GX Works3, GX
Works2, GX
Developer
Communicati
on error
With no file
operation being
executed on GX
Works3, GX
Works2, GX
Developer, re-
execute the CPU
malfunction log
reading.
File access failure.
Please retry.
With no special
module monitor
CPU 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.
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
Read
With no file
operation being
executed on GX
Developer or GX
Works2, re-execute
the file reading.
-
With no file reading
being executed on
ladder edit,
execute the file
operation.
Write
With no file
operation being
executed on GX
Developer or GX
Works2, re-execute
the file writing.
-
With no file writing
being executed on
ladder edit,
execute the file
operation.