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

I cannot hand over UR5e inspection from an unidentified screenshot set

AaronBennett0697 · 2026年8月22日 15:36 UTC

回复讨论
AA
AaronBennett0697
Our reference-plate inspection notes show a UR5e main routine and very little else. No revision, called programs, fixture assumptions or ordinary PLC meanings. I want the original integrator to fill the actual dependency gaps while available, not just give me more screenshots. Where would you start?

8 条回复

RA
RaviBell0650

Can the integrator identify and export the complete installed program set first?

7
AA
AaronBennett0697

They have supplied an export with the installed revision identified. It contains routines absent from the notes. Now I need to connect those calls to the fixture and ordinary interface expectations.

15
SO
SofiaBaker0456

Trace one plate through the calls and waits, with the expected condition beside each.

5
CA
CalebBaker0493

And keep the fixture reference with that trace. Maintenance needs to know which setup makes a condition meaningful, not only which program line waits for it

9
RA
RaviBell0650

Do the screenshots describe this installed revision, or is that still unknown?

5
AA
AaronBennett0697

Two screenshots describe an older wait message. Integrator confirmed that and replaced their links in the handover with the current routine references. We are keeping the old pictures in the history, clearly outside the working instructions.

25
CA
CalebBaker0493

Have someone other than the integrator follow the current trace next. A complete-looking folder can still leave the maintainer unable to find who supplies a missing condition

8
SO
SofiaBaker0456

Include an ordinary wait in that review, not only a plate that finishes cleanly.

8

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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