Which occurrence details would make our UR5e connector-stop video useful?

EllaAdams0120 · 12 Jun 2026, 12:02 UTC

Reply to discussion
EL
EllaAdams0120
Our imported UR5e tray-loading package stops intermittently with molded connector bodies. The seller has asked for more information after my phone video, and the report is now 33 days old. I want to give them a coherent occurrence rather than a larger pile of unrelated pictures.

11 replies

IM
ImranAllen0305
Replying to EllaAdams0120

Start with the message and step at the stop, then the matching log interval and installed program and fixture references. You don't have to film every minute of production, but support needs enough context to know what the equipment was waiting for.

19 points
EL
EllaAdams0120
Replying to ImranAllen0305

My message photograph was taken after the video, and I cannot establish that it belongs to the same occurrence. I have labelled that uncertainty in the ticket rather than letting them assume a match.

8 points
FA
FarahBarnes0591
Replying to EllaAdams0120

That is worth correcting. Ask the shift lead to capture the screen and occurrence time together during the next normal stop, following the cell procedure. The original video can stay as background, but it should not supply a message nobody saw in it.

20 points
EL
EllaAdams0120
Replying to FarahBarnes0591

I've arranged that with the shift lead and requested the relevant log instructions from support. Stores has also identified the installed tray fixture; the first email used an old drawing number.

6 points
IM
ImranAllen0305
Replying to EllaAdams0120

Include the current fixture reference in the corrected ticket, Ella. If the old drawing has different locating or detection features, support could spend their time explaining hardware that isn't there.

4 points
YA
YasminBell0615
Replying to EllaAdams0120

Does the video show which tray pocket was active? That may help match the step.

13 points
EL
EllaAdams0120
Replying to YasminBell0615

Yasmin, the old video does not. We have now captured a new occurrence with the active pocket, program step and screen message together. The message concerns receiving-position confirmation, and support has the corresponding log interval.

4 points
IM
ImranAllen0305
Replying to EllaAdams0120

That's a much more useful occurrence. I'd ask support to identify the confirmation source in your installed revision before anyone treats that wording as proof of a bad detector.

18 points
FA
FarahBarnes0591
Replying to EllaAdams0120

Was that the first placement after a tray exchange, Ella? I ask because knowing the preceding operation can guide the investigation, though one occurrence would not establish that tray exchange caused the stop.

13 points
EL
EllaAdams0120
Replying to FarahBarnes0591

It was after an exchange, Farah. I have added that to this occurrence only. We do not have the same detail for the earlier stops, and the cause is still unknown.

6 points
AN
AnnaAbbott0068
Replying to EllaAdams0120

Ask whether the technical reviewer has enough to trace that receiving confirmation now, because another generic request for video would leave your improved ticket sitting in exactly the same queue.

2 points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.