简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

Our tray index stops matching reality after a restart

CalebBaker0493 · 2026年4月30日 13:55 UTC

回复讨论
CA
CalebBaker0493
My Fairino FR10 program picks a rigid molded spacer, places it and advances the pocket during indexed tray loading in a small fixture loading area. Clean runs work. After a stop between actions, the saved pocket sometimes doesn't match reality. We've 90 planned, and I want recovery sorted before normal production depends on it.

15 条回复

RA
RachelAli0261

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.

20
CA
CalebBaker0493

The trace shows my index update occurs before placement is confirmed. That means the retained number can identify an intended next pocket without establishing that the preceding transfer completed.

13
RA
RachelAli0261

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

22
CA
CalebBaker0493

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

17
RA
RachelAli0261

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

18
CA
CarlaBrooks0836

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.

12
RA
RachelAli0261

@CarlaBrooks0836 I overstated what persistence provides. A retained stage helps interpret the interruption, but recovery still requires reconciling it with established physical conditions and selecting the permitted action.

17
CL
ClaraBell0611

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

17
CA
CalebBaker0493

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

12
SA
SaraAdams0113

Wouldn't a grip signal settle that? Or can 'gripper closed' mean it's holding nothing?

17
RA
RachelAli0261

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
CA
CalebBaker0493

The destination worries me too. If placement happened but the save didn't, the program could send another workpiece to an occupied pocket, right?

4
RA
RachelAli0261

Yes, that's an ambiguity your recovery design must cover. Establish destination condition through suitable evidence or a defined operator procedure, with escalation when it can't be confirmed.

14
CA
CalebBaker0493

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.

10
RA
RachelAli0261

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

23

参与讨论

欢迎来到 Application Robot

所有人都可以阅读论坛。登录或注册后即可发起讨论、回复或上传照片。

忘记密码?

注册账号即表示你同意我们的 使用条款 社区准则。请阅读我们的 隐私政策 ,了解我们如何处理你的信息。