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

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.

Don't call it a gripper fault meanwhile.

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

What does that active step expect?

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.

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.

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.

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

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.

Shared shift note. Not another private phone album.

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

Has maintenance traced the release confirmation yet?

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

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.

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.