Our FR5 spacer-block unloading ticket is 18 days old. Seller on Alibaba wants more than the clip. I have the waiting-step name; the ordinary PLC export doesn't cover the same occurrence.
Which FR5 state does support need when unloading waits?
YasminChen1137 · 2026年1月15日 10:40 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
16 条回复
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分I'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分Jasper, it says destination clear. The matching export was retained after all; destination clear is absent before the unload request.
6分Was the destination actually occupied? Ask the operator who saw it, not just the person reading that signal.
12分TO
Keep physical observation and reported condition separate until someone explains the mismatch.
6分PA
回复 TomMill
Tom, 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分Can the operator see the receiving pocket from the normal loading position? I've been caught assuming that because the phone camera could.
20分TO
回复 PatBlair
Agreed, Pat. I should have said possible mismatch.
25分Elena 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分Then don't order gripper parts on the strength of that clip. How did the block come to remain there?
7分Yasmin, 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分Screen 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分That 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分PA
The 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分Revised 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分Did they improve visibility of the receiving pocket too, or is the screen still his only useful view?
18分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .