Fairino FR5: Sorting restart state before running 154

RaviBell0650 · 13 Jul 2026, 04:40 UTC

Reply to discussion
RA
RaviBell0650
My Fairino FR5 program picks a machined plastic puck, places it and advances the pocket during tray-to-fixture transfer in a small fixture loading area. Clean runs work. After a stop between actions, the saved pocket sometimes doesn't match reality. We've 154 planned, and I want recovery sorted before normal production depends on it.

13 replies

LU
LucaAli0178
Replying to RaviBell0650

@RaviBell0650 Where does the index advance in your trace, relative to placement confirmation? Start with the sequence you've, not where the number ought to change.

12 points
RA
RaviBell0650
Replying to LucaAli0178

It advances before placement confirmation. So after a stop, the number can describe the next intended pocket rather than a transfer we know finished. That's on my sequence.

14 points
LU
LucaAli0178
Replying to RaviBell0650

Map the transfer stages offline, with an agreed completion confirmation. Have your integrator define how saved state is reconciled with tool and pocket conditions; unknown conditions need an explicit recovery route.

6 points
RA
RaviBell0650
Replying to LucaAli0178

So just moving the increment isn't enough? I'd hoped this was one badly placed line, which would've been embarrassing but convenient.

5 points
LU
LucaAli0178
Replying to RaviBell0650

Save the stage immediately after every action and you should always know where to resume.

13 points
LO
LouisCarter1007
Replying to LucaAli0178

There's still a gap between the physical action and the save. A stop in that gap leaves you guessing, just with a more descriptive variable.

0 points
LU
LucaAli0178
Replying to LouisCarter1007

@LouisCarter1007 You're right; saving stages alone doesn't guarantee recovery. The saved stage guides reconciliation, and the physical conditions still need confirmation before an approved next action.

8 points
MA
MayaAdams0127
Replying to LucaAli0178

My separate tray application could retain the same pocket value with the workpiece either held or placed. Explicit stage names helped us discuss those distinct conditions without relying on the index alone.

10 points
RA
RaviBell0650
Replying to MayaAdams0127

Our test actually stopped with the workpiece held while the display said to start another pickup. The recovery message was confidently wrong.

12 points
RO
RosaBell0640
Replying to RaviBell0650

@RaviBell0650 Can recovery infer a held workpiece from the gripper's closed indication, or does that indication fail to establish actual possession?

7 points
LU
LucaAli0178
Replying to RosaBell0640

@RosaBell0640 It depends on what your installed sensing actually establishes. A closed indication isn't automatically proof of a held workpiece; document confirmed, empty and unknown conditions with your integrator.

7 points
RA
RaviBell0650
Replying to LucaAli0178

@LucaAli0178 I've settled on explicit stages plus physical-state reconciliation for the redesign. Any production use depends on integrator review and successful interruption checks; moving the index update alone isn't my fix.

8 points
LU
LucaAli0178
Replying to RaviBell0650

@RaviBell0650 That gives the redesign a clear acceptance condition. The saved state and physical checks now have distinct jobs in your proposal.

16 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.