8.3.6
Precautions
(1) Modules supporting the IP packet transfer function
(a) Master/local module and GX Works2
Before using the IP packet transfer function, check the versions of the master/local module and GX Works2.
(
Page 546, Appendix 8)
(b) CPU module
To use the IP packet transfer function, all the CPU modules on the communication route must support the
function. For supporting CPU module versions, refer to the following.
QnUCPU User's Manual (Function Explanation, Program Fundamentals)
(c) Modules other than those listed above
To use the IP packet transfer function with a module other than those listed above, check the version to see if
the module supports the IP packet transfer function. For how to check the version, refer to the sections listing
functions and added functions on the manual for the module used.
(2) Communications before a baton pass is established (the D LINK LED turns off)
The IP packet transfer function can be used before a baton pass is established. If communications are performed
before that, a timeout error occurs in an Ethernet device (request source device). Whether the baton pass is
established in the own station can be checked on the D LINK LED.
(3) Using other networks
Communications cannot be performed via modules that do not support the IP packet transfer function such as
MELSECNET/H.
Communications over MELSECNET/H
Ex.
Ethernet device
(request source device)
(4) Precautions when using the UDP communication
Using UDP may reduce the reliability of data communications compared to TCP, causing a problem, such as data
missing and changed order of data receiving. If any problem occurs, change the protocol to TCP.
(5) Communications of Broadcast and Multicast
Communications of Broadcast and Multicast cannot be transferred using the IP packet transfer function. Use
Unicast (identifying a single request destination) instead.
160
(request destination device)
MELSECNET/H
Ethernet device