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

LeahAdams0147 · 8 Sept 2025, 02:30 UTC

Closed
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 replies

SA
SamBell0681
Replying to LeahAdams0147

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 points
LE
LeahAdams0147
Replying to SamBell0681

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 points
AM
AmyAllen0293
Replying to LeahAdams0147

Don't call it a gripper fault meanwhile.

22 points
LE
LeahAdams0147
Replying to AmyAllen0293

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

6 points
JA
JaneBarnes0597
Replying to LeahAdams0147

What does that active step expect?

11 points
LE
LeahAdams0147
Replying to JaneBarnes0597

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 points
SA
SamBell0681
Replying to LeahAdams0147

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 points
GR
GraceAli0233
Replying to LeahAdams0147

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 points
LE
LeahAdams0147
Replying to GraceAli0233

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 points
SA
SamBell0681
Replying to LeahAdams0147

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 points
AM
AmyAllen0293
Replying to SamBell0681

Shared shift note. Not another private phone album.

11 points
LE
LeahAdams0147
Replying to SamBell0681

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 points
JA
JaneBarnes0597
Replying to LeahAdams0147

Has maintenance traced the release confirmation yet?

12 points
LE
LeahAdams0147
Replying to JaneBarnes0597

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 points
GR
GraceAli0233
Replying to LeahAdams0147

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 points
SA
SamBell0681
Replying to LeahAdams0147

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 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .