简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

one FR5 acknowledgement between two uses of the same job label

ZaraChen1178 · 2025年9月6日 05:20 UTC

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

8 条回复

FE
FelixBaker0458

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
ZA
ZaraChen1178

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

11
FE
FelixBaker0458

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
RE
RebeccaAli0256

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

14
ZA
ZaraChen1178

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

16
ZA
ZaraChen1178

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

9
RE
RebeccaAli0256

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

5
FE
FelixBaker0458

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

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .