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

our UR5e housing-stop ticket needs something beyond the phone clip

SofiaAdams0108 · 2026年6月17日 14:00 UTC

回复讨论
SO
SofiaAdams0108
The Alibaba seller wants more detail on intermittent housing fixture-loading stops. Ticket is 39 days old. What should I capture with the next occurrence so their technical person can narrow it down?

8 条回复

PA
PavelAdams0092

Link the exact message, current step, time and identified housing job and fixture to one occurrence, then have maintenance retrieve the matching controller and ordinary PLC evidence; keep what the operator expected separate from what happened.

7
SO
SofiaAdams0108

The old clip begins after the message was dismissed. It shows a held housing, not the preceding state. I won't guess the message from another run.

18
HA
HassanChan1052

Who can retrieve those records when you are not there, Sofia? The next useful stop may happen on a different shift.

9
SO
SofiaAdams0108

Maintenance cover can retrieve them. I've asked for one shared occurrence note so the fixture identity doesn't get detached from the saved message and time.

22
PA
PavelAdams0092

Keep the original clip in the ticket with its limitations, rather than replacing it as if the later capture proves what happened before that older film began.

24
HA
HassanChan1052

Has another event been captured under that arrangement yet?

13
SO
SofiaAdams0108

Yes, waiting for receiving fixture confirmation, with matching time and step. The locating area is hidden in the video, so physical seating remains unknown; maintenance has the event records.

23
PA
PavelAdams0092

That establishes a particular sequence wait, not a diagnosis of the gripper or locating hardware; ask the technical owner to interpret the linked evidence and identify the next observation needed.

9

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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