YasminChen1137 · 15 Jan 2026, 10:40 UTC
Get the available history for that occurrence first. A matching export is more use than extending the video after the arm has already stopped.
11 pointsI'm chasing a ready-condition wait on another package. Support only became useful when asked which underlying fixture condition they needed. Does your waiting step name that condition, or just say unloading?
8 pointsJasper, it says destination clear. The matching export was retained after all; destination clear is absent before the unload request.
6 pointsWas the destination actually occupied? Ask the operator who saw it, not just the person reading that signal.
12 pointsKeep physical observation and reported condition separate until someone explains the mismatch.
6 pointsTom, yes, though an occupied destination might mean no mismatch at all. It could be waiting exactly as intended and the real problem is how that state is explained to the operator.
6 pointsCan the operator see the receiving pocket from the normal loading position? I've been caught assuming that because the phone camera could.
20 pointsAgreed, Pat. I should have said possible mismatch.
25 pointsElena and Zara, the operator says a block remained in the receiving pocket, hidden from his usual position. The wide still in our clip shows it too. He thought the wait meant the robot hadn't gripped.
9 pointsThen don't order gripper parts on the strength of that clip. How did the block come to remain there?
7 pointsYasmin, what wording does the operator screen use at that point? A correct condition with the wrong label can send every caller down the same path.
0 pointsScreen says 'transfer not complete'. Support traced the retained block to an earlier interrupted unload; this capture starts afterwards. We still don't know what interrupted that earlier transfer.
8 pointsThat wording is doing you no favours. Ask for the occupied destination and the undecided earlier transfer to be explained separately. Otherwise they'll rename the wait and everyone will assume the original interruption was repaired.
9 pointsThe operator's explanation is useful evidence about the screen, not an embarrassing mistake to bury. Thank you for including it. That's precisely the misunderstanding a handover should catch.
24 pointsRevised screen wording passed our operator walkthrough: he identified the occupied destination and called for the agreed recovery help. No gripper order. The older interruption stays on the ticket as unexplained.
11 pointsDid they improve visibility of the receiving pocket too, or is the screen still his only useful view?
18 pointsThis discussion is closed to new replies after six months without activity. Last activity: .