HarishAllen0315 · 31 May 2025, 04:25 UTC
What does the screen say at the pause?
23 pointsWaiting for release confirmation. The sleeve looks down in the pocket, but the camera angle hides the fingers.
8 pointsWhere does that confirmation come from?
21 pointsA gripper state read through our application. I haven't yet matched that read with the physical jaw state.
19 pointsThat's the comparison I'd ask maintenance for first.
11 pointsDoes the log show a failed read or a closed-jaw value?
19 pointsIt only writes release not confirmed. That line combines a failed read with an actual closed indication. We need separate logging for those cases.
10 pointsAh, two problems wearing the same message.
9 pointsAsk the programmer to include the request result as well as the interpreted jaw state. That should tell you which branch produced the wait when it happens again.
3 pointsCan you still get the raw result from the original incident?
22 pointsOur operator notes once said stuck gripper when the screen merely said no confirmation. Ask the shift what they saw as well; they may remember whether the jaws moved even though your video missed them.
14 pointsHarish, did anyone see the jaws on that occurrence?
14 pointsOperator remembers them opening. No raw read was saved, so I have kept that observation separate from the missing software result.
19 pointsAny repeat since the logging change?
10 pointsAnd does it now preserve the request error itself?
18 pointsYes. One repeat captured a communication error, with the jaws visibly open. I've sent that matched incident to support. We don't know why the read failed yet.
8 pointsThat's a different repair conversation from replacing a gripper. What did support say?
21 pointsThis discussion is closed to new replies after six months without activity. Last activity: .