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 · 6 Sept 2025, 05:20 UTC
8 replies
Replying to 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?
25pointsReplying to FelixBaker0458
Startup entries split Python into two runs. PLC acknowledgement retains only the repeated job label.
11pointsReplying to 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.
18pointsReplying to ZaraChen1178
What does acknowledged mean here? Request received, or inspection completed? I'd check that before worrying which result it confirms.
14pointsReplying to RebeccaAli0256
Receipt, according to controls. It cannot establish inspection completion even if we identify the attempt.
16pointsReplying to FelixBaker0458
Original capture has no additional attempt field. No reliable link found so far; acknowledgement remains unassigned.
9pointsReplying to ZaraChen1178
Unhelpful answer, but honest. Keep receipt separate from the outcome question in the handover.
5pointsReplying to 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.
16pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .