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

Which fixture-ready state belongs with our UR5e sleeve-loading pause?

LeahAdams0147 · 2025年9月8日 02:30 UTC

已关闭
LE
LeahAdams0147
I have a sleeve-loader video showing the tool waiting above the fixture, but the only message screenshot was taken after somebody acknowledged the screen. Our imported package's seller wants more detail. I want the next report to show what it was waiting for, not what the screen looked like once everyone had tried to help.

16 条回复

SA
SamBell0681

Can maintenance retrieve the event history for the video's occurrence time? Start with the original message and active step. The later screenshot may still be useful, but label it as after acknowledgement.

7
LE
LeahAdams0147

History has waiting for fixture ready, but the person exporting it omitted the program step. I've asked them to include it. The acknowledgement screenshot is labelled separately now.

8
AM
AmyAllen0293

Don't call it a gripper fault meanwhile.

22
LE
LeahAdams0147

We did in the ticket title. Changed it to fixture-loading wait. Nobody has actually found a gripper problem.

6
JA
JaneBarnes0597

What does that active step expect?

11
LE
LeahAdams0147

Support says fixture seated and fixture released must both be present. They're asking for a capture of those two ordinary inputs at the wait.

6
SA
SamBell0681

Get both in one capture with the fixture identifier. I mean the physical fixture, not just whichever recipe is selected, because a replacement fixture can carry the same job name.

0
GR
GraceAli0233

Keep the physical observation too. On one of our videos a clamp looked open and I called it released. We didn't have the confirmation, which was the thing the sequence actually needed.

11
LE
LeahAdams0147

Grace, ours looks open as well, but we're leaving that as a visual observation. Sam, fixture F6 is named in the capture request.

10
SA
SamBell0681

Who will send that capture when the wait happens on a shift you're not covering? A decent request is only useful if the next person can find it.

10
AM
AmyAllen0293

Shared shift note. Not another private phone album.

11
LE
LeahAdams0147

Shift lead owns it now. We got F6 with seated present and released absent. Support has that capture with the original step and message.

15
JA
JaneBarnes0597

Has maintenance traced the release confirmation yet?

12
LE
LeahAdams0147

Inspection found its target loose. Maintenance is correcting the mounting, then checking the confirmation and agreed recovery sequence. No return-to-service result yet.

12
GR
GraceAli0233

That's more useful than my old looks-open guess. Keep the target location in the repair note so the next person knows which part of F6 was involved.

15
SA
SamBell0681

Leah, does the supplier need the post-repair comparison under the same ticket? Ask before the next shift sends a fresh report with none of this history attached.

7

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .