Our UR5e test stopped after placement but before the pocket update. On restart it offers that pocket again. One saved number, two different ideas about where the spacer is. What should the recovery review include?
A saved destination that already has a spacer
JoelBlair · 2025年11月7日 00:26 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
3 条回复
回复 JoelBlair
Write the physical observation beside the saved state for that interruption, then test the boundaries around pickup, placement and saving. Include tray and transfer identity. Where the outcome cannot be established, recovery needs an explicit unresolved case, not an automatic repeat based on the old number.
15分Controls has put the unresolved case into the draft. We can identify the tray but still lack confirmation for the destination at one boundary. That gap is staying visible before operator practice.
13分回复 JoelBlair
Please post what the review decides there. Also check a second restart while that transfer remains unresolved; a careful first screen won't help if the next startup silently rebuilds it as ordinary work.
2分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .