OliverBarnes0537 · 12 Jun 2026, 07:09 UTC
What job reference is retained with it? A high bit alone cannot identify the plate.
8 pointsThere'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 pointsDoes that sequence number survive a PLC restart without being reused?
13 pointsIt restarts at zero. We've only reproduced the duplicate on a communication drop so far, with no PLC restart involved.
11 pointsYour reproduced case is narrower, then. Number reuse still needs an answer before a general fix.
21 pointsCan 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 pointsCurrently 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 pointsThat 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 pointsHas a developer proposed where processed result identities persist, Oliver, or is that also missing?
11 pointsAnd what happens when identity is absent? I wouldn't let the screen guess a plate.
15 pointsOscar 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 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.