What would move this UR5e unloading ticket beyond another clip?
OwenBrown0921 · 21 Jun 2026, 22:34 UTC
17 replies
What does this clip actually show around the stop? Start there. A visible spacer doesn't tell support which step the controller was trying to complete.
19pointsIt starts after the arm has stopped, holding the spacer above the fixture. No readable message. I cannot tell whether that position was the intended wait or the place movement ceased.
5pointsThen don't describe the position as the cause. Keep it as an observation and ask which message and sequence details would distinguish those possibilities.
14pointsWho is collecting the next occurrence, Owen? One person needs a clear request before another shift films the same stationary arm and hopes the angle makes it a diagnosis.
12pointsAnd give that person the operator's account to retain too, because the seconds before the stop may include a fixture or part change that doesn't appear in a later screen photograph.
8pointsKeep the clocks explicit if video and logs use different times. I had to untangle that on a connector report before anybody could match an event.
7pointsChen, our shift lead will coordinate it. Sofia and Yasmin, I have added preceding actions and clock information. We can provide installed revisions now without waiting for another occurrence.
12pointsDoes the seller have a named technical recipient for that material, or are you still asking sales to decide what their engineer might need?
3pointsI'd avoid collecting a huge bundle just because no technician has answered. A short occurrence index helps, but Owen still needs someone to say which additional evidence answers the fault question.
1pointsStill through sales. I have asked for the technical recipient and whether they can use our retained history with the approximate clip time. I have not claimed an exact event match.
3pointsGood. Approximate time can narrow a search, but several similar stops can sit inside it. Don't choose the nearest-looking entry merely to complete the report.
12pointsWho tells the relief shift what remains unknown, Owen, so they don't inherit a note saying spacer fault when all you have established is a spacer held during the wait?
18pointsThe shift lead has corrected that wording in the handover. A later occurrence has a readable message and preceding sequence captured, but its video clock differs from the history export.
17pointsRecord that difference, don't quietly edit one timestamp. Can a distinct visible event link the two records, or is the relationship still uncertain?
21pointsYasmin's question is worth answering before forwarding it as one matched occurrence. The operator account still has value independently, even if the exact log correspondence remains open.
7pointsI cannot establish a unique link yet. Thank you Yasmin; the report now preserves both clocks and marks the possible history entries as candidates. We still need the technical recipient to narrow that down.
17pointsThen the better capture is progress, not a diagnosis. Keep the original limited clip separate so nobody combines its held spacer with a later message and calls that one event.
11pointsAdd to the discussion
Welcome to Application Robot
Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.
By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.