Our UR5e inspection app restarts and reuses the job label. PLC and Python clocks disagree. I can see a timeout and an acknowledgement, but can't tell which attempt the acknowledgement belongs to.
One job label, two possible acknowledgements
LinBrown0879 · 2025年6月19日 12:59 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
4 条回复
回复 LinBrown0879
Keep each source in its own recorded order first. Mark the restart and label reuse. Do you have any shared event with a known relationship that could bound the clock difference, rather than forcing the timestamps into one apparently exact sequence?
19分No reliable clock link found. Python order is clear across its saved files, but the PLC acknowledgement has only the reused job label. Leaving it unassigned.
16分回复 LinBrown0879
That is the honest limit of this reconstruction. For the interface repair, give attempts identities that survive this distinction (including a new run after restart), then test delayed acknowledgements against them.
25分回复 LinBrown0879
Did you find any independent evidence for the old acknowledgement, or does it remain unassigned?
-6分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .