What should accompany this UR5e fixture-loading video?

ThomasBrooks0799 · 8 May 2025, 17:05 UTC

Closed
TH
ThomasBrooks0799
Our connector-loading package pauses with the part above the nest. The seller we bought from through Alibaba wants more evidence than my video. I can see the arm stop, but not the message screen. I would like to stop calling it a grip fault until we know what the program is waiting for

17 replies

JA
JamieChan1078
Replying to ThomasBrooks0799

Get the exact message and active step, plus the time for finding the event record. Start there.

17 points
TH
ThomasBrooks0799
Replying to JamieChan1078

The operator saved a photo from one pause: waiting for nest available. The video is from another occurrence. I have told support they may not be the same issue

7 points
JA
JamieChan1078
Replying to ThomasBrooks0799

Was that nest empty?

14 points
TH
ThomasBrooks0799
Replying to JamieChan1078

According to the operator, yes. No clear image of it. We are collecting the nest view with the screen next time

13 points
JA
JamieChan1078
Replying to ThomasBrooks0799

Which program revision are they looking at?

6 points
AN
AnnaBell0677
Replying to ThomasBrooks0799

Can the operator send that photo directly, rather than waiting for you to appear? My own support report improved once we stopped filming everything except the display.

22 points
TH
ThomasBrooks0799
Replying to JamieChan1078

Yes, shift technician is collecting it. Support has our current revision now, confirmed against the installed backup. They had initially referred to an older message name

12 points
JA
JamieChan1078
Replying to ThomasBrooks0799

That would make for an unhelpful conversation. Glad you checked.

13 points
DI
DineshBrooks0821
Replying to ThomasBrooks0799

Ask them which input or combination of conditions controls nest available in that revision. Then maintenance can compare the displayed state with the empty nest at the same occurrence. I would avoid a sensor replacement until those details are known.

15 points
TH
ThomasBrooks0799
Replying to DineshBrooks0821

Requested. No replacement parts ordered. Thanks for making the question concrete; my original report was basically please explain this stationary arm

8 points
LE
LeahAli0234
Replying to ThomasBrooks0799

Our shift got into a habit of closing messages before anyone read them. The helpful change was a tiny card beside the screen with photo, time, what the station was doing. People actually used that. The full troubleshooting document remained beautifully unread.

8 points
JA
JamieChan1078
Replying to ThomasBrooks0799

Thomas, have you caught another pause with both views?

17 points
TH
ThomasBrooks0799
Replying to JamieChan1078

Yes. Empty nest, occupied input shown. Maintenance is investigating with the integrator. That is enough to narrow this occurrence, though the old video still has no matching screen information

11 points
JA
JamieChan1078
Replying to ThomasBrooks0799

Keep that older occurrence unclassified for now.

11 points
AN
AnnaBell0677
Replying to ThomasBrooks0799

Did the seller explain who handles the package-level problem if the ordinary I/O mapping is wrong: their support person or your integrator?

4 points
TH
ThomasBrooks0799
Replying to AnnaBell0677

Integrator owns the local check, with the seller supplying the original interface details. One ticket contact at our end. Cause still open; we have not yet established why occupied remained indicated

15 points
DI
DineshBrooks0821
Replying to ThomasBrooks0799

Please keep the final finding with that message and program revision. The next technician will otherwise inherit the same vague grip-fault description you started with.

9 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .