I cannot assign this acknowledgement to an inspection attempt. Python restarted and reused the label, while its timestamps disagree with the PLC and controller. We have a timeout in the record, but not a defensible combined sequence. What can I reconstruct without pretending the closest timestamp proves ownership?
Our UR5e acknowledgement sits between two reused coupon-job labels
NathanBennett0721 · 2026年6月30日 05:38 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
1 条回复
Keep each source's original order and clock information, then look for shared event or attempt identifiers and independently established anchors. If those cannot distinguish the two attempts, retain both possible histories and the unassigned acknowledgement. The physical coupon's review owner needs that uncertainty, not a convenient guessed timeline.
20分