Our UR5e transfer helper advances the source pocket after pickup. Stop before placement and the next screen starts at the following pocket, with no clear state for the sleeve possibly still held. The training draft calls that resume. I call it missing information.
Pocket saved as empty while the sleeve may still be held
NadiaChan1074 · 2025年8月20日 09:44 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
4 条回复
Does the saved state say anything about the destination pocket? You need to distinguish not picked, possibly held and possibly placed before deciding what recovery can do.
7分Destination isn't saved until placement finishes. Between those writes, the file only knows the next source pocket. That is the gap we're fixing.
10分Include interrupted saving in the offline cases as well as interrupted motion. Or rather, a file update failure might leave the same uncertainty even when the physical placement happened.
21分Developer is adding separate transfer states and routing uncertain ones to the agreed recovery check, not the next pickup. We haven't tested the revised sequence yet. The old resume instruction is out of the training draft.
17分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .