What should our UR5e bracket-inspection handover contain beyond pendant pictures?

LucaCarter0961 · 27 Jun 2026, 15:59 UTC

Reply to discussion
LU
LucaCarter0961
I want the integrator to walk us through the actual installed project while they're still available. Our current bracket-inspection notes show the main routine in screenshots, with no clear revision, called routines, external recipes or fixture and PLC assumptions. What structure would make that walk useful to the covering maintainer?

2 replies

EM
EmmaAbbott0028
Replying to LucaCarter0961

Start from one identified installed revision and follow a bracket through the main routine, called programs, recipe selection and ordinary PLC conditions. Keep fixture references beside that path. Then repeat the walkthrough at an interrupted or rejected step; that is where a screenshot collection usually stops explaining the job.

7 points
LU
LucaCarter0961
Replying to EmmaAbbott0028

We did the first walk with the covering maintainer. It found an external recipe file the screenshots never named, and a called routine whose saved copy differs from the installed version. Integrator is reconciling those before we accept the handover; thanks, Emma, following one actual bracket made both omissions obvious.

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