# UR5e losing comms with Robotiq gripper

**URL:** <https://forum.universal-robots.com/t/ur5e-losing-comms-with-robotiq-gripper/34831>\
**Category:** Technical Questions\
**Created:** [June 19, 2024, 9:33pm UTC](https://forum.universal-robots.com/t/ur5e-losing-comms-with-robotiq-gripper/34831 "2024-06-19T21:33:44Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamesc](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/jamesc/32/6240_2.png) [@jamesc](https://forum.universal-robots.com/u/jamesc)\
**Post date:** [June 19, 2024, 9:33pm UTC](https://forum.universal-robots.com/t/ur5e-losing-comms-with-robotiq-gripper/34831/1 "2024-06-19T21:33:44Z")

</div>

I have a problem that started a few weeks ago and has gone from once in a week to several times a day, the robot locks up and displays a message “Gripper1 must be connected to run this program” this is happening in the middle of a set not the same spot, the gripper seems to be functioning properly but this is creating significant disruptions in production. Any thoughts would be helpful.

---

<div class="post-metadata">

**Author:** ![efn](https://avatars.discourse-cdn.com/v4/letter/e/35a633/32.png) [@efn](https://forum.universal-robots.com/u/efn)\
**Post date:** [June 20, 2024, 4:58am UTC](https://forum.universal-robots.com/t/ur5e-losing-comms-with-robotiq-gripper/34831/2 "2024-06-20T04:58:20Z")

</div>

If you’re not getting any response here, you should contact Robotiq or the distributor of the gripper. 🙂  
Sounds like an issue with the gripper and not the robot.

---

<div class="post-metadata">

**Author:** ![jsiegenfeldta](https://avatars.discourse-cdn.com/v4/letter/j/ea5d25/32.png) [@jsiegenfeldta](https://forum.universal-robots.com/u/jsiegenfeldta)\
**Post date:** [June 24, 2024, 9:05am UTC](https://forum.universal-robots.com/t/ur5e-losing-comms-with-robotiq-gripper/34831/3 "2024-06-24T09:05:05Z")

</div>

sounds like a wire is about to break so it looses connection to the robot intermittandly

---

<div class="post-metadata">

**Author:** ![jamesc](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/jamesc/32/6240_2.png) [@jamesc](https://forum.universal-robots.com/u/jamesc)\
**Post date:** [June 24, 2024, 1:19pm UTC](https://forum.universal-robots.com/t/ur5e-losing-comms-with-robotiq-gripper/34831/4 "2024-06-24T13:19:31Z")

</div>

Yes we thought that was the likely root cause so we replaced the cable from the robot to the gripper. the problem remained. we are looking at the possibility of a connection problem at one of the joints.

---

<div class="post-metadata">

**Author:** ![efn](https://avatars.discourse-cdn.com/v4/letter/e/35a633/32.png) [@efn](https://forum.universal-robots.com/u/efn)\
**Post date:** [June 25, 2024, 6:30am UTC](https://forum.universal-robots.com/t/ur5e-losing-comms-with-robotiq-gripper/34831/5 "2024-06-25T06:30:52Z")

</div>

If you suspect a bad connection in the robot arm, it will have to be inside the tool mounting flange.  
All the tool signals are generated inside the flange. It’s only 48V, GND and two bus wires that run through the robot arm.

So you could try to replace the tool mounting flange. I think you would have seen other errors though, if the fault was here. I still believe the gripper to be the culprit. 🙂

---

<div class="post-metadata">

**Author:** ![jsiegenfeldta](https://avatars.discourse-cdn.com/v4/letter/j/ea5d25/32.png) [@jsiegenfeldta](https://forum.universal-robots.com/u/jsiegenfeldta)\
**Post date:** [June 28, 2024, 6:43am UTC](https://forum.universal-robots.com/t/ur5e-losing-comms-with-robotiq-gripper/34831/6 "2024-06-28T06:43:31Z")

</div>

is the gripper connected through the 8 pin connector on the flange ? then it can be every joint .

---

<div class="post-metadata">

**Author:** ![efn](https://avatars.discourse-cdn.com/v4/letter/e/35a633/32.png) [@efn](https://forum.universal-robots.com/u/efn)\
**Post date:** [June 28, 2024, 7:12am UTC](https://forum.universal-robots.com/t/ur5e-losing-comms-with-robotiq-gripper/34831/7 "2024-06-28T07:12:47Z")

</div>

@jsiegenfeldta What do you base that statement on? 🙂 Because I strongly disagree, as I explained in my earlier message.

---

<div class="post-metadata">

**Author:** ![jsiegenfeldta](https://avatars.discourse-cdn.com/v4/letter/j/ea5d25/32.png) [@jsiegenfeldta](https://forum.universal-robots.com/u/jsiegenfeldta)\
**Post date:** [June 28, 2024, 7:57am UTC](https://forum.universal-robots.com/t/ur5e-losing-comms-with-robotiq-gripper/34831/8 "2024-06-28T07:57:34Z")

</div>

last i checked the electrical connections in the joints are transferred through a disk and a pick up . we had problems in a elbow joint  
with bad connections

---

<div class="post-metadata">

**Author:** ![efn](https://avatars.discourse-cdn.com/v4/letter/e/35a633/32.png) [@efn](https://forum.universal-robots.com/u/efn)\
**Post date:** [June 28, 2024, 8:12am UTC](https://forum.universal-robots.com/t/ur5e-losing-comms-with-robotiq-gripper/34831/9 "2024-06-28T08:12:57Z")

</div>

All joints are hardwired to the next one. 🙂 The UR3(e) has a slip ring connector on the last joint (wrist 3 - tool mounting flange), which allows it to rotate indefintiely. But that’s the only joint and the only robot model with a slip ring disc.  
I highly doubt a bad connection in a joint on the bus wires will show as a gripper losing connection, since there will be issues with the communication to said joint. I believe that should show before it shows issues at the gripper. 🙂

---

<div class="post-metadata">

**Author:** ![jsiegenfeldta](https://avatars.discourse-cdn.com/v4/letter/j/ea5d25/32.png) [@jsiegenfeldta](https://forum.universal-robots.com/u/jsiegenfeldta)\
**Post date:** [June 28, 2024, 8:50am UTC](https://forum.universal-robots.com/t/ur5e-losing-comms-with-robotiq-gripper/34831/10 "2024-06-28T08:50:05Z")

</div>

ok my bad you are probably right . i have trust issues with joints

---

<div class="post-metadata">

**Author:** ![memc](https://avatars.discourse-cdn.com/v4/letter/m/ccd318/32.png) [@memc](https://forum.universal-robots.com/u/memc)\
**Post date:** [July 3, 2024, 7:08pm UTC](https://forum.universal-robots.com/t/ur5e-losing-comms-with-robotiq-gripper/34831/12 "2024-07-03T19:08:46Z")

</div>

The joints are all connected in series with individual power/com wires on each joint. A com error could be a result of a pinched or loose com in any of the joints. It could also be the tool bracket itself as those can also cause com errors quite frequently. The slip ring in wrist 3 can also cause these types of errors.

---

<div class="post-metadata">

**Author:** ![efn](https://avatars.discourse-cdn.com/v4/letter/e/35a633/32.png) [@efn](https://forum.universal-robots.com/u/efn)\
**Post date:** [July 4, 2024, 8:41am UTC](https://forum.universal-robots.com/t/ur5e-losing-comms-with-robotiq-gripper/34831/13 "2024-07-04T08:41:10Z")

</div>

@memc This is a UR5e, so there’s no slip ring. 🙂

I am pretty confident that a bad communication wire in a joint would lead to a robot error with lost communication packages, before it shows issues with the gripper in a URCap.  
Would you not agree with this? 🙂

I’d still say either the electronics in the gripper or the tool mounting bracket being at fault.
