Pendant screenshots leave our inspection handover without a revision

JasperBarnes0551 · 11 Jun 2026, 14:04 UTC

Reply to discussion
JA
JasperBarnes0551
I have photographs of the UR5e main routine and almost none of the context needed to support our sample-housing inspection. No subprogram trail, fixture assumptions or ordinary PLC signal definitions. What should I ask the integrator to walk through before they leave?

4 replies

PA
PavelBrown0875
Replying to JasperBarnes0551

Start with the actual installed project and its dependencies, then have them identify how that version was checked against this fixture, because a folder full of exports can be just as mysterious as your photographs if nobody knows which one belongs on the bench.

10 points
JA
JasperBarnes0551
Replying to PavelBrown0875

They can provide an export. I have asked them to identify the installed revision as well; I do not want the handover silently switched to their newer office copy.

9 points
PA
PavelBrown0875
Replying to JasperBarnes0551

Bring one ordinary cycle and one interrupted inspection to the walkthrough, Jasper, and have both controls owners explain expected request, accepted, complete and fault states against that same revision. Otherwise each team may describe the interface they meant to build.

6 points
GR
GraceArcher0407
Replying to JasperBarnes0551

Include the fixture drawing and sample assumptions beside that walkthrough. A program export cannot explain why a housing is expected to seat against a particular face.

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