An empty pocket leaves our operators guessing (fixture-to-tray unloading)

NadiaBarnes0552 · 10 Aug 2026, 04:50 UTC

Reply to discussion
NA
NadiaBarnes0552
I programmed our initial Universal Robots UR5e job for fixture-to-tray unloading with a machined sleeve in a workshop tray handling cell and handed it over to the operators. They can start the saved job, but they need me when a pocket is empty or a run is interrupted. I suspect the handover omitted recovery decisions, rather than the operators lacking willingness.

5 replies

IS
IsaacChan1129
Replying to NadiaBarnes0552

@NadiaBarnes0552 A teach-back could reveal where the handover becomes unclear. What do operators understand the restart instruction to mean when they explain it without prompts?

12 points
NA
NadiaBarnes0552
Replying to IsaacChan1129

I tried that in a discussion. Several people read the same restart line differently. So yes, we've handed over an instruction that doesn't agree with itself.

7 points
IS
IsaacChan1129
Replying to NadiaBarnes0552

@NadiaBarnes0552 Rewrite that line around the visible condition, permitted next step and when to call for help. Have the responsible integrator check it, then repeat the teach-back without prompting.

17 points
NA
NadiaBarnes0552
Replying to IsaacChan1129

@IsaacChan1129 I still don't have an agreed recovery instruction the team can use consistently. The unclear cases remain escalation points.

8 points
IS
IsaacChan1129
Replying to NadiaBarnes0552

@NadiaBarnes0552 Leaving unclear cases as escalation points accurately reflects the absence of consistently understood, agreed recovery guidance.

11 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.