Universal Robots UR5e: Still waiting for useful help with fixture unloading

Captured it: missing process confirmation. The unedited video shows a wait before release. I'd described it as a dropped part, which didn't help.

Send a corrected description supported by the exact alarm, full recording and installed version details. Ask support to identify the expected confirmation and assign responsibility for the next diagnostic action.

Worth leaving my original description visible? It's wrong, but deleting it might make the replies look odd.

@RaviAllen0302 Keep it with a clear correction. Explain that the full clip shows a pre-release wait; that tells support why the investigation needs to change direction.

@LeoAdams0101 On my setup, the arm and gripper contacts both thought the other owned the test. Naming one coordinator helped us get an actual next step.

I've checked our messages. Same gap here: each contact asks what the other said, but neither has assigned the test.

That missing confirmation points to the gripper, so its contact should take the diagnostic lead.

You're jumping from a missing signal to a failed component. It could be the interface or sequence. The alarm doesn't assign ownership by itself.

You're right; I assigned the cause too early. Ask the package seller to coordinate tracing that confirmation across the interface, with both contacts involved as needed.

Is that Alibaba support, then? I'm muddling the seller and the place you bought it.

The unnamed seller who supplied your package. Alibaba is the marketplace; your technical request here is to the seller and their support contacts.

Would you send every log I have? There are lots, and I don't know which ones cover the stop.

Have support identify the required diagnostic files, then associate the supplied files with the recorded event and explain how they were collected. A large unrelated collection can make the relevant evidence harder to find.

I labelled my own attachments by what they showed, not 'new video final'. A small kindness to the person opening the ticket, and to myself.

Guilty of the 'final' filenames. I also cut the original clip too tightly; it lost the wait leading into the alarm.

@RaviAllen0302 Keep the unedited copy with the ticket. A shorter excerpt can point to the issue, but support needs the lead-in you've just identified.

@NinaCarter1023 Would diagnosis require repeated attempts while support observes, or can the existing alarm and full recording support the next step?

Start with what's captured. Any further equipment test needs a defined procedure from the responsible support or integration person, especially with a workpiece still held.

Correcting the symptom hasn't yet produced an agreed next step with support. We still lack a diagnostic action and the underlying issue is unresolved.