*1:
If the target CPU is not found by the Find CPU function, check the following.
Route:
• Check that access to the target CPU does not pass through any router.
• Check the parameters.
• Check that the Find CPU function is not rejected by a parameter setting of the target CPU.
Computer-side settings:
• Check if an IP address is set.
• Check if use of the Ethernet port is enabled.
• Check if the firewall setting is disabled.
• Check if communication with Built-in Ethernet QCPU is disabled by security software.
CPU-side settings:
• Is the load for service processing too high in the target CPU? (If so, increase the service
*2:
Check the following:
PC side I/F Ethernet board setting
• Correct protocol specification (TCP/UDP)?
• Isn't direct CPU connection selected?
• Correct IP address specification?
*3:
Check if all of the following conditions are met:
• The Built-in Ethernet QCPU connected to GX Developer is in a multiple CPU configuration.
• The control CPU of the MELSECNET/H network module on the route is any other than Built-in
• The product information of the MELSECNET/H network module on the route is:
When enabled, check if communication with Built-in Ethernet QCPU is excluded in the setting.
process time in Service process setting of PLC parameters.)
PC side I/F Detailed setting of PLC module
Ethernet QCPU.
(100320000000000-D or earlier)
CHAPTER12 TROUBLESHOOTING
12 - 42
1
2
3
12
5
6
7
8