our sleeve stop has the right time but the wrong fixture name

The overview is ready. It shows the unloading fixture, receiving tray and their markings. The screen calls both positions station 2 in different pages.

Keep the screen names as quotations, then map each to the physical identity in your note. Otherwise changing your wording to be clearer can make support think you are describing a different signal again.

I have done that. The seller now asks which insert was in the unloading fixture, not which tray. That is a better question, though I do not have the answer yet.

The fixture marking may identify its carrier rather than the removable insert. Check that distinction before attaching a drawing revision to the whole assembly.

Keep the actual sleeve from that occurrence if you can find it, Emma. Sorry, more precisely: don't substitute a fresh sleeve and describe it as the one in the video. A comparison sample can still be useful, just named honestly.

Rosa, the sleeve was returned to the batch, so its identity is lost. Callum, the marking is on the carrier. Tooling is checking the changeover entry for the insert.

Then leave the sleeve unidentified. No point manufacturing certainty for a better-looking ticket.

Does the original video show any insert feature that tooling can compare with the entry? A paperwork match would be stronger with a visible physical detail, especially if more than one insert fits that carrier.

The original clip shows a corner relief that the forwarded version cropped out. Tooling says it matches the insert named in the changeover entry. They have now supplied its drawing reference.

Useful. Did support explain what condition it expected from that insert at the captured step, or are they still only collecting identifiers?

That answer should include whose signal it is. Emma already found two meanings around the tray wording; matching the hardware won't by itself settle the interface description.

Both teams now agree which fixture and ordinary permission the wait concerns. The integrator is checking the source condition from that occurrence. No fault cause confirmed, but the discussion has finally stopped moving between two stations.