My UR5e handover works until the first empty pocket

Ian_Carr · 28 Jun 2026, 16:01 UTC

Reply to discussion
IA
Ian_Carr
I handed our polymer-block loading job to the operators and they can start it, but an empty pocket or interruption still brings me back. I think I taught the saved sequence and left out the decisions around it. How do I find what the handover needs without turning it into another long start-up lesson?

8 replies

JA
JasperAbbott0029
Replying to Ian_Carr

Ask someone to talk through one real interruption from the screen they saw. I'd listen for the point where they need information only you carry around in your head.

24 points
IA
Ian_Carr
Replying to JasperAbbott0029

One operator thought Continue meant advance to the next pocket. I meant continue the current routine after an authorised recovery. Neither meaning appears beside the button, which explains why asking them to be more confident would be unfair.

3 points
PR
PriyaBarnes0568
Replying to Ian_Carr

Fix that decision with the process owner before teaching either interpretation. The label is ambiguous.

11 points
IA
Ian_Carr
Replying to PriyaBarnes0568

The owner has separated the empty-pocket case from uncertain transfer state. The revised screen names the job and pocket, shows why it is stopped and sends uncertain transfer state to the shift lead. Recovery actions are being reviewed against those cases, not left behind Continue.

3 points
JA
JasperAbbott0029
Replying to Ian_Carr

Can the covering shift lead use it too? Otherwise you've moved the phone call one person along without giving them the missing decision.

10 points
PR
PriyaBarnes0568
Replying to Ian_Carr

And test an interruption after pickup. Empty source pocket then means something quite different.

21 points
IA
Ian_Carr
Replying to JasperAbbott0029

We completed the reviewed exercises with both shifts, including empty source, stopped-before-pickup and uncertain transfer after pickup. They identified the correct escalation and didn't infer a new pocket from the empty one. Jasper, thanks for the talk-through idea; their original explanation exposed the misleading label immediately.

14 points
JA
JasperAbbott0029
Replying to Ian_Carr

That sounds like a usable handover now. Keep the scenario notes with the released job so the next trainer can repeat the same exercise instead of relying on your visit.

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