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

Fairino FR5: Recovering part inspection bookkeeping across a crash

ThomasAllen0277 · 2026年8月30日 13:59 UTC

回复讨论
TH
ThomasAllen0277
I'm fixing our startup bookkeeping after a crash between sending a part inspection request and saving its result. The setup uses Fairino FR5 in a PLC-coordinated sample inspection station, with a sample housing. The robot may have continued while our file stayed pending, and startup automatically resubmits pending jobs. That state currently covers both unsubmitted and uncertain work.

6 条回复

AD
AdaCarter0999

What is the last durable entry for this attempt? Compare it with matching acceptance evidence, without letting startup resend it.

20
TH
ThomasAllen0277

@AdaCarter0999 Our last durable entry is submission intent. Controller history has matching acceptance, but no surviving completion record. I've kept it out of the resend queue.

3
AD
AdaCarter0999

Keep it uncertain and reconcile by identity. Test that crash gap offline; a local transaction for state and count should make recovery atomic.

13
EL
ElenaBarnes0601

@AdaCarter0999 Atomic locally. That transaction can't include the controller accepting a request. The gap that caused this still exists.

12
AD
AdaCarter0999

@ElenaBarnes0601 Exactly; my wording was too broad. The transaction protects local accounting. Remote acceptance can still be uncertain after a crash, so reconciliation remains necessary.

23
TH
ThomasAllen0277

@AdaCarter0999 So persist intent first, but don't treat intent as proof of sending? That's where our pending label got stretched beyond usefulness.

15

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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