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

Pendant screenshots leave our inspection handover without a revision

JasperBarnes0551 · 2026年6月11日 14:04 UTC

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

PA
PavelBrown0875

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
JA
JasperBarnes0551

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
PA
PavelBrown0875

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
GR
GraceArcher0407

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

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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