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

I cannot choose the next pocket after an interrupted spacer transfer

MiaCarter0992 · 2026年3月7日 17:24 UTC

回复讨论
MI
MiaCarter0992
My FR5 sequence picks a spacer, places it, then advances the saved pocket. In the interrupted example, the spacer has already left the tray but the stored pocket still points at it. A different interruption happens after placement but before that advance. Same stored number, different physical situation. I can make an uninterrupted run look fine, but restarting from that number would be guesswork. I want to take a proper recovery design to the integrator, including what the operator has to establish when the saved state cannot tell us whether a spacer is held or placed.

9 条回复

JU
JuliaBarnes0587

Write down those two interrupted cases separately, with the tray identity, attempt and last confirmed action. Then make the uncertain cases stop at a recovery decision rather than reuse the pocket as permission to pick. The integrator needs to agree what physical checks support each decision. You have already found why one counter cannot describe the whole transfer.

12
MI
MiaCarter0992

I've made an offline state table. Pick confirmed and placement confirmed are separate entries. If neither tells us the present physical state, the attempt stays unresolved instead of falling back to the normal pickup.

3
VI
VictorBell0620

Can the operator tell which tray and spacer that decision is about, Mia, rather than being shown confirm and expected to know what they are confirming?

15
MI
MiaCarter0992

Not in my first screen. It just said confirm recovery. I've replaced that with the identified tray and interrupted action in the draft, but the actual decision wording needs the integrator and trainer.

6
JU
JuliaBarnes0587

Include a tray exchange during the interruption. The saved pocket may belong to a tray that is no longer fitted, even if you now remember the last action correctly.

16
VI
VictorBell0620

And reopen while recovery is still unresolved, otherwise the second restart can undo the very caution you added to the first.

21
MI
MiaCarter0992

The tray-exchange case stays unresolved in the model. The second restart found a bug: my startup path reset recovery pending to ready. Fixed that and added it to the replay cases. Thanks, Victor.

13
JU
JuliaBarnes0587

Good catch before installation. Have the trainer try the draft with those cases without you explaining what each button secretly means.

13
MI
MiaCarter0992

They did. One phrase sounded like acknowledging a warning rather than making a physical-state decision. We are rewriting that with the integrator. Model fixed, operator wording and station checks still unfinished.

21

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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