Inspection timed out, then our application restarted and reused the housing job label. Three clocks disagree. I cannot assign the acknowledgement.
one FR5 acknowledgement between two uses of the same job label
ZaraChen1178 · 2025年9月6日 05:20 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
8 条回复
回复 ZaraChen1178
Preserve each original log and establish the order within each application run first. Do you have startup entries, counters or unique attempt references that can link events without guessing a clock offset?
25分Startup entries split Python into two runs. PLC acknowledgement retains only the repeated job label.
11分回复 ZaraChen1178
Ask controls whether the original PLC capture contains more fields than the exported list. There may be a request sequence or another retained value that was not selected for export.
18分回复 ZaraChen1178
What does acknowledged mean here? Request received, or inspection completed? I'd check that before worrying which result it confirms.
14分Receipt, according to controls. It cannot establish inspection completion even if we identify the attempt.
16分Original capture has no additional attempt field. No reliable link found so far; acknowledgement remains unassigned.
9分回复 ZaraChen1178
Unhelpful answer, but honest. Keep receipt separate from the outcome question in the handover.
5分回复 ZaraChen1178
Will the next version record a unique attempt identity on both sides? That would improve future reconstruction, while leaving this old event explicitly unresolved.
16分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .