简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
OliverBarnes0537 · 2026年6月12日 07:09 UTC
What job reference is retained with it? A high bit alone cannot identify the plate.
8分There's a sequence number beside it. The application reads both, but the reconnect handler treats any high completion as a new event regardless of the number.
17分Does that sequence number survive a PLC restart without being reused?
13分It restarts at zero. We've only reproduced the duplicate on a communication drop so far, with no PLC restart involved.
11分Your reproduced case is narrower, then. Number reuse still needs an answer before a general fix.
21分Can the screen show a retained result awaiting reconciliation without presenting it as the current job? I would want the operator to see why no new completion was counted.
19分Currently no. It has completed or running, which is a poor choice when the application has just lost its connection and has not matched anything.
12分That wording belongs in the handover as well. I am trying to recover missing interface definitions on another inspection setup; a developer's private understanding is not much use to the next shift.
19分Has a developer proposed where processed result identities persist, Oliver, or is that also missing?
11分And what happens when identity is absent? I wouldn't let the screen guess a plate.
15分Oscar and Amara, persistence and unknown identity are still design questions. Hazel's pending state is in the screen draft. We haven't agreed the run identity with the PLC owner yet.
0分