How should the FR5 recover when the sleeve and saved pocket disagree?

ReeceBaker0471 · 27 Jul 2026, 12:09 UTC

Reply to discussion
RE
ReeceBaker0471
My FR5 sleeve transfer works until a stop separates placement from pocket saving. How should I plan recovery before running our planned 126?

15 replies

DA
DavidBrown0954
Replying to ReeceBaker0471

What evidence does the operator have when it stops: source pocket, held sleeve, destination pocket and active transfer stage? A saved pocket alone cannot tell them which action completed.

13points
RE
ReeceBaker0471
Replying to DavidBrown0954

Pocket number and active step. No reliable saved distinction between holding the sleeve and placement completed.

14points
FA
FarahBaker0504
Replying to ReeceBaker0471

Map the possible interrupted states before choosing recovery actions. Record transfer identity, source and destination context, and evidence of the physical state. Where the evidence cannot establish completion, the design needs an unresolved state with an approved reconciliation route.

16points
FA
FarahBennett0765
Replying to FarahBaker0504

Does removing or replacing a tray invalidate the saved context? A perfectly preserved pocket number can refer to a different physical tray after somebody intervenes.

20points
OW
OwenAli0225
Replying to FarahBaker0504

And how will you establish whether the sleeve is actually held? I would not assume the last gripper command proves its physical location. That distinction has to be part of the proposed evidence.

22points
TH
ThomasChen1147
Replying to OwenAli0225

I am untangling a similar bookkeeping uncertainty in an inspection request. Retaining an identity helps match evidence, but it doesn't establish the outcome. Reece's pocket record needs that same limit made clear to whoever uses it.

7points
IM
ImranAbbott0044
Replying to ThomasChen1147

What happens today if the operator cannot tell where the sleeve is?

17points
RO
RobinBrown0947
Replying to ImranAbbott0044

Keep that case held for the approved review, rather than offering next pocket as a default. The new screen should describe the uncertainty and evidence needed, not simply demand more confidence from the operator.

7points
RE
ReeceBaker0471
Replying to ImranAbbott0044

Today they call me. I've drafted separate transfer states and an unresolved hold, with tray identity retained.

7points
OM
OmarAbbott0056
Replying to ReeceBaker0471

Who covers that review when you're absent?

11points
KA
KaiAdams0106
Replying to OmarAbbott0056

Name the cover before accepting the handover. A hold needs somebody who can resolve it.

19points
FA
FarahBaker0504
Replying to ReeceBaker0471

Test interruption between each physical action and each persisted update, including another restart during reconciliation. Use only the evidence the real system retains. An offline example should not magically know the sleeve location because its author does.

18points
RE
ReeceBaker0471
Replying to FarahBaker0504

Controls owns those tests. Shift lead will own approved reconciliation, with escalation when evidence is insufficient. Nothing implemented yet.

8points
FA
FarahBennett0765
Replying to ReeceBaker0471

Please include authorised manual movement in the context record as well as tray replacement. The operator may legitimately remove a sleeve for inspection while the original saved stage remains unchanged.

13points
RE
ReeceBaker0471
Replying to FarahBennett0765

Added. Thanks, Farah Bennett; tray identity alone missed manual sleeve movement. Recovery design remains under review before production use.

6points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.