Does your clip include the displayed message and the action immediately before this particular stop?
UR5e housing-unloading ticket needs one identifiable stop, not a compilation
OwenBrooks0834 · 6 Jul 2026, 13:49 UTC
21 replies
No readable message. It shows the housing still in the tray and the stationary tool above it. Maintenance has the installed job revision, but the phone time only narrows the event search.
4 pointsThen don't caption it failed pickup yet. Could be waiting before pickup. Preserve that distinction while maintenance looks for the event and exact active step.
10 pointsWho owns the local investigation while the seller replies? A remote contact can interpret a job record but cannot inspect an unspecified gripper fault from that view. Define what your maintainer is authorised to inspect and what support must explain
0 pointsOur maintenance lead owns the local checks. Support has supplied the installed sequence description: before tray entry it requires gripper-open confirmation. The old clip cannot establish whether that was the missing condition in its occurrence.
20 pointsCan the retained records distinguish the commanded open state from its observed confirmation?
17 pointsFor the next documented occurrence, yes. The event record shows an open command and no confirmation at the wait. The operator account identifies the tray and job; this is a new occurrence, not a recovered message for the original clip.
1 pointsWas the gripper physically open when that confirmation was absent, Owen?
10 pointsElliot's question is the useful fork, but don't get someone reaching into the cell to answer it. Existing observations or a qualified inspection under the proper procedure, with what cannot be seen left unknown.
16 pointsAnd no need to recreate the stop just to make a better film. The retained command and confirmation already give the maintainer a narrower inspection than intermittent robot trouble.
12 pointsThe normal observation view did not show the jaw position clearly enough. Maintenance's subsequent inspection found the open-position sensing assembly loose relative to its specified mount. They are checking the mounting condition, not changing the robot pickup points.
10 pointsDid they find damaged mounting parts, or a sound assembly which had moved?
7 pointsAlso retain which mount they found loose. A note saying sensor adjusted would lose the difference between a mounting repair and deciding the original sensing position was wrong.
10 pointsFiona, would you include the confirmed physical open position in the repair check, rather than only a returning input?
5 pointsYes. The confirmation must represent the intended condition. A changing bit alone isn't the acceptance test; maintenance needs the equipment's specified inspection and functional checks, followed by the authorised application verification.
12 pointsYasmin, the mounting hardware was damaged and has been replaced to the specified arrangement. Fiona and Elliot, the report identifies the assembly and confirms its open-position indication against the physical condition. The supervised application check is still to follow.
15 pointsKeep the original unidentified stops outside that conclusion. This repair addresses a found defect and the documented wait; it doesn't retrospectively supply missing evidence for every earlier halt
23 pointsWho will tell the covering operator what was repaired and which old occurrences remain unexplained?
3 pointsI own the handover with maintenance. The supervised checks now include normal opening, unloading, tray replacement and the specified interruption cases; the repaired indication behaved as required and that wait did not recur. The ticket separates this closed finding from the older unclassified clips.
8 pointsThanks for coming back with the physical finding as well as the signal result, Owen; is the reason for the mounting damage known?
1 pointsAdd 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.