Mitsubishi Electric MELSEC iQ-RJ71EN71 User Manual page 255

When communication is unstable
The following lists the actions to be taken when link scan time or transmission delay time is long or when a transient
transmission timeout occurred.
Check item
■RJ71EN71, RnENCPU
Is the L ER LED of the master or slave station on?
■RJ71GF11-T2
Is the L ERR LED of the master or slave station on?
Is the ambient temperature for the module within the specified range?
Is any error shown in "Selected Station Communication Status Monitor" of CC-
Link IE Field Network diagnostics?
Is there any noise affecting the system?
If the above actions do not solve the problem, perform the following tests to check for an error.
• Module communication test ( Page 221 Module communication test)
• Cable test ( Page 239 Cable Test)
When IP communications cannot be performed using the IP packet transfer function
Before troubleshooting the problem as listed below, perform the IP communication test and take actions according to the error
code. ( Page 48 IP communication test)
If the problem cannot be solved using the IP communication test, take actions listed below.
Check item
Is the IP address of the connected Ethernet device correct?
Is the IP address already in use?
Has a communication time over error occurred in the IP
communication test?
Have the routing parameters correctly been set? (Only when
"Dynamic Routing" under "Application Settings" is set to "Disable")
Is the network number of the Ethernet device side (the third octet of
the IP address) the same as that of modules and another Ethernet
device? (This applies only when the request source external device,
request destination external device, and modules between them
have the same first and second octets of the IP address.)
Action
■RJ71EN71, RnENCPU
Perform troubleshooting for when the L ER LED turns on. ( Page 217
When the L ER LED turns on)
■RJ71GF11-T2
Perform troubleshooting for when the L ERR LED turns on. ( Page 217
When the L ERR LED turns on)
Keep the ambient temperature within the specified range by taking action
such as removing heat source.
If an error is identified at P1 or P2, perform a cable test and a module
communication test.
Check the wiring condition.
Action
Set an IP address meeting the IP address setting rules. ( Page 44 Rules for the IP
address setting)
• For the Ethernet device, set the IP address different from that of other devices on the
network, such as a Ethernet-equipped module, master/local module, and Ethernet
adapter module.
• Disconnect the Ethernet device from the line and execute the Ping command to the IP
address of the disconnected Ethernet device. If a response is received even though
the device is disconnected, the IP address is already in use. Change the IP address.
• When "Dynamic Routing" under "Application Settings" is set to "Disable", correct the
relay station network number in "Routing Setting" of "CPU Parameter".
• When "Dynamic Routing" under "Application Settings" is set to "Enable", check
'Communication path determination status' (Un\G24480 to Un\G24495) to check that
the communication path to the transfer destination network number which is set in the
third octet of the Ethernet device IP address is determined.
• Correct "Routing Setting" of "CPU Parameter".
• When the first and second octets of the IP address are the same for the request
source device, request destination device, and modules between them, set the routing
parameters so that the third octet of the IP address of the Ethernet device is used as
the target station network number.
Change the network number of the Ethernet device side (the third octet of the IP
address) to the one different from that of modules and another Ethernet device.
IP address
3 3
Ethernet
192.168. .1 192.168. .30
CC-Link
192.168.1.1
IE Field
(Automatically assigned)
Network
Station No.1
3
Network No.
Change the network numbers to those not used for other stations.
2
192.168. .30 192.168.
192.168.1.125 192.168.1.2
(Automatically assigned)
Master station Station No.2
Network No.1
Network No.
4 TROUBLESHOOTING
4.4 Troubleshooting by Symptom
4
2
.1
2
253