Recovering inspection-cycle execution bookkeeping across a crash (Universal Robots UR5e)

AdaBennett0738 · 2026年6月2日 22:39 UTC

回复讨论

主帖中文翻译暂不可用,以下显示英文原文;回复保留原文。 查看英文原文

AD
AdaBennett0738
I'm fixing our startup bookkeeping after a crash between sending a inspection-cycle execution request and saving its result. The setup uses Universal Robots UR5e in a workshop fixture inspection cell, 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.

2 条回复

JO
JoAli0244

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

21分
AD
AdaBennett0738
回复 JoAli0244

@JoAli0244 I've found persisted submission intent and matching acceptance in the controller history, without a surviving completion record. This attempt is excluded from our automatic resend queue.

23分

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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