简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
NadiaChan1074 · 2025年3月21日 11:44 UTC
What identifies the completed job in the retained registers? You need to compare known results, not throw away a reading because it arrived first.
11分There is a retained job identifier. The local results file also stores it. The monitor's counter ignores that file on startup and just counts observed completion changes.
4分Reconcile the retained identifier with saved results on reconnect. How does the interface prevent identifier reuse from making a later job look like an old one?
24分Include both outage cases in your offline tests: a result already saved, and a result produced while the monitor was absent. Ignoring the first reading makes one screen look right by losing evidence from the other.
4分Did you establish the identifier lifetime? That's still needed before matching against the saved file can be treated as reliable.
25分Identifier reuse is possible after controller maintenance. Controls is revising the interface to include a run boundary. The blanket ignore-first-reading patch is dropped; uncertain matches will stay visibly unresolved during commissioning.
17分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .