简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

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

LucaCarter0961 · 2026年6月27日 15:59 UTC

回复讨论
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 条回复

EM
EmmaAbbott0028

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
LU
LucaCarter0961

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

参与讨论

欢迎来到 Application Robot

所有人都可以阅读论坛。登录或注册后即可发起讨论、回复或上传照片。

忘记密码?

注册账号即表示你同意我们的 使用条款 社区准则。请阅读我们的 隐私政策 ,了解我们如何处理你的信息。