12
TROUBLESHOOTING
12.2 Troubleshooting
12.2.26 When Ethernet communication is not available by a method other than direct connection to GX
12 - 37
9
EMC AND LOW
VOLTAGE
DIRECTIVES
10
LOADING AND
INSTALLATION
11
MAINTENANCE AND
INSPECTION
12
TROUBLESHOOTING APPENDICES INDEX
* 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.
When enabled, check if communication with QnUDE(H)CPU is excluded in the setting.
• Check if communication with QnUDE(H)CPU 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
process time in Service process setting of PLC parameters.)
* 2 : Check the following:
PC side I/F Ethernet board setting
• Correct protocol specification (TCP/UDP)?
PC side I/F Detailed setting of PLC module
• Isn't direct CPU connection selected?
• Correct IP address specification?
* 3: Check if all of the following conditions are met:
• The QnUDE(H)CPU 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
QnUDE(H)CPU.
• The product information of the MELSECNET/H network module on the route is:
(100320000000000-D or earlier)
To Next Page
Loading...
Need help?
General
