Sorting restart state before running 22 (Fairino FR10)

NinaArcher0414 · 24 Jul 2026, 16:06 UTC

Reply to discussion
NI
NinaArcher0414
Our setup uses Fairino FR10 for tray-to-fixture transfer with a rigid molded spacer in a small fixture loading area, with 22 planned. I wrote a pick, place and advance sequence that completes uninterrupted runs, but stopping between those actions can leave the saved pocket inconsistent with the physical state. I need a recovery design before relying on it for normal production.

10 replies

MI
MinaBrooks0859
Replying to NinaArcher0414

Can you locate the index update against the placement confirmation in the recorded sequence? The actual ordering will help identify what the saved value represents at an interruption.

16 points
NI
NinaArcher0414
Replying to MinaBrooks0859

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.

17 points
MI
MinaBrooks0859
Replying to NinaArcher0414

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.

19 points
NI
NinaArcher0414
Replying to MinaBrooks0859

@MinaBrooks0859 Would correcting the position of the index update fully address this? I had hoped the problem was limited to that single sequencing error.

18 points
MI
MinaBrooks0859
Replying to NinaArcher0414

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

6 points
JO
JoChan1114
Replying to MinaBrooks0859

@MinaBrooks0859 Updating a stage after an action doesn't eliminate the interval between the physical event and persistence. An interruption there can leave the saved stage inconsistent with reality.

10 points
MI
MinaBrooks0859
Replying to JoChan1114

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
RA
RaviBell0650
Replying to MinaBrooks0859

On my setup, one index could mean either 'still carrying' or 'already placed'. Giving those states names made the design discussion much less circular.

11 points
NI
NinaArcher0414
Replying to RaviBell0650

We've identified a sequencing issue in the index update, but recovery still needs a reviewed response to uncertain tool and pocket conditions. The job remains short of production readiness.

13 points
MI
MinaBrooks0859
Replying to NinaArcher0414

Finding the early update helps, but the uncertain states still need a recovery decision.

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