one FR5 acknowledgement between two uses of the same job label

ZaraChen1178 · 6 Sept 2025, 05:20 UTC

Closed
ZA
ZaraChen1178
Inspection timed out, then our application restarted and reused the housing job label. Three clocks disagree. I cannot assign the acknowledgement.

8 replies

FE
FelixBaker0458
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?

25 points
ZA
ZaraChen1178
Replying to FelixBaker0458

Startup entries split Python into two runs. PLC acknowledgement retains only the repeated job label.

11 points
FE
FelixBaker0458
Replying 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.

18 points
RE
RebeccaAli0256
Replying to ZaraChen1178

What does acknowledged mean here? Request received, or inspection completed? I'd check that before worrying which result it confirms.

14 points
ZA
ZaraChen1178
Replying to RebeccaAli0256

Receipt, according to controls. It cannot establish inspection completion even if we identify the attempt.

16 points
ZA
ZaraChen1178
Replying to FelixBaker0458

Original capture has no additional attempt field. No reliable link found so far; acknowledgement remains unassigned.

9 points
RE
RebeccaAli0256
Replying to ZaraChen1178

Unhelpful answer, but honest. Keep receipt separate from the outcome question in the handover.

5 points
FE
FelixBaker0458
Replying 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.

16 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .