31. FA TRANSPARENT FUNCTION
31.7 Precautions
31 - 63
28
ENERG
Y MEAS
URIN
G UNIT
/
ELECT
RIC M
UL
TI-
MEAS
UR
ING
INSTRUMENT
CO
NNECT
IO
N
29
GO
T
MUL
T
I-
DRO
P
CONNECTION
30
M
U
LT
I-
CH
A
N
NE
L
FUNCTION
31
FA
TRANS
P
ARENT
FUNCTION
32
CONNECTION
T
O
IA
I
ROBOT CONT
ROLLE
R
33
C
O
NNECTION T
O
OMRON PLC
34
CO
N
N
EC
TI
O
N
T
O
O
M
R
O
N T
E
MPER
TU
RE
C
O
NT
ROL
LE
R
35
CONNECTION T
O
KEY
ENCE PLC
31.7.2 When using GX Works3, GX
Works2, GX Developer
When connecting to QCPU (A mode)
When connecting to QCPU (A mode), set the PLC type
to "A4UCPU" or "QCPU (A mode)" on GX Developer.
When [monitor conditions] have been set on
GX Works3, GX Works2, GX Developer
(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 Developer, 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, GX
Developer 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 Developer and GX
Works2 to 30 seconds or less.
When exiting GX Works3, GX Works2, GX
Developer
For 45 seconds after GX Works3, GX Works2, GX
Developer have been exited, the GOT continues
monitoring at the same speed as when the FA
transparent function is working.
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 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 Works3,
GX Works2,
GX Developer
Corrective
action on
GX Works3,
GX Works2,
GX Developer
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
Communication
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.
Summary of Contents for GT16
Page 1: ......
Page 2: ......
Page 46: ...1 4 1 OVERVIEW 1 1 Features ...
Page 54: ...2 8 2 SYSTEM CONFIGURATION 2 2 System Equipment ...
Page 60: ...3 6 3 SPECIFICATIONS 3 4 Battery specifications ...
Page 72: ...5 8 5 UL cUL STANDARDS AND EMC DIRECTIVE 5 2 EMC Directive ...
Page 102: ...6 30 6 OPTION 6 7 Connector Conversion Box ...
Page 106: ...7 4 7 INSTALLATION 7 1 Installing Procedure ...
Page 110: ...8 4 8 COMMUNICATION CABLE 8 1 Overview of Communication Cable ...
Page 130: ...9 20 9 HANDLING OF POWER WIRING AND SWITCH 9 4 Switch Wiring ...
Page 142: ...10 12 10 UTILITY FUNCTION 10 3 Utility Display ...
Page 184: ...11 42 11 DISPLAY AND OPERATION SETTINGS GOT SET UP 11 4 Maintenance Function ...
Page 202: ...12 18 12 COMMUNICATION INTERFACE SETTING COMMUNICATION SETTING 12 3 Ethernet Setting ...
Page 226: ...13 24 13 DEBUG 13 3 Memory Data Control ...
Page 248: ...14 22 14 SELF CHECK 14 2 Batch Self Check ...
Page 350: ...15 102 15 DATA CONTROL 15 3 OS Project Information ...
Page 410: ...19 22 19 TROUBLESHOOTING 19 2 Error Message and System Alarm ...
Page 418: ...App 8 APPENDICES Appendix 3 Transportation Precautions ...
Page 422: ...REVISIONS 4 ...
Page 425: ......
Page 426: ......
Page 427: ......
Page 428: ......
Page 470: ......
Page 510: ...21 22 21 COMPUTER LINK CONNECTION 21 6 Precautions ...
Page 568: ...22 58 22 ETHERNET CONNECTION 22 5 Precautions ...
Page 584: ......
Page 626: ...25 14 25 SERVO AMPLIFIER CONNECTION 25 7 Precautions ...
Page 632: ...26 6 26 ROBOT CONTROLLER CONNECTION 26 6 Precautions ...
Page 647: ...MULTIPLE GOT CONNECTIONS 29 GOT MULTI DROP CONNECTION 29 1 ...
Page 648: ......
Page 659: ...MULTI CHANNEL FUNCTION 30 MULTI CHANNEL FUNCTION 30 1 ...
Page 660: ......
Page 675: ...FA TRANSPARENT FUNCTION 31 FA TRANSPARENT FUNCTION 31 1 ...
Page 676: ......
Page 742: ...31 66 31 FA TRANSPARENT FUNCTION 31 7 Precautions ...
Page 744: ......
Page 766: ...32 22 32 CONNECTION TO IAI ROBOT CONTROLLER 32 7 Precautions ...
Page 802: ...34 10 34 CONNECTION TO OMRON TEMPERATURE CONTROLLER 34 7 Precautions ...
Page 834: ...36 18 36 CONNECTION TO KOYO EI PLC 36 6 Device Range that Can Be Set ...
Page 858: ...38 12 38 CONNECTION TO SHARP PLC 38 6 Device Range that Can Be Set ...
Page 868: ...39 10 39 CONNECTION TO SHINKO TECHNOS INDICATING CONTROLLER 39 7 Precautions ...
Page 902: ...42 6 42 CONNECTION TO TOSHIBA MACHINE PLC 42 6 Device Range that Can Be Set ...
Page 908: ...43 6 43 CONNECTION TO PANASONIC SERVO AMPLIFIER 43 7 Precautions ...
Page 970: ...48 12 48 CONNECTION TO FUJI TEMPERATURE CONTROLLER 48 7 Precautions ...
Page 1052: ...52 26 52 CONNECTION TO AZBIL CONTROL EQUIPMENT 52 7 Precautions ...
Page 1102: ...55 14 55 CONNECTION TO GE PLC 55 7 Precautions ...
Page 1114: ...57 4 57 CONNECTION TO SICK SAFETY CONTROLLER 57 5 Device Range that Can Be Set ...
Page 1128: ...59 2 59 CONNECTION TO HIRATA CORPORATION HNC CONTROLLER ...
Page 1130: ...60 2 60 CONNECTION TO MURATEC CONTROLLER ...
Page 1132: ......
Page 1270: ...62 68 62 MICROCOMPUTER CONNECTION ETHERNET 62 8 Precautions ...
Page 1271: ...MODBUS CONNECTIONS 63 MODBUS R RTU CONNECTION 63 1 64 MODBUS R TCP CONNECTION 64 1 ...
Page 1272: ......
Page 1292: ...64 12 64 MODBUS R TCP CONNECTION 64 7 Precautions ...
Page 1293: ...CONNECTIONS TO PERIPHERAL EQUIPMENT 65 VNC R SERVER CONNECTION 65 1 ...
Page 1294: ......
Page 1298: ...65 4 65 VNC R SERVER CONNECTION 65 4 Setting in Personal Computer ...
Page 1302: ...REVISIONS 4 ...
Page 1305: ......
Page 1306: ......