My FR10 saved pocket cannot say where the puck stopped

CallumAbbott0012 · 2026年8月22日 01:21 UTC

回复讨论

主帖中文翻译暂不可用,以下显示英文原文;回复保留原文。 查看英文原文

CA
CallumAbbott0012
My machined-plastic-puck transfer completes uninterrupted runs, but a stop between pick, place and advance can leave the saved pocket inconsistent with the trays. What evidence should my recovery design require before it chooses the next action? This is still a workshop test station, not normal production.

11 条回复

CH
ChloeAdams0135

Write down the source, hand and destination possibilities at each interruption boundary. Start with the saved information you actually have, not what you hoped each command accomplished.

16分
AN
AnikaBrown0943

And identify both trays; a pocket number means little after someone exchanges one.

12分
NO
NoahBaker0455

Include stops after physical placement but before its durable record advances.

-1分
CA
CallumAbbott0012

That boundary is exactly where my current design would repeat the pocket. It saves only the next index. No source or destination tray identity, and no recorded uncertain state.

15分
CH
ChloeAdams0135

Then the old saved index cannot support automatic recovery. A revised record needs tray identity and action context, with an explicit hold when physical occupancy cannot be reconciled.

0分
AN
AnikaBrown0943

More fields will not make an unconfirmed placement confirmed

11分
NO
NoahBaker0455

Agreed. Separate commanded actions from observations and from the authorised reconciliation decision.

5分
CA
CallumAbbott0012

My draft now has a held transfer with the two tray identities and relevant pockets. It does not decide placement succeeded from the release command. I still need to define who reconciles the physical state.

16分
CA
CallumAbbott0012

The offline review also found a tray swap that left a plausible pocket number. With an unrecognised destination tray, the revised draft holds the transfer rather than matching only the index.

20分
CH
ChloeAdams0135

Can the person reviewing the hold see which tray was expected and which is presently identified? That would help them report a mismatch without inviting them to choose a convenient tray name.

22分
AN
AnikaBrown0943

Test an unidentified tray too, not only a known wrong one

8分

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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