Our tray index stops matching reality after a restart (Fairino FR5)

IsaacCarter1042 · 24 Jul 2026, 05:11 UTC

Reply to discussion
IS
IsaacCarter1042
Our setup uses Fairino FR5 for fixture-to-tray transfer with a polymer sleeve in a shared parts handling bench, with 228 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

LI
LiamAdams0142
Replying to IsaacCarter1042

@IsaacCarter1042 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.

25 points
IS
IsaacCarter1042
Replying to LiamAdams0142

@LiamAdams0142 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.

13 points
LI
LiamAdams0142
Replying to IsaacCarter1042

@IsaacCarter1042 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.

8 points
IS
IsaacCarter1042
Replying to LiamAdams0142

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

17 points
LI
LiamAdams0142
Replying to IsaacCarter1042

Persisting the transfer stage as soon as each action finishes should let the recovery sequence determine the correct point to resume.

10 points
RE
ReeceChan1080
Replying to LiamAdams0142

@LiamAdams0142 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.

3 points
LI
LiamAdams0142
Replying to ReeceChan1080

@ReeceChan1080 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.

19 points
IM
ImranBrown0914
Replying to LiamAdams0142

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

20 points
IS
IsaacCarter1042
Replying to ImranBrown0914

The early index update explains part of the mismatch. I still need reviewed recovery handling for uncertain physical states, so this isn't ready for normal production.

16 points
LI
LiamAdams0142
Replying to IsaacCarter1042

The sequencing finding narrows the problem while leaving the reviewed handling of uncertain physical conditions as outstanding work.

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