backendcode
Member
Hello Expert,
I am just wondering if someone can help me with my current situation.
I have 5 robots controlled by 1 Allen Bradley PLC. It's a material handling application so each robot has a gripper on EOAT. we are using Turck I/O block on each EOAT to connect my clamp, unclamp and overtravel sensors for the grippers.
On my PLC side, I am using a generic ethernet module in I/O tree to add my turck i/o block and all the turck blocks for each robot configured in the same way.
Now, One of the Turck block on EOAT having a communication issue with my PLC, seems like connection timed out or module status: fault and after a couple of seconds (between 5 to 30 seconds), it makes a connection itself.
I thought it could be a problem with my M8-RJ45 ethernet communication cable, so I replaced that but it didn't help so eventually, I replaced the Turck block but still having the same issue.
I research online and found a couple of posts related to this issue people faced in the past and they were talking about maybe some packet loss during the communication because the module is not configured properly but my another 4 Turck i/o blocks on other robots are configured exactly same way and they all are the same model and never had suck issue with them.
I am also thinking about to replace the power cable because I am thinking my power cable might be flickering.
If anyone can help or give your opinion, I would appreciate
Thank you,
I am just wondering if someone can help me with my current situation.
I have 5 robots controlled by 1 Allen Bradley PLC. It's a material handling application so each robot has a gripper on EOAT. we are using Turck I/O block on each EOAT to connect my clamp, unclamp and overtravel sensors for the grippers.
On my PLC side, I am using a generic ethernet module in I/O tree to add my turck i/o block and all the turck blocks for each robot configured in the same way.
Now, One of the Turck block on EOAT having a communication issue with my PLC, seems like connection timed out or module status: fault and after a couple of seconds (between 5 to 30 seconds), it makes a connection itself.
I thought it could be a problem with my M8-RJ45 ethernet communication cable, so I replaced that but it didn't help so eventually, I replaced the Turck block but still having the same issue.
I research online and found a couple of posts related to this issue people faced in the past and they were talking about maybe some packet loss during the communication because the module is not configured properly but my another 4 Turck i/o blocks on other robots are configured exactly same way and they all are the same model and never had suck issue with them.
I am also thinking about to replace the power cable because I am thinking my power cable might be flickering.
If anyone can help or give your opinion, I would appreciate
Thank you,