My FR10 saved pocket cannot say where the puck stopped

CallumAbbott0012 · 22 Aug 2026, 01:21 UTC

Reply to discussion
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 replies

CH
ChloeAdams0135
Replying to CallumAbbott0012

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 points
AN
AnikaBrown0943
Replying to ChloeAdams0135

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

12 points
NO
NoahBaker0455
Replying to ChloeAdams0135

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

-1 points
CA
CallumAbbott0012
Replying to NoahBaker0455

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 points
CH
ChloeAdams0135
Replying to CallumAbbott0012

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 points
AN
AnikaBrown0943
Replying to ChloeAdams0135

More fields will not make an unconfirmed placement confirmed

11 points
NO
NoahBaker0455
Replying to AnikaBrown0943

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

5 points
CA
CallumAbbott0012
Replying to NoahBaker0455

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 points
CA
CallumAbbott0012
Replying to AnikaBrown0943

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 points
CH
ChloeAdams0135
Replying to CallumAbbott0012

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 points
AN
AnikaBrown0943
Replying to ChloeAdams0135

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

8 points

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.