Completion stays high through the outage. The monitor reconnects and counts it again, without another inspection. I want the retained observation matched to its actual attempt, not cleared or replayed for convenience.
Our UR5e monitor rewards reconnect with another housing completion
CallumAdams0099 · 2026年1月2日 20:07 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
3 条回复
Start with what identity and saved history survive on each side. A retained flag and a familiar housing name may not distinguish the old attempt from a new one. Can the developers show whether this result was already accepted before the disconnect, and what happens when its owner cannot be established?
8分回复 NinaChen1197
Application has its earlier accepted row. PLC interface exposes the job name and completion flag, no attempt reference yet identified. The revised monitor holds the observation separately while controls investigates ownership.
20分Keep a genuinely new completion in the offline tests too. Ignoring everything after reconnect would stop the duplicate very efficiently, but it would not be a useful fix. Also check both sides restarting, not only the monitor reconnecting.
17分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .