简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

A spacer in the nest and an unchanged pocket counter

Anders_Briggs · 2026年4月15日 10:58 UTC

回复讨论
AN
Anders_Briggs
My UR5e tray sequence can place a spacer and stop before saving the advance, leaving restart eager to repeat it. The counter is certain; the physical transfer isn't. I need a better recovery model.

4 条回复

FE
FelixBaker0458

Separate the source, held spacer and destination states, tied to the identified trays and transfer attempt. An uncertain placement needs reconciliation before any repeat or advance. Have the integrator define what evidence and responsible person resolve it.

13
AN
Anders_Briggs

Draft now holds uncertain placement instead of offering repeat. We track the two trays and the spacer attempt separately. The awkward example is a tray exchange while the application was stopped.

12
FE
FelixBaker0458

Include a definitely completed transfer and a definitely unstarted one too. Does reopening after a saved reconciliation preserve that decision? A recovery screen should not create the same uncertainty on every startup.

7
AN
Anders_Briggs

Offline cases now keep those distinctions across reopening, including the exchanged-tray mismatch. The operator walkthrough still needs doing. At least the counter no longer gets the casting vote.

17

参与讨论

欢迎来到 Application Robot

所有人都可以阅读论坛。登录或注册后即可发起讨论、回复或上传照片。

忘记密码?

注册账号即表示你同意我们的 使用条款 社区准则。请阅读我们的 隐私政策 ,了解我们如何处理你的信息。